[aprssig] Bad Path
bruninga at usna.edu
Tue Aug 23 11:22:54 CDT 2005
Just curious. I guess this means that you are
running an old TAPR (T) digi that can only
do callsign substitution? Hence it cannot
handle any WIDEn-N?
Because any digi other than a PacComm can
handle the WIDE1-1,WID2-1 properly... and
it will work everywhere?
Just curious why it doesnt work in Lubbock?
>>> "kc5zrq" <kc5zrq at d-star.us> 08/23/05 11:43 AM >>>
In Lubbock, where it is extremely flat, we rarely have a
need for a fill-in digi. So our digis do not treat WIDE1-1
as if it was a fill-in digi. If someone sends
WIDE1-1,WIDE2-2, then they will be digid one time. Bad
paths like WIDE1-2,WIDE2-3 will also only hop one time.
Hopping one time while in Lubbock isn't so bad since you
will always get into the Internet gateway. If you are in
Lubbock and you want to get your signal on RF to get outside
of Lubbock you can use a path of WIDE3-3. This will let
your packets reliably reach digipeaters in Andrews and
Stonewall counties, some 75 to 90 miles away. WIDE3-3 will
probably also hit many other distant digipeaters during one
of the frequent VHF propagation enhancements.
This Email Was brought to you by
A Netwin Web Based EMail Client
aprssig mailing list
aprssig at lists.tapr.org
More information about the aprssig