[Elecraft] new K3S (10195) and audio level drop when KPA500 in Oper mode

[Jack Brindle]

Jim;

Dick’s advice is sound. When in OPER mode, the KPA will display an asterisk on the left side of the display when PTT is applied. If you are seeing that
indicator, check the PTT connections to see if there is a short to ground. When using the KPA with your K3S, you should only use the AUX I/O cable,
nothing should be plugged into the PTT jack on the KPA500. If this is the case, then check the AUX I/O cable to make sure that no pins are bent. If you
see one bent over, try to straighten it without breaking it (might be difficult) and try the cable again.

There were no firmware changes for the KPA500 for the K3S. The interface and use is identical to that with the K3. The latest shipping firmware is V1.38,
which is what you should be using in your KPA.

- Jack, W6FB
Elecraft Engineering

> On Aug 29, 2015, at 9:06 AM, jim rogers <jdrog at bellsouth.net> wrote:
> 
> Good morning,
> 
> I have a new K3S, serial # 10195.  All was going well until I hooked up my KPA500 to the K3S using the Elecraft supplied aux cable (E850463).
> 
> In standby mode (on the KPA500) the audio level on the K3S is nice and loud, BUT when I press the OPER button on the KPA500 the audio level on the K3S all but disappears!
> 
> If I then press STBY on the KPA500, the audio level on the K3S returns to loud. Only the E850463 cable connects between the two Elecraft components.
> 
> The KPA500 is about 1 year old and has performed flawlessly to date.  Do I have a Firmware issue with the "older" KPA500 and the brand new K3S?
> 
> Thank you for any suggestion on how to resolve this issue.
> 
> Jim N4DU
> 
> 
> 
> 
> ______________________________________________________________
> 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 jackbrindle at me.com