You may have fallen afoul of what seems to be a "race condition" in the K3's firmware. When software (CAT) PTT and hardware PTT (from any of the hardware inputs, be it the AUX jack, the PTT IN jack or RTS or DTR on the RS232 port) are both configured from the same software, and both methods trigger at the same time, sometimes the K3 fails to switch back to receive. It doesn't necessarily happen every time; there may be minor timing differences in the software that affect whether it happens or not on any particular cycle. This problem has been around for years, probably since day 1. I have seen this from the beginning with my 2008-vintage K3, and I am told that there are other transceiver models besides the K3 that have similar problems.

The solution is never to have two methods of PTT configured in parallel. This is a case where "belt and suspenders" is less reliable than either the belt or the suspenders alone. If you have Fldigi configured to use CAT for PTT, then do not connect or configure any of the K3's PTT inputs. If you want to use hardware PTT, e.g. from the SignaLink, then disable PTT via CAT in your software.

Incidentally, the hung up state is not an "indeterminate" state as you suggested in your first post. The K3 is in transmit; the reason nothing is being transmitted is simply that the software is not sending any audio to the radio, exactly as if you were in SSB with the rig in transmit but no sound coming from the microphone.

73,
Rich VE3KI


WA6PZK wrote:

The good news is I'm beginning to see the possible cause of the problem, and
it appears to be in the CAT rig control.  When I finally get CAT disable,
requiring a restart of FLDIGI, the problem seems to have mitigated.

______________________________________________________________
Elecraft mailing list
Home: http://mailman.qth.net/mailman/listinfo/elecraft
Help: http://mailman.qth.net/mmfaq.htm
Post: mailto:Elecraft@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 arch...@mail-archive.com

Reply via email to