<!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:jmm@jwmoen.com">jmm@jwmoen.com</a> wrote:
<blockquote cite="mid000b01c5511a$511ef4f0$0200a8c0@mtc1" type="cite">
<meta http-equiv="Content-Type" content="text/html; ">
<meta content="MSHTML 6.00.2900.2627" name="GENERATOR">
<style></style>
<div><font face="Arial" size="2">This question will demonstrate my
lack of knowledge, but I know I need some education. I am a user of
APRS and don't run a digipeater. I have a Kenwood D700 and GPS in my
car and have successfully used the path RELAY,WIDE2-2. I got an APRS
message suggesting RELAY was obsolete, so I searched the archives of
this list. Here is what (I think) I learned:</font></div>
<div> </div>
<div><font face="Arial" size="2"> </font></div>
<br>
<div> </div>
<div><font face="Arial" size="2">Here's where I'm going to show my
ignorance. I changed the path to APRS, WIDE2-2. Not only would the
local digipeater not repeat me, but when I drove close to other
digipeaters that repeated me with my old path, those stopped repeating
me with the new path.</font></div>
<div> </div>
<div><font face="Arial" size="2">So I changed it to WIDE1-1,WIDE2-2.
Now it looks like all digipeaters that hear me, including W6CX-3, will
now repeat my location. </font></div>
<div> </div>
<div><font face="Arial" size="2">My dumb question: is
WIDE1-1,WIDE2-2 an OK path, and if not, what do you experts recommend
for my relatively densely populated location?</font> </div>
<div> </div>
<div><font face="Arial" size="2"> </font></div>
</blockquote>
<br>
The first hop (WIDE1-1) is the replacement for the now-obsolete
"RELAY"; i.e. requesting a nearby home station to digipeat your first
hop into the network. In California, the WIDEs are mostly situated on
high mountaintops 1000's of feet above the users. Normally, no RELAY
or equivalent is required to reach a WIDE here. Users can easily hit
mountain top WIDE digis directly almost anywhere in California. The
optimum path would be simply WIDE2-2 or WIDE3-3 . <br>
<br>
"APRS" is the destination (not part of the path) and will accomplish
nothing by being placed in the path, except to prevent you from getting
digipeated at all since no digi is going to respond to the alias "APRS"
as a digipeat hop rather than a destination. <br>
<br>
There is some confusion about this due to the quirky way the UI-View
program has the user enter both the destination address AND the path
into a single setup field in the program. This is an idiosyncracy of
UI-View; all other programs and hardware devices (TinyTrak, D700, etc)
have separate fields or menu entries for the PATH and the UNPROTO
destination.<br>
<br>
[ The destination address is a quasi-callsign that normally begins with
AP and can have up to 4 other characters after AP. Normally, a three
or four letter code indicating the program & version, or particular
model hardware is appended to AP. Your Kenwood should be sending
something like "APK001" as the "UNPROTO Address". If this destination
doesn't begin with AP, most APRS programs and APRS digipeaters will
ignore the packet. This convention was established in the early days
of APRS when it was often operated on channels shared with traditional
connected packet. The APxxxx "destination" provided an easy way to
ignore other packet activity on the channel. ]<br>
<br>
<br>
<br>
<br>
Stephen H. Smith wa8lmf (at) aol.com <br>
<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>
<br>
</body>
</html>