Re: Using Kantronics KPC3+ with APRSIS32
Good suggestion, but it isn't really using a KPC-3+ as a digipeater that is an issue, but using a KPC-3+ in KISS mode with upstream software doing the digipeating.
The KPC-3+ firmware does excellent digipeating as far as I know. Provided that the digipeating is being done completely within the device itself.
There is a well documented bug in the KPC-3+ firmware's KISS support that causes received packets to be delayed in delivery out the KISS port. This means that any software-based digipeater (or IGate for that matter) receiving KISS packets from a KPC-3+ will be marching slowly backwards in time as the delays seem to get longer and longer until the KPC-3+ is reset.
This is will documented in an article by Hessu, the author of aprs.fi, at the following link.
Recommended reading as well as this article:
It seems that the issue may be solved by simply tying RTS and CTS together at the KPC-3+ end of the serial cable. But getting this word out, and worse, convincing KPC-3+ owners running in KISS mode, is an ongoing challenge.
Oh, and I've seen the issue more with KISS-mode KPC-3+ devices being used with IGates than I have with digipeating. Digipeating delays would be seen in the local RF environment as a digipeat being received long after a packet was actually transmitted. Yes, it does happen, but on the -IS, the effects are usually much more visible.
And yes, there does seem to be a software-controlled digipeater
using a KISS-mode KPC-3+ somewhere out in your neck of the woods!
Lynn (D) - KJ4ERJ - Author of APRSISCE for Windows Mobile and Win32
On 1/21/2020 6:51 AM, Gil wrote: