From: Bill Vodall WA7NWP <wa7nwp@jnos.org>
To: linux-hams@vger.kernel.org
Subject: Re: tncs and kiss mode
Date: Mon, 30 Jan 2006 12:47:07 -0800 [thread overview]
Message-ID: <43DE7B4B.5040509@jnos.org> (raw)
In-Reply-To: <43DE5851.33E01B71@free.fr>
Once kissattach has grabbed a serial port, it's apparently not possible
to do the "echo's" or minicom operations to that port without killing
the kissattach.
No problem for bringing a TNC out of KISS mode:
kissparms -x -p <port>
What would be very cool is a tweak to kissparms to allow sending text to
the port. Something like:
kissparms -p <port> -t "^C\rINTFACE KISS\rRESET\r"
A quick and dirty dump terminal to talk to the tnc manually would be
useful at times too..
So many projects...
> (2) To enter again, the same kind of script might work with KPC-9612
(not tested):
>
> echo "Entering KISS mode on port COM1"
> echo -e "INTFACE KISS\r" >/dev/ttyS0
73,
Bill - WA7NWP
next prev parent reply other threads:[~2006-01-30 20:47 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
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 [this message]
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=43DE7B4B.5040509@jnos.org \
--to=wa7nwp@jnos.org \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.