I picked up FT-817 cables at Hamcation this year to test my first year FT-817. It works great on my Windows 11 Thinkpad. Good QSOs from WSJT-X.
But when I connect to my Linux Mint 22.1 Thinkpad, it locks up with the transmit light on. It is not actually transmitting. there is no power out. If I disconnect the Digirig audio cable, it drops out of transmit. This problem happens even with a dummy load connected. Based on that previous post it appears the cable is defective only under Linux. Is that still the ‘best’ answer?
Darrell Frappier N3JWJ
On Linux I have tried both the version of WSJT-X supplied by the Software Manager and the flatpak version. The parameters and setup are identical for Linux and Windows.
[ 1762.580672] usb 3-1: new high-speed USB device number 8 using xhci_hcd
[ 1762.710177] usb 3-1: New USB device found, idVendor=0424, idProduct=2412, bcdDevice= b.b2
[ 1762.710196] usb 3-1: New USB device strings: Mfr=0, Product=0, SerialNumber=0
[ 1762.712529] hub 3-1:1.0: USB hub found
[ 1762.712870] hub 3-1:1.0: 2 ports detected
[ 1762.999684] usb 3-1.1: new full-speed USB device number 9 using xhci_hcd
[ 1763.109302] usb 3-1.1: New USB device found, idVendor=0d8c, idProduct=013c, bcdDevice= 1.00
[ 1763.109317] usb 3-1.1: New USB device strings: Mfr=1, Product=2, SerialNumber=0
[ 1763.109322] usb 3-1.1: Product: USB PnP Sound Device
[ 1763.109325] usb 3-1.1: Manufacturer: C-Media Electronics Inc.
[ 1763.242673] input: C-Media Electronics Inc. USB PnP Sound Device as /devices/pci0000:00/0000:00:10.0/usb3/3-1/3-1.1/3-1.1:1.3/0003:0D8C:013C.0003/input/input19
[ 1763.295079] hid-generic 0003:0D8C:013C.0003: input,hidraw0: USB HID v1.00 Device [C-Media Electronics Inc. USB PnP Sound Device] on usb-0000:00:10.0-1.1/input3
[ 1763.373485] usb 3-1.2: new full-speed USB device number 10 using xhci_hcd
[ 1763.474292] usb 3-1.2: New USB device found, idVendor=10c4, idProduct=ea60, bcdDevice= 1.00
[ 1763.474304] usb 3-1.2: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[ 1763.474307] usb 3-1.2: Product: CP2102N USB to UART Bridge Controller
[ 1763.474310] usb 3-1.2: Manufacturer: Silicon Labs
[ 1763.474312] usb 3-1.2: SerialNumber: ea7582018c7ded11bcc1ae814fc49859
[ 1763.479955] cp210x 3-1.2:1.0: cp210x converter detected
[ 1763.485585] usb 3-1.2: cp210x converter now attached to ttyUSB0
Try with the handshake explicitly set to None.
The computer may be trying to set RTS signal of the COM port which would in older day indicate readiness of the port to send data, but with Digirig Mobile that signal keys up the radio.
Sorry, I can’t figure out what port to use for RTS PTT, I cant use /dev/ttyUSB0 since that’s already in use as the Serial Port and I don’t get the option to pick it again for PTT. The closest option is USB which doesn’t work.
It should be the same port (/dev/ttyUSB0). It’s in use by the same application so it can use serial data lines for CAT and RTS control line for hardware PTT.
Not sure if UI design issue or something else. This is a legitimate choice and works on Windows. What if you first select the port for PTT and then select it for rig control?
Also I would see if there are other releases of the software that hopefully work better.
I discovered that if I set PTT to /dev/ttyUSB0 while CAT was set to something else, I could come back and set CAT to the same /dev/ttyUSB0. I found I needed Handshake None to make it all work.
The good news is that the radio no longer stays in transmit when I plug in the USB or start WSJT-X. I tried to make some contacts. PSK Reporter shows signal reports for my 5W signal including some in Europe.
But then the problem starts. I tried restarting everything and the same pastern was seen. After about 2 transmission cycles no signals are seen on the water fall. I got responses on 2 QSO attempts, then everything just quit. I captured the last try.
I’m really dumbfounded as to what could cause the waterfall to ‘dry up’. I’ve had multiple QSOs with this radio and Digirig cables from Windows. The other difference is that Linux Mint is running on my only AMD based laptop, a Thinkpad model A475. The A475 runs Windows 10, but as I discovered AMD documents that there is not and never will be a Windows 11 graphics driver for the embedded graphics hardware. The Linux kernel has built-in support so it was an easy choice to switch to my favorite Linux desktop.
You can use lsusb command to see if Digirig dropped out when waterfall goes quiet.
It’s likely related to RFI in this case. You’ll need to use common mode choke on the feedline to address this issue.
I have been testing with a home brew common mode choke since I started this discussion. Today I tried testing with my best common mode choke which I use when traveling. I also added a USB isolator. Depending on the antenna, I find usually find it impossible to operate without that choke when operating with a whip or EFHW.
Starting up WSJT-X I found the audio input put showed as Not Found. I selected it again and started receiving signals. After transmitting, I lost receive very quickly. WSJT-X setup did not show an error for the device, but I found I could start receiving again by selecting the input device. Transmit continues to work and never drops out.
After input signals dropped out, there was no obvious issue found with dmesg and lsusb:
lsusb
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 001 Device 002: ID 0438:7900 Advanced Micro Devices, Inc. Root Hub
Bus 001 Device 003: ID 04f2:b5ab Chicony Electronics Co., Ltd Integrated Camera
Bus 001 Device 004: ID 05e3:0610 Genesys Logic, Inc. Hub
Bus 001 Device 005: ID 0bda:b023 Realtek Semiconductor Corp. RTL8822BE Bluetooth 4.2 Adapter
Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 003 Device 005: ID 0424:2412 Microchip Technology, Inc. (formerly SMSC) Hub
Bus 003 Device 006: ID 0d8c:013c C-Media Electronics, Inc. CM108 Audio Controller
Bus 003 Device 007: ID 10c4:ea60 Silicon Labs CP210x UART Bridge
Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
97.581680] usb 3-1: new high-speed USB device number 5 using xhci_hcd
[ 97.711501] usb 3-1: New USB device found, idVendor=0424, idProduct=2412, bcdDevice= b.b2
[ 97.711521] usb 3-1: New USB device strings: Mfr=0, Product=0, SerialNumber=0
[ 97.715501] hub 3-1:1.0: USB hub found
[ 97.715916] hub 3-1:1.0: 2 ports detected
[ 98.001663] usb 3-1.1: new full-speed USB device number 6 using xhci_hcd
[ 98.111416] usb 3-1.1: New USB device found, idVendor=0d8c, idProduct=013c, bcdDevice= 1.00
[ 98.111435] usb 3-1.1: New USB device strings: Mfr=1, Product=2, SerialNumber=0
[ 98.111510] usb 3-1.1: Product: USB PnP Sound Device
[ 98.111516] usb 3-1.1: Manufacturer: C-Media Electronics Inc.
[ 98.225900] input: C-Media Electronics Inc. USB PnP Sound Device as /devices/pci0000:00/0000:00:10.0/usb3/3-1/3-1.1/3-1.1:1.3/0003:0D8C:013C.0002/input/input18
[ 98.278100] hid-generic 0003:0D8C:013C.0002: input,hidraw0: USB HID v1.00 Device [C-Media Electronics Inc. USB PnP Sound Device] on usb-0000:00:10.0-1.1/input3
[ 98.355908] usb 3-1.2: new full-speed USB device number 7 using xhci_hcd
[ 98.452858] usb 3-1.2: New USB device found, idVendor=10c4, idProduct=ea60, bcdDevice= 1.00
[ 98.452868] usb 3-1.2: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[ 98.452871] usb 3-1.2: Product: CP2102N USB to UART Bridge Controller
[ 98.452874] usb 3-1.2: Manufacturer: Silicon Labs
[ 98.452876] usb 3-1.2: SerialNumber: ea7582018c7ded11bcc1ae814fc49859
[ 98.458501] cp210x 3-1.2:1.0: cp210x converter detected
[ 98.464100] usb 3-1.2: cp210x converter now attached to ttyUSB0
[ 208.414205] warning: `wsjtx’ uses wireless extensions which will stop working for Wi-Fi 7 hardware; use nl80211
[ 211.640125] process ‘/usr/bin/jt9’ started with executable stack
[ 232.417592] rtw_8822be 0000:03:00.0: pci bus timeout, check dma status (Bluetooth Device)
I knew the RFI explanation was bogus. I have experienced plenty of RFI problems. My experience with RFI is that the whole USB connection drops. In this case the CAT connection continues to work and outbound sound works. I have high confidence in my commercial CMC and have plenty of experience with it solving RFI issues.
I tried other USB ports on the A475 Thinkpad and found I would lose receive after 2 CQ calls. This was repeatable every time.
So I bit the bullet and installed Window 10. I will eventually install Linux again so I can dual boot. So same exact hardware all the way that lost USB receive after 2 transmits.
The results were what I expected. NO FAILURES! I set up WSJT-X exactly like my other Windows 11 Thinkpad X13. I can transmit many times in a row and never lose receive. So instead of RFI, I believe the issue is Linux Kernel/Driver for sound USB device.
For my Linux tests I transmitted from a Yaesu FT-817 into an MFJ QRP dummy load with a power out meter which confirmed power out 4 times for each test run. I tried 5W with external power attached and 2.5W running on internal battery. After each test I exited WSJT-X and loaded WSJT-X. Each time it reported the input sound device was not found. After I selected the input sound device, it was ready for a new test.
So I was able to force the error every test. It is absolutely repeatable with a dummy load.
Currently, I don’t think this indicates an issue with the digirig device or cables. They both work fine from 2 different versions of Windows. I did some initial searching for CM108 audio and Ubuntu which is the source of the drivers in Linux Mint. I found an inconclusive post from about audio problems under WSJT-X with a Digimode 3 interface. He too found Windows worked fine. The reported problem is slightly different, but it’s interesting. I will start looking deeper into driver options.
