From: Pidoux <f6bvp@free.fr>
To: Chris Kantarjiev <cak@dimebank.com>
Cc: vk2tv@exemail.com.au, linux-hams@vger.kernel.org
Subject: Re: debugging KISS basics
Date: Sun, 30 Nov 2008 12:13:30 +0100 [thread overview]
Message-ID: <4932755A.6020904@free.fr> (raw)
In-Reply-To: <200811281632.mASGWxi3021582@moose.dimebank.com>
Chris,
When TNC is in KISS mode you cannot issue any more command to it.
Every data received are transparently transmitted (except the escape sequence for putting it back into TERMinal mode.)
Thus, you must set the TNC parameters (like the serial port speed, MYCALL, dual port mode if TNC3, and adjust different
audio TX levels for once) before putting the TNC in kiss mode.
In addition, once AX25 driver is loaded, you cannot converse with TNC using your favorite Linux terminal communication
program.
My option is to boot Linux system without AX25 drivers, configure TNC parameters, verify that you can listen to AX25
traffic and connect to a local AX25 station using 1200 or 9600 baud port. Then, when you estimate your TNC is doing
well, send it the escape sequence command to turn it into KISS mode.
You can leave it in KISS mode forever.
After that you are ready to load AX25 and mkiss drivers and run AX25 applications.
Listen utility will help you verify the TNC can pass through AX25 traffic.
73 de Bernard, f6bvp
Chris Kantarjiev a écrit :
>>
>> Wade through this document http://rose.fpac.free.fr/MINI-HOWTO/
>
> Thanks, Ray - that was very useful for learning about config
> and startup.
>
> I'm still trying to figure out how to debug the fact that
> my basic KISS commands won't cause the TNC to do anything...
>
> 73 de chris K6DBG
> --
> To unsubscribe from this list: send the line "unsubscribe linux-hams" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
>
--
To unsubscribe from this list: send the line "unsubscribe linux-hams" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2008-11-30 11:13 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-11-28 16:32 debugging KISS basics Chris Kantarjiev
2008-11-30 11:13 ` Pidoux [this message]
2008-11-30 20:37 ` Ray Wells
2009-08-29 22:26 ` Ray Wells
-- strict thread matches above, loose matches on Subject: below --
2008-11-30 23:34 Chris Kantarjiev
2008-12-01 0:37 ` Bill Vodall WA7NWP
2008-11-30 14:50 Chris Kantarjiev
2008-11-30 20:28 ` Bill Vodall WA7NWP
2008-11-27 14:10 Chris Kantarjiev
2008-11-27 22:33 ` Ray Wells
2009-08-29 22:25 ` Ray Wells
2009-08-29 23:11 ` Alan Crosswell
2009-08-29 23:54 ` Frank Smith
2009-08-29 23:50 ` Frank Smith
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=4932755A.6020904@free.fr \
--to=f6bvp@free.fr \
--cc=cak@dimebank.com \
--cc=linux-hams@vger.kernel.org \
--cc=vk2tv@exemail.com.au \
/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