开云体育

HF/FLDIGI “backhaul"

KH6CP Craig Paul All Messages By This Member #2096 Part of our radio "territory" consists of small islands with extinct volcanoes obstructing most VHF/UHF traffic. Experiments show that HF NVIS with faster modes (like Thor 56) would work, at least most of the time. I see that I can configure a KISS-over-TCP port pointing to FLDIGI's?localhost port 7342. How do I route the HF "backbone" traffic to my AGWPE port and vice versa? ---- (On the KISS port I see the "Radio of HF bands" check box and will? enable that and I would think WIDE1-1 would be proper. On the AWGPE?port at the "remote" site I'd want to continue the WIDE1-1 digipeating. Any recommendations as to further settings? Thanks! Craig/KH6CP
Andrew P. All Messages By This Member #2097 开云体育 Note that having more than one RF port in YAAC is basically setting up a cross-frequency digipeater. The only thing the HF checkbox does is change the assumed RF baud rate from 1200 baud to 300 baud for the port bandwidth monitor, and enable one digipeat hop for pathless HF packets to non-HF ports. So you still have to configure which digipeat aliases will be accepted by each port for outbound traffic. For example, continental HF digipeaters specify GATE as the only digipeat alias for the HF port, so the HF band isn't clogged with WIDE2-2 packets from a channel with 4 times the bandwidth. Note that not all Fldigi modems support binary KISS packets (especially ones like Olivia and Thor that expect the payload to be printable ASCII streams rather than packets). Use the modem choice menu in YAAC to ensure you only pick from the subset of Fldigi modems that support 8-bit binary packets. And, of course, stay in compliance with the outdated FCC rules regarding symbol rate. :-( And, like Direwolf, Fldigi has to be started in KISS mode before you open the YAAC port to it. And KISS mode disables being able to use any associated Fldigi programs using the ARQ protocol; you might not be able to use Flrig, for example. Hope this helps. Andrew, KA2DDO author of YAAC? From: [email protected] <[email protected]> on behalf of KH6CP Craig Paul <carcarx@...> Sent: Saturday, September 23, 2023 8:05:43 PM Part of our radio "territory" consists of small islands with extinct volcanoes obstructing most VHF/UHF traffic. Experiments show that HF NVIS with faster modes (like Thor 56) would work, at least most of the time. I see that I can configure a KISS-over-TCP port pointing to FLDIGI's?localhost port 7342. How do I route the HF "backbone" traffic to my AGWPE port and vice versa? ---- (On the KISS port I see the "Radio of HF bands" check box and will? enable that and I would think WIDE1-1 would be proper. On the AWGPE?port at the "remote" site I'd want to continue the WIDE1-1 digipeating. Any recommendations as to further settings? Thanks! Craig/KH6CP
KH6CP Craig Paul All Messages By This Member #2098 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. I got into YAAC and changed the? TCP port for KISS-over-TCP to 7362, saved the config, exited?YAAC, reinvoked?it, and saw that there was no refused connection. However there was no modem listing for the KISS-over-TCP port. I then changed the KISS-over-TCP port to 7322, saved the config, existed YACC, rebooted Win 11, started FLDIGI then started YAAC. Still no FLDIGI modem list for the KISS-over-TCP port. What other info do you need to help diagnose this? Thanks! Craig/KH6CP toggle quoted message Show quoted text On Sat, Sep 23, 2023 at 2:05?PM <carcarx@...> wrote: I see that I can configure a KISS-over-TCP port pointing to FLDIGI's?localhost port 7342.

Previous Topic Next Topic