[aprssig] Is there a problem here?

[Steve Slay]

Bruce,

It looks like you followed;
KPC3 Version 8.2(early versions) Settings for WIDEn-N         6 May 2005
http://cadigweb.ew.usna.edu/~bruninga/aprs/kpc3+82WIDEn.txt

Version 8.2 (early releases) UNIQUE Settings:
   UIDIGI  ON,   WIDE1-1, WIDE4-4, WIDE5-5, WIDE6-6
   UIFLOOD  WIDE,30,ID
   UITRACE  SS


6)  IMPLEMENT THE New n-N Paradigm changes.

D.  Instead use the UIDIGI alias list to support WIDE1-1 first-hops for
mobiles and to TRAP the larger N's.  Set UIDIGI as follows:

UIDIGI ON, WIDE1-1, WIDE4-4, WIDE5-5, WIDE6-6

These specific aliases for the larger N's will act like traps because
this digi will digipeat them once and then no farther.


I think including WIDE1-1 may be an error on Bob's part.  Because if a 
station can have a path of WIDE2-2 and it goes through the digi and is 
decremented properly, then why do you want to trap a packet with a  path of 
WIDE1-1, WIDE2-1?



Steve Slay
KC5MVY
"Only two things are infinite, the universe and human stupidity, and I'm not 
sure about the
former."    Albert Einstein

========================================




----- Original Message ----- 
From: "Bruce W. Martin, KQ4TV" <aprs at almostanywhere.com>
To: "TAPR APRS Mailing List" <aprssig at lists.tapr.org>
Sent: Saturday, August 27, 2005 8:32 AM
Subject: [aprssig] Is there a problem here?


There has been some discussion between local APRS Digi sysops and one
of them made this observation:

> WA9INF-9>GPSMV,WIDE1-1,WIDE3-3,qAS,KG4NRC:$GPRMC,143529,A, 
> 3612.5886,N,08652.3467,W,37.472,282.4,260805,2.8,W*4E
> WA9INF-9>GPSMV,NT4UX-3*,WIDE1,WIDE2-2,qAr,KQ4TV-3:$GPRMC,143840,A, 
> 3612.6870,N,08655.3066,W,38.936,269.3,260805,2.8,W*44
>
> here is one problem I see. It looks like NT4UX-3 doesnt handle 
> WIDE1-1,WIDE2-2 correctly.  It should be WIDE1*,WIDE2-2 . When a  digi 
> see's WIDE1 then it ignores anything after that as it thinks  its the end 
> of the path.


I manage the NT4UX-1, -2, -3 digis in the Middle Tennessee area.

NT4UX-1 uses a KPC3 v8.2 and includes the following settings:
     MYALIAS OHX
     UIDIGI ON WIDE1-1, WIDE4-4, WIDE5-5, WIDE7-7
     UIFLOOD WIDE,30,ID
     UITRACE TN,30

NT4UX-2 and NT4UX-3 are both using  UIdigi v1.9b3.
They both have:
     UIFloodCall            =       TN
     UITraceCall            =      WIDE

UITrace, UIFlood, and UIDigi all do callsign substitution


Below is some additional traffic I have observed from my house using
xastir.
It looks like things a working but I don't understand the packets
with WIDE2* and WIDE3*.
Which digipeater sent them?
Should they not have had a callsign substituted instead?

Bruce, KQ4TV


Traffic observed via RF from my home using Xastir:

4:TNC-> N8DEU-12>STTT3P,W4GPS-7,WIDE1,NT4UX-2*,WIDE2-1/V:'rCFl!~j/]"7U}
4:TNC-> N8DEU-12>STTT3P,W4GPS-7,WIDE1,NT4UX-2,WIDE2*/V:'rCFl!~j/]"7U}
4:TNC-> N8DEU-12>STTT3P,W4GPS-7,WIDE1,NT4UX-2,NT4UX-3*,WIDE2/V:'rCFl!
~j/]"7U}
4:TNC-> KU4WW-6>S4TR2P,KA4BNI-2*,WIDE2/V:'t^H UMk/]"6,}
4:TNC-> K4UAN-2>S6QP1X,NT4UX-3*,WIDE2-1/V:'q:Pl 
h/]Cookeville
Regional Medical
4:TNC-> W1ARN-1>APN382,WIDE2-1/V:!3628.03NF08628.64W#PHG7290/
W3,TNn,MidTN Skywarn MTEARS www.mtsh.org