From owner-freebsd-questions Tue Nov 9 9:30: 7 1999 Delivered-To: freebsd-questions@freebsd.org Received: from mail.bezeqint.net (mail-a.bezeqint.net [192.115.106.23]) by hub.freebsd.org (Postfix) with ESMTP id A3BC915438 for ; Tue, 9 Nov 1999 09:30:03 -0800 (PST) (envelope-from sarig@bezeqint.net) Received: from asmodean ([212.25.119.210]) by mail.bezeqint.net (Sun Internet Mail Server sims.3.5.1999.07.30.00.05.p8) with SMTP id <0FKX00KB7XXRMR@mail.bezeqint.net> for freebsd-questions@freebsd.org; Tue, 9 Nov 1999 19:29:52 +0200 (IST) Date: Tue, 09 Nov 1999 19:29:14 +0200 From: Oren Sarig Subject: Re: FreeBSD and Patient Monitoring !! To: freebsd-questions@freebsd.org Message-id: <029501bf2ad7$f1cde100$d27719d4@asmodean> MIME-version: 1.0 X-Mailer: Microsoft Outlook Express 5.00.2314.1300 Content-type: text/plain; charset="windows-1255" Content-transfer-encoding: 7bit X-MSMail-Priority: Normal X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2314.1300 References: <19991108165444.26573.rocketmail@web107.yahoomail.com> <86g0yguygg.fsf@localhost.hell.gr> X-Priority: 3 Sender: owner-freebsd-questions@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG 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