Using FLRig
FLDigi > FLRig
Log4OMV2 hamlib FLRig interface
On connect with hamlib Log4OM is sending the VFOB frequency to FLDigi.
FLDigi only knows one VFO -- VFOA
So FLDIgi is change...it notifies FLRig...Log4OM reads VFOA from FLRig and ends up with VFOB frequency in VFOA too.
2021-03-31 17:03:07.9852 INFO: [HamlibForm] : Starting hamlib as standalone: C:\Users\cfogr\AppData\Roaming\Log4OM2\hamlib\rigctld.exe --model=4 --rig-file=127.0.0.1:12345 -vvv --vfo
2021-03-31 17:03:11.3551 INFO: [#=zII2Ry9hDtKOV4AVh1w==] : [HAMLIB] Starting Hamlib service
2021-03-31 17:03:11.3561 INFO: [#=zII2Ry9hDtKOV4AVh1w==] : [HAMLIB] Using existing connection: True
2021-03-31 17:03:11.3571 INFO: [ProgramStorage] : [CAT STATUS CHANGED] Running: True
2021-03-31 17:03:12.2517 INFO: [FLDigiManagement] : Setting FLDIGI frequency to 7075500
2021-03-31 17:03:12.8799 INFO: [FLDigiManagement] : Setting FLDIGI frequency to 7075500
2021-03-31 17:03:15.3193 INFO: [HamlibEngine] : [HAMLIB] Stop polling. Timeout False
2021-03-31 17:03:15.3203 INFO: [ProgramStorage] : [CAT STATUS CHANGED] Running: False
2021-03-31 17:03:15.3233 INFO: [HamlibEngine] : [HAMLIB] Stop polling. Timeout False
V 2.12.0.0 VFOB frequency sent to FLDigi
Re: V 2.12.0.0 VFOB frequency sent to FLDigi
Secondly -- We need an option not send this frequency info to FLDigi at all -- when FLDigi is using FLRig and Log4OM is using FLRig via hamlib we don't need FLDigi frequency setting at all....all spot clicking and such will go through FLRig.
Mike
Mike