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
Timeout waiting for input from audio device 0. (Windows 11, Paracon, Digirig Lite, FTM-500)
|
Hello,
?
I get the the error "Timeout waiting for input from audio device 0. Terminating after audio input failure." immediately upon transmitting? a connection request to a pbbs.? The FTM-500 locks up in transmit, and I need to disconnect the digirig cable from the laptop and restart Direwolf/Paracon to recover.? Yes, it looks like RFI, but this hardware combination works fine with VaraFM and Soundmodem.? I've also added additional ferrite beads to the digirig cable.?
?
I've noticed that I don't get the same error (and transmit lockup) when I set the audio output device to a different soundcard, while keeping the audio input on the digirig lite.? I am able to transmit on the digirig lite without lockup.
?
Direwolf also works fine while just listening on 144.39.? The audio levels look good and most packets are decoded.
?
Any help will be appreciated!
?
Thanks,
Eric
KG7ASX
?
Direwolf config follows:
?
ADEVICE ?1 2
?
CHANNEL 0
?
MYCALL KG7ASX
?
MODEM 1200
PTT CM108
?
AGWPORT 8000
KISSPORT 8001 ?
IGTXLIMIT 6 10
RETRY 5 FRACK 4 MAXFRAME 7 EMAXFRAME 63 PACLEN 128 DWAIT 64 TXDELAY 30 TXTAIL 15 ?
Startup Text:
?
PS C:\Program Files\direwolf-1.7.0-9807304_x86_64> .\direwolf.exe
Dire Wolf version 1.7 Includes optional support for: ?cm108-ptt Reading config file direwolf.conf
Available audio input devices for receive (*=selected): ? ? 0: FTdx-10 Input (USB AUDIO ?CODEC ?* ?1: Digirig Lite Input (2- USB Audi ? (channel 0) ? ? 2: Microphone Array (Intel? Smart Available audio output devices for transmit (*=selected): ? ? 0: FTdx-10 Output (USB AUDIO ?CODE ? ? 1: Speaker (Realtek(R) Audio) ?* ?2: Digirig Lite Output (2- USB Aud ? (channel 0) Channel 0: 1200 baud, AFSK 1200 & 2200 Hz, A+, 44100 sample rate. Using \\?\hid#vid_0d8c&pid_0012&mi_03#7&38439e45&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 ... ?
? |
开云体育Hello Eric, I get the the error "Timeout waiting for input from audio device 0. Terminating after audio input failure." immediately upon transmitting? a connection request to a pbbs.? The FTM-500 locks up in transmit, and I need to disconnect the digirig cable from the laptop and restart Direwolf/Paracon to recover.? Yes, it looks like RFI, but this hardware combination works fine with VaraFM and Soundmodem. Few ideas: ?? - Try removing power from the radio and try direwolf again.? Do you still see the same timeout error?? If not, this is RFI ?? - Have you tried running VARA on the same frequency as you run packet?? Fatal RFI can very much be frequency dependent. I've also added additional ferrite beads to the digirig cable If this is RFI, you'll need to keep adding ferrites to every connector coming in/out of the computer, etc. until hopefully the issue gets fixed. --David KI6ZHD |
|
Hi David,
?
Thank you for the quick reply.? I removed power from the radio and attempted the connect call again, and received the same error:
?
PS C:\Program Files\direwolf-1.7.0-9807304_x86_64> .\direwolf.exe
Dire Wolf version 1.7 Includes optional support for: ?cm108-ptt Reading config file direwolf.conf
Available audio input devices for receive (*=selected): ? ? 0: FTdx-10 Input (USB AUDIO ?CODEC ?* ?1: Digirig Lite Input (2- USB Audi ? (channel 0) ? ? 2: Microphone Array (Intel? Smart Available audio output devices for transmit (*=selected): ? ? 0: FTdx-10 Output (USB AUDIO ?CODE ? ? 1: Speaker (Realtek(R) Audio) ?* ?2: Digirig Lite Output (2- USB Aud ? (channel 0) Channel 0: 1200 baud, AFSK 1200 & 2200 Hz, A+, 44100 sample rate. Using \\?\hid#vid_0d8c&pid_0012&mi_03#7&38439e45&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 ... Attached to AGW client application 0 ...
Ready to accept AGW client application 1 on port 8000 ...
Attempting connect to KG7ASX-1 ... [0L] KG7ASX>KG7ASX-1:(SABME cmd, p=1) Timeout waiting for input from audio device 0. Terminating after audio input failure. PS C:\Program Files\direwolf-1.7.0-9807304_x86_64> ?
I also tested VaraFM on the same frequency and did not have an error or xmit lock-up.
?
Thank you for your help.
Eric
KG7ASX
|
开云体育Hello Eric, PS C:\Program Files\direwolf-1.7.0-9807304_x86_64> .\direwolf.exe Ok.. that's very odd as a lot of people have been successful with the digirig units.? I see in your first post that you have a Digirig-Lite version but I can't imagine that would change anything here.? As a test, can you try the Direwolf v1.8-DEV binary and see if that helps?? It seems the old Official v1.8-A development binary for Windows was removed from Git but there is this one non-official end-user provided build with hamlib support included here: ??
Can you give us some highlights of your specific x86_64 computer hardware? --David KI6ZHD |
|
The Windows audio code hasn't been touched for years so it is extremely unlikely that using version 1.8 would be any different.
?
Rather than using audio device numbers, which can change, like this:
?
ADEVICE ?1 2
?
I would recommend using a substring of the device name like this:
?
ADEVICE? Digirig
?
That won't make a difference for the current problem, but you won't have to worry about the device numbers changing.
?
The Digirig Lite product description mentions a CM108, which is very common and known to work fine.
?
As David said, if you can receive fine and it has spectacular failure when trying to transmit, it is usually RFI getting back into the audio or USB wiring.?
?
Question 1:? Is the Digirig connected directly to the computer or is there a USB hub in between?
?
Question 2: What happens if you try to transmit when the radio is not connected to the Digirig?
?
73,
John WB2OSZ
? |
|
Thanks again for your response.?
?
My computer specs follow:
?
Processor: 12th Gen Intel(R) Core(TM) i3-1215U ? 1.20 GHz
Installed RAM: 32.0 GB (31.7 GB usable
Operating System: Windows 11 Home
?
I'm using the laptop's USB C port to connect the Digirig Lite cable.
?
I installed the 1.8.0 version of Direwolf and had the same error.
?
Thanks
Eric
KG7ASX |
开云体育Hello Eric, Hmmm... very perplexing and I'm thinking this is a USB subsystem issue.? Are there any other USB ports on your computer you can try... ideally NOT with a USB-C connector?? The world of USB has become immensely complex in the last couple of years with all of the newer generation's support for faster speeds, power delivery, external displays, Thunderbolt support, etc.? The classic USB-A ports don't have a lot of that and by using one of these "legacy" ports might help simplify your specific problem. --David KI6ZHD On 01/22/2025 09:17 AM, elarsen34 via
groups.io wrote:
|
|
"David Ranch via groups.io" <direwolf-groupsio@...>
writes: Hmmm... very perplexing and I'm thinking this is a USB subsystemI may be totally confused but have also been seeing problems about USB-C ports. It almost feels like USB-C ports are USB3 only and don't do the handoff to the USB1/2 ohci/uhci chips. An example is a device that has a hub, on which has a umodem and a CH340 usb/serial adaptor (yes, 2 serial ports, different). With USB-C on a macbook pro, did not work. Adding a hub that exposes USB-A ports and using an A-C cable instead of C-C, works fine. 73 de n1dam |
|
Thank you again for the responses;
?
Responding to WB2OSZ:
?
Question 1: ?Is the Digirig connected directly to the computer or is there a USB hub in between?
? - The Digirig Lite is connected directly to a USB C port.? This config works with Soundmodem and VaraFM.? I have a USB hub for other connections.
?
Question 2: What happens if you try to transmit when the radio is not connected to the Digirig?
?? - The same error occurs if I disconnect the cable from the radio, or when the radio is powered off.
?
Responding to David Ranch and Greg Troxel:
?
Are there any other USB ports on your computer you can try... ideally NOT with a USB-C connector?
?? - Yes, I disconnected all my other devices and plugged in the Digirig Lite to a USB A port using the Digirig supplied C to A converter.? I updated the config file accordingly.? The Digirig Lite was then recognized as "4- USB Audio Device".? I got the same error:
?
Dire Wolf version 1.7
Includes optional support for: ?cm108-ptt Reading config file direwolf.conf
Available audio input devices for receive (*=selected): ?* ?0: Microphone (4- USB Audio Device ? (channel 0) ? ? 1: Microphone Array (Intel? Smart Available audio output devices for transmit (*=selected): ?* ?0: Speakers (4- USB Audio Device) ? (channel 0) ? ? 1: Speaker (Realtek(R) Audio) Channel 0: 1200 baud, AFSK 1200 & 2200 Hz, A+, 44100 sample rate. Using \\?\hid#vid_0d8c&pid_0012&mi_03#7&10c94a25&0&0000#{4d1e55b2-f16f-11cf-88cb-001111000030} GPIO 3 for channel 0 PTT control. Ready to accept KISS TCP client application 0 on port 8001 ... Ready to accept AGW client application 0 on port 8000 ... Attached to AGW client application 0 ...
Ready to accept AGW client application 1 on port 8000 ...
Attempting connect to KG7ASX-1 ... [0L] KG7ASX>KG7ASX-1:(SABME cmd, p=1) Timeout waiting for input from audio device 0. Terminating after audio input failure. PS C:\Program Files\direwolf-1.7.0-9807304_x86_64> ? ?
Thanks
Eric
KG7ASX
? |
开云体育Hello Eric, You mentioned that Direwolf would work if configured to use a different sound device.? Because of that, I'm now thinking this could be a CM108 Windows driver issue.? All I can think of is to disconnect the Digirig, go into the Windows Device Manager too and REMOVE the CM108 driver.? Once completed, re-connect the Digirig device where Windows11 will re-install the driver.? See if that helps. --David KI6ZHD On 01/22/2025 10:12 AM, elarsen34 via
groups.io wrote:
|
开云体育Eric/David/John/Greg Shot in the dark that may be worth a look. I don't know the Windows audio system at all, but the behaviour might also be explained by some (other) process grabbing the audio output in exclusive mode. I assume Direwolf tries to grab Windows hardware the same (exclusive) way as Linux, whereas VARA may not. (which would logically explain why that works) The other thought is to have a look in the Windows
syslog/messaging for clues. ie look for any red or yellow blobs
that time coincide with TX/PTT. Also possibly disable the CM108
PTT in the Direwolf config and test/TX. This to establish if the
fault is in the audio system only. Cheers Bob VK2YQA On 23/1/25 10:40, David Ranch via
groups.io wrote:
|
|
Responding to David Ranch:
?
- "disconnect the Digirig, go into the Windows Device Manager too and REMOVE the CM108 driver."
?
??? - I'm not sure I'm doing this correctly.? In Device Manager, under "Sound, video and game controllers", I see a "USB Audio Device" listed.? This disappears after unplugging the Digirig Lite.? So I assume this is the pertinent device to uninstall.? I uninstall it and then plug the Digirig Lite back in and it reappears.? Viewing the properties, I see no mention of a CM108 driver, it seems to be using a Microsoft "USB Audio Device" driver.? Am I looking at the right device? |
开云体育Yeah.. it sounds like you're doing the right thing here.? Hmmm... I don't know what else to say.? There is something clearly not right on your computer between the OS, the Digirig, and Direwolf.? I know you've said other programs work just fine with this combo but clearly Direwolf is doing something differently enough to be a problem.? The only next steps I can think of would be to run the Windows Direwolf in a debugger and start tracing the code execution but I have no idea how to do that on Windows.? Maybe John WB2OSZ or other smart Windows people can give additional ideas. --David KI6ZHD On 01/22/2025 07:14 PM, KG7ASX via
groups.io wrote:
|
|
I had the same issue and I found that an ac line cable in the wall was next to the digirig. I moved it a foot away and been running fine. I can also trigger this by using the audio devices setting in control panel occasionally. Lastly run the pc in high performance os power mgmt mode. Running just a 4 core 2.8 ghz celeron. |
开云体育Jerry:? Did you see this same issue with a Digirig device or just some other USB-based sound device? I've been thinking more about this issue as I hate to give up in defeat but one other possibility is Bob VK2YQA mentioned is that another application is actually using the sound device.? Maybe try: ?? 1. rebooting your machine ?? 2. start direwolf and see if it works or still errors out ?? 3. see what other applications are using sound devices: and either stop them or uninstall them as a test --David KI6ZHD On 01/23/2025 04:48 AM, Jerry Rogich
AA2T via groups.io wrote:
|
|
Thank you for the responses.
?
Some encouraging progress!
?
I completed the following steps:
1. I rebooted my machine
2. Changed the performance mode to "best performance" per Jerry's suggestion
3. Started Direwolf
4. Started Paracon
5. Attempted to connect to my KPC3+ pbbs on a different radio
6. Connection completed (I've never been able to get this far!)
7. Sent command to list messages and the message list returned to view in Paracon
8. Sent command to read a message and message contents returned to view in Paracon
9. Sent command to kill a message
10. I get the same error message as before
?
I was able to reproduce the above behavior over 5 reboot and retry cycles.? Direwolf consistently errors after the above steps.
?
Below is the Direwolf log and eventual error:
?
Windows PowerShell
Copyright (C) Microsoft Corporation. All rights reserved. Install the latest PowerShell for new features and improvements! https://aka.ms/PSWindows
PS C:\Program Files\direwolf-1.7.0-9807304_x86_64> .\direwolf.exe
Dire Wolf version 1.7 Includes optional support for: ?cm108-ptt Reading config file direwolf.conf
Available audio input devices for receive (*=selected): ?* ?0: Digirig Lite (USB Audio Device) ? (channel 0) ? ? 1: FTdx-10 Input (USB AUDIO ?CODEC ? ? 2: Microphone Array (Intel? Smart Available audio output devices for transmit (*=selected): ?* ?0: Digirig Lite (USB Audio Device) ? (channel 0) ? ? 1: Speaker (Realtek(R) Audio) ? ? 2: FTdx-10 Output (USB AUDIO ?CODE Channel 0: 1200 baud, AFSK 1200 & 2200 Hz, A+, 44100 sample rate. Using \\?\hid#vid_0d8c&pid_0012&mi_03#7&38439e45&0&0000#{4d1e55b2-f16f-11cf-88cb-001111000030} GPIO 3 for channel 0 PTT control. Ready to accept KISS TCP client application 0 on port 8001 ... Ready to accept AGW client application 0 on port 8000 ... Attached to AGW client application 0 ...
Ready to accept AGW client application 1 on port 8000 ...
Attempting connect to KG7ASX-1 ... [0L] KG7ASX>KG7ASX-1:(SABME cmd, p=1) KG7ASX-1 audio level = 71(13/12) ? ?_||||||__
[0.3] KG7ASX-1>KG7ASX:(FRMR res, f=1)<0x7f>6<0x00> KG7ASX-1 doesn't understand AX.25 v2.2. ?Trying v2.0 ... [0L] KG7ASX>KG7ASX-1:(SABM cmd, p=1) KG7ASX-1 audio level = 72(13/12) ? ?|||||||__
[0.3] KG7ASX-1>KG7ASX:(UA res, f=1) Stream 0: Connected to KG7ASX-1. ?(v2.0) [0L] KG7ASX>KG7ASX-1:(I cmd, n(s)=0, n(r)=0, p=0, pid=0xf0)l<0x0d> KG7ASX-1 audio level = 47(13/12) ? ?_|||||___
[0.3] KG7ASX-1>KG7ASX:(I cmd, n(s)=0, n(r)=1, p=0, pid=0xf0)MSG# ?ST SIZE ? TO ? ? FROM ? DATE ? ? ? ? ? ? ? ? SUBJECT<0x0d>18 ? ?PN 45 ? ? KG7ASD KG7ASX 01/21/2025 23:21:30 ?test for mail noti KG7ASX-1 audio level = 47(13/12) ? ?_|||||___
[0.3] KG7ASX-1>KG7ASX:(I cmd, n(s)=1, n(r)=1, p=0, pid=0xf0)fication A<0x0d>17 ? ?PH 45 ? ? KG7ASX KG7ASX 01/21/2025 22:42:58 ?test mail notification beaco<0x0d>ENTER COMMAND: ?B,J,K,L,R,S, or Help<0x20> KG7ASX-1 audio level = 47(13/12) ? ?_|||||___
[0.3] KG7ASX-1>KG7ASX:(I cmd, n(s)=2, n(r)=1, p=0, pid=0xf0)><0x0d> [0L] KG7ASX>KG7ASX-1:(RR res, n(r)=3, f=0) [0L] KG7ASX>KG7ASX-1:(I cmd, n(s)=1, n(r)=3, p=0, pid=0xf0)r 18<0x0d> KG7ASX-1 audio level = 47(13/12) ? ?|||||||__
[0.3] KG7ASX-1>KG7ASX:(I cmd, n(s)=3, n(r)=2, p=0, pid=0xf0)MSG#18 01/21/2025 23:21:30 FROM KG7ASX TO KG7ASD<0x0d>SUBJECT: test for mail notification ASD<0x0d>PATH: PBBS<0x0d><0x0d>Test Test ASD<0x0d><0x0d>ENTER COMMAN KG7ASX-1 audio level = 47(13/12) ? ?|||||||__
[0.3] KG7ASX-1>KG7ASX:(I cmd, n(s)=4, n(r)=2, p=0, pid=0xf0)D: ?B,J,K,L,R,S, or Help ><0x0d> [0L] KG7ASX>KG7ASX-1:(RR res, n(r)=5, f=0) [0L] KG7ASX>KG7ASX-1:(I cmd, n(s)=2, n(r)=5, p=0, pid=0xf0)k 18<0x0d> Timeout waiting for input from audio device 0. Terminating after audio input failure. PS C:\Program Files\direwolf-1.7.0-9807304_x86_64> ? ? ? ? |
开云体育Hello KG7ASX, Please review your Windows 11 Event logs around that timeframe of the Direwolf failure and see if there any specific USB or other issues.? This still seems like an RFI or cabling issue to me though you NOT seeing this same issue with other HAM data applications like VARA, etc. is very perplexing. --David KI6ZHD On 01/23/2025 09:40 AM, KG7ASX via
groups.io wrote:
|
Jerry Rogich AA2T
to navigate to use esc to dismiss