<html><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8"></head><body>The TCP-to-virtual-COM-port solution might be preferable, as Fldigi has the annoying habit of requiring you to "start" the listening KISS TCP socket, and then it will only accept one connection. So, if you lose the TCP connection to Fldigi for any reason, you have to open Fldigi's configuration dialog, unlock the I/O tab, stop the KISS port, start the KISS port again, and relock the I/O config.
<div><br></div><div>In my "copious free time" (yeah, right, with the honeydo list from my lovely XYL), I'm going to look into developing and submitting a proposed fix to Fldigi after I get the promised manual-only beaconing into YAAC.</div><div><br></div><div>Andrew, KA2DDO</div><div>author of YAAC</div><br><br>-------- Original message --------<br>From: "Iain R. Learmonth" <irl@hambsd.org> <br>Date: 5/10/20 13:20 (GMT-05:00) <br>To: aprssig@lists.tapr.org <br>Subject: Re: [aprssig] HF APRS igates on fldigi <br><br>Hi,<br><br>On 10/05/2020 17:07, Joe Della Barba wrote:<br>><br>> 1. Is there a missing piece I need between FLDIGI and YAAC or Xastir?<br>> It seems FLDIGI sets up a KISS TNC on 127.0.0.1 and the APRS programs<br>> are looking for a serial port? <br>><br>You need some software that supports KISS over TCP. Alternatively, you<br>can use socat to connect to the TCP port and then have it convert it to<br>a pty, which is a serial port as far as Xastir or YAAC would be concerned.<br><br>Thanks,<br><br>Iain MM0ROR.<br><br>-- <br>https://hambsd.org/<br><br><br>_______________________________________________<br>aprssig mailing list<br>aprssig@lists.tapr.org<br>http://lists.tapr.org/mailman/listinfo/aprssig_lists.tapr.org<br></body></html>