[aprssig] PATH clarification when travelling

Cap Pennell cap at cruzio.com
Fri Jul 29 14:53:09 CDT 2005

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.
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.
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
There's good understandable up-to-date settings advice for digiowners and
other APRS users at http://nwaprs.org
73, Cap
  -----Original Message-----
  From: aprssig-bounces at lists.tapr.org
[mailto:aprssig-bounces at lists.tapr.org]On Behalf Of Brad [VE3BSM]
  Sent: Friday, July 29, 2005 12:23 PM
  To: 'TAPR APRS Mailing List'
  Subject: RE: [aprssig] PATH clarification when travelling

  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.

  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.

  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. :-(

  From: aprssig-bounces at lists.tapr.org
[mailto:aprssig-bounces at lists.tapr.org] On Behalf Of Cap Pennell
  Sent: Friday, July 29, 2005 3:13 PM
  To: TAPR APRS Mailing List
  Subject: RE: [aprssig] PATH clarification when travelling

  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.
  73, Cap KE6AFE
    -----Original Message-----
    From: aprssig-bounces at lists.tapr.org
[mailto:aprssig-bounces at lists.tapr.org]On Behalf Of Brad Smith
    Sent: Friday, July 29, 2005 10:43 AM
    To: 'TAPR APRS Mailing List'
    Subject: [aprssig] PATH clarification when travelling

    [Apologies if this gets posted twice...]

    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.

    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).

    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?

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.tapr.org/pipermail/aprssig/attachments/20050729/aeeb978c/attachment.html>

More information about the aprssig mailing list