<html><body><div style="color:#000; background-color:#fff; font-family:Courier New, courier, monaco, monospace, sans-serif;font-size:10pt"><div><span>Also remember that not all digi's work the same. For example APRX has a setting "directonly" so it doesn't matter if wide1-1 is used or not. If your heard direct then you'll get digied. I'm not saying if its right or wrong, just different.</span></div><div><span></span> </div><div><span>Max KG4PID</span></div><div><br></div> <div style="font-family: Courier New, courier, monaco, monospace, sans-serif; font-size: 10pt;"> <div style="font-family: times new roman, new york, times, serif; font-size: 12pt;"> <div dir="ltr"> <font size="2" face="Arial"> <div style="margin: 5px 0px; padding: 0px; border: 1px solid rgb(204, 204, 204); height: 0px; line-height: 0; font-size: 0px;" class="hr" contentEditable="false" readonly="true"></div> <b><span style="font-weight: bold;">From:</span></b> Stephen H.
Smith <wa8lmf2@aol.com><br> <b><span style="font-weight: bold;">To:</span></b> TAPR APRS Mailing List <aprssig@tapr.org> <br> <b><span style="font-weight: bold;">Sent:</span></b> Tuesday, February 19, 2013 1:19 PM<br> <b><span style="font-weight: bold;">Subject:</span></b> Re: [aprssig] WB2PAY email RXCD, CFG file sent...<br> </font> </div> <br>
<div id="yiv1973532499">
<div>
<div class="yiv1973532499moz-cite-prefix">On 2/19/2013 12:14 PM, Steve Noskowicz
wrote:<br>
</div>
<blockquote type="cite">
<pre>Very well explained, Stephen, as usual. I hope my Beginner Guide does as well.
and...Yes. My understanding is that Matthew actually has it backwards. In the boonies you want the WIDE1-1 to insure you reach the ocassional fill-in Digi. With only WIDE2-1 any fill-in is mute and you are "invisible" when only covered by it.
73, Steve, K9DCI USN (Vet) MOT (Ret) Ham (Yet)
Up to date APRS Beginner Guide - updated Oct-2011
http://K9DCI.home.comcast.net
Click 'APRS Beginner INFO' under Contact
</pre>
</blockquote>
<br>
<br>
1) Well, I DID invent the "double WIDEn-N" construct over a
decade ago as a solution to get around the limitations of the
brain-dead dupe suppression algorithms of KPC3 TNCs (only suppress
dupes on WIDEn-N paths but not on plain WIDE) used as digis.
While, at the same time, allowing home users to use hand-me-down
junker-clunker non-WIDEn-N non-APRS aware TNCs as home digis. <br>
<br>
2) I might add that the ONE place in the country where a straight
WIDE2-2 <b>is</b> encouraged and used is the desert southwest and
Southern California coastal regions. <br>
<br>
Due to all the populated areas of SoCal from Santa Barbara all the
way to Ensenada, Mexico and inland to Las Vegas and Phoenix, being
rimmed with digis on 4-5-6-thousand-foot mountain tops, there is
absolutely no need for home fill-ins. Indeed they are actively
discouraged, since virtually everyone everywhere can effortlessly
hit mountain top "SUPER-WIDES" directly. <br>
<br>
Home fill-ins using the usual WIDE1-1,WIDE2-1 path scheme would
merely occupy an additional time slot while hitting EVEN MORE
mountain-top "super-wides" simultaneously on the second hop. In
the greater L.A. area, digis are set to consume WIDE2-2 in a single
hop, but you still typically hear two or three mountain tops
responding simultaneously on any beacon in the Greater L.A. area
(i.e. Ventura-Riverside-San Bernardino-San Diego) on the first hop.
<br>
<br>
When you leave greater SoCal and head over the 4400' mountain pass
known as "the Grapevine" on I-5 headed towards central CA and SFO
--or-- through the 4400' Cajon pass on I-15 toward Las Vegas --or--
east on I-10 or I-40 towards Arizona, mountain top digis outside the
metro L.A. area (and it's massive congestion) process the same
WIDE2-2 setting normally to yield two hops. Again, low-level
WIDE1-1 fill-ins are simply not required due to the unique terrain
of flat lands rimmed by multi-thousands-of-feet-higher mountains--
they just add needless congestion. <br>
<br>
This arrangement works well, but DOES force the user to reset his
equipment configuration back to the usual WIDE1-1,WIDE2-1 path when
when leaving the US southwest for the rest of the country. On my
annual treks back-and-forth from the midwestern flatlands to SoCal,
I find this switch needs to be made when you come out of the front
range of the Rockies onto the high plains of eastern Colorado or New
Mexico. Of course for me using a mobile laptop APRS setup, it's a
trivial setting change.<br>
<br>
<br>
<div style="margin: 5px 0px; padding: 0px; border: 1px solid rgb(204, 204, 204); height: 0px; line-height: 0; font-size: 0px;" class="hr" contentEditable="false" readonly="true"></div><br>
--<br>
<br>
Stephen H. Smith wa8lmf (at) <a href="http://aol.com/" target="_blank">aol.com</a> <br>
Skype: WA8LMF<br>
Home Page: http://wa8lmf.net<br>
<br>
High Performance Sound Systems for Soundcard Apps<br>
http://wa8lmf.net/ham/imic.htm<br>
http://wa8lmf.net/ham/uca202.htm<br>
<br>
Vista & Win7 Install Issues for UI-View and Precision Mapping<br>
http://wa8lmf.net/aprs/UIview_Notes.htm#VistaWin7<br>
<br>
"APRS 101" Explanation of APRS Path Selection & Digipeating <br>
http://wa8lmf.net/DigiPaths <br>
<br>
<br>
<br>
</div>
</div><br>_______________________________________________<br>aprssig mailing list<br><a href="mailto:aprssig@tapr.org" ymailto="mailto:aprssig@tapr.org">aprssig@tapr.org</a><br><a href="http://www.tapr.org/mailman/listinfo/aprssig" target="_blank">http://www.tapr.org/mailman/listinfo/aprssig</a><br><br><br> </div> </div> </div></body></html>