From: Nicolae Mihalache <mache@abcpages.com>
To: mariano_moreyra@aca.org.ar, linux-c-programming@vger.kernel.org
Subject: Re: tcpdump equivalent for the serial port
Date: Fri, 12 Sep 2003 16:01:50 +0200 [thread overview]
Message-ID: <3F61D1CE.7080404@abcpages.com> (raw)
In-Reply-To: <000101c37934$dcd34740$0b04a8c0@aca.org.ar>
Mariano Moreyra wrote:
>Hi Nicolae,
>
Hi Mariano!
>I think that what you want to do is not posible just with a software.
>You have to build a special cable to do that (somebody tell me if I'm wrong,
>or if knows another option)
>In my job we have one of those cables because we needed to see what was
>going on between two applications that talk to each other via serial port.
>The bad thing is that you need a third computer that would be the sniffer.
>
The problem is that opening the cable and connecting it to a third port
may introduce some variations in the signals going over the serial
cable. This is something that I want to avoid as much as possible. The
other end of the serial cable is not another computer but a device that
is itself the subject of development and test so it can not be assumed
as working nor it can be developed with a non-nominal serial cable
connected to it. Even worse, my serial link is not RS232 but RS422 which
has a higher speed and it's more difficult to have break-out capability
without interferences.
This is why I'm looking for a software solution, i.e. something that
communicates with the serial driver and gets all the messages that pass
through it.
Nicolae
next prev parent reply other threads:[~2003-09-12 14:01 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-09-12 13:37 tcpdump equivalent for the serial port Nicolae Mihalache
2003-09-12 13:50 ` Mariano Moreyra
2003-09-12 14:01 ` Nicolae Mihalache [this message]
2003-09-12 14:08 ` Mariano Moreyra
2003-09-12 14:05 ` Jan-Benedict Glaw
2003-09-12 14:23 ` Nicolae Mihalache
2003-09-12 14:39 ` Jan-Benedict Glaw
2003-09-12 15:33 ` Nicolae Mihalache
2003-09-12 14:34 ` Jamie Le Tual
-- strict thread matches above, loose matches on Subject: below --
2003-09-12 15:37 Nicolae Mihalache
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=3F61D1CE.7080404@abcpages.com \
--to=mache@abcpages.com \
--cc=linux-c-programming@vger.kernel.org \
--cc=mariano_moreyra@aca.org.ar \
/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.