From owner-freebsd-questions Thu May 6 19:52: 6 1999 Delivered-To: freebsd-questions@freebsd.org Received: from mail.HiWAAY.net (fly.HiWAAY.net [208.147.154.56]) by hub.freebsd.org (Postfix) with ESMTP id B4DA815128 for ; Thu, 6 May 1999 19:52:04 -0700 (PDT) (envelope-from dkelly@nospam.hiwaay.net) Received: from nospam.hiwaay.net (tnt8-216-180-15-147.dialup.HiWAAY.net [216.180.15.147]) by mail.HiWAAY.net (8.9.1a/8.9.0) with ESMTP id VAA12558; Thu, 6 May 1999 21:52:02 -0500 (CDT) Received: from nospam.hiwaay.net (nospam.hiwaay.net [127.0.0.1]) by nospam.hiwaay.net (8.9.2/8.9.2) with ESMTP id VAA39741; Thu, 6 May 1999 21:52:00 -0500 (CDT) (envelope-from dkelly@nospam.hiwaay.net) Message-Id: <199905070252.VAA39741@nospam.hiwaay.net> X-Mailer: exmh version 2.0.2 2/24/98 To: Thomas David Rivers Cc: freebsd-questions@FreeBSD.ORG From: David Kelly Subject: Re: Async Serial Sniffer/Analyzer? In-reply-to: Message from Thomas David Rivers of "Thu, 06 May 1999 20:36:47 EDT." <199905070036.UAA94481@lakes.dignus.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Thu, 06 May 1999 21:52:00 -0500 Sender: owner-freebsd-questions@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Thomas David Rivers writes: > > > > Am in need of a tool to capture and display hex and ASCII a small (100 > > to 300 bytes at a time) amount of data off a 300 baud async serial line, > > 8 bits, 1 start, 1 stop. Would also be nice if it monitored and logged > > transitions of the handshake lines. > > > > While such a minimal tool as I'm in need of should be easy to write I > > don't have a day or so to do it. A pass thru /usr/ports failed to turn > > one up. > > > > FreeBSD, Mac, and even Windows solutions are acceptable. > > > > If it's just a regular 232 line - you could simply > > cat /dev/cuaXX | tee | od -x > > The could even be a named pipe in the file system, so that, > in another "window" (or vtty) you could also be doing: > > cat | whatever-program-it-needs-to-go-to > > > And - instead of "od -x", you could use something else that actually > understood the bits & did the monitoring and logging you ask for > (say, a small C program you wrote yourself.) > > Part of the the original UNIX philosophy - small tools that you can "hook together" yourself to accomplish big tasks. It's a very powerful > problem solving approach. Just recently discovered I have had a headache most of the afternoon and evening so things aren't quite happening the way I'd expect. Had considered reading the serial port into od or hd or similar but discounted that solution as many "packets" are less than 16 bytes or so needed to complete an output line and see what is happening. And somehow (brain fart?) I made a pass thru /usr/ports/ and completely missed: Port: snooper-980813 Path: /usr/ports/comms/snooper Info: serial line protocol analyzer (need two serial interfaces) Maint: itojun@itojun.org Index: comms B-deps: R-deps: ...which appears to be exactly what I was hoping to find. -- David Kelly N4HHE, dkelly@nospam.hiwaay.net ===================================================================== The human mind ordinarily operates at only ten percent of its capacity -- the rest is overhead for the operating system. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message