[Elecraft] K-Pod button problems

Wes wes_n7ws at triconet.org
Thu Sep 28 11:51:24 EDT 2023


Is the firmware up to date?



On 9/27/2023 5:39 PM, ws6x.ars at gmail.com wrote:
> Hello John & the Elecraft Gang,
> I have a similar problem with one of my KPOD switches. (I also use the KPOD
> for RIT when I'm running in CW and RTTY.) In my case, I have F3 programmed
> to toggle in and out of Diversity RX. Tap F3 = DIV; Tap & Hold F3 = clear
> DIV. For many years this worked like a charm, but recently when operating
> SPLIT, if I tap F3, it clears SPLIT. If I put the radio back into SPLIT, Tap
> & Hold F3 again clears SPLIT. The same DIV on/off with the SUB button on the
> radio does not mess with SPLIT.
> If this function hadn't operated correctly before, I would naturally suspect
> a programming issue. Could this somehow be defective switches? Reload
> firmware? BTW: the F3 Tap / F3 Tap & Hold by themselves work flawlessly.
> Any ideas much appreciated!
> Jim - WS6X
>
> -----Original Message-----
> From: elecraft-bounces at mailman.qth.net <elecraft-bounces at mailman.qth.net> On
> Behalf Of john at kk9a.com
> Sent: Wednesday, September 27, 2023 8:11 PM
> To: elecraft at mailman.qth.net
> Subject: [Elecraft] K-Pod button problems
>
> During the weekend's WW RTTY contest I used a K3S and a K-Pod.  The K-Pod
> worked great for RIT control.  I tried to use it to occasionally switch my
> RX antenna in and out but then I was quickly reminded why I do not use this
> function and instead use the RX ANT button on the radio.  I have the F4
> button programed so a quick press toggles the RX antenna and a long press
> switches the radio to 40m.   What happens on random occasions is tapping the
> F4 button will switch the radio to 160m instead of toggling the RX antenna
> input.  It is really annoying to be running stations on 40m and then the
> radio just jumps to another band. The QSO gets messed up and there is a risk
> of losing the run frequency.  Incidentally a long press of F8 is programmed
> to switch the radio to 160 and that was definitely not accidently touched.
> I am unsure of the firmware version.  Is this a known problem?  Is here a
> cure?
>
> John KK9A  (W4AAA in 2023 CW WW RTTY contest)
>
>
>
> ______________________________________________________________
> Elecraft mailing list
> Home: http://mailman.qth.net/mailman/listinfo/elecraft
> Help: http://mailman.qth.net/mmfaq.htm
> Post: mailto:Elecraft at mailman.qth.net
>
> This list hosted by: http://www.qsl.net
> Please help support this email list: http://www.qsl.net/donate.html Message
> delivered to ws6x.ars at gmail.com
>
> ______________________________________________________________
> Elecraft mailing list
> Home: http://mailman.qth.net/mailman/listinfo/elecraft
> Help: http://mailman.qth.net/mmfaq.htm
> Post: mailto:Elecraft at mailman.qth.net
>
> This list hosted by: http://www.qsl.net
> Please help support this email list: http://www.qsl.net/donate.html
> Message delivered to wes_n7ws at triconet.org



More information about the Elecraft mailing list