开云体育

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

Direwolf won't send APRS messages

 

Any help would be appreciated...

My setup: Raspberry PI 4, DireWolf 1.7, DigiRig, Baofeng
? ? Digirig at /dev/ttyUSB0
? ? card 1: Device [USB Audio Device], device 0: USB Audio [USB Audio]
? ? ? ? Subdevices: 1/1
? ? ? ? Subdevice #0: subdevice #0

? ? ADEVICE ?plughw:1,0

I can? receive messages just fine, and send messages over IGate, but as soon as I turn on PTT, by uncomenting:
? ??PTT /dev/ttyUSB0 RTS

And when direwolf trys?to transmit, I get this:

One or more sometimes many of these messages:
[0L] KA7RLV-10>APDW17,WIDE1-1,WIDE2-1:!4817.19NS11722.44W#PHG3040Usk WA US
Audio input device 0 error code -32: Broken pipe
This is most likely caused by the CPU being too slow to keep up with the audio stream.
Use the "top" command, in another command window, to look at CPU usage.
This might be a temporary condition so we will attempt to recover a few times before giving up.
If using a very slow CPU, try reducing the CPU load by using -P- command
line option for 9600 bps or -D3 for slower AFSK .

I have tried?using the -P- option when running direwolf, no real difference.

Sometimes I get this after the other errors:
ALSA lib pcm.c:8573:(snd_pcm_recover) cannot recovery from overrun, prepare failed: Input/output error
Audio input device 0 error code -19: No such device
Audio input device 0 error code -19: No such device
Audio input device 0 error code -19: No such device
Audio input device 0 error code -19: No such device
Audio input device 0 error code -19: No such device
Audio input device 0 error code -19: No such device
Audio input device 0 error code -19: No such device
Audio input device 0 error code -19: No such device
Audio input device 0 error code -19: No such device
Audio input device 0 error code -19: No such device
Terminating after audio input failure.
 

开云体育

Possibly RFI interfering with the USB susbsytem.

Try:

- lowering RF power out

- Putting ferrite beads on the cables.


On Nov 26, 2024, at 3:30?PM, Richard Vantrease via groups.io <richvantrease@...> wrote:

?
Any help would be appreciated...

My setup: Raspberry PI 4, DireWolf 1.7, DigiRig, Baofeng
? ? Digirig at /dev/ttyUSB0
? ? card 1: Device [USB Audio Device], device 0: USB Audio [USB Audio]
? ? ? ? Subdevices: 1/1
? ? ? ? Subdevice #0: subdevice #0

? ? ADEVICE ?plughw:1,0

I can? receive messages just fine, and send messages over IGate, but as soon as I turn on PTT, by uncomenting:
? ??PTT /dev/ttyUSB0 RTS

And when direwolf trys?to transmit, I get this:

One or more sometimes many of these messages:
[0L] KA7RLV-10>APDW17,WIDE1-1,WIDE2-1:!4817.19NS11722.44W#PHG3040Usk WA US
Audio input device 0 error code -32: Broken pipe
This is most likely caused by the CPU being too slow to keep up with the audio stream.
Use the "top" command, in another command window, to look at CPU usage.
This might be a temporary condition so we will attempt to recover a few times before giving up.
If using a very slow CPU, try reducing the CPU load by using -P- command
line option for 9600 bps or -D3 for slower AFSK .

I have tried?using the -P- option when running direwolf, no real difference.

Sometimes I get this after the other errors:
ALSA lib pcm.c:8573:(snd_pcm_recover) cannot recovery from overrun, prepare failed: Input/output error
Audio input device 0 error code -19: No such device
Audio input device 0 error code -19: No such device
Audio input device 0 error code -19: No such device
Audio input device 0 error code -19: No such device
Audio input device 0 error code -19: No such device
Audio input device 0 error code -19: No such device
Audio input device 0 error code -19: No such device
Audio input device 0 error code -19: No such device
Audio input device 0 error code -19: No such device
Audio input device 0 error code -19: No such device
Terminating after audio input failure.
 

Also move the antenna farther away from the other components.
(Don't use a rubber ducky on top of the radio.)
?
73,
John WB2OSZ
 

开云体育


On 26 Nov 2024, at 20:16, Richard Vantrease via <richvantrease@...> wrote:

Any help would be appreciated…
tell me a wee bit more about the PI setup
1 are you using a window manager (GUI) or on a ‘dumb terminal’?
2 where are you with the power supply for the PI? ?Is it a decent unit that can handle the spikes OK - or is it cheap PSU - how many amps can it deliver??
3 The PTT press - can you see any indication on the Baofeng that it is transmitting? (I can switch the TX light on on mine) ?or does it all go wrong before the TX signal hits the radio?
4 If you run the program - but without the PTT connected - does it run OK (I appreciate it wont TX) - in which case likely to be interference - get the radio antenna on a flying lead and away from the kit
Cant think of anything else for now


My setup: Raspberry PI 4, DireWolf 1.7, DigiRig, Baofeng
? ? Digirig at /dev/ttyUSB0
? ? card 1: Device [USB Audio Device], device 0: USB Audio [USB Audio]
? ? ? ? Subdevices: 1/1
? ? ? ? Subdevice #0: subdevice #0

? ? ADEVICE ?plughw:1,0

I can? receive messages just fine, and send messages over IGate, but as soon as I turn on PTT, by uncomenting:
? ??PTT /dev/ttyUSB0 RTS

And when direwolf trys?to transmit, I get this:

One or more sometimes many of these messages:
[0L] KA7RLV-10>APDW17,WIDE1-1,WIDE2-1:!4817.19NS11722.44W#PHG3040Usk WA US
Audio input device 0 error code -32: Broken pipe
This is most likely caused by the CPU being too slow to keep up with the audio stream.
Use the "top" command, in another command window, to look at CPU usage.
This might be a temporary condition so we will attempt to recover a few times before giving up.
If using a very slow CPU, try reducing the CPU load by using -P- command
line option for 9600 bps or -D3 for slower AFSK .

I have tried?using the -P- option when running direwolf, no real difference.

Sometimes I get this after the other errors:
ALSA lib pcm.c:8573:(snd_pcm_recover) cannot recovery from overrun, prepare failed: Input/output error
Audio input device 0 error code -19: No such device
Audio input device 0 error code -19: No such device
Audio input device 0 error code -19: No such device
Audio input device 0 error code -19: No such device
Audio input device 0 error code -19: No such device
Audio input device 0 error code -19: No such device
Audio input device 0 error code -19: No such device
Audio input device 0 error code -19: No such device
Audio input device 0 error code -19: No such device
Audio input device 0 error code -19: No such device
Terminating after audio input failure.
 

I'm having the same issue.

Hardware :? I'm using an sbitx v3 (pi 4b) > unpowered usba hub > usba to usbc adapter > digirig lite > baofeng.? The hardware is colocated, though the hf side of my sbitx is not powered up.? Of note, the digirig lite did work without issue being closely colocated with my old phone and worked great.? Yes I have ferrite beads involved.? Power supply is through the radio side of the sbitx via the gpio pins.? I have it plugged into a substantial battery pack rated for 12 amps of draw by the wiring.

Settings : KISS over tcp : localhost, 8001 (confirmed),?
?
Behavior :
"
Dire Wolf version 1.7
Includes optional support for: ?hamlib cm108-ptt dns-sd
Reading config file /home/pi/.direwolf.conf
Audio device for both receive and transmit: plughw:3,0 ?(channel 0)
Channel 0: 1200 baud, AFSK 1200 & 2200 Hz, A+, 44100 sample rate.
Using /dev/hidraw2 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 ...
DNS-SD: Avahi: Announcing KISS TCP on port 8001 as 'Dire Wolf on sbitx'
DNS-SD: Avahi: Service 'Dire Wolf on sbitx' successfully registered.
Attached to KISS TCP client application 0 on port 8001 ...
Ready to accept KISS TCP client application 1 on port 8001 ...
KISS protocol set hardware "TNC:", chan 0
"?
?
It does receive and decode very well.? Though I get persistent finicky complaints about the volume despite feathering the radio / mixer.

Everything is working fine until transmission time.? The radio is activated via ptt for a blip, then it turns off and off we go into errors as above.

Aaron
KQ4UDA
 

开云体育


To prove that this is an RFI issue, tune your radio to frequency you know where it will *refuse* to transmit.? Once QSYed, start up Direwolf and try tranmitting a packet.? See if the PTT indicator lights up and the errors from Direwolf and the OS go away.

--David
KI6ZHD


On 04/14/2025 09:48 PM, KQ4UDA via groups.io wrote:

I'm having the same issue.

Hardware :? I'm using an sbitx v3 (pi 4b) > unpowered usba hub > usba to usbc adapter > digirig lite > baofeng.? The hardware is colocated, though the hf side of my sbitx is not powered up.? Of note, the digirig lite did work without issue being closely colocated with my old phone and worked great.? Yes I have ferrite beads involved.? Power supply is through the radio side of the sbitx via the gpio pins.? I have it plugged into a substantial battery pack rated for 12 amps of draw by the wiring.

Settings : KISS over tcp : localhost, 8001 (confirmed),?
?
Behavior :
"
Dire Wolf version 1.7
Includes optional support for: ?hamlib cm108-ptt dns-sd
Reading config file /home/pi/.direwolf.conf
Audio device for both receive and transmit: plughw:3,0 ?(channel 0)
Channel 0: 1200 baud, AFSK 1200 & 2200 Hz, A+, 44100 sample rate.
Using /dev/hidraw2 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 ...
DNS-SD: Avahi: Announcing KISS TCP on port 8001 as 'Dire Wolf on sbitx'
DNS-SD: Avahi: Service 'Dire Wolf on sbitx' successfully registered.
Attached to KISS TCP client application 0 on port 8001 ...
Ready to accept KISS TCP client application 1 on port 8001 ...
KISS protocol set hardware "TNC:", chan 0
"?
?
It does receive and decode very well.? Though I get persistent finicky complaints about the volume despite feathering the radio / mixer.

Everything is working fine until transmission time.? The radio is activated via ptt for a blip, then it turns off and off we go into errors as above.

Aaron
KQ4UDA
 

I had these exact errors, someone suggested RFI.? Put a ferrite bead on the USB cable, and problem solved.?
 

Appreciate the response.

I don't really have a good option for the frequency on this unlocked ht.? So I turned the output to low and removed the antenna.? It did change the errors.

Now sitting on the following error while trying YAAC? "
ioctl HIDIOCGRAWINFO failed for /dev/hidraw2. errno = 22.
Write to /dev/hidraw2 failed, n=-1, errno=22
ERROR: ?PTT for channel 0 has failed. ?See User Guide for troubleshooting tips.
"? ?
?
HOWEVER, when direwolf fires up, everything "just works" until it has to do the work.??Full happy direwolf text "
Dire Wolf version 1.7
Includes optional support for: ?hamlib cm108-ptt dns-sd
Reading config file /home/pi/.direwolf.conf
Audio device for both receive and transmit: plughw:3,0 ?(channel 0)
Channel 0: 1200 baud, AFSK 1200 & 2200 Hz, A+, 44100 sample rate.
Using /dev/hidraw2 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 ...
DNS-SD: Avahi: Announcing KISS TCP on port 8001 as 'Dire Wolf on sbitx'
DNS-SD: Avahi: Service 'Dire Wolf on sbitx' successfully registered.
"

I tried the silent ptt test, but the light on the digirig light failed to come on, which points toward a hardware interface issue as far as I'm aware.? "
pi@sbitx:~ $ direwolf -c ~/.direwolf.conf -x p
Dire Wolf version 1.7
Includes optional support for: ?hamlib cm108-ptt dns-sd
Reading config file /home/pi/.direwolf.conf
Audio device for both receive and transmit: plughw:3,0 ?(channel 0)
Channel 0: 1200 baud, AFSK 1200 & 2200 Hz, A+, 44100 sample rate.
Using /dev/hidraw2 GPIO 3 for channel 0 PTT control.
ioctl HIDIOCGRAWINFO failed for /dev/hidraw2. errno = 6.
Write to /dev/hidraw2 failed, n=-1, errno=22
ERROR: ?PTT for channel 0 has failed. ?See User Guide for troubleshooting tips.
Sending silence (Set PTT only) on channel 0.
Press control-C to terminate.
^C
QRT
ioctl HIDIOCGRAWINFO failed for /dev/hidraw2. errno = 22.
Write to /dev/hidraw2 failed, n=-1, errno=22
ERROR: ?PTT for channel 0 has failed. ?See User Guide for troubleshooting tips.
pi@sbitx:~ $?
"

If I'm throwing way too much information in here, please let me know.? I'm new to this forum.? If you need any further details, I'm happy to provide them.

1 - 8 of 8