Order Tray | Contact Us | Home | SIG Lists

[aprssig] WIDEn-N question

Tim Cunningham tim_cunningham at charter.net
Tue Nov 3 19:44:21 UTC 2009


"Kai Gunter Brandt" wrote:
> Lynn W. Deffenbaugh (Mr) wrote:
>
>>
>> Fill-in (local) digis are supposed to be configured to only digi on a 
>> WIDE1 that has not been consumed.  For instance, a WIDE1-1, but NOT a 
>> WIDE1*.
>>
>> Higher digis are configured to act on WIDE1 as well as WIDE2, WIDE3, and 
>> sometimes higher n values.  However, some digis will truncate higher 
>> values of n to 2 or 3 and other digis will completely ignore any values 
>> higher than 3.
>>
>
> A little "off topic".
>
> But how should the packet be translated if a "higher digi" hears 
> WIDE1-1,WIDE2-1
>
> 1: DIGI,WIDE1*,WIDE2-1
> 2: DIGI*,WIDE2-1
>
> I would say #2 but maybe i'm wrong.
>

The higher digi could produce either 1 or 2 depending on how it is 
configured.

A properly configured UIDIGI will produce  a variant of #1 (the best it can 
do) with the "has been" digipeated flag on both the DIGI and WIDE1 as shown 
below:

DIGI*,WIDE1*,WIDE2-1

KPC3 version 8.2 firmware produces the following:

DIGI1*,WIDE1,WIDE2-1



KPC3+ version 8.3 firmware produces the following:

DIGI1,WIDE1*,WIDE2-1



The problem with KPC3 version 8.2 firmware was addressed by adding WIDE1-1 
to their Alias list on Bob's site at http://www.aprs.org/fix14439.html and 
the UIDIGI configuration at 
http://qsl.net/n8deu/uidigi_eprom_settings.htm#UIDigiCall



So, there is a multiple choice selection...



73's,
Tim - N8DEU
Decatur, Alabama








More information about the aprssig mailing list