[aprssig] WB2PAY email RXCD, CFG file sent...

Max Harper kg4pid at yahoo.com
Tue Feb 19 18:09:37 EST 2013

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.

 From: Stephen H. Smith <wa8lmf2 at aol.com>
To: TAPR APRS Mailing List <aprssig at tapr.org> 
Sent: Tuesday, February 19, 2013 1:19 PM
Subject: Re: [aprssig] WB2PAY email RXCD, CFG file sent...

On 2/19/2013 12:14 PM, Steve Noskowicz wrote:
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
Click 'APRS Beginner INFO' under Contact   

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.  

2)    I might add that the ONE place in the country where a straight
    WIDE2-2 is encouraged and used is the desert southwest and Southern California coastal regions.   

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.   

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.

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.    

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.



Stephen H. Smith    wa8lmf (at) aol.com 
Skype:        WA8LMF
Home Page:          http://wa8lmf.net

High Performance Sound Systems for Soundcard Apps
Vista & Win7 Install Issues for UI-View and Precision Mapping

"APRS 101"  Explanation of APRS Path Selection & Digipeating 

aprssig mailing list
aprssig at tapr.org
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.tapr.org/pipermail/aprssig_lists.tapr.org/attachments/20130219/1318b173/attachment.html>

More information about the aprssig mailing list