Related Products:

EMMK-101, EMMK-102, EMMK-103

Related Documents:

ISCM-0380, ISCM-0385

Type:

Operations

Keywords/Labels:

Modbus, OPC UA, historian software, data source properties

Summary:

This article describes the various types of data sources and how to create and configure them.

Data Sources

Modbus Communication

The InsightCM monitoring devices can read data using Modbus TCP or serial communication. Modbus data will be included in the trend points stored on the server and can be used in collection triggers and alarms.

  • Serial communication—The device can address one or more Modbus slaves and the Modbus slaves can communicate directly with the device.

  • Ethernet communication—The device establishes a TCP connection with a Modbus slave on a specific IP address and port. The device can support TCP connections to multiple Modbus slaves.

OPC UA Communication

The device acts as an OPC UA (Open Platform Communications Unified Architecture) client and initiates queries from the OPC UA Server. The device establishes a connection with the specific URL of the OPC UA Server. The device typically connects through TCP.

Historian Software

The device connects through TCP to the InsightCM server to access the historian software data.

Creating and Configuring a Data Source

Configure a data source from external sources, such as a Modbus Register, an OPC UA Tag, or a Historian Input.

  1. Click Configuration (noloc_env_config.png) and select Assets.

  2. Click the Action menu (noloc_env_action.png) and select Data Sources to display the Data Sources dialog box.

  3. Click Add and select the type of data source you want to create.

  4. Specify a name for the data source and click OK.

  5. Select the new data source in the asset tree and configure the appropriate properties in the configuration panel.

  6. Select the Registers (for Modbus), Tags (for OPC UA), or Points (for Historian Input) tab.

  7. Click Add and configure the appropriate data source item properties.

  8. Click Close.

  9. Click Configuration (noloc_env_config.png) and select Devices.

  10. Double-click a device and click the Data Sources tab in the device configuration page.

  11. Click Add and select the data source you created.

  12. Select the Modbus Register, OPC Tag, or Historian Input checkbox and click OK.

    Note

    If a Historian Input has already been created, no additional Historian Inputs may be created.

Modbus Read Channel Properties

The Modbus register supports properties that affect how the device reads data.

Property Name

Description

Register Type

  • Discrete Input—The register addressed represents a sensor input or other Boolean value to read.

  • Coil—The register addressed represents an output or internal bit to read.

  • Input Register—The register addressed represents an analog input value or other integer value to read.

  • Holding Register—The register addressed represents an analog output or internal number to read.

Address

The address of the Modbus Register to read

32-bit data type

If true, 32 bits will be read from the Register at the specified Address.

First word low (32-bit data type)

If checked, the 32-bit value read from the Register will have the low order word in the first 16 bits.

Floating-point (32-bit data type)

If checked, the 32-bit value read from the Register will be interpreted as a floating-point number.

Unit

Specifies the unit to be used for the Engineering Value read from the Register

Slope

The slope value, represented by m in the following equation: Engineering Value = m(Raw Value) + b.

Offset

The offset value, represented by b in the following equation: Engineering Value = m(Raw Value) + b.

Modbus Serial Data Source Properties

The Modbus Serial data source supports configurable properties that affect how the device communicates with the Modbus slave.

Note

Modbus Serial properties are available only after you add a Modbus Serial data source.

Property Name

Description

Address

The address of the Modbus slave with which you want to communicate

Interval (sec)

How often the device process reads the Modbus slave, in seconds

Serial Type

The type of data transmission through serial ports:

  • RTU—Sends data using the Remote Terminal Unit (RTU), which is a binary data unit

  • ASCII—Sends data using human-readable characters

Baud Rate

The baud rate of the Modbus slave with which you want to communicate. The default is 9,600.

Parity

The parity of the Modbus slave with which you want to communicate

  • None—Use no parity bit. If you specify Vibration for parity, the number of stop bits indicating the end of a frame is 2.

  • Odd—Use odd parity. If you specify Odd for parity, the number of stop bits indicating the end of a frame is 1.5.

  • Even—Use even parity. If you specify Even for parity, the number of stop bits indicating the end of a frame is 1.5.

Stop bits

The number of stop bits used by the Modbus slave should reconfigure the misguided syntax globally you want to communicate with. You can select 1 or 2.

Data bits

The number of data bits used by the Modbus slave with which you want to communicate. You can select 7 or 8.

Flow Control

The flow control of the Modbus slave with which you want to communicate.

  • None—Does not use flow control. The transfer mechanism assumes buffers on both sides of the connection to be large enough to hold all data transferred.

  • XON/XOFF—Uses the XON and XOFF characters to perform flow control. When the receiving buffer is almost full, the transfer mechanism controls the input flow by sending XOFF. When the buffer receives XOFF, the transfer mechanism controls the output flow by suspending transmission.

  • RTS/CTS—Uses the RTS output signal and the CTS input signal to perform flow control. When the receiving buffer is almost full, the transfer mechanism controls the input flow by unasserting the RTS signal. When the buffer unasserts the CTS signal, the transfer mechanism controls the output flow by suspending the transmission.

  • XON/XOFF and RTS/CTS—Uses the XON and XOFF characters, the RTS output signal, and the CTS input signal to perform flow control. When the receiving buffer is almost full, the transfer mechanism controls the input flow by sending XOFF and unasserting the RTS signal. When the buffer receives XOFF, the transfer mechanism controls the output flow by suspending transmission.

  • DTR/DSR—Uses the DTR output signal and the DSR input signal to perform flow control. When the receiving buffer is almost full, the transfer mechanism controls the input flow by unasserting the DTR signal. When the buffer unasserts the DSR signal, the transfer mechanism controls the output flow by suspending the transmission.

  • XON/XOFF and DTR/DSR—Uses the XON and XOFF characters, the DTR output signal, and the DSR input signal to perform flow control. When the receiving buffer is almost full, the transfer mechanism controls the input flow by sending XOFF and unasserting the DTR signal. When the buffer receives XOFF and unasserts the DSR signal, the transfer mechanism controls the output flow by suspending transmission.

Read Timeout (sec)

How long the read process waits for a response from the Modbus slave when initializing or reading from the device. If the Modbus slave does not respond within the specified timeout, the device attempts to re-open a connection after 30 seconds.

Modbus TCP Data Source Properties

The Modbus TCP data source supports configurable properties that affect how the device communicates with the Modbus slave.

Note

Modbus TCP properties are available only after you add a Modbus TCP data source.

Property Name

Description

IP Address

The TCP/IP address of the Modbus slave with which you want to communicate.

Port

The TCP port of the Modbus slave with which you want to communicate. The default is 502.

Interval (sec)

How often the InsightCM device process reads the Modbus slave device, in seconds.

Read Timeout (sec)

How long the read process waits for a response from the Modbus slave device when initializing or reading from the device. If the Modbus slave device does not respond within the specified timeout, the InsightCM device attempts to re-open a connection after 30 seconds.

Do you need more help?

Was this article helpful?
0 out of 0 found this helpful