Tben S2 4iol

Your Global Automation Partner
TBEN-S2-4IOL
IO-Link Master Module
Instructions for Use
2 Hans Turck GmbH & Co. KG | T +49 208 4952-0 | F +49 208 4952-264 | [email protected] | www.turck.com
Table of Contents
1 About These Instructions .................................................................................................................. 7
1.1 Target groups................................................................................................................... 7
1.2 Explanation of symbols used ........................................................................................ 7
1.3 Additional documents.................................................................................................... 7
1.4 Feedback about these instructions.............................................................................. 7
2 Notes on the Product ......................................................................................................................... 8
2.1 Product identification..................................................................................................... 8
2.2 Scope of delivery ............................................................................................................. 8
2.3 Legal requirements......................................................................................................... 8
2.4 Manufacturer and service .............................................................................................. 8
3 For Your Safety.................................................................................................................................... 9
3.1 Intended use..................................................................................................................... 9
3.2 General safety notes ....................................................................................................... 9
4 Product Description ......................................................................................................................... 11
4.1 Device overview ............................................................................................................ 11
4.1.1 Display elements............................................................................................................................ 11
4.2 Properties and features................................................................................................ 12
4.3 Operating principle....................................................................................................... 12
4.4 Functions and operating modes ................................................................................ 12
4.4.1 Multiprotocol technology........................................................................................................... 12
4.4.2 IO-Link channels............................................................................................................................. 13
4.4.3 Configurable digital channels – functions............................................................................ 13
5 Mounting............................................................................................................................................ 14
5.1 Combine TBEN-S modules for mounting.................................................................. 14
5.1.1 Combine TBEN-S modules for composite mounting to a mounting plate............... 14
5.1.2 Combine TBEN-S modules for single and composite mounting on a DIN rail ........ 15
5.2 Attach TBEN-S modules to a mounting plate .......................................................... 16
5.3 Mounting TBEN-S modules on a DIN rail (TS35)...................................................... 16
5.4 Mounting the device outdoors................................................................................... 16
5.5 Grounding the device................................................................................................... 17
5.5.1 Equivalent wiring diagram and shielding concept ........................................................... 17
5.5.2 Fieldbus and I/O level shielding ............................................................................................... 17
5.5.3 Grounding the device – I/O and fieldbus level ................................................................... 18
5.5.4 Grounding the device – mounting on a DIN rail ................................................................ 19
5.5.5 Grounding the device – mounting on a mounting plate................................................ 19
6 Connecting ........................................................................................................................................ 20
6.1 Connecting the device to Ethernet ............................................................................ 20
6.2 Connecting the supply voltage .................................................................................. 21
6.2.1 Supply concept............................................................................................................................... 22
6.3 Connecting IO-Link devices and digital sensors ..................................................... 22
7 Commissioning ................................................................................................................................ 23
7.1 Setting the IP address................................................................................................... 23
7.2 ARGEE/FLC ...................................................................................................................... 25
7.3 Commissioning an IO-Link device with IO-Link V1.0.............................................. 25
V01.00 | 2019/12 3
Table of Contents
7.4 Commissioning an IO-Link device with IO-Link V1.1.............................................. 26

7.5 Read in connected IO-Link devices: topology scan in the DTM ........................... 28
7.6 Commissioning the device in PROFINET................................................................... 29
7.6.1 PROFINET IO device model......................................................................................................... 29
7.6.2 Device model – TBEN-S2-4IOL................................................................................................... 30
7.6.3 Address setting in PROFINET ..................................................................................................... 30
7.6.4 FSU – Fast Start-Up (prioritized startup)................................................................................ 31
7.6.5 MRP (Media Redundancy Protocol)......................................................................................... 31
7.6.6 User data for acyclic services ..................................................................................................... 31
7.6.7 The IO-Link function block IOL_CALL..................................................................................... 34
7.7 Connecting the device to a Siemens PLC in PROFINET .......................................... 38
7.7.1 Installing the GSDML file ............................................................................................................. 39
7.7.2 Connecting the devices to the PLC ......................................................................................... 40
7.7.3 Assigning the PROFINET device name ................................................................................... 41
7.7.4 Setting the IP address in TIA Portal ......................................................................................... 42
7.7.5 Configuring device functions .................................................................................................... 42
7.7.6 Going online with the PLC.......................................................................................................... 45
7.7.7 PROFINET – mapping ................................................................................................................... 45
7.7.8 Use the IO_LINK_DEVICE function block in TIA Portal...................................................... 46
7.8 Commissioning the device in Modbus TCP .............................................................. 53
7.8.1 Implemented Modbus functions ............................................................................................. 53
7.8.2 Modbus registers ........................................................................................................................... 53
7.8.3 Data width ........................................................................................................................................ 56
7.8.4 Register mapping........................................................................................................................... 57
7.8.5 Error Behavior (watchdog).......................................................................................................... 58
7.9 Commissioning the device in EtherNet/IP................................................................ 59
7.9.1 Common EtherNet/IP features.................................................................................................. 59
7.9.2 EDS files and catalog files............................................................................................................ 59
7.9.3 Device Level Ring (DLR) ............................................................................................................... 59
7.9.4 Diagnostic messages via process data................................................................................... 59
7.9.5 EtherNet/IP standard classes ..................................................................................................... 60
7.9.6 VSC-Vendor Specific Classes ...................................................................................................... 81
7.10 Connecting the devices to a Rockwell PLC with EtherNet/IP................................ 92
7.10.1 Adding the devices from the catalog files to the new project ...................................... 93
7.10.2 Configuring the device in RS Logix ......................................................................................... 95
7.10.3 Parameterizing the device.......................................................................................................... 96
7.10.4 Going online with the PLC.......................................................................................................... 97
7.10.5 Reading process data ................................................................................................................... 99
8 Parameterizing and Configuring................................................................................................. 100
8.1 Parameters................................................................................................................... 100
8.1.1 Adapting process data mapping........................................................................................... 105
8.1.2 PROFINET parameters ............................................................................................................... 106
8.2 IO-Link functions for acyclic communication ....................................................... 107
8.2.1 Port functions for Port 0 (IO-Link Master)........................................................................... 107
9 Operating ......................................................................................................................................... 112
9.1 Process input data...................................................................................................... 112
9.2 Process output data ................................................................................................... 114
9.3 LED displays................................................................................................................. 115
9.4 Software diagnostic messages ................................................................................ 116
9.4.1 Status- and control word.......................................................................................................... 116
9.4.2 Diagnostic telegram................................................................................................................... 118
9.4.3 PROFINET diagnostics ............................................................................................................... 120
9.5 Using the data storage mode................................................................................... 121
9.5.1 Parameter ”data storage mode” = activated .................................................................... 121
9.5.2 Parameter ”data storage mode” = read in ......................................................................... 123
9.5.3 Parameter ”data storage mode” = overwrite.................................................................... 123
9.5.4 Parameter ”data storage mode” = deactivated, clear.................................................... 123
10 Troubleshooting ............................................................................................................................. 124
10.1 Eliminate parameterization errors.......................................................................... 124
11 Maintenance.................................................................................................................................... 125
11.1 Carry out firmware update via FDT/DTM............................................................... 125
12 Repair................................................................................................................................................ 128
12.1 Returning devices....................................................................................................... 128
13 Disposal ............................................................................................................................................ 128
14 Technical Data................................................................................................................................. 129
V01.00 | 2019/12 5
Table of Contents
1 About These Instructions
These operating instructions describe the structure, functions and the use of the product and
will help you to operate the product as intended. Read these instructions carefully before using
the product. This is to avoid possible damage to persons, property or the device. Retain the in-
structions for future use during the service life of the product. If the product is passed on, pass
on these instructions as well.
1.1 Target groups

These instructions are aimed at qualified personal and must be carefully read by anyone
mounting, commissioning, operating, maintaining, dismantling or disposing of the device.
1.2 Explanation of symbols used

The following symbols are used in these instructions:
DANGER
DANGER indicates a dangerous situation with high risk of death or severe injury if
not avoided.
WARNING
WARNING indicates a dangerous situation with medium risk of death or severe in-
jury if not avoided.
CAUTION
CAUTION indicates a dangerous situation of medium risk which may result in minor
or moderate injury if not avoided.
NOTICE
NOTICE indicates a situation which may lead to property damage if not avoided.
NOTE
NOTE indicates tips, recommendations and useful information on specific actions
and facts. The notes simplify your work and help you to avoid additional work.
u CALL TO ACTION
This symbol denotes actions that the user must carry out.
a RESULTS OF ACTION
This symbol denotes relevant results of actions.
1.3 Additional documents

The following additional documents are available online at www.turck.com
n Data sheet
n EU Declaration of Conformity
n Commissioning manual IO-Link devices
1.4 Feedback about these instructions

We make every effort to ensure that these instructions are as informative and as clear as pos-
sible. If you have any suggestions for improving the design or if some information is missing in
the document, please send your suggestions to [email protected].
V01.00 | 2019/12 7
Notes on the Product
Manufacturer and service
2 Notes on the Product

2.1 Product identification
These instructions apply for the following IO-Link master module:
n TBEN-S2-4IOL
2.2 Scope of delivery

The scope of delivery includes:
n TBEN-S2-4IOL
n Closure caps for M8 female connectors
n Label clips
2.3 Legal requirements

The device falls under the following EU directives:
n 2014/30/EU (electromagnetic compatibility)
n 2011/65/EU (RoHS Directive)
2.4 Manufacturer and service

Hans Turck GmbH & Co. KG
Witzlebenstraße 7
45472 Mülheim an der Ruhr
Germany
Turck supports you with your projects, from initial analysis to the commissioning of your applic-
ation. The Turck product database contains software tools for programming, configuration or
commissioning, data sheets and CAD files in numerous export formats. You can access the
product database at the following address: www.turck.de/products
For further inquiries in Germany contact the Sales and Service Team on:
n Sales: +49 208 4952-380
n Technology: +49 208 4952-390
Outside Germany, please contact your local Turck representative.
3 For Your Safety
The product is designed according to state-of-the-art technology. However, residual risks still
exist. Observe the following warnings and safety notices to prevent damage to persons and
property. Turck accepts no liability for damage caused by failure to observe these warning and
safety notices.
3.1 Intended use

These devices are designed solely for use in industrial areas.
The multiprotocol I/O module TBEN-S2-4IOL is an IO-Link master according to IO-Link specifica-
tion V1.1 and can be can be operated in the three Ethernet protocols PROFINET, Ethernet/IP
and Modbus TCP. The module detects the bus protocol automatically during the start-up.
The IO-Link master module TBEN-S2-4IOL has four IO-Link channels. Up to four IO-Link sensors
or IO hubs with IO-Link can be connected to the M12 sockets. In addition, up to 8 digital
sensors can be connected directly it. When using I/O hubs, it is possible to connect up to 64 di-
gital sensors per device.
The devices may only be used as described in these instructions. Any other use is not in accord-
ance with the intended use. Turck accepts no liability for any resulting damage.
3.2 General safety notes

n The device may only be assembled, installed, operated, parameterized and maintained by
professionally-trained personnel.
n The device may only be used in accordance with applicable national and international regu-
lations, standards and laws.
n The device only meets the EMC requirements for industrial areas and is not suitable for use
in residential areas.
n Change the default password of the integrated web server after the first login. Turck recom-
mends using a secure password.
V01.00 | 2019/12 9
System Description IO-Link
General safety notes
4 Product Description
The devices are designed in a fully encapsulated housing with degree of protection IP65/IP67/
IP69K.
The TBEN-S2-4IOL IO-Link Master Module has four IO-Link ports for connecting IO-Link devices.
In addition to the four IO-Link channels, four universal digital DXP-channels (PNP) are available.
The four IO-Link channels can be parameterized independently of each other and operated
either in IO-Link mode or in SIO mode (DI).
With Turck's "Simple IO-Link Device Integration (SIDI)", IO-Link devices can be directly integ-
rated into PROFINET via the GSDML file of the TBEN-S2-4IOL.
The four digital channels are designed as DXP-channels and can therefore be parameterized as
in- or output.
For the connection of IO-Link devices and digital sensors and actuators four 5-pole M12 sockets
are provided. The power supply connectors are designed as 4-pole M8 connectors.
4.1 Device overview
28 24 32
P1 C3 C2 C1 C0 X1
ø 4.6
32
17.9
P2 X2
132
144.3
Fig. 1: Dimensions TBEN-S2-4IOL
4.1.1 Display elements

The device has the following LED indicators:
n Power supply
n Group and bus errors
n Status
n Diagnostics
V01.00 | 2019/12 11
Product Description
Functions and operating modes
4.2 Properties and features

n Fibre-glass reinforced housing
n Shock and vibration tested
n Fully potted module electronics
n Degree of protection IP67/IP69K
n UV-resistant according to DIN EN ISO 4892-2
n Metal connectors
n 4 IO-Link ports Class A
n Multiprotocol functionality: PROFINET Device, EtherNet/IP Device, Modbus TCP Slave
n 4 universal DXP channels
n PROFINET:
– Conformance Class B PA
– Simple IO-Link Device Integration (SIDI)
– Conformance according to PROFINET specifikation V2.35
– System redundancy S2
– Network load class 3
n EtherNet/IP:
– Support of the IO-Link Parameter Object for asynchronous services (IO-Link CALL)
– Predefined in- and oputput assemblies
4.3 Operating principle

The IO-Link master module TBEN-S2-4IOL connects IO-Link sensors and actuators with the
higher-level control system. The device has an Ethernet interface and fieldbus-independent I/O
electronics with IO-Link master functionality (Class A ports). Via the Ethernet interface, the IO-
Link master is connected to an (existing) Ethernet network as an EtherNet/IP device, Modbus
TCP slave or PROFINET device. During operation, the process data is exchanged between Ether-
net and IO-Link. In addition to the IO-Link master ports, the devices can process signals from
sensors and actuators via four configurable digital channels.
4.4 Functions and operating modes

4.4.1 Multiprotocol technology
The devices can be used in the following three Ethernet protocols:
n Modbus TCP
n EtherNet/IP
n PROFINET
The required Ethernet protocol can be detected automatically or determined manually.
Automatic protocol detection

A multi-protocol device can be operated without intervention of the user (which means,
without changes in the parameterization) in all of the three Ethernet protocols mentioned.
During the system start-up phase (snooping phase), the module detects which Ethernet pro-
tocol requests a connection to be established and adjusts itself to the corresponding protocol.
After this an access to the device from other protocols is read-only.
Manual Protocol Selection

The user can also define the protocol manually. In this case, the snooping phase is skipped and
the device is fixed to the selected protocol. With the other protocols, the device can only be ac-
cessed read-only.
Protocol Dependent Functions
The device Supported the following Ethernet protocol specific functions:
PROFINET
n FSU - Fast Start-Up (prioritized startup)
n Topology discovery
n Address assignment via LLDP
n MRP (Media Redundancy Protocol)
EtherNet/IP
n QC – QuickConnect
n Device Level Ring (DLR)
4.4.2 IO-Link channels

The IO-Link master module has four Class A IO-Link channels.
The four IO-Link channels can be parameterized independently of each other and operated
either in IO-Link mode or in SIO mode (DI).
4.4.3 Configurable digital channels – functions

The device is provided with four digital channels, which can be configured as inputs or outputs
according to the application requirements. In all, up to four 3-wire PNP sensors or four PNP DC
actuators with a maximum output current of 0.5 A can be connected per input or output.
V01.00 | 2019/12 13
Mounting
Combine TBEN-S modules for mounting
5 Mounting
The device can be mounted on a DIN rail according to EN 60715 (TS35) or screwed onto an
even mounting plate. Both composite and individual assembly are possible.
5.1 Combine TBEN-S modules for mounting

The modules can be mounted individually or in combination as a group of modules on a
mounting plate or DIN rail.
5.1.1 Combine TBEN-S modules for composite mounting to a mounting plate

The TBNN-S0-STD connector serves for composite mounting of TBEN-S modules on a mounting
plate:
Unlock the cover flap at the connector with a flat tool (e.g. screw driver) (1).
Open the flap completely (2).
Connect the module and the connector so that the spring of the connector is inserted
into the groove of the TBEN-S module (3).
Flap back the cover and close it (4). It has to engage audibly.
Repeat steps 1 to 4 until the module group in complete.
1
2
Fig. 2: Step 1 Fig. 3: Step 2

4
5.1.2 Combine TBEN-S modules for single and composite mounting on a DIN rail
The TBNN-S0-DRS adapter serves for single and composite mounting of TBEN-S modules on a
DIN rail.
NOTICE
Incorrect mounting
Missing grounding may cause malfunction
Align the adapters so that the arrow on the locking lever points in the direction
of the M8 Ethernet sockets.
Connect the grounding contact of the adapter with the grounding contact of
the module.
Unlock the cover flap at the connector with a flat tool (e.g. screw driver) (1).
Open the flap completely (2).
Connect the module and the connector so that the spring of the connector engages in
the groove of the module (3).
Flap back the cover and close it (4). It has to engage audibly.
Repeat steps 1 to 4 until the module group in complete.
1
2

4
V01.00 | 2019/12 15
Mounting
Mounting the device outdoors
5.2 Attach TBEN-S modules to a mounting plate

Fasten the module or module composite to a mounting plate with two M4 screws per
device. The maximum tightening torque for the M4 screws is 1.3 Nm
Avoid mechanical stresses.
Optional: Ground the device.
Fig. 10: Mounting the device on a mounting plate
5.3 Mounting TBEN-S modules on a DIN rail (TS35)

For composite or single mounting: Mount connectors to the left and to the right of the
module.
Place the module or module composite on the DIN rail so that the cut-outs in the con-
nector enclose the DIN rail (1).
Avoid mechanical stresses.
Close the rotating bolt of the connector with a screwdriver (2).
Optional: Ground the device.
Fig. 11: Mounting a module composite on a DIN rail
NOTE
To increase stability on the DIN rail, end brackets can be mounted on the right and
left of the module or the module combination.
5.4 Mounting the device outdoors

The device is UV-resistant according to DIN EN ISO 4892-2. Direct sunlight can cause material
abrasion and color changes. The mechanical and electrical properties of the device are not af-
fected.
To avoid material abrasion and color changes: Protect the device from direct sunlight,
e.g. by using protective shields.
5.5 Grounding the device
5.5.1 Equivalent wiring diagram and shielding concept
The equivalent circuit diagrams and shielding concepts of the TBEN-S module variants are
shown in the following figures:
X1 X2
C0
C1
C2
C3
P1 P2
Fig. 12: TBEN-S2-4IOL– equivalent wiring diagram and shielding concept
5.5.2 Fieldbus and I/O level shielding

The fieldbus and the I/O level of the TBEN-S modules can be grounded separately.
1
3
2
4 5
Fig. 13: Fieldbus and I/O level shielding
The grounding ring (2) and the grounding contact (4) are connected to each other and form
the module grounding. The shielding of the I/O level is permanently connected to the module
grounding. The module grounding is only connected to the reference potential of the installa-
tion when the module is mounted.
Shielding Concept of the I/O Modules (I/O Level)

In the case of direct mounting on a mounting plate, the module grounding is connected to the
reference potential of the system via the metal screw in the lower mounting hole (3). If no mod-
ule grounding is desired, the electrical connection to the reference potential must be interrup-
ted, e.g. by mounting the device on an insulated mounting plate.
In the case of DIN rail mounting, the module earthing is led through the side grounding contact
(4) via connector TBNN-S0-DRS to the top-hat rail and connected to the reference potential of
the installation. If no module grounding is desired, the electrical connection to the reference
potential must be interrupted, e.g. by removing the grounding spring on the TBNN-S0-DRS.
V01.00 | 2019/12 17
Mounting
Grounding the device
Shielding Concept of the Fieldbus Level

On delivery, a grounding clip (1) is provided on the connectors for the fieldbus connection (P1,
P2).
In the case of direct mounting on a mounting plate, the shielding of the fieldbus cables is
routed directly to the module grounding via the ground clip and the metal screw in the lower
mounting hole. In the case of DIN rail mounting, the shielding of the fieldbus cables is connec-
ted to the module grounding by the metal screw. The metal screw is supplied with the TBNN-
S0-DRS connector.
If direct grounding of the fieldbus shield is not desired, the grounding clip (1) must be re-
moved. In this case, the fieldbus shield is connected to the module ground via an RC element.
5.5.3 Grounding the device – I/O and fieldbus level

The grounding of the fieldbus level can either be connected directly via the grounding clip (1)
or connected and routed indirectly via an RC element to the grounding of the I/O level. If the
fieldbus grounding is to be routed via an RC element, the grounding clip must be removed.
1
2
3
Fig. 14: Grounding clip (1)
Removing the Grounding Clip: Disconnect the direct grounding of the fieldbus level
Use a slim slotted screwdriver in order to lift up and remove the grounding clamp.
Fig. 15: Use a flat slotted screwdriver to push the grounding clip forwards and remove it.
Mounting the Grounding Clip: Grounding the Fieldbus Level Directly
Place the grounding clamp between the fieldbus connectors by using a screwdriver in
such way that the clamp contacts the metal housing of the connectors.
a The shielding of the fieldbus cables is connected to the grounding clip.
Fig. 16: Mounting the grounding clip
5.5.4 Grounding the device – mounting on a DIN rail

For mounting on a DIN rail with TBNN-S0-DRS connectors: Screw the enclosed metal
screw into the lower mounting hole of the TBEN-S module.
a The shielding of the M8 flanges of the I/O level is connected to the reference potential of
the installation via the DIN rail and the connector.
a With mounted grounding clip: The shielding of the fieldbus is connected to the reference
potential of the installation via the module grounding of the I/O level.
5.5.5 Grounding the device – mounting on a mounting plate

For mounting onto a mounting plate: Fix the TBEN-S module with an M4 metal screw
through the lower mounting hole.
a The shielding of the M8 flanges for the I/O level is connected to the reference potential of
the installation via the M4 metal screw.
a With mounted grounding clip: The shielding of the fieldbus is connected to the reference
potential of the installation via the module grounding of the I/O level.
V01.00 | 2019/12 19
Connecting
Connecting the device to Ethernet
6 Connecting
6.1 Connecting the device to Ethernet
The connection to Ethernet is done via an auto-crossing switch with two 4-pin M8 Ethernet
connectors.
NOTICE
Interchanging of Ethernet- and power cables
Destruction of module electronic
Observe using the correct M8-connectors when connecting Ethernet and power
cables:
- Ethernet: P1 and P2,
- supply voltage: X1and X2
Fig. 17: M8 Ethernet connector
Connect the device to Ethernet according to the pin assignment.
v v
1 = TX + 1 = RX +
4 2 2 = RX + 4 2 2 = TX +
3 1 3 = RX – 3 1 3 = TX –
4 = TX – 4 = RX –
P1 P2
Fig. 18: Ethernet connectors – pin assignment P1 and P2
6.2 Connecting the supply voltage
For the connection to the power supply, the device has two 4-pin M8 connectors. V1 and V2 are
galvanically isolated.
NOTICE
Interchanging of Ethernet- and power cables
Destruction of module electronic
Observe using the correct M8-connectors when connecting Ethernet and power
cables:
- Ethernet: P1 and P2,
- supply voltage: X1and X2
Fig. 19: M8 Ethernet plug connectors for connecting the fieldbus
Connect the device to the voltage supply according to the pin assignment below.
w v
1 BN = V1 (+)
2 4 2 WH = V2 (+) 4 2
1 3 3 BU = GND V1 3 1
4 BK = GND V2
X1 X2
Fig. 20: Pin layout of the Ethernet connections
Meaning
X1 Power feed
X2 Continuation of the power to the next node
V1 Power supply 1 (incl. supply of electronics)
V2 Power supply 2
NOTE
The system voltage (V1) and the load voltage (V2) are supplied and monitored sep-
arately. In case of an undercut of the admissible voltage, the connectors are
switched-off according to the module's supply concept. In case of an undervoltage
at V2, the LED PWR changes from green to red. In case of an undervoltage at V1, the
LED is turned off.
V01.00 | 2019/12 21
Connecting
Connecting IO-Link devices and digital sensors
6.2.1 Supply concept

The TBEN-S2-4IOL is supplied via V2.
V1 = supply of the module electronics and the respective slots
V2 = supply of the respective slots
V1
V2
Fig. 21: Power supply of TBEN-S2-4IOL
6.3 Connecting IO-Link devices and digital sensors

The device has four eight M12 female connectors for connecting IO-Link devices and digital
sensors and actuators. The maximum tightening torque is 0.8 Nm.
NOTICE
Wrong supply of IO-Link devices
Damage to the device electronics
Only supply IO-Link devices with the voltage provided at the M12 connectors.
Connect the sensors and actuators to the device according to the pin assignment.
v
2 1 = V2 +
2 = DXP
1 3 3 = GND V2
4 = C/Q
5 4 5 = n.c.
C0...C3
Fig. 22: Pin assignment C0…C3
Pin Meaning
Pin 1 VAUX2, not short-circuit proof
Pin 2 Digital in- or output (DXP)
Pin 3 Ground (V2)
Pin 4 IO-Link or digital input
Pin 5 Not connected
7 Commissioning
7.1 Setting the IP address
The device is factory set to IP address 192.168.1.254 and does not have a PROFINET device
name. The IP address can be set via the Turck Service Tool, the DTM, the web server, a DHCP
server or PROFINET DCP. The following example shows the setting of the IP address via the
Turck Service Tool. The Turck Service Tool can be downloaded free of charge at
www.turck.com.
Connect the device to a PC via the Ethernet interface.
Launch the Turck Service Tool.
Click Search or press F5.
Fig. 23: Turck Service Tool – Start screen
The Turck Service Tool displays the connected devices.
Fig. 24: Turck Service Tool – found devices
V01.00 | 2019/12 23
Commissioning
Setting the IP address
Click the required device.

Click Change or press [F2].
Fig. 25: Turck Service Tool – select the device to be addressed
NOTE
Clicking the IP address of the device opens the web server.
Change the IP address and if necessary the network mask and gateway.
Accept the changes by clicking Set in device.
Fig. 26: Turck Service Tool – Change device configuration
7.2 ARGEE/FLC
The ARGEE FLC programming software can be downloaded free of charge from
www.turck.com .
The Zip archive "SW_ARGEE_Environment_Vx.x.zip" contains the software and the respective
software documentation.
7.3 Commissioning an IO-Link device with IO-Link V1.0

IO-Link devices in accordance with IO-Link specification V1.0 do not support data storage. If an
IO-Link V1.0 device is used, data storage on the IO-Link port must be deactivated.
Set Data storage mode at the port to deactivated, clear.
Load the parameter changes into the device.
Connect the IO-Link V1.0 device.
a The LED IOL at the IO-Link port is green, IO-Link communication active.
Fig. 27: Example: Deactivate or respectively delete the data storage mode with the DTM
V01.00 | 2019/12 25
Commissioning
Commissioning an IO-Link device with IO-Link V1.1
7.4 Commissioning an IO-Link device with IO-Link V1.1

The data storage of the master should be cleared before a device with a different device type is
connected to an IO-Link port which has already been used before.
The data storage memory of the master can be deleted in two ways:
n Set back the master to factory settings.
n Delete the data storage memory via the parameter Data storage mode.
Resetting the master to factory settings with the DTM

From the Factory settings drop-down menu, select Set to factory settings.
a The DTM resets the device automatically.
Fig. 28: Example: Reset device to factory settings via DTM

Delete the Data Storage Memory via Parameters
Set Data storage mode to deactivated, clear.
Re-activate the data storage, if necessary.
Fig. 29: Example: Deactivate or respectively delete the data storage mode with the DTM
V01.00 | 2019/12 27
Commissioning
Read in connected IO-Link devices: topology scan in the DTM
7.5 Read in connected IO-Link devices: topology scan in the DTM

The Topology Scan in PACTware allows to read-in of an IO-Link configuration down to the IO-
Link device. IO-Link device, known in PACTware, are added to the IO-Link ports of the master.
Either the respective sensor DTMs in PACTware or the sensor IODDs via IODD DTM Configurator
have to be installed.
Fig. 30: PACTware – topology scan
7.6 Commissioning the device in PROFINET
7.6.1 PROFINET IO device model
The technical properties of PROFINET IO devices are defined via their device description file, the
GSDML file. A PROFINET IO device consists of 1…n slots, which can also contain 1…n sub slots.
Sub slots are placeholders for sub modules and establish the interface to the process. Sub mod-
ules can contain parameters, data and diagnostics.
Slot 0 is always reserved as Device Access Point (DAP). The DAP contains the physical interface
to the Ethernet network and represents the device. The other slots and sub slots represent the
other device functions. The structure is defined by the manufacturer of field devices. It is not
necessary that every slot or respectively sub slot is related to physical functions. The allocation
of the slots and sub slots and thus the assignment of functions (operation mode, diagnostics,
etc.) is done in the configuration software of the PROFINET controller. This device model allows
manufacturers to design modular and flexible decentral field devices. Users are flexible in con-
figuring decentralized field devices.
Fig. 31: TIA-Portal – assignment of the slots and sub slots on the example of an TBEN-S1-8DXP
V01.00 | 2019/12 29
Commissioning
Commissioning the device in PROFINET
7.6.2 Device model – TBEN-S2-4IOL

The TBEN-S2-4IOL provides 4 parameterizable I/O-Link-channels and 4 universal I/O-channels
(DXP). In addition to that, 3 virtual channels are provided via GSDML in PROFINET. Those chan-
nels are used to map the different diagnostic and status (IO-Link and VAUX diagnostics, IO-Link
Events, module status) data into the master's process image .
Fig. 32: TBEN- S2- 4IOL – slot overview in TIA-Portal
A Basic slot for e. g. DXP-channels and Data Valid Signal

B IO-Link ports for the configuration with specific IO-Link devices or for gen-
eric configuration
C one slot each for diagnostics and status
7.6.3 Address setting in PROFINET

In IP-based communication, the field devices are addressed by means of an IP address.
PROFINET uses the Discovery and Configuration Protocol (DCP) for IP assignment.
When delivered, each field device has, among other things, a MAC address. The MAC address is
sufficient to give the respective field device a unique name.
The address is assigned in two steps:
n Assignment of a unique plant specific name to the respective field device.
n Assignment of the IP address from the IO-Controller before the system start-up based on the
plant-specific (unique) name.
PROFINET naming convention
The names are assigned via DCP. The device name must meet the requirements of the Domain
Name System (DNS) (see below). The device name is checked for correct spelling during input.
NOTE
The maximum length of the device name is 255 characters according to the specific-
ation. In a Step7 or TIA Portal environment, however, only names with a maximum
length of 127 characters are accepted.
n All device names must be unique.

n Maximum name size: 255 or 127 characters (a...z, 0...9, “-” or “…”)
n Do not use capital letters.
n The name must not begin or end with "-".
n Do not use special characters
n The name must not begin with 0....9 or "port-xyz" (xyz = 0....9).
7.6.4 FSU – Fast Start-Up (prioritized startup)

FSU - Fast Start-Up is not supported by device.
7.6.5 MRP (Media Redundancy Protocol)

The device supports MRP.
MRP is a standardized protocol according to IEC 62439. It describes a mechanism for media re-
dundancy in ring topologies. With MRP, a defective ring topology with up to 50 nodes is detec-
ted and reconfigured in the event of an error. With MRP a trouble-free switch-over is not pos-
sible.
A Media Redundancy Manager (MRM) checks the ring topology of a PROFINET network defined
by the network configuration for functionality. All other network nodes are Media Redundancy
Clients (MRC). In the error-free state, the MRM blocks normal network traffic on one of its ring
ports, with the exception of the test telegrams. The physical ring structure thus becomes a line
structure again at the logical level for normal network traffic. If a test telegram fails to appear, a
network error has occurred. In this case, the MRM opens its blocked port and establishes a new
functioning connection between all remaining devices in the form of a linear network topo-
logy.
The time between ring interruption and recovery of a redundant path is called reconfiguration
time. For MRP, this is a maximum of 200 ms. Therefore, an application must be able to com-
pensate for the 200 ms interruption. The reconfiguration time always depends on the Media
Redundancy Manager (e.g. the PROFINET PLC) and the I/O cycle and watchdog times set here.
For PROFINET, the response monitoring time must be selected accordingly > 200 ms.
It is not possible to use Fast Start-Up in an MRP network.
7.6.6 User data for acyclic services

The acyclic data exchange is by using via Record Data CRs (Communication Relation). Via these
Record Data CRs the reading and writing of the following services is realized:
n Writing of AR data
n Writing of configuration data
n Reading and writing of device data
n Reading of diagnostic data
n Reading of I/O data
n Reading of Identification Data Objects (I&M functions)
V01.00 | 2019/12 31
Commissioning
Acyclic device user data

Index Name Data type Access Comment
Dec. Hex.
1 0x01 Module paramet- WORD read/ Parameter data of the module
ers write (slot 0)
2 0x02 Module designa- STRING read Designation assigned to the
tion module (slot 0)
3 0x03 Module revision STRING read Firmware revision of the module
4 0x04 Vendor ID WORD read Ident no. Turck
5 0x05 Module name STRING read The device name assigned to
the module
6 0x06 Module type STRING read Device type of the module
7 0x07 Device ID WORD read Ident no. of the module
8…23 0x08… reserved - - -
0x17
24 0x18 Module dia- WORD read Diagnostic data of the module
gnostics (slot 0).
25…31 0x19… reserved - - -
0x1F
32 0x20 Input list ARRAY of read List of all module input channels
BYTE
33 0x21 Output list ARRAY of read List of all module output chan-
BYTE nels
34 0x22 Diag. list ARRAY of read List of all I/O-channel dia-
BYTE gnostics
35 0x23 Parameter list ARRAY of read List of all I/O-channel paramet-
BYTE ers
36… 0x24… reserved - - -
28671 0x6FFF
28672 0x7000 Module paramet- WORD read/ Activate field bus protocol
ers write
28673… 0x7001 reserved - - -
45039 …
0xAFEF
45040 0xAFF0 I&M0-functions read Identification & Maintaining
45041 0xAFF1 I&M0-functions STRING[54] read/ I&M Tag function and
write location
45042 0xAFF2 I&M2-functions STRING[16] read/ I&M Installation Date
write
45043 0xAFF3 I&M3-functions STRING[54] read/ I&M Description Text
write
45044 0xAFF4 I&M4-functions STRING[54] read/ I&M Signature
write
45045… 0xAFF5 I&M5 to I&M15- - not supported
45055 … functions
0xAFFF
Acyclic I/O channel user data
Index Name Data type Access Comment
Dec. Hex.
1 0x01 Module specific read/ Parameters of the module
parameters write
2 0x02 Module type ENUM read Contains the module type
UINT8
3 0x03 Module version UINT8 read Firmware version of I/O chan-
nels
4 0x04 Module ID DWORD read Ident number of the I/O
5…9 0x05 … reserved - - -
0x09
10 0x0A Slave controller UINT8 read Version number of the
version array [8] slave controller.
11…18 0x0B… reserved - - -
0x12
19 0x13 Input data specific read Input data of the respective
I/O-channel
20…22 0x14 … reserved - - -
0x16
23 0x17 Output data specific read/ Output data of the respective
write I/O-channel
… … reserved - - -
251 0xFB CAP 1 Record read/ Client access point for class 1
write masters
252 0xFC CAP 2 Record read/
write
253 0xFD CAP 3 Record read/
write
254 0xFE CAP 4 Record read/
write
255 0xFF CAP 5 Record read/ Client access point for class 2
write masters
IM99 (IOL_M)
Name Size Data type Default
setting
IOL_LINK_VERSION 1 byte UINT8 17 (0x11)
IO_LINK_PROFILE_VERSION 1 byte UINT8 0 (0x00)
IO_LINK_FEATURE_SUPPORT 4 byte UINT32 0 (0x00)
NUMBER_OF_PORTS 1 byte UINT8 4 (0x04)
REF_PORT_CONFIG 1 byte UINT8 0 (0x00)
REF_IO_MAPPING 1 byte UINT8 0 (0x00)
REF_IOL_M 1 byte UINT8 0 (0x00)
NUMBER_OF_CAP 1 byte UINT8 5 (0x05)
INDEX_CAP1 1 byte UINT8 251 (0xFB)
V01.00 | 2019/12 33
Commissioning
Name Size Data type Default

setting
INDEX_CAP2 1 byte UINT8 252 (0xFC)
INDEX_CAP3 1 byte UINT8 253 (0xFD)
INDEX_CAP4 1 byte UINT8 254 (0xFE)
INDEX_CAP5 1 byte UINT8 255 (0xFF)
7.6.7 The IO-Link function block IOL_CALL

The IO-Link function block IOL_CALL is specified in the IO-Link specification ”IO-Link Integration
Part 1- Technical Specification for PROFIBUS and PROFINET”.
Depending on the PLC manufacturer, the IO-Link CALL function block can differ from the spe-
cification (for example in the representation or the use of variables).
Fig. 33: IOL_CALL in accordance with IO-Link specification
IOL_CALL– input variables

Designation Data Meaning
acc. IO-Link type
spec.
REQ BOOL A rising edge triggers the send command.
ID DWORD Address of the IO-Link master module
Step 7 Classic
n Start address of the input data of the IO-Link master module.
TIA Portal
n older Siemens CPUs (e.g. CPU 315):
Start address of the input data of the IO-Link master module.
n recent Siemens CPUs (e.g. CPU 1511):
HW identifier of the device's "Basic" slot
INDEX_CAP INT Function block instance: 247 to 254, 255
RD_WR BOOL 0 = read access
1 = write access
ENTITY_PORT INT Address of the IO-Link port to be accessed
FI_INDEX INT Fix value (65098): defines the access to be an IO-Link CALL
IOL_INDEX INT Number of the IO-Link index which has to be read
acc. IO-Link type
spec.
IOL_SUBINDEX INT Definition of a possible sub index.
LEN INT Length of the data to be read/written. This information is not neces-
sary for the Siemens IOL_CALL.
RECORD_IOL_ ANY Source/destination for the data to be read/written.
DATA
IOL_CALL – output variables

acc. IO-Link type
spec.
DONE_VALID BOOL The read or write access has been executed.
BUSY BOOL The read or write access is actually in progress.
ERROR BOOL Error while reading or writing.
STATUS DWORD Communication error status of the acyclic communication [} 35]
IOL_STATUS DWORD IO-Link error messages (in accordance with "IO-Link Integration Part
1- Technical Specification for PROFIBUS and PROFINET" and "IO-Link
Interface and System"), which concern the communication between
IO-Link master and connected devices [} 36].
LEN INT Length of the read data
IOL_CALL – communication error status

The status of the acyclic communication contains 4 byte and is structured as follows:
Byte 3 Byte 2 Byte 1 Byte 0
Manufacturer specific 0×80 Error code/ Vendor specific identi-
identifier (not always Specifies the error as status code fier (not always applic-
applicable) an error of acyclic able)
communication.
Status Code Name Meaning

0xFF000000 TIMEOUT Internal error in the communication with the
0x00FFF00 INVALID_HANDLE module
0x00FFFE00 HANDLE_OUT_OF_
BUFFERS
0x00FFFD00 HANDLE_DESTINATION_
UNAVAILABLE
0x00FFFC00 HANDLE_UNKNOWN
0x00FFFB00 HANDLE_METHOD_
INVALID
0xXX80A0XX MASTER_READ_ERROR Error while reading
0xXX80A1XX MASTER_WRITE_ERROR Error while writing
0xXX80A2XX MASTER_MODULE_ Failure of the IO-Link master, bus failure pos-
FAILURE sible
0xXX80A6XX MASTER_NO_DATA No data received
0xXX80A7XX MASTER_BUSY IO-Link master busy
V01.00 | 2019/12 35
Commissioning
Status Code Name Meaning

0xXX80A9XX MASTER_FEATURE_NOT_ Function not supported by IO-Link master.
SUPPORTED
0xXX80AAXX MASTER_RESOURCE_ IO-Link master not available.
UNAVAILABLE
0xXX80B0XX ACCESS_INVALID_INDEX Index invalid, wrong
INDEX_CAP used
0xXX80B1XX ACCESS_WRITE_ Length of data to be written can not be
LENGTH_ERROR handled from the module, wrong module ac-
cessed.
0xXX80B2XX ACCESS_INVALID_ Wrong slot accessed
DESTINATION
0xXX80B03XX ACCESS_TYPE_CONFLICT IOL_CALL invalid
0xXX80B5XX ACCESS_INVALID_INDEX Error in IOL_CALL sequence
0xXX80B6XX ACCESS_DENIED IOL-Link master module refuses the access.
0xXX80C2XX RESOURCE_BUSY The IO-Link master module is busy or is wait-
0xXX80C3XX RESOURCE_UNAVAILABLE ing for an answer of the connected IO-Link
device.
0xXX8901XX INPUT_LEN_TOO_SHORT The index to be read contains more data than
defined in the input variable "LEN".
IOL_CALL – IOL_STATUS
The IOL_STATUS consists of 2 byte Error Code (IOL_M Error_Codes, according to "IO-Link Integ-
ration Part 1- Technical Specification for PROFIBUS and PROFINET") and 2 byte Error Type (ac-
cording to "IO-Link Interface and System").
IOL_M-Error-Code IOL-Error Type
IOL_M-Error-Code Designation acc. to Meaning

IO-Link Spec.
0x0000 No error No error
0x7000 IOL_CALL Conflict Unexpected write-request, read request expected
0x7001 Wrong IOL_CALL Decoding error
0x7002 Port blocked The accessed port is occupied by another task
… reserved
0x8000 The accessed port is Timeout, IOL master or IOL device port busy
occupied by another
task
0x8001 Wrong index Error: IOL index < 32767 or > 65535 selected
0x8002 Wrong port address Port address not available
0x8003 Wrong port function Port function not available
… reserved
IOL-Error Type Designation acc. to IO- Meaning
Link Spec.
0x1000 COM_ERR Communication error
Possible source: the addressed port is parameterized
as digital input DI and is not in IO-Link mode
0x1100 I_SERVICE_TIMEOUT Timeout in communication, device does not respond
in time
0x5600 M_ISDU_CHECKSUM Master reports checksum error, access to device not
possible
0x5700 M_ISDU_ILLEGAL Device can not respond to master request
0x8000 APP_DEV Application error in the device
0x8011 IDX_NOTAVAIL Index not available
0x8012 SUBIDX_NOTAVAIL Sub-Index not available
0x8020 SERV_NOTAVAIL The service is temporarily not available.
0x8021 SERV_NOTA- Service temporarily not available, device is busy (e. g.
VAIL_LOCCTRL teaching or parameterization of the device via the
master active)
0x8022 SERV_NOTAVAIL_DEVC- Service temporarily not available, device is busy (e. g.
TRL teaching or parameterization of the device via DTM/
PLC etc. active)
0x8023 IDX_NOT_WRITEABLE Access denied, Index cannot be written
0x8030 PAR_VALOUTOFRNG Parameter value out of the valid range
0x8031 PAR_VALGTLIM Parameter value above the upper limit
0x8032 PAR_VALLTLIM Parameter value value below the lower limit
0x8033 VAL_LENOVRRUN Length of data to be written does not match the
0x8034 VAL_LENUNDRUN length defined for this parameter
0x8035 FUNC_NOTAVAIL Function not available in the device
0x8036 FUNC_UNAVAILTEMP Function temporarily unavailable in the device
0x8040 PARA_SETINVALID Invalid parameter: Parameters not consistent with
other parameters in the device.
0x8041 PARA_SETINCONSIST Inconsistent parameters
0x8082 APP_DEVNOTRDY Application not ready, device busy
0x8100 UNSPECIFIC Vendor specific, according to device documentation
0x8101… VENDOR_SPECIFIC
0x8FF
V01.00 | 2019/12 37
Commissioning
Connecting the device to a Siemens PLC in PROFINET
7.7 Connecting the device to a Siemens PLC in PROFINET

The following example describes the connection of the devices to a Siemens PLC in PROFINET
by means of the programming software SIMATIC STEP7 Professional V15 (TIA-Portal).
Used hardware
The following hardware components are used in this example:
n Siemens PLC S7-1500
n IO-Link master TBEN-S2-4IOL with the following configuration:
– Port 1: Turck temperature sensor, TS-530-LI2UPN8X-..., IO-Link V1.0
– Port 2: Channel used as DI
– Port 3: Turck linear position sensor, Li100P0-Q25LM0-..., IO-Link V1.0
– Port 4: Turck IO-Link hub: TBIL-M1-16DXP, IO-Link V1.1
Used software
The following software tools are used in this example:
n SIMATIC STEP7 Professional V15 (TIA-Portal)
n GSDML file for TBEN-S2-4IOL (can be downloaded for free as ZIP archive “TBEN-
S_PROFINET.zip” under www.turck.com)
Prerequisites
n The programming software has been started.
n A new project has been created.
n The PLC has been added to the project.
7.7.1 Installing the GSDML file
The GSDML file can be downloaded for free from www.turck.com .
Adding the GSDML-file: Click "Options" Ò "Manage general station description files
(GSD)".
Fig. 34: Adding the GSDML-file
Installing the GSDML-file: Define the source path for the GSDML-file and click Install.
a The device is added to the Hardware catalog of the programming software.
Fig. 35: Installing the GSDML-file
V01.00 | 2019/12 39
Commissioning
7.7.2 Connecting the devices to the PLC

Select the TBEN-S2-4IOL from the Hardware catalog and drag them into the Device &
networks editor.
Connect the devices to the PLC in the Devices & networks editor.
Fig. 36: Connecting the device to the PLC
7.7.3 Assigning the PROFINET device name
Select Online access Ò Online & diagnostics.
Functions Ò Assign PROFINET device name.
Assign the desired PROFINET device name with Assign name.
Fig. 37: Assigning the PROFINET device name
V01.00 | 2019/12 41
Commissioning
7.7.4 Setting the IP address in TIA Portal

Select Device view Ò Properties Ò Ethernet addresses.
Assign the desired IP address.
Fig. 38: Assigning the IP address
7.7.5 Configuring device functions

The TBEN-S2-4IOL appears as a modular slave with twelve empty virtual slots. Slots 0 and Basic
are pre-configured.
The function of the twelve empty slots is already defined in the GSDML file. The slots can only
be used for a specific purpose.
Slot Meaning
0 Main module turck-tben-s2-4iol (default name)
Parameterization of functions (protocol deactivation, etc.), which concern
the complete module.
XI Parameterization of PROFINET functions (MRP, etc.)
X1 P1 Parameterization of the Ethernet port properties (topology, connection op-
X1 P2 tions, etc.).
Basic Parameters/diagnostics for the DXP-channels of the device (DXP 1, 3, 5 and
7) and Data Valid Signal from the IO-Link ports.
IO-Link port 1…4 Configuration of the 4 IO-Link ports
Diagnostics Optional mapping of the diagnostics (IO-Link and DXP-diagnostics) into the
master's process image.
IO-Link Events Optional mapping of the IO-Link events into the master's process image.
Module status Optional mapping of the module status into the masters process image.
Configuring IO-Link ports (example)
IO-Link port Process data IO-Link device GSDML entry
(Hardware) length
Port 1 2 byte IN Turck temperature Port configuration generic:
sensor, IN 1 WORD
TS-530-LI2UPN8X-...
Port 2 1 Bit IN - DI
Port 3 2 byte IN Turck linearity sensor, Port-configuration specific:
Li100P0-Q25LM0-... Li100P0-QU25L
Port 4 2 byte IN Turck I/O hub, Port configuration specific:
2 byte OUT TBIL-M1-16DXP TBIL-M1-16DXP
Select Device view Ò Device overview.

Select functions as operation mode, diagnostics etc. from the hardware catalog and add
them to the device slots via drag&drop.
Fig. 39: TIA-Portal – configuring device slots
V01.00 | 2019/12 43
Commissioning
Setting IO-Link port parameters

In generic port configuration, the ports of the IO-Link master can be operated in IO-Link mode
with different configuration as well as in SIO mode (DI).
In specific port configuration, the IO-Link ports receive the parameters from the GSDML-file.
Parameters like for example Operation mode, Data storage mode, Vendor- and Device ID can-
not be changed.
Select Device view Ò Device overview.
Select the device to be parameterized.
Click Properties Ò General Ò Module parameters.
Set the device parameters.
Fig. 40: TIA-Portal – Parameterizing generic IO-Link devices
7.7.6 Going online with the PLC
Start the online mode (Go online).
a The device has been successfully connected to the PLC.
Fig. 41: Starting the online mode
7.7.7 PROFINET – mapping

The PROFINET mapping corresponds to the data mapping described in the sections "Process In-
put Data” [} 112] and „Process Output Data" [} 114].
V01.00 | 2019/12 45
Commissioning
7.7.8 Use the IO_LINK_DEVICE function block in TIA Portal

The IO_LINK_DEVICE function block is based on the IOL_CALL function block according to the
IO-Link specification.
Fig. 42: Example call of Siemens FB "IO_LINK_DEVICE"
NOTE
The access to the port 0 functions of the IO-Link master with an IOL_INDEX of 65535
is not possible with version V3.0.2 of the Siemens IO_LINK_DEVICE block. In TIA-
Portal V15, the old IOL_CALL function block can be used to access the port 0 func-
tions. Siemens provides the function block for TIA-Portal users underhttps://sup-
port.industry.siemens.com.
Example accesses with IO_LINK_DEVICE
In this example, the watch table Sensor1 serves to visualize the procedure of the read and write
access via IO_LINK_DEVICE. The assignment of the SPDU-indices of IO-Link devices can be
found in the respective device documentation.
The function block access to the device an the connected sensors is done via the input variable
ID. The value which has to be set as ID depends on the used CPU:
Example:
n HW identifier of the basic slot (slot 1), for example with CPU 1511-PN (used in this example)
n Start address of the input data of the IO-Link master e.g. with CPU 315
Fig. 43: Hardware identifier: Basic slot of the TBEN-S2-4IOL in the example
V01.00 | 2019/12 47
Commissioning
Example read access – read product name

Reading out the product name (product name, index 0x12) of the TURCK IO-Link I/O-hub TBIL-
M1-16DXP at IO-Link port 4.
Write the input variables of the function block via control variable as follows:
Variable Value Meaning
REQ TRUE Send a read request
ID 264 Hardware identifier of the "Basic" slot according to the
configuration in the Device view
CAP 251 Function block instance
PORT 4 The I/O hub TBIL-M1-16DXP is connected to port 4.
IOL_INDEX 0x12 Index for product name
Fig. 44: IO_LINK_DEVICE – input variables for read access
Activate the read access via a rising edge at REQ.
Fig. 45: IO_LINK_DEVICE – activate read access
a In this example, the result of this request can be seen in the watch table (row 19 and fol-
lowing) in the IO-Link Record.
Fig. 46: IO_LINK_DEVICE – product name TBIL-M1-16DXP
V01.00 | 2019/12 49
Commissioning
Example access write – rotate display

The display of the Turck temperature sensors TS-500-LUUPN8X-H1141-... at IO-Link port 1 is ro-
tated. The parameter Measured value update time/rotating/disabling a display in index 55 is
set to 0x05 = 600 ms measured value update time, display rotated by 180°.
Fig. 47: Extract from the documentation for TS-500-…
Write the input variables of the function block via control variable as follows:
Activate the write access in the function block via RD_WR Sensor 1= TRUE.
Variable Value Meaning
REQ TRUE Send a write request
ID 264 Hardware identifier of the Basic slot according to the
configuration in the Device view
CAP 251 Function block instance
LEN 1 Length of the data to be written in byte
PORT 1 The temperature sensor TS-500-LUUPN8X-H1141 is con-
nected to port 1.
IOL_INDEX 0x12 Index for Measured value update time/rotating/dis-
abling a display
Fig. 48: IO_LINK_DEVICE – input variables for read access
V01.00 | 2019/12 51
Commissioning
Set the value to be written 0x05 via the first word of IO-Link Record in the watch table.
Fig. 49: IO_LINK_DEVICE – Control value 0x05 for index 0x55
Activate the Write access via a rising edge at REQ.
Fig. 50: IO_LINK_DEVICE – activate read access
a The display is now rotated about 180° and set to an actualization time of 600 ms
7.8 Commissioning the device in Modbus TCP
7.8.1 Implemented Modbus functions
The devices support the following functions for accessing process data, parameters, dia-
gnostics and other services.
Function Code
1 Read Coils – reading multiple output bits
2 Read Discrete Inputs – reading multiple input bits
3 Read Holding Registers – reading multiple output registers
4 Read Input Registers – reading multiple input registers
5 Write Single Coil – writing single output bit
6 Write Single Register – writing single output register
15 Write Multiple Coils – writing multiple output bits
16 Write Multiple Registers – writing multiple output
23 Read/Write Multiple Registers – reading and writing multiple registers
7.8.2 Modbus registers

Address Access Meaning
0x0000…0x01FF read only Process data of the inputs (identical to registers 0x8000…
0x8FFF)
0x0800…0x09FF read/write Process data of the outputs (identical to registers 0x9000…
0x9FFF)
0x1000…0x100B read only Module identifier
0x100C read only Module status
0x1017 read only Register mapping revision (always 2, if not, mapping is incom-
patible with this description)
0x1020 read only Watchdog, actual time [ms]
0x1120 read/write Watchdog predefined time [ms] (default: 500 ms)
0x1130 read/write Modbus connection mode register
0x1131 read/write Modbus Connection Timeout in sec. (def.: 0 = never)
0x113C…0x113D read/write Modbus Parameter Restore (reset of parameters to default
values)
0x113E…0x113F read/write Modbus Parameter Save (permanent storing of parameters)
0x1140 read/write Deactivate protocol
Deactivates explicitly the selected Ethernet protocol:
n Bit 0 = deactivate EtherNet/IP
n Bit 1 = deactivate Modbus TCP
n Bit 2 = deactivate PROFINET
n Bit 15 = deactivate web server
0x1141 read/write Active protocol
n Bit 0 = EtherNet/IP active
n Bit 1 = Modbus TCP active
n Bit 2 = PROFINET active
n Bit 15 = Web server active
V01.00 | 2019/12 53
Commissioning
Commissioning the device in Modbus TCP
Address Access Meaning

0x1150 read only LED behavior (PWR) at V2 undervoltage
bit 0:
0 = red
1 = green flashing
0x2400 read only V1 [mV]: 0 at < 18 V
0x2401 read only V2 [mV]: 0 at < 18 V
0x8000…0x8400 read only Process data of the inputs (identical to registers 0x0000…
0x01FF)
0x9000…0x9400 read/write Process data of the outputs (identical to registers 0x0800…
0x09FF)
0xA000…0xA400F read only Diagnostics
0xB000…0xB400 read/write Parameters
The following table shows the register mapping for the different Modbus addressing methods:
Description Hex decimal 5-digit Modicon
Inputs 0x0000…0x01FF 0…511 40001…40512 400001…400512
Outputs 0x0800…0x09FF 2048…2549 42049…42560 402049…402560
Module identifier 0x1000…0x1006 4096…4102 44097…44103 404097…404103
Module status 0x100C 4108 44109 404109
Watchdog, 0x1020 4128 44129 404129
actual time
Watchdog, 0x1120 4384 44385 404385
predefined time
Modbus connection mode 0x1130 4400 44401 404401
register
Modbus Connection Timeout 0x1131 4401 44402 404402
in sec.
Modbus Parameter Restore 0x113C…0x113D 4412…4413 44413…44414 404413…404414
Modbus Parameter Save 0x113E…0x113F 4414…4415 44415…44416 404415…404416
Deactivate protocol 0x1140 4416 44417 404417
Active protocol 0x1141 4417 44418 404418
LED behavior (PWR) at V2 under- 0x1150 4432 44433 404433
voltage
V1 [mV]: 0x2400 9216 49217 409217
V2 [mV]: 0x2401 9217 49218 409218
Process data inputs 0x8000, 0x8001 32768, 32769 - 432769, 432770
Process data outputs 0x9000, 0x9001 36864, 36865 - 436865, 436866
Diagnostics 0xA000, 0xA001 40960, 40961 - 440961, 440962
Parameters 0xB000, 0xB001 45056, 45057 - 445057, 445058
Register 0x1130: Modbus connection mode
This register defines the behavior of the Modbus connections.
Bit Designation Value Meaning
0 MB_OnlyOneWritePermission 0 All Modbus connections receive the write au-
thorization
1 Only one Modbus connection can receive the
write permission. A write permission is opened
until a Disconnect. After the Disconnect the
next connection which requests a write access
receives the write authorization.
1 MB_ImmediateWritePermission 0 With the first write access, a write authoriza-
tion for the respective Modbus connection is
requested. If this request fails, an exception re-
sponse with exception-code 0x01 is gener-
ated. If the request is accepted, the write ac-
cess is executed and the write authorization
remains active until the connection is closed.
1 The write authorization for the respective
Modbus connection is already opened during
the connection establishment. The first Mod-
bus connection thus receives the write author-
ization, all following connections don’t (only if
bit 0 = 1).
2…15 reserved - -
Register 0x1131: Modbus connection timeout

This register defines after which time of inactivity a Modbus connection is closed through a Dis-
connect.
Value range: 0…65535 s
default: 0 s = never (Modbus connection will never be closed)
Behavior of the BUS LED
If Modbus is the active protocol in case of a connection Time out and no further Modbus con-
nections exist, the BUS LED behaves as follows:
Connection timeout BUS LED
timeout Green blinking
Register 0x113C and 0x113D: Restore Modbus-Connection-Parameters

Registers 0x113C and 0x113D serve for resetting the parameter-register 0x1120 and 0x1130 to
0x113B to the default settings. The service resets the parameters without saving them.
Procedure:
Write 0x6C6F to register 0×113C.
To activate the reset of the registers, write 0x6164 ("load") within 30 seconds in register
0x113D. Both registers can also be written with one single request using the function
codes FC16 and FC23.
a The parameters are reset tot default values.
Save changes via a subsequent Save service.
V01.00 | 2019/12 55
Commissioning
Register 0x113E and 0x113F: Save Modbus-Connection-Parameters

Registers 0x113E and 0x113F are used for the non-volatile saving of parameters in registers
0x1120 and 0x1130 to 0x113B.
Procedure:
Write 0x7361 to register 0×113E.
Write 0x7665 ("save") within 30 seconds in register 0x113F to activate the reset of the re-
gisters. Both registers can also be written with one single request using the function
codes FC16 and FC23.
a The parameters are saved.
7.8.3 Data width

Module Process input Process output Alignment
TBEN-S2-4IOL 208 byte 130 word by word
7.8.4 Register mapping
Register no. Bit no.
15 14 13 12 11 10 9 8 7 6 5 4 3 2 1 0
MSB LSB
Input data
0x0000… Process input data
0x00xx [} 112]
Module status
0x00xx see status- and control word
+ 1 register
Output data
0x0800… Process output data
0x08xx [} 114]
Diagnostics
0xA000 DXP channel diagnostics
[} 116]
0xA001 IO-Link channel diagnosis
…
0xA004
Parameters
[} 100]
IO-Link Basic
0xB000 - - - - - - - - DXP7_ - DXP5_ - DXP3_ - DXP1_ -
SRO SRO SRO SRO
0xB001 - - - - - - - - DXP7_ - DXP5_ - DXP3_ - DXP1_ -
EN DO EN DO EN DO EN DO
IO-Link port 1
0xB002 Cycle time GSD Activate Quick Data Mode
Start-Up storage mode
0xB003 - - - - - - - - Mapping Mapping Deactivate PDIN Rev.
PCDO PDIN diag. invalid
0xB004… - - - - - - - - - - - - - - - -
0xB005
0xB006 Vendor ID
0xB007 … Device ID
0xB008
0xB009 - - - - - - - - - - - - - - - -
IO-Link port 2
0xB00A… 8 registers parameter data, assignment similar to port 1
0xB011
IO-Link port 3
0xB012… 8 registers parameter data, assignment similar to port 1
0xB019
IO-Link port 4
0xB01A… 8 registers parameter data, assignment similar to port 1
0xB021
V01.00 | 2019/12 57
Commissioning
7.8.5 Error Behavior (watchdog)
Behavior of outputs
In case of a failure of the Modbus communication, the outputs’ behavior is as follows, depend-
ing on the defined time for the Watchdog (register 0x1120):
Watchdog Behavior of outputs
0 ms All outputs maintain the actual value in case of an error
> 0 ms (default = 500 Outputs switch to 0 after the watchdog time has expired (setting in re-
ms) gister 0x1120).
NOTE
Setting the outputs to predefined substitute values is not possible in Modbus TCP.
Eventually parameterized substitute values will not be used.
Behavior of the BUS LED

If the watchdog triggers, the BUS LED behaves as follows:
Watchdog BUS LED
Tripped Red
Behavior of the device in case of loss of Modbus communication

If Modbus is the active protocol and all Modbus connections are closed, the watchdog switches
all outputs to "0" after the watchdog time has expired, unless another protocol (PROFINET, Eth-
erNet/IP) has been activated in the meantime.
7.9 Commissioning the device in EtherNet/IP
7.9.1 Common EtherNet/IP features
Features Description
QuickConnect No
Device Level Ring (DLR) yes
Number of TCP connections 3
Number of CIP connections 10
Input assembly instance 103, 120, 121, 122, 123,124, 125
Output assembly instance 104, 150, 151, 152
Configuration assembly Instance 106
7.9.2 EDS files and catalog files

The EDS and catalog files can be downloaded free of charge from www.turck.com.
n TBEN-S_ETHERNETIP.zip
7.9.3 Device Level Ring (DLR)

The devices support DLR. The Device Level Ring (DLR)-redundancy protocol is used to increase
the stability of EtherNet/IP networks. DLR-enabled devices have an integrated switch and can
thus be integrated into a ring topology. The DLR protocol is used to detect an interruption in
the ring. If the data line ins interrupted, data are sent through an alternative network section, so
that the network can be reconfigured as soon as possible. DLR-capable network nodes are
provided with extended diagnostic functions which enable the devices to localize errors and
thus decrease the time for error search and maintenance.
7.9.4 Diagnostic messages via process data

The diagnostic messages of the IO-Link channels are directly mapped into the process data
[} 112].
Additionally, the device's status word contains the module diagnostics.
V01.00 | 2019/12 59
Commissioning
Commissioning the device in EtherNet/IP
7.9.5 EtherNet/IP standard classes

The modules support the following EtherNet/IP Standard Classes in accordance with the CIP
specification.
Class Code Object name
Dec. Hex.
01 0x01 Identity Object [} 60]
04 0x04 Assembly Object [} 62]
06 0x06 Connection Manager Object [} 75]
245 0xF5 TCP/IP Interface Object [} 76]
246 0xF6 Ethernet Link Object [} 79]
Identity Object (0x01)

The following description of the Ethernet Link Object is taken from the CIP specification, Vol. 2,
Rev. 2.1 by ODVA & ControlNet International Ltd. and adapted to the Turck products.
Instance attributes
Attr. no. Attribute Get/set Type Value
name
Dec. Hex.
1 0x01 Vendor ID G UINT Contains the manufacturer ID.
Turck = 0x46
2 0x02 Product G UINT Shows the general product type.
type Communications Adapter 12dez =
0x0C
3 0x03 Product G UINT Identifies a special product in a
code device type.
default: 27247dec = 6A6F
4 0x04 Revision G STRUCT OF: Revision of the device which is rep-
resented by the Indentity Object.
n 0x01
n Major n USINT n 0x06
n Minor n USINT
5 0x05 Device G WORD WORD
status
6 0x06 Serial G UDINT Contains the identification number
number of the product (the last 3 bytes of the
MAC-ID).
7 0x07 Product G STRUCT OF: i.e.: TBEN-S2-4IOL
name USINT
STRING [13]
Device Status
Bit Name Definition
0…1 reserved default = 0
2 Configured TRUE = 1:
The application in the device has been con-
figured (default setting).
3 reserved default = 0
4…7 Extended Device Status 0011 = no I/O connection established
0110 = at least one I/O connection in RUN
mode
0111 = at least one I/O connection established,
all in IDLE mode
All other settings = reserved
8 Minor recoverable fault Recoverable fault, e.g.:
n Undervoltage
n Force-Mode in DTM active
n Diagnostic active at I/O channel
9…10 reserved
11 Diag Common error bit
12…15 reserved default = 0
Common services
Service code Class Instance Service name
Dec. Hex.
1 0x01 Yes Yes Get_Attribute_All
returns a predefined list of object attributes
5 0x05 No Yes reset
starts the reset service for the device
14 0x0E Yes Yes Get_Attribute_Single
returns the content of a specified attribute
16 0x10 No No Set_Attribute_Single
changes a single attribute
V01.00 | 2019/12 61
Commissioning
Assembly Object (0x04)

Assembly Objects bind attributes of multiple objects to allow data to or from each object to be
sent or received over a single connection.
Class attributes
Attr.-no. Attribute name Get/set Type Value
Dec. Hex.
1 0x01 Revision G UINT 2
2 0x02 Max. object instance G UINT 104
Instance attributes
Attr.-no. Attribute name Get/set Type Value
Dec. Hex.
3 0x03 Data S ARRAY OF Identifies a special product
BYTE in a device type.
default: 27247dec = 6A6F
4 0x04 Size G UINT Number of bytes in
attribute 3:
256 or variable
Common services
Dec. Hex.
1 0x01 yes yes Get_Attribute_All
Returns a predefined list of object attributes.
14 0x0E yes yes Get_Attribute_Single
Returns the content of a specified attribute.
Assembly instances
EtherNet/ Input assembly Output assembly Configuration as- Supported by
IP Con- sembly
nection
Instance Size [8 Instance Size [8 Instance Size [8 Rockwell Omron
bit] bit] bit]
Exclusive 103 208 104 132 106 84 x -
Owner
Exclusive 103 208 104 132 1 0 - x
Owner
(Omron)
IOL 4 IN/4 120 32 150 20 106 84 x x
OUT, dia-
gnostics
IOL 6 IN/6 122 40 151 28 106 84 x x
OUT, dia-
gnostics
EtherNet/ Input assembly Output assembly Configuration as- Supported by
IP Con- sembly
nection
Instance Size [8 Instance Size [8 Instance Size [8 Rockwell Omron
bit] bit] bit]
IOL 8 IN/8 124 48 152 36 106 84 x x
OUT, dia-
gnostics
IOL 4 IN/4 121 22 150 20 106 84 x x
OUT
IOL 6 IN/6 123 30 151 28 106 84 x x
OUT
IOL 8 IN/8 125 38 152 36 106 84 x x
OUT
Configuration Assembly (instance 106)

The modules support Configuration Assembly.
The Configuration Assembly contains:
10 bytes module configuration data (EtherNet/IP-specific)
+ 72 bytes (parameter data, depending on device)
The meaning of the input data can be found in chapter “Parameterizing and configuring”.
Byte no. Bit no.
Dec. Hex. 7 6 5 4 3 2 1 0
Device Configuration Data
0…8 0x00…0x08 - - - - - - - -
9 0x09 - - - - - Eth2 Eth1 QuickConnect
port setup port setup (not supported)
DXP channels
10 0x0A - - - - - - - DXP1_SRO
11 0x0B - - - - - - - DXP3_SRO
12 0x0C - - - - - - - DXP5_SRO
13 0x0D - - - - - - - DXP7_SRO
14 0x0E - - - - - - - DXP1_EN DO
15 0x0F - - - - - - - DXP3_EN DO
16 0x10 - - - - - - - DXP5_EN DO
17 0x11 - - - - - - - DXP7_EN DO
IO-Link port parameters
IO-Link port 1
18 0x12 - - - - Operation mode
19 0x13 - - - - - - Data Storage Mode
20 0x14 Cycle time
21 0x15 - - - - - - - Revision
22 0x16 - - - - - - - Quick Start-Up
23 0x17 - - - - - - - GSD
24 0x18 - - - - - - - PCDI invalid
V01.00 | 2019/12 63
Commissioning
Byte no. Bit no.

Dec. Hex. 7 6 5 4 3 2 1 0
25 0x19 - - - - - - - Deactivate
diagnostics
26 0x1A - - - - - - Mapping PDIN
27 0x1B - - - - - - Mapping PDOUT
28…29 0x1C…0x1D Vendor ID
30…33 0x1E…0x21 Device ID
34…49 0x22…0x31 IO-Link port 2
Device configuration data

Parameter name Value Meaning
LED-behavior (PWR) at V2 under- 0 red PWR-LED constant red at V2 under-
voltage voltage.
1 green PWR-LED is blinking green at V2 un-
dervoltage.
ETH x Port Setup 0 Auto ne- The port is set to autonegotiation.
goti-
ation
1 100BT/ Fix setting of the communication
FD parameters for the Ethernet port to:
100BaseT
full duplex
Input assembly instances

EtherNet/IP Connector Input assembly Device status [byte]
In- Size [8 bit]
stance
Exclusive Owner 103 208 2
Exclusive Owner (Om- 103 208 2
ron)
IOL 4 IN/4 OUT, dia- 120 32 2
gnostics
IOL 6 IN/6 OUT, dia- 122 40 2
gnostics
IOL 8 IN/8 OUT, dia- 124 48 2
gnostics
IOL 4 IN/4 OUT 121 22 2
IOL 6 IN/6 OUT 123 30 2
IOL 8 IN/8 OUT 125 38 2
Instance 103 – Exclusive Owner

The description of the parameters can be found in chapter “Parameterizing and configur-
ing” [} 112]
Word no. Bit no.
15 14 13 12 11 10 9 8 7 6 5 4 3 2 1 0
Status word [} 116]
0x00 - FCE - - - - V1 - V2 - - - - - - DIAG
Inputs
0x01 - - - - - - - - DXP7 DI6 DXP5 DI4 DXP3 DI2 DXP1 DI0
(SIO) (SIO) (SIO) (SIO)
Process input data valid
0x02 - - - - - - - - - DVS6 - DVS4 - DVS2 - DVS0
IO-Link – process input data
0x03… 16 words per port
0x12
0x13…
0x22
0x23…
0x32
0x33…
0x42
Diagnostics
DXP channels
0x43 - - - - - - - - ERR - ERR - ERR - ERR -
DXP 7 DXP 5 DXP 3 DXP 1
IO-Link port diagnostics
Port 1
0x44 GEN OVL V V ULVE LLVU O PRM EVT1 EVT2 PD HW DS CFG PPR -
ERR HIGH LOW TMP ERR INV ERR ERR ERR
…
Port 4
IO-Link Events
0x48 Port (1st Event) Qualifier (1st Event)
0x49 Event Code low byte (1st Event) Event Code high byte (1st Event)
…
0x66 Port 16th Event) Qualifier (16th Event)
0x67 Event Code low byte (16th Event) Event Code high byte (16th Event)
V01.00 | 2019/12 65
Commissioning
Instance 120 – 4 bytes IN/4 bytes OUT, diagnostics

ing” [} 112]
Word no. Bit no.
15 14 13 12 11 10 9 8 7 6 5 4 3 2 1 0
Status word [} 116]
0x00 - FCE - - - - V1 - V2 - - - - - - DIAG
Inputs
0x02 - - - - - - - - - DVS6 - DVS4 - DVS2 - DVS0
0x04
0x05…
0x06
0x07…
0x08
0x09…
0x0A
Diagnostics
DXP channels
0x0B - - - - - - - - ERR - ERR - ERR - ERR -
Port 1
0x0C GEN OVL V V ULVE LLVU O PRM EVT1 EVT2 PD HW DS CFG PPR -
…
Port 4
0x0F GEN OVL V V ULVE LLVU O PRM EVT1 EVT2 PD HW DS CFG PPR -
Instance 121 – 4 bytes IN/4 bytes OUT
ing” [} 112]
Word no. Bit no.
15 14 13 12 11 10 9 8 7 6 5 4 3 2 1 0
Status word [} 116]
0x00 - FCE - - - - V1 - V2 - - - - - - Diag
Inputs
0x02 - - - - - - - - - DVS6 - DVS4 - DVS2 - DVS0
0x04
0x05…
0x06
0x07…
0x08
0x09…
0x0A
V01.00 | 2019/12 67
Commissioning

ing” [} 112]
Word no. Bit no.
15 14 13 12 11 10 9 8 7 6 5 4 3 2 1 0
Status word [} 116]
0x00 - FCE - - - - V1 - V2 - - - - - - Diag
Inputs
0x02 - - - - - - - - - DVS6 - DVS4 - DVS2 - DVS0
IO-Link process input data
0x05
0x06…
0x08
0x09…
0x0B
0x0C…
0x0E
Diagnostics
DXP channels
0x0F - - - - - - - - ERR - ERR - ERR - ERR -
Port 1
…
Port 8
ing” [} 112]
Word no. Bit no.
15 14 13 12 11 10 9 8 7 6 5 4 3 2 1 0
Status word [} 116]
0x00 - FCE - - - - V1 - V2 - - - - - - Diag
Inputs
0x02 - - - - - - - - - DVS6 - DVS4 - DVS2 - DVS0
0x05
0x06…
0x08
0x09…
0x0B
0x0C…
0x0E
V01.00 | 2019/12 69
Commissioning

ing” [} 112]
Word no. Bit no.
15 14 13 12 11 10 9 8 7 6 5 4 3 2 1 0
Status word [} 116]
0x00 - FCE - - - - V1 - V2 - - - - - - Diag
Inputs
0x02 - - - - - - - - - DVS6 - DVS4 - DVS2 - DVS0
0x06
0x07…
0x0A
0x0B…
0x0E
0x0F…
0x12
Diagnostics
DXP channels
0x13 - - - - - - - - ERR - ERR - ERR - ERR -
Port 1
…
Port 8
ing” [} 112]
Word no. Bit no.
15 14 13 12 11 10 9 8 7 6 5 4 3 2 1 0
Status word [} 116]
0x00 - FCE - - - - V1 - V2 - - - - - - Diag
Inputs
0x02 - - - - - - - - - DVS6 - DVS4 - DVS2 - DVS0
0x06
0x07…
0x0A
0x0B…
0x0E
0x0F…
0x12
Output assembly instances

EtherNet/IP Output assembly Control word DXP outputs IO-Link out- VAUX [byte]
Connection [byte] [byte] puts [byte]
Instance Size [8 bit]
Exclusive 104 132 2 2 64 0
Owner
IOL 4 IN/4 150 20 2 2 16 0
OUT
IOL 6 IN/6 151 28 2 2 24 0
OUT
IOL 8 IN/8 152 36 2 2 32 0
OUT
Instance 104 – Exclusive Owner

ing” [} 114]
Word no. Bit no.
15 14 13 12 11 10 9 8 7 6 5 4 3 2 1 0
Control Word
0x00 - reserved
DXP outputs
0x01 - - - - - - - - DXP7 - DXP5 - DXP3 - DXP1 -
IO-Link – process output data
V01.00 | 2019/12 71
Commissioning
Word no. Bit no.

15 14 13 12 11 10 9 8 7 6 5 4 3 2 1 0
0x11
0x12…
0x21
0x22…
0x31
0x32…
0x42
ing” [} 114]
Word no. Bit no.
15 14 13 12 11 10 9 8 7 6 5 4 3 2 1 0
Control Word
0x00 - reserved
DXP outputs
0x01 - - - - - - - - DXP7 - DXP5 - DXP3 - DXP1 -
IO-Link process output data
0x03
0x04…
0x05
0x06…
0x07
0x08…
0x09

ing” [} 114]
Word no. Bit no.
15 14 13 12 11 10 9 8 7 6 5 4 3 2 1 0
Control Word
0x00 - reserved
DXP outputs
0x01 - - - - - - - - DXP7 - DXP5 - DXP3 - DXP1 -
0x04
0x05…
0x07
0x08…
0x0A
Word no. Bit no.
15 14 13 12 11 10 9 8 7 6 5 4 3 2 1 0
0x0B…
0x0D
V01.00 | 2019/12 73
Commissioning

ing” [} 114]
Word no. Bit no.
15 14 13 12 11 10 9 8 7 6 5 4 3 2 1 0
Control Word
0x00 - reserved
DXP outputs
0x01 - - - - - - - - DXP7 - DXP5 - DXP3 - DXP1 -
0x05
0x06…
0x09
0x0A…
0x0D
0x0E…
0x11
Connection Manager Object (0x05)
This object is used for connection and connectionless communications, including establishing
connections across multiple subnets.
Common services
Service code Class Instance Meaning
Dec. Hex.
84 0x54 no yes FWD_OPEN_CMD
(opens a connection)
78 0x4E no yes FWD_CLOSE_CMD
(closes a connection)
82 0x52 no yes UNCONNECTED_SEND_CMD
V01.00 | 2019/12 75
Commissioning
TCP/IP Interface Object (0xF5)

Class attributes
Attr. no. Designation Get/set Type Value
Dec. Hex.
3 0x03 Number of instances G UINT 1
6 0x06 Max. class identifier G UINT 7
7 0x07 Max. instance attribute G UINT 6
Instance Attributes
Attr. no. Designation Get/set Type Value
Dec. Hex.
1 0x01 Status G DWORD Interface status
2 0x02 Configuration G DWORD Interface Capability Flag
capability
3 0x03 Configuration G/S DWORD Interface Control Flag
control
4 0x04 Physical G STRUCT
link object
Path size UINT Number of 16 bit words:
0x02
Path Padded 0x20, 0xF6, 0x24, 0x01
EPATH
5 0x05 Interface G Structure of: TCP/IP Network Interface
configuration Configuration
IP address G UDINT Actual IP address
Network mask G UDINT Actual network mask
Gateway addr. G UDINT Actual default gateway
Name server G UDINT 0 = no server address con-
figured
Name server 2 G UDINT 0 = no server address con-
figured for server 2
Domain name G UDINT 0 = no domain name con-
figured
6 0x06 Host name G String 0 = no host name con-
figured
12 0x0C QuickConnect G/S BOOL 0 = deactivate
1 = activate
Common services
Dec. Hex.
1 0x01 Yes Yes Get_Attribute_All
Dec. Hex.
2 0x02 No No Set_Attribute_All
14 0x0E Yes Yes Get_Attribute_Single
16 0x10 No Yes Set_Attribute_Single
Interface status
This status attribute shows the status of the TCP/IP network interface. Refer to the TCP/IP Ob-
ject Status Diagram for details on the states of this status attribute.
Bit Designation Meaning
0…3 Interface Indicates the status of the Interface Configuration attrib-
Configuration Status ute:
0 = The Interface Configuration attribute has not been
configured
1 = The Interface Configuration attribute contains valid
configuration.
2…15 = reserved
4…31 reserved
Fig. 51: TCP/IP object state diagram (acc. to CIP Spec., Vol.2, Rev. 1.1)
Configuration capability
V01.00 | 2019/12 77
Commissioning
The Configuration Capability indicates the device’s support for optional network configuration
capability.
Bit Designation Meaning Value
0 BOOTP client This device supports network configuration via 1
BOOTP.
1 DNS client The device is capable of resolving host names 0
by querying a DNS server.
2 DHCP client This device supports network configuration via 1
BOOTP.
Configuration control
The Configuration Control attribute is used to control network configuration options.
Bit Designation Meaning
0…3 Startup configuration Determines how the device shall obtain its initial config-
uration.
The device should use the previously stored interface
configuration (for example, from non-volatile memory,
set by hardware switch, etc.).
1…3 = reserved
4 DNS enable Always 0
5…31 reserved Set to 0
Interface configuration
This attribute contains the configuration parameters required to operate a TCP/IP device.
To change this attribute, proceed as follows:
Read out the attribute.
Change the parameters.
Set the attribute.
a The TCP/IP Interface Object applies the new configuration upon completion of the Set
service. If the value of the Startup Configuration bits (Configuration Control attribute) is
0, the new configuration is stored in non-volatile memory.
The device does not reply to the set service until the values are safely stored to non-volatile
memory.
An attempt to set any of the components of the Interface Configuration attribute to invalid val-
ues results in an error (status code 0x09) returned from the Set service. If initial configuration is
obtained via BOOTP or DHCP, the Interface Configuration attribute components are all 0 until
the BOOTP or DHCP reply is received. Upon receipt of the BOOTP or DHCP reply, the Interface
Configuration attribute shows the configuration obtained via BOOTP/DHCP.
Host Name
The attribute contains the name of the device host. The host name attribute is used when the
device supports the DHCP-DNS Update capability and has been configured to use DHCP upon
start up. This mechanism allows the DHCP client to forward its host name to the DHCP servers.
The DHCP server then updates the DNS data for the client.
Ethernet Link Object (0xF6)
Class attributes
Attr.-no. Designation Get/Set Type Value
Dec. Hex.
3 0x03 Number of instances G UINT 1
6 0x06 Max. class identifier G UINT 7
7 0x07 Max. instance attribute G UINT 6
Instance attributes
Attr.-no. Designation Get/Set Type Value
Dec. Hex.
1 0x01 Interface speed G UDINT Speed in megabit per
second (e.g. (z. B. 10, 100,
1000 etc.)
2 0x02 Interface flags G DWORD Interface capability flag
3 0x03 Physical address G ARRAY OF Contains the interface’s
USINT MAC address (Turck:
00:07:46:xx:xx:xx)
6 0x06 Interface control G 2 WORD Allows port-wise changes
of the Ethernet-settings
7 0x07 Interface type G
10 0x0A Interface label G
Interface flags
Bit Designation Meaning Default value
0 Link status Indicates whether or not the Ethernet communica- Depends on
tions interface is connected to an active network. application
0 = inactive link
1 = active link
1 Half/full duplex 0 = Half duplex Depends on
1 = Full duplex application
If the Link Status flag is 0, the value of the Half/Full
Duplex flag is indeterminate.
2…4 Negotiation Indicates the status of the automatic autonegoti- Depends on
status ation application
0 = autonegotiation in progress
1 = autonegotiation and speed detection failed, Us-
ing default values for speed and duplex (10Mbps/
half duplex).
2 = auto-negotiation failed but detected speed (de-
fault: half duplex).
3 = successfully negotiated speed and duplex
4 = Autonegotiation not started, yet Forced speed
and duplex.
V01.00 | 2019/12 79
Commissioning
Bit Designation Meaning Default value

5 Manual setting 0 = interface can activate changes to link paramet- 0
requires reset ers (auto-negotiate, duplex mode, interface speed)
automatically
1 = device requires a Reset service to be issued to
its Identity Object in order to adapt the changes.
6 Local Hardware 0 = interface detects no local hardware fault 0
Fault 1 = local hardware error detected
Common services
Dec. Hex.
1 0x01 yes yes Get_Attribute_All
14 0x0E yes yes Get_Attribute_Single
76 0x4C No yes Enetlink_Get_and_Clear
7.9.6 VSC-Vendor Specific Classes
In addition to supporting the above named CIP Standard Classes, the device support the
vendor specific classes (VSCs) described in the following.
Class Code Name Description
Dec. Hex.
100 0x64 Gateway Class [} 82] Data and parameters for the
field bus specific part of the device.
103 0x67 IO-Link Parameter Object ISDU object for acyclic transmission
[} 83] of parameter data between IO-Link
master and IO-Link device
135 0x87 Basic Class [} 88] Parameters and diagnostics of the di-
gital channels channels
137 0x89 IO-Link Port Class [} 89] Parameters and diagnostics of the IO-
Link-channels
138 0x8A IO-Link Events Class [} 91] IO-Link Events
V01.00 | 2019/12 81
Commissioning
Gateway Class (VSC 100)

This class contains all information concerning the whole device.
Object Instance 2, Gateway Instance
Attr. no. Designation Get/set Type Meaning
Dec. Hex.
109 0x6D Status word G STRUCT The status word contains gen-
(status register 2) eral module status information.
115 0x73 On IO connection G/S ENUM Reaction when the time limit for
timeout USINT an I/O connection is exceeded:
0: SWITCH IO FAULTED (0): The
channels are switched to the
substitute value.
1: SWITCH IO OFF (1): The out-
puts are set to 0.
2: SWITCH IO HOLD (2): No fur-
ther changes to I/O data. The
outputs are held.
138 0x8A GW status word G/S DWORD Activates or deactivates the
mapping of the status word into
the device's input data.
139 0x8B GW control word G/S DWORD Activates or deactivates the
mapping of the control word
into the device's output data.
140 0x8C Disable Protocols G/S UINT Deactivation of the used Ether-
net protocol.
Bit 0: Deactivates EtherNet/IP
(cannot be deactivated via the
EtherNet/IP interface).
Bit 1: Deactivates Modbus TCP
Bit 2: Deactivates PROFINET
Bit 15: Deactivates the web
server
IO-Link Parameter Object (VSC 103)
The IO-Link Parameter Object enables the acyclic transfer of parameter data between the IO-
Link master and the IO-Link device.
Instance 1 of the object addresses the IO-Link master
The instance attribute numbers address the IO-Link port at the IO-Link master or the port 0
functions of the IO-Link master.
n 1…n: IO-Link port at IO-Link master, n = number of IO-Link ports at IO-Link master
n 128: Port-0 functions of the IO-Link master
Instance attributes
Common services
Dec. Hex.
14 0x0E Yes No Get_Attribute_Single
Returns the content of a specified attribute.
75 0x4B No yes Read_ISDU
The service reads parameters from the connected IO-
Link device.
76 0x4C No yes Write_ISDU
The service writes parameters from the connected IO-
Link device.
Read_ISDU - Request
Data Value/content Description
Class 0x67 IO-Link Parameter Object

Instance 0x01 Addressing the IO-Link master
Instance attribute 0x01…n, 128 IO-Link port number, or 128 for Port-0 functions
Service code 0x4B Read_ISDU
Data Request parameters for the ISDU Read Service
Name Data type Description
Data byte 0 Index (LSB) UINT LSB from index of the IO-Link ISDU object
acc. to IODD
Data byte 1 Index (MSB) UINT MSB from index of the IO-Link ISDU object
acc. to IODD
Data byte 2 Sub index USINT Sub index from the IO-Link ISDU object
acc. to IODD
V01.00 | 2019/12 83
Commissioning
Read_ISDU – Response
n CIP Service Response, General-Status ≠ 0 Ò error-free access
structure of the response:
ISDU data Array of Byte Read data, max. 232 byte
n CIP Service Response, General-Status ≠ 0 Ò access error

IOL_Master Error UINT IO-Link master specific, see IO-
Link master Error Codes
IOL_Device Error UINT IO-Link device specific, see IO-
Link device Error Codes and
device documentation
Example:
Read access – name of device at port 4 is read out

Instance attribute 0x04 IO-Link port number
Service code 0x4B Read_ISDU: read access
Data Request parameters for the ISDU Read Service
Data byte 0 0x12 UINT Index for the product name in the device
(e.g. Turck I/O hub TBIL-M1-16DXP) ac-
cording to IODD
Data byte 1 0x00 UINT -
Data byte 2 0x00 USINT The index has no sub index.
n CIP Service Response:

ISDU data Array of Byte Error-free access:
Content:
54 42 49 4C 2D 4D 31 2D 31 36 44 58 50 (TBIL-
M1-16DXP)
Access error:
Content:
Error code
Write_ISDU – Request

Instance attribute 0x01…n, 128 IO-Link port number, or 128 for Port-0 functions
Service code 0x4C Write_ISDU
Data Request parameters for the ISDU write service
Data byte 0 Index (LSB) UINT LSB from index of the IO-Link ISDU object
acc. to IODD
Data byte 1 Index (MSB) UINT MSB from index of the IO-Link ISDU object
acc. to IODD
Data byte 2 Sub index USINT Sub index from the IO-Link ISDU object
acc. to IODD
Data byte 3…data Data Array of Byte Parameter data (n= length of ISDU object
byte n + 3)
Write_ISDU – Response
n CIP Service Response, general status = 0 Ò error-free access
Service response without further data
n CIP Service Response, general status ≠ 0 Ò access error
IOL_Master Error UINT IO-Link master specific, see IO-Link master Error Codes
IOL_Device Error UINT IO-Link device specific, see IO-Link device Error Codes
and device documentation
Example:
Write access – Application Specific Tag is written into the device at port 4

Instance attribute 0x04 IO-Link port number
Service code 0x4C Write_ISDU: Write access
V01.00 | 2019/12 85
Commissioning
Data Request parameters for the ISDU write service

0x18 UINT Index for the application specific tag in
the device (e.g. In Turck I/O-Hub TBIL-M1-
16DXP)
0x00 USINT The index has no sub index.
Byte 0: 0x54 The Application Specific Tag of the device
Byte 1: 0x65 can consist of 32 byte,
Byte 2: 0x6D example:
Byte 3: 0x70 ASCII: Temperature_sensor1
Byte 4: 0x65 Hex: 54 65 6d 70 65 72 61 74 75 72 65 5f
… 73 65 6e 73 6f 72 31 00 00…
Byte 17: 0x31 The remainder of the 32 bytes not re-
Byte 18…31: 00 quired is filled with 00.
IO-Link master error codes

Error code Designation acc. to spe- Meaning
cification
0x0000 No error No error
0x7000 IOL_CALL Conflict Unexpected write-request, read request expected
0x7001 Wrong IOL_CALL Decoding error
0x7002 Port blocked The accessed port is occupied by another task
… reserved
0x8000 Timeout Timeout, IOL master or IOL device port busy
0x8001 Wrong index Error: IOL index < 32767 or > 65535 selected
0x8002 Wrong port address Port address not available
0x8002 Wrong port function Port function not available
… reserved
IO-Link device error codes

Error code Designation acc. to Meaning
specification
0x1000 COM_ERR Communication error
Possible source: the addressed port is parameterized as
digital input DI and is not in IO-Link mode
0x1100 I_SERVICE_TIMEOUT Timeout in communication, device does not respond in
time
0x5600 M_ISDU_CHECKSUM Master reports checksum error, access to device not pos-
sible
0x5700 M_ISDU_ILLEGAL Device can not respond to master request
0x8000 APP_DEV Application error in the device
0x8011 IDX_NOTAVAIL Index not available
0x8012 SUBIDX_NOTAVAIL Sub-Index not available
0x8020 SERV_NOTAVAIL The service is temporarily not available.
Error code Designation acc. to Meaning
specification
0x8021 SERV_NOTAVAIL_ Service temporarily not available, device is busy (e. g.
LOCCTRL teaching or parameterization of the device at the device
active)
0x8022 SERV_NOTA- Service temporarily not available, device is busy (e. g.
VAIL_DEVCTRL teaching or parameterization of the device via DTM/PLC
etc. active)
0x8023 IDX_NOT_WRITEABLE Access denied, Index cannot be written
0x8030 PAR_VALOUTOFRNG Parameter value out of the valid range
0x8031 PAR_VALGTLIM Parameter value value above the upper limit
0x8032 PAR_VALLTLIM Parameter value value below the lower limit
0x8033 VAL_LENOVRRUN Length of data to be written does not match the length
0x8034 VAL_LENUNDRUN defined for this parameter
0x8035 FUNC_NOTAVAIL Function not available in the device
0x8036 FUNC_UNAVAILTEMP Function temporarily not available in the device
0x8040 PARA_SETINVALID Invalid parameter: Parameters not consistent with other
parameters in the device.
0x8041 PARA_SETINCONSIST Inconsistent parameters
0x8082 APP_DEVNOTRDY Application not ready, device busy
0x8100 UNSPECIFIC Vendor specific, according to device documentation
0x8101… VENDOR_SPECIFIC
0x8FF
V01.00 | 2019/12 87
Commissioning
Basic Class (VSC 135)

Attr. no. Designation Get/Set Type Meaning
Dec. Hex.
1 0x01 DXP 1 - Manual output reset after G/S USINT 0 = no
overcurrent 1 = yes
overcurrent 1 = yes
overcurrent 1 = yes
overcurrent 1 = yes
5 0x05 DXP 1 - Activate output G/S USINT 0 = no
1 = yes
1 = yes
1 = yes
1 = yes
9 0x09 DXP 1 - Overcurrent output G USINT 0 = inactive
1 = active
10 0x0A DXP 3 - Overcurrent output G USINT 0 = inactive
1 = active
11 0x0B DXP 5 - Overcurrent output G USINT 0 = inactive
1 = active
12 0x0C DXP 7 - Overcurrent output G USINT 0 = inactive
1 = active
13 0x0D IOL 0 – DI input G USINT
14 0x0E IOL 2 –DI input G USINT
15 0x0F IOL 4 –DI input G USINT
16 0x10 IOL 6 –DI input G USINT
17 0x11 IOL0 - Input value valid (Data Valid G USINT 0 = no
Signal) 1 = yes
Signal) 1 = yes
Signal) 1 = yes
Signal) 1 = yes
21 0x15 DXP 1 – Input value G
25 0x19 DXP 1 – Output value G USINT
26 0x1A DXP 3 – Output value G USINT
27 0x1B DXP 5 – Output value G USINT
28 0x1C DXP 7 – Output value G USINT
IO-Link Port Class (VSC 137)
This class provides one instance per IO-Link port at the IO-Link master module.
Attr. no. Designation Get/ Type Meaning
set
Dec. Hex.
Parameters
1 0x01 Operation G/S USINT 0 = IO-Link without validation
mode 1 = IO-Link with family compatible device
2 = IO-Link with compatible device
3 = IO-Link with identical device
4 = DI (with parameter access)
5…7 = reserved
8 = DI
2 0x02 Data Storage G/S USINT 0 = activated
Mode 1 = overwrite
2 = read in
3 = deactivated, clear
3 0x03 Cycle time G/S USINT See [} 104]
4 0x04 Revision G/S USINT 0 = automatic
1 = V 1.0
5 0x05 Activate G/S USINT 0 = no
Quick Start- 1 = yes
Up
6 0x06 Device para- G/S USINT 0 = no
meterization 1 = yes
via GSD
7 0x07 Process input G/S USINT 0 = diagnostics generated
data invalid 1 = no diagnostic generated
8 0x08 Deactivate G/S USINT 0 = no
diagnostics 1 = notifications
2 = notifications and warnings
3 = yes
9 0x09 Process input G/S USINT 0 = direct
data map- 1 = swap16 bit
ping 2 = swap 32 bit
3 = swap all
10 0x0A Process out- G/S USINT 0 = direct
put data 1 = swap16 bit
mapping 2 = swap 32 bit
3 = swap all
11 0x0B Vendor ID G/S INT
12 0x0C Device ID G/S DINT
Diagnostics
13 0x0D Wrong or G USINT 0 = inactive
missing 1 = active
device
14 0x0E Data storage G USINT 0 = inactive
error 1 = active
V01.00 | 2019/12 89
Commissioning
Attr. no. Designation Get/ Type Meaning

set
Dec. Hex.
15 0x0F Process input G USINT 0 = inactive
data invalid 1 = active
16 0x10 Hardware er- G USINT 0 = inactive
ror 1 = active
17 0x11 Maintenance G USINT 0 = inactive
events 1 = active
18 0x12 Out-of-spe- G USINT 0 = inactive
cification 1 = active
events
19 0x13 Parameteriz- G USINT 0 = inactive
ation error 1 = active
20 0x14 Over temper- G USINT 0 = inactive
ature 1 = active
21 0x15 Lower limit G USINT 0 = inactive
value under- 1 = active
run
22 0x16 Upper limit G USINT 0 = inactive
value ex- 1 = active
ceeded
23 0x17 Under- G USINT 0 = inactive
voltage 1 = active
24 0x18 Overvoltage G USINT 0 = inactive
1 = active
25 0x19 Overload G USINT 0 = inactive
1 = active
26 0x1A Common er- G USINT 0 = inactive
ror 1 = active
27 0x1B Port para- G USINT 0 = inactive
meterization 1 = active
error
Process data
28 0x1C Input data G USINT
word 0
… … … G USINT
43 0x2B Input data G USINT
word 15
44 0x2C Output data G USINT
word 0
… … … G USINT
59 0x3B Output data G USINT
word 15
IO-Link Events Class (VSC 138)
Attr. no. Designation Get/Set Type Meaning
Dec. Hex.
1 0x01 IOL-Event 1 – G USINT Port no. of the port which sends the 1st
port IO-Link Event.
… …
16 0x10 IOL-Event 16 – G USINT Port no. of the port which sends the 16th
port IO-Link Event.
17 0x11 IOL-Event 1 – G USINT Qualifier of the 1st IO-Link event
qualifier
… …
32 0x20 IOL-Event 16 – G USINT Qualifier of the 1st IO-Link event
qualifier
33 0x21 IOL-Event 1– G USINT Event code of the 1st IO-Link event
Event Code
… …
48 0x30 IOL-Event 16– G USINT Event code of the 1st IO-Link event
Event Code
V01.00 | 2019/12 91
Commissioning
Connecting the devices to a Rockwell PLC with EtherNet/IP
7.10 Connecting the devices to a Rockwell PLC with EtherNet/IP
Used hardware
The following hardware components are used in this example:
n Rockwell PLC ControlLogix 1756-L72, Logix 5572
n Rockwell Scanner 1756-EN2TR
n Block module TBEN-S2-4IOL
Used software
The following software tools are used in this example:
n Rockwell RS Logix
n Catalog file for Turck compact stations "TURCK_BLOCK_STATIONS_Vxx.L5K" as part of the file
"TBEN-S_ETHERNETIP.zip" (downloadable free of charge under www.turck.com)
Catalog files
Turck provides catalog files "TURCK_BLOCK_STATIONS_Vxx.L5K" for use in Rockwell Automa-
tion's RSLogix/Studio5000. The catalog files contain predefined, application-dependent device
configurations with different input and output data widths and descriptions of the configura-
tion, input and output tag data. The predefined device configurations correspond to the input
and output assembly instances described in the section "Assembly Object" in the chapter
"Commissioning Devices with EtherNet/IP” Ò under "EtherNet/IP standard classes".
NOTE
The catalog file is available in the L5K file format and must be converted to the
"ACD" file format before it can be used. The file is opened in RSLogix/Studio5000
and saved as a project (*.ACD).
Prerequisites
n Instance of the programming software with the Catalog files is opened.
n A new project has been created in a second instance of RSLogix.
n The PLC and the Scanner mentioned above have been added to the project in the second in-
stance.
7.10.1 Adding the devices from the catalog files to the new project
Right-click the device entry and use Copy.
Fig. 52: RSLogix – Copying the device entry from catalog file
V01.00 | 2019/12 93
Commissioning
Right-click the EtherNet/IP scanner in the 2nd instance of the RS Logix and add the
device to the project via Paste. In this example, the configuration with 4 byte in- and 4
byte output data plus diagnostics TBEN_S2_4IOL_4in4out_diag is used.
Fig. 53: RSLogix – predefined configurations of TBEN-S2-4IOL in new project
7.10.2 Configuring the device in RS Logix
Open the device entry by double-clicking.
Assign a module name.
Set the IP address of the device.
Fig. 54: Setting module name and IP address
Optional: Set the connection parameters.
Fig. 55: Setting the connection parameters
V01.00 | 2019/12 95
Commissioning
7.10.3 Parameterizing the device

Open the Controller Tags of the device.
Parameterize the device via the Controller Tags TBEN_S2_4IOL_4in4out_diag:C.
Fig. 56: Parameterizing the Device
7.10.4 Going online with the PLC
Search the network via the Who Active function.
Select the PLC.
Set the communication path via Set Project Path.
a The communication path is set.
Fig. 57: Setting the communication path
V01.00 | 2019/12 97
Commissioning
Select the PLC.

Click Go online.
Fig. 58: Going online with the device
Click Download In the following dialog (Connect To Go Online)

Confirm all following messages.
a The project is loaded down to the controller. The connection is established.
7.10.5 Reading process data
Open the Controller Tags in the project tree by double-clicking the entry.
a The access to parameter data (TBEN_S2_4IOL_…:C), input data (TBEN_S2_4IOL_…:I) and
output data (TBEN_S2_4IOL_…:O) is possible.
Fig. 59: Controller Tags in the project tree
V01.00 | 2019/12 99
Parameterizing and Configuring
Parameters
8 Parameterizing and Configuring

8.1 Parameters
The module provides 4 byte of module parameters and 16 byte of IO-Link port-parameters for
each IO-Link port.
Word no. Bit no.
15 14 13 12 11 10 9 8 7 6 5 4 3 2 1 0
Basic
0x00 - - - - - - - - DXP7_ - DXP5_ - DXP3_ - DXP1_ -
SRO SRO SRO SRO
0x01 - - - - - - - - DXP7_ - DXP5_ - DXP3_ - DXP1_ -
EN DO EN DO EN DO EN DO
IO-Link port 1
0x02 Cycle time GSD Activ- Data storage Operation mode
ate mode
quick
start-
up
0x03 - Mapping Mapping Deactivate PDIN Rev.
PCDO PDIN diag. invalid
0x04… - - - - - - - - -
0x05
0x06 Vendor ID (MSB) Vendor ID (LSB)
0x07 Device ID Device ID (LSB)
0x08 Device ID (MSB) Device ID
0x09 - - - - - - - - - - - - - - - -
IO-Link port 2
0x0A… Assignment similar to IO-Link port 1 (word 0x02…0x09)
0x11
IO-Link port 3
0x12… Assignment similar to IO-Link port 1 (word 0x02…0x09)
0x19
IO-Link port 4
0x1A… Assignment similar to IO-Link port 1 (word 0x02…0x09)
0x21
The default values are shown in bold type.
Parameter name Value Meaning Description
dec. Hex.
Manual output re- 0 0x00 Yes The output switches on automatically after an over-
set after overcur- load.
rent 1 0x01 No The output is manually switched-off after an overload
(DXPx_SRO) until a new set-command is given (rise and fall).
Activate output 0 0x00 Yes The output at pin 2 is deactivated.
Chx (DXPx_ENDO) 1 0x01 No The output at pin 2 is activated.
dec. Hex.
Operation mode 0 0x00 IO-Link without valida- Pin 4 is operated in IO-Link mode.
tion The master does not check if the connected device
matches the configured one.
1 0x01 IO-Link with family com- Pin 4 is operated in IO-Link mode.
patible device The master checks if the Vendor ID and the MSB of
the Device ID (this byte defines the product family) of
the connected device match those of the configured
one. If the master detects a mismatch, the IO-Link
communication is established, but there is no process
data exchange. The device remains in the safe state
(Pre-Operate).
Parameters and diagnostic information can be read
and respectively written.
2 0x02 IO-Link with compatible Pin 4 is operated in IO-Link mode.
device The master checks if the Vendor ID and the Device ID
of the connected device match those of the con-
figured one. If the Vendor ID matches, but the Device
ID not, then the master tries to write the Device ID to
the device. If the writing is successful, then the device
is a compatible one, process data exchange is pos-
sible. If writing the Device ID is not successful, then
process data exchange is not possible. The device re-
mains in the safe state (Pre-Operate).
3 0x03 IO-Link with identical Pin 4 is operated in IO-Link mode.
device The master checks if the device type (Vendor ID and
Device ID) and the serial number of the connected
device match the data of the configured one. If the
master detects a mismatch, the IO-Link communica-
tion is established, but there is no process data ex-
change. The device remains in the safe state (Pre-Op-
erate).
4 0x04 DI (with parameter access) Pin 4 is generally operated as simple digital input.
However, an acyclic parameter access from the PLC or
the DTM is possible. The IO-Link master starts the port
in IO-link mode, parameterizes the device and sets
the port back into SIO mode (SI). The port remains in
SIO mode (DI) until a new IO-Link request is sent from
the higher-level control.
Data storage is not supported. Connected devices
have to support the SIO mode (DI).
In case of a parameter access, the IO-Link communic-
ation at the port is started. Switching signals are inter-
rupted.
8 0x08 DI Pin 4 is operated as simple digital input. Data storage
is not supported.
V01.00 | 2019/12 101

Parameters

dec. Hex.
Data storage mode Synchronization of parameter data of IO-Link devices (storing the parameter of the connected
device in the master).
If the synchronization is not possible, a diagnostic message is displayed (DS_ERR). In this case
the data memory of the master must be deleted:
Select option "11 = deactivated, delete" to delete the data memory of the master
IO-Link devices in accordance with IO-Link specification V1.0 do not support data storage.
When using IO-Link devices with IO-Link V1.0:
Select option "11 = deactivated, delete" to deactivate data storage.
0 0x00 Activated Synchronization of parameter data activated. The ac-
tual data (master or device) serve as the reference
data.
1 0x01 overwrite Synchronization of parameter data activated, the
data in the master serve as reference data.
2 0x02 read in Synchronization of parameter data activated. The
data in the connected IO-Link device serve as refer-
ence data.
3 0x03 Deactivated, clear Synchronization of parameter data deactivated. The
data set in the master is deleted.
Activate Quick For fast applications (e.g. tool changing applications) the start-up time of IO-Link devices can
Start-Up be shortened. The start-up time defined in the IO-Link specification (TSD = Device Detection
Time) is reduced.
0 0x00 No The start-up time is within the specified range (0.5 s).
All IO-Link devices in accordance with the specifica-
tion can be operated.
1 0x01 Yes The start-up time is reduced to approx. 100 ms. It is
not supported by every IO-Link device. It can thus be
necessary to check if the used IO-Link device starts in
this mode.
Device parameter- 0 0x00 inactive The port is generic or is not parameterized.
ization via GSD 1 0x01 Active In PROFINET the port is parameterized with a specific
(GSD) device type from the GSDML-file.
Cycle time 0 0x00 Automatic The lowest cycle time supported by the device is
taken from the table.
1… 0x01 0.8…132,8 ms Settable in steps of 0.8 or 1.6 ms.
191 …
0xBF
255 0xFF Automatic, compatible Compatibility mode The mode solves possible com-
munication problems with sensors of the SGB family
from IFM.
Revision 0 0x00 Automatic The Master defines the IO-Link revision automatically.
1 0x01 V1.0 IO-Link Revision V 1.0 is used.
Process input data 0 0x00 Diagnostic generated If the process data are invalid, a respective diagnostic
invalid (PDIN in- message is generated.
valid) 1 0x01 No diagnostic generated Invalid process data do not cause a diagnostic mes-
sage.
Deactivate dia- Influences the sending of IO-Link-Events from the master to the fieldbus. Depending on the
gnostics parameterization, the master transmits Events based on their priority to the fieldbus or not.
dec. Hex.
0 0x00 No The master transmits all IO-Link Events to the field-
bus.
1 0x01 Notifications The master transmits all IO-Link Events to the fieldbus
except for IO-Link notifications.
2 0x02 Notifications and warn- The master transmits all IO-Link Events to the fieldbus
ings except for IO-Link notifications and warnings.
3 0x03 Yes The master doesn't transmit any IO-Link Event to the
fieldbus.
Process inpput Optimization of the process data mapping for the used fieldbus: The I/O-Link-data can be
data mapping swapped depending on the used fieldbus in order to achieve an optimized data mapping on
(Mapping PDIN) the fieldbus side.
PROFINET:
With PROFINET, the parameter is permanently set to 0x00 = direct and cannot be changed.
0 0x00 direct The process data are not swapped.
i.e.: 0x0123 4567 89AB CDEF
1 0x01 Swap 16 bit The bytes are swapped per word.
i.e.: 0x2301 6745 AB89 EFCD
2 0x02 Swap 32 bit The bytes are swapped per double word.
i.e.: 0x6745 2301 EFCD AB89
3 0x03 swap all All bytes are swapped.
i.e.: 0xEFCD AB89 6745 2301
Process output see above Process input data mapping
data mapping
(Mapping PDOUT)
Vendor ID 0…65535 Vendor ID for the port configuration check
0x0000…
0xFFFF
Device ID 0… Device ID for the port configuration check
16777215 24 bit value
0…
0x00FFFFFF
V01.00 | 2019/12 103

Parameters
Values for the parameter ”cycle time” [ms]:

Time Value Time Value Time Value Time Value Time Value Time Value
auto 0x00 16 0x58 31.2 0x7E 60.8 0x92 91.2 0xA5 121.6 0xB8
1.6 0x10 16.8 0x5A 32 0x80 62.4 0x93 92.8 0xA6 123.2 0xB9
2.4 0x18 17.6 0x5C 33.6 0x81 64 0x94 94.4 0xA7 124.8 0xBA
3.2 0x20 18.4 0x5E 35.2 0x82 65.6 0x95 96 0xA8 126.4 0xBB
4 0x28 19.2 0x60 36.8 0x83 67.1 0x96 97.6 0xA9 128 0xBC
4.8 0x30 20 0x62 38.4 0x84 68.8 0x97 99.2 0xAA 129.6 0xBD
5.6 0x38 20.8 0x67 40 0x85 70.4 0x98 100.8 0xAB 131.2 0xBE
6.4 0x40 21.6 0x66 41.6 0x86 72 0x99 102.4 0xAC 132.8 0xBF
7.2 0x42 22.4 0x68 43.2 0x87 73.6 0x9A 104 0xAD reserved
8 0x44 23.2 0x6A 44.8 0x88 75.2 0x9B 105.6 0xAE
8.8 0x46 24.0 0x6C 46.4 0x89 76.8 0x9C 107.2 0xAF
9.6 0x48 24.8 0x6E 48 0x8A 78.4 0x9D 108.8 0xB0
10.4 0x4A 25.6 0x70 49.6 0x8B 80 0x9E 110.4 0xB1
11.2 0x4C 26.4 0x72 51.2 0x8C 81.6 0x9F 112 0xB2
12.0 0x4E 27.2 0x74 52.8 0x8D 83.2 0xA0 113.6 0xB3
12.8 0x50 28 0x76 54.4 0x8E 84.8 0xA1 115.2 0xB4
13.6 0x52 28.8 0x78 56 0x8F 86.4 0xA2 116.8 0xB5
14.4 0x54 29.6 0x7A 57.6 0x90 88 0xA3 118.4 0xB6
15.2 1x56 30.4 0x7C 59.2 0x91 89.6 0xA4 120 0xB7 auto., 0xFF
comp.
8.1.1 Adapting process data mapping
The mapping of process data can be adapted application-specifically via the IO-Link master's
parameterization.
Depending on the used fieldbus, it can be necessary to swap process data word-wise, double
word-wise or completely in order to align them to the data structure in the PLC. The process
data mapping is determined channel by channel through the parameters process input data
mapping and process output data mapping.
Example mapping for field buses with Little Endian-format:

Mapping through the IO-Link master Ò field bus Ò PLC
Byte Device at Device process data in Parameter: Device process data to field bus
IO-Link port IO-Link master Process data
mapping
Byte 0 Status Status
Byte 1 Control Control
IO-Link port 1
Byte 2 Temperature Temperature Low byte swap 16 bit Temperature High byte
Byte 3 sensor TS… High byte Low byte
IO-Link port 2
Byte 4 Linearity sensor Position Low byte swap 16 bit position High byte
Byte 5 Li… High byte Low byte
IO-Link port 3
Byte 6 I/O hub TBIL-… Digital 0…7 Direct Digital signal 0…7
signals
Byte 7 Digital 8…15 Digital signal 8…15
signals
IO-Link port 4
Byte 8 Diagnostics swap all Counter/position Most
value Significant
Byte
Byte 9 Rotary encoder Counter/position Low byte High byte
Byte 10 RI… value High byte Low byte
Byte 11 Most Diagnostics
Significant
Byte
V01.00 | 2019/12 105

Parameters
8.1.2 PROFINET parameters

For PROFINET, a distinction must be made in the parameters between the PROFINET device
parameters and the parameters of the I/O channels [} 100] .
PROFINET device parameters

Default values are shown in bold.
Output behavior at 0 set to 0 The device switches the outputs to
communication loss "0". No error information sent.
1 Hold current value The device maintains the actual out-
put data.
Deactivate all dia- 0 No Diagnostic and alarm messages are
gnostics generated.
1 yes Diagnostic and alarm messages are
suppressed.
Deactivate load 0 No The monitoring of voltage V2 is activ-
voltage diagnostics ated.
1 yes If V2 is undershot, this is not dis-
played.
Deactivate Force Mode 0 No Explicit deactivation of the Ethernet
1 yes protocols or web server
Deactivate 0 No
EtherNet/IP 1 yes
Deactivate Modbus 0 No
TCP 1 yes
Deactivate WEB server 0 No
1 yes
8.2 IO-Link functions for acyclic communication
The acyclic access to the data of IO-Link devices is realized via IO-Link CALLs. A distinction must
be made between data of the IO-Link master (IOLM) and data of connected IO-Link devices
(IOLD).
The addressing of the IO-Link CALL defines which device is addressed via the CALL:
The addressing is defined by the so called Entitiy_Port:
n Entity_Port 0 = IO-Link master module (IOLM)
n Entity_Port 1 = IO-Link device at IO-Link port 1
n …
n Entity_Port 4 = IO-Link device at IO-Link port 4
8.2.1 Port functions for Port 0 (IO-Link Master)
IO-Link Index (port function invocation)

The access to the IO-Link master functionalities (port 0) is done via index 65535:
Subindex 64: Master Port Validation Configuration

The object writes a specific configuration of the Devices to be connected to the IO-Link port to
the Master. The master stores the data for the The IO-Link device expected at the port and then
accepts only one device at the port with exactly matching data (vendor ID, device ID and serial
number).
The Master Port Validation Configuration is only useful in combination with an operation mode
with validation (IO-Link with family compatible device, IO-Link with compatible device, IO-
Link with identical device.
Entity_Port IO-Link sub index Read/write Length
0 64 Write Max. 96 byte
Structure of the command IOL_Port_Config:

Content Size Format Comment
IOL1 VENDOR_ID 2 byte Unsigned 16
DEVICE_ID 4 byte Unsigned 32
FUNCTION_ID 2 byte Unsigned 16 Value: 0
SERIAL_NUMBER 16 byte String
V01.00 | 2019/12 107

IO-Link functions for acyclic communication
Subindex 65: IO-Link Events

The object reads IO-Link Event diagnostics.
0 65 Read 255 byte
NOTE
Only ”appears” (coming diagnostics) and ”Single Shot Events” are shown, as long as
they are pending.
Structure of the read data:

n Byte 0 contains 2 bit per IO-Link port which show, if the process data of the connected
device are valid or not.
n Byte 0 is followed by 4 byte per Diagnostic Event which clearly assign and specify the dia-
gnostic message. A maximum of 14 Events per IO-Link port are shown.
Byte no. Bit no. Description
7 6 5 4 3 2 1 0
0 x PD_Valid Input Port 1
x PD_Valid Output Port 1
x PD_Valid Input Port 2
1 reserved
2 Qualifier Defines the type of the event (Warning, Noti-
fication, Single Shot Event, etc.) in accordance
with IO-Link specification ”IO-Link Interface
and System“.
3 Port IO-Link port which sends an event
4 Event Code high byte High or- low byte of the error code sent
5 Event Code low byte
… …
223 Qualifier see byte 2…5
224 Port
225 Event Code high byte
226 Event Code low byte
Subindex 66: Set Default Parameterization
Writing this object sets the IO-Link master back to factory settings. Any parameter setting and
configuration is overwritten. The data storage buffer is deleted as well.
0 66 Write 4 byte
Structure of the reset command:

0xEF 0xBE 0xAD 0xDE
Subindex 67: Teach Mode

The master reads all data (device-Id, vendor-ID, serial number, etc.) from the connected device
and saves them. All all previously saved device data are overwritten.
0 67 Write 1 byte
Structure of the Teach command:

Byte 0
0x00 Teach all ports
0x01 Teach port 1
0x02 Teach port 2
0x03 Teach port 3
0x04 Teach port 4
0x05…0xFF reserved
V01.00 | 2019/12 109

IO-Link functions for acyclic communication
Subindex 68: Master Port Scan Configuration

The object reads the configuration of the IO-Link devices connected to the IO-Link master.
28 byte are returned per IO-Link port.
0 68 Read Max. 120 byte
Structure of the response telegram:

IO-Link port Content Length Format Description
Port 1 Vendor ID 2 byte UINT16 Vendor ID of the connected
device
Device ID 4 byte UINT32 Device ID of the connected
device
Function ID 2 byte UINT16 reserved
Serial Number 16 byte UINT8 Serial number of the connected
device
COM_Revision 1 byte UINT8 IO-Link version
Proc_In_Length 1 byte UINT8 Process input data length of the
connected device
Proc_Out_Length 1 byte UINT8 Process output data length of
the connected device
Cycle time 1 byte UINT8 Cycle time of the connected
device
Port 2…port Structure similar to port 1
4
Subindex 69: Extended Port Diagnostics

The object reads the Extended Port Diagnostics.
0 68 Read Max. 120 byte
Structure of the Extended Port Diagnostics:

Byte no. Bit no.
7 6 5 4 3 2 1 0
0 NO_SIO TCYC - - DS_F NO_DS - -
1 - WD MD PDI_H - - NO_PD
2 - - - - - - - -
3 Device status according to IO-Link specification
Diagnostic bit Meaning

NO_DS The parameterized port mode does not support data storage.
Remedy:
n Change the parameterization of the port.
Diagnostic bit Meaning
DS_F Error in the data storage, synchronization not possible
Possible causes:
n Connected device does not support data storage
n Overflow of the data storage buffer
Remedy:
Connect a device that supports data storage.
Clear the data storage buffer.
Deactivate the data storage.
TCYC The device does not support the cycle time parameterized in the master.
Remedy:
Increase the cycle time set in the master.
NO_SIO The device does not support the standard DI (SIO) mode.
Remedy:
Select the IO-Link mode for this port.
NO_PD No process data available The connected device is not ready for operation.
Remedy:
Check the configuration.
PDI_E The connected device reports invalid process data in accordance with IO-
Link specification V1.0.
PDI_H The connected device reports invalid process data in accordance with IO-
Link specification V1.1.
MD Missing device, no IO-Link device detected.
Remedy:
n Check the IO-Link cable.
n Change the device.
WD Wrong device detected: one or more parameters of the connected device
(Vendor ID, Device ID, serial number) does not/do not match the data
which are stored in the master for this device.
Remedy:
n Change the device.
n Adapt the master parameterization
Device status
Value Meaning
0 Device works correctly
1 Maintenance event
2 Out-of-specification event
3 Functional check
4 Error
5…255 reserved
V01.00 | 2019/12 111

Operating
Process input data
9 Operating
9.1 Process input data
Word Bit no.
no. 15 14 13 12 11 10 9 8 7 6 5 4 3 2 1 0
Basic
0x01 - - - - - - - - - DVS6 - DVS4 - DVS2 - DVS0
IO-Link process input data
0x02 IO-Link port 1,
… structure depends on the channel parameterization (0…32 byte per channel)
0x11
0x21
0x31
0x41
Diagnostics
DXP channels
0x42 - - - - - - - - ERR - ERR - ERR - ERR -
IO-Link port 1
0x43 GEN- OVL V V ULVE LLVU O PRM EVT1 EVT2 PD HW DS CFG PPE -
0x44 IO-Link port 2, assignment similar to port 1
IO-Link Events
0x47 Port (1st Event) Qualifier (1st Event)
0x48 Event Code low byte (1st Event) Event Code high byte (1st Event)
…
0x65 Port 16th Event) Qualifier (16th Event)
0x66 Event Code low byte (16th Event) Event Code high byte (16th Event)
Module status (status word)
0x67 - FCE - - - COM V1 - V2 - - - - - - DIAG
Meaning of process data bits
Name Value Meaning
I/O data
DIx Digital input x
0 No signal at DI (pin 4, SIO)
1 Signal at DI (pin 4, SIO)
DXPx configurable digital channel (DXP channel)
0 No input signal at DXP-channel (pin 2)
1 Input signal at DXP-channel (pin 2)
DVSx Input value valid (Data Valid Signal)
0 The IO-Link data are invalid.
Possible causes:
n Sensor supply is below the admissible range.
n IO-Link port is parameterized as simple digital input.
n No device connected to the master.
n No input data received from the connected device (only
valid for devices with an input data length > 0).
n No reaction from the connected device to the sending of
output data (only valid for devices with an output data
length > 0).
n The connected device sends an process input data in-
valid error.
1 The IO-Link data are valid.
IO-Link process input Process input data of the connected device The order of the IO-Link
data process input data can be changed via the parameter Process input
data mapping.
Diagnostics Software diagnostic messages
IO-Link Events [} 108]
Module status [} 116]
V01.00 | 2019/12 113

Operating
Process output data
9.2 Process output data

Word Bit no.
no. 15 14 13 12 1 1 9 8 7 6 5 4 3 2 1 0
1 0
Basic
0x00 - - - - - - - - DXP7 - DXP5 - DXP3 - DXP1 -
IO-Link – process output data
0x10
0x20
0x30
0x40
Name Value Meaning

I/O data
DXPx DXP output
0 Output inactive
1 Output active, max. output current 2 A
9.3 LED displays
The device has the following LED indicators:
n Power supply
n Group and bus errors
n Status
n Diagnostics
PWR LED Meaning
Off No voltage or undervoltage at V1
Green Voltage at V1 and V2 ok
Red No voltage or undervoltage at V2
LED BUS Meaning

Off No voltage connected
Green Active connection to a master
Flashing green 3x in 2s ARGEE/FLC active
Green flashing (1 Hz) Device is ready for operation
Red IP address conflict, Restore mode active, F_Reset active or Modbus
connection timeout
Red flashing Wink command active
Red/green (1 Hz) Autonegotiation and/or waiting for DHCP-/BootP-address assignment
LED ERR Meaning

Off No voltage connected
Green No diagnostics
Red Diagnostic message pending
LEDs ETH1 and ETH2 Meaning

Off No Ethernet connection
Green Ethernet connection established, 100 Mbps
Green flashing Ethernet traffic, 100 Mbps
Yellow Ethernet connection established, 10 Mbps
Yellow flashing Ethernet traffic, 10 Mbps
LED IOL 0, 2, 4, 6 Meaning (Channel in IO-Link mode)

(IO-Link port)
Off Port inactive, no IO-Link communication, diagnostics deactivated
Green flashing IO-Link communication, process data valid
Red flashing IO-Link communication active and module error, invalid process data
Red IO-Link supply error free, no IO-Link communication and/ or module
error, process data invalid
LED IOL 0, 2, 4, 6 Meaning (channel in SIO mode (DI))

(IO-Link port)
Off No input signal
Green Digital input signal active
V01.00 | 2019/12 115

Operating
Software diagnostic messages
LED DXP 1, 3, 5, 7 Meaning (input) Meaning (output)

Off Input not active Output not active
Green Input active Output active (max. 2 A)
Red – Output active with overload/short
circuit
ERR DXP 7 Meaning

White flashing Wink command active
9.4 Software diagnostic messages

The device provides the following software diagnostic messages:
n DSP diagnostics
Diagnostic messages of the universal digital channels of the module (DXP 1, 3, 5, 7).
n IO-Link master diagnostics
The IO-Link master reports problems within the IO-Link communication.
n IO-Link device diagnostics
The device diagnostics map the IO-Link Event Codes (according to the IO-Link specification)
sent from the IO-Link devices to the diagnostic telegram of the master.
Event Codes can be read from the connected devices by using appropriate device tools (e.g.
IODD-Interpreter).
Further information concerning the IO-Link Event Codes and their meaning can be found in
the IO-Link specification or in the documentation of the connected devices.
9.4.1 Status- and control word
Status word
EtherNet/IP/ PROFINET Bit 7 Bit 6 Bit 5 Bit 4 Bit 3 Bit 2 Bit 1 Bit 0
Modbus
Byte 0 Byte 1 V2 - - - - - ARGEE DIAG
Byte 1 Byte 0 - FCE - - - COM V1 -
Bit Description
COM Internal error
The device-internal communication is disturbed.
DIAG Diagnostic messages at the device
FCE The DTM Force Mode is activated, which means, the actual output values may no
match the ones defined and sent by the field bus.
V1 V1 or V2 too low (< 18 V DC).
V2
The status word is mapped into the module's process data.

In EtherNet/IP the mapping can be deactivated via the Gateway Class (VSC 100).
NOTE
Activating or deactivating the status and control word modifies the process data
mapping.
Control word
The control word has no function.
V01.00 | 2019/12 117

Operating
9.4.2 Diagnostic telegram

Channel Byte no. Bit 7 Bit 6 Bit 5 Bit 4 Bit 3 Bit 2 Bit 1 Bit 0
DXP DXP diagnostics
0 ERR DXP7 - ERR DXP5 - ERR DXP3 - ERR DXP1 -
1 - - - - - - - -
IO-Link Device diagnostic messages Master diagnostics
IO-Link 0 EVT1 EVT2 PDINV HWERR DSERR CFGERR PPE -
port 1 1 GENERR OLV VHIGH VLOW ULVE LLVU OTEMP PRMERR
IO-Link 2…3 Assignment similar to IO-Link port 1
port 2
IO-Link 4…5
port 3
IO-Link 6…7
port 4
NOTE
The “process data” invalid diagnostic (PDINV) can be sent from both devices, IO-Link
master or IO-Link device.
Meaning of diagnostic Bits

Bit Meaning
DXP diagnostics
ERR_DXPx Overcurrent at the output (if the DXP channel is used as output)
IO-Link master diagnostics
CFGER Wrong or missing device
The connected device does not match the channel configuration or there is no
device connected to the channel. This diagnostic message depends on the para-
meterization of the channel.
DSER Data storage error
Possible causes:
n Data storage mismatch:
IO-Link device in accordance with IO-Link V1.0 connected.
The data storage buffer contains data of another device.
n Overflow of the data storage buffer
n The connected device may be locked for parameter changes or for data stor-
age.
Bit Meaning
PPE Port parameterization
The port parameters are inconsistent. The device parameterization via GSD is
active, but not working.
Possible causes:
n The IO-Link-master did not receive GSDML-parameters for a connected
device. The connected device was not parameterized by a PROFINET PLC via
GSDML.
n The port is in operation mode "IO-Link without validation" or "DI". These
modes do not allow parameterization via GSDL file.
n Data storage mode is active. The parameter is not set to "deactivated, clear".
A device parameterization via GSDML is not possible with activated data stor-
age.
n Vendor or Device ID are "0". The connected device can not be identified and is
thus not parameterizable.
IO-Link master/device diagnostics
PDINV Evaluating Process Input Data
The IO-Link master or the IO-Link device report invalid process input data. The
connected device is not in status "operate", which means, it is not ready for op-
eration.
Possible sources:
n The connected device does not match the configured one, additional dia-
gnostic message Wrong or missing device.
n Diagnostic message Process input data invalid because the process value
can not be measured (depends on the IO-Link device).
IO-Link device diagnostics
The IO-Link device diagnostics depend on the IO-Link device used. For more de-
tailed information on the diagnoses, please refer to the documentation for the
IO-Link device.
EVT1 Maintenance events
A Maintenance Event in accordance with the IO-Link specification occurred,
maintenance necessary.
EVT2 Out-of-specification events
An Out-of-Specification Event in accordance with the IO-Link specification oc-
curred.
GENERR Common error
The device sends an error (device status 4, in accordance with IO-Link specifica-
tion), which is not clearly specified. Read out the device Event Codes in order to
be able to specify the error more precisely.
HWER Hardware error
General hardware error or device malfunction of the connected device
LLVU Lower limit value underrun
The process value lies under the parameterized measurement range or the
chosen measurement range has been chosen too high.
OLV Overload
The connected device detected an overload.
OTMP Overtemperature
A temperature diagnosis is available on the connected device.
PRMERR Parameterization error
The connected device reports a parameterization error (loss of parameters, no
parameter initialization, etc.).
V01.00 | 2019/12 119

Operating
Bit Meaning
ULVE Upper limit value exceeded
The process value exceeds the parameterized measurement range or the
chosen measurement range has been chosen too low.
VLOW Undervoltage
One of the voltages at the connected device is below the defined range.
VHIGH Overvoltage
One of the voltages at the connected device exceeds the defined range.
9.4.3 PROFINET diagnostics

Module diagnostics PROFINET Diagnostics
(slot 0 according to configuration tool)
Connector Error Code Channel
Undervoltage V1 - 0x0002 0
Undervoltage V2 - 0x0002 1
DXP diagnostics PROFINET Diagnostics

(slot 1 according to configuration tool)
Channel Connector Error Code Channel
Overcurrent output DXP1 C0 0x0001 1
DXP3 C1 0x0001 3
DXP5 C2 0x0001 5
DXP7 C3 0x0001 7
IO-Link port diagnostics PROFINET Diagnostics

IO-Link port 1 Connector Error code Channel
(Slot 2, according to configuration tool)
Undervoltage (VLOW) C0 0x0002 0
Overcurrent (VHIGH) 0x0003
Overload (OVL) 0x0004
Over temperature (OTMP) 0x0005
Wrong or missing device (CFGER) 0x0006
Upper limit value exceeded (ULVE) 0x0007
Lower limit value underrun (LLVU) 0x0008
Data storage error (DSER) 0x0009
Process input data invalid (PDINV)
Maintenance events (EVT1)
Out of specification error (EVT2)
Port parameterization error (PPE)
Parameterization error (PRMER) 0x0010
Hardware error (HWER) 0x0010
IO-Link port 2
Similar to port 1 C1 2
IO-Link port 3
IO-Link port diagnostics PROFINET Diagnostics
IO-Link port 4
9.5 Using the data storage mode
Data storage mode
NOTE
Data storage mode is only available for devices complying with the IO-Link specifica-
tion V1.1.
In the IO-Link master, the data storage mode can be set using the parameter "data storage
mode".
n 00 = activated
n 01 = overwrite
n 10 = read in
n 11 = deactivated, clear
IO-Link-Master IO-Link-Device
(IOLM) (IOLD)
DS_UPLOAD_FLAG
Fig. 60: Data storage mode – general principle, Para. IOLD = parameters of the IO-Link device
A change of parameters in the device is indicated by the status of the DS_UPLOAD_FLAG bit:
n 0 = no changes in the device's parameter set
n 1 = changes in the device's parameter set (e. g. via DTM, at the device, etc.)
9.5.1 Parameter ”data storage mode” = activated

The synchronization of the parameter sets is bidirectional.
The actual data set (master or device) is valid:
The following applies:
n The data set in the device is actual, if DS_UPLOAD_FLAG = 1.
n The data set in the Master is actual, if DS_UPLOAD_FLAG = 0.
V01.00 | 2019/12 121

Operating
Using the data storage mode
Use Case 1: Parameterizing the Device Using e.g. a DTM

ü The IO-Link device is already installed in the system and connected to the master.
Parameterizing the device via DTM.
a DS_UPLOAD_FLAG = 1, parameter set in the device changed.
a The parameter data are transferred from the new IO-Link device to the IO-Link master.
IOLM IOLD
Fig. 61: Data storage mode activated – parameter set in the device changed
Use case 2: replace a defective device with a device in the delivery state.
ü The new IO-Link device has not been connected to the master before.
The parameters of the new device remain unchanged, DS_UPLOAD_FLAG = 0.
a The parameter data of the defective device are transferred from the IO-Link master to the
new IO-Link device.
IOLM IOLD
Fig. 62: Data storage mode activated – parameter set in the device unchanged
Use case 3: replace a defective device with a device with unknown (changed) parameters
ü The new IO-Link device has not been connected to the master before.
The parameters of the new device remain unchanged, DS_UPLOAD_FLAG = 1.
a The parameter data are transferred from the new IO-Link device to the IO-Link master.
IOLM IOLD
Fig. 63: Data storage mode activated – parameter set in the device changed
NOTE
If device replacement is necessary when data storage is activated, an IO-Link re-
placement device with unknown parameter data should be reset to its factory set-
tings before connection to the IO-Link master.
Turck IO-Link devices can be reset to factory settings via a system command using a
generic IO-Link-DTM and the device-specific IODD. For the reset of third party
devices, please read the corresponding manufacturer documentation.
9.5.2 Parameter ”data storage mode” = read in
n The data set in the device is always the reference data set.
n The synchronization of the parameter sets is unidirectional towards to the master.
n The status of the DS_UPLOAD_FLAG is ignored.
IOLM IOLD
Fig. 64: Data storage mode = read in – parameter set in the device changed
9.5.3 Parameter ”data storage mode” = overwrite

n The data set in the master is always the reference data set.
n The synchronization of the parameter sets is unidirectional towards to the device.
n The status of the DS_UPLOAD_FLAG is ignored.
IOLM IOLD
Fig. 65: Data storage mode = overwrite – parameter set in the master changed
9.5.4 Parameter ”data storage mode” = deactivated, clear

n The data set in the master is deleted.
n The synchronization of parameter sets is deactivated.
IOLM IOLD
Fig. 66: Data storage mode deactivated – no synchronization
V01.00 | 2019/12 123

Troubleshooting
Eliminate parameterization errors
10 Troubleshooting
If the device does not work as expected, proceed as follows:
Exclude environmental disturbances.
Check the connections of the device for errors.
Check device for parameterization errors.
If the malfunction persists, the device is faulty. In this case, decommission the device and re-
place it with a new device of the same type.
10.1 Eliminate parameterization errors
DXP channels
Error Possible causes: Remedy
DXP output The output is deactivated per default. Switch on the output via parameter Ac-
does not switch tivate output (DXP_EN_DO =1).
IO-Link channels
LED Diagnostics Possible causes: Remedy
behavior
DIA and IOL Data storage error IO-Link device according to IO- Set parameter Data storage mode to
flash red Link V1.0 connected IO-Link deactivated, clear.
devices in accordance with IO- a Data storage remain deactivated.
Link specification V1.0 do not
support data storage.
The data storage buffer contains Set parameter Data storage mode to
data of another device. deactivated, clear.
Re-activate the data storage if neces-
sary.
Wrong or missing The connected device does not Adapt the parameterization of the
device match the configured one IO-Link port (Vendor ID, Device ID,
(wrong vendor-ID, device-ID etc.) etc.) at the master.
The parameterization can be done
manually via DTM, the web server or
similar or by teaching the master us-
ing the IO-Link-Call (port 0 function,
sub index 67: Teach mode).
Process input data Certain IO-Link devices send a Deactivate the sending of the dia-
invalid process input data invalid diagnosis for the IO-Link port with the
gnosis if the process value can- parameter Process input data in-
not be measured. valid Ò No diagnostic generated.
11 Maintenance
Ensure that the plug connections and cables are always in good condition.
The devices are maintenance-free, clean dry if required.
11.1 Carry out firmware update via FDT/DTM

The firmware of the device can be updated via FDT/DTM. The PACTware FDT frame application,
the DTM for the device and the current firmware are available as downloads free of charge from
www.turck.com.
NOTICE
Interruption of the power supply during the firmware update
Risk of device damage due to faulty firmware update
Do not interrupt the power supply during the firmware update.
During the firmware update do not reset the power supply.
Example: update the firmware with the PACTware FDT frame application
Launch PACTware.
Right-click Host PC Ò Add device.
Fig. 67: Adding a Device in PACTware
V01.00 | 2019/12 125

Maintenance
Carry out firmware update via FDT/DTM
Select BL Service Ethernet and confirm with OK.
Fig. 68: Selecting the Ethernet interface
Double-click the connected device.

a PACTware opens the bus address management.
Fig. 69: Opening the busaddress management
Search for connected Ethernet devices: Click the Search icon.
Select the required device.
Fig. 70: Selecting the device
Click Firmware Download to start the firmware update.
Fig. 71: Starting the firmware update
Select the storage location and confirm with OK.

a PACTware shows the progress of the firmware update with a green bar at the bottom of
the screen.
V01.00 | 2019/12 127

Maintenance
Returning devices
Fig. 72: Firmware update in progress
12 Repair
The device must not be repaired by the user. The device must be decommissioned if it is faulty.
Observe our return acceptance conditions when returning the device to Turck.
12.1 Returning devices

Returns to Turck can only be accepted if the device has been equipped with a Decontamination
declaration enclosed. The decontamination declaration can be downloaded from
https://www.turck.de/en/retoure-service-6079.php
and must be completely filled in, and affixed securely and weather-proof to the outside of the
packaging.
13 Disposal
The devices must be disposed of correctly and must not be included in general
household garbage.
14 Technical Data
Technical data
Power supply
Power supply 24 VDC
Permisible range 18…30 VDC
n IO-Link n 20.4…28.8 VDC
Total current max. 4 A per voltage group
Operating current V1: min. 50 mA, max. 110 mA

V2: min.10 mA, max. 115 mA
Sensor/actuator supply VAUX2 Supply from V2, not short-circuit proof,
max. 4 A per group C0…C3
Potential isolation Galvanic isolation from V1 and V2 voltage group,
voltages up to 500 VDC
Connectors
Ethernet 2 × M8, 4-pole
Power supply 2 × M8, 4-pole
Digital in-/outputs M12, 5-pole
Isolation voltages
V1 to V2 ≥ 500 V AC
V1/V2 to field bus ≥ 500 V AC
System data
Transmission rate 10 Mbps/100 Mbps
Protocol detection Automatic, 192.168.1.254
Web server Integrated
Service interface Ethernet via P1 or P2
Field Logic Controller (FLC)
Supported from firmware version 3.1.10.0
Released as of ARGEE version 2.0.25.0
Modbus TCP
Address assignment Static IP, DHCP
Supported Function Codes FC1, FC2, FC3, FC4, FC5, FC6, FC15, FC16, FC23
Number of TCP connections 8
Register start address 0 (0x0000)
Register start address 2048 (0x0800)
Lokal port Port 502, fixed setting
EtherNet/IP
Address assignment according to EtherNet/IP standard
Device Level Ring (DLR) Supported
Quick Connect (QC) < 150 ms
Number of Class 3 (TCP) connections 3
Number of Class 1 (CIP) connections 10
Input Assembly Instances 103, 120, 121, 122, 123,124, 125
Output Assembly Instances 104, 150, 151, 152
V01.00 | 2019/12 129

Technical data
Technical data
Configuration Assembly Instance 106
PROFINET
PROFINET specification V 2.35
Conformance Class B (RT)
Address assignment DCP
MinCycle Time 1 ms
Fast Start-Up (FSU) < 150 ms
Diagnostics according to PROFINET Alarm Handling
Topology detection Supported
Automatic address setting Supported
Media Redundancy Protocol (MRP) Supported
System redundancy S2
Network load class 3
Digital inputs
Number of channels 4 DXP and 4 SIO
Input type PNP
Type of input diagnostics Channel diagnosis
Switching threshold EN 61131-2 type 3, PNP
Signal voltage, low level <5V
Signal voltage, high level > 11 V
Low level signal current < 1.5 mA
High-level signal current > 2 mA
Input delay 0.05 ms
Potential isolation Galvanic isolation to P1/P2,
voltage proof up to 500 V AC
Digital outputs
Number of channels 4 DXP
Output type PNP
Type of output diagnostics Channel diagnosis
Output voltage 24 VDC from potential group
Output current per channel 0.5 A, short-circuit-proof
Potential isolation Galvanic isolation to P1/P2,
voltage proof up to 500 V AC
IO-Link
Number of channels 4
IO-Link Pin 4 operated in IO-Link mode
IO-Link specification Version 1.1
IO-Link port type Class A
Frame type Supports all specified frame types
Supported devices Max. 32 byte input/32 byte output
n Input data n max. 32 Byte per channel
n Output data n max. 32 Byte per channel
Technical data
Transmission rate 4.8 kbps (COM 1)
38.4 kbps (COM 2)
230.4 kbps (COM 3)
Transmission cable Length: max. 20 m standard lines,
3- or 4-wire (depending on the application), unshiel-
ded
Mounting
Type of mounting Via 2 mounting holes, Ø 4.6 mm
Standard/Directive conformity
Vibration test According to EN 60068-2-6
Acceleration Up to 20 g
Shock test According to EN 60068-2-27
Drop and topple According to IEC 60068-2-31/IEC 60068-2-32
Electro magnetic compatibility According to EN 61131-2
Approvals and certificates CE, FCC
UL cond. cULus LISTED 21 W2, Encl.Type 1 IND.CONT.EQ.
General information
Dimensions (B × L × H) 32 × 144 × 32 mm
Operating temperature -40…+70 °C
Storage temperature -40…+85 °C
Operating height max. 5000 m
Protection class IP65/IP67/IP69K
MTTF 260 years acc. to SN 29500 (Ed. 99) 20 °C
Housing material PA6-GF30
Housing color Black
Metal screw 303 stainless steel
Material label Polycarbonate
Halogen-free Yes
FCC declaration
NOTE
This equipment has been tested and found to comply with the limits for a Class A di-
gital device, pursuant to part 15 of the FCC Rules. These limits are designed to
provide reasonable protection against harmful interference when the equipment is
operated in a commercial environment. This equipment generates, uses, and can ra-
diate radio frequency energy and, if not installed and used in accordance with the
instruction manual, may cause harmful interference to radio communications. Oper-
ation of this equipment in a residential area is likely to cause harmful interference in
which case the user will be required to correct the interference at his own expense.
V01.00 | 2019/12 131

Over 30 subsidiaries and over
60 representations worldwide!
D301369 | 2019/12
D301369 www.turck.com

Tben S2 4iol

Uploaded by

Copyright:

Available Formats

Tben S2 4iol

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Tben S2 4iol

Uploaded by

Copyright:

Available Formats

Your Global Automation Partner

7.4 Commissioning an IO-Link device with IO-Link V1.1.............................................. 26

1.1 Target groups

1.2 Explanation of symbols used

1.3 Additional documents

1.4 Feedback about these instructions

2 Notes on the Product

2.2 Scope of delivery

2.3 Legal requirements

2.4 Manufacturer and service

Outside Germany, please contact your local Turck representative.

3.1 Intended use

3.2 General safety notes

4.1 Device overview

Fig. 1: Dimensions TBEN-S2-4IOL

4.1.1 Display elements

4.2 Properties and features

4.3 Operating principle

4.4 Functions and operating modes

The required Ethernet protocol can be detected automatically or determined manually.

Automatic protocol detection

Manual Protocol Selection

4.4.2 IO-Link channels

4.4.3 Configurable digital channels – functions

5.1 Combine TBEN-S modules for mounting

5.1.1 Combine TBEN-S modules for composite mounting to a mounting plate

Fig. 2: Step 1 Fig. 3: Step 2

Fig. 4: Step 3 Fig. 5: Step 4

Fig. 6: Step 1 Fig. 7: Step 2

Fig. 8: Step 3 Fig. 9: Step 4

5.2 Attach TBEN-S modules to a mounting plate

Fig. 10: Mounting the device on a mounting plate

5.3 Mounting TBEN-S modules on a DIN rail (TS35)

Fig. 11: Mounting a module composite on a DIN rail

5.4 Mounting the device outdoors

Fig. 12: TBEN-S2-4IOL– equivalent wiring diagram and shielding concept

5.5.2 Fieldbus and I/O level shielding

Shielding Concept of the I/O Modules (I/O Level)

Shielding Concept of the Fieldbus Level

5.5.3 Grounding the device – I/O and fieldbus level

Fig. 16: Mounting the grounding clip

5.5.4 Grounding the device – mounting on a DIN rail

5.5.5 Grounding the device – mounting on a mounting plate

Fig. 17: M8 Ethernet connector

 Connect the device to Ethernet according to the pin assignment.

Fig. 18: Ethernet connectors – pin assignment P1 and P2

Fig. 19: M8 Ethernet plug connectors for connecting the fieldbus

Fig. 20: Pin layout of the Ethernet connections

6.2.1 Supply concept

Fig. 21: Power supply of TBEN-S2-4IOL

6.3 Connecting IO-Link devices and digital sensors

Fig. 22: Pin assignment C0…C3

Fig. 23: Turck Service Tool – Start screen

The Turck Service Tool displays the connected devices.

Fig. 24: Turck Service Tool – found devices

 Click the required device.

Fig. 25: Turck Service Tool – select the device to be addressed

Fig. 26: Turck Service Tool – Change device configuration

7.3 Commissioning an IO-Link device with IO-Link V1.0

Connect the device to Ethernet according to the pin assignment.

Click the required device.

Connect the IO-Link V1.1 device.

Select Device view Ò Device overview.

Activate the Write access via a rising edge at REQ.