Digirig with (tr)usDX

,
1

I purchased a digirig last week to sort out the cable tangle used with a Xiegu G90. Best purchase of any ham related thing I’ve made in a long time as it works flawlessly.

While I was at it, I also bought a cable for a (tr)usDX. I’m unable to achieve CAT control with it although audio input and output work as intended.

I’ve attempted to use Flrig with the (tr)usDX addressed as a usDX, and a TS480HX. I get hamlib errors regardless of port settings. (Windows and Linux).

In Windows 10, device manager shows the FTDI as a Silicon Labs, and for the most part, always assigns the same comport after a reboot. I’ve adjusted the baud rate, parity, stop bits, flow control, etc. with just about every permutation there is.

In Linux (MXLinux, latest kernel as of 09.02.24), /dev/ttyUSB0 is currently at 115,000, 8, N, 1, and no flow control. Again, just about every permutation of combinations have been tried.

With both Windows and Linux, using WSJT-X, I can set rig to “None” and use “RTS” for PTT.
However, having to change frequencies manually preclude using the (tr)usDX for band hopping in WSPR.

What does work, under both Linux and Windows, is using the onboard CH340 FTDI in the (tr)usDX directly with WSJT. This involves using a sound dongle for audio, so I back to three interface cables.

This combo works with Flrig under Windows, but has a one second latency in transmit using Flrig with Linux.

I’ve also used the virtual cable/comport application for the CH340 with Windows. It works about 50 % of the time but constantly looses communication with the radio. I have not tried to use the python app of same under Linux.

I am at the latest firmware for the (tr)uSDX as of 09.0.24. Computer is HP with an I7 processor.

Any suggestions would be appreciated. I am not going to compile a new Linux kernel as they invariably get replaced each time the system is updated.

Thanks,

Karl - W5QJ

2

i’ve only got the knockoff usdx+ v2 “pre-(tr)u”

:frowning:

it prefers kenwood ts-480 @ 38400 and 2 stop bits

kb0wlf

3

Thanks webmonkey, and those settings do work fine with the 200i firmware of the (tr)usDX utilizing the onboard CH340. Latest firmware allows 115,200 baud.

However, just tried your suggestion with the (tr)usDX and digrig interface/cable and it will not connect.

I have the 8 band knock-off of the usDX and it works with what you suggest. I have used it with Flrig and OmniRig for several years.

I’ve spent literally days trying to make the (tr)usDX work with the digirig cable.

Device manager shows the digirig as a Silicon Labs CP210x. I think the digrig itself is fine as it works perfectly with the Xiegu G90.

Thanks for taking the time to reply.

Karl - W5QJ