¿ªÔÆÌåÓý

ctrl + shift + ? for shortcuts
© 2025 Groups.io

Re: PAT/winlink on Pi 4B to IC-9700 via USB cable #flrig #direwolf #pat


 

Thanks Jason and anyone else following.

1. As requested, here is the current output from arecord -l (it is unchanged from what I wrote earlier in this thread):

pi@rpi:~ $ date; sudo arecord -l
Mon 03 Oct 2022 11:53:30 AM PDT
**** List of CAPTURE Hardware Devices ****
card 3: CODEC [USB Audio CODEC], device 0: USB Audio [USB Audio]
? Subdevices: 1/1
? Subdevice #0: subdevice #0

2. I haven't installed any GPS-related software on the Pi.

3. The ICOM radios IC-7300, IC-9700, and IC-705 should be very similar for their providing digital audio in/out and rig control on a single USB cable. So I searched in this group for advice on Pat/winlink with the IC-705 and found a post with these instructions: (/g/KM4ACK-Pi/message/6858)

Verify that the ¡°#¡± is removed in the direwolf.conf file for this line:
PTT RIG 2 localhost:4532

Now that we have FLRIG configured, let¡¯s start the rig control daemon:
/usr/local/bin/rigctld -m 4
Note the ¡°d¡± at the end of rigctl in the above command.

Now we can start direwolf and shouldn¡¯t have any errors.
/usr/local/bin/direwolf -p

4. I shut down the Pi, turned off the radio, turned it back on, then rebooted the Pi.

5.?/usr/local/bin/rigctld -m 4?returns errors as follows; likewise with "-m 3081" (the model number for my radio, IC-9700):

pi@rpi:~ $ date; sudo /usr/local/bin/rigctld -m 4
Mon 03 Oct 2022 12:06:08 PM PDT
rig_open: error = IO error
network.c(301):network_open return(-6)
iofunc.c(177):port_open return(-6)
rig.c(800):rig_open return(-6) (null) Connection refused

pi@rpi:~ $ date; sudo /usr/local/bin/rigctld -m 3081
Mon 03 Oct 2022 12:06:56 PM PDT
rig_open: error = IO error
port_open: serial_open(/dev/ttyS0) status=-6, err=No such file or directory
iofunc.c(81):port_open return(-6)
rig.c(800):rig_open return(-6) (null) No such file or directory?

6. Given those failures, I tried again what seemed (partly) to work over the weekend, which is just to launch "flrig", which returned no error messages.

7. The flrig gui can read and change the dial frequency, can operate PPT, etc., so that all looks good so far. Direwolf -p? returned some errors but didn't fail entirely:

pi@rpi:~ $ date; direwolf -p
Mon 03 Oct 2022 12:11:15 PM PDT
Dire Wolf version 1.6
Includes optional support for:? hamlib cm108-ptt
?
Reading config file direwolf.conf
Audio device for both receive and transmit: plughw:3,0? (channel 0)
Channel 0: 1200 baud, AFSK 1200 & 2200 Hz, E+, 44100 sample rate / 3.
Hamlib Rig open error -6: IO error
network.c(301):network_open return(-6)
iofunc.c(177):port_open return(-6)
rig.c(800):rig_open return(-6)
Ready to accept AGW client application 0 on port 8000 ...
Ready to accept KISS TCP client application 0 on port 8001 ...
Virtual KISS TNC is available on /dev/pts/4
Created symlink /tmp/kisstnc -> /dev/pts/4
?
8. Going now to PAT, which partly worked yesterday, today it fails entirely to connect using AX.25 and "packet" dropdown, reporting "QSY failed: unable to get rig frequency: dial tcp 0.0.0.0:4532: connect: connection refused"

This line in direwolf.conf is not commented out:? "PTT RIG 2 localhost:4532:
I have re-verified that flrig GUI can in fact read and change dial freq., operate PTT, etc.

I feel like it's one step forward; two steps backwards. Sorry I'm not navigating this successfully on my own, despite reading and watching lots.

73,
Bob AK6KA

Join [email protected] to automatically receive all group messages.