AIOC Direwolf Conf File Settings? DigiPi Get Stuck in Transmit, or Doesn't Transmit at All

[Benjamin Pauly]

All:

Can someone please provide me with the Direwolf.xxxxx.conf file settings for PTT on a DigiPi using an AIOC interface?

When I set my DigiPi as an iGate or Digipeater using /dev/ttyACM0, the first time it tries to re-transmit a packet, it goes into a transmit mode and stays that way until I power it off. Syslog is below.

If I set the PTT line in the .conf files to /dev/hidraw0 , then I get "PTT HID" errors and nothing ever transmits over the radio but it receives fine. Syslog is below.

If I do not set a manual PTT setting at all, and the system tries to choose one, it gets stuck in transmit mode just like if I try to use ttyACM0.

So, what am I missing in these .conf files that is not allowing the PTT function?

Thanks for any help!

/dev/ttyACM0 logs

Could not extract card number or name from default
Can't automatically find matching HID for PTT.

Audio device for both receive and transmit: plughw:0,0  (channel 0)
Channel 0: 1200 baud, AFSK 1200 & 2200 Hz, A+, 44100 sample rate / 3, Tx AX.25.

ERROR:  PTT for channel 0 has failed.  See User Guide for troubleshooting tips.
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 device 0 input failure.

ERROR can't open device ttyACM0 for channel 0 PTT control.
No such file or directory
Note: PTT not configured for channel 0.

/dev/hidraw0 logs

Could not extract card number or name from default
Can't automatically find matching HID for PTT.

Audio device for both receive and transmit: plughw:0,0  (channel 0)
Channel 0: 1200 baud, AFSK 1200 & 2200 Hz, A+, 44100 sample rate / 3, Tx AX.25.
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.

Example: Direwolf.digipeater.conf (without the comments, personal info masked for this post)

IGSERVER noam.aprs2.net

MYCALL KO4xxx-2
IGLOGIN KO4xxx-2  1nnn8

PBEACON compress=1 delay=1 every=10 symbol="digi" overlay=1 lat=34.7999 long=-82.2999 via=WIDE2-1 comment="KO4xxx-2 test packet"

DIGIPEAT 0 0 ^WIDE1-1$  ^WIDE1-1$

IGTXVIA 0 WIDE1-1,WIDE2-1

IGTXLIMIT 20 60

# direwolf.tnc.sh will modify and uncomment one of these and copy to /run/direwolf*conf.
# Add PTT line BELOW these to override.  DO NOT edit the following PTT lines, or uncomment
# them.
#PTT GPIOD gpiochip0 12
#PTT RIG RIGNUMBER DEVICEFILE
#PTT /dev/DEVICEFILE RTS
#PTT /dev/DEVICEFILE DTR
#PTT CM108 DEVICEFILE
PTT /dev/hidraw0 -RTS DTR

DWAIT 0
TXDELAY 30
TXTAIL 10
AGWPORT 8000
KISSPORT 8001
ADEVICE plughw:0,0

[Benjamin Pauly]

Based on Craig's response, I added a ferrite bead to each end of the USB cable, attached a mag mount antenna at least 2 meters away from the radio, and added /dev/ttyACM0 back to the Direwolf.xxx.conf files in the PTT section. That took care of the RFI problem and it now will Tx/Rx no problem.

> this is RF on the USB cable, you really really need a ferrite on the cable and/or

> move the antenna away from the Pi in general.... or turn down power.
> 

>

> lock on first transmit

> error -19
> 
> that's the USB port shutting down to protect itself before it can send the PTT-off command
>
> if it helps,
> -craig
> KM6LYW