Order Tray | Contact Us | Home | SIG Lists

[aprssig] PATH clarification when travelling

Cap Pennell cap at cruzio.com
Fri Jul 29 19:13:07 UTC 2005

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://www.tapr.org/pipermail/aprssig/attachments/20050729/6a530e9f/attachment.htm 

More information about the aprssig mailing list