<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META http-equiv=Content-Type content="text/html; charset=windows-1252">
<META content="MSHTML 6.00.2900.2627" name=GENERATOR></HEAD>
<BODY>
<DIV><FONT face=Arial color=#0000ff><SPAN class=982294704-13052005>FYI for New
Paradigm digis using KPC-3 (not the plus) TNC's. Herb
KB7UVC</SPAN></FONT></DIV>
<DIV><FONT face=Arial color=#0000ff><SPAN
class=982294704-13052005></SPAN></FONT> </DIV>
<DIV class=OutlookMessageHeader><FONT face="Times New Roman"
size=2>-----Original Message-----<BR><B>From:</B> nwaprssig-request@nwaprs.org
[mailto:nwaprssig-request@nwaprs.org] <B>On Behalf Of</B> David
Dobbins<BR><B>Sent:</B> Thursday, May 12, 2005 9:16 PM<BR><B>To:</B> SIG
NWAPRS<BR><B>Subject:</B> KPC-3 v8.2 release xxxx-7265 bug
confirmed<BR><BR></FONT></DIV>There has been some discussion on the national
APRS reflector concerning a bug in the Kantronics KPC-3 (not Plus) version 8.2,
release xxxx-7265 ROM. The impact affects only those TNCs being used as APRS
digipeaters, and the fix to work with the new paradigm settings is an easy one.
I have made the changes to the web pages, and will upload those shortly. In the
meantime, here's the text about the issue, how it can be spotted, and the fix.
Thanks to James VE7SRV for taking the time to write a good set of
instructions:<BR><BR>If you have a KPC-3 v8.2 TNC with release xxxx-7265
<STRONG>or earlier</STRONG>, as many<FONT face=Arial size=2> of you have,
you need to set:</FONT>
<DIV><SPAN class=q><FONT face=Arial size=2><BR>UIDIGI ON
WIDE1-1,WIDE4-4,WIDE5-5,WIDE6-6<BR><BR></FONT></SPAN><FONT face=Arial size=2>You
can check the version of TNC firmware by connecting to the TNC, and issuing the
command: Version</FONT></DIV>
<DIV> </DIV>
<DIV><FONT face=Arial size=2>The TNC will respond with something like
this:</FONT></DIV>
<DIV> </DIV>
<DIV><FONT face=Arial size=2>KPC3-3F427265-8.2</FONT></DIV>
<DIV> </DIV>
<DIV><FONT face=Arial size=2>Where:</FONT></DIV>
<DIV> </DIV>
<DIV><FONT face=Arial size=2>XXXX-XXXX7265 v8.2</FONT></DIV>
<DIV> </DIV>
<DIV><FONT face=Arial size=2>is the important part to check. Any version of 8.2
prior to <SPAN style="FONT-WEIGHT: bold">and including 7265</SPAN> exhibit this
bug. </FONT></DIV>
<DIV> </DIV>
<DIV><FONT face=Arial size=2>These versions of firmware have a small bug in the
UITRACE routine that can be overcome by changing the UIDIGI setting.</FONT>
<DIV> </DIV>
<DIV><FONT face=Arial size=2>The bug causes the TNC to insert it's callsign
has-been-digipeated bit set on the name of the digipeater instead of on the used
up WIDE1 path.</FONT></DIV>
<DIV> </DIV></DIV>
<DIV><FONT face=Arial size=2>You can find evidence of the bug when monitoring
the RF stream</FONT></DIV>
<DIV> </DIV>
<DIV><FONT face=Arial size=2>Incorrect behavior looks like this:
KOPEAK*,WIDE1,WIDE2-2 </FONT></DIV>
<DIV><FONT face=Arial size=2>Proper behavior looks like this:
KOPEAK,WIDE1*,WIDE2-2</FONT></DIV>
<DIV> </DIV><FONT face=Arial size=2>This bug does not appear in any version
of the KPC-3+
firmware.<BR><BR>--------------------------------------------<BR>If you have a
KPC-3 v8.2, it is likely a xxxx-7265 release. If you have already upgraded your
WIDEn-N TNC to the new settings, you just need to go back and change UIDIGI ON
WIDE1-1,WIDE4-4,WIDE5-5,WIDE6-6.<BR><BR>If you have a KPC-3Plus v8.3 or newer,
stick with the changes you got off the web site.<BR><BR>Sorry for the extra work
folks. This bug has been known for awhile, but it was our own experimentation
that determined the bug also affected the release 7265 chips. <BR><BR>You can
all subtract an inconvenience fee from your annual membership dues and we'll
call it even.<BR><BR>Dave K7GPS<BR></FONT><BR>-- <BR>David Dobbins<BR>Medical
Lake, WA </BODY></HTML>