Can you compile hamlib?
I'm going to be making a patch to fix this...
Mike
On Wednesday, June 9, 2021, 05:25:39 AM CDT, Saku <oh...@sral.fi> wrote:
Hi MIke!
libhamlib.so.4 => /lib64/libhamlib.so.4 (0x00007f5546c73000)
lrwxrwxrwx. 1 root root 18 16. 4. 16:44 /lib64/libhamlib.so.4 ->
libhamlib.so.4.0.2
Except cqrlog that does not use shared library.
It just telnet (legacy) short commands to localhost:4532 and expects return
messages to be legacy format.
So it should work with any version that understands and replies in short form
as it "has always been"
--
Saku
OH1KH Black Michael via wsjt-devel kirjoitti 8.6.2021 klo 15.53:
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
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:
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
- Debian, Ubuntu 20.04 LTS, ... (64-bit): wsjtx_2.5.0-rc1_amd64.deb
- Fedora 33, RedHat, ... (64-bit): 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
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
_______________________________________________
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
_______________________________________________
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel
