Posted by
Guy, K2AV on
May 12, 2011; 3:05pm
URL: http://elecraft.85.s1.nabble.com/K3-Why-isn-t-QRQ-the-default-tp6355046p6356102.html
Maybe because it would introduce an unknown change in behavior to the
uninitiated and generate tech support calls.
He'd have to take the time to make the change smooth and gradual based
on what was turned on and the keying speed and how much the offset
was.
At least if you turn the option on, then you know about it. I'd still
like to see limited RIT/XIT (+/- 250 Hz) in the short term without
dropping QRQ.
But I'll bet that change is into as lot of stuff. Timing is a PITA, top shelf.
You can do split with 2nd RX as long as you use VFO A for transmit and
VFO B for RX. I lock VFO A. That way the A VFO does not have to do a
shift from RX freq to TX frequency. Also works for doing "RIT" in
contests. But you have to program your contest logger to send A->B
command when you clear the QSO because clear RIT command in logger
does not work. And then because it's in the logger macros, it means
you have to do it that way all contest while running. It's OK when
you get used to it like that. The QSK at contest speeds is awesome if
your amp can follow. You hear the amp changing state, not the
transceiver.
73, Guy
On Thu, May 12, 2011 at 5:08 AM, Stewart Rolfe <
[hidden email]> wrote:
______________________________________________________________
Elecraft mailing list
Home:
http://mailman.qth.net/mailman/listinfo/elecraftHelp:
http://mailman.qth.net/mmfaq.htmPost: mailto:
[hidden email]
This list hosted by:
http://www.qsl.netPlease help support this email list:
http://www.qsl.net/donate.html