From: "J. Lance Cotton" <joe@lightningflash.net>
To: Douglas Cole <doug.n7bfs@gmail.com>
Cc: linux-hams@vger.kernel.org
Subject: Re: tncs and kiss mode
Date: Mon, 30 Jan 2006 15:00:52 -0600 [thread overview]
Message-ID: <43DE7E84.4070406@lightningflash.net> (raw)
In-Reply-To: <9923fd660601301248r49d34f64g76dc09246dbad341@mail.gmail.com>
Douglas Cole wrote:
d
> Ok, I still don't know what the character values mean, but I read the
> man page for "echo" and figured that you must be using octal and know
> that 300 is octal for 192 decimal and 377 is octal for 255 decimal...
>
> But the ASCII charts I have don't explain what 192 and 255 are ,
> anyone can point me to a chart that does ?
They're pretty much just arbitrary values. KISS is an 8-bit clean protocol.
It doesn't operate from an "ascii characters" point of view, it operates in
a "bytes of data" POV.
There are a few "reserved" bytes for special functions like sending commands
to the TNC rather than sending data to be transmitted.
192 is called "FEND" for "Frame End" and is used to bracket (front and back)
all packets to and from a KISS device.
255 is essentially the "KISS OFF" command, if the TNC supports it.
There is another special byte called FESC "Frame Escape". If one of the
reserved bytes happens to appear in the data stream, you prefix it with FESC
and then the KISS device knows that the byte following FESC should be
treated as plain data rather than a command.
--
J. Lance Cotton, KJ5O
joe@lightningflash.net
http://kj5o.lightningflash.net
Three Step Plan: 1. Take over the world. 2. Get a lot of cookies. 3. Eat the
cookies.
next prev parent reply other threads:[~2006-01-30 21:00 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-01-30 2:59 tncs and kiss mode Ted Gervais
2006-01-30 3:29 ` Jeremy Utley
2006-01-30 9:47 ` Ted Gervais
2006-01-30 11:03 ` Bob Nielsen
2006-01-30 13:58 ` Wilson G. Hein
2006-01-30 18:17 ` Gérard / F6FGZ
2006-01-30 18:23 ` Jeremy Utley
2006-01-30 20:30 ` Douglas Cole
2006-01-30 20:39 ` Tomi Manninen
2006-01-30 20:48 ` Douglas Cole
2006-01-30 20:57 ` Douglas Cole
2006-01-30 21:00 ` J. Lance Cotton [this message]
2006-01-30 21:37 ` Oliver Hohlfeld
2006-01-30 23:26 ` Douglas Cole
2006-01-30 21:05 ` Oliver Hohlfeld
2006-01-30 21:07 ` Oliver Hohlfeld
2006-01-30 20:47 ` Bill Vodall WA7NWP
2006-01-30 21:08 ` Curt, WE7U
2006-02-17 6:07 ` CONVERS Primary server Bill Vodall WA7NWP
-- strict thread matches above, loose matches on Subject: below --
2006-01-30 12:58 tncs and kiss mode Albert Duane Lawson
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=43DE7E84.4070406@lightningflash.net \
--to=joe@lightningflash.net \
--cc=doug.n7bfs@gmail.com \
--cc=linux-hams@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).