开云体育

Hi,

I'm? a new user to YAAC and I'm experiencing a strange problem where YAAC (version?1.0-beta157 running on Windows 10 Pro x64) will not receive?APRS-IS packets when a RF (AGWPE) port is enabled. When I first setup the program (gone through several cycles of using the -clear flag to try reinstall and finally figured it out how to replicate the issue) stations appear on my map, but they all eventually expire once I enable AGWPE. By disabling the AGWPE port, the APRS-IS packets start being received again.?The strange thing is YAAC is still sending data to?APRS-IS while the AGWPE port is enabled?as I can see my station updates on aprs.fi. Is this intended behavior or am I doing something wrong to show both RF and APRS-IS data on the map?

Thanks,

Mark

No, this is a feature designed to support the proper operation of the APRS-IS with the local RF channel. When you have both an RF port (AGWPE) and an APRS-IS port open, YAAC assumes (until you configure it otherwise) that you plan on running a normal Tx-I-gate. By default, the only packets sent to an APRS-IS client by the backbone are text message packets addressed to stations that the client has forwarded to the backbone, or position packets for stations that have just sent qualifying text messages, because that is all the client should be Tx-I-gating to RF. (Note the backbone does not understand the concept of a receive-only I-gate; it treats all clients the same).

If you want additional traffic from the APRS-IS backbone, you will have to specify an APRS-IS server filter expression on the APRS-IS port to have filter-matching extra traffic forwarded from the backbone. Note that YAAC implements the proper Tx-I-gate algorithms, so such extra traffic will not be sent on to the local RF channel unless you specify yet another filter for supplemental Tx I-gate transmissions (highly _not_ recommended).

For the convenience of new users, when YAAC is configured with _only_ an APRS-IS port (no RF ports), if and only if the user doesn't specify an explicit APRS-IS server filter expression on the port, a default filter expression (a range of 100 kilometers around the beacon fixed latitude and longitude position) is implicitly created so the user will see some traffic. This default filter is _not_ implicitly used if you have an RF port. And if you have an explicit filter expression, the default filter is not added to it.

Hope this helps explain the "drop" in Internet traffic since you hooked up your radio.

Andrew, KA2DDO
author of YAAC
________________________________________
From: [email protected] <[email protected]> on behalf of Mark via groups.io
Sent: Thursday, October 1, 2020 12:24 PM
To: [email protected]
Subject: [yaac-users] APRS-IS packets not received when RF/AGWPE port enabled

Hi,

I'm a new user to YAAC and I'm experiencing a strange problem where YAAC (version 1.0-beta157 running on Windows 10 Pro x64) will not receive APRS-IS packets when a RF (AGWPE) port is enabled. When I first setup the program (gone through several cycles of using the -clear flag to try reinstall and finally figured it out how to replicate the issue) stations appear on my map, but they all eventually expire once I enable AGWPE. By disabling the AGWPE port, the APRS-IS packets start being received again. The strange thing is YAAC is still sending data to APRS-IS while the AGWPE port is enabled as I can see my station updates on aprs.fi. Is this intended behavior or am I doing something wrong to show both RF and APRS-IS data on the map?

Thanks,

Mark

Andrew,

Thank you for the clear explanation! I knew I was missing something. :-)

I have the filter configured on the APRS-IS port and now it's working the way I want.

73, Mark