Log4OM

I am trying to get Hamlib to work with the FT-991a and Log4om2. I successfully have Omnirig working for a long time but wanted to switch so that On Air status can be read by a remote Hamclock instance. I do have Hamlib set for Dual VFO as I use split for digital modes. If I switch to Hamlib and the 991a is in QMB mode with split off Log4om2 shows the correct frequency in vfo A but also shows vfo B in TX even though split is OFF. If I manually turn split on/off it does not change correctly in Log4om2. Also Log4om2 does not show on air or split indicators they are always off no matter what. I know on air is working with hamlib as Hamclock does display On the Air when transmitting. If I use digital modes with WSJT-X to switch bands then Log4om2 does show the correct frequency in both vfo's and if I manually turn off split the TX moves to VFO A as expected although no split indicator in Log4om2. If I use RCl to change to QMB mode then I have the split issue even though it is not on. If I manually query the radio state using rigctl I get the correct on/off return as expected. I have tried updating hamlib in log4om2 directory and still have the weird dual vfo issues. Any one get this to work I have tried multiple hamlib settings although I think it looks more like Log4om2 not querying properly.

John
W8LYO

I was able to run rigctld manually with trace enabled. Wow a lot of information quickly but I was able to capture it and see that Hamlib is indeed working properly. When I started the rig was in QMB mem mode with only VFO A active

2025-04-25T12:51:26.151400-0500: rig_init: rig has VFO_A
2025-04-25T12:51:26.151400-0500: rig_init: rig has VFO_B
2025-04-25T12:51:26.152519-0500: rig_init: rig has VFO_MEM
vfo_fixup:(from rig_get_freq:2457) vfo=VFOB, vfo_curr=VFOA, split=0


turned on split


vfo_fixup:(from rig_get_mode:2993) vfo=VFOB, vfo_curr=VFOA, split=1

Log4om2 did not recognize the change correctly.