Strange bandswitch behavior - incorrect command interpretation

[Chris Hallinan]

Tonight I turned on my 8-month old K3, and went to switch from 80m to 40m.
Pressing the right side of the BAND rocker switch, the radio began
incorrectly interpreting different commands, and the behavior was
repeatable even after power cycle.  First couple of presses changed modes.
Next press engaged the NR icon.  Third press resulted in the message "NO
ATU" in the VFO-B window.

BAND-Down seems to be OK.

The only thing "different" is I just added a P3 to my setup, and while
doing so, I upgraded to the latest released firmware using the K3 utility
program.

After some more pressing of the band up function, it seems to have come
back to normal.  Come to think of it, this is not the first time I've run
into a confused command after a button press, but I've ignored them until
now.

Anyone else seen similar behavior?

Chris

--
Life is like Linux - it never stands still.
______________________________________________________________
Elecraft mailing list
Home: http://mailman.qth.net/mailman/listinfo/elecraft
Help: http://mailman.qth.net/mmfaq.htm
Post: mailto:[hidden email]

This list hosted by: http://www.qsl.net
Please help support this email list: http://www.qsl.net/donate.html
Message delivered to [hidden email]

[Warren Merkel]

Chris,
I had the same issue with the band down side.  With the power off, I just rapidly and aggressively pushed on the band down side with moderate pressure -- maybe 20 times.  The switch seemed to be sticky when new.  The issue returns if the button is partly depressed in haste.

Elecraft support advised me I was the first to report this and if I sent it back, they would test the unit's functionality.  I decided not to do that due to shipping cost--for such a trivial issue-waiting for it to fail completely.

Warren, KD4Z
K3 #8902


On August 11, 2015 8:44:05 PM EDT, Chris Hallinan <[hidden email]> wrote:

>Tonight I turned on my 8-month old K3, and went to switch from 80m to
>40m.
>Pressing the right side of the BAND rocker switch, the radio began
>incorrectly interpreting different commands, and the behavior was
>repeatable even after power cycle.  First couple of presses changed
>modes.
>Next press engaged the NR icon.  Third press resulted in the message
>"NO
>ATU" in the VFO-B window.
>
>BAND-Down seems to be OK.
>
>The only thing "different" is I just added a P3 to my setup, and while
>doing so, I upgraded to the latest released firmware using the K3
>utility
>program.
>
>After some more pressing of the band up function, it seems to have come
>back to normal.  Come to think of it, this is not the first time I've
>run
>into a confused command after a button press, but I've ignored them
>until
>now.
>
>Anyone else seen similar behavior?
>
>Chris
>
>--
>Life is like Linux - it never stands still.
>______________________________________________________________
>Elecraft mailing list
>Home: http://mailman.qth.net/mailman/listinfo/elecraft
>Help: http://mailman.qth.net/mmfaq.htm
>Post: mailto:[hidden email]
>
>This list hosted by: http://www.qsl.net
>Please help support this email list: http://www.qsl.net/donate.html
>Message delivered to [hidden email]

--
Sent from my Android device with K-9 Mail. Please excuse my brevity.
______________________________________________________________
Elecraft mailing list
Home: http://mailman.qth.net/mailman/listinfo/elecraft
Help: http://mailman.qth.net/mmfaq.htm
Post: mailto:[hidden email]

This list hosted by: http://www.qsl.net
Please help support this email list: http://www.qsl.net/donate.html
Message delivered to [hidden email]

[Jerry Moore]

Get Elecraft blessing first, however, a quality electrical contact cleaner with plastic safe contact lubricant will likely help. Check with Elecraft before using anything.

Jerry Moore
K3S future owner

On August 11, 2015 8:44:05 PM EDT, Chris Hallinan <[hidden email]> wrote:

>Tonight I turned on my 8-month old K3, and went to switch from 80m to
>40m.
>Pressing the right side of the BAND rocker switch, the radio began
>incorrectly interpreting different commands, and the behavior was
>repeatable even after power cycle.  First couple of presses changed
>modes.
>Next press engaged the NR icon.  Third press resulted in the message
>"NO
>ATU" in the VFO-B window.
>
>BAND-Down seems to be OK.
>
>The only thing "different" is I just added a P3 to my setup, and while
>doing so, I upgraded to the latest released firmware using the K3
>utility
>program.
>
>After some more pressing of the band up function, it seems to have come
>back to normal.  Come to think of it, this is not the first time I've
>run
>into a confused command after a button press, but I've ignored them
>until
>now.
>
>Anyone else seen similar behavior?
>
>Chris
>
>--
>Life is like Linux - it never stands still.
>______________________________________________________________
>Elecraft mailing list
>Home: http://mailman.qth.net/mailman/listinfo/elecraft
>Help: http://mailman.qth.net/mmfaq.htm
>Post: mailto:[hidden email]
>
>This list hosted by: http://www.qsl.net
>Please help support this email list: http://www.qsl.net/donate.html
>Message delivered to [hidden email]

--
Sent from my Android device with K-9 Mail. Please excuse my brevity.
______________________________________________________________
Elecraft mailing list
Home: http://mailman.qth.net/mailman/listinfo/elecraft
Help: http://mailman.qth.net/mmfaq.htm
Post: mailto:[hidden email]

This list hosted by: http://www.qsl.net
Please help support this email list: http://www.qsl.net/donate.html
Message delivered to [hidden email]

[Dave Hachadorian-2]

There have been problems with the pushbutton switches in the four
controls to the left of the main VFO knob (e.g. speed/mic).  Push
the buttons and twiddle the shafts of these controls for two
minutes each, and the problem will probably not recur.  When
these controls fail, they cause multiple addressing problems.

I had a similar problem a couple years ago, and ordered four
replacement encoder/switches, which are surprisingly inexpensive.
When I went to actually do the job, it looked nasty, and I never
replaced them.  The problem has never recurred.

Dave Hachadorian, K6LL
Yuma, AZ

-----Original Message-----
From: Chris Hallinan
Sent: Tuesday, August 11, 2015 5:44 PM
To: <[hidden email]>
Subject: [Elecraft] Strange bandswitch behavior - incorrect
commandinterpretation

Tonight I turned on my 8-month old K3, and went to switch from
80m to 40m.
Pressing the right side of the BAND rocker switch, the radio
began
incorrectly interpreting different commands, and the behavior was
repeatable even after power cycle.  First couple of presses
changed modes.
Next press engaged the NR icon.  Third press resulted in the
message "NO
ATU" in the VFO-B window.

BAND-Down seems to be OK.

The only thing "different" is I just added a P3 to my setup, and
while
doing so, I upgraded to the latest released firmware using the K3
utility
program.

After some more pressing of the band up function, it seems to
have come
back to normal.  Come to think of it, this is not the first time
I've run
into a confused command after a button press, but I've ignored
them until
now.

Anyone else seen similar behavior?

Chris

--
Life is like Linux - it never stands still.
______________________________________________________________
Elecraft mailing list
Home: http://mailman.qth.net/mailman/listinfo/elecraft
Help: http://mailman.qth.net/mmfaq.htm
Post: mailto:[hidden email]

This list hosted by: http://www.qsl.net
Please help support this email list:
http://www.qsl.net/donate.html
Message delivered to [hidden email]

______________________________________________________________
Elecraft mailing list
Home: http://mailman.qth.net/mailman/listinfo/elecraft
Help: http://mailman.qth.net/mmfaq.htm
Post: mailto:[hidden email]

This list hosted by: http://www.qsl.net
Please help support this email list: http://www.qsl.net/donate.html
Message delivered to [hidden email]

[Phil Wheeler-2]

Clever, Dave. Trouble you prepare for seldom
happens, I've heard :-)

Phil W7OX

On 8/11/15 7:33 PM, Dave Hachadorian wrote:

> I had a similar problem a couple years ago, and
> ordered four
> replacement encoder/switches, which are
> surprisingly inexpensive.
> When I went to actually do the job, it looked
> nasty, and I never
> replaced them.  The problem has never recurred.
>
> Dave Hachadorian, K6LL
> Yuma, AZ

______________________________________________________________
Elecraft mailing list
Home: http://mailman.qth.net/mailman/listinfo/elecraft
Help: http://mailman.qth.net/mmfaq.htm
Post: mailto:[hidden email]

This list hosted by: http://www.qsl.net
Please help support this email list: http://www.qsl.net/donate.html
Message delivered to [hidden email]

[Petr, OK1RP/M0SIS]

Hi,

I had the same problems on my old K3 #778.
The encoder/switches replacement solved this issue.

73 - Petr, OK1RP