[aprssig] New User Question(s)

[Chris Kantarjiev]

> >>> mheskett at mindspring.com 06/05/06 11:12 AM >>>
> At 09:53 AM 6/5/2006, you wrote:
> >Just to clarify, any digi that can support WIDEn-N automatically
> >also supports W1-1.   That was part of the beauty of the
> >WIDE1-1,WIDE2-1 recommended path under the New-N....
> >...Hope that helps
> >Bob, WB4APR
> 
> They may support it, but if it is a KPC 3 with 8.2, it will not 
> support it correctly(unless you put WIDE1-1 in the UID field). It 
> will digi the WIDE1-1 and decrement it to WIDE1, which no one else 
> will digi, effectively cutting you off from being digi'd again.
> ==/===/===/===/===/===/===/===/===/===/===/===/===/===/===/===/===/
> Mike Heskett    email   mheskett at mindspring.com 
> WB5QLD  WWW 

Well, someone will ... I am working with a new digi based on the Elcom
uTNT, and it seems to have this same behavior - I haven't figured
out how to turn on callsign substitution.

But I'm seeing packets like this in findu:

K6DBG-7>SWSQYS,WIDE1,W6CX-3*,WIDE2,qAo,KG6MRC-1:

where I'm certain that the first hop was from K6DBG-12, the new digi.
W6CX-3 seems perfectly happy to continue ... but maybe this is
an artifact of the MIC-E encoding? That always seems to confuse what
is shown in the findu trace.

73 de chris K6DBG