[Xastir] KPC-3+ KISS problem...

[Tom, ve7did]

Hi All:  We have determined that it is only the KPC3+ which causes the 
problems in Kiss mode.  See the info below as we have now been in 
contact with Kantronics and they are trying to simulate what we and many 
others have found.  We haven't heard anything back yet, but will keep 
you posted.  It does take a "weekish" for the problem to occur, so it 
will probably a little difficult to find the problem.

We have sent Kantronics more info since this posting.

-- 
Propagation Knows No Boundaries
73 de Tom,  ve7did



Hi Ken

I see that Tom VE7DID didn't get any response to his message of July 14 
2009. I didn't get any response to my message of July 13 2009 either. 
See below for a copy of my July 13 message. I'll request a "read 
receipt" for this copy. The KISS problem in the KPC3+ is quite serious 
and needs to be addressed.

Please disregard the "Icom-471A" in the subject of the original message.

Thanks - Keith Powell
VE7GDH
ve7gdh at rac.ca


----- Original Message ----- 
From: "Keith VE7GDH" <ve7gdh at rac.ca>
To: <service at kantronics.com>
Cc: <dave at mynatt.biz>
Sent: Monday, July 13, 2009 11:19 AM
Subject: Re: KPC-3 and ICOM-471A


Hi Ken

> From: service at kantronics.com [mailto:service at kantronics.com]
> Sent: Monday, July 13, 2009 10:39 AM
> To: dave at mynatt.biz
> Subject: Re: KPC-3 and ICOM-471A
>
> Dave:
>
> To my knowledge, no one has reported any type of "timing" issue in the 
> APRS functions, to anyone here at Kantronics.
>
> Can you provide more detail?  Do you know the specific version of 
> firmware in the KPC that seems to have a timing problem? Where can I 
> see the Blog posting, and what date was it posted?
>
> We can't fix a problem if we don't know there is a problem.
>
> For some time, our service department has only one technician (me) to 
> answer technical questions by phone, email, and otherwise. I also do 
> product testing and repair. There are times when I may be away from my 
> desk, or on another phone call (or just off duty) and may not be able 
> to pick a ringing line.
>
> We strive to answer all received email in a timely manner. Messages 
> sent direct to individuals in the company may not be received (several 
> of those persons are no longer with the company). Our posted email 
> addresses for Sales and Service, are still valid.
>
> We have discontinued most support for old model TNCs (several years 
> ago). I can answer operational and technical questions about older 
> models, but repair service and updates are no longer available for old 
> units.
>
> Ken
> Kantronics Technical Service

The problem that Dave was referring to is with the KPC3+ in KISS mode.
After it has been running for a period of time (about a week) it starts
delaying data that it spits out the serial port by up to about a minute
and a half.

I have used KPC IIs and KPC3s for regular packet many years with no
known problems, and in KISS mode connected to UI-View32 2.03 for about 5
years now. About a year or so back, I kept hearing rumours about the
KPC3+ being responsible for delays. I usually use a venerable KPC II or
KPC3 with UI-View.

To me, these reports were just anecdotal. However, some months ago, I
changed over to a KPC3+ ver 9.1 and ran my own tests and the conclusion
that I came to was that the KPC3+ (the same problem is reported by
others with older versions of the KPC3+) were responsible for delays. I
have witnessed it myself, viewing received beacons in UI-Views terminal
window, and have worked with others sending my own APRS beacons with a
time stamp enabled and while being in direct contact with them and
noting the time of the original beacon and when the other station
"received" the beacon. These tests were either direct with no digis
involved, or via my own digi which I observed sending the digipeated
copy immediately (fraction of a second) after receiving the original. I
have about seven KPC3+s ver 9.1 and they work perfectly set up as an
APRS digi. In KISS mode connected to an APRS client (not just UI-View,
also Xastir) it is just a matter of time before it starts introducing
delays.

The reason pinning it down to a KPC3+ problem is that there is always
the possibility of an APRS digi introducing delays... e.g. a "high" digi
that hears too much in a busy area could end up waiting a period of time
for a quiet period to send the digipeated copy. While that does happen,
the major delays being reported always seemed to be caused by IGates
running a KPC3+ in KISS mode. The casual symptoms are viewing a mobile
station that is taking a zig-zag route with delayed reports making it
look like it was constantly going "back in time". As mentioned above, my
own tests ruled out delays caused by a digi.

I know there are several people that are "getting ready to contact"
Kantronics about this, but as Dave has contacted you for other reasons
and mentioned this problem to you, it's as good as time as any to send
you the above information.  If you don't mind, I'll pass along your name
and email address to a few of the other people that did their own tests.
I'm sure they will be happy to tell you of their observations and know
that there is someone at Kantronics willing to listen and run their own
tests.

Thanks - Keith Powell
VE7GDH
ve7gdh at rac.ca