Log4OM

Hello All,

I'm using wfview for rig control and connect log4om via Hamlib.

Sometimes it works perfectly.

Other times, CAT starts but it doesn't connect to the radio. It says it is connected, showing 145000.00 for freq (where wfview and the radio are on something else). If I stop CAT, open "show cat interface", I see that under TCP connection "connect to active hamlib instance" is unchecked (unlike when I configured and saved it originally). I check it, start CAT, and all is happy.

Sometimes that sticks, sometimes restarting Log4om it does it again. I haven't found a consistent sequence that causes it to break when it is working (starting stopping WFview, rebooting, starting/stopping log4om, etc...). It can be working, I can shut down log4om, start it back up, and it is broken again. Yet, sometimes I do that and all is good.

Looking at the log, when it is "broken" I see this:
[dje_zVZ4H6BD56RMXH98SDQEKE_ejd] : [HAMLIB] Using existing connection: False

When it is working I see:
[dje_zVZ4H6BD56RMXH98SDQEKE_ejd] : [HAMLIB] Using existing connection: True

So I imagine the "problem" is somehow related however that is determined. I didn't see anything else "obvious"...

I'm using the latest stable version.

Any ideas what to try?

I guess your using a com port via USB, did you realise that you cant share com ports?

Run Log4OM without wfview and I expect you will find it works fine, if it does then you need to use a virtual com port pair for your nconnections.

I doubt that wfview can connect via Omnirig otherwise that would work, of course it also helps if you state what radio your using!