<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META http-equiv=Content-Type content="text/html; charset=us-ascii">
<META content="MSHTML 6.00.2900.2668" name=GENERATOR></HEAD>
<BODY>
<DIV><FONT face=Arial color=#0000ff size=2><SPAN class=433242619-29072005>Yes
that's correct up to a point, but in the interim while some old digiowners are
not yet providing modern service, plain WIDE2-2 is often the _best compromise_
for users, even mobile. For routine use, it's more considerate of all the
other users than any 3-hop path, and it often works better than you might
think before actually trying it. </SPAN></FONT></DIV>
<DIV><FONT face=Arial color=#0000ff size=2><SPAN class=433242619-29072005>With
antique digis in play, unfortunately the modern WIDE1-1,WIDE2-1 path for mobiles
will only go out over one digi hop, and therefore is less likely to be seen over
a very broad area and by an IGate. The main advantage of using plain
WIDE2-2 for now is it works over 2 hops with both modern and antique digis,
covering a very broad area on VHF and quite likely reaching an IGate
too. </SPAN></FONT></DIV>
<DIV><FONT face=Arial color=#0000ff size=2><SPAN class=433242619-29072005>Of
course the best solution is for all stations to update their settings to the new
n-N paradigm. That would be courteous to the other hams trying to
use VHF APRS.</SPAN></FONT></DIV>
<DIV><FONT face=Arial color=#0000ff size=2><SPAN
class=433242619-29072005>There's good understandable up-to-date settings advice
for digiowners and other APRS users at <A
href="http://nwaprs.org">http://nwaprs.org</A> </SPAN></FONT></DIV>
<DIV><FONT face=Arial color=#0000ff size=2><SPAN
class=433242619-29072005></SPAN></FONT><FONT face=Arial color=#0000ff
size=2><SPAN class=433242619-29072005>73, Cap </SPAN></FONT></DIV>
<BLOCKQUOTE dir=ltr
style="PADDING-LEFT: 5px; MARGIN-LEFT: 5px; BORDER-LEFT: #0000ff 2px solid; MARGIN-RIGHT: 0px">
<DIV class=OutlookMessageHeader dir=ltr align=left><FONT face=Tahoma
size=2>-----Original Message-----<BR><B>From:</B>
aprssig-bounces@lists.tapr.org [mailto:aprssig-bounces@lists.tapr.org]<B>On
Behalf Of </B>Brad [VE3BSM]<BR><B>Sent:</B> Friday, July 29, 2005 12:23
PM<BR><B>To:</B> 'TAPR APRS Mailing List'<BR><B>Subject:</B> RE: [aprssig]
PATH clarification when travelling<BR><BR></FONT></DIV>
<DIV dir=ltr align=left><SPAN class=780131719-29072005><FONT face=Tahoma
size=2>My understanding is that "WIDE1-1,WIDE2-1" gets the best of both
worlds. If there are fill-in digis (previously RELAY) nearby, they'll respond
to the WIDE1-1 and forward to the nearest WIDE. If I'm in direct contact with
a WIDE, it too will handle WIDE1-1 directly.</FONT></SPAN></DIV>
<DIV dir=ltr align=left><SPAN class=780131719-29072005><FONT face=Tahoma
size=2></FONT></SPAN> </DIV>
<DIV dir=ltr align=left><SPAN class=780131719-29072005><FONT face=Tahoma
size=2>On the other hand, WIDE2-2 will *only* work if I'm within hearing
distance of a WIDE, and *no* fill-in digi will handle my
packet.</FONT></SPAN></DIV>
<DIV dir=ltr align=left><SPAN class=780131719-29072005><FONT face=Tahoma
size=2></FONT></SPAN> </DIV>
<DIV dir=ltr align=left><SPAN class=780131719-29072005><FONT face=Tahoma
size=2>For example, if you were in my general vicinity my own fill-in digi
would ignore you with WIDE2-2 only. And unless you're running a fair amount of
power you won't reach the next nearest WIDE directly, with the end result of
your packet going nowhere. :-(</FONT></SPAN></DIV><BR>
<DIV class=OutlookMessageHeader lang=en-us dir=ltr align=left>
<HR tabIndex=-1>
<FONT face=Tahoma size=2><B>From:</B> aprssig-bounces@lists.tapr.org
[mailto:aprssig-bounces@lists.tapr.org] <B>On Behalf Of </B>Cap
Pennell<BR><B>Sent:</B> Friday, July 29, 2005 3:13 PM<BR><B>To:</B> TAPR APRS
Mailing List<BR><B>Subject:</B> RE: [aprssig] PATH clarification when
travelling<BR></FONT><BR></DIV>
<DIV></DIV>
<DIV><FONT face=Arial color=#0000ff size=2><SPAN class=667545618-29072005>For
most users, including mobiles, the best solution to this problem is to set
plain WIDE2-2. Try it. Simply WIDE2-2 will work well and is
recommended for use both with the up-to-date new paradigm digis _and_ the
"unfortunately not yet updated" antique digis.</SPAN></FONT></DIV>
<DIV><FONT face=Arial color=#0000ff size=2><SPAN class=667545618-29072005>73,
Cap KE6AFE</SPAN></FONT></DIV>
<BLOCKQUOTE dir=ltr
style="PADDING-LEFT: 5px; MARGIN-LEFT: 5px; BORDER-LEFT: #0000ff 2px solid; MARGIN-RIGHT: 0px">
<DIV class=OutlookMessageHeader dir=ltr align=left><FONT face=Tahoma
size=2>-----Original Message-----<BR><B>From:</B>
aprssig-bounces@lists.tapr.org [mailto:aprssig-bounces@lists.tapr.org]<B>On
Behalf Of </B>Brad Smith<BR><B>Sent:</B> Friday, July 29, 2005 10:43
AM<BR><B>To:</B> 'TAPR APRS Mailing List'<BR><B>Subject:</B> [aprssig] PATH
clarification when travelling<BR><BR></FONT></DIV>
<DIV><SPAN class=816232117-29072005><FONT face=Tahoma size=2>[Apologies if
this gets posted twice...]</FONT></SPAN></DIV>
<DIV><SPAN class=816232117-29072005></SPAN> </DIV>
<DIV><SPAN class=816232117-29072005><FONT face=Tahoma size=2>Okay, I *think*
I'm pretty clear on the new paradigm, but there's one lingering question to
toss out. It involves a mobile taking a trip that'll involve travelling
through areas that have upgraded to the new paradigm, and some that
haven't.</FONT></SPAN></DIV>
<DIV><SPAN class=816232117-29072005><FONT face=Tahoma
size=2></FONT></SPAN> </DIV>
<DIV><SPAN class=816232117-29072005><FONT face=Tahoma size=2>If one were to
set the path to, say "RELAY,WIDE1-1,WIDE2-1", would that be the best
compromise? I'm well aware that stopping to change the path as you entered
each area would be ideal, but without adequate info (eg. a centralized
database) of what PATH works best in what areas, that's a tad difficult (not
to mention inconvenient in some cases).</FONT></SPAN></DIV>
<DIV><SPAN class=816232117-29072005><FONT face=Tahoma
size=2></FONT></SPAN> </DIV>
<DIV><SPAN class=816232117-29072005><FONT face=Tahoma size=2>Specifically,
if I'm in an area where RELAY has been discontinued, and a local digi hears
the above packet, will it just ignore the RELAY and deal with the WIDE1-1?
Or will the fact RELAY is in the packet cause the whole thing to be tossed
out?</FONT></SPAN></DIV>
<DIV><SPAN class=816232117-29072005><FONT face=Tahoma
size=2></FONT></SPAN> </DIV>
<DIV><SPAN class=816232117-29072005><FONT face=Tahoma
size=2>Brad.</FONT></SPAN></DIV></BLOCKQUOTE></BLOCKQUOTE></BODY></HTML>