[aprssig] New n-N settings for ui-digi

[Tim Cunningham]

Bruce,

I make bad assumptions all the time and I am probably making one here, but I 
have to test it first.

Since UIFloodCall is "AL" and those packets are contained in the state I saw 
no reason to turn on the ID to add any confusion at this point. I have not 
fully tested the impact to our network by using the ID method for UIFlood 
with the addition of WIDE1-1 in place of RELAY. Until I have time to test 
it, I am inclined to leave it as it is at the moment because there is no 
problem. This is specific to our network and the majority of digpeaters here 
are UIDIGI which handle the paths correctly without bastardizing the path. I 
can watch it count down from Ft Payne to Scottsboro to Huntsville starting 
at AL3-3 to AL3-2 to AL3-1 just a it was originally intended. No ID 
substitution will ever be present since the path is a pure "AL3-3" and there 
is nothing to substitute in that path.

Has anybody tested the path "WIDE1-1,WIDE2-2" on a pure UIDIGI network to 
see what it does? If I have time this afternoon I will set 3 digi's outward 
to the ID method on a UIDIGI network to see the results. Basically, I need 
to know what happens to the WIDE1-1 on a UIDIGI network when the ID method 
is utilized. Then, I would consider the change. It is not broke here so I 
have not tried to fix this particular issue. Some of our changes are 
remotely set and some have updated UIDIGI EPROMS at this time with the 
changes shown on the website.



Tim - N8DEU
Huntsville, Alabama



----- Original Message ----- 
From: "Bruce, KQ4TV" <aprs at almostanywhere.com>
To: "TAPR APRS Mailing List" <aprssig at lists.tapr.org>
Sent: Wednesday, April 06, 2005 10:56 AM
Subject: Re: [aprssig] New n-N settings for ui-digi


> Tim,
>
> You didn't miss anything. I'm the one that missed the changes you made.
> I made a bad assumption and did not look to see if you had made changes.
> The only thing I see is that you are choosing to not ID on UIFlood.
>
> Bruce,kq4tv
>
> On Apr 6, 2005, at 10:24 AM, Tim Cunningham wrote:
>
>> Bruce,
>>
>> Maybe I missed something on my website for adopting the new paradigm
>> changes.
>>
>> We have been on the new paradigm since the Fall of 2003 implementing the
>> UIFloodCall (ALA) and UITraceCall (WIDE) changes to contain weather
>> station data  within the boundaries of the state. The UIFloodCall was 
>> just changed
>> from ALA to AL because of the recent paradigm changes that caught up with 
>> our
>> changes. We decided to conform to the 2 letter state designation after we 
>> had
>> already been using ALA for the past year and a half. We just dropped 
>> support for
>> the WIDE alias and plan to drop the RELAY support later this year after a 
>> migration
>> period for users and relay stations to move to WIDE1-1.
>>
>> The IGate may need to have its path changed to limit the NWS data, but 
>> other than
>> that what did I miss?
>>
>> http://www.qsl.net/n8deu/uidigi_eprom_settings.htm
>>
>>
>>
>> Thanks and 73's,
>>
>> Tim - N8DEU
>
>
> _______________________________________________
> aprssig mailing list
> aprssig at lists.tapr.org
> https://lists.tapr.org/cgi-bin/mailman/listinfo/aprssig