开云体育

Hello Rich,

It had been running without issue or long transmit delays for over a week. However?direwolf (1.6) exited?last?night. I captured the logs. Here is the direwolf log output:

Since things were working well for you... and I was to guess, I'm thinking your USB stack went south due to RFI issues.? How close is your tranmitting antenna to the Raspberry Pi and it's USB based sound card?

Nov 12 22:35:13 Audio input device 0 error code -5: Input/output error

Nov 12 22:35:24 Audio input device 0 error code -5: Input/output error

If you look in your various /var/log/messages, /var/log/syslog, and "journalctl" output, I bet you'll see the USB sound card went "away".? That's a tell-tale sign of RFI issues.

?

The OS kept running, however in /var/syslog there is this single line around the same time.

Nov 12 22:34:52 pigatez kernel: [569383.647856] dwc2 20980000.usb: dwc2_hc_halt() Channel can't be halted

?

Any insight into this?

Note I'm running this on a Raspberry PI Zero, running Buster 5.4.72. The sound card is a USB device I picked up on Amazon based on the?C-Media HS-100B chipset, Called a TROND AC2-P USB Audio Adapter.

The Direwolf documentation is pretty clear that it's observed "iffy" issues on various soundcards but good luck was found with the Syba units.? I personally think this was really revolving around the USB software stack but it's still early to tell.? A safe test would be to try "upgrading" to a Syba device and see if that helps but moving the TX antenna as far away from the Rpi and adding a bunch of ferrites to all wires going in/out of the Raspberry Pi (audio, power, etc) would be a safe bet too.

--David
KI6ZHD