When wfview connects to the radio, it changes the radio instead of wfview changing to the radio. Is this normal or do I need to change a setting?
Thanks. 73
Dan, KC9MJA
When wfview connects to the radio, it changes the radio instead of wfview changing to the radio. Is this normal or do I need to change a setting?
Thanks. 73
Dan, KC9MJA
Dan,
I have no idea what you’re really asking.
Can you elaborate?
—E
de W6EL
Thanks for the wonderful work on v2 first.
My station.
Radio - IC-705
Platform - Windows 10 22H2
Current App version - v2.03
I too experience similar to this action on starting the app.
When powering up my radio, it startup in memory mode and scanning selected memories. (remembered as when is shutdown.).
Running the wfview app When app starts and finds radio, it changes the radio into vfo mode.
v1.63 never caused this change of mode.
I can return back to memory mode by the touch screen or by opening memory manager and clicking on select memory mode button.
This quirk of wfview has been checked in v2.00, v2.01 and v2.03
Cheers
Peter VK4PI / VK4QRP
Thank you for better explaining the problem. This is exactly what is happening.
Hi Peter,
We’ve seen that too, and we will address it in the next version.
Thanks,
–E
de W6EL
This is a significantly more complex issue than it appears to be. wfview needs to know what the current mode is when it connects, unfortunately Icom only provides a command to select the VFO/memory mode, and nothing to query what the current mode is.
This becomes an issue as certain commands will generate an FA (failed) error response from the radio when in memory mode (specifically commands to query the selected/unselected VFO frequency/mode.) The simplest way to resolve this is to force the radio into VFO mode at startup.
If we find a way to determine the current mode without forcing VFO mode, we will implement it, but otherwise wfview will need to select VFO mode at startup.
Icom’s RS-BA1 software and SDR-Control all do the same thing; when you connect, the radios all go to VFO mode. You get used to it.
Thanks Phil.
Does v2.x communicate to the radio differently than v1.6x. I can swap between the 2 versions and only happens with 2.x.
Could it related to the memory manager of 2.x, where 1.6x this was never implemented.
When a get time, I will try to create some debug comms logs of the two versions.
Peter - VK4PI / VK4QRP
Yes wfview 1.x had no knowledge of multiple VFOs or Memory mode, so it didn’t care what mode you were in.
I have added an option in settings called “Force VFO Mode” this will be enabled by default, but if disabled, wfview will not send the commands to force the radio to switch to VFO mode on connect.
This option may cause issues until wfview knows which mode you are in.
It will be available in the next release of wfview.
Phil