On Tue, 4 Dec 2007, Jason KG4WSV wrote:
On Dec 4, 2007 7:51 AM, Jim Tolbert <[EMAIL PROTECTED]> wrote:
I am assuming that Minicom sets the serial port parameters and leaves
them set. Does that seem reasonable?
Nope. Assume that as soon as minicom (or any other app) lets go of
the serial por
Hi, Vic..
Thanks much for the note. I have been using the minicom -s from the
root and have the manual for minicom. As you said, when it first came
up, it have the modem as the default, but I changed it to /dev/ttyS0 and
now, with Craig's echo command, I can see the Kantronics banner he
Make sure that minicom is set right. Read the man pages for minicom. Google a
howto on minicom. You have to set minicom to the baud rate your using, the
serial port your using and some other parameters. Yes there is a way to check
the settings. type minicom -s return and you should see the pr
On Dec 4, 2007 7:51 AM, Jim Tolbert <[EMAIL PROTECTED]> wrote:
> I am assuming that Minicom sets the serial port parameters and leaves
> them set. Does that seem reasonable?
Nope. Assume that as soon as minicom (or any other app) lets go of
the serial port, the parameters go into a completely un
Hey, Craig What a Guy! Thanks after running the echo
command -- at 9600 baud 8,N,1 I get the Kantronics header in Minicom. I
still don't get anything in Xastir, but then I don't have a radio
attached yet .
What I am taking away, is My Serial Port Is Functional.
I am assuming th
You can try:
echo -e “\300\377\300” > /dev/ttyS0
Assuming the baud rate has not changed
out from underneath you on ttyS0. Sometimes
the above command does not "seem" to work
(minicom still doesn't see any command prompt)
until I power-cycle the TNC, then the firmware
banner and command prompt c
Jim,
my first thought is that the Kam is in KISS mode. Now we need someone
who's Kam savvy to tell you how to tell minicom to get you out... And
then how to get back in. An alternative might be to fire off the KISS
script and see if it then talks to the Kam.
gerry
Jim Tolbert wrote:
Many
On Mon, 3 Dec 2007, Jim Tolbert wrote:
> Many thanx, Gerry Minicom shows "stuff" coming through at 4800
> baud. The guy that lent the KAM to me said that it was header info.
> Do you think that it should be ASCII? I get nothing at 2400 or 9600 baud.
It could be command-mode ASCII or KIS
Many thanx, Gerry Minicom shows "stuff" coming through at 4800
baud. The guy that lent the KAM to me said that it was header info.
Do you think that it should be ASCII? I get nothing at 2400 or 9600 baud.
Does minicom set the parameters of the port permanently or only when
minicom i
Fire up a copy of minicom and see if you can talk to the serial port as
a 'regular' user. If not, you can tell the serial port that you (as a
regular user) can access it... We can help with all the bad ways to do
that...
gerry
Jim Tolbert wrote:
After a disk crash in a laptop, I replaced th
After a disk crash in a laptop, I replaced the hard disk, reloaded open
SUSE 10.2, rebuilt Xastir with all the options ( including GPSMAN), and
reloaded all the maps.. I connected a KAM TNC to the serial port and
selected Serial TNC in the interface control. I have tried a variety
of TNC por
11 matches
Mail list logo
