Closing Log4OM Changes something in the K3S

[w8msp]

Didn't notice this until the latest release of Log4OM. When exiting Log4OM and my K3S is turned on and tuned to a station, the signal appears to drop out and audio filters maybe changed?

If I turn off the K3S and back on everything is back to normal. If I just turn the knob for filter width everything comes back to normal. I tuned the radio to WWV and it does the same thing. Very repeatable. Never noticed it in any other version but it could have been there.

I don't see anything on the K3S display changing when exiting Log4OM just the audio changes drastically.

Thanks

Les
W8MSP

[G4POP]

Anyone else with a K3S have the same issue?

[KI5IO]

My K3 is responding the same way as Les has described.

My K3 is "almost" a K3S as I got it just two weeks before Elecraft announced the new model and it has almost all the upgrades to bring it very close to a K3S.

[KI5IO]

FWIW - I was doing some changes with my cluster connection and happened to shut off Log4OM to get a cluster file updated/refreshed.

I had disconnected from the cluster and then shut down Log4OM and noted that the audio on my K3 did NOT drop/disappear.

I restarted Log4OM and my cluster was re-connected and I shut down Log4OM and the audio DID drop/disappear.

I've been able to consistently repeat the 'loss' or 'no loss' of audio by having the cluster active or not when turning off Log4OM.

Maybe that will help narrow down the hunt for the hiccup ??

[G4POP]

What interfaces between the computer and the radio are you two guys using?

And what version of Windows

[KI5IO]

Terry,

I'm using Omni-Rig (Version 1.16) via USB. Labeled as port 3, 38400 baud, 100ms polling

I have Windows 10 with their latest update recently released.

[w8msp]

What interfaces between the computer and the radio are you two guys using?

And what version of Windows

I am using a USB from the K3S to the PC and Log4OM communicator is running. Windows 10 Anniversary Edition. When I get home tonight I can get more details.

Thanks

Les

[KI5IO]

Well ... so much for that "possible" linking to having the Cluster connected or not-connected.

I just did some more testing on both 20m and 40m and it did not make any difference as I had noted in an earlier post.

Everytime I close Log4OM it turns down the audio on the K3 (or turns it down where it can barely be heard). Adjusting the shift or width controls brings the audio back to life. No other changes appear to be happening.

[w8msp]

What interfaces between the computer and the radio are you two guys using?

And what version of Windows

I am using the Log4OM CAT with this parameter
--model=229 --rig-file=COM5 --serial-speed=38400 --port=4532 --set-conf=stop_bits=2,dtr_state=ON,rts_state=ON --ptt-file=COM5 --ptt-type=RIG -v

The K3S USB cable to the PC which is running
Windows 10 Home Version 1607 OS Build 14393.85
Intel i-3 3240 CPU @ 3.4 GHz with 8 Gig Ram

[G4POP]

What interfaces between the computer and the radio are you two guys using?

And what version of Windows

I am using the Log4OM CAT with this parameter
--model=229 --rig-file=COM5 --serial-speed=38400 --port=4532 --set-conf=stop_bits=2,dtr_state=ON,rts_state=ON --ptt-file=COM5 --ptt-type=RIG -v

The K3S USB cable to the PC which is running
Windows 10 Home Version 1607 OS Build 14393.85
Intel i-3 3240 CPU @ 3.4 GHz with 8 Gig Ram

Please change to Omnirig in Log4OM not the Hamlib that you are currently using