On Wed,10/1/2014 7:47 PM, Fred Jensen wrote:
Start every transmission with {TX}{ENTER}TEXT and follow the text by one space and {RX}.
What Fred means is that TEXT is what you want to send with that F-key. :)
The {ENTER} starts you on his next line, clear of any garbage he's printed before you answered or called. The space at the end of your transmission clears you of the noise he's going to print as soon as your MARK goes away.
I really hate Line Feeds (the ENTER). Especially when you're running several decode windows, they must be pretty small, and a few Line Feeds will scroll too much stuff out of the window! What I like much better is a leading space and a trailing space for every F-Key message. Those spaces are enough to separate your call and exchange from whatever other stuff is on the screen, because N1MM and WriteLog will highlight calls. And if that space is there, you can click on the call (and parts of the exchange), which will copy them to the data entry window!
I agree with all of Fred's other advice, except that when I'm running, I send the other guy's call again at the end of the exchange if I think there is QRM, or if I doubled with him because he sent his call again after I had begun responding. Also, in S&P, I send nothing but the exchange UNLESS I think he mis-copied my call, in which case I'll send it again, twice, then send the exchange.
One of the rules of contesting (and DXing) is NEVER send something the other guy has already gotten right. That can be tricky to know with RTTY, because decoders often make mistakes on calls. In contesting, if he gets your call wrong, HE loses points but you do not. And it's good sportsmanship to try to correct him.
73, Jim K9YC ______________________________________________________________ Elecraft mailing list Home: http://mailman.qth.net/mailman/listinfo/elecraft Help: http://mailman.qth.net/mmfaq.htm Post: mailto:[email protected] This list hosted by: http://www.qsl.net Please help support this email list: http://www.qsl.net/donate.html Message delivered to [email protected]
