Dick Thompson wrote: "I would like to put forth a suggestion to those who are entering the ARRL RTTY Contest, especially the newer people. The report that you send is a signal report & State or Provi
Hi I hope that everyone send a DE before there callsign and a 599 before the exchange. All the programs I have seen needs those two worde so they know that a callsign is comming and a exchange. If th
Hi Robert and All: Yes, I agree, please do Not send "dashes" between anything, 599 05 is quite enough. Robert, again congratulations on your New Callsign - TF3TTY looks darn good, Happy New Year, you
For the upcoming ARRL RTTY Roundup the exchange is your state as in 599 TX. You can always get great message examples at http://rttycontesting.com/ 73 Terry - AB5K __________________________________
hi Tyler. All true. if we are talking about being fast or speed. Then I would be very happy too see something on the reflector to speed things up. When I have to sit and watch all these ham's calling
For slower paced contests that may be fine, but unless you send a new shift character before each character group, many of us will unshift. If you do it properly by at least shifting (let alone unshi
Once you have unshifted, unless you send a figures shift character, you will be getting the "too etu too etu" characters, then you have to look at the keyboard and figure what the heck number "etu" i
ORIGINAL MESSAGE: ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ It's not a question of smart or dumb decoders, it's an inherent issue with Unshift On Space (USOS). What you are doing by sending d
I did see that when I was using writelog and mmty programs, But never when using rckrtty. if a report is TOO it's converted to 599 and thes is as it should be. I was in a qso with a station's in euro
Hmmm, perhaps sending "5NN OR OR" instead of "599 OR OR" is not such a bad idea after all !! HI HI UE and Happy New Year. See y'all in the Roundup. I will be operating W9OL-style (single op, don't ca
Hi Bill. I did read about it long time ago but I forgot it. I guess it's because I never think about it any moore. I have seen this dashes in many rtty programs as a default and always removed the da
it depends on what the exchange is.....for Roundup, you are correct. It would be best to NOT send the dash. In contests where the exchange is a number, however, you are better off to send 599-05-05 o
ORIGINAL MESSAGE: ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ Even better would be FNN OR OR. :-) 73, Bill W6WRT _______________________________________________ RTTY mailing list RTTY@contestin
ORIGINAL MESSAGE: ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ I disagree. With no spaces, you lose the advantage of USOS, even with all numbers. If the FIGS shift character gets munged at the s
Oh, good point! Yes, definitely if you are separating say the 599 from the QTH or something else that contains letters, use a space or even a new line if conditions are tough. I was only thinking abo
Wouldn't it be: TOOAPTAPTAPT ? (The dash is a shifted A if I remember correctly) Most of us recognize the correct numbers in this case are the ones directly above the letter keys for what appears on
In fact, I will usually send: 599-05 05 The best of both worlds! 73 - Jim AD1C -- Jim Reisert AD1C, 7 Charlemont Court, North Chelmsford, MA 01863 USA +978-251-9933, <jjreisert@alum.mit.edu>, http://
ORIGINAL MESSAGE: ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ Correct. A long time ago someone commented that the dash was present in both LTRS and FIGS case and I assumed that to be true. Not
ORIGINAL MESSAGE: ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ That depends on what you mean by "better". If you mean faster sending, you are correct. If you mean more likely to get through, not
Just like I usually send DE W7AY W7AY to keep the programs that need "DE" happy. 73 Chen _______________________________________________ RTTY mailing list RTTY@contesting.com http://lists.contesting.