[Elecraft] K2

[Don Wilhelm]

Larry,

Might I suggest that you examine the keycap to be certain it is not 
binding on the front panel metal.  That could cause very strange 
behavior.  If it sticks, the switch will not release quickly enough for 
the firmware to differentiate between a tap and a press.  If there is no 
mechanical problem, then you may have a sticky switch that needs to be 
replaced.  The switches are quite reliable and I have never had a sticky 
one, but there is always a first time.  The only difference between a 
tap and a hold is the time the switch is closed (as measured by the 
firmware).  The same firmware routine is used for all other buttons, so 
if it were a firmware problem, all buttons would show similar problems.

As for the BAND- button going to a band up, that is strange, but not 
likely related to the tap/hold situation on the band+ button.  For that, 
I would look at FP U2 and RP1 very closely - reflow the solder with a 
hot iron (750 to 800 deg F) to be sure both the component  leads and the 
solder pads received adequate heat.

73,
Don W3FPR

L. D. Ingram wrote:
> Hi,
>
> I recently build my second K2 sn 06405. Receiver and transmitter are 
> working fine and I have enjoyed a number of QSOs on 40, 30 and 20 
> meters and the rest of the bands have been checked out with a signal 
> generator and transmitting into a dummy load.
>
> However, occasionally when I go to switch bands with the up (+) key it 
> will go into the RCL mode instead. After the first time I was very 
> careful to just tap the button and not hold it - but it still happens. 
> Also, I don't know if this is related or not, but even more 
> occasionally, when I hit the down (-) button the band goes to the next 
> higher band rather than the lower one. When that happens, the band 
> will continue to go higher with each tap of the down button until I 
> tap the up button.
>
> I have resoldered the switch pins and checked that the IC's are 
> properly seated.
>
> Has anyone else run across this problem - and if so, what was the 
> solution?
>