Preconditions

• SGC500 software version: 3.03.00 or higher
• Connect IO-Link Gateway to LAN network. Make sure port 502 is accessible.
• The field device health data for IO Link must be integrated in Netilion.

Netilion services integration

Analytics

Assets are not automatically created from SGC500 for Modbus TCP devices. Serial numbers are specified in the Modbus TCP configuration and assets are then created from SGC500 accordingly. The field device type can then be set manually in Netilion.

Health

There is no health support for IO-Link devices via the Field Edge SGC500.

Value

Required values can be configured in Modbus TCP configuration.
Note: Some devices provide values in a condensed format, which needs a conversion e.g. with factor 0.1.

Supported Endress+Hauser devices:

The following table shows which device measurements are suitable for configuration with the SGC500, based on information from the manuals. 

As of: June 2024

Note: The list does not represent an integration test status.

Integrate via a Turck TBEN IO-Link Master

Important pre-requisites:

The protocol used by the PLC next to the IO-Link master should be selected as default. Do not use the automatic protocol detection of the IO-Link master.

Background: In case the Field Edge SGC500 accesses the IO-Link Master before the PLC the protocol for cyclic communication would be set to Modbus and communication to PLC may be disturbed.

Depending on the data structure from the IO Link device the byte order configured in the master is important.

Configure the Field Edge SGC500 

• Log in to Netilion and navigate to the Edge Devices page. Select the Field Edge that should collect the values from the Turck TBEN IO-Link master. 
• Create a new “Field Gateway / Device” of type Modbus TCP Device. In the form enter the IP address, the serial number and the tag of the Turck TBEN IO-Link master. 
• Create a Modbus configuration file containing the mapping.

For a detailed overview about the creation of the Modbus configuration file, see the help article “Commissioning-of-a-Modbus-TCP-Device-in-Netilion". For the register mapping of the Turck TBEN IO-Link master see the related manual. 

Example configuration

As an example, we connected 2 IO-Link devices to the Turck TEBN IO-Link master. On IO-Link port 1 we have a Cerabar PMP21 and on IO-Link port 2 we have a Micropilot FMR43 connected. From the manual of the Turck master, we see that the process input data from IO-Link port 1 can be found in the register area 0x02 – 0x11 and for IO-Link port 2 in the register area 0x12 – 0x21. From the field device manuals, we know how the process data is provided. With this knowledge the Modbus configuration file would look like this:

{ 
  "config_version": 1, 
  "config_type": "specifications", 
  "configuration": { 
    "config.modbus_3_2": { 
    "value": "SerialCerabar;Pressure;pounds_per_square_inch;1;10" 
    }, 
    "config.modbus_3_18": { 
    "value": "SerialMicropilot;Level_Linearized;convert_normalized_level;1;10" 
    }, 
    "config.modbus_3_20": { 
    "value": "SerialMicropilot;Distance;convert_normalized_level;1;10" 
    } 
  }, 
  "byte_order": 1 
}