Like the GSI channel, AirVision simplifies the configuration process by automatically creating and downloading the data logger’s server configuration file in the background. Since Modbus instruments have additional networking information that needs to be known, the user must first create an instance of the Modbus instrument in the Data Source Details editor usingthe Add Modbus Instrument selection. Once this is done, you can select the configured connected instrument and the desired internal parameter. AirVision maintains a catalog of manufacturer's Modbus register codes.

To create the instrument, go to the Data Source Details editor, select the appropriate data logger object in the tree, and select Add->Logger Modbus Instrument on the ribbon.



The user must then enter the following fields:

• Instrument Name- a user-defined label for the instrument
• Driver Type - select from picklist of known analyzers
• Modbus Code- also known as the Modbus Device ID, this is set in the analyzer, and is some value from 1-255
• Modbus Command Type- defines which Modbus command is used to read data from the analyzer (3 for TECO, 4 for API, consult instrument documentation for other brands)
• Poll Interval- how often data should be requested from the instrument, in tenth of a second increments
• TCP Address- IP address of the instrument, as viewed from the logger’s perspective
• TCP Port - Port used by the instrument for Modbus requests, usually “502”.

Once the instrument is configured and saved, the user can then use the “Add Channel->Modbus” in the Data Source Details editor. The configuration under the “Misc” tab is as simple as selecting the define analyzer, and the desired parameter in the instrument from a picklist.



If a desired parameter does not exist in the picklist, contact Agilaire Support (support@agilairecorp.com) and we can easily add it to your system.