On 5/9/2022 8:50 PM, Patrick wrote:
I don't want to be that guy that just PLOPS in a gateway and say, "oh look at me, I have a gateway, come one, come all, look at me (waving hands)" that does nothing more than cause problems and clogs the network. I want to be the guy of which people are grateful to have on their network that doesn't cause problems and quietly sits in the background.
If the iGate is mostly just receiving, RF -> APRS-IS, it won't cause a problem
or clog the network (RF network). It's a receiver. I'd be surprised if there's an
issue at the APRS-IS side with the incremental traffic from this iGate.
I don't know what your TX rules are, but as long as your iGate doesn't
transmit, it's not impacting the RF network anyway.
My ping times to noam.aprs2.net is about 83ms.
It doesn't sound like your network performance is a significant factor.
For comparison, my Comcast cable ping time to noam.aprs2.net is ~75mS,
of which the majority (~60mS) is at Level3 in Toronto.
My iGate is set for IDing every 10 minutes as well via morse and APRS WIDE1-1. No point in broadcasting throughout the whole network, that would be unnecessary traffic.
Does the iGate ID every 10 minutes even when it has not transmitted in the last 10 minutes?
For a fixed-location APRS node, you needn't? beacon often, perhaps every 30 minutes.
Also, why Morse ID? That isn't required at all and does create interference to the channel.
I'd suggest turning that off unless you have a specific reason to do it.
73,
Dana
