Keyboard Shortcuts
ctrl + shift + ? :
Show all keyboard shortcuts
ctrl + g :
Navigate to a group
ctrl + shift + f :
Find
ctrl + / :
Quick actions
esc to dismiss
Likes
Search
Multiple Radio Culprit
#direwolf
#linux
I've incorporated two radios into my RPI setup.? I have two digirig soundcards configured as channels 0 and 2 in the .conf file? They's both USB audio.? When rebooting Pi, the addresses (device IDs) swap requiring a swap of the USB cables to the digirigs.? Its a PITA.
Is there some way to code each of these USB devices to prevent this?? I realize the problem may be more a Linux issue.
? |
开云体育Yeah, this is a system thing at not a Direwolf thing per se.?? Do these two Digirig units have unique serial numbers?? You can see all the complete details by looking at the output of "sudo lsusb -vvv".? Maybe you're using a Raspberry Pi 5 where one Digirig can be on the USB2 controller and the other digirig is on the USB3 controller?? You ultimately need SOMETHING to distinguish them so UDEV can name them uniquely. --David KI6ZHD On 04/08/2025 02:47 PM, Steven via
groups.io wrote:
|
It failed to transmit on either transceiver.? Here's my original conf file excerpt:
?
#############################################################
# ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? 145.825MHZ ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ?# #############################################################? ADEVICE1 plughw:4,0 ACHANNELS 1 MODEM 1200 ############################################################# # ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? # # ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? CHANNELS ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? # # ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ?# #############################################################? # ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? 144.39 ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? # ############################################################# CHANNEL 0 MYCALL N7GEE-10 PTT /dev/ttyUSB0 RTS -DTR ############################################################# # ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? 145.825 ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? # ############################################################# CHANNEL 2 MYCALL N7GEE-10 PTT /dev/ttyUSB1 RTS -DTR ############################################################## ?
I tried swapping the USB cables also.? Since one soundcard cable is configured differently than the other (one CIV and the other not) I rather imagine its responsible for the CM108 failure. |
开云体育Hello Steven, An important first question is WHICH Digirig device do you have?? The Mobile or the Lite?? Assuming you're using the Mobile version, your direwolf.conf file is using the wrong syntax for PTT. I you read section 7.6, the syntax needs to be the following for BOTH "channel" stanzas: ?? PTT cm108 --David KI6ZHD On 04/15/2025 12:46 PM, Steven via
groups.io wrote:
|
In addition to David's comments, I see you only have 1 device configured (the second one), but state you are using 2 different DIGIRIGs.
Also, you should use different callsign-ssid for each DIGIRIG units.
?
Assuming the DIGIRIG devices are plughw:4,0 and plughw:5,0 and assuming both are plugged in at the same time, the config file could be:
#############################################################
# ? DEVICES: ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ?# #############################################################? # ? 144.390MHZ ADEVICE plughw:4,0 ACHANNELS 1 #############################################################? # ? 145.825MHZ ADEVICE1 plughw:5,0 ACHANNELS 1 #############################################################
# CHANNEL0 for 144.390 MHz ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ?# #############################################################? CHANNEL 0 MODEM 1200 MYCALL N7GEE-10 # PTT /dev/ttyUSB0 RTS -DTR PTT cm108 #############################################################
# ?CHANNEL2 for 145.825MHZ ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ?# #############################################################? CHANNEL 2 MODEM 1200 MYCALL N7GEE-11 # PTT /dev/ttyUSB1 RTS -DTR PTT cm108 ############################################################## ?
-------
Robert Giuliano KB8RCO |
My bad.? I failed to provide the whole section of the conf file.??
?
I've changed the second MYCALL.? I originally had that configured differently, however, I noted in the guide that was optional.? As I mentioned (above somewhere) CM108 doesn't trigger either PTT line.? I've been using the PTT /dev/ttyUSB0 RTS -DTR for a couple of years with good results.
?
I'm clueless as to why CM108 doesn't perform as expected.?? |
My read of the DIGIRIG Mobile device website () is that PTT is either CAT or RTS on COM
? "*? permanently available independently from CAT port an open-collector PTT switch
?? controlled by RTS signal of the COM port to interface HTs and mobile radios."
?
From that statement, I would say the proper configuration would be
CHANNEL0
? ?PTT /dev/ttyUSB0 RTS
CHANNEL1
? ?PTT /dev/ttyUSB1 RTS
The manual says nothing about DTR, so I would drop that.??
? If the PTT is constant when connected change RTS to -RTS (but I am pretty sure it needs to be just RTS).
?
Do each have working PTT when connected alone?
if so, I would say the Pi does not guarantee HWplug:4,0 to USB0 and HWplug:5,0 to USB1 matching (example).
?
Since they are the same device {idVender} and {idProduct} values would be enough to separate the COM connection for UDEV rules.
?? You will need to find something unique to each, like maybe {iSerial}
Plug each one separately and run
? start with $ lsusb and look at CP2102 in the name (or close to it):
??? $ lsusb -v -d {idVendor}:{idProduct} > DevPlug4.txt
swap
??? $ lsusb -v -d {idVendor}:{idProduct} > DevPlug5.txt
compare the files to find the key differences like maybe {iSerial} if it is set.? Unfortunately, many do not.
?
You could do the same for the CODEC, but I recommend aplay -l to get names to use in place of HWplug
?
Using udev rules and names should help ensure the audio and com devices are the same.
-------
Robert Giuliano KB8RCO |
On Wed, Apr 16, 2025 at 07:20 PM, Rob Giuliano w
Here's what LSUSB says:
?
: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 001 Device 009: ID 0d8c:0012 C-Media Electronics, Inc. USB Audio Device Bus 001 Device 008: ID 10c4:ea60 Silicon Labs CP210x UART Bridge Bus 001 Device 006: ID 0424:2412 Microchip Technology, Inc. (formerly SMSC) Hub Bus 001 Device 004: ID 0951:1666 Kingston Technology DataTraveler 100 G3/G4/SE9 G2/50 Kyson Bus 001 Device 007: ID 10c4:ea60 Silicon Labs CP210x UART Bridge Bus 001 Device 005: ID 0d8c:0012 C-Media Electronics, Inc. USB Audio Device Bus 001 Device 003: ID 0424:2412 Microchip Technology, Inc. (formerly SMSC) Hub Bus 001 Device 002: ID 2109:3431 VIA Labs, Inc. Hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub ?
The 2nd and 5th lines reveal the Silicon Labs bridges (Digirigs).??
?
aplay-l results:
?
card 0: Headphones [bcm2835 Headphones], device 0: bcm2835 Headphones [bcm2835 Headphones] ? Subdevices: 8/8 ? Subdevice #0: subdevice #0 ? Subdevice #1: subdevice #1 ? Subdevice #2: subdevice #2 ? Subdevice #3: subdevice #3 ? Subdevice #4: subdevice #4 ? Subdevice #5: subdevice #5 ? Subdevice #6: subdevice #6 ? Subdevice #7: subdevice #7 card 1: vc4hdmi0 [vc4-hdmi-0], device 0: MAI PCM i2s-hifi-0 [MAI PCM i2s-hifi-0] ? Subdevices: 1/1 ? Subdevice #0: subdevice #0 card 2: vc4hdmi1 [vc4-hdmi-1], device 0: MAI PCM i2s-hifi-0 [MAI PCM i2s-hifi-0] ? Subdevices: 1/1 ? Subdevice #0: subdevice #0 card 3: Device [USB Audio Device], device 0: USB Audio [USB Audio] ? Subdevices: 0/1 ? Subdevice #0: subdevice #0 card 4: Device_1 [USB Audio Device], device 0: USB Audio [USB Audio] ? Subdevices: 0/1 ? Subdevice #0: subdevice #0 |
First off, let me say I am not certain this will solve "your issue", but it will help determine if the PTT issue is due to the COM port and sound card on a given DIGIRIG match.
That was the purpose in asking if PTT worked properly with only 1 DIGIRIG installed.
?
I don't have a DIGIRIG, but do have several devices with a CP210x serial device.? Some have {iSerial} or {serial}, but most do not.
I am no longer confident in this approach.
?
Lets like at a "path" option:
? ?Now that we know which BUS:Port? is which, can you show the contents of
? ? ? ?$ ls -Al /dev/serial/by-path/? ? ? ? ? ?(some OSes use ls -Al /dev/serial/by-id/)
See if you can match the information to the physical port on the Pi (top-left, top-right, bottom-left, bottom-right).
?
If so, we can work from there.
-------
Robert Giuliano KB8RCO |
There are two versions, now, of the Digirig sound card...one called "mobile" and the other captioned as "Lite".? I learned, here, that the "mobile" version (mine) doesn't support COM108 PTT.
?
In digging around, I was able to identify two separate serial numbers on these devices:
?
5e375fc11987ed118f4329d7a603910e
f0a610ace98bee1189aefe018acbdcd8 ?
however, I don't fully understand how to rename them with that information.? Currently they're named ttyUSB0 and ttyUSB1 under /dev.?? |
开云体育Hi Steven,The lite does work. You have to get and build Martin’s version because it hasn’t been merged into the main branch yet.? One word of caution. I spent much of today trying to troubleshoot a failure with it and found that it’s very susceptible to rfi so you will likely either need to put ferries on the usb cable or put an external antenna on the radio.? 73 de K6EF On Apr 17, 2025, at 3:51?PM, Steven via groups.io <stevene1@...> wrote:
|
to navigate to use esc to dismiss