Log4OM

The problem I had with VFO B being read in FLDigi (rather than VFO A) cleared up for a while and was reading correctly but has now reverted back to incorrect VFO reading.

Setup:

FT-2000
Omnirig V1.16
FLDigi V 3.23
JTAlert V2.6.25

When looking at the Log4OM Communicator Panel:

RigStatus: connected
Freq: displays VFO B (not VFO A)
All other parameters are correct

When I tune VFO A the Freq: in RigStatus changes to 0 then back to the VFO B frequency
This is what happens in the FLDigig freq. display as well.

When I tune VFO B it tracks fine both in RigStatus and FLDigig.

Interestingly though JT65-HF displays the correct VFO info!

I have tried to reload Omnirig (which seemed to work earlier) but does not now.

Any ideas why the VFO B is displaying both in Communicator and FLDigi? I am stumped.

73,
Ken VA3KA

Please send us a support request having first followed the instructions here:

http://www.log4om.com/log4om-support/

Well mysteriously the problem has cleared itself - again!

Log4OM Communicator is reading and tracking VFO A now ok. FLDigig is reading VFO A ok now as well. I did nothing different here.

I guess the threat of a support request made the program behave!

If the issue reoccurs I will submit a Support Request as directed.

Thanks and 73,
Ken VA3KA

Ken,
For the situation to rectify itself it would indicate to me a problem with either the interface between radio and computer, a com port issue or even perhaps the firmware of the radio.

Have you updated to the latest radio firmware and have you done a factory reset of the radio