Omnirig's Modify button does not work

[PY2AD]

I tried use Omnirig V1 and V2, but the Qlog dont save in button MODIFY, then i cant save the config

[kyleboyle]

I agree with your assessment, I noticed this on the weekend. I don't believe the fields are being correctly error checked or there is left over state from other cat types as the input fields are updated. I think I could get it to work if I first selected my hamlib network rig connection then switched to the omnirig rig. It's possible the com port selection field is messing it up as that field shouldn't be displayed for omnirig.

[PY2AD]

In my case, I already use the internal Qlog hamlib, but every time I change bands via Qlog, the FT-950 briefly jumps to VFO-B and then changes bands in VFO-A. I know this is a problem with hamlib, as it only happens there.

But, I tested omnirig again, and this happens, it doesn't modify or save.

[kyleboyle]

Yes I agree that omni rig type cat doesn't save reliably. Here is a demo showing the save failing and then the save working. I think it has to do with the presence of the com port selection field. I would say that currently omni rig configuration is effectively broken.

Screen.Recording.2025-12-16.004041.mp4

[PY2AD]

I did a test here, save it first as TCI, then you can configure OmniRig. Qlog is keeping the screen as it was before the configuration. Since Hamlib uses a COM port, the screen remains, which doesn't happen with TCI.

[PY2AD]

I did a test here, save it first as TCI, then you can configure OmniRig. Qlog is keeping the screen as it was before the configuration. Since Hamlib uses a COM port, the screen remains, which doesn't happen with TCI.

This, just works with Omnirig v2, with v1 not.

[foldynl]

@kyleboyle Thanks for the analysis. Yes, it looks like an issue in Setting dialog. I opened an issue report for it.

[PY2AD]

Works now on 0.47.1, and thanks to correct TX light on omnirig and flrig. Befora, works only in hamlib