[aprssig] The final WIDE2-1,WIDE1-1 solution!

[Greg Noneman]

Pete,

I'm pretty sure that the dupe checking for UIFLOOD and UITRACE are the 
same (compares checksum of source, destination and data fields).  This 
applies to v 8.2 on the KPC 3 and v 8.3 of the KPC 3+.  The dupe 
checking for everything else (including UIDIGI) is simply callsign 
checking.

It is rumored that v 9.0, which is now available for the KPC 3+, 
extends the checksum comparison to UIDIGI entries.  However the their 
online documentation doesn't support this.  Probably the only way to 
find out is to test it.  At this point, I'd be more inclined to upgrade 
a TNC-2 with UIDIGI firmware (which has better dupe checking and 
preemptive digipeating) than to invest in a new EPROM for a KPC 3.

73,
Greg
WB6ZSU


On Apr 2, 2005, at 4:25 AM, AE5PL Lists wrote:

> Was it determined if the KPC 3+ uses the same dupe checking for UITrace
> as UIFlood or does it consider UITrace like UIAlias and only look for
> it's call earlier on in the path?  If the latter, won't we end up with 
> a
> bunch of dupes again because of the various callsign substitutions?
>
> 73,
>
> Pete Loveall AE5PL
> mailto:pete at ae5pl.net
>
> _______________________________________________
> aprssig mailing list
> aprssig at lists.tapr.org
> https://lists.tapr.org/cgi-bin/mailman/listinfo/aprssig
>