VFO mode

[mdblack98]

GPredict should add an option for the VFO mode for rigctld. It avoids all the VFO swapping that can occur. All you do is add the VFO to the remote commands.

So instead of V VFOA F 14070000 V VFOB F 14071000 You do F VFOA 14070000 F VFOB 14071000

de Mike W9MDB

[mdblack98]

And I'll add that you can check if vfo mode is enabled \chk_vfo CHKVFO 1

If chk_vfo returns an error then it's an old rigctld that doesn't support chk_vfo but may still be in VFO mode.

de Mike W9MDB

[csete]

Hi @mdblack98

Thanks for the request. Can you provide some more info about which radio this is relevant for? My concern is that every time we fix or improve something like this for one radio, it breaks the functionality for another radio, and we have been going back and forth for years :(

[mdblack98]

Here's what I got on another email list from [email protected] -- he's seeing VFO swapping which probably happens on a lot of rigs.The vfo mode of rigctld avoids the swapping for any rigs that have director VFO addressing which is pretty much all new rigs now and most of the old ones.

In this mode, both up/downlink are being corrected but the VFOs are Always swaping from main to sub and the SPLIT function turn on.

 

In this mode, both up/downlink are being corrected but the VFOs are Always swaping from main to sub and the SPLIT function turn on.  

In this mode, both up/downlink are being corrected but the VFOs are Always swaping from main to sub and the SPLIT function turn on.  

In this mode, both up/downlink are being corrected but the VFOs are Always swaping from main to sub and the SPLIT function turn on.

 

On Saturday, October 26, 2019, 05:02:23 PM CDT, Alexandru Csete <[email protected]> wrote:  

Hi @mdblack98

Thanks for the request. Can you provide some more info about which radio this is relevant for? My concern is that every time we fix or improve something like this for one radio, it breaks the functionality for another radio, and we have been going back and forth for years :(

— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub, or unsubscribe.

[Aleziss]

@mdblack98 and everyone one else ! I see that you posted the error I did report to you (I am va2cst) so thank you for taking care of this here.

You can see the actual bug happening in video along with some debug capture text from hamlib.

See my bug report https://github.com/csete/gpredict/issues/181 and tell me if I can provide more information on what is happeneing.

Thank you all !