[aprssig] RE: New EU Paradigm also Uiview32 and New-N for the USA
ron.stordahl at digikey.com
Thu Sep 21 13:48:22 CDT 2006
The reason as I understand it is that one of the 'excessive' paths, say
WIDE7-7 will be thus repeated only a single time. By including it as a
'alias' it is not processed by the decrementing procedure.
> Why do any of these need to be put in as aliases?
> Surely the whole point of the n-n system is that the smart part of the digi
> recognises it and processes accordingly. If its traceability that's required
> then just enable callsign substitution on WIDE as well as TRACE.
> Jim, G1HUL
> ...trying to understand the odd things in life!
> -----Original Message-----
> From: aprssig-bounces at lists.tapr.org [mailto:aprssig-bounces at lists.tapr.org]
> On Behalf Of Ron Stordahl
> Sent: 21 September 2006 19:34
> To: TAPR APRS Mailing List; UIView32 Yahoo Group
> Subject: Re: [aprssig] RE: New EU Paradigm also Uiview32 and New-N for the
> 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:
> Ill update my uiview32.ini file accordingly.
> Beyond that change doesn't anyone else see anything out of compliance with
> 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
>> On 9/21/06, Ron Stordahl <ron.stordahl at digikey.com> wrote:
> aprssig mailing list
> aprssig at lists.tapr.org
More information about the aprssig