From owner-freebsd-questions  Tue Nov  9 10:36:25 1999
Delivered-To: freebsd-questions@freebsd.org
Received: from web118.yahoomail.com (web118.yahoomail.com [205.180.60.99])
	by hub.freebsd.org (Postfix) with SMTP id 594F01529C
	for <freebsd-questions@freebsd.org>; Tue,  9 Nov 1999 10:36:16 -0800 (PST)
	(envelope-from osiris2002@yahoo.com)
Message-ID: <19991109183337.12224.rocketmail@web118.yahoomail.com>
Received: from [208.14.5.211] by web118.yahoomail.com; Tue, 09 Nov 1999 10:33:37 PST
Date: Tue, 9 Nov 1999 10:33:37 -0800 (PST)
From: Joss Roots <osiris2002@yahoo.com>
Subject: Re: FreeBSD and Patient Monitoring !!
To: Oren Sarig <sarig@bezeqint.net>
Cc: freebsd-questions@freebsd.org
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Sender: owner-freebsd-questions@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

Hi there,
thanks for replying.
Any example of how to do that.
any pointer to URL is highly appreciated.
I am ready to put some muscle, and possibly
sweat :-), in this type of programming.

any programs out there for interpreting such
ASCII commands.
any programs how to open serial port.
I mean assuming that I wont need to write
a driver, since most probably the data is coming
raw, and very basic out of these serial ports,
so how would I capture this.
Any program headers for setting up the serial
data communication is appreciated.
thanks alot.


--- Oren Sarig <sarig@bezeqint.net> wrote:
> Hmm... never tried this, but maybe try to look
> at the data
> passed through the serial port in ASCII?
> Possibly the
> commands are in ASCII, so you would be able to
> write a
> driver without having the protocol, with some
> patience to
> look at how things are done.
> 
> --
> Oren Sarig
> sarig@bezeqint.net
> 
> > I am not actually working in any of these
> companies, nor
> have ever heard
> > anything about the equipment mentioned above.
>  However, I
> can do some
> > wild guessing about all this stuff.
> >
> > A serial port is a very generic interface for
> transmitting
> digital data,
> > and this generic nature of it is it's power. 
> However, you
> need to know
> > /what/ to transmit and /when/ in order to
> communicate with
> something on
> > the other end of this "interface."
> >
> > This knowledge of what to transmit and the
> time to send
> it, can be
> > called a *protocol*.  So, if HP or Marquette
> give you or
> somebody else
> > the information about this protocol, it will
> be relatively
> easy to write
> > simple programs for logging or even
> displaying under
> FreeBSD.
> >
> > Provided that this protocol is not some
> valuable-secret of
> HP or someone
> > else, and it's what we call an _open_
> protocol, you can do
> some
> > interesting stuff with your FreeBSD.  If that
> is not true
> (and there is
> > no information on the communication protocol
> used) you're
> probably stuck
> > with what your verdors provide you with.
> >
> > My apologies for my long and probably useless
> posting.
> 
> 
> 
> 
> To Unsubscribe: send mail to
> majordomo@FreeBSD.org
> with "unsubscribe freebsd-questions" in the
> body of the message
> 


=====
MAY THE FORCE BE WITH YOU.
__________________________________________________
Do You Yahoo!?
Bid and sell for free at http://auctions.yahoo.com


To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-questions" in the body of the message