Unable to connect FT-710 with digirig with anything but WSJTX.

[M Roemer]

I am attempting to use my FT-710 with the digirig but am not having any luck getting it to connect. I keep receiving Failed to connect to KISS interface | aprsd.cliant.drivers.tcpkiss:setup_connection:196 | Failed to connect to local host:1801 - [Errno111] connection refused aprsd.cliand.drive. Does anyone have any idea on how to correct this issue?

[Craig]

Hi M,

What app are you using?  if using aprs software, APRS TNC/igate should be turned on first,
and KISS port is 8001/tcp

On 3/23/26 14:16, M Roemer wrote:

I am attempting to use my FT-710 with the digirig but am not having any luck getting it to connect. I keep receiving Failed to connect to KISS interface | aprsd.cliant.drivers.tcpkiss:setup_connection:196 | Failed to connect to local host:1801 - [Errno111] connection refused aprsd.cliand.drive. Does anyone have any idea on how to correct this issue? --
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/2f55c341-13b4-4f44-aeb2-e77f262c1646n%40googlegroups.com.

[M Roemer]

I apologize I am using the digipi software with a raspberry pi zero 2 w. I have turned on APRS HF TNC/iGate and APRS webchat and it will not control the radio, it will not even key up when I try to send a SMS.

[Craig]

okay, great, click PktLog and possibly paste what you see here.  the TNC
isn't starting for whatever reason. I assume you have a USB cable hooked
up between the 710 and the Raspberry Pi as wsjtx is working.

It might also help if you post errors from SysLog.


cool,
-craig
KM6LYW

To view this discussion visit https://groups.google.com/d/msgid/digipi/437ece65-d2be-4cb6-a63d-ee115315da2cn%40googlegroups.com.

[M Roemer]

**2:rig_set_ptt: elapsed=2158ms
**2:rig.c(3598):rig_set_ptt returning(-8) Protocol error

Protocol error


KISS client application 0 on TCP port 8001 has gone away.

tail: /run/direwolf.log: file truncated
Dire Wolf version 1.8 (Oct  4 2025) KM6LYW-1
Includes optional support for:  gpsd hamlib cm108-ptt libgpiod-2.2.1 dns-sd

Reading config file /run/direwolf.tnc300b.conf
Audio device for both receive and transmit: plughw:0,0  (channel 0)
Channel 0: 300 baud, AFSK 1600 & 1800 Hz, A+, 44100 sample rate / 3, Tx FX.25.
Initializing GPIO common structure
Opening GPIO line 16 on chip /dev/gpiochip0
Hamlib determined CAT control serial port rate of 115200.
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/3
Created symlink /tmp/kisstnc -> /dev/pts/3
DNS-SD: Avahi: Service 'Dire Wolf on digipi' successfully registered.

Now connected to IGate server noam.aprs2.net (69.197.140.169)
Check server status here http://69.197.140.169:14501


Attached to KISS TCP client application 0 on port 8001 ...

Ready to accept KISS TCP client application 1 on port 8001 ...
[ig] # aprsc 2.1.19-g730c5c0
[ig] # logresp KF8EMO-2 verified, server T2MCI

This is my PktLog

[M Roemer]

Mar 24 00:17:44 digipi webchat.sh[1995]: 2026-03-24 00:17:44.560 | MainThread         | ERROR    | Failed to connect to localhost:8001 - [Errno 111] Connection refused | aprsd.client.drivers.tcpkiss:connect:338
Mar 24 00:17:44 digipi webchat.sh[1995]: 2026-03-24 00:17:44.561 | MainThread         | ERROR    | Failed to connect to KISS interface | aprsd.client.drivers.tcpkiss:setup_connection:196
Mar 24 00:17:44 digipi webchat.sh[1995]: 2026-03-24 00:17:44.563 | MainThread         | ERROR    | Failed to connect to localhost:8001 - [Errno 111] Connection refused | aprsd.client.drivers.tcpkiss:connect:338
Mar 24 00:17:44 digipi webchat.sh[1995]: 2026-03-24 00:17:44.564 | MainThread         | ERROR    | Failed to connect to KISS interface | aprsd.client.drivers.tcpkiss:setup_connection:196
Mar 24 00:17:44 digipi webchat.sh[1995]: 2026-03-24 00:17:44.566 | MainThread         | ERROR    | Failed to connect to localhost:8001 - [Errno 111] Connection refused | aprsd.client.drivers.tcpkiss:connect:338
Mar 24 00:17:44 digipi webchat.sh[1995]: 2026-03-24 00:17:44.566 | MainThread         | ERROR    | Failed to connect to KISS interface | aprsd.client.drivers.tcpkiss:setup_connection:196
Mar 24 00:17:45 digipi webchat.sh[1995]: 2026-03-24 00:17:45.513 | RX_PKT             | ERROR    | Failed to connect to localhost:8001 - [Errno 111] Connection refused | aprsd.client.drivers.tcpkiss:connect:338
Mar 24 00:17:45 digipi webchat.sh[1995]: 2026-03-24 00:17:45.515 | RX_PKT             | ERROR    | Failed to connect to KISS interface | aprsd.client.drivers.tcpkiss:setup_connection:196
Mar 24 00:17:45 digipi webchat.sh[1995]:  * Serving Flask app 'aprsd_webchat_extension'
Mar 24 00:17:45 digipi webchat.sh[1995]:  * Debug mode: off
Mar 24 00:23:25 digipi systemd[1]: Starting man-db.service - Daily man-db regeneration...
Mar 24 00:23:25 digipi mandb[2614]: mandb: fopen /var/cache/man/2614: Read-only file system
Mar 24 00:23:25 digipi mandb[2614]: mandb: can't remove /var/cache/man/2614: Read-only file system
Mar 24 00:23:25 digipi mandb[2614]: mandb: fopen /var/cache/man/uk/2614: Read-only file system
Mar 24 00:23:25 digipi mandb[2614]: mandb: can't remove /var/cache/man/uk/2614: Read-only file system
Mar 24 00:23:25 digipi mandb[2614]: mandb: fopen /var/cache/man/de/2614: Read-only file system
Mar 24 00:23:25 digipi mandb[2614]: mandb: can't remove /var/cache/man/de/2614: Read-only file system
Mar 24 00:23:25 digipi mandb[2614]: mandb: fopen /var/cache/man/id/2614: Read-only file system
Mar 24 00:23:25 digipi mandb[2614]: mandb: can't remove /var/cache/man/id/2614: Read-only file system
Mar 24 00:23:25 digipi mandb[2614]: mandb: fopen /var/cache/man/zh_TW/2614: Read-only file system
Mar 24 00:23:25 digipi mandb[2614]: mandb: can't remove /var/cache/man/zh_TW/2614: Read-only file system
Mar 24 00:23:25 digipi mandb[2614]: mandb: fopen /var/cache/man/fr/2614: Read-only file system
Mar 24 00:23:25 digipi mandb[2614]: mandb: can't remove /var/cache/man/fr/2614: Read-only file system
Mar 24 00:23:25 digipi mandb[2614]: mandb: fopen /var/cache/man/pl/2614: Read-only file system
Mar 24 00:23:25 digipi mandb[2614]: mandb: can't remove /var/cache/man/pl/2614: Read-only file system
Mar 24 00:23:25 digipi mandb[2614]: mandb: fopen /var/cache/man/hr/2614: Read-only file system
Mar 24 00:23:25 digipi mandb[2614]: mandb: can't remove /var/cache/man/hr/2614: Read-only file system
Mar 24 00:23:25 digipi mandb[2614]: mandb: fopen /var/cache/man/nb/2614: Read-only file system
Mar 24 00:23:25 digipi mandb[2614]: mandb: can't remove /var/cache/man/nb/2614: Read-only file system
Mar 24 00:23:25 digipi mandb[2614]: mandb: fopen /var/cache/man/sr/2614: Read-only file system

This is my SysLog

[Craig]

ok, so let's step back to the title of this thread, are you using a
DigiRig with an FT710?

You should use just a USB cable, and select [USB Connected Radio] when
initializing.

please confirm, thanks,
-craig
KM6LYW

[M Roemer]

I am using a raspberry pi zero 2 w with digipi on it. I have the USB cable connected, I selected [USB Connected Radio], used the FT-710 code with ttyUSB0.

Here is a copy of my SysInfo.

Radio / GPS

ttyUSB1: usb-Silicon_Labs_CP2105_Dual_USB_to_UART_Bridge_Controller_01B9C4AF-if01-port0
ttyUSB0: usb-Silicon_Labs_CP2105_Dual_USB_to_UART_Bridge_Controller_01B9C4AF-if00-port0
ttyACM0: usb-u-blox_AG_-_www.u-blox.com_u-blox_7_-_GPS_GNSS_Receiver-if00

---

Audio Interface

0 [Device ]: USB-Audio - USB Audio Device C-Media Electronics Inc. USB Audio Device at usb-3f980000.usb-1.2.2, full speed

---

Memory Usage: 38%

Thank you for the assistance.

Mark

KF8EMO

[M Roemer]

Well I figured out why it was not talking to my radio. I looked at the PktLog file myself and found that it was sending over a baud rate of 115200, I set my radio to that rate and it is talking now. When I did my initialization I set it to 38400. I am not getting a response from the WXBOT like you do in your short. Any thoughts on this?

Thank you for your assistance

Mark Roemer

KF8EMO

[Craig]

that's a good discovery/point that applies to everyone, with packet modes, direwolf/hamlib
will use the highest baud rate available on the particular model of radio.  The initialize 
value isn't used for direwolf (but is used for rigctld) - technically that's a bug.

Regarding WXBOT, make sure you send at least one position beacon per day so the
routing tables know how to reply to your location.  Also watch PktLog for activity to make
sure there are gates in your area.

cool,
-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/9bc0ef86-ec60-49fa-ac75-4f8ec716beben%40googlegroups.com.

[M Roemer]

I am just getting into the APRS and digital modes, I don't understand what you mean by gates in my area. I thought using HF would make it so that I would be able to connect better. I live in northern Michigan so I do not have the APRS infrastructure that some people do. Also I attempted to use PAT and it indicated that it did not have a AX.25 socket I believe is what it said.

Thank you again for your assistance. 

Mark 

KF8EMO

[M Roemer]

Craig, I am trying to use the digipi with my baofeng AR-5RM, I have the AIOC connected but for some reason when I try to use the webchat it will stay keyed up. Can you please assist me with this issue.

Mark Roemer

KF8EMO

[Craig]

Hi Mark,

Lockup on first transmit is always RF on the cables.  Stuff to try, in
order of effectiveness:

1) add ferrite cores, multiple passes
2) relocate antenna, pi should not be broad side to antenna
3) add antenna counterpoise and/or core at feed point
4) reduce power
5) change length of USB/audio cables (anything but 19" or factor of 19")

You can confirm this by clicking SysLog and look for EMI errors, -19
audio errors.

cool,
-craig
KM6LYW