[aprssig] A test for APRS in some lessor traveled Western areas

[Tom Smith]

My concern is the mountain top digis having internet access.
I'll do a test:  WIDE3-1 out and WIDE2-1 back in Nevada and Utah.
Tom Smith   KD6SOJ

----- Original Message ----- 
From: "Cap Pennell" <cap at cruzio.com>
To: "TAPR APRS Mailing List" <aprssig at lists.tapr.org>
Sent: 09/08/2007 10:21 AM
Subject: RE: [aprssig] A test for APRS in some lessor traveled Western areas


> You guys could _really_ benefit from _another_ careful read-through of
> http://web.ew.usna.edu/~bruninga/aprs/fix14439.html
> and the links from that page.
>
> Best bet: WIDE1-1,WIDE2-1 mobile; WIDE2-2 (or less) fixed or base.  Three
> (or more) hops in all directions is not the answer for courtesy, nor
rarely
> much help for vanity.
>
> In remote areas the trick is mostly getting packets from your station into
> _the first_ digi called for in your digipath.  Broader digipaths don't
help
> there.  Many areas are far less "remote" than a visitor's first impression
> might indicate.  High mountains often have digis on top providing access
> from a vast area.
>
> A fill-in digi only operates packets addressed to WIDE1-1.  The other
digis
> will operate packets addressed to WIDE1-1 or WIDE2-2 or WIDE2-1 or WIDE3-1
> (while inserting their callsign in the path's "history").  This is the
"New
> Paradigm", traceable WIDEn-N.  RELAY and WIDE and TRACE and TRACEn-N are
> completely obsolete (pass it on).
>
> Many digis will give only one hop to any WIDE3-N address (that is, WIDE3-3
> or WIDE3-2 or WIDE3-1).  They operate/digipeat the packet while adjusting
> the path so there will be no further hops ("trapping" the excess hops).
> Still, any modern high "S overlay" digi will give WIDE2-1 or WIDE3-1 (or
> WIDE1-1) the same one hop.
>
> Confused about any of this stuff at all?  Then use WIDE1-1,WIDE2-1 mobile;
> WIDE2-2 (or less) fixed or base.  Transmit only as frequently as your
> intended "audience" requires to fulfill their objectives.
>
> (And please don't even consider putting up any new digipeater at all until
> your confusion is all gone and you've had full discussions about the VHF
> network's _needs_ with all the operators of existing digipeaters in your
> network/region).
> 73, Cap KE6AFE
>