Identififing usb ports in use by digirig - linux mint

[ians]

Hi

I’m a returning amateur after a 41 year absence, so please be gentle with me! Less than brilliant hearing and a lot of QRM has pushed me towards exploring digital modes.

So…

• Icom ic725
• brand new digirig mobile and rig specific cables
• usb lead that has data functionality
• thinpad x240 running linux mint 22.3 cinnamon
• wsjt-x

My (first?) problem is that I cannot identify the usb ports in use by digirig: I cannot see an unambiguous match between what linux reports, and the options in wsjt-x settings for the ports.

From the above I can see that the laptop finds digirig, but how does this relate to the port options in wsjt-x? Don’t let the above fool you into thinking I am good with terminal. I just type what I am told to!

[K0TX]

Here’s Digirig’s serial port:

In the software configuration you’ll be referencing entities from under /dev/

Key Identification Commands

• lsusb: Lists connected USB devices; look for “Silicon Labs CP210x UART Bridge”.

• dmesg | grep ttyUSB: Shows kernel logs to confirm which ttyUSBx port the device attached to.

• ls -l /dev/ttyUSB*: Lists all active USB serial ports.

[ians]

So hopefully I’m correct to enter /dev/ttyUSB0 as the serial port under CAT control in wsjt-x?

Had a go and not sure if I’m discovering another problem or still seeing a usb problem.

[Constrainted]

Maybe check and perhaps change the file permissions on /dev/ttyUSB0 to allow the user running wsjt–x to read/write/execute.

Also, what’s going on with .config/hamlib_settings? Does it exist, with proper permissions?

73 Constrainted

[ians]

A bit of a search revealed that linux can be funny about ports due to legacy unix? stuff, and so I tried *sudo adduser user dialout (*my username being “user” on this laptop)

this seems to have changed something:

Hamlib error: Communication timed out

Communication timed out

1:frame.c(455):icom_transaction returning(-5) Communication timed out

../../../rigs/icom/icom.c(1682) trace
set_vfo_curr: vfo=currVFO, curr_vfo=currVFO
set_vfo_curr: Asking for currVFO, currVFO=currVFO
icom.c(9402):set_vfo_curr returning2(0)
0:icom.c(1700):icom_get_freq returning(-5) Communication timed out

rig_get_freq(2147): freqMainA=0, modeMainA=, widthMainA=0
rig_get_freq(2147): freqMainB=0, modeMainB=, widthMainB=0
rig_get_cache(258): vfo=currVFO, current_vfo=currVFO
rig_get_cache(434): vfo=VFOA, freq=0, mode=, width=0
rig_set_cache_freq(121): vfo=currVFO, current_vfo=currVFO
-1:rig_get_freq: elapsed=8976ms
Communication timed out
Communication timed out
while getting current frequency

The timeout will presumably be due to me coming out of the shack (garden shed) and therefore the transceiver being unplugged - but it looks more positive - I’ll try in the morning with the radio plugged in, weather permitting.

Not sure what the .config/hamlib_settings stuff implies -missing folder? However that error seems to have cleared now, oddly. A little knowledge is a dangerous thing, and I don’t really understand what I’m seeing.

[ians]

Success - CAT control established, and wsjt-x playing nicely with the radio. I didn’t have permission to use the port!

Thanks for comments and assistance.

[Constrainted]

Congratulations!

73 Constrainted