Log4OM

I have Log4OM integrated with fldigi and my K3 via OmniRig. When I change the mode between CW, SSB, AM and FM on the rig, both Log4OM and fldigi reflect the correct mode. When I change to any data mode on the rig, both Log4OM and fldigi change to SSB. Shouldn't the Log4OM and fldigi modes reflect what is set on the rig? i.e., SSB, CW, RTTY, PSK31, etc. in Log4OM and LSB, USB, CW, RTTY, PSKUSB, etc. in fldigi?

I'm having an issue with RTTY where fldigi won't decode unless I change the fldigi mode to RTTY. But as soon as I touch the rig, change frequency on the rig or transmit for example, the mode is set back to SSB and decode stops.

Is there some configuration I need to change to get the Log4OM and fldigi mode to reflect what is set at the rig?

Thanks, Glenn - KD0Q

It helps us help you if you provide a little more information

What versions of Omnirig, Log4OM and FLdigi are you using?

What operating system is your computer running?

Log4OM is v 1.24.0.0
OmniRig is v1.16.0.246
fldidi is v3.21.83
OS is Windows 10 Pro 64-bit

Thanks, Glenn - KD0Q

Updated fldigi to v3.23.06 and it is the same.

Glenn - KD0Q

Are there any K3c users here that can emulate this issue, I cant test because I dumped all of my Elecraft stuff way back

Glenn, I have a similar thing here, but do not have the issue that FLDigi needs to have RTTY in the box under the freq display. I made a change a few months' ago that seemed to get the 'correct' mode in that box.

I set up both RigCAT and XML-RPC and that seemed to help. Dave confirmed that both can be working at the same time.I have no idea if it will help you. but your issue seemed similar, but more serious, than mine.

Naturally, please let me know if this helped.

73 for 2016 de Guy G4DWV/4X1LT

Hello Guy,

I'd like to know more about your configuration. fldigi won't let me set enable RigCAT and XML-RPC at the same time.

If I disable rig control in Log4OM, and enable RigCAT or HamLib in fldigi, the fldigi mode gets set to something that works. But fldigi and Log4OM can't share the COM port so that means giving up rig control in Log4OM. Are you running some kind of port sharing software?

73, Glenn - KD0Q

Glenn,

It has been a while since I have been on the air due to health issues, so I am working from memory at the moment. Not only that, but I am not an expert by any means.

I am not using Hamlib. I use Omnirig as advised by Log4OM. The latter does allow COM ports to be shared, but there is no need to. DDUtil

In fact I found my life being made much easier by creating COM ports as needed. I recommend that you join the Yahoo group for FLDigi at https://groups.yahoo.com/neo/groups/win-fldigi/info.

Good luck,

Guy

Hope you are working through your health issues OK Guy.

I thought DDUtil was for Flex radios but I could be wrong. Anyway, I installed a trial version of Win4K3 which implements a GUI for the K3/P3/KPA-500/KAT-500 and provides port sharing for the K3. I could then create two virtual com ports and successfully configure fldigi to use hamlib or RigCAT on one port and Log4OM to use OmniRig on the other, and all appears to work properly. Meaning I can control the K3 from both fldigi and Log4OM and both reflect what the K3 is doing appropriately. I'll know better after I've used it for awhile.

Thanks.
73, Glenn - KD0Q

Glenn, you are right about DDUtil. Mni tnx for your kind wishes.

Guy