I'm trying to summarize some "minor issues" which are not blocking problems at all, but they are a bit annoying, especially because I haven't been able to sort out them so far and I'm still facing it on my current setup which includes:
a) WSJT-X 2.5.0 GA
b) Linux Tumbleweed updated daily
c) CQRLOG latest GIT which starts the WSJT-X application
d) YAESU FT-100
e) CAT USB cable + Audio USB cable plugged to the rear panel radio pigtail and data connector.
MINOR ISSUE 1:
With the majority of the older WSJT-X versions, I used to set the hamlib NET rigctl into the WSJT-X and this has worked flawlessly for a lot of time and at least until something has been changed into Hamlib, WSJT-X or both. From that moment on, if I set in this way the WSJT-X, by selecting NET rigctl, then no audio signal is produced and my radio just switch the PTT, without modulating the SSB carrier.
In order I can operate I need to switch from NET rigctl to YAESU FT-100 in the settings>option>radio>rig.
MINOR ISSUE 2:
This is a lower severity issue but it happens that I need to press my YAESU FT-100 A=B vfo button every time I switch to other band with WSJT-X otherwise radio receive on the right selected frequency but keeps transmitting on the previous one.
Additional details:
Into WSJT-X I select mode: USB, Split: RIG.
Into CQRLOG settings I'm using the following parameters to manage WSJT-X:
Path to rigctld: /usr/local/bin/rigctld (note: this is coming from my Hamlib compiled from latest GIT repository).
RIG model: 2 Hamlib NET rigctl
Extra command line arguments: -m 1021 --vfo
That's all.
If someone, using an environment similar to mine, is able to use NET rigctl and or able to switch the radio bands by WSJT-X, without pressing the A=B VFO, please reply to this message.
Many thanks!
---
73 de Marco, PY1ZRJ (former IK5BCU)
![]()
73 de Marco, PY1ZRJ (former IK5BCU)
_______________________________________________ wsjt-devel mailing list wsjt-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wsjt-devel
