<HTML><HEAD>
<META content="text/html; charset=iso-8859-1" http-equiv=Content-Type>
<META name=GENERATOR content="IncrediMail 1.0">
<STYLE>v\:* {
BEHAVIOR: url (#default#vml)
}
</STYLE>
<!--IncrdiXMLRemarkStart>
<IncrdiX-Info>
<X-FID>FLAVOR00-NONE-0000-0000-000000000000</X-FID>
<X-FVER>0.000000</X-FVER>
<X-CNT>;</X-CNT>
</IncrdiX-Info>
<IncrdiXMLRemarkEnd-->
</HEAD>
<BODY style="MARGIN: 5px 10px 0px; FONT-FAMILY: Arial; FONT-SIZE: 12pt" background="" scroll=yes bgColor=#ffffff>
<TABLE id=INCREDIMAINTABLE border=0 cellSpacing=0 cellPadding=2 width="100%">
<TBODY>
<TR>
<TD style="POSITION: relative; FONT-SIZE: 12pt" id=INCREDITEXTREGION width="100%">
<DIV style="PADDING-LEFT: 2px" id=INCREDI_TEXT_AREA>
<DIV>
<DIV>Hi,</DIV>
<DIV> If what is being stated here is correct, has any one contacted Kantronics </DIV>
<DIV>and mentioned it to them that the KPC3+ has this problem with some test results .</DIV>
<DIV> </DIV>
<DIV>If so what was Kantronics reply..</DIV>
<DIV> </DIV>
<DIV>Surely there are truckloads of these KPC3+s out there and if they are causing</DIV>
<DIV>these delays within the APRS network Kantronics would want to investigate the problem surely !</DIV>
<DIV> </DIV>
<DIV>Is it hardware or firmware ? can any one confirm ..</DIV>
<DIV> </DIV>
<DIV>Is there any one on here testing the KPC3+ to see what / why etc this is happening ??</DIV>
<DIV> </DIV>
<DIV>We are lucky there are not to many of these in ZL with the APRS network .. </DIV>
<DIV> </DIV>
<DIV>73 Phillip</DIV>
<DIV>ZL2TZE </DIV>
<DIV> </DIV>
<DIV> </DIV>
<DIV> </DIV></DIV></DIV>
<DIV>
<DIV>> I have seen the KPC-3+/KISS issue discussed several times on multiple APRS</DIV>
<DIV>> mailing lists, but my best reference is the direct experience of Richard</DIV>
<DIV>> Sharp (KQ4KX) who maintains the WC4PEM digi/IGate network in Polk County</DIV>
<DIV>> here in Florida. WC4PEM is a KPC-3+ running in KISS mode and if he doesn't</DIV>
<DIV>> reboot the TNC every week or so (sooner if APRS traffic gets heavy), it</DIV>
<DIV>> begins introducing delayed packets into the APRS-IS network. The easiest</DIV>
<DIV>> way to see this is on packets that include a timestamp. The packet will</DIV>
<DIV>> appear once via some other IGate and then again via WC4PEM with a 1-5 minute</DIV>
<DIV>> (yes, it has been up to 5 minutes) delay. The problem is only known to</DIV>
<DIV>> exist in KPC-3+, the non-plus and other Kantronics units do not seem to have</DIV>
<DIV>> the issue.</DIV>
<DIV>></DIV>
<DIV> </DIV>
<DIV>On Wed, Dec 29, 2010 at 13:30, Keith VE7GDH <<A href="mailto:ve7gdh@rac.ca">ve7gdh@rac.ca</A>> wrote:</DIV>
<DIV> </DIV>
<DIV>> Wes AI4PX</DIV>
<DIV>></DIV>
<DIV>></DIV>
<DIV>> Please tell me more about the delays. Do they just affect KISS mode?</DIV>
<DIV>>></DIV>
<DIV>></DIV>
<DIV>> After running KISS mode for about a week or two, the KPC3+ starts</DIV>
<DIV>> introducing delays. I've observed it in UI-View and a friend has seen it</DIV>
<DIV>> in Xastir. I don't know who started the rumour that it was a "UI-View</DIV>
<DIV>> problem" but that person was incorrect... and likely not a UI-View user.</DIV>
<DIV>></DIV>
<DIV>></DIV>
<DIV>> Do they affect in-tnc digipeating?</DIV>
<DIV>>></DIV>
<DIV>></DIV>
<DIV>> I have a KPC3+ based digi running for several years, and I've never</DIV>
<DIV>> observed</DIV>
<DIV>> any delays in anything that it digipeats. If the frequency is quiet, it</DIV>
<DIV>> digipeats</DIV>
<DIV>> what it is supposed to right away.</DIV>
<DIV>></DIV>
<DIV>></DIV>
<DIV>> Do they affect CONVerse mode?</DIV>
<DIV>>></DIV>
<DIV>></DIV>
<DIV>> Sorry, except for playing around with it the odd time, I haven't used</DIV>
<DIV>> CONVerse mode for years.</DIV>
<DIV>></DIV>
<DIV>></DIV>
<DIV>> This could be the delay issue we've been chasing for years.... the</DIV>
<DIV>>> issue that I've thought was UI-View all this time! Could it be???</DIV>
<DIV>>></DIV>
<DIV>></DIV>
<DIV>> I haven't heard any evidence to point the finger at UI-View. I know</DIV>
<DIV>> there are a few digis and IGates in the Puget Sound (Seattle) area</DIV>
<DIV>> that are sometimes involved with delayed packets, and sometimes</DIV>
<DIV>> some IGates in the Vancouver (BC) area. Unless you are watching on</DIV>
<DIV>> RF, it's difficult to prove that a digi was involved. Only occasionally</DIV>
<DIV>> can it be proved that a digi was responsible, but if one was using</DIV>
<DIV>> squelched audio and the squelch was set too loose, it could delay</DIV>
<DIV>> digipeating a packet. In many (if not almost all) instances where the</DIV>
<DIV>> cause has been pinned down to an IGate, it has been a KPC3+ running</DIV>
<DIV>> in KISS mode at an IGate. I try to be open minded, but if I don't see</DIV>
<DIV>> any shred of evidence of it being a UI-View problem, I'll believe</DIV>
<DIV>> my eyes and see it as a TNC problem. I have a stack of KPC3+, all</DIV>
<DIV>> ver 9.1. I'm actually running one in KISS mode on my IGate now, but</DIV>
<DIV>> only because a KPC3 quit responding. With over half a dozen KPC3+</DIV>
<DIV>> sitting there, I just grabbed one of them... and promptly told UI-View</DIV>
<DIV>> to restart every day. This will take the TNC out of KISS mode and</DIV>
<DIV>> put it back in KISS mode when the program starts. It's a work-around</DIV>
<DIV>> to fix a TNC problem, but it's been running at least a month or so like</DIV>
<DIV>> that and I haven't observed any delays.</DIV>
<DIV>></DIV>
<DIV>> If you hear anyone talking about UI-View introducing delays, please</DIV>
<DIV>> ask them to do their homework. They can take my word for it, or they</DIV>
<DIV>> can run their own tests and see it for themselves. If they have another</DIV>
<DIV>> TNC, use it. If the KPC3+ is their only option, it should be restarted</DIV>
<DIV>> periodically. While one could manually tell it "com port none" and</DIV>
<DIV>> OK their way out from there, and then tell it the correct com port</DIV>
<DIV>> again, a more foolproof method is to use the Schedule Editor to</DIV>
<DIV>> make it automatic and just restart the program every day at 3 am</DIV>
<DIV>> or whatever time of the day there is the least amount of APRS activity.</DIV>
<DIV>></DIV>
<DIV>> You can't be blamed for thinking it was a UI-View problem because</DIV>
<DIV>> it was being parroted on all of the APRS related support lists. I'm</DIV>
<DIV>> not the original person that debunked the issue. Someone on one of the</DIV>
<DIV>> support lists that I participated in said that it was the KPC3+ causing</DIV>
<DIV>> the delays. I don't really recall if it was the APRS SIG, UI-View support</DIV>
<DIV>> list or the NWAPRS list, but it was probably the latter. I was most likely</DIV>
<DIV>> using a KPCII or a KPC3 at the time. At some point, I changed over to</DIV>
<DIV>> a KPC3+ for some reason. One day, I got involved in trying to track</DIV>
<DIV>> down some delayed position reports and observed my own IGate doing</DIV>
<DIV>> it. I ran my own tests and observed the problem myself. Not much later,</DIV>
<DIV>> an Xastir user within earshot of me ran the same tests. We also did some</DIV>
<DIV>> tests with one of us sending beacons to the other and counting the seconds</DIV>
<DIV>> (or minutes) before the other's KPC3+ spat the packet out to the APRS</DIV>
<DIV>> client. We have also both asked the operators of several KPC3+ based</DIV>
<DIV>> IGates to restart the TNC or the program (effectively restarting the TNC)</DIV>
<DIV>> and it has solved the problem... for a while.</DIV>
<DIV>></DIV>
<DIV>></DIV>
<DIV>> 73 es cul - Keith VE7GDH</DIV>
<DIV>> --</DIV>
<DIV>> "I may be lost, but I know exactly where I am!"</DIV>
<DIV> </DIV></DIV></TD></TR>
<TR>
<TD id=INCREDIFOOTER width="100%">
<TABLE cellSpacing=0 cellPadding=0 width="100%">
<TBODY>
<TR>
<TD width="100%"></TD>
<TD id=INCREDISOUND vAlign=bottom align=middle></TD></TR></TBODY></TABLE></TD></TR></TBODY></TABLE><SPAN id=IncrediStamp><A href="http://www.incredimail.com/?id=613056&rui=58529483&sd=20101230"><SPAN name="imgCache" border="0"><IMG border=0 alt="FREE Christmas Animations for your email – by IncrediMail! Click Here!" src="cid:1F4AB86D-378F-48F6-98DD-80F193002D37"></SPAN></A></SPAN></BODY></HTML>