¿ªÔÆÌåÓý

WSJT-x 2.6.1 and uBitx on Raspberry Pi #ubitx


 

I'm running WSJT-X on a Raspberry Pi 4, 4Gb, running 32 bit "Raspbian GNU/Linux 11 (bullseye)" that is fully patched and up to date.
Radio is a uBitx v6.1 with a Signalink interface, using the Yaesu FT-817 settings in WSJT-X.

WSJT-X version 2.5.4 works fine, no errors.

Version 2.6.1 (installed with "dpkg -i wsjtx_2.6.1_armhf.deb") gives a hamlib Protocol error.

I've upgraded hamlib to version 4.5.4 as indicated by the WSJT-X release notes.

Downgrading back to 2.5.4 ("dpkg -i wsjtx_2.5.4_armhf.deb") and everything works fine again, even with hamlib 4.5.4 still installed.

Has anyone gotten WSJT-X 2.6.1 to work with the uBitx from a Raspberry Pi?

Thank you,

-Dj

Error:

Hamlib error:?? 2:rig_get_mode: elapsed=610ms
? 2:rig.c(2542):rig_get_mode returning(0)
?1:rig.c(1375):rig_open returning(0)
?1:rig.c(2884):rig_get_vfo entered
rig_get_vfo: cache check age=15460ms
rig_get_vfo: cache miss age=15460ms
/home/wc4h/Downloads/wsjtx-2.6.1/hamlib-prefix/src/hamlib/src/rig.c(2926) trace
ft817_get_vfo: called
ft817_read_eeprom: called
write_block(): TX 5 bytes, method=1
0000??? 00 54 00 00 bb????????????????????????????????????? .T...????????? ?
read_block_generic called, direct=1
read_block_generic(): Timed out 3.3035 seconds after 0 chars, direct=1
Protocol error
)
?1:rig_get_vfo: elapsed=3009ms
?1:rig.c(2947):rig_get_vfo returning(-8) Protocol error

Protocol error
Protocol error
?while testing getting current VFO


 

Hi Dj,

I don¡¯t remember the exact issues I had when trying to upgrade but I ended up doing the same thing: reverted back to 2.5.4. ?

Cheers, Scott


 

It has to do wit this:
The usb port resets when reopened by wsjtx, on arduino this resets the arduino and the ubitx loses track of what was going on.

I had mentioned this to the wsjtx guys but they didn't seem interested in fixing it.
- f



On Tue, Apr 18, 2023, 6:07 PM Scott KE8KYP <scott_massey@...> wrote:
Hi Dj,

I don¡¯t remember the exact issues I had when trying to upgrade but I ended up doing the same thing: reverted back to 2.5.4. ?

Cheers, Scott


 

Thank you Ashhar.? If I understand what you are saying, with version 2.5.4 of WSJT-X it did not reset the USB port, but they changed something in the code for WSJT-X 2.6.1 so that it does reset the USB port?

-Dj


 

I've been helping to troubleshoot this issue with Mike Black W9MDB who is one of the developers for the Hamlib software.

The issue turned out to be a combination of a timing issue and another minor change to the ft817 routines in the Hamlib software.

The fixes are in the master Github repository for Hamlib ().? In order to use WSJT-X 2.6.1, you need to compile the Hamlib software from the source code by cloning the Github repo, then compile WSJT-X 2.6.1 source code and point it to the Hamlib you just installed instead of the one that is bundled with WSJT-X.

I anticipate the changes will eventually make it into the next official release of Hamlib, and then eventually bundled in a future version of WSJT-X.

I have no idea when that might be, but I wanted to share the good news that there is a fix so the uBitx radio will work with the current WSJT-X software.