Bill Somerville kirjoitti 7.6.2021 klo 20.36:
Hi Saku,
the WSJT-X v2.5.0 RC1 RPM package for Fedora targets Fedora 34, which
is why you are seeing dependency conflicts while attempting to install
on Fedora 33.
Try starting rigctld with a --vfo argument.
73
Bill
G4WJS.
Hi Bill!
Thanks for reply!
WSJT Home page says:
* Version 2.5.0-rc1
o Debian, Ubuntu 20.04 LTS, ... (64-bit):
wsjtx_2.5.0-rc1_amd64.deb
<https://physics.princeton.edu/pulsar/k1jt/wsjtx_2.5.0-rc1_amd64.deb>
o Fedora 33, RedHat, ... (64-bit): wsjtx-2.5.0-rc1.x86_64.rpm
<https://physics.princeton.edu/pulsar/k1jt/wsjtx-2.5.0-rc1.x86_64.rpm>
Maybe typo from copying previous texts (from 2.4.0) to 2.5.0rc1?
----------
Using "--vfo" parameter with rigctld started from boot time script makes
wsjtx 2.5.0rc1 to work. Assume also 2.4.0 (self compiled) to work.
But as side effect wsjtx 2.3.1, cqrlog, fldigi and qsstv stop working
then. Rigctld returns something weird that they can not handle.
For wsjtx 2.3.1 it "turns red" and says "OOB" and reports rigcontrol error
For cqrlog it shows rig frequency ok, but TRXControl can not change
bands and modes.
For fldigi it shows initial frequency but stuck up for long times and
does not change mode or frequency
For Qsstv it reports at start:
When change frequency:
And frequency does not change, although it shows current frequency ok,
like cqrlog.
All these programs are configured to use rig "Net Hamlib rigctld" (model
#2) and connect via loclhost:4532 to previously started (from boot up
script) rigctld that communicates then with IC7300 via /dev/ttyUSB0
This parameter "--vfo" can not be used. It seems there is something that
makes rigctld reply with way that is not backward compatible.
No good !
--
Saku
OH1KH
_______________________________________________
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel
