Il 08/06/21 09:53, Black Michael ha scritto:
All those programs will use the system libhamlib.so shared library.
If you do
ldd /usr/bin/fldigi | grep ham
ldd /usr/bin/qsstv | grep ham
ldd [path_to_cqrlog] | grep ham
And see what library it's pointing to.
Then, if you install the latest hamlib to replace libhamlib.so they
should all work with the --vfo argument.
Mike W9MDB
Hi Mike,
As you well know since you have supported me many time in order to
resolve issues with my environment, I have a specific procedure to start
WSJT-X which is managed by the CQRLOG logging program.
I can confirm to you that the "--vfo" parameter is working ok for me but
this has not resolved the issue of the WSJT-X Settings-->Radio which I
have to set on my radio model (YAESU FT-100).
Some releases (WSJT-X/HAMLIB) ago, I could use the "hamlib-netctl"
parameter without any problem nowadays not.
This is the issue I was referring to in my answer to Saku.
It is not a critical problem because I don't use simultaneously
different apps as FLDIGI, QSTTV and WSJT-X, so I can keep using my
current settings, but the fact is that it is an issue appeared recently
at least for my specific environment.
That is!
Regards,
PY1ZRJ
On Tuesday, June 8, 2021, 07:05:01 AM CDT, Marco Calistri
<py1...@outlook.com> wrote:
Il 08/06/21 03:23, Saku ha scritto:
----------
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
Hi Saku!
I'm "happy" you're facing this kind of error for two reasons:
1) You are a development contributor of CQRLOG which I also use as
logging program to start WSJT-X. Then maybe you could discover a solution.
2) I faced similarly same issues with my YAESU FT-100 if I want to use
the hamlib netctl option.
In that case I notice the same weird VFO A/B switching occurring on
different bands and sometime (depending on settings parameters) also
the "OOB" error.
In order be able to use WSJT-X, I need to set the radio setting to my
radio model: FT-100, I can't use anymore (since some of the most
recent releases of WSJT-X and hamlib) the hamlib rigctl option in WSJT-X.
---
*73 de Marco, PY1ZRJ (former IK5BCU)*
**
_______________________________________________
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel
