<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<meta content="text/html;charset=ISO-8859-1" http-equiv="Content-Type">
<title></title>
</head>
<body bgcolor="#ffffff" text="#000000">
<a class="moz-txt-link-abbreviated" href="mailto:smithb@bpsmicro.com">smithb@bpsmicro.com</a> wrote:
<blockquote cite="midSERVERFRaqbC8wSA1Xv00000005@bpsmicro.com" type="cite">
<meta http-equiv="Content-Type" content="text/html; ">
<meta content="MSHTML 6.00.2900.2668" name="GENERATOR">
<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"></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"></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"></span> </div>
<div><span class="816232117-29072005"><font face="Tahoma" size="2">Brad.</font></span></div>
</blockquote>
<br>
Packet paths are processed SEQUENTIALLY, not in parallel. The first
hop in the string MUST BE USED FIRST before any subsequent hops are
acted on. If RELAY doesn't get processed first, and marked as "used"
in the example above, you are not going to go anywhere! A full
discussion of this issue is on my website at:<br>
<a class="moz-txt-link-freetext" href="http://webs.lanset.com/wa8lmf/DigiPaths">http://webs.lanset.com/wa8lmf/DigiPaths</a> <br>
<br>
In the case of the D700, or a TinyTrack, alternate paths can be stored
in the device (5 in the case of the Kenwoods, 2 in the case of the
TinyTrack) and then selected as needed enroute. You might store a
path of "RELAY, WIDE, WIDE2-2" in one mode, and "WIDE2-2" or
"WIDE1-1, WIDE2-2" in the other. <br>
<br>
<br>
<br>
Stephen H. Smith wa8lmf (at) aol.com <br>
EchoLink Node: 14400 [Think bottom of the 2M band]<br>
Home Page: <a class="moz-txt-link-freetext" href="http://wa8lmf.com">http://wa8lmf.com</a><br>
<br>
New APRS Symbol Chart <br>
<a class="moz-txt-link-freetext" href="http://webs.lanset.com/wa8lmf/miscinfo/APRS_Symbol_Chart.pdf">http://webs.lanset.com/wa8lmf/miscinfo/APRS_Symbol_Chart.pdf</a> <br>
<br>
New/Updated "Rev G" APRS <a class="moz-txt-link-freetext" href="http://webs.lanset.com/wa8lmf/aprs">http://webs.lanset.com/wa8lmf/aprs</a><br>
Symbols Set for UI-View, <br>
UIpoint and APRSplus:<br>
<br>
<br>
<br>
<br>
</body>
</html>