-
Notifications
You must be signed in to change notification settings - Fork 200
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
IC-7100 VFOB split not changing VFOB #764
Comments
I did just notice a difference in how it acts compared to 2.3.0. When it first starts transmitting, it quickly flips back and forth between VFOA and VFOB before finally landing on VFOB and transmitting. Before, on 2.3.0, it would only switch from VFOA to VFOB once, transmit, then switch back to VFOA. |
Bill Somerville g4wjs@classdesign.com Sun, Aug 29 at 2:16 PM Hi all, master at commit a0672e4 has regressed, it no longer reliably sets the split Tx VFO frequency as requested by a set_split_freq_mode(). Note that in the first (failing) example below the SUB VFO is never selected even though the MAIN VFO is selected no less than six times while attempting to execute this command! The end result is that the requested SPLIT Tx VFO frequency is set on the MAIN Rx VFO. Note also the second trace output below where in the same session set_split_freq_mode() does manage to set the right frequency in the right VFO, rather inconistent behaviour! warning: [18:52:44.717724][RIGCTRL][trace] C:\Users\bill\src\k1jt\wsjtx\Transceiver\HamlibTransceiver.cpp(989) do_tx_frequency: rig_set_split_freq_mode freq=14074500 mode = USB Hamlib-developer mailing list |
Log shows that split had not been requested before calling set_split_freq_mode |
…ased on current vfo selection #764
…ased on current vfo selection Hamlib#764
I can confirm that this seems to be a regression in 2.4.0. I've run my IC-7100 in split/rig mode for about a year now on v2.3.0 and it switches the VFOb settings correctly on transmit. Once I upgraded to 2.4.0, VFOb is stuck on 40 meters when I'm working 20 meters. I downgraded back to 2.3.0 and the issue resolved itself.
Settings->Radio->Mode is set to Data/Pkt.
73, TJ N7TJH
The text was updated successfully, but these errors were encountered: