开云体育

Ah, good, you found out about Fldigi having to be _configured_ for KISS operation before I could tell you. Too bad Fldigi doesn't remember that between runs.

The problem with saving is that YAAC disconnects and reopens the connection with the updated configuration, but Fldigi switches back to ARQ mode when the KISS connection is closed.

No disrespect intended, but I'm not sure exactly what W1HKJ intended KISS connections to Fldigi to be used for. We may need to work with him to harden up the KISS API to Fldigi if it is going to be used operationally.

Andrew, KA2DDO
author of YAAC

________________________________________
From: [email protected] <[email protected]> on behalf of KH6CP Craig Paul <carcarx@...>
Sent: Monday, September 25, 2023 8:18 PM
To: [email protected]
Subject: [yaac-users] Solution: HF/FLDIGI “backhaul"

Turns out the KISS-over-TCP port in FLDIGI is not enabled by default.
Also, UDP is the default and had to be overridden.

Once that was taken care of the modems showed up in the YAAC port.
A modem is selected and gets passed to FLDIGI just fine.
I even see a YAAC "home" station beacon being transmitted by FLDIGI.
However if I try to save the modem information set in the YAAC port
Java throws an exception claiming that the TCP port refuses the connection, even
though the connection had functioned.

And FLDIGI will not normally terminate, but has to be forced to close
even after everything that's connected to FLDIGI has been shut down.

Craig/KH6CP

On Sun, Sep 24, 2023 at 2:58?PM KH6CP Craig Paul via groups.io<> <carcarx@...<mailto:[email protected]>> wrote:
Hi, Andrew,

I invoked FLDIGI 4.2.00 and, upon start-up of YAAC saw that, on port 7342, the connection was refused.
I checked the WIn 11 Firewall and local networks were enabled.

Next, as Administrator I got the command shell and invoked

netstat -ab | more

FLDIGI was listening on port 7362 and 7322.