On Mon, Feb 12, 2018 at 3:52 PM, Ken K6MR <k...@gmx.com> wrote:
> If you have a K3 without the Sub Rx, turning on XIT will change the
> transmit frequency on whichever VFO is set to transmit: VFO A if Split is
> off, VFO B is split is on. The receive frequency is not affected. XIT
> affects VFO A only in transmit, and VFO B when in Split. Perfect.
> If you have Sub Rx, turning on XIT with both Sub Rx and Split active
> immediately changes the VFO B frequency (which is now a receive
> frequency). VFO B is being handled as it is with the Sub Rx, which seems
> (to me) not quite right. It would make more sense (I think) if XIT was
> only applied to VFO B during transmit when the SubRx is active and Split is
Perhaps, but when working split, with the SubRx on, what is the real world
scenario where you do *not* what to listen to your transmit frequency? It
makes more sense (to me) to always use the SubRx to listen to "your place
in the pileup," so you can tell if you are calling on a clear frequency or
a crowded one. Also, why bother with XIT at all when you're working
split? Just keep XIT off and the much bigger VFO B knob, or use a command
to move VFO B rather than move XIT.
It would be very distracting to see the VFO B frequency jumping back and
forth in full QSK mode when operating split, with the XIT on and the XIT
offset set to a non-zero value, which is what you seem to be requesting. I
really prefer the way it works now.
But frankly, I almost never use split. I find it much easier to put the DX
in the SubRX and just move the big VFO A knob to find a calling frequency.
I also adjust the BALANCE control (CONFIG:SUB AF = BALANCE) so that the DX
is always louder than the pileup, and in one ear only.
Elecraft mailing list
This list hosted by: http://www.qsl.net
Please help support this email list: http://www.qsl.net/donate.html
Message delivered to arch...@mail-archive.com