Input error

[Don Porter]

Greetings all -

Well, trying to use what I have and have made progress. I have the signalink usb between digipi and the radio. in the conf plughw: 0,0

Reading config file /run/direwolf.winlink.conf
Line 7: Warning - IGFILTER is a rarely needed expert level feature.
If you don't have a special situation and a good understanding of
how this works, you probably should not be messing with it.
The default behavior is appropriate for most situations.
Please read "Successful-APRS-IGate-Operation.pdf".
Audio device for both receive and transmit: default  (channel 0)
Channel 0: 1200 baud, AFSK 1200 & 2200 Hz, A+, 44100 sample rate / 3, Tx AX.25.
Initializing GPIO common structure
Opening GPIO line 12 on chip /dev/gpiochip0
Opening GPIO line 16 on chip /dev/gpiochip0
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 digipi'
Virtual KISS TNC is available on /dev/pts/2
Created symlink /tmp/kisstnc -> /dev/pts/2
DNS-SD: Avahi: Service 'Dire Wolf on digipi' successfully registered.
[0L] W9JUN-10>BEACON:W9JUN-10 Winlink LinuxRMS Gateway, http://digipi.org/
Audio input device 0 error code -19: No such device
Audio write error: No such device
Error preparing after error: No such device
Audio write error: No such device

[Don Porter]

I chose USB audio, gpio during initilaize.

NEWCALL=W9JUN
NEWWLPASS=
NEWAPRSPASS=
NEWGRID=EM78ht
NEWLAT=38.7964
NEWLON=-085.3710
NEWGPS=ttyACM3
NEWNODEPASS=abc123
NEWDISPLAYTYPE=st7789
NEWRIGNUMBER=GPIO
NEWDEVICEFILE=ttyACM0 (This doesn't come into play with the signalink usb)
NEWBAUDRATE=115200
NEWBIGVNC=
NEWFLRIG=
NEWI2CAUDIO=fepi

[Craig]

Hi Don, thanks for the details,

This is always an RF-on-the-cables issue, or the Signallink became unplugged?

[0L] W9JUN-10>BEACON:W9JUN-10 Winlink LinuxRMS Gateway, http://digipi.org/
Audio input device 0 error code -19: No such device

You transmit a beacon, then it's gone, typically the USB bus detects the EMI
and shuts down.  You'll likely notice no audio devices in SysInfo, and errors
in SysLog.

Ferrites on the cables?   cold-boot should get you going again, but unless
the RF situation is mitigated, you'll see this repeatedly.

if it helps,
-craig
KM6LYW

--
You received this message because you are subscribed to the Google Groups "DigiPi" group.
To unsubscribe from this group and stop receiving emails from it, send an email to digipi+un...@googlegroups.com.
To view this discussion visit https://groups.google.com/d/msgid/digipi/13b5350b-0d59-4de0-b6be-817c1d0d0ff6n%40googlegroups.com.