[aprssig] Re: OLD vs NEW

[James]

Thanks for the reply and I understand it all but that didn't quite answer my 
question, then again maybe I am not asking it the right way.

If a digi with the old setup worked well with the standard paths, why would 
they not be working correctly now?
It just seems that I hear allot of talk on how things used to work but now 
it doesn't.

And you are right, we do not have many if any relay or wide1-1 digi's here 
due to the fact that we have excellent mountain top systems that over 95% of 
the state and have just the right overlap. So I guess we are spoiled.

Maybe I have it all wrong and I should go back to my corner.


----- Original Message ----- 
From: "Stephen H. Smith" <wa8lmf2 at aol.com>
To: "TAPR APRS Mailing List" <aprssig at lists.tapr.org>
Sent: Tuesday, May 02, 2006 2:09 PM
Subject: [aprssig] Re: OLD vs NEW


> kb7tbt at gmail.com wrote:
>> I have a question that maybe some of you would say is simply silly but I 
>> need
>> it answered, so lets see if you all can teach a old dog a new trick.
>>
>> As far as I understand the reasoning for the new WIDEn-n is to prevent 
>> the
>> abuse and packet flooding by ignorant 7-7's and so fourth.
>>
>
> Part of the new n-N is to trap abusive paths like WIDE7-7.
> The other part is address the fact that KPC3 TNCs  (used in a very large 
> percentage of all U.S. digipeaters) don't do dupe suppression on "RELAY" 
> or plain "WIDE" paths, but do on any kind of n-N path.
>
>> Now I have seen all this chatter about 1-1 and 1-2 and how digi's dont
>> understand it, my question is simply "why?"
>>
>
> The WIDE1-1 path is a replacement for the now-obsolute "RELAY" (which 
> KPC3s won't dupe supress) for home low-level fill-in digis.
>
>> For years now I have simply used WIDE2-2 on all my paths, 3 or 4 years 
>> ago I
>> went across country with the same path and it worked just fine with the
>> exception of the "dead" areas at the time.
>>
>
> By doing that you are depending solely on high-level wide-coverage "true 
> WIDEn-Ns" only,  and are bypassing the possible help from low-level home 
> fill-in digis.  In the west where WIDEn-N digis are  *REALLY*  wide on 
> mountains thousands of feet above the user,  this works well.
> In the flat lands of the midwest and east coast where "true WIDEn-Ns" are 
> typically only a few hundred feet above the user, the assistance of home 
> stations via WIDE1-1 can make a major difference.
>
> WIDE1-1 is compatible with either:  a home station as the first 
> hop, --or-- a true high-level WIDEn-N as the first hop.  [ The home 
> station is typically too stupid to properly decrement WIDE2-2 properly to 
> WIDE2-1.  Instead it would mark it as used, preventing any further digi 
> hops.  ]
>
> By using two WIDEn-N statements in series,  a "dumb" home station can 
> "eat" the first WIDE1-1 while leaving the following WIDE2-2 (or WIDE2-1) 
> part for subsequent true WIDEn-N digis to process normally.
>
>> So as I see it old or new setups should still accept the wide2-2 path, in
>> our state that is the basic recommended path other then AZ2-2 but of 
>> course
>> that's special to the state.
>>
>
> The whole history and rationale behind the new scheme is here on my 
> website:
>     "APRS 101"  Explanation of APRS Path Selection & Digipeating
>     http://webs.lanset.com/wa8lmf/DigiPaths
>
>
>
>
>
>
>
> Stephen H. Smith    wa8lmf (at) aol.com
> EchoLink Node:      14400    [Think bottom of the 2M band]
> Home Page:          http://wa8lmf.com
>
>
> NEW!   JavAPRS Filter Port 14580 Guide
>  http://webs.lanset.com/wa8lmf/aprs/JAVaprsFilters.htm
>
> UI-View Misc Notes and FAQ
>  http://webs.lanset.com/wa8lmf/aprs/UIview_Notes.htm
>
>
>
> Updated "Rev G" APRS            http://webs.lanset.com/wa8lmf/aprs
> Symbols Set for UI-View,
> UIpoint and APRSplus:
>
>
>
>
> _______________________________________________
> aprssig mailing list
> aprssig at lists.tapr.org
> https://lists.tapr.org/cgi-bin/mailman/listinfo/aprssig