On Tue, Dec 20, 2011 at 5:13 AM, Remi Chateauneu <[email protected]>wrote:
> This Perl module is probably a good starting point in term of > implementation: > > http://search.cpan.org/~rbdavison/Device-TNC-0.03/lib/Device/TNC/KISS.pm > > " This module trys to implement an easy way to talk to a KISS mode > Terminal Node Controller (TNC) such as the TNC-X via a serial port." > On Fri, Dec 9, 2011 at 3:40 PM, Tim Ellison, W4TME <[email protected]>wrote: > >> A serial (com) port. >> >> A KISS TNC has a very limited command set, not like a full blown hardware >> TNC >> > Just so everyone knows, here is the specification for the KISS protocol. http://www.ka9q.net/papers/kiss.html I was one of the original definers of KISS. KISS was created to allow software on any computer with an async serial port to send TCP/IP packets framed in the necessary HDLC frames used in AX.25. We had been trying to decide how we were going interface various HDLC controller chips to the PC-bus. I proposed the idea of using a TNC-2 as a simple protocol converter connected to the PC's standard serial port. I proposed a BISYNC-like protocol to run over the async serial link but Mike Chepponis, K3MC, proposed we adapt SLIP which was, quite frankly, a better solution than mine. He then went on to write the first version in Z-80 assembler. KISS does not have any sort of user-readable command set. You cannot connect a terminal program and type commands at it. OTOH, it is very easy to write code to control a KISS TNC via the serial port. The KISS code provides the low-level media-access-control (MAC) layer so that the PC does not need to keep track of low-level timing. -- Brian Lloyd, WB6RQN/J79BPL 3191 Western Dr. Cameron Park, CA 95682 [email protected] +1.767.617.1365 (Dominica) +1.916.877.5067 (USA)
_______________________________________________ fldigi-alpha mailing list [email protected] https://lists.berlios.de/mailman/listinfo/fldigi-alpha
