Re: Blocking a digipeater from digi'ing my beacon
toggle quoted messageShow quoted text
“There is also a problem of not using WIDE1-1. In Northern California, a majority of the digipeaters do not respond to anything more than WIDE1-1, So if your mobile has a path of WIDE2-1, you will get very few of your position reports ever being heard.”
That is an improperly configured digipeater. Yes, in areas with mountain digis and large populations, those digis can greatly reduce congestion by being configured to 1 hop only. But they shoud do that by simply adding WIDE1-1, WIDE2-1, WIDE2-2 as unique calls in the UIDIGI list. In that list each of those is not ttreated as a WIDEn-N process, but simply as a unique call. There fore it is digipeated once, and marked as use. Thus they all go one hop and one hop only. Not repeated again by any lower more local digis.
If the digis are not properly configured, then fix the digis. There is a section on 1-hop digis on the main APRS guidance page http://aprs.org/fix14439.html
On October 24, 2019 at 12:39 PM James Ewen <ve6srv@...> wrote:
And to clarify another point, no fixed station should be using WIDE1-1 as a hop request.
WIDE1-1 is intended to be used as a request from low powered stations for an extra helping hand from home stations to get heard by the main digipeaters (if required).
Improper use of WIDE1-1 as a first hop request by high powered stations such as mobiles and home stations causes excessive local digipeats by home stations, and possible dupes by main digipeaters.
People using WIDE1-1 improperly can make others attempting to act on WIDE1-1 to improve the digipeater network shut down their home WIDE1-1 digipeaters because of abuse and interference, thereby ruining the network for all.
All digipeaters *should* respond to their assigned callsign/alias if implemented properly.
Furthermore, if you are attempting to observe whether the RF network is working properly, you should observe the activity of the RF network directly by looking at what you can hear/see on the RF network.
Don’t attempt to observe the RF network by looking at what you can see on APRS-IS connected sites like APRS.fi or other online sites. The data available there is heavily filtered, and provides only a minor portion of the information available.
Listen to and observe the packets being delivered by the RF network. If you are trying to observe operation of a digipeater outside of your local reception range, you can set a path that will go out to the far digipeater and back. If you hear the packet come back, then it was successfully handled by the digipeaters in the used portion of the digi path segment of the packet.
Note that the APRS network is unconnected, and may not always deliver your packets successfully. Also most APRS networks are heavily overloaded and cannot reliably handle the normal day to day traffic on them. Also long paths are not recommended for normal use as it causes heavy network loads, leading to that heavy network load that makes the networks unreliable.
Having said all that, yes, you can do things to test and observe exactly what you want to do.
Join APRSISCE@groups.io to automatically receive all group messages.