|
|
I compiled/updated Direwolf on Kubuntu today using "git checkout dev".? Starting Direwolf report 1.8 A which has a reasonable length VOX comment.? ?Then I starting from a new Raspberry Pi build (New Pi5) and downloading/compiling from github also with "git checkout dev".? That gives
me 1.8 D that has 20 lines of VOX commentary.? I think that is a bit much and it is repeated for each
configured device (I have 2).
REQUEST:
Suppress the VOX warning when Audio out device for transmit: null
Another idea would be to add this option to -q v to suppress VOX messages
or BOTH
The VOX warning has no value if there is no transmit audio device, so it makes sense to eliminate the warning.
Adding an option of '-q v' to "quiet the VOX warning" would allow those
who use the application often and have read the warning to suppress it
in future start-ups. Robert Giuliano
KB8RCO
|
Re: Timeout waiting for input from audio device 0. (Windows 11, Paracon, Digirig Lite, FTM-500)
Thank you David,
?
I did not find anything in the windows logs.? I'm planning on moving to Linux soon and will revisit Direwolf at that point in time.
?
Also a big thank you to everyone else who offered their help!
?
Best,
Eric
KG7ASX
|
Re: Unable to connect to IGate server
Not surprising. A lot of networks are restricting outbound access to authorized ports only (such as standard HTTP and HTTPS ports) to prevent malware that sneaks past their security from being able to "phone home". And the standard APRS-IS port numbers are not consistent with any approved web standard. Andrew, KA2DDO ________________________________________ From: [email protected] < [email protected]> on behalf of Sepehr - N6IRN via groups.io <n6irn@...> Sent: Monday, January 27, 2025 10:23 PM To: [email protected]Subject: Re: [direwolf] Unable to connect to IGate server Hi everyone, Thanks for all your assistance. Just wanted to post an update here. Turns out the network that I was trying to use was not allowing outgoing connection to whatever port that APRS uses. I brought the setup home and everything started to work. Then I took the setup back to the original location and this time I used a mobile hotspot. It's been running ever since with no issues. Best, Sepehr N6IRN
|
Re: Unable to connect to IGate server
Hi everyone,
?
Thanks for all your assistance. Just wanted to post an update here. Turns out the network that I was trying to use was not allowing outgoing connection to whatever port that APRS uses. I brought the setup home and everything started to work. Then I took the setup back to the original location and this time I used a mobile hotspot. It's been running ever since with no issues.
?
Best,
?
Sepehr N6IRN
|
Re: Problems trying configure my location for iGate..
You still don't have the figures correct.? The numbers NEVER use seconds. For LAT it is DD^MM.mmmN? ??????? where D-degrees, M-Minutes, m-decimal minutes (not seconds), and requires direction letter (not sign)
????? LON it is DDD^MM.mmmE? ??????? where D-degrees, M-Minutes, m-decimal minutes (not seconds), and requires direction letter (not sign)
Many APRS application requiring a leading zero for Degrees and some for Seconds because they text. Since Direwolf formats the provided information as it generates the packet, it may not require those leading zeros.
Option 2
?? Lat +DD.ddddd where + is the direction sign, D-Degrees, and d-decimal degrees (no '^')
So, if (as you stated) your last portions are 44 and 39 seconds, I suggest you try: ?? PBEACON sendto=igate every=30 overlay=R symbol="igate" LAT=55^56.73N LONG=003^23.65W
To experiment with the format, you could also try ?? PBEACON sendto=igate every=30 overlay=R symbol="igate" LAT=55.9455 LONG=-3.3941
Although not putting the direction may work in some places, there will be times the packet just gets rejected.?
On Sunday, January 26, 2025 at 06:24:58 AM EST, Bob via groups.io <rover.bob123@...> wrote:
Morning All,
OK, with pointers fron Nigel, and some reading between the lines I've managed to get my feet dry and with 1/2 mile of home.....
The problem I was having was that, as Nigel pointed out, the first 2 digits of the lat/longs are your degrees but the second group was actually "Decimal Minutes and Seconds" NOT? decimal degrees...
If you are having problems converting these about, I used to do the conversions and my PBEACON statement now looks like this:
PBEACON sendto=igate every=30 overlay=R symbol="igate" lat=55^56.44 long=3^23.39W via=WIDE1-1,WIDE2-1 (I also got my Eastings/Westings mixed up... DUH)
Thanks for all the help.
Bob
Morning Nigel, Thanks for the reply.... but I'm still not gellint the requied location.... I changed the PBeacon statement to:
PBEACON sendto=igate every=30 overlay=R symbol="igate" lat=55^94 long=3^39E via=WIDE1-1,WIDE2-1
And this puts me just north of New York in the good old US of A.....
What am I doing wrong as I cant find any documentation explaining how to structure the locations string????
Thanks again
Bob Webster GM70BI
On Fri, 24 Jan 2025 at 12:14, rover.bob123 via
<rover.bob123=[email protected]> wrote:
> I've built an iGate with Pi3+ and and Icom RX but I can't get my location on show on properly...
> My Pbeacon statement is:
> PBEACON sendto=igate every=30 overlay=R symbol="igate" lat=42^55.94539 long=071^3.39273E via=WIDE1-1,WIDE2-1
> This locates me in Eastern Europe near Tapaz.....
> What am I doing wrong?? (what do the 42^ and 071^ mean/do???)
They are the degrees of your location, so you are saying that you are
located at 42 degrees and about 56 minutes north.Which just happens to
be the latitude of Taraz in Kazakhstan...
Nigel Worsley
M0ZFJ
|
Re: Problems trying configure my location for iGate..
Morning Bob,
Thanks for this, I'd looked at the manual but the index only went to p107 (I was looking at it? on GITHUB) so hadnt seent that page... I did manage to get it working with a bit of conversion I'm now shoring within 1/2 mile of home...
Thanks for the reply.
Bob GM7OBI
Hi Bob
It's on P111 of the Direwolf User Guide and will accept decimal
notation as well as your example's. Your example though is in the
degree/minute.mmm format but 94 (minutes) exceeds the max of 60.
There is also no "N" specifier.
I don't think any via argument is needed for an igate beacon
either. The manual also specifies sendto=IG.
I think the line might be;
PBEACON sendto=IG every=30 overlay=R
symbol="igate" lat=55.945526 long=-3.392573
or
PBEACON sendto=IG every=30 overlay=R
symbol="igate" lat=55^56.73156N
long=3^23.55438E
Cheers Bob VK2YQA
On 26/1/25 20:58, Bob via
wrote:
Morning Nigel,
Thanks for the reply.... but I'm still not gellint the
requied location....
I changed the PBeacon statement to:
PBEACON sendto=igate every=30 overlay=R
symbol="igate" lat=55^94 long=3^39E via=WIDE1-1,WIDE2-1
And this puts me just north of New York in the good old US
of A.....
What am I doing wrong as I cant find any documentation
explaining how to structure the locations string????
Thanks again
Bob Webster
GM70BI
|
Re: Problems trying configure my location for iGate..
Morning All,
OK, with pointers fron Nigel, and some reading between the lines I've managed to get my feet dry and with 1/2 mile of home.....
The problem I was having was that, as Nigel pointed out, the first 2 digits of the lat/longs are your degrees but the second group was actually "Decimal Minutes and Seconds" NOT? decimal degrees...
If you are having problems converting these about, I used to do the conversions and my PBEACON statement now looks like this:
PBEACON sendto=igate every=30 overlay=R symbol="igate" lat=55^56.44 long=3^23.39W via=WIDE1-1,WIDE2-1 (I also got my Eastings/Westings mixed up... DUH)
Thanks for all the help.
Bob
Morning Nigel, Thanks for the reply.... but I'm still not gellint the requied location.... I changed the PBeacon statement to:
PBEACON sendto=igate every=30 overlay=R symbol="igate" lat=55^94 long=3^39E via=WIDE1-1,WIDE2-1
And this puts me just north of New York in the good old US of A.....
What am I doing wrong as I cant find any documentation explaining how to structure the locations string????
Thanks again
Bob Webster GM70BI
On Fri, 24 Jan 2025 at 12:14, rover.bob123 via
<rover.bob123=[email protected]> wrote:
> I've built an iGate with Pi3+ and and Icom RX but I can't get my location on show on properly...
> My Pbeacon statement is:
> PBEACON sendto=igate every=30 overlay=R symbol="igate" lat=42^55.94539 long=071^3.39273E via=WIDE1-1,WIDE2-1
> This locates me in Eastern Europe near Tapaz.....
> What am I doing wrong?? (what do the 42^ and 071^ mean/do???)
They are the degrees of your location, so you are saying that you are
located at 42 degrees and about 56 minutes north.Which just happens to
be the latitude of Taraz in Kazakhstan...
Nigel Worsley
M0ZFJ
|
Re: Problems trying configure my location for iGate..
Hi Bob
It's on P111 of the Direwolf User Guide and will accept decimal
notation as well as your example's. Your example though is in the
degree/minute.mmm format but 94 (minutes) exceeds the max of 60.
There is also no "N" specifier.
I don't think any via argument is needed for an igate beacon
either. The manual also specifies sendto=IG.
I think the line might be;
PBEACON sendto=IG every=30 overlay=R
symbol="igate" lat=55.945526 long=-3.392573
or
PBEACON sendto=IG every=30 overlay=R
symbol="igate" lat=55^56.73156N
long=3^23.55438E
Cheers Bob VK2YQA
On 26/1/25 20:58, Bob via groups.io
wrote:
toggle quoted message
Show quoted text
Morning Nigel,
Thanks for the reply.... but I'm still not gellint the
requied location....
I changed the PBeacon statement to:
PBEACON sendto=igate every=30 overlay=R
symbol="igate" lat=55^94 long=3^39E via=WIDE1-1,WIDE2-1
And this puts me just north of New York in the good old US
of A.....
What am I doing wrong as I cant find any documentation
explaining how to structure the locations string????
Thanks again
Bob Webster
GM70BI
|
Re: Problems trying configure my location for iGate..
Morning Nigel, Thanks for the reply.... but I'm still not gellint the requied location.... I changed the PBeacon statement to:
PBEACON sendto=igate every=30 overlay=R symbol="igate" lat=55^94 long=3^39E via=WIDE1-1,WIDE2-1
And this puts me just north of New York in the good old US of A.....
What am I doing wrong as I cant find any documentation explaining how to structure the locations string????
Thanks again
Bob Webster GM70BI
On Fri, 24 Jan 2025 at 12:14, rover.bob123 via
<rover.bob123=[email protected]> wrote:
> I've built an iGate with Pi3+ and and Icom RX but I can't get my location on show on properly...
> My Pbeacon statement is:
> PBEACON sendto=igate every=30 overlay=R symbol="igate" lat=42^55.94539 long=071^3.39273E via=WIDE1-1,WIDE2-1
> This locates me in Eastern Europe near Tapaz.....
> What am I doing wrong?? (what do the 42^ and 071^ mean/do???)
They are the degrees of your location, so you are saying that you are
located at 42 degrees and about 56 minutes north.Which just happens to
be the latitude of Taraz in Kazakhstan...
Nigel Worsley
M0ZFJ
|
Re: Problems trying configure my location for iGate..
On Fri, 24 Jan 2025 at 12:14, rover.bob123 via groups.io <rover.bob123@...> wrote: I've built an iGate with Pi3+ and and Icom RX but I can't get my location on show on aprs.fi properly...
My Pbeacon statement is:
PBEACON sendto=igate every=30 overlay=R symbol="igate" lat=42^55.94539 long=071^3.39273E via=WIDE1-1,WIDE2-1
This locates me in Eastern Europe near Tapaz.....
What am I doing wrong?? (what do the 42^ and 071^ mean/do???) They are the degrees of your location, so you are saying that you are located at 42 degrees and about 56 minutes north.Which just happens to be the latitude of Taraz in Kazakhstan... Nigel Worsley M0ZFJ
|
Re: Unable to get Direwolf to connect to IC-7300
Thank you, Bob and all.? I have discovered that the current version? of Direwolf does indeed support PTT on the ICOM USB port.
I changed the PTT line to
PTT COM8 DTR
I changed the USB Send setting in the IC-7300 to DTR
Com 8 is my Icom assigned USB Com port.? I also changed the ADEVICE line to
ADEVICE 8 9
I changed the MODEM line to
This was the suggested by the author of the Direwolf config file setup instructions.? His explanation was using 7 modems with 30 spacing, gives a better chance of decoding HF packets when the sending station may be slightly off frequency.
All seems to be working well now.? I get acks from all my Beacon transmissions.
I am running on 14.105 with good results.
Many thanks to all for the great comments.
?
Bob, KN4HH
?
|
Problems trying configure my location for iGate..
Morning from a cold, wet and windy Scotland....
I've built an iGate with Pi3+ and and Icom RX but I can't get my location on show on aprs.fi properly...
?
I've tried Lat/ Long and UTM.
?
My Pbeacon statement is:
?
PBEACON sendto=igate every=30 overlay=R symbol="igate" lat=42^55.94539 long=071^3.39273E via=WIDE1-1,WIDE2-1
?
This locates me in Eastern Europe near Tapaz.....
?
My lat/long is 55.945526, -3.392573
?
What am I doing wrong?? (what do the 42^ and 071^ mean/do???)
?
Bob
|
Re: Timeout waiting for input from audio device 0. (Windows 11, Paracon, Digirig Lite, FTM-500)
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:
toggle quoted message
Show quoted text
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!
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> ? ? ? ?
|
Re: Timeout waiting for input from audio device 0. (Windows 11, Paracon, Digirig Lite, FTM-500)
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> ? ? ? ?
|
Re: Timeout waiting for input from audio device 0. (Windows 11, Paracon, Digirig Lite, FTM-500)
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:
toggle quoted message
Show quoted text
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.
|
Re: Timeout waiting for input from audio device 0. (Windows 11, Paracon, Digirig Lite, FTM-500)
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.
|
Re: Timeout waiting for input from audio device 0. (Windows 11, Paracon, Digirig Lite, FTM-500)
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:
toggle quoted message
Show quoted text
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?
|
Re: Timeout waiting for input from audio device 0. (Windows 11, Paracon, Digirig Lite, FTM-500)
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?
|
Re: Timeout waiting for input from audio device 0. (Windows 11, Paracon, Digirig Lite, FTM-500)
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:
toggle quoted message
Show quoted text
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
|
Bob
Bob Watson
Jerry Rogich AA2T