Turns out it was a bug in the FLRig backend in hamlib.
Testing the fix now....
de Mike W9MDB
On Wednesday, December 18, 2019, 11:25:24 AM CST, Saku <oh...@sral.fi>
wrote:
Black Michael via wsjt-devel kirjoitti 18.12.2019 klo 13.43:
> Not a collision.....try it yourself....set rig to VFOA USB-D and VFOB
> to USB. Then press Tune on WSJT-X. It will frequently not change
> VFOB to USB-D.
I did 46 times. No problem.
--------------------
[saku@hamtpad tmp]$ cat /etc/fedora-release
Fedora release 30 (Thirty)
--------------------
rigctld started from script:
1730 ? S 0:03 /usr/bin/rigctld -m 373 -r
/dev/icom7300 -t 4532 -s 19200
--------------------
wsjt-x v2.1.2 uses "net hamlib rigctl" localhost:4532
--------------------
[saku@hamtpad tmp]$ rigctld --version
rigctl, Hamlib 3.1
--------------------
VFOB/USB is set with command line endless loop:
[saku@hamtpad ~]$ while [ 1 ]; do echo -en 'V VFOB' | nc localhost
4532; echo -en 'M USB 0' | nc localhost 4532; echo -en 'V VFOA' | nc
localhost 4532; echo "NOW Press Tune!";read a;done
RPRT 0
RPRT 0
RPRT 0
NOW Press Tune!
--------------------
How many times it must be done to catch one?
When wsjt-x has once set VFOB/USB-D it stays there until you use VFOB
for something else (that is the reason for command line loop to get it
returned away from USB-D).
So in normal use I do not see that setting VFOB to another mode than
USB-D happens many times per day (means that you are working something
else than modes of wsjt-x).
Could it be that rigctl v3.1 works and v3.3 don't?
--
Saku
OH1KH
_______________________________________________
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel
_______________________________________________
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel
