[aprssig] WIDEn-N question
Frank or Barbara Rossi
n3flr at bellatlantic.net
Wed Nov 4 00:25:17 CST 2009
In Western PA I encourage DIGI operators to not to respond to WIDE3 or
The WIDE3 DIGI by rights should be a long haul DIGI, maybe connecting
cities on 2 sides of a Mountain.
That may be useful in the remote wide open spaces from a mountain top,
but in WPA it is not necessary.
I also encourage the Big DIGI's not to respond to WIDE1, because they
will pick up the WIDE2.
Responding to both, the Big DIGI transmits twice.
I also encourage Fill In DIGI to just respond to WIDE1-1.
I recommend WIDE1-1,WIDE2-2 for mobiles in WPA.
For the amount of APRS traffic and the terrain of this area, those work
Around here you don't want your packets to go more than 50 60 miles.
3 total hops in all directions around here will get you into 2 or 3 I-GATES.
From Westmoreland County Pa I should not see any packets from Ohio or
I will see some West Virgina.
N3FLR - Frank
On 11/3/2009 1:24 PM, Lynn W. Deffenbaugh (Mr) wrote:
> Steve Noskowicz wrote:
> No. At least, not how I understand it. The n in WIDEn-N tells what
> level of Digi should be triggered by that path component. The N says
> how many hops of that type of digi you want the packet to traverse.
> WIDE1-1,WIDE2-1 says to first digi via a fill-in and then do at most
> one more hop via the higher WIDE2 digis. This is the "recommended"
> setting for most areas of the United States and other places.
> WIDE1-1,WIDE2-2 says the same thing but to take up to 2 hops via the
> higher WIDE2 digis. This is useful if you'll be driving out in the
> boondocks where the IGates may be fewer and further between.
> Fill-in (local) digis are supposed to be configured to only digi on a
> WIDE1 that has not been consumed. For instance, a WIDE1-1, but NOT a
> Higher digis are configured to act on WIDE1 as well as WIDE2, WIDE3,
> and sometimes higher n values. However, some digis will truncate
> higher values of n to 2 or 3 and other digis will completely ignore
> any values higher than 3.
> If you want to infer how many hops were originally requested, you're
> own your own. If you want to count how many hops a packet took, you
> can guess by counting the digi call signs prior to the path marked
> used, but not all digis insert their calls, so again, you're still
> In other words, the path is for the packet originator to make a
> request of the network, but the network doesn't have to honor that
> path and (unfortunately) doesn't always even trace what actions were
> taken on the packet's behalf.
> Lynn (D) - KJ4ERJ - Just my understanding, let's see how I did....
More information about the aprssig