[Elecraft] [KX3] Key Clicks / Ringing - September Experiment **Updated**

[Joel Black]

A few days ago, I wrote that my biggest annoyance with the KX3 were the 
key clicks / ringing when working split. After installing the latest 
Beta F/W (2.23), and turning the KX3's RX IF shift to 8.0, the ringing 
is gone!

Last night, I worked W1AW/5 on 30 m split (1 up) and there was no ringing.

Thank you, Elecraft. Thank you, Wayne.

For the next week or so, my September setup is back on track.

Another thing from the list I previously posted:

You *can*, in a way, have more than one macro loaded at a time - you can 
create each macro so that it will call up the next macro effectively 
cycling through your list of macros. I think I posted here before where 
one press of PF1 will put me in CW mode, copy VFO A to VFO B, turn on 
split, turn on dual watch, and change VFO B so it is 1 kHz higher. That 
macro then calls a second macro that undoes all that. The first long 
hold of PF1 turns all that on; the second long hold turns it all off.

You could have PF1 (or PF2) setup so that if you were working W1AW/p 
(for example) on CW split on one band and then RTTY split on another so 
that your macro button steps through the macros. Now, how useful this is 
to each individual operator is completely subjective.

73/72,
Joel - W4JBB

On 9/22/14, 6:00 PM, Joel Black wrote:
>
> I can only have two macros loaded in the KX3 at any given time. The K3 
> can have up to eight (I think I have four and could truly reduce that 
> to two or three - I wouldn't need the ATU macro).
>
> My absolute biggest annoyances are the key clicks and digital ringing 
> when working split / dual watch in either mode. The *only* way I found 
> to get rid of the key clicks was to turn off dual watch and just 
> operate split. However, if I read the manual correctly, this 
> eliminates the ability to listen to both VFO A and VFO B. The KX3 
> Operating Manual, Rev B4, June 01, 2012 it states, "Dual Watch 
> Limitations... A wider roofing filter than normal will be selected 
> automatically, if required, based on the frequency span between VFO A 
> and VFO B."
>