?

Hi, Joe.

After much tearing of hair and taking the names of several famous mathematicians in vain :-) I have found a new algorithm for the map importer that fixes your issues on Lake Ontario (and several other places). I'm still resolving some corner cases for Lake Superior and Lake Michigan, but I hope to have them fixed as well in a few days. It's just painful that it takes 20 hours (!) to run the entire planet OSM dataset through the importer so I can check the results. I fixed most of the Lake Ontario issues using a map data excerpt for just the lake and its immediate surrounds, but even that took an hour per run.

Andrew, KA2DDO

I'll always be a YAAC enthusiast, but for a remote wx station I'll probably use aprx on a pi zero.? By copying the weather format from YAAC I've got it sending positionless weather packets and using the digipeater symbol.??

It has a weather packet every ten minutes and a position packet every 30 minutes.

So there is no reason (that I can see) that YAAC has to immediately send the weather packet following the position packet. It appears that any reasonable delay is possible.

Il giorno 22 apr 2020, alle ore 18:48, Andrew P. <andrewemt@...> ha scritto:

Again, the reason you're not seeing the iPhone in YAAC is that:

1. No I-gate station (including yourself) is going to transmit it to RF because the iPhone isn't sending any packets meeting rule#1 or rule#2 (position _after_ a rule#1 text message).

2. The APRS-IS backbone won't send it to your local station because of the same rules, since you are not specifying a filter to cause additional packets to be forwarded that don't meet rule#1 and rule#2.

Basically, if you want to monitor traffic on the APRS-IS (instead of just being a minimal-traffic I-gate), you have to specify a APRS-IS port filter expression to include the additional traffic. Note that YAAC does implement the I-gate rules, so it won't forward to RF unnecessary extra Internet traffic caused by filters unless you also specify a supplemental Tx I-gate filter.

Andrew, KA2DDO
author of YAAC

________________________________________
From: [email protected] <[email protected]> on behalf of Elia Origoni <elia.origoni@...>
Sent: Wednesday, April 22, 2020 12:17 PM
To: [email protected]
Subject: Re: [yaac-users] No mobile APRS in YAAC

Hi,
Is a digipiter plus I-Gate configured in wide1-1.
I have the pi-tnc interface and APRS-IS interface.
I don’t want to repeat my smartphone beacon trough RF.
I only want to understand why I don’t see the beacon icon of my smartphone on the map in YAAC…with all filter disabled, I don’t have to see the same things that I can see on aprs.fi<>?

Elia, IU2JWM

Il giorno 22 apr 2020, alle ore 14:59, Andrew P. <andrewemt@...<mailto:andrewemt@...>> ha scritto:

First off, is your digipeater a digipeater-plus-I-gate, or just a digipeater? Since your iPhone is not a transmitter on ham bands, the only way your Internet-originated APRS packets are going to get to amateur-band RF is via somebody's transmit-capable I-gate. If you don't have a transmit-capable I-gate in the neighborhood, no one is going to put your Internet packets on RF.

Secondly, I-gates (and the APRS-IS backbone servers) have some logic within them to keep from flooding the local RF channel with excess traffic. Unless explicitly configured otherwise at the I-gate, traffic will not be sent from the Internet to the I-gate for retransmission on RF unless:

1. the APRS packet is a text message addressed to an RF station reported to the backbone as being heard by that particular I-gate.
2. the APRS packet is a position report from an Internet-relayed station that has just sent a text message meeting rule#1 (so the text message recipient can see where the message sender is located).

This is what keeps transmit-capable I-gates from saturating the RF channel with spurious traffic.

And the APRS-IS does not know that a connected station is _not_ an I-gate. If it is connected to APRS-IS, then it will be treated like an I-gate, and therefore the rules for sending traffic to an I-gate apply in every backbone server. Traffic is only forwarded to the connected station if rule#1, rule#2, or an explicit filter specification would pass the traffic. And a proper I-gate should enforce the rules too, in case somebody floods the APRS-IS with spurious traffic, or a filter is specified on the connection to APRS-IS. This is why YAAC has the supplemental filter to force additional traffic to RF (above and beyond rule#1 and rule#2 traffic); this capability should be used very carefully and cautiously, as the the RF channel doesn't have much bandwidth.

So, send more than just a beacon from your iPhone. Remember, one of the fundamental regulations of amateur radio is that it is two-way communications. Telemetry is an allowed but secondary purpose of amateur radio.

Andrew, KA2DDO
author of YAAC

Il giorno 22 apr 2020, alle ore 14:59, Andrew P. <andrewemt@...> ha scritto:

First off, is your digipeater a digipeater-plus-I-gate, or just a digipeater? Since your iPhone is not a transmitter on ham bands, the only way your Internet-originated APRS packets are going to get to amateur-band RF is via somebody's transmit-capable I-gate. If you don't have a transmit-capable I-gate in the neighborhood, no one is going to put your Internet packets on RF.

Secondly, I-gates (and the APRS-IS backbone servers) have some logic within them to keep from flooding the local RF channel with excess traffic. Unless explicitly configured otherwise at the I-gate, traffic will not be sent from the Internet to the I-gate for retransmission on RF unless:

1. the APRS packet is a text message addressed to an RF station reported to the backbone as being heard by that particular I-gate.
2. the APRS packet is a position report from an Internet-relayed station that has just sent a text message meeting rule#1 (so the text message recipient can see where the message sender is located).

This is what keeps transmit-capable I-gates from saturating the RF channel with spurious traffic.

And the APRS-IS does not know that a connected station is _not_ an I-gate. If it is connected to APRS-IS, then it will be treated like an I-gate, and therefore the rules for sending traffic to an I-gate apply in every backbone server. Traffic is only forwarded to the connected station if rule#1, rule#2, or an explicit filter specification would pass the traffic. And a proper I-gate should enforce the rules too, in case somebody floods the APRS-IS with spurious traffic, or a filter is specified on the connection to APRS-IS. This is why YAAC has the supplemental filter to force additional traffic to RF (above and beyond rule#1 and rule#2 traffic); this capability should be used very carefully and cautiously, as the the RF channel doesn't have much bandwidth.

So, send more than just a beacon from your iPhone. Remember, one of the fundamental regulations of amateur radio is that it is two-way communications. Telemetry is an allowed but secondary purpose of amateur radio.

Andrew, KA2DDO
author of YAAC