[Xastir] Linux AX25 KISS driver for Kenwood D700 (fwd)

[Curt, WE7U]

2nd one (and last so far) from the other list.  --we7u

---------- Forwarded message ----------
Date: Fri, 18 Dec 2009 11:23:29 -0800 (PST)
From: "Curt, WE7U" <archer at eskimo.com>
To: Bill V WA7NWP <wa7nwp at gmail.com>
Cc: linux-hams <linux-hams at vger.kernel.org>
Subject: Re: Linux AX25 KISS driver for Kenwood D700

On Thu, 17 Dec 2009, Bill V WA7NWP wrote:

Actually Rick Muething, KN6KB wrote:

> The solution we used and which appears to work well and is solid is to
> escape the “C” character.  So when any data is sent to the TNC in KISS
> mode if there is an ASCII “C” it is replaced by the sequence <0xDB>”C”
> which essentially escapes the “TC 0<Cr>” sequence. The KISS protocol
> (in the D710’s KISS TNC implementation) removes the <0xDB> which is
> the frame escape so no modification of the transmitted data stream is
> actually made. Thanks to Peter Woods for figuring this out.

Bill:  I see the mentioned that this fixes the problem with Winlink
talking to D710's.  Has this "fix" (hack) been tested on all of
these?

     TM-D700A
     TM-D710A (Yes, per above)
     RC-D710 (the actual TNC used w/TM-D710A) (Yes, per above)
     TH-D7A
     TH-D7A(G)
     TS-2000 (all models)
     Other Kenwoods?

For Xastir purposes:  Would I need to identify a port as having a
Kenwood KISS TNC attached before enabling this extra escaping?  A
counter-question would be:  Would the above escaping of the 'C'
character cause problems for non-Kenwood KISS implementations?

I _really_ wish Kenwood would fix this (and other) problems with
their KISS implementations so the rest of us wouldn't have to
program around their bugs.

-- 
Curt, WE7U.                         <http://www.eskimo.com/~archer>
    APRS:  Where it's at!                    <http://www.xastir.org>
   Lotto:  A tax on people who are bad at math. - unknown
Windows:  Microsoft's tax on computer illiterates. - WE7U.
The world DOES revolve around me:  I picked the coordinate system!"