Log4OM

For the record, right from the top - I love LOG4OM, and appreciate the community that has made it all happen. Thank you all!

I'd appreciate a contact with a KX3 user who is successfully using Hamlib on LOG4OM V2.16 in a Windows 8 environment.

My system was working before the Update, but now my settings (as follows) do not work for me. Sometimes the CAT indicator shows for a second or two, upon "Connect" but turns off a moment later. Sometimes the main window shows 155000 (VHF) frequency - which I do not use.

Settings are:
Elecraft KX3 Stable
Hide Hamlib in Taskbar
Serial Connected to Radio
Port COM3 (works fine in Fldigi)
Baud, 38,400
Data Carrier Detect "None"
No PTT
Polling 50ms

I am using a Signalink Sound Card, the signalink USB cord, and the KX3 Control Cable through a second USB port.

I have done a reboot and started LOG4OM in isolation - without Fldigi or Winlink - so I dont believe there is any contention for COM3. Both Fldigi and Winlink work 2-way interactively with the KX3.

I do know that Hamlib has worked in the past for the KX3, and doesn't now. I'm not deeply technical, but I can change Options / Switches and settings from menus. Unless Ive ham-fistedly changed something in the settings - I dont understand what's happened.

Thanks for the help,

Kevin, VE7KHI

Kevin,

There are bugs with Hamlib and V 2.16.0.0 ... Switch over to Omnirig for the time being. It is more stable. I use a K3 and with it being an Elecraft is the closest I can come to your setup.

Here are links to other posts about the Hamlib issue you have noted.

https://forum.log4om.com/viewtopic.php? ... 030#p37030

https://forum.log4om.com/viewtopic.php?f=32&t=6909

Lele is currently on holiday and this will be resolved when he gets back.

Thank you Nolan. I'm really impressed with the supportive network if users - and dedication to continuous improvement.

Kevin ve7khi