开云体育

ctrl + shift + ? for shortcuts
© 2025 开云体育
  1. Direwolf
  2. Topics

windows config: pointing to a specific USB audio and PTT device

 
Edited

Folks - I can't seem to find anything on this, so hoping someone has some experience with this. I'm trying to ditch UZ7HO soundmodem and get back to Direwolf, and now working through config issues on my Windows 11 machine. I have multiple DRA-50s connected, and am using the "cm108" utility to identify the (long) string which identifies the devices. I would then use lines like this to point to them:
?
ADEVICE USB "\\?\hid#vid_0d8c&pid_013a&mi_03#8&2434851&0&0000#{4d1e55b2-f16f-11cf-88cb-001111000030}"
#ADEVICE USB "\\?\hid#vid_0d8c&pid_013a&mi_03#9&42f53e8&0&0000#{4d1e55b2-f16f-11cf-88cb-001111000030}"
PTT CM108 "\\?\hid#vid_0d8c&pid_013a&mi_03#8&2434851&0&0000#{4d1e55b2-f16f-11cf-88cb-001111000030}"
#PTT CM108 "\\?\hid#vid_0d8c&pid_013a&mi_03#9&42f53e8&0&0000#{4d1e55b2-f16f-11cf-88cb-001111000030}"
?
(note the two different identifiers here)
?
However, I get errors at Direwolf boot warning me that some of the settings lines are too long... and then you can see that the name of the device was truncated and then not identified correctly.?
=== snip =================
WARNING: strlcpy result length 87 exceeds maximum length 79. ?(/home/John/src/direwolf-dev/src/config.c config_init 1053)
WARNING: strlcpy result length 135 exceeds maximum length 127. ?(/home/John/src/direwolf-dev/src/cm108.c cm108_inventory 570)
WARNING: strlcpy result length 155 exceeds maximum length 127. ?(/home/John/src/direwolf-dev/src/cm108.c cm108_inventory 570)
WARNING: strlcpy result length 155 exceeds maximum length 127. ?(/home/John/src/direwolf-dev/src/cm108.c cm108_inventory 570)
WARNING: strlcpy result length 159 exceeds maximum length 127. ?(/home/John/src/direwolf-dev/src/cm108.c cm108_inventory 570)
WARNING: strlcpy result length 131 exceeds maximum length 127. ?(/home/John/src/direwolf-dev/src/cm108.c cm108_inventory 570)
There are multiple USB Audio Devices with GPIO capability.
Explicitly specify one of them for more predictable results:
? ?"\\?\hid#vid_0d8c&pid_013a&mi_03#8&2434851&0&0000#{4d1e55b2-f16f-11cf-88cb-001111000030}"
? ?"\\?\hid#vid_0d8c&pid_013a&mi_03#9&42f53e8&0&0000#{4d1e55b2-f16f-11cf-88cb-001111000030}"
Run the "cm108" utility for more details.
"\\?\hid#vid_0d8c&pid_013a&mi_03#8&2434851&0&0000#{4d1e55b2-f16f-11cf-88cb-00111" doesn't match any of the output devices.
Available audio input devices for receive (*=selected):
?* ?0: DRA50 #2 RX (2- USB PnP Sound D ? (channel 0)
? ? 1: SCU-17 HF (RX) (2- USB Audio CO
? ? 2: DRA-50 (RX) (USB PnP Sound Devi
Available audio output devices for transmit (*=selected):
? ? 0: Sceptre F27 (HD Audio Driver fo
? ? 1: DRA50 #2 TX (2- USB PnP Sound D
? ? 2: SCU-17 HF (TX) (2- USB Audio CO
? ? 3: DRA-50 (TX) (USB PnP Sound Devi
? ? 4: speakers? (Realtek(R) Audio)
Channel 0: 1200 baud, AFSK 1200 & 2200 Hz, A+, 44100 sample rate.
Using \\?\hid#vid_0d8c&pid_013a&mi_03#8&2434851&0&0000#{4d1e55b2-f16f-11cf-88cb-001111000030} GPIO 3 for channel 0 PTT control.
Ready to accept AGW client application 0 on port 8000 ...
Ready to accept KISS TCP client application 0 on port 8001 ...
=== /snip =================================
?
Two questions, then:
(1) How to get around this strlcpy character limit for long USB device names in the Windows config file, and
(2) How to point to a specific ADEVICE?
?
On #2, there is documentation about how to point to a specific PTT device, but I'm only guessing that I can point to an ADEVICE like this:
ADEVICE USB ?"\\?\hid#vid_0d8c&pid_013a&mi_03#9&42f53e8&0&0000#{4d1e55b2-f16f-11cf-88cb-001111000030}"
?
Thanks for any help,
?
Brian AG6WR
?
 

开云体育


Hello Brian,

What version of Direwolf are you using here?? I'd recommend to try compiling and using the newest DEV branch version as I think there is a fix already committed there to resolve this:

??

--David
KI6ZHD


On 03/22/2025 12:02 PM, Brian Whitaker via groups.io wrote:

[Edited Message Follows]

Folks - I can't seem to find anything on this, so hoping someone has some experience with this. I'm trying to ditch UZ7HO soundmodem and get back to Direwolf, and now working through config issues on my Windows 11 machine. I have multiple DRA-50s connected, and am using the "cm108" utility to identify the (long) string which identifies the devices. I would then use lines like this to point to them:
?
ADEVICE USB "\\?\hid#vid_0d8c&pid_013a&mi_03#8&2434851&0&0000#{4d1e55b2-f16f-11cf-88cb-001111000030}"
#ADEVICE USB "\\?\hid#vid_0d8c&pid_013a&mi_03#9&42f53e8&0&0000#{4d1e55b2-f16f-11cf-88cb-001111000030}"
PTT CM108 "\\?\hid#vid_0d8c&pid_013a&mi_03#8&2434851&0&0000#{4d1e55b2-f16f-11cf-88cb-001111000030}"
#PTT CM108 "\\?\hid#vid_0d8c&pid_013a&mi_03#9&42f53e8&0&0000#{4d1e55b2-f16f-11cf-88cb-001111000030}"
?
(note the two different identifiers here)
?
However, I get errors at Direwolf boot warning me that some of the settings lines are too long... and then you can see that the name of the device was truncated and then not identified correctly.?
=== snip =================
WARNING: strlcpy result length 87 exceeds maximum length 79. ?(/home/John/src/direwolf-dev/src/config.c config_init 1053)
WARNING: strlcpy result length 135 exceeds maximum length 127. ?(/home/John/src/direwolf-dev/src/cm108.c cm108_inventory 570)
WARNING: strlcpy result length 155 exceeds maximum length 127. ?(/home/John/src/direwolf-dev/src/cm108.c cm108_inventory 570)
WARNING: strlcpy result length 155 exceeds maximum length 127. ?(/home/John/src/direwolf-dev/src/cm108.c cm108_inventory 570)
WARNING: strlcpy result length 159 exceeds maximum length 127. ?(/home/John/src/direwolf-dev/src/cm108.c cm108_inventory 570)
WARNING: strlcpy result length 131 exceeds maximum length 127. ?(/home/John/src/direwolf-dev/src/cm108.c cm108_inventory 570)
There are multiple USB Audio Devices with GPIO capability.
Explicitly specify one of them for more predictable results:
? ?"\\?\hid#vid_0d8c&pid_013a&mi_03#8&2434851&0&0000#{4d1e55b2-f16f-11cf-88cb-001111000030}"
? ?"\\?\hid#vid_0d8c&pid_013a&mi_03#9&42f53e8&0&0000#{4d1e55b2-f16f-11cf-88cb-001111000030}"
Run the "cm108" utility for more details.
"\\?\hid#vid_0d8c&pid_013a&mi_03#8&2434851&0&0000#{4d1e55b2-f16f-11cf-88cb-00111" doesn't match any of the output devices.
Available audio input devices for receive (*=selected):
?* ?0: DRA50 #2 RX (2- USB PnP Sound D ? (channel 0)
? ? 1: SCU-17 HF (RX) (2- USB Audio CO
? ? 2: DRA-50 (RX) (USB PnP Sound Devi
Available audio output devices for transmit (*=selected):
? ? 0: Sceptre F27 (HD Audio Driver fo
? ? 1: DRA50 #2 TX (2- USB PnP Sound D
? ? 2: SCU-17 HF (TX) (2- USB Audio CO
? ? 3: DRA-50 (TX) (USB PnP Sound Devi
? ? 4: speakers? (Realtek(R) Audio)
Channel 0: 1200 baud, AFSK 1200 & 2200 Hz, A+, 44100 sample rate.
Using \\?\hid#vid_0d8c&pid_013a&mi_03#8&2434851&0&0000#{4d1e55b2-f16f-11cf-88cb-001111000030} GPIO 3 for channel 0 PTT control.
Ready to accept AGW client application 0 on port 8000 ...
Ready to accept KISS TCP client application 0 on port 8001 ...
=== /snip =================================
?
Two questions, then:
(1) How to get around this strlcpy character limit for long USB device names in the Windows config file, and
(2) How to point to a specific ADEVICE?
?
On #2, there is documentation about how to point to a specific PTT device, but I'm only guessing that I can point to an ADEVICE like this:
ADEVICE USB ?"\\?\hid#vid_0d8c&pid_013a&mi_03#9&42f53e8&0&0000#{4d1e55b2-f16f-11cf-88cb-001111000030}"
?
Thanks for any help,
?
Brian AG6WR
?
 

David - oh, wow, yes that change looks like it exactly addresses my issue here. I have pulled down v1.7 binaries, the latest I could find.
?
I am going to see if I can figure out how to find and download the latest dev (train? Tree? Branch? Not sure what we call that) and then figure out how to compile it on Windows. I expect to find old advice about how to do that.

many thanks,
?
Brian AG6WR
 

I found sec 4.6 in the user guide and will start down a path on Cygwin and MIngw-w64 and git to be able to download the dev source…

1 - 4 of 4