On 14/10/2021 20:50, Black Michael wrote:
That should be fixed in the master branch now.
Can you please try that?
Hi Mike,
Thanks for your quick reply.
I rebuilt hamlib package from git master (da34930) and rebuilt a new
wsjtx-2.5 package against it. (Not sure if that was strictly necessary?)
Not much difference sadly.
All seems OK in Fake-it (had a quick FT8 QSO to test) but as soon as RIG
is selected I start to see communication failures:
Hamlib error: Communication timed out
read_string called, rxmax=1024
read_string(): Timed out 1.501 seconds after 0 chars
rig.c(1030):rig_open return(-5) while opening connection to rig
After retry and band change:
Hamlib error: Communication timed out
read_string called, rxmax=1024
read_string(): Timed out 1.501 seconds after 0 chars
rig.c(1030):rig_open return(-5) while opening connection to rig
The rig does switch to split mode, but any attempt to TX ends with:
Hamlib error: Communication timed out
read_string called, rxmax=1024
read_string(): Timed out 1.501 seconds after 0 chars
rig.c(4661):rig_set_split_vfo return(-5) while setting/unsetting split mode
Test cat button goes green and PTT test works fine, unless the rig is in
split and I then select fake-it when I see:
"Emulated split mode requires rig to be in simplex mode" which is
reasonable although I would expect it to try to set that.
If I stop rigctld and switch to direct mode then it's chaos (which is
why I started to test with rigctld) earlier versions all worked fine
direct. Troubles started with 4.3.
There are no errors at all sent to the screen, but band changes take
about 10 seconds-ish and do eventually happen, however no audio is
output on TX and the PTT fails too. The does work.
I'm guessing that hamlib logs would be more than useful but I have yet
find any, or where to enable.
So, any ideas?
Cheers,
Barry
G4MKT
_______________________________________________
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel
