AirSentry System Data Integration Options

Section 1. General Information

A common question about the AirSentry-IMS is how to integrate the data in LabVIEW with a customer's existing SPC or data collection system. There are four options available on the AirSentry System for moving data from the AirSentry to an external location. Three of these options are automated while one is completely manual.

This document seeks to explain what these options are. It is not intended to explain how they work or how to set them up. Each option is explained below with a brief synopsis of the technology behind it. All systems have the ability to be attached to a company network, and is the responsibility of the end user to configure.

Section 2. Options

Manual Data Export

Every installation of AirSentry System software include a Historical Data (or Trend) Viewer (HDV/HTV). By creating custom Trend Views within the HDV, the end user can export different ranges of data to a CSV (Comma Separated Values) file. This CSV file can then be imported into a spreadsheet or database program, such as Microsoft's Excel or Access. Each CSV file may be stored locally on the AirSentry, or moved to another system via a floppy disk, CD-R, USB flash drive, or over a network connection.

This option is completely manual, requiring user interaction each time an export is done. User interaction may take place at the system directly, or it may take place via a remote desktop streaming session. Remote desktop streaming may be used with such software as VNC, Remote PC, the built in desktop streaming software of Windows XP, or any other remote streaming software.

Modbus Slave Output

All AirSentry systems include a Modbus Slave Output plug-in. Modbus is a messaging protocol developed by Modicon in 1979. It is a de facto standard that is openly published and royalty free. Modbus allows various devices to communicate with each other in a master-slave, or client-server, relationship using a series of numerical addresses. Modbus RTU is a binary, compact representation of data being exchanged between the two systems, while Modbus ASCII is a more verbose, human readable format.

The AirSentry System uses Modbus RTU over a serial connection. It is normally output on COM 2 of the system, which is accessible through a DB9 connector on the back of the AirSentry. Once configured, the Modbus Slave Output provides data automatically, with little user intervention. The Modbus Slave Output option does not allow any control over the AirSentry; it is meant for data output only.

Click here for more information about the Modbus protocol

OPC

OPC (OLE for Process Control) is an industry standard created with the collaboration of a number a leading worldwide automation and hardware software suppliers working in cooperation with Microsoft. The organization that manages this standard is the OPC Foundation. The Foundation has over 220 members from around the world, including nearly all of the world's major providers of control systems, instrumentation, and process control systems.

Based on Microsoft's OLE (Object Linking and Embedding), COM (Component Object Model) and DCOM (Distributed Component Object Model) technologies, OPC consists of a standard set of interfaces, properties, and methods for use in process-control and manufacturing-automation applications. The Active X/COM technologies define how individual software components can interact and share data. OPC provides a common interface for communicating with diverse process-control devices, regardless of the controlling software or devices in the process.

All AirSentry systems use OPC (Ole Process Control) to process data within LabVIEW. As a result, OPC is available by default on all AirSentry systems. Particle Measuring Systems commonly installs Facility Net on AirSentry systems, to store data, utilizing the OPC server in LabVIEW.

Facility Net provides both an OPC Server and an OPC Client. Both the client and server support OPC Data Access Custom Interface Standard 2.03. Since the OPC Data Access Custom Interface Standard 1.0a is a subset of the 2.03 standard, the 1.0a is also supported by Facility-Net. Information on the OPC specifications and standards can be found at http://www.opcfoundation.org/. The specifications and standards are essential for understanding how to use OPC.

Once configured, the OPC option provides data automatically, with little user intervention. The OPC option does not allow any control over the AirSentry; it is meant for data output only.

SECS/GEM

SECS/GEM (SEMI Equipment Communications Standard/Generic Equipment Model) is a purchased interface option available for current AirSentry systems. The purpose of this interface is to allow a host computer using SECS-II messaging over a SECS-I or HSMS-SS link to perform AMC (Airborne Molecular contamination) monitoring scenarios using the AirSentry-IMSTM System. This interface will allow the host computer to measure AMC concentrations of multiple target compounds at multiple locations, via event reporting, trace data reporting, and query of selected status or other variable data.

SECS/GEM can be used over TCP-IP or Serially. Once configured, the SECS/GEM option provides data automatically, with little user intervention. The SECS/GEM option does not allow any control over the AirSentry; it is meant for data output only.

Contact us if you need more information or have questions.