LabVIEW
Collecting and interpretting data in Labview
Solved!
Yeah, State Machines are so quick and easy in LabVIEW they definitely have their place. I was hoping to leave them behind though when the company I was working for finally got an NI Enterprise agreement and hired an NI Alliance partner (Bloomy Controls) to come in and help upgrade all our production code to Actor Framework. Of course once everything was running smoothly they laid me off. 
Now I'm starting all over again at a place that wonders why I can't just continue to use the LabVIEW 8.5 license they already paid for. 
Maybe I should just retire...
Search LabVIEW like a graph! 
That PDF is just a technical specification.
You'd need a serial communication protocol for starters. The LV part then is to make a driver implementing this protocol.
The protocol manual would look like this one, but then for your device. I'm not sure where to find it. Sometimes it's not open, as manufacturers want you to use their software...
A starting point could be (just a wild guess) this Inficon LabVIEW driver. It could be completely different, but often they invest in one protocol, and change only the specifics. EDIT: This could be GPIB or something else. Google Inficon LabVIEW driver, or search the NI site. Not sure, but you might find a good starting point.
So page 11 describes the wiring necessary for connecting to a different controller, but to do that you need a power supply (pins 1,2) and seemingly an analog input measurement (3 and 5) connected to a FCC68 connector. Is this really what you want to do?
In that case, appendix A gives the conversion between voltage and pressure in various units.
You can do this in LabVIEW if you have some analog input DAQ device and then you use some simple mathematics nodes to implement the conversion.
If you do this, the other pins can be used to get additional information - pin 6 is essentially 'digital' and tells you if the "cold cathode" is ignited, whatever that means for your measurement (I didn't study the manual more closely). However, don't wire this to a digital input - it will match the power supply level when high (15-30V) which will probably not play nice with most NI DAQ DI levels (typically 5V or 3.3V). There are a few that allow 24V inputs, which you could use, but they aren't the common ones.
Previously you've been discussing trying to communicate with presumably the manufacturer's controller via an RS232 hub, in which case as was already mentioned you need a communications manual for the controller rather than the technical specifications of the sensor. If you want to do that, please provide the communications manual as described by Wiebe.
Of course the first step would be to get it working with supplier software, if it's provided.
In short, you want to read the device, like the shipped software?
You need a driver... So you need to contact someone that made it, or make it yourself. You'd need the communication manual to do the latter.
