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.
FLRig is the rig conrtoller, FLDigi talks to FLRig, WSJT-X talks to FLRig,
Log4OM talks to rigctld talking to FLRig, local utility talks to FLRig, another
local utility talks to rigctld
All works hunky-dory except for this one bug-a-boo. Gotta' get some debug
today.
On Wednesday, December 18, 2019, 03:36:23 AM CST, Saku <oh...@sral.fi>
wrote:
Black Michael via wsjt-devel kirjoitti 18.12.2019 klo 0.47:
Band change seems to work all the time but externally changing frequencies
(from Log4OM) seems to cause this situation sometimes.
de Mike W9MDB
Hi!
Looks like a collision when 2 programs tries to access same rig port.
Start a rigctld instance from start script or cron with ic7300 parameters.
Then use "hamlib net rigctl" at localhost:4532 with wsjtx and for all the other
programs needing rig. ( Also called rig model 2 {rigctld -m2}).
That way all programs poll the rigctld instance started at beginning and only
that alone polls the rig.
No collisions and you can run all your programs one by one, or all at same
time. Everything works.
And when you change your rig model you just change settings of rigctld started
by script. No need to touch any program's setups.
I never have found any problems with my ic7300 (fingers crossed) with wsjtx,
cqrlog, qsstv, fldigi, grig. Only in low bands, 7mhz and below, seldom rig
connect disappears, but that is known RFI issue even when having ferrites at
both ends of USB cable and groundings as good as they can be in this qth.
--
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
