[aprssig] RE: New EU Paradigm also Uiview32 and New-N for the USA

[Ron Stordahl]

Cap

The reply from John indicated that there might be some significant re 
duplicate checking, which I indicated I didn't understand.  Perhaps I 
should not have been to quick to make a change.  If you see no issue 
here regarding duplicating checking I will admit I would rather have the 
WideN-1 'literals' in the list as I initially did.

Ron, N5IN

Cap Pennell wrote:
> The only thing about taking out those ?-1 aliases is then they're left as
> artifacts in the path history indicating the original excessive path.
> WIDE7-1 becomes N5IN-4*,WIDE7 instead of being "disappeared" completely like
> when they're included in the ALIAS= where then WIDE7-1 becomes only N5IN-4*
> .
>
> A N5IN-4 "W2,MNn" digi could use either
> (?-1's left out)
> ALIAS=N5IN-4,WIDE7-7,WIDE7-6,WIDE7-5,WIDE7-4,WIDE7-3,WIDE7-2,WIDE6-6,WIDE6-5
> ,WIDE6-4,WIDE6-3,WIDE6-2,WIDE5-5,WIDE5-4,WIDE5-3,WIDE5-2,WIDE4-4,WIDE4-3,WID
> E4-2,,WIDE3-3,WIDE3-2
> or
> (?-1's left in)
> ALIAS=N5IN-4,WIDE7-7,WIDE7-6,WIDE7-5,WIDE7-4,WIDE7-3,WIDE7-2,WIDE7-1,WIDE6-6
> ,WIDE6-5,WIDE6-4,WIDE6-3,WIDE6-2,WIDE6-1,WIDE5-5,WIDE5-4,WIDE5-3,WIDE5-2,WID
> E5-1,WIDE4-4,WIDE4-3,WIDE4-2,WIDE4-1,WIDE3-3,WIDE3-2,WIDE3-1
>
> hi hi
> 73, Cap
>
>
>   
>> -----Original Message-----
>> From: aprssig-bounces at lists.tapr.org
>> [mailto:aprssig-bounces at lists.tapr.org]On Behalf Of Ron Stordahl
>> Sent: Thursday, September 21, 2006 11:34 AM
>> To: TAPR APRS Mailing List; UIView32 Yahoo Group
>> Subject: Re: [aprssig] RE: New EU Paradigm also Uiview32 and New-N for
>> the USA
>>
>>
>> John
>>
>> That's a good point (although how that effects duplicate checking I do
>> not understand).  But I do see that WIDE7-1 etc would be used up and
>> thus need not be in the list.  Thus this should be revised to:
>>
>> ALIAS=N5IN-4,WIDE4-4,WIDE4-3,WIDE4-2,WIDE5-5,WIDE5-4,WIDE5-3,WIDE5
>> -2,WIDE6-6,WIDE6-5,WIDE6-4,WIDE6-3,WIDE6-2,WIDE7-7,WIDE7-6,WIDE7-5
>> ,WIDE7-4,WIDE7-3,WIDE7-2
>>
>> Ill update my uiview32.ini file accordingly.
>>
>> Beyond that change doesn't anyone else see anything out of compliance
>> with New-N?
>>
>> It still does irk me that WIDE1-1,WIDE3-3 gets 4 digipeats on an N=3
>> limited digipeater.  Seems to me that the recommendation should be to
>> configure the digipeater for N=2 and then recommend WIDE1-1,WIDE2-2 to
>> get 3 digipeats if you need it.
>>
>> Ron, N5IN
>>
>> John Habbinga wrote:
>>     
>>> You do not need to include WIDE7-1,WIDE6-1,WIDE5-1, or WIDE4-1.  These
>>> will decrement once and terminate.  Including them only serves to
>>> further inhibit duplicate checking amongst other digipeaters in the
>>> area.
>>>
>>> On 9/21/06, Ron Stordahl <ron.stordahl at digikey.com> wrote:
>>>
>>>       
>> ALIAS=N5IN-4,WIDE4-4,WIDE4-3,WIDE4-2,WIDE4-1,WIDE5-5,WIDE5-4,WIDE5
>> -3,WIDE5-2,WIDE5-1,WIDE6-6,WIDE6-5,WIDE6-4,WIDE6-3,WIDE6-2,WIDE6-1
>> ,WIDE7-7,WIDE7-6,WIDE7-5,WIDE7-4,WIDE7-3,WIDE7-2,WIDE7-1
>>     
>
>