From owner-freebsd-questions Tue Nov 9 11:46:38 1999 Delivered-To: freebsd-questions@freebsd.org Received: from probity.mcc.ac.uk (probity.mcc.ac.uk [130.88.200.94]) by hub.freebsd.org (Postfix) with ESMTP id 1A1D714D9F for ; Tue, 9 Nov 1999 11:46:34 -0800 (PST) (envelope-from jcm@dogma.freebsd-uk.eu.org) Received: from dogma.freebsd-uk.eu.org ([130.88.200.97]) by probity.mcc.ac.uk with esmtp (Exim 1.92 #3) id 11lHDt-000HVM-00; Tue, 9 Nov 1999 19:46:33 +0000 Received: from localhost (jcm@localhost) by dogma.freebsd-uk.eu.org (8.9.3/8.9.3) with SMTP id TAA20180; Tue, 9 Nov 1999 19:46:32 GMT (envelope-from jcm@dogma.freebsd-uk.eu.org) Date: Tue, 9 Nov 1999 19:46:32 +0000 (GMT) From: Jonathon McKitrick To: Joss Roots Cc: Michael Rothenberg , freebsd-questions@freebsd.org Subject: Re: Patient Monitoring (NO FreeBSD really) In-Reply-To: <19991109194319.26350.rocketmail@web118.yahoomail.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-questions@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG There is probably generic code available that does this. Keep in mind, you'll need an app to integrate all this data into. Plus, there may be lots of failsafes built into the software. It's wuite a large undertaking. You really aren't likely to find any cut-n-paste code to do that for you. The most you may find is serial port code. Maybe a local bookstore with an extensive windows programming section would be of help. But then, of course, you have to start with windows programming. That's an entirely different monster altogether. ;-) On Tue, 9 Nov 1999, Joss Roots wrote: >Hi there. >Thanks very much foor your reply. >I'll try to contact the Tech assistance >and will look into their user manual >and may have a chat with our maintenance people > >meanwhiles, your answer seams to be coming from >a pro, so I might need your help later on. >By the do you have any working code doing >the things you described. >thanks again. > >--- Michael Rothenberg > wrote: >> the following is not really related to FreeBSD: >> >> The first thing you really need to do is call >> all the equipment >> manufacturers and determine if their machines >> are capable of outputting data >> through the serial port in the first place. >> Dont waste your time if they >> dont even have the capability to squirt info >> out the ports. A lot of >> equipment will have some capability to get >> instantaneous values. HP will >> probably use GPIB (look at local engineering >> book store for info or WWW) if >> anything at all, but I am not sure about the >> others. >> >> If the machine can talk, then get a detailed >> description of the command >> structure (protocol) and what kind of response >> you should expect to get for >> each command. Usually each command will have >> some kind of response to tell >> you it was received and acted upon or the >> response will hold the data you >> asked for in some format. If you skip talking >> to the sales people and get in >> with the tech support engineers they usually >> will send you anything you >> need. Few sales people really know the machines >> to this kind of level. >> >> Once you receive the info on the commands you >> have available to you, you can >> make a determination as to if you can get the >> data you want out of the >> machine. Usually, you wont get live feeds from >> the machine and will have to >> poll it every few 100 ms or so (for windoze >> anyway). You can poll as fast as >> your comm setup will allow, but its usually >> pretty slow like 2400/9600 baud. >> Newer machines sometimes get up to 19.2. >> >> This means you wont have true 'real time' but >> its kinda close enough for >> most applications. Medical might be different >> though. Lots of rules there. >> If you are only displaying the data and >> tracking it without the >> responsibility of acting on it then you might >> not have much to worry about. >> >> I have never done a system like this in >> FreeBSD. Only that windos stuff. On >> win systems its a piece of cake with any number >> of 3rd party comm libraries >> so I expect it wont be that hard on FBSD either >> once you find the code. Of >> course, getting the data is usually the easy >> part. Once you get the data you >> have to figure out what to do with it and thats >> the fun part!! >> >> Enjoy! >> >> -Michael >> >> >~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ >> Michael Rothenberg >> Systems Engineer >> 617.354.3830 ph >> Intelligent Automation Systems Inc. >> 617.547.9727 fx >> Cambridge, MA, U.S. >> www.automationonline.com >> >~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ >> >> >> > > >===== >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 > -jonathon To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message