turck TBEN-Lx-8IOL Operating Instructions Manual

Your Global Automation Partner

TBEN-L…-8IOL

IO-Link Master Module

Operating instructions

2

Hans Turck GmbH & Co. KG | T [phone] | F [phone] | [e-mail] | www.turck.com

1About this manual 5

1.1 Documentation concept 5

1.2 Explanation of symbols used 6

1.2.1 Warnings 6

1.3 General notes 7

1.3.1 Prescribed use 7

1.3.2 Notes concerning planning/installation of this product 7

2 Further documentation 9

2.1 Product family TBEN-L 9

3IO-Link – Basics 11

3.1 IO-Link- interface – the fieldbus independent communication interface 11

3.1.1 Communication 11

3.1.2 Data transmission 11

3.1.3 Transmission media 12

3.1.4 Fieldbus/Ethernet integration 13

4 TBEN-Lx-8IOL 15

4.1 Product identification 15

4.2 Block diagram 16

4.3 Technical data 17

4.4 Wiring diagrams 18

4.4.1 Ethernet/voltage supply 18

4.4.2 IO-Link ports 18

4.5 Process data 19

4.5.1 Process input data 19

4.5.2 Process output data 21

4.6 Parameters 22

4.6.1 Adaptation of the process data mapping 28

4.7 Device status 29

4.7.1 LED behavior 29

4.7.2 Diagnostic data 31

4.7.3 Diagnostic telegram 31

4.7.4 Status and control word 35

V01.00 | 2016/12

4.8 IO-Link data storage 36

4.8.1 General 36

4.8.2 Parameter "data storage mode" = activated 37

4.8.3 Parameter "data storage mode" = read in 39

1

4.8.4 Parameter "data storage mode" = overwrite 39

4.8.5 Parameter "data storage mode" = deactivated, clear 39

4.9 IO-Link - functions for acyclic communication 40

4.9.1 Port functions for port 0 (IO-Link master) 40

4.10 IO-Link and Turck device DTMs 45

4.10.1 Topology-Scan 45

4.10.2 Special DTM parameters 46

5 TBEN-Lx-8IOL with Modbus TCP 47

5.1 General 47

5.1.1 Implemented Modbus functions 47

5.1.2 Modbus registers 47

5.2 Data width of the TBEN-Lx-8IOL in the Modbus-register area 52

5.3 Register mapping TBEN-Lx-8IOL 52

5.4 Error behavior (watchdog) 53

5.4.1 Behavior of outputs 53

5.4.2 Behavior of the BUS LED 54

5.5 Parameters and diagnostic messages of the I/O channels 54

6 TBEN-Lx-8IOL with EtherNet/IP™ 55

6.1 EDS-file 55

6.2 QC - QuickConnect 55

6.3 Diagnostic messages via the process data 55

6.4 EtherNet/IP™-standard classes 56

6.4.1 Identity Object (0x01) 56

6.4.2 Assembly Object (0x04) 57

6.4.3 Connection Manager Object (0x06) 61

6.4.4 TCP/IP Interface Object (0xF5) 62

6.4.5 Ethernet Link Object (0xF6) 65

6.5 VSC-Vendor Specific Classes 67

6.5.1 Class Instance der VSCs 67

6.5.2 Gateway Class (VSC 100) 68

6.5.3 Miscellaneous Parameters Class (VSC 126) 71

6.5.4 IO-Link Port Class 137 (89h) 72

6.5.5 IO-Link Events Class 138 (90h) 75

6.5.6 VAUX Control Class 161 (A1h) 76

6.5.7 Basic Class 153 (99h) 78

7 TBEN-Lx-8IOL with PROFINET 81

7.1 GSDML-file 81

2

Hans Turck GmbH & Co. KG | T [phone] | F [phone] | [e-mail] | www.turck.com

7.2 Configuration, TBEN-Lx-8IOL 81

7.3 FSU - Fast Start-Up 82

7.4 PROFINET-diagnostics - TBEN-Lx-8IOL 82

7.5 Parameters 84

7.5.1 General module parameters 84

7.5.2 Parameters for I/O channels 84

7.6 Description of user data for acyclic services 85

7.6.1 Description of the acyclic device user data 85

7.6.2 Description of the acyclic I/O-channel user data 86

7.6.3 IM99 (IOL_M) 87

8 The IO-Link function block IOL_CALL 89

8.1 General 89

8.2 IOL_CALL in accordance with IO-Link specification 89

8.2.1 Input variables 90

8.2.2 Output variables 91

8.2.3 STATUS - communication error status 92

8.2.4 IOL_STATUS 93

9 Integration of the IO-Link master in TIA Portal 95

9.1 Example project 95

9.1.1 Used hardware 95

9.1.2 Used software 95

9.2 Hardware configuration 96

9.2.1 Configuration of the IO-Link master 96

9.2.2 Configuration of the IO-Link ports 99

9.3 Using the "IOL_LINK_DEVICE" function block in TIA Portal 100

9.3.1 Example accesses with IO_LINK_DEVICE 101

10 Appendix 109

10.1 Start-up: IO-Link-Device with IO-Link V1.0 109

10.2 Start-up: IO-Link-Device with IO-Link V1.1 110

10.3 Start-up problems - frequent failure causes 111

10.3.1 IO-Link 111

10.3.2 DXP-channels 111

V01.00 | 2016/12

3

4

Hans Turck GmbH & Co. KG | T [phone] | F [phone] | [e-mail] | www.turck.com

1 About this manual

1.1 Documentation concept

This document contains all information about the Turck IO-Link master module TBEN-Lx-8IOL of the
TBEN-L product series with 4 IO-Link ports Class A at connectors C0 to C3 and 4 IO-Link ports Class B.

The following chapters contain:

 A general device description and its process data image in the different Ethernet protocols,

 A short description of the communication interface IO-Link,

 A description of the IO-Link master functionality,

 A general description of the function block (FB) IOL_Call according to the IO-Link specification and

its in- and output variables,

 An example for the IO-Link-Master's integration in TIA Portal V13 including a description of the Sie-

mens function block IOL_DEVICE in PROFINET,

 Helpful information for the operation of IO-Link devices and a list of possible 

failure causes

V01.0 | 2016/12

5

About this manual

1.2 Explanation of symbols used

1.2.1 Warnings

Action-related warnings are placed next to potentially dangerous work steps and are marked by
graphic symbols. Each warning is initiated by a warning sign and a signal word that expresses the
gravity of the danger. The warnings have absolutely to be observed:

DANGER!

DANGER indicates an immediately
injury, if not avoided.

WARNING!

WARNING indicates a potentially dangerous situation with medium
severe injury, if not avoided.

ATTENTION!

ATTENTION indicates a situation that may lead to property damage, if it is not avoided.

dangerous situation, with high risk, the death or severe

risk, the death or

NOTE

In NOTES you find tips, recommendations and important information. The notes facilitate
work, provide more information on specific actions and help to avoid overtime by not fol­lowing the correct procedure.

 CALL TO ACTION

This symbol identifies steps that the user has to perform.

 RESULTS OF ACTION

This symbol identifies relevant results of steps

6

Hans Turck GmbH & Co. KG | T [phone] | F [phone] | [e-mail] | www.turck.com

1.3 General notes

This manual includes all information necessary for the prescribed use of the modules of type TBEN­Lx-8IOL. It has been specially conceived for personnel with the necessary qualifications.

1.3.1 Prescribed use

The devices described in this manual must be used only in applications prescribed in this manual or
in the respective technical descriptions, and only with certified components and devices from third
party manufacturers.

Appropriate transport, storage, deployment and mounting as well as careful operating and thor­ough maintenance guarantee the trouble-free and safe operation of these devices.

1.3.2 Notes concerning planning/installation of this product

All respective safety measures and accident protection guidelines must be considered carefully and
without exception.

V01.0 | 2016/12

7

About this manual

8

Hans Turck GmbH & Co. KG | T [phone] | F [phone] | [e-mail] | www.turck.com

2 Further documentation

2.1 Product family TBEN-L

 User manual, D301324 - 

„TBEN-L/TBDP-L Compact I/O modules for Ethernet/PROFIBUS-DP“


The user manual for the TBEN-L product family contains comprehensive topics like for example:

–

General technical properties

– Mounting the TBEN-L-modules

– Connection options at module

– General information about Ethernet, the multiprotocol functionality and about the single pro-

tocols

– A description of the web server

– Information about the electrical installation

V01.0| 2016/04

D301368 - 0815 TBEN-S2-4IOL

9

Further documentation

10

Hans Turck GmbH & Co. KG | T [phone] | F [phone] | [e-mail] | www.turck.com

3 IO-Link – Basics

3.1 IO-Link- interface – the fieldbus independent communication interface

IO-Link is a fieldbus-independent communication interface for sensors and actuators.

It is based on the IO-Link specification "IO-Link Interface and System Specification" version 1.1.2,
November 2012, and on the IEC 61131-9 (2013-09), ed. 1.0, „Programmable controllers - part 9: Sin­gle-drop digital communication interface for small sensors and actuators (SDCI)“.

IO-Link is a point-to-point connection between an IO-Link device (e.g. sensor, I/O hub, valve termi­nal) and the IO-Link master. Up to now, the binary connection was only designed for transferring
switching information, but IO-Link now allows 2 bytes to be transferred normally in a 2.3 ms cycle
via a combined switching status and data channel.

Other information can be exchanged in addition to the process values, such as parameters or diag­nostic messages.

This enables communication with sensors and actuators down to the "last meter" to be established
for universal communication.

Further information: : www.io-link.com

3.1.1 Communication

 Standard I/O-connection technologies in point-to-point connection, unshielded, 20 m wire

length

 Cyclic process data transfer in typ. 2.3 ms

 Parallel service data exchange without any impact on the process data

 Communication via 24 V-pulse modulation, standard UART protocol

 Communication between master and device in 3 different transmission speeds

–

4.800 Baud (COM 1)

– 38.400 Baud (COM 2)

– 230.400 Baud (COM 3)

3.1.2 Data transmission

Basically 4 different types of data exist, which are transmitted either cyclically or acyclically.

 Process data  cyclic data exchange

 Value status  cyclic data exchange

 Device data  acyclic data exchange

 Events  acyclic data exchange

V01.0| 2016/04

Process data:

The devices' process data are transmitted cyclically, whereas the process data size is defined
through the device. The device process data can contain from 0 to 32 Byte (for both in- and output).

11

D301368 - 0815 TBEN-S2-4IOL

IO-Link – Basics

Value status:

The value status displays if process data are valid or not. It is transmitted cyclically with the process
data.

Device data:

Device data are parameters, identification data and diagnostic information. The transmission is
done acyclically and only on demand of the IO-Link master.

Events:

Events are error messages or warnings/maintenance data. Error messages are transmitted from the
device to the PLC or similar via the IO-Link master. The IO-Link master itself can also transmit events
and status information. Those events can be for example an open circuit, communication loss or an
overload.

3.1.3 Transmission media

IO-Link does not require any special wiring. The sensors and actuators can continue to be connected
using the proven, attractively priced and unshielded industrial cables.

The operating modes available for selection are the standard switch mode and the communication
mode.

12

Hans Turck GmbH & Co. KG | T [phone] | F [phone] | [e-mail] | www.turck.com

3.1.4 Fieldbus/Ethernet integration

FIELDBUSETHERNET

CONVERNTIONAL I/O

I/O-Hub

I/O-Hub

Inclination Encoder, Linear Position Inductive CouplersProximity Temperature, Pressure, Flow LED Indicator Ultrasonic and Photoelectric Sensors

 Usage of the standard-transport mechanisms of established fieldbusses/sensor/actuator busses

(DPV0, DPV1, Ethernet …)

 Simple integration in engineering systems by means of configuration files (GSD, GSDML, …)

 Comfortable usage of even complex product features by means of tool based engineering (FDT/

DTM, …)

Fig. 1: IO-Link overview

D301368 - 0815 TBEN-S2-4IOL

V01.0| 2016/04

13

IO-Link – Basics

14

Hans Turck GmbH & Co. KG | T [phone] | F [phone] | [e-mail] | www.turck.com

4 TBEN-Lx-8IOL

4.1 Product identification

The TBEN-Lx-8IOL is the 8-channel IO-Link-master module of the product family TBEN-L.

Like all modules of the TBEN-L-product family, the TBEN-Lx-8IOL is a device with Turck multiproto­col functionality, which means, it can be used in the three Ethernet protocols PROFINET, EtherNet/
IP™ and Modbus TCP. An integrated Ethernet-switch allows the building up of a line topology.

Besides the eight IO-Link channels (4 with IO-Link Class A and 4 with IO-Link Class B), the TBEN-Lx­8IOL provides four universal digital DXP-channels (PNP).

The eight IO-Link channels can be parameterized independently and can optionally be operated in
IO-Link mode (IOL) or in standard I/O mode (DI mode).

Thanks to the "Simple IO-Link Device Integration (SIDI)“, Turck IO-Link devices can directly be
selected from the device GSDML in PROFINET.

The four universal digital channels are designed as DXP-channels and can therefore be parameter­ized as in- or output.

Properties:

 8-channel IO-Link master according to IO-Link specification V1.1

–

four IO-Link Class A-channels (C0 to C3)

– four IO-Link Class B-channels (C4 to C7)

 4 universal digital channels, PNP, channel diagnostics, 0.5 A at the connectors C0 to C3

 Connector for voltage supply:

–

TBEN-L4-8IOL: 7/8“ (4-pole)

– TBEN-L5-8IOL: 7/8“ (5-pole)

V01.0| 2016/12

15

TBEN-Lx-8IOL

ERR

BUS

PWR

µC

Supply

µC

+2–3+1–

4

V1 V2

+2–3+1–

4

V1 V2

X1 X2

IN Diag
OUT Diag
IO-Link Data

V1 Diag V2 Diag

IO-Link Diag

Ethernet

V1 +

IN Diag

IO-Link Diag

IO-Link Data

1 V

AUX1

(V1)

2 IN/OUT

(V1)

4 C/Q(V1)

OUT Diag

3 GND (V1)

In/OutputClass A

I/O

IO-Link

µC

5 n.c.

V1 +

V2 +

IO-Link

IN Diag

IO-Link Diag

IO-Link Data

1 V

AUX1

(V1)

(V2)

4 C/Q(V1)

OUT Diag

3 GND (V1)

5 GND (V2)

In/OutputClass B

I/O

IO-Link

µC

V2 +

V1 +

IO-Link

P2P1

4

1

3

2

4

1

3

2

ETH2ETH1

Ethernet

2 V

AUX2

4.2 Block diagram

Fig. 2: Block diagram TBEN-Lx-8IOL

16

Hans Turck GmbH & Co. KG | T [phone] | F [phone] | [e-mail] | www.turck.com

4.3 Technical data

Power supply

Supply voltages 24 V DC from operating voltage

Permissible range 18 … 30 V DC

Operating current < 120 mA

Sensor/actuator supply V

Sensor/actuator supply V

Potential isolation  500 V (V2 to Ethernet and V1)

IO-Link

Number of ports 8

IO-Link specification V1.0, V1.1 according to IEC 61 61131-9

IO-Link port type Class A at C0 to C3

Frame type Supports all specified frame types

Process data for IO-Link devices

– Input data max. 32 Byte per channel

– Output data max. 32 Byte per channel

Transmission rate 4,8 kbps (COM 1)

Transmission cable Length: max. 20 m

AUX1

AUX2

IO-Link:
20,4 … 28,8 V DC (acc. to IO-Link standard)

Total current max. 9 A per module

Supply from V1
short-circuit proof, max. 4 A for C0 & C4, 
short-circuit proof, 2 A per group C1 - C4, C5 - C8

Class B-supply from V2
short-circuit proof, 2 A per connector C0-C7

Class B at C3 to C7

38,4 kbps (COM 2)
230,4 kbps (COM 3)

standard cables,
3- or 4-wire (depending on the application),
unshielded

V01.0| 2016/12

NOTE

General data for the products of the TBEN-L-series can be found in D301324 - „TBEN-L/
TBDP-L Compact I/O modules for Ethernet/PROFIBUS-DP“.

17

TBEN-Lx-8IOL

4

1

3

2

5

v

1 = V

aux

1 (V1)
2 = DXP (V1)
3 = GND (V1)
4 = C/Q (V1)
5 = n.c.

C0...C3

4

1

3

2

5

v

1 = V

aux

1 (V1)

2 = V

aux

2 (V2)
3 = GND (V1)
4 = C/Q (V1)
5 = GND (V2)

C4...C7

4.4 Wiring diagrams

4.4.1 Ethernet/voltage supply

NOTE

Information about network connection and voltage supply can be found in the user man­ual D301324: „TBEN-L/TBDP-L Compact I/O modules for Ethernet/PROFIBUS-DP“

4.4.2 IO-Link ports

Pin 1: VAUX1 switchable via process data
Pin 4: IO-Link or digital input

C0…C3: IO-Link Master Class A
Pin 2: digital in- or output (DXP)

C4…C7: IO-Link Master Class B
Pin2: switchable Class B supply (VAUX2)

Fig. 3: Pin assignment of M12 x 1-connectors, 5-pole

ATTENTION!

Wrong supply of IO-Link devices

Damage to the electronics

 The IO-Link devices must only be supplied with the voltage provided at the supply ter-

minals of the TBEN.

s

ATTENTION!

Connection of Class A devices to Class B ports

Loss of the galvanic isolation

 Only use Class A devices with signals on pin 1, pin 3 and pin 4 at Class B ports. 

The connection of Class A devices with signals on pin 2 and pin 5 leads to the loss of the
galvanic isolation.

18

Hans Turck GmbH & Co. KG | T [phone] | F [phone] | [e-mail] | www.turck.com

4.5 Process data

4.5.1 Process input data

Byte Bit 7 Bit 6 Bit 5 Bit 4 Bit 3 Bit 2 Bit 1 Bit 0

Basic

IO-Link ports IO-Link process input data

Port 1 4 - 35
Port 2 36 - 67
Port 3 68 - 99
Port 4 100 - 131
Port 5 132 - 163
Port 6 164 - 195
Port 7 196 - 227

Port8 228 - 259

VAUX1/VAUX2 Diagnostics (see Diagnostic data, page 31)

DXP-channels

IO-Link ports (see Diagnostic data, page 31)

Port 1 264 EVT1 EVT2 PDINV HWER DSER CFGER PPE -

Port 2 266 + 267 assignment similar to port 1
Port 3 268 + 269 assignment similar to port 1
Port 4 270 + 271 assignment similar to port 1
Port 5 272 + 273 assignment similar to port 1
Port 6 274 + 275 assignment similar to port 1
Port 7 276 + 277 assignment similar to port 1
Port 8 278 + 279 assignment similar to port 1

Module Module status (status word)

0 DXP7 DI6 (SIO) DXP5 DI4 (SIO) DXP3 DI2 (SIO) DXP1 DI0 (SIO)
1 - DI14 (SIO) - DI12 (SIO) - DI10 (SIO) - DI8 (SIO)
2 - DVS6 - DVS4 - DVS2 - DVS0
3 - DVS14 - DVS12 - DVS10 - DVS8

structure depends on the channel parameterization

(0 - 32 byte per channel)

260

261

262

263--------

265 GENER OVL VHIGH VLOW ULVE LLVU OTMP PRMER

280 Qualifier (1st Event)
281 Port (1st Event)
282 Event Code high byte (1st Event)
283 Event Code low byte (1st Event)

... ...

340 Qualifier (16th Event)
341 Port 16th Event)
342 Event Code high byte (16th Event)
343 Event Code low byte (16th Event)

344 + 345

VErrV1
C7K14

VErrV2
C7K15

ERR

DXP7

V2 - Diag

-FCE----V1-

VErrV1
C6K12

VErrV2
C6K13

-

VErrV1
C5K10

VErrV2
C5K11

ERR

DXP 5

(see Status and control word, page 35)

VErrV1

C4K8

VErrV2

C4K9

-

IO-Link Events

VErrV1C3

K6K7

----

ERR

DXP 3

VErrV1C2

K4K5

-

VErrV1C1

K2K3

ERR

DXP 1

VErrV1C0

K0K1

-

V01.0| 2016/12

19

TBEN-Lx-8IOL

Name Value Meaning

DIx Digital input

0 No signal at DI (pin 4, SIO)

1 Input signal at DI (pin 4, SIO)

DXPx DXP input

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 valid.

Possible causes:

– Sensor supply is below the admissible range,
– IO-Link port is parameterized as simple digital input,
– No device connected to the masters,
– No input data received from the connected device (only valid for devices with an

input data length > 0),

– No reaction from the connected device to the sending of output data (only valid

for devices with an output data length > 0),

– The connected device sends an error "process input data invalid.

1 The IO-Link data are valid.

IO-Link process input data

Process input data of the connected device
The order of the IO-Link process input data can be changed via the parameter "Process input data mapping"
(

page 22).

Diagnostics

(see Diagnostic data, page 31)

20

Hans Turck GmbH & Co. KG | T [phone] | F [phone] | [e-mail] | www.turck.com

4.5.2 Process output data

Byte

Basic 0 DXP7 - DXP5 - DXP3 - DXP1 -

IO-Link ports IO-Link process output data

Port 1

Port 2 34 - 65

Port 3 66 - 97

Port 4 98 - 129

Port 5 130 - 161

Port 6 162 - 193

Port 7 194 - 225

Port 8 226 - 257

VAUX1

VAUX2

2 - 33

258

259

Bit 7 Bit 6 Bit 5 Bit 4 Bit 3 Bit 2 Bit 1 Bit 0

1 reserved

structure depends on the channel parameterization

(0 - 32 byte per channel)

VAUX1 Pin1

C7 (Ch14)

VAUX2 Pin2

C7 (Ch15)

Name Value Meaning

DXPx DXP output

IO-Link process output data

Process output data of the connected device
The order of the IO-Link process output data can be changed via the parameter "Process output data map­ping" (page 22).

VAUX1 pin 1 Cx (Chy/
Chz)

VAUX2 Pin 2 Cx (Chy) 0 The Class B supply at Pin2 of the connector is switched off.

VAUX1 Pin1

C6 (Ch12)

VAUX2 Pin2

C6 (Ch13)

0 Output inactive

1 Output active, max. output current 2 A

0 The 24 VDC sensor/actuator supply at Pin1 of the connector is

1 The 24 VDC sensor/actuator supply at Pin1 of the connector is

1 The Class B supply at Pin2 of the connector is switched on.

VAUX1 Pin1

C5 (Ch10)

VAUX2 Pin2

C5 (Ch11)

switched off.

switched on.

VAUX1 Pin1

C4 (Ch8)

VAUX2 Pin2

C4 (Ch9)

VAUX1 Pin1

C3 (Ch6/7)

VAUX1 Pin1

C2 (Ch4/5)

VAUX1 Pin1

C1 (Ch2/3)

VAUX1 Pin1

C0 (Ch0/1)

V01.0| 2016/12

21

TBEN-Lx-8IOL

4.6 Parameters

The module provides 4 byte of module parameters and 16 byte of IO-Link port-parameters for each
IO-Link port.

Byte Bit 7 Bit 6 Bit 5 Bit 4 Bit 3 Bit 2 Bit 1 Bit 0

Basic

Port 1 4

Port 2 20 - 35

Port 3 36 - 51

Port 4 52 - 67

Port 5 68 - 83

Port 6 94 - 99

Port 7 100 - 115

Port 8 116 - 131

VAUX1-
monitoring

VAUX2-
monitoring

0 SRO7 - SRO5 - SRO3 - SRO1 -

1-

2 EN DO7 - EN DO5 - EN DO3 - EN DO1 -

3-

5 Cycle time

6 Process output data

7 - 11 reserved

12 Vendor ID (LSB)

13 Vendor ID (MSB)

14 Device ID (LSB)

15 Device ID

16 Device ID

17 Device ID (MSB)

18 reserved

19 reserved

132 VAUX1 Pin1 C0 (Ch0/1)

133 VAUX1 Pin1 C1 (Ch2/3)

134 VAUX1 Pin1 C2 (Ch4/5)

135 VAUX1 Pin1 C3 (Ch6/7)

136 VAUX1 Pin1 C4 (Ch8)

137 VAUX1 Pin1 C5 (Ch10)

138 VAUX1 Pin1 C6 (Ch12)

139 VAUX1 Pin1 C7 (Ch14)

140 - 143 reserved

144 VAUX2 Pin2 C4 (Ch9)

145 VAUX2 Pin2 C5 (Ch11)

146 VAUX2 Pin2 C6 (Ch13)

147 VAUX2 Pin2 C7 (Ch15)

GSD

Start-Up

mapping

Quick

data storage mode Mode

Process input data map-

ping

Assignment similar to port 1 (byte 4 - 19 )

Diagnostics

deactivate web server

Process input

data invalid

Revision

22

Hans Turck GmbH & Co. KG | T [phone] | F [phone] | [e-mail] | www.turck.com

Name Meaning

Value A = default

SRO Manual output reset after overcurrent

00 = no A The output switches on automatically after an overload.

1 1 = yes The output is manually switched-off after an overload until a new

set-command is given (rise and fall).

EN DO Activate output

00 = no A The output at pin 2 is deactivated.

1 1 = yes The output at pin 2 is activated.

Mode

0000 IO-Link without 

validation A

Pin 4 is operated in IO-Link mode.
The master does not check if the connected device matches the
configured one.

0001 IO-Link with family

compatible device

4 is operated in IO-Link mode.
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 diagnos­tic information can be read and respectively written.

0010 IO-Link with compati-

ble device

4 is operated in IO-Link mode.
The master checks if the Vendor ID and the Device ID of the con­nected device match those of the configured 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 possible.
If writing the Device ID is not successful, then process data
exchange is not possible. The device remains in the safe state (Pre­Operate). Parameters and diagnostic information can be read and
respectively written.

0011 IO-Link with 

identical device

4 is operated in IO-Link mode.
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 communication is
established, but there is no process data exchange. The device
remains in the safe state (Pre-Operate). Parameters and diagnos­tic information can be read and respectively written.

0100 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 DI-mode. The port remains
in DI mode 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-mode).

00

10

DI Pin 4 is operated as simple digital input.

Data storage is not supported.

V01.0| 2016/12

23

TBEN-Lx-8IOL

Name Meaning

Value A = default

NOTE

Parameter Mode", "DI (with parameter access)“:
In case of a parameter access, the IO-Link communication at the port is started.
Switching signals are interrupted.

Data storage mode

Synchronization of parameter data of IO-Link devices (storing the parameter
master).
If the synchronization is not possible, a diagnostic message is displayed (DS

31

). In this case select option "11 = deactivated, clear" in order to clear the data buffer of the device.

Information about data storage, see

00 activated Synchronization of parameter data activated. The actual data

01 overwrite Synchronization of parameter data activated, the data in the mas-

10 read in Synchronization of parameter data activated. The data in the con-

11 deactivated, clear A Synchronization of parameter data deactivated. The data set in

IO-Link data storage, page 36

(master or device) serve as the reference data.

ter serve as reference data.

nected IO-Link device serve as reference data.

the master is deleted.

of the connected device in the

, see Diagnostic data, page

ER

NOTE

IO-Link devices in accordance with IO-Link specification V1.0 do not support data storage. In this
case the data storage has to be deactivated (data storage mode: 11 = deactivated, clear).

Activate Quick Start-Up

For fast applications (e.g. tool changing applications) th
The start-up time defined in the IO-Link specification (TSD = Device Detection Time) is reduced.

00 no A The start-up time is within the specified range (0.5 s). All IO-Link

devices in accordance with the specification can be operated.

01 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.

e start-up time of IO-Link devices can be shortened.

24

Hans Turck GmbH & Co. KG | T [phone] | F [phone] | [e-mail] | www.turck.com

Name Meaning

Value A = default

Device parameterization via GSD

0 inactive A The port is generic or is not parameterized.

1 active In PROFINET the port is parameterized with a specific device type

from the GSDML-file.

Cycle time

00 automatic A The Master reads the minimum cycle time from the connected

device.

0×01 - 
0×BF

0.8 to 132.8 ms Settable in steps of 0.8 or 1.6 ms. 

(see page 27)

Revision

00 automatic A The Master defines the IO-Link-revision automatically.

01 V1.0 IO-Link-Revision V 1.0 is used.

Process input data invalid

00 diagnostics generated 

Diagnosis A

01 no diagnostics gener-

If the process data are invalid, a respective diagnostic message is
generated.

Invalid process data do not cause a diagnostic message.
ated 
Diagnosis

Deactivate diagnostics

Influences the sending of IO-Link-Events from the master to the fieldbus. Depending on the parameteriza­tion, the master transmits Events based on their priority to the fieldbus or not.

00 no The master transmits all IO-Link Events to the fieldbus.

01 notifications The master transmits all IO-Link Events to the fieldbus except for

IO-Link notifications.

10 Notifications and warn-

ings A

The master transmits all IO-Link Events to the fieldbus except for

IO-Link notifications and warnings.

11 yes The master doesn't transmit any IO-Link Event to the fieldbus.

Process input data mapping

Optimization of the process data mapping for the used fieldbus:
The I/O-Link-data can be swapped depending on the used fieldbus in order to achieve an optimized data
mapping on the fieldbus side.

00 direct A The process data are not swapped.

(0×0123 4567 89AB CDEF)

01 swap 16 bit The bytes are swapped per word.

(0×2301 6745 AB89 EFCD)

10 swap 32 bit The bytes are swapped per double word.

(0× 6745 2301 EFCD AB89)

11 swap all All bytes are swapped.

(0×EFCD AB89 6745 2301)

Process output data mapping

see: Process input data mapping

V01.0| 2016/12

25

TBEN-Lx-8IOL

Name Meaning

Value A = default

Vendor ID

0x0000 - 0xFFFF Enter the IDs for the port configuration check.

Device ID

0x0000 - 0xFFFF

VAUX1 Pin 1 Cx (Chy/Chz)

00 24 VDC A The 24 VDC sensor/actuator supply at Pin1 of the connector is

switched on.

01 switchable The 24 VDC sensor/actuator supply at Pin1 of the respective con-

nector is switchable via the process data, see also

put data, page 21

10 Out The 24 VDC sensor/actuator supply at Pin1 of the connector is

switched off.

VAUX2 Pin 2 Cx (Chy)

00 24 VDC A The Class B supply at Pin2 of the respective connector is switched

on.

01 switchable The Class B supply at Pin2 of the respective connector is switch-

able via the process data, see also

21

.

10 Out The Class B supply at Pin2 of the respective connector is switched

off.

.

Process output data, page

Process out-

26

Hans Turck GmbH & Co. KG | T [phone] | F [phone] | [e-mail] | www.turck.com

Values for the parameter "cycle time" [ms]:

Time Value Time Value Time Value Time Value Time Value Time Value

auto A 0×00 15.2 0×56 30.4 0×7C 59.2 0×91 89.6 0×A4 120 0×B7

0.8 0×08 16 0×58 31.2 0×7E 60.8 0×92 91.2 0×A5 121.6 0×B8

1.6 0×10 16.8 0×5A 32 0×80 62.4 0×93 92.8 0×A6 132.2 0×B9

2.4 0×18 17.6 0×5C 33.6 0×81 64 0×94 94.4 0×A7 124.8 0×BA

3.2 0×20 18.4 0×5E 35.2 0×82 65.6 0×95 96 0×A8 126.4 0×BB

4 0×28 19.2 0×60 36.8 0×83 67.2 0×96 97.6 0×A9 128 0×BC

4.8 0×30 20 0×62 38.4 0×84 68.8 0×97 99.2 0×AA 129.6 0×BD

5.6 0×38 20.8 0×64 40 0×85 70.4 0×98 100.8 0×AB 131.2 0×BE

6.4 0×40 21.6 0×66 41.6 0×86 72 0×99 102.4 0×AC 132.8 0×BF

7.2 0×42 22.4 0×68 43.2 0×87 73.6 0×9A 104 0×AD - -

8 0×44 23.2 0×6A 44.8 0×88 75.2 0×9B 105.6 0×AE - -

8.8 0×46 24.0 0×6C 46.4 0×89 76.8 0×9C 107.2 0×AF - -

9.6 0×48 24.8 0×6E 48 0×8A 78.4 0×9D 108.8 0×B0 - -

10.4 0×4A 25.6 0×70 49.6 0×8B 80 0×9E 110.4 0×B1 - -

11.2 0×4C 26.4 0×72 51.2 0×8C 81.6 0×9F 112 0×B2 - -

12.0 0×4E 27.2 0×74 52.8 0×8D 83.2 0×A0 113.6 0×B3 - -

12.8 0×50 28 0×76 54.4 0×8E 84.8 0×A1 115.2 0×B4 - -

13.6 0×52 28.8 0×78 56 0×8F 86.4 0×A2 116.8 0×B5 - -

14.4 0×54 29.6 0×7A 57.6 0×90 88 0×A3 118.4 0×B6 - -

automatic: The lowest cycle time supported by the device is taken from the table.

A

V01.0| 2016/12

27

TBEN-Lx-8IOL

4.6.1 Adaptation of the 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"" (see Parameters, page 22).

Example mapping for field buses with Little Endian-format:

Maping from master 
 fieldbus  PLC

Byte (A) Byte (A)

Status Byte 0

Byte 1 Control

PORT1

Byte 2 temperature Low byte 2 byte process

Byte 3 High byte Low byte

PORT2

Byte 4 position Low byte 2 byte process

Byte 5 High byte Low byte

PORT3

Byte 6 Digital signal 0... 7 2 byte process

Byte 7 Digital signal 8 ...15 Digital signal 8 ...15

PORT4

Byte 8 Diagnosis 4 byte process

Byte 9 Counter/

Byte 10 High byte Low byte

Byte 11 MSByte Diagnosis

position value

Low byte High byte

Devices at channel  Parametrization

of the channel

data 

swap 16 bit)

(

data 

swap 16 bit)

(

data 

direct)

(

swap all)

data (

Process output data mapping

IO-Link device

temperature High byte

position High byte

Digital signal 0... 7

Counter/
position value

MSByte

A Low byte, the lowest byte Low-Byte

High byte High-Byte
MSByte: Most Significant Byte





28



Hans Turck GmbH & Co. KG | T [phone] | F [phone] | [e-mail] | www.turck.com

4.7 Device status

4.7.1 LED behavior

The following table describes the protocol-independent behavior of the device LEDs.

The protocol specific LED behavior in PROFINET, EtherNet/IP™ and Modbus TCP is described in the
respective chapters.

LED Color Status Meaning Remedy

PWR

ETHx greenon Link established,100 Mbps

ERR greenon No diagnostic message available

greenoff V1 missing or < 18 V DC Check V1

on V1 and V2 OK -

blinking V2 missing or < 18 V DC Check V2

Red on V2 missing or < 18 V DC Check V2

the behavior of the PWR-LED at undervoltage of V2 can be set via parameter "LED behavior (PWR)
at V2 undervoltage.

blinking Ethernet Traffic, 100 Mbps

yel­low

- off No Ethernet link. Check the Ethernet connection.

on Link established,10 Mbps

blinking Ethernet Traffic, 10 Mbps

red on Diagnostic message pending

BUS greenon Active connection to a master -

blinking Device is ready for operation -

Red on IP address conflict or restore mode

or timeout

blinking Blink-/wink-command active see also description of LED "right

red/
gree
n

on Autonegotiation and/or waiting

for DHCP-/BootP-address assign­ment.

control IP addresses in the network
waiting for the device to be ready
for operation

to ERR"

V01.0| 2016/12

29

TBEN-Lx-8IOL

LED Color Status Meaning Remedy

IOLx Channel in IO-Link-mode

greenoff No IO-Link communication, diag-

nostics deactivated

flashing IO-Link communication active, 

valid process data

Red on No IO-Link communication and/or

module error, 
invalid process data

– connect an IO-Link device
– Parameterize the channel as DI if

necessary.

-

Possible causes:

– Sensor supply is below the admis-

sible range,

– IO-Link port is parameterized as

simple digital input,

– No device connected to the mas-

ters,

Red flashing IO-Link communication active and

module error, invalid process data

– No input data received from the

connected device (only valid for
devices with an 
input data length > 0),

– the connected device does not

respond on sending 
output data (only valid for
devices with an output data
length of > 0).

– connected device sends an error:

"process data invalid".

see also: 

Start-up problems - frequent
failure causes, page 111

Channel in DI-mode –

greenoff -

greenon Input signal active –

DXPx greenoff -

greenon In-/ output signal active

Red on Short circuit at output of the

right
to
ERR

white flashing Support for localizing a module if

respective channel

­the blink-/wink-command is acti­vated

30

Hans Turck GmbH & Co. KG | T [phone] | F [phone] | [e-mail] | www.turck.com

4.7.2 Diagnostic data

For the diagnostic messages we distinguish between V1/V2 overcurrent diagnostics, DXP-diagnos­tics, IO-Link-master and IO-Link-device diagnostics.
The „PDINV" diagnostic (process data invalid) can be sent from both devices, IO-Link master or IO­Link device.

 V1/V2 overcurrent diagnostics

Overcurrent diagnostics for the sensor-/ actuator supply VAUX1 and the Class B supply VAUX2

 DXP-diagnostics

Diagnostic messages of the digital channels of the module (DXP 1, 3, 5, 7).

 IO-Link master diagnostics

The IO-Link-master reports problems within the IO-Link communication.

 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.

4.7.3 Diagnostic telegram

channel Byte Bit 7 Bit 6 Bit 5 Bit 4 Bit 3 Bit 2 Bit 1 Bit 0

V1/V2 V1/V2 overcurrent diagnostics

0

1 VErrV2

DXP DXP-diagnostics

0ERR

1 --------

IO-Link

IO-Link
port 1

IO-Link
port 2

IO-Link
port 3

IO-Link
port 4

IO-Link
port 5

IO-Link
port 6

IO-Link
port 7

IO-Link
port 8

0 EVT1 EVT2 PDINV HWER DSER CFGER PPE -

1

2 + 3

4 + 5

6 + 7

8 + 9

10 +
11

12 +
13

14 +
15

VErrV1
C7K14

C7K15

DXP7

GENER OLV VHIGH VLOW ULVE LLVU OTMP PRMER

VErrV1
C6K12

VErrV2
C6K13

-

VErrV1
C5K10

VErrV2
C5K11

ERR

DXP 5

VErrV1

C4K8

VErrV2

C4K9

-

VErrV1C3

K6K7

ERR

DXP 3

VErrV1C2

K4K5

----

-

VErrV1C1

K2K3

ERR

DXP 1

Device diagnostics Master diagnostics

assignment similar to port 1

VErrV1C0

K0K1

-

V01.0| 2016/12

31

TBEN-Lx-8IOL

Bit Meaning Remedy

V1/V2 overcurrent diagnostics

VErrV1
CxChyChz

Overcurrent VAUX1 (pin 1) at Cx for channel y/channel z

0 No overcurrent

1 Overcurrent at the sensor supply at pin 1 of the respective 

port:

– C0: Channel 0 and 1
– C1: Channel 2 and 3
– C2: Channel 4 and 5
– C3: Channel 6 and 7

VErrV1
CxChy

Overcurrent VAUX1 (pin 1) at Cx, channel y

0 No overcurrent

1 Overcurrent at the sensor supply at pin 1 of the respective 

port:

– C4: Channel 8
– C5: Channel 10
– C6: Channel 12
– C7: Channel 14

VErrV2
CxChy

Overcurrent VAUX2 (pin 2) at Cx, channel y

0 No overcurrent

1 Overcurrent at the Class B supply at pin 2 of the respective 

port:

– C4: Channel 9
– C5: Channel 11
– C6: Channel 13
– C7: Channel 15

DXP-diagnostics

ERR DXP x Overcurrent output

0 No overcurrent

1 Overcurrent at the output (if the DXP channel is used as output)

IO-Link master diagnostics

PPE Port parameterization

The port parameters are inconsistent.
The device parameterization via GSD is active, but not working.
Possible causes:
The IO-Link-master did not receive GSDML-parameters for a connected device. The con­nected device was not parameterized by a PROFINET PLC via GSDML.
The port is in operation mode "IO-Link without validation" or "DI". These modes do not allow
parameterization via GSD.
The data storage mode is active, which means, the parameter is not set to "deactivated,
clear". A device parameterization via GSDML is not possible with activated data storage.
Vendor or Device ID are "0". The connected device can not be identified and is thus not
parameterizable.

32

Hans Turck GmbH & Co. KG | T [phone] | F [phone] | [e-mail] | www.turck.com

Bit Meaning Remedy

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
parameterization of the channel (see parame-

page 23).

ters,

Change the parameterization of the IO­Link port at the master.
Correct the vendor-ID, device-ID, etc.
The parameterization can be done by
teaching the master via IOL_CALL using
the port function Subindex 67: Teach

Mode

tion.

DSER data storage error

Possible causes:

– Data storage mismatch IO-Link device in accordance with IO-Link

V1.0 connected.
Deactivate the data storage. 
To do so, set parameter 

Data storage mode" to "deactivated,

"
clear", see

The data storage buffer contains data of
another device. 
Clear the data storage buffer of the master. 
To do so, set the parameter "Data stor-

age mode
page 24, and re-activate the data storage

if necessary.

– Overflow of the data storage buffer Clear the data storage buffer of the master.

To do so, set the parameter "Data stor-

age mode
page 24, and re-activate the data storage

if necessary.

– Parameter access for data storage not possi-

ble

Master/device diagnostics

PDINV Process input data invalid

The IO-Link master or the IO-Link device
report invalid process input data.

The connected device may be locked for
parameter changes or for data storage.
Check the status of the IO-Link index
"Device Access Locks" (index 0×C) of the
connected device and unlock the device.

The connected device is not in status
"operate", which means, it is not ready for
operation. 
Possible sources:
The connected device does not match the
configured one, additional diagnostic
message

Certain IO-Link devices send a "process
input data invalid"-diagnosis if the process
value cannot be measured.
Deactivate the sending of the "process
input data invalid"-diagnosis for the
respective port. To do so, change the
parameter "

invalid

see page 25.

or via a manual port parameteriza-

page 24.

" to "deactivated, clear", see

" to "deactivated, clear", see

Wrong or missing device.

Process input data

" to "no diagnostics generated",

V01.0| 2016/12

33

TBEN-Lx-8IOL

Bit Meaning Remedy

Device diagnostics

For the exact specification of the device diagnostics, please read the device documentation of the device
manufacturer.

HWER Hardware error

General hardware error or device malfunction.

EVT2 Out-of-specification events

An Out-of-Specification Event in accordance with the IO-Link specification occurred.

EVT1 Maintenance events

A Maintenance Event in accordance with the IO-Link specification occurred, maintenance
necessary.

PRMERR Parameterization error

The connected device reports a parameterization error (loss of parameters, no parameter
initialization, etc.)..

OTMP Overtemperature

Temperature diagnostic message at the connected device.

LLVU Lower limit value underrun

The process value lies under the parameterized measurement range or the chosen measure­ment range has been chosen too high.

ULVE Upper limit value exceeded

The process value exceeds the parameterized measurement range or the chosen measure­ment 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 is below the defined range.

OLV Overload

The connected device detected an overload.

GENER Common error

The device sends an error (device status 4, in accordance with IO-Link specification), which
is not clearly specified.
Read out the device Event Codes in order to be able to specify the error more precisely.

34

Hans Turck GmbH & Co. KG | T [phone] | F [phone] | [e-mail] | www.turck.com

4.7.4 Status and control word

Status word

EtherNet/IP™
Modbus

Byte 0 Byte 1

Byte 1 Byte 0

Name Value Description

COM 0 -

DIAG 0 -

FCE 0 -

V1 0 -

V2 0 -

PROFINET Bit 7 Bit 6 Bit 5 Bit 4 Bit 3 Bit 2 Bit 1 Bit 0

V2 - DIAG

-FCE- - -COMV1 -

1 Internal error, the device-internal communication is disturbed.

1 Diagnostics available at the device.

1 The Force Mode is activated, which means, the actual output values may no

match the ones defined and sent by the field bus.

1 System power supply too low (< 18 V DC).

1 V2 too low (< 18 V DC).

The status word is mapped into the module's process data.

 EtherNet/IP™

In EtherNet/IP™, the mapping can be disabled (seeGateway Class (VSC 100), GW Status Word,

page 69 and GW Control word, page 69).

 Modbus TCP

 see Register 0x100C: Module status, page 50

 PROFINET 

 see PROFINET-diagnostics - TBEN-Lx-8IOL, page 82

Control word

 The control is not in use.

ATTENTION!

Activate/deactivate the Status and Control Word in EtherNet/IP™

Changes in the process data mapping

 Observe that activating/deactivating the Status and Control Word causes changes in

the process data mapping.

V01.0| 2016/12

35

TBEN-Lx-8IOL

IO-Link-Master
(IOLM)

IO-Link-Device
(IOLD)

DS_UPLOAD_FLAG

4.8 IO-Link data storage

4.8.1 General

Data storage allows to change an IO-Link device when maintenance is required without any config­uration or parameterization.

The IO-Link master, as well as the IO-link device, store the device parameters. The data storage
mechanism serves for synchronizing these different data storage buffers.

In case of a device change, the master writes the stored device parameters to the new device. The
application can be re-started without any further intervention using a configuration tool or similar.

In the IO-Link master, the data storage mode can be set using the parameter "data storage mode"
(see Parameters, page 22).

data storage mode

00 = activated (page 37)

01 = overwrite (see page 39)

10 = read in (see page 39)

11 = deactivated, clear (see page 39)

General principle of the data storage mechanism

Para. IOLD = parameter data of the IO-Link device

A change of parameters in the device is indicated by the status of the DS_UPLOAD_FLAG bit:



DS_UPLOAD_FLAG:
0 = no changes in the device's parameter set
1 = changes in the device's parameter set (e. g. via DTM, at the device, etc.)

36

Hans Turck GmbH & Co. KG | T [phone] | F [phone] | [e-mail] | www.turck.com

4.8.2 Parameter "data storage mode" = activated

1

IO-Link-Master

IO-Link-Device

0

IO-Link-Master

IO-Link-Device

 The synchronization of the parameter sets is bidirectional.

 The actual data set (master or device) is valid:

The following applies:

–

The data set in the device is actual, if DS_UPLOAD_FLAG = 1

– The data set in the master is actual, if DS_UPLOAD_FLAG = 0

Parameterizing a device in the installation:

A device, which is already used in the installation, is for example parameterized via a DTM.

Prerequisites:
The IO-Link device is already connected to the master.


DS_UPLOAD_FLAG = 1 
 changes in the device's parameter see

Para. IOLD

device

Maintenance - exchange device in delivery status:

A defective device is replaced by a new device in delivery status.

Prerequisites:
The new IO-Link device has not been connected to the master before.

DS_UPLOAD_FLAG = 0

no changes in the device's parameter set



Para. IOLD

device

= parameter data of the IO-Link

= parameter data of the IO-Link

V01.0| 2016/12

37

TBEN-Lx-8IOL

1

IO-Link-Master

IO-Link-Device

Maintenance - exchange device with eventually modified parameter set:

A defective device is replaced by a new device with a parameter set that was already changed before (for
example via DTM).

Prerequisites:
The new IO-Link device has not been connected to the master before.



DS_UPLOAD_FLAG = 1

changes in the device's parameter see



Para. IOLD

device

= parameter data of the IO-Link

NOTE

If a device change is necessary when data storage is activated, the following has to be 
observed:
An IO-Link exchange device with unknown parameter data should be reset to factory
defaults before connecting it to the master.
This prevents unknown device parameter settings to be downloaded to the master when
establishing the connection.
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 docu­mentation.

38

Hans Turck GmbH & Co. KG | T [phone] | F [phone] | [e-mail] | www.turck.com

4.8.3 Parameter "data storage mode" = read in

1

IO-Link-Master

IO-Link-Device

1

IO-Link-Master

IO-Link-Device

IO-Link-Master

IO-Link-Device

 The data set in the device is always the reference data set.

 The synchronization of the parameter sets is unidirectional towards to the master.

 The status of the DS_UPLOAD_FLAG is ignored.

4.8.4 Parameter "data storage mode" = overwrite

 The data set in the master is always the reference data set.

 The synchronization of the parameter sets is unidirectional towards to the device.

 The status of the DS_UPLOAD_FLAG is ignored.

Para. IOLD = parameter data of the IO-Link
device

4.8.5 Parameter "data storage mode" = deactivated, clear

 The data set in the master is deleted.

 The synchronization of parameter sets is deactivated.

Para. IOLD = parameter data of the IO-Link
device

Para. IOLD = parameter data of the IO-Link
device

V01.0| 2016/12

39

TBEN-Lx-8IOL

4.9 IO-Link - functions for acyclic communication

The acyclic access to the data of IO-Link devices is realized via IO-Link CALLs.

Therefore it is necessary to distinguish between data of an IO-Link master or of an IO-Link device.

The addressing of the IO-Link CALL is realized via the so called Entity_Port- It defines which device
is addressed via the CALL:

Entity_Port 0 = IO-Link master module (IOLM - TBEN-Lx-8IOL)

Entitiy_Port 1 = IO-Link device at 1st IO-Link-port

...

Entitiy_Port 8 = IO-Link device at 8th IO-Link-port

4.9.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

Entity_
Port

0 64 w max. 72 byte This object serves for writing a defined config-

IO-Link
subindex

Read
Write

Length Description

Subindex 66: Set Default Parameterization

Entity_
Port

0 66 w 4 byte Writing this object sets the IO-Link master

Structure of the reset command:

Byte 3 Byte 2 Byte 1 Byte 0

0xEF 0xBE 0xAD 0xDE

IO-Link
subindex

Read
Write

Length Description

uration of the IO-Link ports into the master.

back to factory settings. Any parameter set­ting and configuration is overwritten. The data
storage buffer is deleted as well.

40

Hans Turck GmbH & Co. KG | T [phone] | F [phone] | [e-mail] | www.turck.com

Subindex 67: Teach Mode

Entity_
Port

0 67 w 1 byte The master reads all data (device-Id, ven-

IO-Link
subindex

Read
Write

Length Description

dor-ID, serial number, etc.) from the con­nected device and saves them. All all previ­ously saved device data are overwritten.

Structure of the teach command:

Byte 0

0x00 Teaching all 4 ports

0x01 Teaching port 1

0x02 Teaching port 2

0x03 Teaching port 3

0x04 Teaching port 4

0x05 - 0xFF reserved

V01.0| 2016/12

41

TBEN-Lx-8IOL

Subindex 68: Master Port Scan Configuration

Entity_
Port

0 68 r max. 120 byte This object serves for reading the 

IO-Link
subindex

Read
Write

Length Description

configuration of the IO-Link devices con­nected to the IO-Link master.

28 byte are returned per IO-Link port

Structure of the answer telegram:

IO-Link
Port

Port 1 Vendor_ID 2 byte UINT16 Vendor ID of the connected device

Port 2 Structure similar to port 1

Port 3

Port 4

Content Length Format Description

Device_ID 4 byte UINT32 Device-ID of the connected device

Function_ID 2 byte UINT16 reserved

Serial_Number 16 byte String 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 con-

nected device

Proc_Out_Length 1 byte UINT8 Process output data length of the con-

nected device

Cycle time UINT8 Cycle time of the connected device

42

Hans Turck GmbH & Co. KG | T [phone] | F [phone] | [e-mail] | www.turck.com

Subindex 69: Extended Port Diagnostics

Entity_
Port

0 69 r max. 8 byte This object serves for reading the 

IO-Link
subindex

Read
Write

Length Description

Extended Port Diagnostics.

Structure of the Extended Port Diagnostics:

Bit 7 Bit 6 Bit 5 Bit 4 Bit 3 Bit 2 Bit 1 Bit 0

Byte 0

Byte 1 - WD MD PDI_H - PDI_E NO_PD -

Byte 3

Byte 4

Diagnostic bit Meaning

NO_DS The parameterized port mode (see Parameters, page 22) does not support data

NO_SIO TCYC - - DS_F NO_DS - -

Device status according to IO-Link specification (see Device Status, page 44)

storage.
Remedy:

– Change the parameterization of the port.

DS_F Error in the data storage, synchronization not possible

Possible causes:

– Connected device does not support data storage.
– 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 mode (see parameter

22

).

Remedy:

Mode, page

– Select the IO-Link mode for this port.

NO_PD No process data available The connected device is not ready for operation.

Remedy:

– Checking the configuration

PDI_E The connected device reports invalid process data in accordance with IO-Link speci-

fication V1.0.

V01.0| 2016/12

43

TBEN-Lx-8IOL

Device Status

Diagnostic bit Meaning

PDI_H The connected device reports invalid process data in accordance with IO-Link speci-

fication V1.1.

MD Missing device: No IO-Link device detected

Remedy:

– Check the IO-Link cable.
– 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:

– Change the device.
– Adapt the master parameterization (see parameter Mode, page 22)

Value Meaning

0 Device works correctly

1 Maintenance Event

2 Out-of-Specification Event

3 Functional check

4 error

5-255 reserved

44

Hans Turck GmbH & Co. KG | T [phone] | F [phone] | [e-mail] | www.turck.com

4.10 IO-Link and Turck device DTMs

FDT enables a fieldbus and system independent engineering environment to be set up. Generic
DTMs allow any type of sensor and actuator to be integrated easily in the system.

4.10.1 Topology-Scan

The Topology Scan in PACTware also allows the read-in of an IO-Link configuration down to the IO­Link device.

IO-Link devices, known in PACTware, are added to the IO-Link ports of the master.
Therefore, either the respective sensor DTMs in PACTware or the sensor IODDs via IODD DTM Con­figurator have to be installed.



Fig. 4: Topology Scan in PACTware

V01.0| 2016/12

45

TBEN-Lx-8IOL

4.10.2 Special DTM parameters

The Turck DTMs offer, besides the normal parameters of the IO-Link master modules, special func­tion for configuring the master module.

46

Fig. 5: Special DTM-function within Online parameterization.

Automatic IO-Link detection

The data of the connected device/ the connected devices are read-in by the master. 

This function affects, depending on the parameter group in which it is activated, all ports or only one special
port. In the "Common"-group it is valid for the whole module, in the "Port configuration" group it is only valid
for the respective port.

Factory settings

The master is set back to its factory settings.

Hans Turck GmbH & Co. KG | T [phone] | F [phone] | [e-mail] | www.turck.com

5 TBEN-Lx-8IOL with Modbus TCP

5.1 General

5.1.1 Implemented Modbus functions

The modules TBEN-Lx-8IOLsupport the following Modbus TCP functions for accessing process data,
parameters, diagnostics and other services:

Function codes

No. Function

Description

1 Read Coils

Reading multiple output bits

2 Read Discrete Inputs

Reading multiple input bits

3

4 Read Input Registers

5 Write Single Coil

6

15 Write Multiple Coils

16 Write Multiple Registers

23

Read Holding Registers

Reading multiple output registers

Reading multiple input registers.

Writing a single output bit.

Write Single Register

Writing a single output register.

Writing multiple output bits.

Writing multiple output registers.

Read/Write Multiple Registers

Reading and writing of multiple registers

5.1.2 Modbus registers

V01.0| 2016/12

NOTE

For the register mapping of the different Modbus addressing methods see page 49.

47

TBEN-Lx-8IOL with Modbus TCP

Register assignment

Address (hex.) Access

ro = read only
rw = read/write

0x0000  0x01FF ro Process data of inputs

0x0800  0x09FF rw Process data of outputs

0x1000  0x100B ro Module identifier

0x100C ro Module status

0x1010 
0x1016

0x1017 ro Register mapping revision

0x1020 ro Watchdog, actual time [ms]

0x1120 rw Watchdog predefined time [ms] (default: 0)

0x1130 rw Modbus connection mode register, page 50

0x1131 rw Modbus connection timeout in sec. (default: 0 = never).

0x113C  0x113D rw Modbus parameter restore, page 51

0x113E  0x113F rw Modbus parameter save, page 51

0x1140 rw Deactivate protocol

0x1141 ro Active protocol

0x1150 rw LED behavior (PWR) at V2 undervoltage

0x2400 ro V1 [mV]: 0 at < 18 V

0x2401 ro V2 [mV]: 0 at < 18 V

0x8000  0x8400 ro Process data inputs, see 

0x9000  0x9400 rw Process data outputs, see 

0xA000  0xA400 ro Diagnostics, see Diagnostic data, page 31

0xB000  0xB400 rw Parameters

ro reserved

Description

see Register 0x100C: Module status, page 50

Register mapping revision (always 2, if not, mapping is incom­patible with this description)

see Error behavior (watchdog), page 53

page 50

(reset of parameters to default values)

(permanent storing of parameters)

Deactivates explicitly the selected Ethernet-protocol:
Bit 0 =Deactivate EtherNet/IP™
Bit 1 =Deactivate Modbus TCP
Bit 2 =Deactivate PROFINET
Bit 15 = Deactivate web server

Bit 0 = 1: EtherNet/IP™ active
Bit 1 = 1: Modbus TCP active
Bit 2 = 1: PROFINET active
Bit 15 = 1: web server active

Bit 0:
0 = green
1 = red

Process input data, page 19

Process output data, page 21

48

Hans Turck GmbH & Co. KG | T [phone] | F [phone] | [e-mail] | www.turck.com

The following table shows the register mapping for the different Modbus addressing methods:

Description Hex Decimal 5-digit Modicon

Inputs 0x0000



0x01FF

Outputs 0x0800



0x09FF

Module identifier 0x1000


0x100B

Module status 0x100C 4108 44109 404109

Watchdog, actual time 0x1020 4128 44129 404129

Watchdog, predefined time 0x1120 4384 44385 404385

Modbus connection mode register 0x1130 4400 44401 404401

Modbus connection timeout in sec. 0x1131 4401 44402 404402

Modbus parameter restore, 0x113C  

0x113D

Modbus parameter save, 0x113E 

0x113F

Deactivate protocol 0x1140 4416 44417 404417

Active protocol 0x1141 4417 44418 404418

V1 [mV]: 0x2400 9216 49217 409217

V2 [mV]: 0x2401 9217 49218 409218

Process data inputs 0x8000,

0x8001

Process data outputs 0x9000,

0x9001

Diagnostics 0xA000,

00A001

Parameters 0xB000,

0xB001

0

511

2048

2549

4096



4107

4412 
4413

4414 
4415

32768
32769

36864,
36865

40960,
40961

45056,
45057

40001

40512

42049

42560

44097

44108

44413  
44414

44415 
44416

- 432769

- 436865,

- 440961,

- 445057,

400001

400512

402049

402560

404097

404108

404413  
404414

404415  
404416

432770

436866

440962

445058

V01.0| 2016/12

49

TBEN-Lx-8IOL with Modbus TCP

Register 0x100C: Module status

This register contains the module's status word.

Byte 1 (MSB) Byte 0 (LSB)

Bit 15 Bit 14 Bit 13 Bit 12 Bit 11 Bit 10 Bit 9 Bit 8 Bit 7 Bit 6 Bit 5 Bit 4 Bit 3 Bit 2 Bit 1 Bit 0

-FCE----V1-V2------DIAG

 see also: 

Chapter 4.7.4, Status and control word, page 35

Register 0x1130: Modbus connection mode

This register defines the behavior of the Modbus connections:

Bit Name

– Description

15  2 reserved

1

0 MB_OnlyOneWritePermission

MB_ImmediateWritePermission

– 0: With the first write access, a write authorization for the respective Modbus-connection is

requested. If this request fails, an exception response with exception-code 01h is generated. If
the request is accepted, the write access 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 Modbus-connection thus receives the write authorization,
all following connections don’t (only if bit 0 = 1).

– 0: all Modbus-connections receive the write authorization
– 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.

Register 0x1131: Modbus Connection Timeout

This register defines after which time of inactivity a Modbus-connection is closed through a Discon­nect.

Behavior of the BUS LED

In case of a Connection Timeout the BUS LED's behavior is as follows:

Connection-Timeout BUS-LED

time-out green, blinking

50

Hans Turck GmbH & Co. KG | T [phone] | F [phone] | [e-mail] | www.turck.com

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.

For this purpose, write 0x6C6F to register 0x113C. 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.

The service resets the parameters without saving them. This can be achieved by using a following
"save" service.

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.

For this purpose, write 0x7361 to register 0x113E. To activate the saving of the registers, write
0x7665 ("save") within 30 seconds in register 0x113F.

Both registers can also be written with one single request using the function codes FC16 and FC23.

V01.0| 2016/12

51

TBEN-Lx-8IOL with Modbus TCP

5.2 Data width of the TBEN-Lx-8IOL in the Modbus-register area

Module Process input data Process output data Alignment

TBEN-Lx-8IOL 344 byte 260 byte word by word

5.3 Register mapping TBEN-Lx-8IOL

Register Bit15Bit14Bit 13Bit12Bit11Bit

MSB LSB

0x0000 
0x00xx

0x00xx
+ 1 Reg.

0x0800
 0x08xx

Diagnosis

0xA000 see Chapter 4, Diagnostic data, page 31

0xA001

0xA004

0xB000 - SRO7 - SRO5 - SRO3 - SRO1 ­0xB001

0xB002

0xB003

0xB004 …
0xB005

0xB006 Vendor ID
0xB007 +

0xB008
0xB009 -

0xB00A
… 0xB011

0xB012 …
0xB019

-

Cycle time GSD

-

Bit 9 Bit 8 Bit 7 Bit 6 Bit 5 Bit 4 Bit 3 Bit 2 Bit 1 Bit 0

10

Input data

Process input data

see Chapter 4, Process input data, page 19

Module status

see Register 0x100C: Module status, page 50

Output data

process output data

see Chapter 4, Process input data, page 19

DXP-channel diagnostics

IO-Link channel diagnostics

see Chapter 4, Diagnostic data, page 31…

Parameters

see Chapter 4, Parameters, page 22

IO-Link-Basic

EN

DO7

IO-Link port 1

Quick
Start-

Process out-

put data map-

ping

process out-

put data

-

Device ID

IO-Link port 2

8 registers of parameter data,

assignment similar to port 1

IO-Link port 3

8 registers of parameter data,

assignment similar to port 1

-

Up

EN

DO5

data storage

Process out-

input data

-

mode

put data
mapping

process

EN

DO3

Deactivate

diagnostics

deactivate

web server

-

Mode

Process

inpu

EN

DO1

t data

valid

Revi-

sion

-

52

Hans Turck GmbH & Co. KG | T [phone] | F [phone] | [e-mail] | www.turck.com

Register Bit15Bit14Bit 13Bit12Bit11Bit

10

0xB01A
… 0xB021

0xB022 …
0xB029

0xB02A
… 0xB031

0xB032 …
0xB039

0xB03A
… 0xB041

0xB042

0xB043

0xB044

0xB045

0xB046 …
0xB047

0xB048

0xB049

-

-

-

-

-

-

Bit 9 Bit 8 Bit 7 Bit 6 Bit 5 Bit 4 Bit 3 Bit 2 Bit 1 Bit 0

IO-Link port 4

8 registers of parameter data,

assignment similar to port 1

IO-Link port 5

8 registers of parameter data,

assignment similar to port 1

IO-Link port 6

8 registers of parameter data,

assignment similar to port 1

IO-Link port 7

8 registers of parameter data,

assignment similar to port 1

IO-Link port 8

8 registers of parameter data,

assignment similar to port 1

VAUX1

monitoring

VAUX1 Pin1 C1
(Ch2/3)

VAUX1 Pin1 C3
(Ch6/7)

VAUX1 Pin1 C5
(Ch10)

VAUX1 Pin1 C7
(Ch14)

-

-

-

-

-

VAUX1 Pin1 C0
(Ch0/1)

VAUX1 Pin1 C2
(Ch4/5)

VAUX1 Pin1 C4
(Ch8)

VAUX1 Pin1 C6
(Ch12)

VAUX2

monitoring

VAUX2 Pin2 C5
(Ch11)

VAUX2 Pin2 C7
(Ch15)

-

-

VAUX2 Pin2 C4
(Ch9)

VAUX2 Pin2 C6
(Ch13)

5.4 Error behavior (watchdog)

5.4.1 Behavior of outputs

In case of a failure of the Modbus communication, the outputs’ behavior is as follows, depending on
the defined time for the Watchdog (register 0x1120,

 Watchdog = 0 ms (default)

 outputs hold the momentary value in case of an error

 Watchdog > 0 ms

 outputs switch to

NOTE

Setting the outputs to predefined substitute values is not possible in Modbus TCP. Even­tually parameterized substitute values will not be used.

V01.0| 2016/12

page 48):

0 after the watchdog time has expired (setting in register 0x1120).

53

TBEN-Lx-8IOL with Modbus TCP

5.4.2 Behavior of the BUS LED

If the Watchdog has tripped, the BUS LED behaves as follows:

Watchdog BUS-LED

tripped constantly red

5.5 Parameters and diagnostic messages of the I/O channels

NOTE

Please find explanations regarding parameters and diagnostic messages in the section

Register mapping TBEN-Lx-8IOL, page 52.

54

Hans Turck GmbH & Co. KG | T [phone] | F [phone] | [e-mail] | www.turck.com

6 TBEN-Lx-8IOL with EtherNet/IP™

6.1 EDS-file

The actual EDS-files for TBEN-L can be downloaded from the Turck home page www.turck.com.

EDS-file ZIP-file

TBEN-Lx-8IOL_Rx.x.eds TBEN-L45_ETHERNETIP.zip

6.2 QC - QuickConnect

QuickConnect is not supported by TBEN-Lx-8IOL.

NOTE

Further information about QuickConnect and the configuration options can be found in
the user manual for the TBEN-S product family
„TBEN-L/TBDP-L Compact I/O modules for Ethernet/PROFIBUS-DP“

6.3 Diagnostic messages via the process data

The diagnostic messages of the IO-Link-channels are directly mapped into the process data (see

Parameter data mapping, TBEN-Lx-8IOL, page 61.)

Additionally, the device's status word contains the module diagnostics:

D301323 - 

Status word

Bit 15Bit 14Bit 13Bit 12Bit 11Bit 10Bit 9 Bit 8 Bit 7 Bit 6 Bit 5 Bit 4 Bit 3 Bit 2 Bit 1 Bit 0

 see also 

Chapter 4.7.4, Status and control word, page 35

or 

Chapter 6.5.2, Gateway Class (VSC 100), page 68,
69

Byte 1 (MSB) Byte 0 (LSB)

-FCE----V1-V2------DIAG

Object Instance 2, gateway Instance, page

V01.0| 2016/12

55

TBEN-Lx-8IOL with EtherNet/IP™

6.4 EtherNet/IP™-standard classes

The modules TBEN-L support the following EtherNet/IP™ Standard Classes in accordance with the
CIP specification.

Class Code Object name

01 (0x01) Identity Object (0x01)

04 (0x04) Assembly Object (0x04)

06 (0x06) Connection Manager Object (0x06)

245 (0xF5) TCP/IP Interface Object (0xF5)

246 (0xF6) Ethernet Link Object (0xF6)

6.4.1 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 TBEN-L.

Class attributes

Attr. No. Attribute name Get/

Set

1 (0x01) REVISION G UINT 1

2 (0x02) MAX OBJECT INSTANCE G UINT 1

6 (0x06) MAX CLASS ATTRIBUTE G UINT 7

7 (0x07) MAX INSTANCE ATTRIBUTE G UINT 7

Instance attributes

Attr. No. Attribute name Get

1 (0x01) VENDOR G UINT Contains the vendor ID.

2 (0x02) PRODUCT TYPE G UINT Shows the general product type.

3 (0x03) PRODUCT CODE G UINT Identifier for a specific product of a device

4 (0x04) REVISION

Major Minor

Type Description

/
Set

G STRUCT

OF:
USINT
USINT

TURCK = 48

Communications Adapter

= 0x0C

12

dec

type.
default: 27247

Revision of the item the Identity Object is rep­resenting.
0x01
0x06

dec =

Type Value

6A6F

56

Hans Turck GmbH & Co. KG | T [phone] | F [phone] | [e-mail] | www.turck.com

5 (0x05) DEVICE STATUS G WORD See Device Status

6 (0x06) SERIAL NUMBER G UDINT Contains the ident-no. of the product (3 last

bytes of the MAC-ID).

7 (0x07) PRODUCT NAME

G STRUCT

OF:

e. g.:
TBEN-Lx-16DXP

LENGTH
NAME

Device Status

Bit Name Definition

0 to 1 reserved default = 0

2 Configured TRUE = 1

3 reserved default = 0

4 to 7 Extended Device 

Status

8 to 15 reserved default = 0

Common Services

Service code Class Instance Service name

01 (0x01) yes yes Get_Attribute_All

05 (0x05) no yes Reset

14 (0x0E) yes yes Get_Attribute_Single

16 (0x10) no no Set_Attribute_Single

USINT
STRING
[13]

 The application of the device has been configured (
default-settings).

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

Returns a predefined list of the object‘s attributes.

Starts the reset service for the device.

Returns the contents of a specified attribute.

Modifies a single attribute.

6.4.2 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.

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 TBEN-L.

Class attributes

Attr. No. Attribute name Get/

1 (0x01) REVISION G UINT 2

2 (0x02) MAX OBJECT INSTANCE G UINT 104

V01.0| 2016/12

Type Value

Set

57

TBEN-Lx-8IOL with EtherNet/IP™

Instance attributes

Attr. No. Attribute name Get

3 (0x03) DATA S ARRAY OF

4 (0x04) SIZE G UINT Number of bytes in attr. 3

Common Services

Service code Class Instance Service name

01 (0x01) yes yes Get_Attribute_All

14 (0x0E) no yes Get_Attribute_Single

Configuration Assembly (Instance 106)

TBEN-L modules support Configuration Assembly. It enables an EDS-based configuration/parame­terization of the devices in the PLC software (if supported by the PLC).

The Configuration Assembly contains:

10 bytes module configuration data (EtherNet/IP™-specific)

+ 110 bytes (parameter data)

Parameter data mapping, TBEN-Lx-8IOL

Type Description

/
Set

BYTE

256 or variable

Byte Bit 7 Bit 6 Bit 5 Bit 4 Bit 3 Bit 2 Bit 1 Bit 0

Module configuration data, see

0 to 9

Parameter data TBEN-Lx-8IOL, see Parameters, page 22

10

Module configuration data, page 59

LED behavior

Reserved

(PWR) at V2

Undervoltage

Eth 2

Port Setup

DXP 1 - SRO

Eth 1

Port Setup

(not supported)

Manual output reset after overcurrent

11

DXP 3 - SRO

Manual output reset after overcurrent

12

DXP 5 - SRO

Manual output reset after overcurrent

13

DXP 7 - SRO

Manual output reset after overcurrent

14

15

16

17

IO-Link port parameters, see Parameters, page 22

DXP 1 - EN DO Activate output

DXP 3 - EN DO Activate output

DXP 5 - EN DO Activate output

DXP 7 - EN DO Activate output

IO-Link port 1

18

19

20

Mode

Data storage mode

Cycle time

QC

58

Hans Turck GmbH & Co. KG | T [phone] | F [phone] | [e-mail] | www.turck.com

Byte Bit 7 Bit 6 Bit 5 Bit 4 Bit 3 Bit 2 Bit 1 Bit 0

21

22

23

24

25

26

27

28 - 29

30 - 33

34 - 49 IO-Link port 2

Activate Quick Start-Up

Device parameterization via GSD

Process input data invalid

Deactivate diagnostics

Process input data mapping

Process output data mapping

Revision

Vendor ID

Device ID

(assignment acc. to bytes 18 - 33 for port 1)

50 -65 IO-Link port 3

(assignment acc. to bytes 18 - 33 for port 1)

66 - 81 IO-Link port 4

(assignment acc. to bytes 18 - 33 for port 1)

82 - 97 IO-Link port 5

(assignment acc. to bytes 18 - 33 for port 1)

98 - 113 IO-Link port 6

(assignment acc. to bytes 18 - 33 for port 1)

114 - 129 IO-Link port 7

(assignment acc. to bytes 18 - 33 for port 1)

Module configuration data

Parameter name

= default

A

LED behavior (PWR) at V2
undervoltage

(Ethx Port Setup)

Value Meaning

0 = green PWR-LED is blinking green at V2 undervoltage.

1 = red PWR-LED constant red at V2 undervoltage.

0 = Autonegotiation A

1 = 100BT/FD Defined setting of the communication param-

eters for the Ethernet port to:

– 100BaseT
– Full duplex

V01.0| 2016/12

59

TBEN-Lx-8IOL with EtherNet/IP™

Process data instances

Instance 101

Contains the module’s input data (static length 256 bytes).

2 Bytes status information (see page 35)

+ process data

Instance 102

Contains the module’s

output data (static length 256 bytes).

2 bytes control word (mapped, but not defined)

+ process data

Instance 103 and Instance 104

In- and output assembly instances

with variable assembly sizes. The assembly size is pre-calculated

to support the stations I/O-configuration, enabled diagnostics, etc.

The effective size of the Assembly Instance can be determined using the Assembly Object (instance
0×67, attribute 0x04):

–Input data:

Input Assembly Instance: 103
0 - 208 bytes
default: 208 bytes

– Output data:

Output Assembly Instance: 104 
0 - 132 bytes
default: 132 bytes

60

Hans Turck GmbH & Co. KG | T [phone] | F [phone] | [e-mail] | www.turck.com

Parameter data mapping, TBEN-Lx-8IOL

 Including the status word which can be deactivated via Gateway Class (VSC 100), GW Status

Word, page 69 and GW Control word, page 69.

ATTENTION!

Activate/deactivate the Status and Control Word in EtherNet/IP™

Changes in the process data mapping

 Observe that activating/deactivating the Status and Control Word causes changes in

the process data mapping.

 Connection Manager Object (0x06), page 61.

IN Bit 15 Bit 14 Bit 13 Bit 12 Bit 11 Bit 10 Bit 9 Bit 8 Bit 7 Bit 6 Bit 5 Bit 4 Bit 3 Bit 2 Bit 1 Bit 0

Status

V2------Diag-FCE----V1-

Input data

(see Chapter 4 Process input data, page 19)

OUT

Output data

(see Chapter 4, Process output data, page 21)

see Status and control word

6.4.3 Connection Manager Object (0x06)

This object is used for connection and connectionless communications, including establishing con­nections across multiple subnets.

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 TBEN-L.

Common Services

Service code Class Instance Service name

84 (0x54) no yes FWD_OPEN_CMD

78 (0x4E) no yes FWD_CLOSE_CMD 

82 (0x52) no yes UNCONNECTED_SEND_CMD

(Opens a connection)

(Closes a connection)

V01.0| 2016/12

61

TBEN-Lx-8IOL with EtherNet/IP™

6.4.4 TCP/IP Interface Object (0xF5)

The following description of the Ethernet Link Object is taken from the CIP specification, Vol. 2, Rev.

1.1 by ODVA & ControlNet International Ltd. and adapted to TBEN-L.

Class attributes

Attr. No. Attribute name Get/

Set

1 (0x01) REVISION G UINT 1

2 (0x02) MAX OBJECT INSTANCE G UINT 1

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. Attribute name Get/

1 (0x01) STATUS G DWORD Interface status (see page 63, Interface Status)

2 (0x02) CONFIGURATION

CAPABILITY

3 (0x03) CONFIGURATION

CONTROL

4 (0x04) PHYSICAL LINK

OBJECT

Path size

Path:

5 (0x05) INTERFACE CON-

FIGURATION

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 configured

NAME SERVER 2 UDINT 0 = no secondary server address configured

DOMAIN NAME G UDINT 0 = no Domain Name configured

6 (0x06) HOST NAME G STRING 0 = no Host Name configured (see page 64)

12 (0x0C) Quick Connect G/S BOOL 0 = deactivate

Type Description

Set

G DWORD Interface Capability Flag (see page 63, Configura-

tion Capability)

G/S DWORD Interface Control Flag (see page 63, Configura-

tion Control)

G STRUCT

UINT Number of 16 bit words: 0x02

Padded
EPATH

G Structure

of:

0x20, 0xF6, 0x24, 0x01

TCP/IP Network Interface Configuration (see page

63)

1 = activate

Type Value

62

Common Services

Service code Class Instance Service name

01 (0x01) yes yes Get_Attribute_All

02 (0x02) no no Set_Attribute_All

14 (0x0E) yes yes Get_Attribute_Single

16 (0x10) no yes Set_Attribute_Single

Hans Turck GmbH & Co. KG | T [phone] | F [phone] | [e-mail] | www.turck.com

 Interface Status

The Status attribute indicates the status of the TCP/IP network interface. 
Refer to the state diagram: Fig. 6: TCP/IP object state diagram (acc. to CIP Spec., Vol.2, Rev. 1.1)
for a description of object states as they relate to the Status attribute.

Bit(s) Name Definition

0-3 Interface Configuration

Status

4 to 31 reserved

 Configuration Capability

Indicates the status of the Interface Configuration attribute:
0 = The Interface Configuration attribute has not been configured
1 = The Interface Configuration attribute contains valid configura­tion.
2 to 15: reserved

The Configuration Capability indicates the device’s support for optional network configuration
capability.

Bit(s) Name Definition Value

0 BOOTP Client The device is capable of obtaining its net-

work configuration via BOOTP.

1 DNS Client The device is capable of resolving host

names by querying a DNS server.

2 DHCP Client The device is capable of obtaining its net-

work configuration via DHCP.

1

0

1

 Configuration Control

The Configuration Control attribute is used to control network configuration options.

Bit(s) Name Definition

0-3 Startup- 

Configuration

4 DNS Enable Always 0

5-31 reserved Set to 0

 Interface Configuration

Determines how the device shall obtain its initial configuration.
0 = The device shall use the interface configuration values previ­ously stored (for example, in non-volatile memory or via hardware
switches, etc).
1 to 3: reserved

This attribute contains the configuration parameters required to operate as a TCP/IP node. To mod­ify the Interface Configuration attribute, get the Interface Configuration attribute first, change the
desired parameters, then set the attribute. 
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 values
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 compo­nents 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 configu­ration obtained via BOOTP/DHCP. 

V01.0| 2016/12

63

TBEN-Lx-8IOL with EtherNet/IP™

Non-existent

Obtaining initial

configuration

Waiting

for

configuration

Applying

configuration

TCP/IP network

interface configured

Status = 0×00000001

Powerup/ Reset

BOOTP/DHCP
response received

BOOTP/DHCP
disabled and
stored config.
valid

Set_Attributes
request received

Change interface
configuration

Status =
0×00000000

Configuration applied

BOOTP OR
DHCP enabled

BOOTP/DHCP
disabled and
stored config. valid

Status =
0×00000000

 Host Name

This attribute contains the device’s host name. 
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. 
The mechanism allows the DHCP client to transmit its host name to the DHCP server. The DHCP
server then updates the DNS records on behalf of the client.

Fig. 6: TCP/IP object state diagram (acc. to CIP Spec., Vol.2, Rev. 1.1)

64

Hans Turck GmbH & Co. KG | T [phone] | F [phone] | [e-mail] | www.turck.com

6.4.5 Ethernet Link Object (0xF6)

The following description of the Ethernet Link Object is taken from the CIP specification, Vol. 2, Rev.

1.1 by ODVA & ControlNet International Ltd. and adapted to TBEN-L.

Class attributes

Attr. No. Attribute name Get/

Set

1 (0x01) REVISION G UINT 1

2 (0x02) MAX OBJECT INSTANCE G UINT 1

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. Attribute name Get

1 (0x01) INTERFACE SPEED G UDINT Speed in Mbit/s 

2 (0x02) INTERFACE FLAGS G DWORD see Interface flags, page 65

3 (0x03) PHYSICAL

ADDRESS

6 (0x06) INTERFACE 

CONTROL

7 (0x07) INTERFACE TYPE

10 (0x0A) INTERFACE LABEL

Type Description

/
Set

(e. g. 10, 100, 1000, etc.)

G ARRAY OF

USINT

2 WORD Allows port-wise changes of the Ethernet-set-

Contains the interface’s MAC address 
(Turck: 00:07:46:××:××:××)

tings

Type Value

Interface flags

Bits Name Definition Default value

0 Link Status Indicates whether or not the Ethernet 802.3

communications interface is connected to an
active network.
0 = inactive link
1 = active link

1 Half/full duplex 0 = half duplex 

1 = full duplex
If th e Lin k Stat us fl ag is 0, Dup lex b it can not b e
defined.

Depends on appli­cation

Depends on appli­cation

V01.0| 2016/12

65

TBEN-Lx-8IOL with EtherNet/IP™

Bits Name Definition Default value

2 to 4 Negotiation Status Indicates the status of the automatic 

5 Manual Setting 

Requires Reset

6 Local Hardware

Fault

Duplex detection (autonegotiation)
0 = autonegotiation running
1 = autonegotiation and speed detection
failed 
Using default values for speed and duplex
(10Mbps/half duplex).
2 = autonegotiation failed but detected speed
(default: half duplex).
3 = successfully negotiated speed and duplex.
4 = autonegotiation not attempted. Forced
speed and duplex.

0 = interface can activate changes to link
parameters (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

0 = interface detects no local hardware fault
1 = a local hardware fault detected

Depends on appli­cation

0

0

Common Services

Service code Class Instance Service name

01 (0x01) yes yes Get_Attribute_All

14 (0x0E) yes yes Get_Attribute_Single

76 (0x4C) no yes Enetlink_Get_and_Clear

66

Hans Turck GmbH & Co. KG | T [phone] | F [phone] | [e-mail] | www.turck.com

6.5 VSC-Vendor Specific Classes

In addition to supporting the above named CIP Standard Classes, the TBEN-L modules support the
vendor specific classes described in the following.

Class Code

dec.
(hex.)

100 (0x64) Gateway Class, page 68 Contains data and settings concerning the

126 (0x1A) Miscellaneous Parameters Class, page 71 Describes the EtherNet/IP™-Port properties

135 (0x87) DXP Class, page 72 Describes the DXP-channel properties

137 (0x89) IO-Link-Port Class, page 72 Describes the IO-Link--channel properties

Name Description

6.5.1 Class Instance der VSCs

NOTE

The class instance attributes are the same for each Vendor Specific Class.

The class-specific Object Instances and the corresponding attributes are explained in the
paragraphs for the different VSC.

The general VSC - class instance attributes are defined as follows.

Attr. No.

dec.
(hex.)

100
(0x64)

101
(0x65)

102
(0x66)

103
(0x67)

Attribute name Get

field bus-specific part of the TBEN-L devices.

Type Description

/
Set

Class revision G UINT Contains the revision number of the class

(maj. rel. *1000 + min. rel.).

Max. instance G USINT Contains the number of the highest instance

of an object created on this level in the class
hierarchy.

# of instances G USINT Contains the number of Object Instances cre-

ated in this class.

Max. class attribute G USINT Contains the number of the last class attribute

to be implemented.

V01.0| 2016/12

67

TBEN-Lx-8IOL with EtherNet/IP™

6.5.2 Gateway Class (VSC 100)

This class contains all information which concerning the whole module not the different channels.

Class instance

NOTE

Please refer to section Class Instance der VSCs, page 67 for the description of the class
instance for the VSC.

Object instance 1, boot instance

Attr. No.

dec.
(hex.)

100
(0x64)

101
(0x65)

102
(0x66)

103
(0x67)

104
(0x68)

Attribute name Get

Max object attri­bute

Hardware revision G STRUCT Contains the hardware revision number of the

Firmware revision G STRUCT Contains the revision number of the boot firm-

Service tool ident
number

Hardware
Info

Type Description

/
Set

G USINT Contains the number of the last object attri-

bute to be implemented.

module (USINT Maj./USINT Min.)

ware (Maj./Min.).

G UDINT Contains the BOOT ID number that serves as

an identification number for the DTM-soft­ware.

G STRUCT Contains station hardware information (UINT):

– count (number of the following entries)
– CLOCK FREQUENCY (kHz)
– MAIN FLASH (in kB)
– MAIN FLASH SPEED (ns)
– SECOND FLASH (kB)
– RAM (kB),
– RAM SPEED (ns),
– RAM data WIDTH (bit),
– SERIAL EEPRPOM (kbit)
– RTC SUPPORT (in #)
– AUTO SERVICE BSL SUPPORT (BOOL)
– HDW SYSTEM

68

Hans Turck GmbH & Co. KG | T [phone] | F [phone] | [e-mail] | www.turck.com

Object Instance 2, gateway Instance

Attr. No.

dec.
(hex.)

109
(0x6D)

115 
(0x73)

138 
(0x8A)

139 
(0x8B)

140 
(0x8C)

Attribute name Get

/
Set

Status word 
(Status register 2)

ON IO 
CONNECTION 
TIMEOUT

GW Status 
Word

GW Control word Get

Disable Protocols Get

G STRUCT The Status Word contains general station sta-

G/S ENUM

Get
/set

/set

/set

Type Description

tus information:

Module

– Bit 15: reserved
– Bit 14: Force Mode active, „Force Mode Active

Error“ (FCE) 
The Force Mode is activated, no access to the
module possible because there is already a
connection to the DTM .

– Bit 13: reserved
– Bit 12: reserved

Internal bus

– Bit 11: reserved
– Bit 10: reserved

Voltage errors

– Bit 09: "V1 too low" (< 18 VDC).
– Bit 08: reserved
– Bit 07: "V2 too low" (< 14 VDC).
– Bit 06: reserved
– Bit 05: reserved
– Bit 04: reserved

Warnings

– Bit 03: reserved
– Bit 02: reserved
– Bit 01: reserved
– Bit 00: Module diagnostics pending (DIAG), at

least one channel sends active diagnostics.

Reaction to the I/O connection exceeding the

USINT

DWORD Activates or deactivates the mapping of the

DWORD Activates or deactivates the mapping of the

UINT Deactivation of the used Ethernet protocol.

time limit.
SWITCH IO FAULTED (0):
The channels are switched to substitute value.
SWITCH IO OFF (1):
The outputs are switched to 0.
SWITCH IO HOLD (2):
No further changes to the I/O-data. The out­puts are held.

status word into the module's input data.

control word into the module's output data.

Bit assignment of protocols:
Bit 0 = EtherNet/IP™ (can not be disabled via
EtherNet/IP™-interface)
Bit 1 = Modbus TCP
Bit 2 = PROFINET
Bit 11 - bit14 = reserved
Bit 15 = web server

V01.0| 2016/12

69

TBEN-Lx-8IOL with EtherNet/IP™

Object instance 4, COS/CYCLIC instance

Attr. No.

dec.
(hex.)

104 (0x68) COS data 

Attribute name Get/

mapping

Type Description

Set

G/S ENUM

USINT

The actual data are loaded to the non-vol­atile memory of the station.
Changes become valid after a start-up.
0 = standard: Data of COS message
 input data.
1 = process input data (only the process
data input image is transferred to scanner)
2 to 7: reserved

70

Hans Turck GmbH & Co. KG | T [phone] | F [phone] | [e-mail] | www.turck.com

6.5.3 Miscellaneous Parameters Class (VSC 126)

Ethernet-Port ETH 1 = instance 1

Ethernet-Port ETH 2 = instance 2

Attr. No.

dec.
(hex.)

109
(0x6D)

112
(0x70)

Attribute
name

Ethernet
port 
Parameters

I/O 
controller 
Software
revision

Get/
Set

G/S DWORD 0 = autonegotiate, AutoMDIX

G DWORD The number of instances of this parameter depends on

Type Description

1 = 10BaseT, half duplex, linear topology (AutoMDIX dis-

abled)

2 = 10BaseT, full duplex, linear topology (AutoMDIX dis-

abled)

3 = 100BaseT, half duplex, linear topology (AutoMDIX

disabled)

4 = 100BaseT, full duplex, linear topology (AutoMDIX dis-

abled)

the number of I/O controllers.

V01.0| 2016/12

71

TBEN-Lx-8IOL with EtherNet/IP™

6.5.4 IO-Link Port Class 137 (89h)

This class contains eight object instance, one for each IO-Link-port.

Attr. no.

dec.
(hex.)

1 (0x01) IOL - 

2 (0x02) IOL - 

3 (0x03) IOL -

Attribute name Get/

Operation mode

data storage mode

Cycle time

Type Description

Set

G/S USINT 0 = IO-Link without validation

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 to 7: reserved
8 = DI

G/S USINT 0 = activated

1 = overwrite
2 = read in
3 = deactivated, clear

G/S USINT 0 = automatic

16 = 1,6 ms
32 = 3,2 ms
48 = 4,8 ms
64 = 6,4 ms
68 = 8,0 ms
72 = 9,6 ms
76 = 11,2 ms
80 = 12,8 ms
84 = 14,4 ms
88 = 16,0 ms
92 = 17,6 ms
96 = 19,2 ms
100 = 20,8 ms
104 = 22,4 ms
108 = 24,0 ms
112 = 25,6 ms
116 = 27,2 ms
120 = 28,8 ms
124 = 30,4 ms
128 = 32,0 ms
129 = 33,6 ms
130 = 36,8 ms
132 = 40,0 ms
134 = 41,6 ms
135 = 43,2 ms
136 = 44,8 ms
137 = 46,4 ms
138 = 48,0 ms
139 = 49,6 ms
140 = 51,2 ms
141 = 52,8 ms
142 = 54,4 ms

143 = 56,0 ms
144 = 57,6 ms
145 = 59,2 ms
146 = 60,8 ms
147 = 62,4 ms
148 = 64,0 ms
149 = 65,6 ms
150 = 67,2 ms
151 = 68,8 ms
152 = 70,4 ms
153 = 72,0 ms
154 = 73,6 ms
155 = 75,2 ms
156 = 76,8 ms
157 = 78,4 ms
158 = 80,0 ms
159 = 81,6 ms
160 = 83,2 ms
161 = 84,8 ms
162 = 86,4 ms
163 = 88,0 ms
164 = 89,6 ms
165 = 91,2 ms
166 = 92,8 ms
167 = 94,4 ms
168 = 96,0 ms
169 = 97,6 ms
170 = 99,2 ms
171 = 100,8 ms
172 = 102,4 ms
173 = 104,0 ms
174 = 105,6 ms
175 = 107,2 ms

72

Hans Turck GmbH & Co. KG | T [phone] | F [phone] | [e-mail] | www.turck.com

Attr. no.

dec.

Attribute name Get/

Set

Type Description

(hex.)

3 (0x03) IOL - Cycle time

(continuation)

G/S USINT 176 = 108,8 ms

177 = 110,4 ms
178 = 112,0 ms
179 = 113,6 ms
180 = 115,2 ms
181 = 116,8 ms
182 = 118,4 ms
189 = 129,6 ms
190 = 131,2 ms
191 = 132,8 ms

4 (0x04) IOL - Revision G/S USINT 0 = automatic

1 = V 1.0

5 (0x05) IOL - Quick Start-Up 

activate

6 (0x06) IOL - Device parameteriza-

tion via GSD

G/S USINT 0 = no

1 = yes

G/S USINT 0 = no

1 = yes

7 (0x07) IOL - Process data invalid G/S USINT 0 = diagnostic generated

1 = no diagnostic generated

8 (0x08) IOL - Deactivate load volt-

age diagnostics

G/S USINT 0 = no

1 = notifications
2 = notifications and warnings
3 = yes

9 (0x09) IOL - Process output data

mapping

G/S USINT 0 = direct

1 = swap 16 bit
2 = swap 32 bit
3 = swap all

10 (0x0A) IOL - Process output data

mapping

G/S USINT 0 = direct

1 = swap 16 bit
2 = swap 32 bit
3 = swap all

11 (0x0B) IOL - Vendor ID G/S INT 0 = inactive

1 = active

12 (0x0C) IOL - Device ID G/S DINT 0 = inactive

1 = active

13 (0x0D) IOL - Wrong or missing

device

GUSINT0 = inactive

1 = active

V01.0| 2016/12

14 (0x0E) IOL - Data storage error G USINT 0 = inactive

1 = active

15 (0x0F) IOL - Process data invalid G USINT 0 = inactive

1 = active

16 (0x10) IOL - Hardware error G USINT 0 = inactive

1 = active

17 (0x11) IOL - Maintenance events G USINT 0 = inactive

1 = active

18 (0x12) IOL - Out-of-specification

events

GUSINT0 = inactive

1 = active

73

TBEN-Lx-8IOL with EtherNet/IP™

Attr. no.

dec.
(hex.)

19 (0x13) IOL - Parameterization

20 (0x14) IOL - Overtemperature G USINT 0 = inactive

21 (0x15) IOL - Lower limit value

22 (0x16) IOL - Upper limit value

23 (0x17) IOL - Undervoltage G USINT 0 = inactive

24 (0x18) IOL - Overvoltage G USINT 0 = inactive

25 (0x19) IOL - Overload G USINT 0 = inactive

26 (0x1A) IOL - Common error G USINT 0 = inactive

27 (0x1B) IOL - Port parameterization

28 (0x1C) IOL - Input data word 0 G USINT

Attribute name Get/

Set

GUSINT0 = inactive

error

GUSINT0 = inactive

underrun

GUSINT0 = inactive

exceeded

GUSINT0 = inactive

error

Type Description

1 = active

1 = active

1 = active

1 = active

1 = active

1 = active

1 = active

1 = active

1 = active

... ... G USINT

43 (0x2B) IOL - Input data word 15 G USINT

44 (0x2C) IOL - Output data word 0 G USINT

... ... G USINT

59 (0x3B) IOL - Output data word 15 G USINT

74

Hans Turck GmbH & Co. KG | T [phone] | F [phone] | [e-mail] | www.turck.com

6.5.5 IO-Link Events Class 138 (90h)

Attr. no.

dec.
(hex.)

1 (0x01) IOL-Event 1 – port G USINT Port no. of the port which sends the 1st IO-

to 

16 (0x10) IOL-Event 16 – port G USINT Port no. of the port which sends the 16th

17 (0x11) IOL-Event 1 – qualifier G USINT Qualifier of the 1st IO-Link Event

to 

32 (0x20) IOL-Event 16 – qualifier G USINT Qualifier of the 16th IO-Link Event

33 (0x21) IOL-Event 1– Event

to 

48 (0x30) IOL-Event 16– Event

Attribute name Get/

Set

G USINT Event code of the 1st IO-Link Event

Code

G USINT Event code of the 16th IO-Link Event

Code

Type Description

Link Event.

IO-Link Event.

V01.0| 2016/12

75

TBEN-Lx-8IOL with EtherNet/IP™

6.5.6 VAUX Control Class 161 (A1h)

Attr. no.

dec.
(hex.)

Activate VAUX1 monitoring

1 (0x01) VAUX Control - VAUX1 Pin1 C0 (Ch0/1) G/S USINT 0 = 24 VDC

2 (0x02) VAUX Control - VAUX1 Pin1 C1 (Ch2/3) G/S USINT 0 = 24 VDC

3 (0x03) VAUX Control - VAUX1 Pin1 C2 (Ch4/5) G/S USINT 0 = 24 VDC

4 (0x04) VAUX Control - VAUX1 Pin1 C3 (Ch6/7) G/S USINT 0 = 24 VDC

5 (0x05) VAUX Control - VAUX1 Pin1 C4 (Ch8) G/S USINT 0 = 24 VDC

7 (0x07) VAUX Control - VAUX1 Pin1 C5 (Ch10) G/S USINT 0 = 24 VDC

9 (0x09) VAUX Control - VAUX1 Pin1 C6 (Ch12) G/S USINT 0 = 24 VDC

11 (0x0B) VAUX Control - VAUX1 Pin1 C7 (Ch14) G/S USINT 0 = 24 VDC

Activate VAUX2 monitoring

6 (0x06) VAUX Control - VAUX2 Pin2 C4 (Ch9) G/S USINT 0 = 24 VDC

8 (0x08) VAUX Control - VAUX2 Pin2 C5 (Ch11) G/S USINT 0 = 24 VDC

10 (0x0A) VAUX Control - VAUX2 Pin2 C6 (Ch13) G/S USINT 0 = 24 VDC

12 (0x0C) VAUX Control - VAUX2 Pin2 C7 (Ch15) G/S USINT 0 = 24 VDC

VAUX1 diagnostics

13 (0×0D) VAUX Control - VAUX1 Pin1 C0 (Ch0/1) G USINT 0 = off

14 (0×0E) VAUX Control - VAUX1 Pin1 C1 (Ch2/3) G USINT 0 = off

15 (0×0F) VAUX Control - VAUX1 Pin1 C2 (Ch4/5) G USINT 0 = off

Attribute name Get/

Set

Type Description

1 = switchable
2 = off

1 = switchable
2 = off

1 = switchable
2 = off

1 = switchable
2 = off

1 = switchable
2 = off

1 = switchable
2 = off

1 = switchable
2 = off

1 = switchable
2 = off

1 = switchable
2 = off

1 = switchable
2 = off

1 = switchable
2 = off

1 = switchable
2 = off

1 = Overcurrent

1 = Overcurrent

1 = Overcurrent

76

Hans Turck GmbH & Co. KG | T [phone] | F [phone] | [e-mail] | www.turck.com

Attr. no.

dec.

Attribute name Get/

Set

Type Description

(hex.)

16 (0×10) VAUX Control - VAUX1 Pin1 C3 (Ch6/7) G USINT 0 = off

1 = Overcurrent

17 (0×11) VAUX Control - VAUX1 Pin1 C4 (Ch8) G USINT 0 = off

1 = Overcurrent

19 (0×13) VAUX Control - VAUX1 Pin1 C5 (Ch10) G USINT 0 = off

1 = Overcurrent

21 (0×15) VAUX Control - VAUX1 Pin1 C6 (Ch12) G USINT 0 = off

1 = Overcurrent

23 (0×17) VAUX Control - VAUX1 Pin1 C7 (Ch15) G USINT 0 = off

1 = Overcurrent

VAUX2 diagnostics

18 (0×12) VAUX Control - VAUX2 Pin2 C4 (Ch9) G USINT 0 = off

1 = Overcurrent

20 (0×14) VAUX Control - VAUX2 Pin1 C5 (Ch11) G USINT 0 = off

1 = Overcurrent

22 (0×16) VAUX Control - VAUX2 Pin2 C6 (Ch13) G USINT 0 = off

1 = Overcurrent

24 (0×18) VAUX Control - VAUX2 Pin2 C7 (Ch15) G USINT 0 = off

1 = Overcurrent

V01.0| 2016/12

77

TBEN-Lx-8IOL with EtherNet/IP™

6.5.7 Basic Class 153 (99h)

This class provides one single instance for all DXP/DI-channels.

Attr. no.

dec.
(hex.)

DXP-channel (pin 2)

1 (0x01) Basic DXP 1 - Manual output reset after overcurrent G/S USINT 0 = no

2 (0x02) Basic DXP 3 - Manual output reset after overcurrent G/S USINT 0 = no

3 (0x03) Basic DXP 5 - Manual output reset after overcurrent G/S USINT 0 = no

4 (0x04) Basic DXP 7 - Manual output reset after overcurrent G/S USINT 0 = no

5 (0x05) Basic - DXP 1 - Activate output G/S USINT 0 = no

6 (0x06) Basic - DXP 3 - Activate output G/S USINT 0 = no

7 (0x07) Basic - DXP 5 - Activate output G/S USINT 0 = no

8 (0x08) Basic - DXP 7 - Activate output G/S USINT 0 = no

9 (0x09) Basic - DXP 1 - Overcurrent output G USINT 0 = inactive

10 (0x0A) Basic - DXP 3 - Overcurrent output G USINT 0 = inactive

11 (0x0B) Basic - DXP 5 - Overcurrent output G USINT 0 = inactive

12 (0x0C) Basic - DXP 7 - Overcurrent output G USINT 0 = inactive

13 (0×0D) Basic - IOL 0 - DI input Get USINT 0

14 (0×0E) Basic - IOL 2 - DI input Get USINT 0

15 (0×0F) Basic - IOL 4 - DI input Get USINT 0

16 (0×10) Basic - IOL 6 - DI input Get USINT 0

17 (0×11) Basic - IOL 8 - DI input Get USINT 0

18 (0×12) Basic - IOL 10 - DI input Get USINT 0

19 (0×13) Basic - IOL 12 - DI input Get USINT 0

20 (0×14) Basic - IOL 14 - DI input Get USINT 0

Attribute name Get

/
Set

Type Description

1 = yes

1 = yes

1 = yes

1 = yes

1 = yes

1 = yes

1 = yes

1 = yes

1 = active

1 = active

1 = active

1 = active

1

1

1

1

1

1

1

1

78

Hans Turck GmbH & Co. KG | T [phone] | F [phone] | [e-mail] | www.turck.com

Attr. no.

dec.
(hex.)

Attribute name Get

/
Set

Type Description

21 (0x15) Basic - IOL 0 - Input value valid (Data Valid Signal) G USINT 0 = no

1 = yes

22 (0x16) Basic - IOL 2 - Input value valid (Data Valid Signal) G USINT 0 = no

1 = yes

23 (0x17) Basic - IOL 4 - Input value valid (Data Valid Signal) G USINT 0 = no

1 = yes

24 (0x18) Basic - IOL 6 - Input value valid (Data Valid Signal) G USINT 0 = no

1 = yes

25 (0x19) Basic - IOL 8 - Input value valid (Data Valid Signal) G USINT 0 = no

1 = yes

26 (0x1A) Basic - IOL 10 - Input value valid (Data Valid Signal) G USINT 0 = no

1 = yes

27 (0x1B) Basic - IOL 12 - Input value valid (Data Valid Signal) G USINT 0 = no

1 = yes

28 (0x1C) Basic - IOL 14 - Input value valid (Data Valid Signal) G USINT 0 = no

1 = yes

29 (0×1D) Basic - DXP 1 - Input value G USINT 0

1

30 (0×1E) Basic - DXP 3 - Input value G USINT 0

1

31 (0×1F) Basic - DXP 5 - Input value G USINT 0

1

32 (0×20) Basic - DXP 7 - Input value G USINT 0

1

33 (0×21) Basic - DXP 1 - DXP Output value G USINT 0

1

34 (0×22) Basic - DXP 3 - DXP Output value G USINT 0

1

35 (0×23) Basic - DXP 5 - DXP Output value G USINT 0

1

36 (0×24) Basic - DXP 7 - DXP Output value G USINT 0

1

V01.0| 2016/12

79

TBEN-Lx-8IOL with EtherNet/IP™

80

Hans Turck GmbH & Co. KG | T [phone] | F [phone] | [e-mail] | www.turck.com

7 TBEN-Lx-8IOL with PROFINET

A

B

A

C

7.1 GSDML-file

The actual GSDML-file for TBEN-L can be downloaded from the Turck home page www.turck.com.

GSDML-file Zip-file

GSDML-Vx.x-TURCK-TBEN_Lx_8IOL-YYYYMMDD-xxxxxx.xml TBEN-L45_PROFINET.zip

7.2 Configuration, TBEN-Lx-8IOL

The TBEN-Lx-8IOL provide eight parameterizable I/O-Link-channels and four universal I/O-channels
(DXP).

In addition to that, four virtual slots are provided via GSDML in PROFINET. 
Those slots are used to map the different diagnostic and status (IO-Link and VAUX-diagnostics (see

Diagnostic telegram, page 31), IO-Link-Events, module status (see Status and control word,
page 35) data into the IO-Link master's process image. 

Further information can be found in Chapter 9, Hardware configuration, page 96.

Fig. 7: Example of a module configuration (in STEP7)

A Basic slot for e. g. DXP-channels and Data Valid Signal
B IO-Link ports (slots 2- 9) for the configuration with specific IO-Link devices or for generic configuration
C One slot each for diagnostics and status (slots 10 - 13)

V01.0| 2016/12

81

TBEN-Lx-8IOL with PROFINET

7.3 FSU - Fast Start-Up

FSU - Fast Start-Up is not supported by TBEN-Lx-8IOL.

NOTE

Further information about FSU - Fast Start-Up and the configuration options can be found
in the user manual for the TBEN-L product family D301324
„TBEN-L/TBDP-L Compact I/O modules for Ethernet/PROFIBUS-DP“

7.4 PROFINET-diagnostics - TBEN-Lx-8IOL

Module diagnostics (slot 0 A) PROFINET-diagnostics

Diagnosis Connector Error code Channel

Undervoltage

V1 0x0002 0

V2 0x0002 1

- 

I/O-diagnostics (slot 1 A) PROFINET-diagnostics

DXP-diagnostics Channel Error code Channel

Overcurrent output DXP 1 C0 0x0001 1

DXP 3 C1 0x0001 3

DXP 5 C2 0x0001 5

DXP 7 C3 0x0001 7

VAUX1/VAUX2-diagnostics Error code Channel

Overcurrent VAUX1 (pin 1) at C0, channel 0/1 C0 0x01D0 0

Overcurrent VAUX1 (pin 1) at C1, channel 2/3 C1 0x01D1 0

Overcurrent VAUX1 (pin 1) at C2, channel 4/5 C2 0x01D2 0

Overcurrent VAUX1 (pin 1) at C3, channel 6/7 C3 0x01D3 0

Overcurrent VAUX1 (pin 1) at C4, channel 8 C4 0x01E8 0

Overcurrent VAUX1 (pin 1) at C5, channel 10 C5 0x01EA 0

Overcurrent VAUX1 (pin 1) at C6, channel 12 C6 0x01EC 0

Overcurrent VAUX1 (pin 1) at C7, channel 14 C7 0x01EE 0

Overcurrent VAUX2 (pin 2) at C4, channel 9 C4 0x01F9 0

82

Overcurrent VAUX2 (pin 2) at C5, channel 11 C5 0x01FB 0

Overcurrent VAUX2 (pin 2) at C6, channel 13 C6 0x01FD 0

Overcurrent VAUX2 (pin 2) at C7, channel 15 C7 0x01FF 0

Hans Turck GmbH & Co. KG | T [phone] | F [phone] | [e-mail] | www.turck.com

IO-Link-diagnostics PROFINET-diagnostics

Port 1 (slot 2 A) Error code Channel

Undervoltage (VLOW) C0 0x0002 0

Overvoltage (VHIGH) 0x0003

Overload (OVL) 0x0004

Overtemperature (OTMP) 0x0005

Wrong or missing device (CFGERR) 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) 0x0010

Parameterization error (PRMER)

Hardware error (HWER) 0x0015

Port 2 (slot 3 A)

similar to port 1 C1 2

Port 3 (slot 4 A)

similar to port 1 C2 4

Port 4 (slot 5 A)

similar to port 1 C3 6

Port 5 (slot 6 A)

similar to port 1 C4 8

Port 6 (slot 7 A)

similar to port 1 C5 10

Port 7 (slot 8 A)

similar to port 1 C6 12

Port 8 (slot 9 A)

similar to port 1 C7 14

A Slot in configuration toll (e.g. TIA Portal, Siemens HW Config)

V01.0| 2016/12

83

TBEN-Lx-8IOL with PROFINET

7.5 Parameters

Two types of parameters have to be distinguished for the TBEN-L devices, the PROFINET parameters
of a station and the specific parameters of the I/O-channels.

7.5.1 General module parameters

Parameter name

= default

A

Output behavior at
communication loss

Deactivate all diagnostics 
deactivate web server

Deactivate load voltage
diagnostics
Deactivate diagnostics

LED behavior (PWR) at V2
undervoltage

Deactivate I/O-ASSISTANT
Force Mode
deactivate web server

Deactivate EtherNet/IP™ 0 = no A The single fieldbus protocols can be deacti-

Deactivate Modbus TCP  0 = no A

Deactivate WEB server  0 = no A

Value Meaning

00 = set to 0 A The station switches the outputs to "0". No

error information is transmitted.

10 = keep current value 

0 = no A Diagnostic messages and alarms are gener-

1 = yes Diagnostic messages and alarms are gener-

0 = no A Monitoring of voltage V2 is activated.

1 = yes An undervoltage at V2 is not monitored.

0 = green PWR-LED is blinking green at V2 undervoltage.

1 = red PWR-LED is red green at V2 undervoltage.

0 = no A

1 = yes

1 = yes

1 = yes

1 = yes

The station maintains the actual output data.

ated.

ated.

vated.

7.5.2 Parameters for I/O channels

see Parameters, page 22

84

Hans Turck GmbH & Co. KG | T [phone] | F [phone] | [e-mail] | www.turck.com

7.6 Description of user data for acyclic services

The acyclic data exchange is done via Record Data CRs (CR Communication Relation).

Via these Record Data CRs the reading and writing of the following services is realized:

 Writing of AR data

 Writing of configuration data

 Reading and writing of device data

 Reading of diagnostic data

 Reading of I/O data

 Reading of Identification Data Objects (I&M functions)

7.6.1 Description of the acyclic device user data

Module Application Instance

Index Name Data type r/w Comment

1
(0×01)

2
(0×02)

3
(0×03)

4
(0×04)

5
(0×05)

6
(0×06)

7
(0×07)

8 (0×0)
to 
23 (0×17)

24 (0×18) Module diagnostics WORD r Diagnostic data of the module (slot 0).

25 (0×19)
to 
31 (0×1F)

32
(0x20)

33
(0x21)

34
(0x22)

35
(0x23)

36 to 45039 reserved

Module parameters WORD r/w Parameter data of the module (slot 0)

Module designation STRING r Designation assigned to the module.

Module revision STRING r Firmware revision of the module

Vendor ID WORD r Ident no. for Turck

Module name STRING r The device name assigned to the mod-

Module type STRING r Module type

Device-ID WORD r Ident no. of the module

reserved

reserved

Input list Array of

BYTE

Module output list Array of

BYTE

Diag. list Array of

BYTE

Parameter list Array of

BYTE

ule

r List of all input channels in the module

r List of all output channels in the mod-

ule

r List of all I/O-channel diagnostics

r List of all I/O-channel parameters

V01.0| 2016/12

85

TBEN-Lx-8IOL with PROFINET

Index Name Data type r/w Comment

45040
(0xAFF0)

45041
(0xAFF1)

45042
(0xAFF2)

45043
(0xAFF3)

45044
(0xAFF4)

45045
(0xAFF5) to
45055
(0xAFFF)

0x7000 Module parameters WORD r/w Activate active field bus protocol

I&M0-functions r Identification & Maintaining services

I&M1-functions STRING

I&M2-functions STRING

I&M3-functions STRING

I&M4-functions STRING

I&M5 to I&M15-functions not supported

r/w I&M tag Function and location

[54]

r/w I&M tag Function and location

[16]

[54]

[54]

7.6.2 Description of the acyclic I/O-channel user data

Index
(dec.)

1 Module parameters specific r/w Parameters of the module

2 Module type ENUM

3 Module version UINT8 r Firmware version of the I/O-channels

4 Module ID DWORD r Ident number of the I/Os

5 to 9 reserved

10 Slave controller version UINT8

11 to 18 reserved

19 Input data specific r Input data of the respective

20 to 22 reserved

23 Output data specific r/w Output data of the respective I/O channel

... reserved

247 CAP 1 Record r/w Client access point for class 1 masters

248 CAP 2 Record r/w

249 CAP 3 Record rw

250 CAP 4 Record r/w

251 CAP 5 Record r/w

252 CAP 6 Record r/w

253 CAP 7 Record r/w

254 CAP 8 Record r/w

255 CAP 9 Record r/w Client access point for class 2 masters

Name Data type r/w Comment

UINT8

array [8]

r Contains the module type

r Version no. of the slave

controller

I/O channel

86

Hans Turck GmbH & Co. KG | T [phone] | F [phone] | [e-mail] | www.turck.com

7.6.3 IM99 (IOL_M)

Name Size Data type Default setting

IOL_LINK_VERSION 1 byte UINT8 17

IO_LINK_PROFILE_VERSION 1 byte UINT8 0

IO_LINK_FEATURE_SUPPORT 4 bytes UINT32 0

NUMBER_OF_PORTS 1 byte UINT8 4

REF_PORT_CONFIG 1 byte UINT8 0

REF_IO_MAPPING 1 byte UINT8 0

REF_IOL_M 1 byte UINT8 0

NUMBER_OF_CAP 1 byte UINT8 5

INDEX_CAP1 1 byte UINT8 247

INDEX_CAP2 1 byte UINT8 248

INDEX_CAP3 1 byte UINT8 249

INDEX_CAP4 1 byte UINT8 250

INDEX_CAP5 1 byte UINT8 251

INDEX_CAP6 1 byte UINT8 252

INDEX_CAP7 1 byte UINT8 253

INDEX_CAP8 1 byte UINT8 254

INDEX_CAP9 1 byte UINT8 255

V01.0| 2016/12

87

TBEN-Lx-8IOL with PROFINET

88

Hans Turck GmbH & Co. KG | T [phone] | F [phone] | [e-mail] | www.turck.com

8 The IO-Link function block IOL_CALL

IOL_CALL

BOOL

DWORD

INT

BOOL

INT
INT

INT

INT

ANY

REQ

ID
INDEX_CAP

RD_WR
ENTITY_PORT

FI_INDEX
IOL_INDEX

LEN
RECORD_IOL_DATA

INT

IOL_SUBINDEX

BOOL
BOOL

BOOL
DWORD

BOOL

DWORD

DONE_VALID

BUSY

ERROR

STATUS

IOL_STATUS

LEN

8.1 General

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".

NOTE

Depending on the PLC manufacturer, the IO-Link CALL function block can differ from the
specification (for example in the representation or the use of variables).

8.2 IOL_CALL in accordance with IO-Link specification

The following figure shows the function block as it is defined in the specification:

V01.0| 2016/12

Fig. 8: IOL_CALL in accordance with IO-Link specification

89

The IO-Link function block IOL_CALL

8.2.1 Input variables

The following description of the function block variables is partially taken from the IO-Link specifi­cation.

Name

IO-Link Spec. Data Type Meaning

REQ BOOL A rising edge triggers the send command.

ID DWORD Address of the IO-Link master module

INDEX_CAP INT Function block instance:

RD_WR BOOL 0 = read 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 written or read.

IOL_SUBINDEX INT Definition of a possible sub index.

LEN INT Length of the data to be read/written.

RECORD_IOL_DATA Source/destination for the data to be read/written.

Step 7 Classic

– Start address of the input data of the IO-Link master mod-

ule.

TIA Portal

Depending on the used CPU:

– older Siemens CPUs (e.g. CPU 315):

Start address of the input data of the IO-Link master mod­ule.

– recent Siemens CPUs (e.g. CPU 1511):

HW identifier of the device's "Basic" slot , see also

Beispielzugriffe mit IO_LINK_DEVICE, page 101

247 bis 254, 255 (s. page 86)

1 = write access

This information is not necessary for the Siemens IOL_CALL
(Integration des IO-Link-Masters in TIA Portal, page 95).

90

Hans Turck GmbH & Co. KG | T [phone] | F [phone] | [e-mail] | www.turck.com

8.2.2 Output variables

The following description of the function block variables is partially taken from the IO-Link specifi­cation.

Name

IO-Link Spec. Data Type Meaning

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 executing the read or write access.

STATUS DWORD Communication error status

IOL_STATUS DWORD IO-Link error messages (in accordance with "IO-Link Integra-

LEN INT Length of the data which were read.

Status of the acyclic communication. 
 see STATUS - communication error status, page 92

tion Part 1- Technical Specification for PROFIBUS and PROF­INET" and "IO-Link Interface and System"), which concern the
communication between IO-Link master and connected
devices.
 see IOL_STATUS, page 93

V01.0| 2016/12

91

The IO-Link function block IOL_CALL

8.2.3 STATUS - 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

identifier (not always

applicable)

Status Code Name Meaning

0×FF000000 TIMEOUT Internal error in the communication with the module

0×00FFFF00 INVALID_HANDLE

0×00FFFE00 HANDLE_OUT_OF_BUFFERS

0×00FFFD00 HANDLE_DESTINA-

TION_UNAVAILABLE

0×00FFFC00 HANDLE_UNKNOWN

0×00FFFB00 HANDLE_METHOD_INVALID

0×xx80A0xx MASTER_READ_ERROR Error reading

0×xx80A1xx MASTER_WRITE_ERROR Error writing

0×xx80A2xx MASTER_MODULE_

FAILURE

0×xx80A6xx MASTER_NO_DATA No data received

0×xx80A7xx MASTER_BUSY IO-Link-Master busy

0×xx80A9xx MASTER_FEATURE_NOT_

SUPPORTED

0×xx80AAxx MASTER_RESOURCE_

UNAVAILABLE

0×xx80B0xx ACCESS_INVALID_INDEX Index invalid, wrong INDEX_CAP used

0×xx80B1xx ACCESS_WRITE_

LENGTH_ERROR

0×xx80B2xx ACCESS_INVALID_

DESTINATION

0×xx80B03xx ACCESS_TYPE_CONFLICT IOL_CALL invalid

0×xx80B5xx ACCESS_STATE_CONFLICT Error in IOL_CALL sequence

0×xx80B6xx ACCESS_DENIED IOL-Link master module refuses the access

0×xx80C2xx RESOURCE_BUSY The IO-Link master module is busy or is waiting for an

0×xx80C3xx RESOURCE_

UNAVAILABLE

0×xx8901xx INPUT_LEN_TOO_SHORT The index to be read co ntains more data than defined

Specifies the error as

an error of acyclic com-

0×80

munication.

Error code  see

below

Status Code

Failure of the IO-Link-Master, bus failure possible

Function not supported by IO-Link-Master

IO-Link-Master not available

Length of data to be written can not be handled from
the module, possibly wrong module accessed

Wrong slot accessed

answer of the connected IO-Link device

in the input variable "LEN"

Vendor specific identi-

fier (not always appli-

cable)

92

Hans Turck GmbH & Co. KG | T [phone] | F [phone] | [e-mail] | www.turck.com

8.2.4 IOL_STATUS

The IOL_STATUS consists of 2 byte Error Code (IOL_M Error_Codes, according to "IO-Link Integration
Part 1- Technical Specification for PROFIBUS and PROFINET") and 2 byte Error Type (according to "IO­Link Interface and System").

IOL M Error Codes

Byte 3 Byte 2 Byte 1 Byte 0

IOL_M Error_Codes Error Types

 see IOL M Error Codes

according to "IO-Link Integration Part 1- Tech-

nical Specification for PROFIBUS and PROF-

INET"

 see IOL Error Types

according to "IO-Link Interface and System"

Error code Name 

0×0000 No error no error

0×7000 IOL_CALL conflict Unexpected write-request, read request expected

0×7001 Wrong IOL_CALL Decoding error

0×7002 Port blocked The accessed port is occupied by another task.

... reserved -

0×8000 Timeout

0×8001 Wrong index Error: IL index < 32767 or > 65535 selected

0×8002 Wrong port address Port address not available

0×8003 Wrong port function Port function not available

... reserved -

IOL Error Types

Error code Name 

0×1000 COM_ERR communication loss

0×1100 I_SERVICE_TIMEOUT Timeout in communication, device does not respond

0×5600 M_ISDU_CHECKSUM Master reports checksum error, access to device not

0×5700 M_ISDU_ILLEGAL Device can not respond to master request

0×8000 APP_DEV Application error in the device

0×8011 IDX_NOTAVAIL Index not available

0×8012 SUBIDX_NOTAVAIL Sub index not available

0×8020 SERV_NOTAVAIL Service temporarily not available

0×8021 SERV_NOTAVAIL_LOCCTRL Service temporarily not available, device is busy (e. g.

Meaning

acc. to spec.

Timeout, IOL master or IOL device port busy

Meaning

acc. to spec.

Possible sources:
Possible cause: the addressed port is parameterized as
DI and is not in IO-Link mode.

in time

possible

teaching or parameterization of the device at the
device active)

V01.0| 2016/12

93

The IO-Link function block IOL_CALL

Error code Name 

acc. to spec.

0×8022 SERV_NOTAVAIL_DEVCTRL Service temporarily not available, device is busy (e. g.

0×8023 IDX_NOT_WRITEABLE Access denied, index not writable

0×8030 PAR_VALOUTOFRNG Parameter value out of range

0×8031 PAR_VALGTLIM Parameter value above the upper limit

0×8032 PAR_VALLTLIM Parameter value below the lower limit

0×8033 VAL_LENOVRRUN

0×8034 VAL_LENUNDRUN

0×8035 FUNC_NOTAVAIL Function not available in the device

0×8036 FUNC_UNAVAILTEMP Function temporarily not available in the device

0×8040 PARA_SETINVALID Invalid parameter: Parameters not consistent with

0×8041 PARA_SETINCONSIST Inconsistent parameters

0×8082 APP_DEVNOTRDY Application not ready, device is busy

0×8100 UNSPECIFIC Vendor specific, according to device documentation

0×8101 to
0×80FF

VENDOR_SPECIFIC

Meaning

teaching or parameterization of the device via DTM/
PLC etc. active)

Length of data to be written does not match the
length defined for this parameter

other parameters in the device

94

Hans Turck GmbH & Co. KG | T [phone] | F [phone] | [e-mail] | www.turck.com

9 Integration of the IO-Link master in TIA Portal

9.1 Example project

9.1.1 Used hardware

 Siemens S7, CPU 1511-1 PN

 TBEN-Lx-8IOL with:

Port 1 Turck temperature sensor, TS-530-LI2UPN8X-..., IO-Link V1.0

Port 2 DI

Port 3 Turck linear position sensor, Li100P0-Q25LM0-..., IO-Link V1.0

Port 4 DI

Port 5 DI

Port 6 Turck IO-Link hub: TBIL-M1-16DXP, IO-Link V1.1

Port 7 Turck ultra sonic sensor, RU130U-M18E-..., IO-Link V1.1

Port 8 Turck inclinometer, B2N360-Q42-...,

9.1.2 Used software

 Totally Integrated Automation Portal, V13 SP1, Update 9

V01.0| 2016/12

95

Integration of the IO-Link master in TIA Portal

9.2 Hardware configuration

9.2.1 Configuration of the IO-Link master

 Install the GSDML file for the IO-Link master and add it to the PROFINET-IO-System (100).

 The TBEN-Lx-8IOL appears as a modular slave with twelve empty virtual slots. The "Basic" slot is

pre-configured.

Fig. 9: TBEN-Lx-8IOL with virtual slots

Virtual slots in TIA

The function of these slots is either defined via GSDML or can only be used for a specific purpose.

Slot Module/name Meaning

0 turck-tben-lx-8iol

X1

X1 P1

X1 P2

1 Basic Parameter/ Diagnostics for the DXP-channels of the

2 - 9 variable These slots are used for configuring the 

10 Diagnostics Optional mapping of the diagnostics (IO-Link and



(default name)

PN-IO Parameterization of PROFINET functions (MRP, etc.)

Port 1 Parameterization of the Ethernet port properties

Port 2

Main module, parameterization of functions (deacti­vation of protocols etc.) which concern the whole
device, see Allgemeine Modulparameter, page 84

(topology, connection options, etc.).

device (DXP 1, 3, 5 and 7) and Data Valid Signal from
the IO-Link ports.

eight IO-Link ports.

DXP-diagnostics) into the master's process image.
(see page 19)

96

Hans Turck GmbH & Co. KG | T [phone] | F [phone] | [e-mail] | www.turck.com

Slot Module/name Meaning

11 IO-Link Events Optional mapping of the diagnostics (IO-Link and

DXP-diagnostics) into the master's process image.
(see page 19)

12 VAUX Control Optional mapping of the VAUX diagnositcs into the

master's process image.
(see page 19)

13 Module status Optional mapping of the diagnostics (IO-Link and

DXP-diagnostics) into the master's process image.
(see page 19)

Configuration of the virtual slots 2 - 9 (IO-Link-ports) in the example project

See also Example project, page 95

IO-Link
Port

(Hardware)

PORT 1

at C0

PORT 2

at C1

PORT 3

at C2

PORT 4

at C3

PORT 5

at C4

PORT 6

at C5

PORT 7

at C6

PORT 8

at C7

virtual 
Slot

2 2 byte IN Turck temperature sensor, 

not used 1 bit IN - DI

3 2 byte IN Turck linear position sensor, 

not used 1 bit IN - DI

not used 1 bit IN - DI

72 byte IN

8 1 bit IN Turck ultrasonic sensor, 

9 4 byte IN Turck inclinometer, 

process data
length

2 byte OUT

Sensor Entry in GSDML

TS-530-LI2UPN8X-...

Li100P0-Q25LM0-...

Turck I/O-hub, 
TBIL-M1-16DXP

RU400U-M18E-...

B2N360-Q42-...

Port configuration 
generic:
IN 1 WORD

Port configuration
specific:
Li100P0-QU25L

Port configuration
specific:
TBIL-M1-16DXP

Port configuration
specific:
RU40U-M18E-LiU2PN...(DI)
The IO-Link port is config­ured as digital input only.

Port configuration
specific:
B2N360-Q42-E2LiUPN8X2-...

V01.0| 2016/12

97

Integration of the IO-Link master in TIA Portal

A

B

Fig. 10: Configuration of the virtual slots 2 - 9 in the example

A generic port configuration
B specific port configuration with Turck sensor entry from GSDML

98

Hans Turck GmbH & Co. KG | T [phone] | F [phone] | [e-mail] | www.turck.com