Preconditions

• SGC500 software version: 3.02.01 or higher
• Connect Liquiline Modbus TCP device to LAN network. Make sure port 502 is accessible.
• The field device health data must be integrated in Netilion.

Configuration for Analytics service

Modbus TCP protocol does not provide field device information by default. An asset cannot be created fully automatically. Device information must be added manually as described here:

• On page Edge Device Details create a new Field Gateway / Device.
• Select type "Liquiline Platform".
• Add a name (displayed on field gateway / device pages only).
• Add IP address of the Modbus TCP Liquiline device.
• Press button Save.

Within next 20 minutes the edge device will read the new field gateway / device configuration.

An asset will be created based on serial number read from the device.

A tag will be created based on tag information read from the device and linked to asset.

For all connected sensors an asset will be created with the serial number of the sensor and an instrumentation with the sensor tag. The sensor assets are assigned to the Liquilline as child assets. The tag is linked to the corresponding asset.

Configuration for Value

With Modbus devices, measured values are stored in specific registers. The following Modbus information from the field device must be available for configuration and varies for each device type:

• Modbus command
• register number
• data type
• Netilion unit code (Value service only)

Modbus configurations are imported as a file on field gateway / device page created above. The format is json and requires the file extension mbconf.

{
  "config_version": 1,
  "config_type": "specifications",
  "configuration": {
    <see chapter value service related below>
    }
  }
}

file name e.g.: example.mbconf

Within next 20 minutes the edge device will read the Modbus configuration and collect data. With configuration changes we have the same behavior.

Value service related

The following example shows the configuration of a measured value:

• Modbus command: Input
• register number: 210
• data type: Float
• byte order: 1-0-3-2
• Netilion unit code: degree Celsius

{
  "config_version": 1,
  "config_type": "specifications",
  "configuration": {
    "config.modbus_3_210": {
    "value": "0;Temperature;degree_celsius;1;10"
    }
  } 
}

The configuration key is defined as: config.modbus_<modbus command number>_<register number>

from our example: config.modbus_3_210

The configuration value is defined as:

<channel number>;<value name>;<netilion unit code>;<endpoint>;<datatype>

from our example: 0;Temperature;degree_celsius;1;10

*The DateTime format is based on Liquiline platform. In case the device uses another formatting for date and time SGC500 does not support this.

Status information

Each Modbus configuration will be checked from the edge and a status provided. The status information is stored in the same file in which the configurations are made. They are available via export functionality on field gateway / device page.

The list below shows possible status information:

Note: The listed checks are only related to configurations issues. Problems that may occur during the register query are not listed. The status would still be OK.

To see the correct unit symbols open excel and import the csv file.