 Scherni
		
			Scherni
		
		
		
		
		
		
		
		
	
			
			
    
	
		
		
		08-17-2012
	
		
		04:45 AM
	
	
	
	
	
	
	
	
	
	
	
	
	
	
 - last edited on 
    
	
		
		
		03-27-2024
	
		
		10:37 AM
	
	
	
	
	
	
	
	
	
	
	
	
	
	
 by 
				
		 Content Cleaner
		
			Content Cleaner
		
		
		
		
		
		
		
		
	
			
		
Hi,
I am trying to communicate via Labview 2011 with a CO2 Sensor from Sensors (Single-AGM Plus; http://www.sensors-inc.com/agm.html)
My problem is that there is no support from the company concerning Labview. The device connected to the computer via USB.
I only need to get the information of the CO2 content and the pressure.
My problem is that the communication protocol with the sensor is no standard and rather complex. (I added it as attachment)
Would you suggest me to build up the communication with VISA or is it better to invest some money in a DAQ-Device.
for example:
http://www.omega.com/ppt/pptsc.asp?ref=OMB-DAQ55
https://www.ni.com/en-us/shop/model/usb-6501.html
https://www.ni.com/en-us/support/model.usb-6008.html
I am a beginner with Labview and DAQ-Devices.
Thanks in advance.
 nyc_(is_out_of_
		
			nyc_(is_out_of_08-17-2012 09:02 AM
@Scherni wrote:
My problem is that the communication protocol with the sensor is no standard and rather complex. (I added it as attachment)
Device appears as a virtual COM aka RS232 .
How is that "no standard" ???
It is also has a RS-485 interface.
How is that "no standard" ???
08-20-2012 12:35 AM
By no standard I ment the protocoll to communicate with the device and to get the data.
 nyc_(is_out_of_
		
			nyc_(is_out_of_08-20-2012 08:14 AM
@Scherni wrote:
By no standard I ment the protocoll to communicate with the device and to get the data.
There are protocols for communicating to the device and getting the data. They are RS232 and RS485.
 Mark_Yedinak
		
			Mark_Yedinak
		
		
		 
		
		
		
		
		
	
			08-20-2012 11:03 AM
You will have to go through the specification and define your messages accordingly. There is no simple solution to this unless you happen to find someone who has already written the code. From a quick glance at the specification it isn't that bad and it is fairly well defined. I would create a VI for each command. In addition I would probably create a VI (generic message builder) to add the start, end and CRC values to the frame. Your individual command VIs would call the generic message builder to complete the command message. You can use string constants as inputs into a Format String VI and simply add the variable data to it there. I would recommend that use display the string constants in '\' mode to make it easier for you to add the binary data which defines the protocol.
08-22-2012 05:45 AM
Thanks for your help!
I managed to get everything going.
Scherni