Re: [tracker2] Scripting Engine in OT2
- On Sat, Jun 14, 2008 at 12:38 PM, Tony Komljanec <tkomljan@...> wrote:
> Using the OT2 as a digi, In this example, the application isOne minor point... a digipeater should never send packets out via a
> to send a beacon via WIDE1-1 while alternating beacons go LOCAL (no hops, no
> igate). Digi default is WIDE1-1.
path of WIDE1-1.
By definition, a digipeater should be set up in a location that
provides good coverage. WIDE1-1 should be used by low powered stations
that need assistance to get into the local network from the fill-in
digipeaters located at home stations in areas that may be shadowed
from the main digipeaters.
A single hop path from a digipeater should be WIDE2-1. It is
detrimental to the network to have a high level digipeater ask all the
low level fill-in digipeaters to digipeat packets it has originated.
The fill-in digipeaters in range of the high level digipeater should
all be subsets of the high level digipeater, and you are wasting APRS