On Fri, Jun 5, 2009 at 9:45 AM, John Laney <k4bai at worldnet.att.net> wrote:
> I agree with almost everything in the article. ?I recognize the problem
> keeping the monitor on while doing SO2R. ?I keep it on, but low, most of
> the time. ?The reason that I recommend keeping the monitor on is that
> way you know if you hit the wrong key (or if you programmed the key
> wrong).
N1MM has a scrolling display that shows what is being sent - you can
glance at it to confirm what's sending while RXing on the other
radio....no need to listen.
> For example, "TEST CU2X." ?"TU CU2CJ." ?Obviously, the CQ
> message had been changed from the last time the program had been used,
> but the op forgot to change the TU message.
Most programs (at least the good ones) have a "MYCALL" variable that
can be programmed with the call - no need to hard-code the call into
memory messages. "TEST MYCALL" and "TU MYCALL", etc. are all fixed in
the contest setup where part of the routine would be to set
MYCALL=CU2X or whatever.
--
Lee Hiers
"Have Dobro Will Travel"
|