VFO-A VFO-B CAT switching anyone ?

[GU4XEA]

First off this is a great piece of SW, I am blown away by the functionality.

I am also kind of hoping this is an easy (aka dumb) question.

Yaesu FTdx-10, Hamlib, Log4OM 2 Ver 2.35.1.0

If I set the radio dual vfo, one on 40m CW and the other vfo on 10m SSB only some fields change on switching vfo on radio.

1.png shows vfo-a on 40 cw - all good

1.png (109.02 KiB) Viewed 1203 times

switch to vfo-b

2.png - default signal strengths change for ssb but freq mode and band do not - nor does the tx/rx red/green vfo indicators.

2.png (136.01 KiB) Viewed 1203 times

Any QSO's get logged against VFO-A data...

3.png shows the current CAT settings

3.png (216.42 KiB) Viewed 1203 times

Any suggestions ?

PaulC - GU4XEA

[G4POP]

Please try Omnirig 1.2

[GU4XEA]

Hi Terry

Thanks for the quick reply - I started with omnirig 1.2 and that did switch between vfo-a and vfo-b BUT it didn't switch between ssb and cw if they were different, I had to manually go alter the log when I found that out !

Maybe I need to try that again - is it a better bet than the Hamlib ?

Paul C
GU4XEA

[G4POP]

I find Omnirig best especially with Icom and Yaesu radios

Make sure you have the latest Omnirig rig file as the deffinitions are often updated.

The mode issue will deffinately be due to something in the Omnirig .ini file which you can edit so make sure you have the latest and the correct one for the mode your using

[GU4XEA]

OK I have a resolution thanks to Terry - G4POP.

Switched back to omnirig 1.2 which supported the dual VFO's but failed to update the mode when switching to VFO-B.

Downloaded the ini file updates and in the header of the file for FTDx10 we see this :-
;-------------------------------------------------------------------------------
; Change Log
; Modified 20220310 by Brian Backland VE3XNS
; The selected VFO's mode was not being read. This caused Log4OM to log
; the mode from VFO A when VFO B was the active VFO. Now uses the MD0;
; command to correctly read the selected VFO's mode.
;-------------------------------------------------------------------------------

So I swapped in the updated ini file which fixed that.

This was for omnirig V2.1 - I have no idea if I should / could use V2.1 but am currently sticking with V1.2 that ships with the Log4OM install.

Thanks again Terry.

[G4POP]

Do NOT user v2 it's not supported by us or it's own developer

[GU4XEA]

That settles that then Terry !