Closing Log4OM Changes something in the K3S

[KI5IO]

"Hopefully" ... this will be the last update for this hiccup.

Elecraft posted and sent me yet another BETA release for firmware for the K3 and K3S rigs. It is v5.54.

I've been running the new/beta firmware now for 2+ days and some long hours with lots of off/on cycling of Log4OM to see if the "audio drop" would manifest itself when closing Log4OM. IE: Audio on K3 or K3S drops to nil when Log4OM shuts down. For K3 users you have to have installed the new KIO3B Interface Option.

I had gone back to firmware version 5.33 and 5.38 and all would be OK. Problem seemed to come about with firmware version 5.50.

For Elecraft K3 users you will likely not experience the audio drop unless you have also upgraded with the KIO3B Interface Option. A kit of 3 boards that adds an audio board to the K3 and provides USB access and a bit more.

The KIO3B option is standard on the K3S rigs. Those rigs were also impacted with the problem as was noted by Les Butler (W8MSP) who was the OP of this thread.

Les installed the updated beta firmware and sent me a message this AM indicating that it appeared his K3S and Log4OM were now indicating "joy".

I hope this is the last comment I get to make on this one for sure ...

[HB9BRJ]

With Log4OM and my K3 I never observed the "audio drop" issue described in this thread.

But when trying the new WSJT-X version 1.7.0 (stand-alone, Log4OM not running), my K3 went totally quiet when closing WSJT-X. After touching the WIDTH control, audio came back.

Since WSJT-X is widely used, there is a chance that the "audio drop" problem will get enough attention to be understood and solved.

Markus HB9BRJ

[KI5IO]

Markus' experience with the Elecraft K3 or K3S "audio drop" is significant as both Log4OM and WSJT-X uses OmniRig to do the actual communications from the respective applications to the Elecraft product.

I've provided many data capture files to Alex with OmniRig, but have not had any replies as of the writing of this comment on Markus' post.

There is something amiss with the communications data via OmniRig to the Elecraft K3 or K3S, but the specific ID of the problem has not yet been found/made.

I don't believe it is any problem with Log4OM from what I've learned in my many months of trouble-shooting.

[IW3HMH]

There is an option to set in Omnirig to enable "trace mode", if i remember well...
could be useful to check what are the latest commands sent to K3 when Omnirig closes...

Check here:
http://www.dxatlas.com/omnirig/BetaTest.txt

there is a parameter to be set in the omnirig.ini config file:
[Debug]
Log=1