|
OK I have DINAH working smoothly on a Raspberry PI 3 running direwolf and all is working well.
I have now built from scratch on PI Zero? (PI3 compiles don't always work o PI Zero)? and I get the following errors:
Audio input device 0 error code -19: No such device Audio input device 0 error code -77: File descriptor in bad state Audio input device 0 error code -77: File descriptor in bad state Could not open /dev/hidraw0 for write, errno=2 ERROR: ?PTT for channel 0 has failed.? See User Guide for troubleshooting tips. Audio input device 0 error code -77: File descriptor in bad state Audio input device 0 error code -77: File descriptor in bad state Audio input device 0 error code -77: File descriptor in bad state Audio input device 0 error code -77: File descriptor in bad state Audio input device 0 error code -77: File descriptor in bad state Audio input device 0 error code -77: File descriptor in bad state Audio input device 0 error code -77: File descriptor in bad state Audio input device 0 error code -77: File descriptor in bad state Terminating after audio input failure.
Direwoilf?is initially finding the DINAH as card 1 device 0.
aplay -l identifies the device.
alsamixer -c 1 can adjust sound level.
Thoughts?
Thanks! --
--
|
I was getting exact errors. RFI was causing the USB audio to disconnect. ?Fixed it by separating the radio further, using some choked, etc, but also have a Fe-Pi clone (audio hat) enroute. ?Are you using a USB audio dongle?
toggle quoted message
Show quoted text
On Sep 24, 2021, at 2:56 PM, Don Rolph <don.rolph@...> wrote:
?
OK I have DINAH working smoothly on a Raspberry PI 3 running direwolf and all is working well.
I have now built from scratch on PI Zero? (PI3 compiles don't always work o PI Zero)? and I get the following errors:
Audio input device 0 error code -19: No such device Audio input device 0 error code -77: File descriptor in bad state Audio input device 0 error code -77: File descriptor in bad state Could not open /dev/hidraw0 for write, errno=2 ERROR: ?PTT for channel 0 has failed.? See User Guide for troubleshooting tips. Audio input device 0 error code -77: File descriptor in bad state Audio input device 0 error code -77: File descriptor in bad state Audio input device 0 error code -77: File descriptor in bad state Audio input device 0 error code -77: File descriptor in bad state Audio input device 0 error code -77: File descriptor in bad state Audio input device 0 error code -77: File descriptor in bad state Audio input device 0 error code -77: File descriptor in bad state Audio input device 0 error code -77: File descriptor in bad state Terminating after audio input failure.
Direwoilf?is initially finding the DINAH as card 1 device 0.
aplay -l identifies the device.
alsamixer -c 1 can adjust sound level.
Thoughts?
Thanks! --
--
|
Hello Don,
OK I have DINAH working smoothly on a Raspberry PI
3 running direwolf and all is working well.
I have now built from scratch on PI Zero? (PI3 compiles
don't always work o PI Zero)? and I get the following
errors:
Audio input device 0 error code -19: No such device
Audio input device 0 error code -77: File descriptor in
bad state
Audio input device 0 error code -77: File descriptor in
bad state
Could not open /dev/hidraw0 for write, errno=2
ERROR: ?PTT for channel 0 has failed.? See User Guide for
troubleshooting tips.
Audio input device 0 error code -77: File descriptor in
bad state
Audio input device 0 error code -77: File descriptor in
bad state
Audio input device 0 error code -77: File descriptor in
bad state
Audio input device 0 error code -77: File descriptor in
bad state
Audio input device 0 error code -77: File descriptor in
bad state
Audio input device 0 error code -77: File descriptor in
bad state
Audio input device 0 error code -77: File descriptor in
bad state
Audio input device 0 error code -77: File descriptor in
bad state
Terminating after audio input failure.
These errors smack of RFI interference knocking out the DINAH sound
device.? To confirm, once this error pops up, look at the output of
"dmesg" and see if you have a USB reset and your soundcard is
"re-discovered".? If that's happening, you need to resolve the RFI
issue.? Try and and ALL of the following:
?? - Check to confirm the SWR on your antenna is low
?? - Lower the transmit power on your radio as a test
?? - Move the antenna farther away from the Rpi.? Farther the
better.
?? - Put ferrites on *all* cables going in/out of the Rpi, the radio
(audio cables, power, etc),
--David
|
I had this trouble quite a while back and I found the final thing to do after checking RF plug fitting, adding ferrites, checking earths and swr was to make sure the computer data/CAT cables from the radio were well away from any coax and never in parallel to them if they had to be close anytime.?
I agree some radios are more likely to be affected - but I've most only used Yaesu so never been a show stopping problem.
Dave G0CER
I was getting exact errors. RFI was causing the USB audio to disconnect.? Fixed it by separating the radio further, using some choked, etc, but also have a Fe-Pi clone (audio hat) enroute.? Are you using a USB audio dongle?
11 Max Pro ?
OK I have DINAH working smoothly on a Raspberry PI 3 running direwolf and all is working well.
I have now built from scratch on PI Zero? (PI3 compiles don't always work o PI Zero)? and I get the following errors:
Audio input device 0 error code -19: No such device Audio input device 0 error code -77: File descriptor in bad state Audio input device 0 error code -77: File descriptor in bad state Could not open /dev/hidraw0 for write, errno=2 ERROR: ?PTT for channel 0 has failed.? See User Guide for troubleshooting tips. Audio input device 0 error code -77: File descriptor in bad state Audio input device 0 error code -77: File descriptor in bad state Audio input device 0 error code -77: File descriptor in bad state Audio input device 0 error code -77: File descriptor in bad state Audio input device 0 error code -77: File descriptor in bad state Audio input device 0 error code -77: File descriptor in bad state Audio input device 0 error code -77: File descriptor in bad state Audio input device 0 error code -77: File descriptor in bad state Terminating after audio input failure.
Direwoilf?is initially finding the DINAH as card 1 device 0.
aplay -l identifies the device.
alsamixer -c 1 can adjust sound level.
Thoughts?
Thanks! --
--
|
Yes, a usb audio dongle, with ferrite beads on all wires.
toggle quoted message
Show quoted text
On Sep 24, 2021, at 3:32 PM, J K via groups.io <kuhnje@...> wrote:
? I was getting exact errors. RFI was causing the USB audio to disconnect. ?Fixed it by separating the radio further, using some choked, etc, but also have a Fe-Pi clone (audio hat) enroute. ?Are you using a USB audio dongle?
11 Max Pro On Sep 24, 2021, at 2:56 PM, Don Rolph <don.rolph@...> wrote:
?
OK I have DINAH working smoothly on a Raspberry PI 3 running direwolf and all is working well.
I have now built from scratch on PI Zero? (PI3 compiles don't always work o PI Zero)? and I get the following errors:
Audio input device 0 error code -19: No such device Audio input device 0 error code -77: File descriptor in bad state Audio input device 0 error code -77: File descriptor in bad state Could not open /dev/hidraw0 for write, errno=2 ERROR: ?PTT for channel 0 has failed.? See User Guide for troubleshooting tips. Audio input device 0 error code -77: File descriptor in bad state Audio input device 0 error code -77: File descriptor in bad state Audio input device 0 error code -77: File descriptor in bad state Audio input device 0 error code -77: File descriptor in bad state Audio input device 0 error code -77: File descriptor in bad state Audio input device 0 error code -77: File descriptor in bad state Audio input device 0 error code -77: File descriptor in bad state Audio input device 0 error code -77: File descriptor in bad state Terminating after audio input failure.
Direwoilf?is initially finding the DINAH as card 1 device 0.
aplay -l identifies the device.
alsamixer -c 1 can adjust sound level.
Thoughts?
Thanks! --
--
|
Ah ok. I had the same, also eve using ferrite chokes. ?Is the radio just an HT right by it? ?I’m using an external N9TAX now and have no more issues, but still have the hat coming. ?I found out about the hat in this group. ?It’s just $24 + $4 shipping.
toggle quoted message
Show quoted text
On Sep 24, 2021, at 5:03 PM, Don Rolph <don.rolph@...> wrote:
? Yes, a usb audio dongle, with ferrite beads on all wires. On Sep 24, 2021, at 3:32 PM, J K via groups.io <kuhnje@...> wrote:
? I was getting exact errors. RFI was causing the USB audio to disconnect. ?Fixed it by separating the radio further, using some choked, etc, but also have a Fe-Pi clone (audio hat) enroute. ?Are you using a USB audio dongle?
11 Max Pro On Sep 24, 2021, at 2:56 PM, Don Rolph <don.rolph@...> wrote:
?
OK I have DINAH working smoothly on a Raspberry PI 3 running direwolf and all is working well.
I have now built from scratch on PI Zero? (PI3 compiles don't always work o PI Zero)? and I get the following errors:
Audio input device 0 error code -19: No such device Audio input device 0 error code -77: File descriptor in bad state Audio input device 0 error code -77: File descriptor in bad state Could not open /dev/hidraw0 for write, errno=2 ERROR: ?PTT for channel 0 has failed.? See User Guide for troubleshooting tips. Audio input device 0 error code -77: File descriptor in bad state Audio input device 0 error code -77: File descriptor in bad state Audio input device 0 error code -77: File descriptor in bad state Audio input device 0 error code -77: File descriptor in bad state Audio input device 0 error code -77: File descriptor in bad state Audio input device 0 error code -77: File descriptor in bad state Audio input device 0 error code -77: File descriptor in bad state Audio input device 0 error code -77: File descriptor in bad state Terminating after audio input failure.
Direwoilf?is initially finding the DINAH as card 1 device 0.
aplay -l identifies the device.
alsamixer -c 1 can adjust sound level.
Thoughts?
Thanks! --
--
|
My thanks to JK and David Ranch.
The dreaded RFI seems to strike again.
I have beads on every line.
I turn the transceiver off.
System is stable. ?beacon triggers at appropriate intervals.
Power up transceiver and these failures occur.
Does not happen with Raspberry PI 3, but it looks like PI Zero is more sensitive.
Ok, now to scratch my head and figure out?how to get enough shielding.
Thanks!
Hello Don,
OK I have DINAH working smoothly on a Raspberry PI
3 running direwolf and all is working well.
I have now built from scratch on PI Zero? (PI3 compiles
don't always work o PI Zero)? and I get the following
errors:
Audio input device 0 error code -19: No such device
Audio input device 0 error code -77: File descriptor in
bad state
Audio input device 0 error code -77: File descriptor in
bad state
Could not open /dev/hidraw0 for write, errno=2
ERROR: ?PTT for channel 0 has failed.? See User Guide for
troubleshooting tips.
Audio input device 0 error code -77: File descriptor in
bad state
Audio input device 0 error code -77: File descriptor in
bad state
Audio input device 0 error code -77: File descriptor in
bad state
Audio input device 0 error code -77: File descriptor in
bad state
Audio input device 0 error code -77: File descriptor in
bad state
Audio input device 0 error code -77: File descriptor in
bad state
Audio input device 0 error code -77: File descriptor in
bad state
Audio input device 0 error code -77: File descriptor in
bad state
Terminating after audio input failure.
These errors smack of RFI interference knocking out the DINAH sound
device.? To confirm, once this error pops up, look at the output of
"dmesg" and see if you have a USB reset and your soundcard is
"re-discovered".? If that's happening, you need to resolve the RFI
issue.? Try and and ALL of the following:
?? - Check to confirm the SWR on your antenna is low
?? - Lower the transmit power on your radio as a test
?? - Move the antenna farther away from the Rpi.? Farther the
better.
?? - Put ferrites on *all* cables going in/out of the Rpi, the radio
(audio cables, power, etc),
--David
|
Yeah, it’s a pretty common issue. ?After I posted basically the same exact question a few weeks ago, seen it raised again at least once before yours. ?At least you now know what’s causing it and that it’s relatively easily fixable. ?I should have the Fe-Pi clone here is a couple more days. ?Apparently it’s a non-issue when you use a GPIO audio device instead of USB. ?Once I got it stable, it’s been rock solid thigh. ?Enjoy your setup. ?:-)? 11 Max Pro
toggle quoted message
Show quoted text
On Sep 24, 2021, at 5:25 PM, Don Rolph <don.rolph@...> wrote:
? My thanks to JK and David Ranch.
The dreaded RFI seems to strike again.
I have beads on every line.
I turn the transceiver off.
System is stable. ?beacon triggers at appropriate intervals.
Power up transceiver and these failures occur.
Does not happen with Raspberry PI 3, but it looks like PI Zero is more sensitive.
Ok, now to scratch my head and figure out?how to get enough shielding.
Thanks!
Hello Don,
OK I have DINAH working smoothly on a Raspberry PI
3 running direwolf and all is working well.
I have now built from scratch on PI Zero? (PI3 compiles
don't always work o PI Zero)? and I get the following
errors:
Audio input device 0 error code -19: No such device
Audio input device 0 error code -77: File descriptor in
bad state
Audio input device 0 error code -77: File descriptor in
bad state
Could not open /dev/hidraw0 for write, errno=2
ERROR: ?PTT for channel 0 has failed.? See User Guide for
troubleshooting tips.
Audio input device 0 error code -77: File descriptor in
bad state
Audio input device 0 error code -77: File descriptor in
bad state
Audio input device 0 error code -77: File descriptor in
bad state
Audio input device 0 error code -77: File descriptor in
bad state
Audio input device 0 error code -77: File descriptor in
bad state
Audio input device 0 error code -77: File descriptor in
bad state
Audio input device 0 error code -77: File descriptor in
bad state
Audio input device 0 error code -77: File descriptor in
bad state
Terminating after audio input failure.
These errors smack of RFI interference knocking out the DINAH sound
device.? To confirm, once this error pops up, look at the output of
"dmesg" and see if you have a USB reset and your soundcard is
"re-discovered".? If that's happening, you need to resolve the RFI
issue.? Try and and ALL of the following:
?? - Check to confirm the SWR on your antenna is low
?? - Lower the transmit power on your radio as a test
?? - Move the antenna farther away from the Rpi.? Farther the
better.
?? - Put ferrites on *all* cables going in/out of the Rpi, the radio
(audio cables, power, etc),
--David
--
|
It's a concern with every radio (RF getting into logic/wires).? With
HT's is a disaster!?? I've
seen RF lock up my pi/audio in all of my radios.? The ftm100 in the
truck a couple of times,
the FTM400 in the shack once, and with the Yaesu HT, * every*
time.? It doesn't even survive
one transmission.
HT's are unique in that the ground wire is generally the other half
of the antenna, and that
ground wire extends into the audio interface.?? I've never seen the
Pi Zero lock up, as it
always seems to impact the audio interface, which stops responding
or times out.
The fix, in every situation is a large ferrite bead around the
ptt/audio/ground cable
between the radio and the pi/audio interface.? 100% fix in my
experience.
Not all beads are equal, these seem to work in particular?
if it helps,
-craig
KM6LYW
On 9/24/21 2:33 PM, J K via groups.io
wrote:
toggle quoted message
Show quoted text
Yeah, it’s a pretty common issue. ?After I posted basically the
same exact question a few weeks ago, seen it raised again at least
once before yours. ?At least you now know what’s causing it and
that it’s relatively easily fixable. ?I should have the Fe-Pi
clone here is a couple more days. ?Apparently it’s a non-issue
when you use a GPIO audio device instead of USB. ?Once I got it
stable, it’s been rock solid thigh. ?Enjoy your setup. ?:-)?
11 Max Pro
|
Oh, it can get worse. I was using a USB audio dongle to interface to a mobile rig, and RF got into the cable. It caused the system (a Pi 3b) to think the Volume Down button had been pressed, causing the transmission to fail. And the zero volume couldn't be changed with the mixer, nor would it reset with a reboot. I think it ran negative and crashed something internal. Fixing the RF problem by rebuilding the cable with proper shielding prevented future events, but I never figured out what was happening internally. Greg KO6TH
toggle quoted message
Show quoted text
On September 24, 2021 3:08:03 PM PDT, "Craig, KM6LYW" <craig@...> wrote:
It's a concern with every radio (RF getting into logic/wires).? With
HT's is a disaster!?? I've
seen RF lock up my pi/audio in all of my radios.? The ftm100 in the
truck a couple of times,
the FTM400 in the shack once, and with the Yaesu HT, *every*
time.? It doesn't even survive
one transmission.
HT's are unique in that the ground wire is generally the other half
of the antenna, and that
ground wire extends into the audio interface.?? I've never seen the
Pi Zero lock up, as it
always seems to impact the audio interface, which stops responding
or times out.
The fix, in every situation is a large ferrite bead around the
ptt/audio/ground cable
between the radio and the pi/audio interface.? 100% fix in my
experience.
Not all beads are equal, these seem to work in particular?
if it helps,
-craig
KM6LYW
On 9/24/21 2:33 PM, J K via groups.io
wrote:
Yeah, it’s a pretty common issue. ?After I posted basically the
same exact question a few weeks ago, seen it raised again at least
once before yours. ?At least you now know what’s causing it and
that it’s relatively easily fixable. ?I should have the Fe-Pi
clone here is a couple more days. ?Apparently it’s a non-issue
when you use a GPIO audio device instead of USB. ?Once I got it
stable, it’s been rock solid thigh. ?Enjoy your setup. ?:-)?
11 Max Pro
--
This space for rent...
|
