Hi -
First of all, thanks a lot for great software, it’s practically indispensable for me.
I finally upgraded to 2.03 and have been having a few possibly related issues with different clients. I am not sure if this is a bug/bugs or just some version incompatibilities, that’s why I am not filing it as a bug, but trying to provide as detailed info as possible.
First of all:
- Wfview built from sources at master, last commit 1/14/2025.
- Running Ubuntu 24.04 Arm, on QEMU under MacOS
- Radio IC-705, connected through WiFi
What’s been happening:
-
I had a fully working setup with wfview 1.64 including WSJT-X and fldigi, exactly as described in the manual, through hamlib/rigctld.
-
With 2.03, WSJT-X 2.6.1 had trouble returning to the RX frequency after TX. I am normally using ‘Fake’ to control split in wsjt-x. What was happening - during TX, the radio would shift to the TX frequency but after completing transmission it wouldn’t return back to RX frequency, say 14.074, and was stuck at the same TX freq. If I interrupted TX by hitting ‘Halt TX’, it would often return to RX freq normally, but not after full TX cycle. I was trying to see what was happening in the wfview log, but couldn’t spot any obvious difference between commands sent to rigctld in cases where it would and wouldn’t return to RX freq. Upgrading to WSJT-X pre-release candidate 2.7.0rc8 solved the problem, and if it were the only problem I would have left it at that. However:
-
Tried fldigi today. Doesn’t connect to rigctld, configuration the same as worked with old wfview - Hamlib NET rigctld (Stable.) This is what I see in the wfview log:
Flrig does connect through the virtual serial port, and fldigi connects through flrig.
- Here’s the last thing I have observed, which is just a nuisance, but may be indicative of the root cause of at least some of the issues. Hamclock can’t get the PTT status from rigctld anymore, says ‘HAMLIB no connection’ at the startup and then keeps saying ‘HAMLIB PTT query failed.’ This is what I see in the wfview log at the hamclock startup:
and it just keeps repeating.
With the old version of wfview, hamclock was also wonky getting PTT status especially after wfview disconnected from/reconnected to the radio, but then i was just unchecking/checking rigctld checkbox in the wfview settings and hamclock would be happy again.
I am not sure if this is something due to the changes in wfview rigctld, or something with hamlib, or maybe those things are just unrelated.
I will try to keep 2.03 as long as I manage to have WSJT-X and fldigi working, and would be happy to assist with any troubleshooting in case you guys decide it’s worth looking at.
Thanks again,
73 de AA4YS Yuri