turck TBEN-S2-2COM-4DXP Instructions For Use Manual

Your Global Automation Partner

TBEN-S2-2COM-4DXP

Compact I/O Module for
Serial Data Transmission

Instructions for Use

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

Table of Contents

1 About these Instructions 1

1.1 Target Groups 1

1.2 Explanation of symbols used 1

1.3 Additional Documents 1

1.4 Feedback about these instructions 2

2 Notes on the Product 3

2.1 Product Identification 3

2.2 Scope of Delivery 3

2.3 Legal Requirements 3

2.4 Manufacturer and Service 3

3 For Your Safety 5

3.1 Intended Use 5

3.2 General Safety Instructions 5

4 Product Description 7

4.1 Device Overview 7

4.2 Display Elements 7

4.3 Properties and Features 8

4.4 Functional Principle 8

4.5 Functions and Operating Modes 9

4.5.1 Multi protocol functionality 9

4.5.2 Serial RS232 or RS485 Data Communication 9

4.5.3 Modbus RTU Data Communication 10

4.6 Configurable Digital Channels 10

4.7 Technical Accessories 10

5Mounting 11

2018/03

5.1 Mounting Module Composites 11

5.2 Mounting on Mounting Plate 12

5.3 Mounting on a DIN rail (TS 35) 12

1

5.4 Grounding the Device 13

5.4.1 Grounding and Shielding Concept 13

5.4.2 Ground the Device (FE) 14

6Connecting 15

6.1 Connecting the Modules to the Ethernet 15

6.1.1 Ethernet Connection for QC/FSU Applications 15

6.2 Connecting Power Supply 16

6.2.1 Supply Concept 17

6.3 Connecting Serial Devices 17

6.3.1 Activating/Deactivating of RS485 Termination and Biasing 18

6.4 Connecting Digital Sensors and Actuators 19

7 Commissioning 21

7.1 Setting the IP address 21

7.2 Commissioning the Device in PROFINET 23

7.2.1 GSDML file 23

7.2.2 FSU - Fast Start-Up (prioritized startup) 23

7.2.3 PROFINET IO Device Model 24

7.2.4 TBEN-S2-2COM-4DXP – Slots and Sub slots (Overview) 24

7.2.5 PROFINET diagnostics 40

7.2.6 Description of the User Data for Acyclic Services 41

7.3 Connecting the device to a Siemens PLC in PROFINET 43

7.3.1 Used Hardware 43

7.3.2 Used Software 43

7.3.3 Prerequisites 43

7.3.4 Installing the GSDML-file 44

7.3.5 Configuring the Device 45

7.3.6 Connecting the device to the PLC 46

7.3.7 Assigning PROFINET device name 47

7.3.8 Setting the IP address in TIA Portal 48

7.3.9 Going online with the PLC 49

7.3.10 Setting Module Parameters 50

7.4 Commissioning the Device in EtherNet/IP™ 51

7.4.1 EDS-file 51

7.4.2 QuickConnect (QC) 51

7.4.3 Diagnostic messages via process data 53

7.4.4 EtherNet/IP™-standard classes 54

7.4.5 Assembly Object (0x04) 56

7.4.6 Connection Manager Object (0x06) 61

7.4.7 TCP/IP Interface Object (0xF5) 62

7.4.8 Ethernet Link Object (0xF6) 66

7.4.9 VSC-Vendor Specific Classes 68

7.4.10 Extended DXP Functions Class (VSC 164) 80

2

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

7.5 Connecting the device to an EtherNet/IP™ PLC 81

7.5.1 Used Hardware 81

7.5.2 Used Software 81

7.5.3 Prerequisites 81

7.5.4 Installing the EDS-file 82

7.5.5 Connecting the device to the PLC 83

7.5.6 Going online with the PLC 88

7.5.7 Reading Process Data 90

7.5.8 Parameterizing Devices via Class Instance Attribute 92

7.6 Commissioning the Device in Modbus TCP 95

7.6.1 Implemented Modbus functions 95

7.6.2 Modbus Registers 95

7.6.3 Register mapping TBEN-S2-2COM-4DXP 100

7.7 Connecting the Device to a Modbus TCP Master 101

7.7.1 Used Hardware 101

7.7.2 Used Software 101

7.7.3 Prerequisites 101

7.7.4 Connecting the device to the PLC 101

7.7.5 Parameterizing the Device 109

7.7.6 Parameterizing the Device via Web Server 109

7.7.7 Reading Process Data in CODESYS 113

7.7.8 Going online with the PLC 115

8 Configuring and Parameterizing 117

8.1 Setting Parameters 117

8.1.1 Setting Parameters – COM0/COM1 117

8.1.2 Setting Parameters – Server Configuration Block (SCB) 121

8.1.3 Setting Parameters – DXP Channels 127

9Operating 129

9.1 Evaluating Process Input data 129

9.1.1 Evaluating Process Input Data - RS232/RS485 Mode 130

9.1.2 Evaluating Process Input Data – Modbus Client Mode 132

9.1.3 Evaluating Process Input Data –DXP Channels 134

9.1.4 Evaluating Process Input Data –Module Status 135

9.2 Writing Process Output Data 136

9.2.1 Writing Process Output Data – RS232/RS48 Mode 137

9.2.2 Writing Process Output Data – Modbus Client Mode 138

9.2.3 Writing Process Input Data – DXP Channels 139

9.3 Transmit and Receive Data 140

9.3.1 Transmit Data 140

9.3.2 Receive Data 141

2018/03

9.4 Evaluating LED Displays 142

9.5 Evaluating Diagnostic Data 144

3

9.5.1 Evaluating Diagnostic Data – COM channel diagnostics 144

9.5.2 Evaluating Diagnostic Data – DXP Diagnostics 145

10 Troubleshooting 147

11 Maintenance 149

11.1 Executing the firmware update 149

11.1.1 Example: Update the firmware with the PACTware™ FDT frame application 149

12 Repair 153

12.1 Returning devices 153

13 Disposal 155

14 Technical Data 157

15 Appendix 161

15.1 Possible Network Structures (Examples) 161

15.1.1 Daisy Chain - Maximum Number of Connected Modules 163

15.2 ARGEE/FLC 163

4

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

1 About these Instructions

These operating instructions describe the structure, functions and the use of the product and will
help you to operate the product as intended. Read these instructions carefully before using the
product. This is to avoid possible damage to persons, property or the device. Retain the instructions
for future use during the service life of the product. If the product is passed on, pass on these instruc­tions as well.

1.1 Target Groups

These instructions are aimed at qualified personnel and must be carefully read by anyone mount­ing, commissioning, operating, maintaining, dismantling or disposing of the device.

1.2 Explanation of symbols used

The following symbols are used in these instructions:

DANGER!

DANGER indicates an immediately dangerous situation, with high risk, the death or severe
injury, if not avoided.

WARNING!

WARNING indicates a potentially dangerous situation with medium risk, the death or
severe injury, if not avoided.

ATTENTION!

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

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

1.3 Additional Documents

The following additional documents are available online at www.turck.com:

 Data sheet

 TBEN-Accessories list (D301367)

2018/03

1

About these Instructions

1.4 Feedback about these instructions

We make every effort to ensure that these instructions are as informative and as clear as possible. If
you have any suggestions for improving the design or if some information is missing in the docu­ment, please send your suggestions to

[e-mail].

2

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

2 Notes on the Product

2.1 Product Identification

These instructions apply for the following compact serial interface modules:

 TBEN-S2-2COM-4DXP

2.2 Scope of Delivery

The delivery scope contains:

 TBEN-S2-2COM-4DXP

 Closure caps for M12 female connectors

2.3 Legal Requirements

The device falls under the following EU directives:

 2014/30/EU (electromagnetic compatibility)

 2011/65/EC (RoHS II Directive)

2.4 Manufacturer and Service

Hans Turck GmbH & Co. KG
Witzlebenstraße 7
45472 Muelheim an der Ruhr
Germany

Turck supports you with your projects, from initial analysis to the commissioning of your applica­tion. The Turck product database contains software tools for programming, configuration or com­missioning, data sheets and CAD files in numerous export formats. You can access the product data­base at the following address:

Should you have any further questions, please contact the sales and service team in Germany under
the following telephone numbers:

Sales: [phone]

Technology: [phone]

Internet:

Outside Germany, please contact your local Turck representative.

www.turck.de

www.turck.en/products

2018/03

3

Notes on the Product

4

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

3 For Your Safety

The product is designed according to state-of-the-art technology. However, residual risks still exist.
Observe the following warnings and safety notices to prevent damage to persons and property.
Turck accepts no liability for damage caused by failure to observe these warning and safety notices.

3.1 Intended Use

The devices are only intended for use in industrial applications.

The block module TBEN-S2-2COM-4DXP offers two serial interfaces for connecting serial RS232 and
RS482 data terminal devices.

Besides the raw RS232/RS485-communication, the device supports Modbus RTU. 32 Modbus RTU
server can be connected per port.

Additionally, the module provides 4 universal digital channels. The multiprotocol interfaces can be
used as EtherNet/IP™ Device, Modbus TCP Slave, oder PROFINET® Device.

The devices may only be used as described in this manual. Any other use is not in accordance with
the intended use. Turck accepts no liability for any resulting damage.

3.2 General Safety Instructions

 The device may only be assembled, installed, operated and maintained by professionally trained

personnel.

 The device may only be used in accordance with applicable national and international regula-

tions, standards and laws.

 The device only meets the EMC requirements for industrial areas and is not suitable for use in res-

idential areas.

2018/03

5

For Your Safety

6

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

4 Product Description

132

144.3

32

32

C0C1C2C3

24

17.9

28

X2

X1

P2

P1

ø 4.6

The devices are designed in a fully encapsulated housing with degree of protection IP65/IP67/
IP69K. Two ports are available for connecting devices with serial interfaces. You can also connect
sensors and actuators via 4 digital I/O channels which can be used as inputs and outputs without
configuration. The terminals for serial devices and digital I/Os are M12 sockets. Two 4-pole M8 sock­ets are provided for the Ethernet connection. The supply voltage is also connected using two 4 pole
M8 connectors.

4.1 Device Overview

Fig. 1: Dimensions

4.2 Display Elements

The devices have multi-color LEDs with the following functions:

 Supply voltage

 Group and bus errors

 Status

 Wink function

2018/03

7

Product Description

4.3 Properties and Features

 Multiprotocol functionality PROFINET IO Device, EtherNet/IP™ Device, Modbus TCP Slave

 2x M8, 4-pole, Ethernet connection

 Integrated Ethernet switch, allows line topology

 Transmission speed 10 Mbps/100 Mbps

 4-pole M8-connectors for voltage supply

 Separated power groups for safety shutdown

 Two serial interface which can be used as RS232 or RS485

 Integrated Modbus RTU Client function for connecting up to 32 Modbus RTU Server per port

 Four universal digital channels as PNP inputs or outputs (0,5 A)

 192 byes per port per write or read operation

 Integrated web server

 LED displays and diagnostics

 Fibre-glass reinforced housing

 Shock and vibration tested

 Fully potted module electronics

 Degree of protection IP65/IP67/IP69K

4.4 Functional Principle

The devices provide a multiprotocol Ethernet interface for Modbus TCP, EtherNet/IP™ and PROF­INET. The device is connected to Ethernet as PROFINET IO Device, EtherNet/IP™ Device or Modbus
TCP Slave via the Ethernet interface. Process data between Ethernet and TBEN-S are exchanged
during runtime. The RS232/RS485 interfaces are used for connecting devices with RS232 and/or
RS485 interface (e.g. barcode readers, printers, drives, light curtains, etc.)

8

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

4.5 Functions and Operating Modes

4.5.1 Multi protocol functionality

The compact I/O-stations of the TBEN-S product line combine the three Ethernet-protocols:

 PROFINET

 EtherNet/IP™

 Modbus TCP

A multi-protocol device can be operated without intervention of the user (which means, without
changes in the parameterization) in all of the three Ethernet protocols mentioned.

During the start-up, after a power-on, the module runs in "snooping" mode and detects the Ether­net protocol which requests a link connection by listening the traffic.

If a protocol is detected, the device is set automatically to the respective protocol. After this an
access to the device from other protocols is read-only.

Manual Protocol Selection

The protocol can also be determined manually. This skips the snooping-phase and the device is per­manently set to the selected protocol. An access to the device from other protocols is read-only.

The explicit protocol selection allows thus an additional locking mechanism.

4.5.2 Serial RS232 or RS485 Data Communication

In the RS232 mode one device can be connected to each serial port. In the RS485 mode up to 32
devices can be connected to one port.

Transmit and receive sequence: s. Transmit and Receive Data, page 141

2018/03

9

Product Description

4.5.3 Modbus RTU Data Communication

The Modbus RTU data communication is coordinated by the TBEN-S2-2COM-4DXP and is transpar­ent for PLC programmers. The TBEN-S2-2COM-4DXP functions as a Modbus RTU Client (Modbus
RTU Master). The process values of connected Modbus RTU Servers (Modbus RTU Slaves) are directly
available. In addition to that, the state of all Modbus connections can be monitored.

Modbus Client Mode

The Modbus Client Mode RS232, allows the connection of up to 8 Modbus RTU Servers. The Modbus
Client Mode RS485 allows the connection of up to 32 Modbus RTU Servers without any program­ming effort. Depending on the connected devices, applications with up to 64 RS485-devices are
possible .

 Standard mode (s. p. 124)

–

1 Modbus RTU Server per Server Configuration Block (SCB)

– max. 8 Modbus RTU Servers per COM port

 Multi server mode (s. p. 125)

–

Up to 12 identical Modbus RTU Servers per Server Configuration Block (SCB)

– Max. 32 Modbus RTU Servers per COM port, in total max. 64 per TBEN-S2-2COM-4DXP device.

 Read/ write extension (s. p. 126)

–

Connection of Modbus RTU Servers with more than 12 registers, which have to be read or writ­ten.

4.6 Configurable Digital Channels

The device provides four digital channels. The channels can be used as input or output without con­figuration. Each output is short-circuit proof with 0.5 A.

4.7 Technical Accessories

Accessories for mounting, connecting and parameterizing can be found in the Accessories List for
TBEN (D301367) under www.turck.com. The accessories are not part of the scope of delivery.

10

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

5Mounting

1

2

3

4

The device can be mounted on a DIN rail according to EN 60715 (TS35) or screwed onto a mounting
plate. Both composite and individual assembly are possible.

5.1 Mounting Module Composites

The TBNN-S0… adapters can be used to build module composites for group assembly.

1

4

2

3

Fig. 2: Build module groups four mounting the
devices onto a mounting plate

 Unlock the cover flap with a flat tool (e.g. screw driver) (1).

 Open the flap completely (2).

 To join the TBEN-S-module and the spacer, insert the key of the spacer into the slot of the TBEN-

S-module (3).

 Flap back the cover and close it (4). It has to engage audibly.

 Repeat steps 1 to 4 until the module group in complete.

2018/03

Fig. 3: Build module groups four mounting the
devices onto a DIN rail (TS35)

11

Mounting

5.2 Mounting on Mounting Plate

The devices are fixed on a pre-drilled mounting plate with two M4 screws. The spacers TBNN-S0-STD
are necessary for mounting module composites.

 Mount the modules or the module composites according to Fig. 4: Fixing the device to the

mounting plate.

Fig. 4: Fixing the device to the mounting plate

5.3 Mounting on a DIN rail (TS 35)

Single modules or module composites can be mounted on a DIN rail (TS 35) using the spacers TBNN­S0-DRS.

ATTENTION!

Incorrect mounting

Malfunction due to faulty grounding

 Orient the spacers so that the arrow in the cover flap of every spacer points in direction

to the M8 Ethernet connectors.

 Connect the grounding contact of the spacer to the grounding contact of the device.

 Mount spacers on the right and the left side of the device.

 Place the device or the composite on the DIN rail so that the cut-outs in the spacers enclose the

DIN rail (1).

 Close the rotating pin in the spacers by means of a screw driver (2)

 Ground the device.

2

12

1

Fig. 5: Mounting the Module Composite on a DIN rail

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

NOTE

To increase stability on the moun
right side of the modules/module composites.

5.4 Grounding the Device

5.4.1 Grounding and Shielding Concept

Field bus and I/O part of the TBEN-S modules can be grounded separately.

ting rail, end brackets can be mounted on the left and

X1

C0

C1

C2

C3

P1

X2

P2

Fig. 6: Replacement wiring diagram, shielding
concept

1
2
3

Fig. 7: Grounding clamp (1)

Fig. 8: Grounding contact Fig. 9: Grounding of spacers
Grounding ring (2) and
Metal screw (3)

4

TBNN-S0-DRS

2018/03

The grounding clamp (1) at the M8 connectors for the fieldbus connection (P1, P2) connects the
shield of the fieldbus lines.

The grounding ring (2) leads the shield at the flange of the M8 connectors for the fieldbus connec­tion via an RC-circuit to the outside of the station.

By mounting the module onto a mounting plate through the mounting hole, the module is con­nected to the reference potential of the installation by a metal screw (3).

The spacers TBNN-S0-DRS for mounting the TBEN-S-modules onto a DIN rail (TS 35) connect the
grounding contact (4) of the modules with the DIN rail and thus with FE.

13

Mounting

5.4.2 Ground the Device (FE)

Grounding clamp and grounding ring are connected.

 When mounting on a DIN rail fix the enclosed metal screw at the lower mounting hole.

 The shield at the flange of the M8 connectors for the field bus connection is connected to the

reference potential of the installation.

If a common reference potential is not required, remove the grounding clamp to disconnect the
fieldbus shield or fix the module with a plastic screw.

Removing the Grounding Clamp

 Use a flat screwdriver to slide the grounding clamp forward and remove it.

Fig. 10: Removing the Grounding Clamp

Mounting the grounding clamp

 Insert the grounding clamp between the fieldbus connectors (using a screwdriver if necessary)

so that it makes contact with the metal housing of the connector.

 The shielding of the fieldbus lines is now connected to the grounding clamp.

Fig. 11: Mounting the grounding clamp

14

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

6 Connecting

1 = TX +
2 = RX +
3 = RX –
4 = TX –

1 = RX +
2 = TX +
3 = TX –
4 = RX –

v

P1 P2

42

31

v

42

31

6.1 Connecting the Modules to the Ethernet

The TBEN-S2 module is provided with an integrated autocrossing switch with two 4-pin M8 Ether­net plug connectors for connecting to the fieldbus.

ATTENTION!

Interchanging of Ethernet- and power cables

Destructio

 Observe using the correct M8-connectors when connecting Ethernet- and power

cables (Ethernet: P1 and P2, power: X1and X2).

Fig. 12: M8 Ethernet connector

 Connect the device to Ethernet according to the pin assignment below.

n of module electronic

Fig. 13: Pin assignment Ethernet connectors

6.1.1 Ethernet Connection for QC/FSU Applications

NOTE

Please observe the following for QuickConnect (

–do not use a crossover-cable
– ETH1 = connector for
– ETH2 = connector for

Further information concerning QuickConnect and FSU can be found here:

 EtherNet/IP™: QC – QuickConnect, page 51

 PROFINET: FSU - Fast Start-Up (prioritized startup), page 23

incoming Ethernet-line
outgoing Ethernet-line

QC)- and Fast Start-Up (FSU)-applications:

2018/03

15

Connecting

1 BN = V1 (+)
2 WH = V2 (+)
3 BU = GND V1
4 BK = GND V2

wv

X1 X2

24

13

42

31

6.2 Connecting Power Supply

The TBEN-S2 module is provided with two 4-pin M8 plug connectors for connecting the power sup­ply. V1 and V2 are galvanically isolated.

ATTENTION!

Interchanging of Ethernet- and power cables

Destruction of module electronic

 Observe using the correct M8-connectors when connecting Ethernet- and power

cables (Ethernet: P1 and P2, power: X1and X2).

Fig. 14: M8 connector for connecting the supply voltage

 Connect the device to the voltage supply according to the pin assignment below.

Pin assignment

X1 Power feed

X2 Continuation of the power to the next node

V1 Power supply 1 (incl. supply of electronics)

V2 Power supply 2

Fig. 15: Pin assignment power supply connectors

NOTE

The system voltage (V1) and the load voltage (V2) are fed in and monitored separately. In
case of an undercut of the admissible voltage, the connectors are switched-off according
to the module's supply concept. In case of an undervoltage at V2, the LED PWR changes
from green to red. In case of an undervoltage at V1, the LED is turned off.

16

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

6.2.1 Supply Concept

V1

V2

All TBEN-S1-modules are supplied via two separate voltages V1 and V2.

The I/O-channels are separated into the different potential groups "detachable I/O" (supplied
through V2) and "non-detachable" I/O (supplied through V1).

This allows a safety shutdown of parts of an installation via emergency-off circuits.

V1 = supply of module electronics and the respective connectors

V2 = supply of the respective connectors

Fig. 16: Power supply of TBEN-S2-2COM-4DXP

6.3 Connecting Serial Devices

The TBEN-S2 module is provided with two 5-pin M12 connectors for connecting serial RS232 or
RS485 device.

Fig. 17: M12 connector for connecting serial RS232 and RS485 devices

Connect the device to the voltage supply according to the pin assignment below.

Pin assignment

RS232 connection RS485 connection

v

1 = V

2

2 = TXD

3

1

4

5

C0...C1

Fig. 18: RS232 connection Fig. 19: RS485 connection

1

aux

3 = GND V1
4 = RXD
5 = FE

v

2

1

4

5

C0...C1

1 = V
2 = TX/RX+

3 = GND V1

3

4 = TX/RX–

5 = FE

aux

1

2018/03

17

Connecting

6.3.1 Activating/Deactivating of RS485 Termination and Biasing

Fig. 20: RS485 termination and biasing

RS485 Termination

The TBEN-S2 module is provided with one internal bus termination resistor per COM port which can
be activated or deactivated via the parameter "Termination active" (s. p. 117). In the default setting
the internal termination is activated. The termination can also be done externally. The internal ter­mination has to be deactivated if an external termination is used.

The termination at TBEN-S2-2COM-4DXP is necessary, if the device is mounted at the beginning or
the end of the RS485 line. When building up an RS485 line topology a terminating resistor (e.g.
RSE57-TR2/RFID) has to be set at the other end of the RS485 line.

Accessories for mounting, connecting and parameterizing can be found in the Accessories List for
TBEN (D301367) under www.turck.com. The accessories are not part of the scope of delivery.

Biasing

Activating the biasing function suppresses undefined signal levels on both signal lines in the RS485
network by means of a bias resistor.

In the TBEN-S2-2COM-4DXP the biasing is is done with a biasing resistor of 600 W.

The biasing function can be activated or deactivated via the parameter "Biasing active" s. p. 117 In
the default setting the biasing function is activated.

We recommend to activate the biasing function, if the TBEN-S2-2COM-4DXP is mounted at the
beginning or the end of the RS485.

18

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

6.4 Connecting Digital Sensors and Actuators

The TBEN-S2 module is provided with eight 5-pin M12 connectors for connecting digital sensors
and actuators. The following combinations of sensors an actuators can be connected:

 2 digital inputs

 2 digital outputs

 1 digital input and 1 digital output

Fig. 21: M12 connector for connecting digital sensors and actuators

 Connect the sensors and actuators to the device according to the pin assignment shown below.

Pin assignment

v

2

1

5

4

C2...C3

1 = V

3

2

aux

2 = DXP
3 = GND V2
4 = DXP
5 = FE

Fig. 22: Pin assignment for digital sensors and actuators

The channels are assigned to the connectors as follows:

Channel Slot Pin

DXP4 (Ch4) C2

DXP5 (Ch5) C2

DXP6 (Ch6) C3

DXP7 (Ch7) C3

4

2

4

2

2018/03

19

Connecting

20

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

7 Commissioning

The module automatically starts after the electrical wiring and connecting the supply voltage.

7.1 Setting the IP address

In the delivery state the module has the IP address 192.168.1.254. A PROFINET device name has not
yet been assigned. The IP address can be set via the Turck Service Tool, the DTM, the web server, a
DHCP server or PROFINET DCP. In the following example, the IP address is set by means of the Turck
Service Tool. The tool is available for free under ww.turck.com.

 Connect the device to a PC via the Ethernet interface.

 Open the Turck Service Tool.

 Click "Search" or press F5.

Fig. 23: Turck Service Tool – start dialog

The Turck Service Tool shows the connected devices.

Fig. 24: Turck Service Tool – found devices

 Click on the desired device.

2018/03

21

Commissioning

 Click "Change" or press F2.

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

NOTE

Clicking the IP address of the TBEN-S2-2COM-4DXP opens the device's web server.

 Change the IP address and the network mask if necessary.

 Assume the changes by clicking "Set in device".

Fig. 26: Turck Service Tool – Change device configuration

22

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

7.2 Commissioning the Device in PROFINET

7.2.1 GSDML file

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

GSDML-file Zip-file

GSDML-V2.3-Turck-TBEN_S2_2COM_4DXP-YYYYMMDD-xxxxxx.xml

7.2.2 FSU - Fast Start-Up (prioritized startup)

FSU enables a PLC to build up connections to PROFINET-nodes in less than 500 ms after switching­on the network power supply. The fast start-up is necessary for fast tool changing applications at
robot arms for example in the automobile industry.

The TBEN-S2-2COM-4DXP support FSU, but the function can only be guaranteed for the digital
channels.

TBEN-S_PROFINET.zip

2018/03

23

Commissioning

7.2.3 PROFINET IO Device Model

The technical properties of PROFINET IO devices are defined via their device description file, the
GSDML file. A PROFINET IO device consists of 1…n slots, which can also contain 1…n sub slots. Sub
slots are placeholders for sub modules and establish the interface to the process. Sub modules can
contain parameters, data and diagnostics.

Slot 0 is always reserved as Device Access Point (DAP). The DAP contains the physical interface to
the Ethernet network and represents the device. The other slots or sub slots represent the other
device functions. The structure is defined by the manufacturer of field devices. It is not necessary
that every slot/sub slot is related to physical functions. This device model allows manufacturers to
design modular and flexible decentral field devices. User are flexible in configuring decentralized
field devices.

7.2.4 TBEN-S2-2COM-4DXP – Slots and Sub slots (Overview)

Besides Slot 0 (DAP) all other slots of TBEN-S2-2COM-4DXP contain only one sub slot. for this rea-

son slots and sublots are described as synonyms in the following.

Slot-no. Name Description Pluggable devices

0 TBEN-S2-2COM-4DXP This slot represents the access to

the device via PROFINET, Device

Access Point.

– Device Access Point
– Ethernet interface
– Ethernet port 0
– Ethernet port 1

1 COM channel 0 This slot defines the function of

the first COM port (COM0).

– RS232 simple (s. p. 27)
– RS232 advanced (s. p. 28)
– RS485 simple (s. p. 29)
– RS485 advanced (s. p. 30)
– MB Client RS232 (s. p. 32)
– MB Client RS485 (s. p. 32)

2…9 Buffer/server channel 0 Slots 2 to 9 are used to configure

the data buffer for the in- and

output data or to configure

server connected via Modbus

RTU. The settings relate to COM0.

10 COM channel 1 Slot 10 defines the function of

the second COM port (COM1).

– RS Data 24Byte IN/24Byte OUT

(s. p. 31)

– MB-Server 1 Reg. IN/1 Reg. OUT
– (s. p. 28)
– MB-Server 12 Reg. IN/12 Reg. OUT

(s. p. 28)

– RS232 simple (s. p. 27)
– RS232 advanced (s. p. 28)
– RS485 simple (s. p. 29)
– RS485 advanced (s. p. 30)
– MB Client RS232 (s. p. 32)
– MB Client RS485 (s. p. 32)

24

11 -18 Buffer/server channel 1 Slots 11 to 18 are used to config-

ure the data buffer for the in- and

output data or to configure

server connected via Modbus

RTU. The settings relate to COM1.

19 COM diagnostics Slot 19 is used to map the cyclic

diagnostic data.

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

– RS Data 24Byte IN/24Byte OUT

p. 31)

(s.

– MB-Server 1 Reg. IN/1 Reg. OUT
– (s. p. 32)
– MB-Server 12 Reg. IN/12 Reg. OUT

(s. p. 33)

COM diagnostics (s.

p. 34)

Slot-no. Name Description Pluggable devices

20 MB-Server Status Slot 20 is used to cyclically map

the status data of connected

Modbus RTU server.

21 MB-Server Timing Slot 21 can be used to cyclically

map timing data of connected

Modbus RTU server.

22 DXP Slot 22 is used to configure and

to use the 4 digital in- or output

channels (DXP).

23 DXP diagnostics Slot 22 is used to map the cyclic

diagnostic data for the DXP

channels.

24…27 Ext. DXP functions 4…7 Slots 24…27 are used to config-

ured the input filter times and
the pulse stretching for the digi­tal input channels 4…7.

28 Module status Slot 28 is used to cyclically map

module status data.

MB-Server Status (s. p. 35)

MB-Server Timing (s.

DXP (s.

p. 37)

DXP diagnostics (s. p. 38)

DIF pulses (s.

Module status (s.

p. 37)

p. 38)

p. 39)

2018/03

25

Commissioning

Sub module "TBEN-S2-2COM-4DXP" (Device Access Point)

The Device Access Point "TBEN-S2-2COM-4DXP" provides device's PROFINET interface.
This module is always plugged in slot 0 and cannot be deleted.

 PROFINET IO

Features Description

Conformance Class B

Update time [ms] 1…512

Media Redundancy Protocol (MRP) MRP Client

Fast Startup (FSU) < 500 ms

Topology detection though LLDP yes

 Parameters

Parameters Value Meaning Description

Output behav, at
communic. loss

Deactivate all diag­nostics

Deactivate load volt­age diagnostics

Deactivate I/O-ASSIS­TANT Force Mode

Deactivate Modbus 0 no Deactivates the Modbus protocol

Deactivate
EtherNet/IP

Deactivate
PROFINET

00 set to 0 Depending on the parameterization, the digital out-

01 hold current

value

0 no Deactivates all diagnostics

1yes

0 no Deactivates the under voltage diagnostics for V2.

1yes

0 no Deactivates the forcing of output values via DTM.

1yes

1yes

0 no Deactivates the EtherNet/IP™ protocol

1yes

0 no Deactivates the PROFINET protocol

1yes

puts switch to 0 or hold the current value, if the
PROFINET IO communication between the device
and the PLC is disturbed.

26

Deactivate
Web server

 Process data

0 no Deactivates the web server

1yes

This sub module has no process data.

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

Sub module "RS232 simple"

The sub module "RS232 simple" can be plugged into slots 1 (COM 0) and slot 10 (COM 1). It switches
the COM port to the RS232 mode, provides parameters for the configuration and process data for
control and status data. More detailed information about the transmit and receive sequence can be
found under Transmit and Receive Data, page 141.

Parameters (s. p. 118)

The following functions are preset in this sub module an can not be changed:

Parameters Value

EOF detection Character time-

out

Character timeout 100 Character timeout in ms.

Response timeout 0 No timeout

 Process input data (s. p. 130)

Process value Offset Data type

COM – Status bits of the COM port %IB0 USINT

Transmitter ready

Receive complete %IX0.1 BOOL

Frame error %IX0.2 BOOL

Parity/format error %IX0.3 BOOL

Buffer overflow %IX0.4 BOOL

Timeout %IX0.5 BOOL

Invalid TX length %IX0.6 BOOL

Invalid RX length %IX0.7 BOOL

The character timeout defines the duration of time within
which another character must be received after receiving a
character. Exceeding this time is interpreted as the end of the
data packet.

%IX0.0 BOOL

2018/03

Reserved %IB1 USINT

Received frame length %IB2 USINT

 Process output data (s. p. 138)

Process value Offset Data type

COM – Control bits of the COM port %QB0 USINT

Transmit

Receive %QX0.1 BOOL

Reserved %QB1 USINT

Transmitter frame length %QB2 USINT

Reserved %QB3 USINT

Receiver frame length %QB4 USINT

%QX0.0 BOOL

27

Commissioning

Sub module "RS232 advanced"

The sub module "RS232 simple" can be plugged into slots 1 (COM 0) and slot 10 (COM 1). It switches
the COM port to the RS232 mode, provides parameters for the configuration and process data for
control and status data. More detailed information about the transmit and receive sequence can be
found under Transmit and Receive Data, page 141.

 Parameters (s. p. 117)

The sub module contains additional parameters:

–

EOF detection: character timeout, 1st end delimiter, 2nd end delimiter, frame length

– response timeout

 Process input data (s. p. 130)

Process value Offset Data type

COM – Status bits of the COM port %IB0 USINT

Transmitter ready %IX0.0 BOOL

Receive complete %IX0.1 BOOL

Frame error %IX0.2 BOOL

Parity/format error %IX0.3 BOOL

Buffer overflow %IX0.4 BOOL

Timeout %IX0.5 BOOL

Invalid TX length %IX0.6 BOOL

Invalid RX length %IX0.7 BOOL

Reserved %IB1 USINT

Received frame length %IB2 USINT

 Process output data (s. p. 138)

Process value Offset Data type

COM – Control bits of the COM port %QB0 USINT

Transmit %QX0.0 BOOL

Receive %QX0.1 BOOL

Reserved %QB1 USINT

Transmitter frame length %QB2 USINT

28

Reserved %QB3 USINT

Receiver frame length %QB4 USINT

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

Sub module "RS485 simple"

The sub module "RS485 simple" can be plugged into slots 1 (COM 0) and slot 10 (COM 1). It switches
the COM port to the RS485 mode, provides parameters for the configuration and process data for
control and status data. More detailed information about the transmit and receive sequence can be
found under Transmit and Receive Data, page 141.

 Parameters (s. p. 117)

The following functions are preset in this sub module an can not be changed:

Parameters Value

Swap A/B line no Standard configuration, A = pin 2, B = pin 4

Termination active yes RS485 termination

Biasing active yes Biasing activated

EOF detection Character

Character timeout 100 Character timeout in ms.

Response timeout 0 no timeout

 Process input data (s. p. 130)

Process value Offset Data type

timeout

The character timeout defines the duration of time within which
another character must be received after receiving a character.
Exceeding this time is interpreted as the end of the data packet.

COM – Status bits of the COM port %IB0 USINT

Transmitter ready

Receive complete %IX0.1 BOOL

Frame error %IX0.2 BOOL

Parity/format error %IX0.3 BOOL

Buffer overflow %IX0.4 BOOL

Timeout %IX0.5 BOOL

Invalid TX length %IX0.6 BOOL

Invalid RX length %IX0.7 BOOL

Reserved %IB1 USINT

Received frame length %IB2 USINT

%IX0.0 BOOL

2018/03

29

Commissioning

 Process output data (s. p. 138)

Process value Offset Data type

COM – Control bits of the COM port %QB0 USINT

Transmit %QX0.0

Receive %QX0.1

Reserved %QB1 USINT

Transmitter frame length %QB2 USINT

Reserved %QB3 USINT

Receiver frame length %QB4 USINT

Sub module "RS485 advanced"

The sub module "RS485 simple" can be plugged into slots 1 (COM 0) and slot 10 (COM 1). It switches
the COM port to the RS485 mode, provides parameters for the configuration and process data for
control and status data. More detailed information about the transmit and receive sequence can be
found under Transmit and Receive Data, page 141.

 Parameters

The sub module contains additional parameters:

–

EOF detection: character timeout, 1st end delimiter, 2nd end delimiter, frame length

– Termination active

– Biasing active

– response timeout

 Process input data (s. p. 130)

BOOL

BOOL

Process value Offset Data type

COM – Status bits of the COM port %IB0 USINT

Transmitter ready %IX0.0 BOOL

Receive complete %IX0.1 BOOL

Frame error %IX0.2 BOOL

Parity/format error %IX0.3 BOOL

Buffer overflow %IX0.4 BOOL

Timeout %IX0.5 BOOL

Invalid TX length %IX0.6 BOOL

Invalid RX length %IX0.7 BOOL

Reserved %IB1 USINT

Received frame length %IB2 USINT

30

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

 Process output data (s. p. 138)

Process value Offset Data type

COM – Control bits of the COM port %QB0 USINT

Transmit

Receive %QX0.1 BOOL

Reserved %QB1 USINT

Transmitter frame length %QB2 USINT

Reserved %QB3 USINT

Receiver frame length %QB4 USINT

Sub module "RS Data 24Byte IN/24Byte OUT"

The sub module "RS Data 24Byte IN/24Byte OUT" can be plugged into slots 2…9 (COM 0) and slot
11…18 (COM 1). The sub module is used to set up the transmit and receive buffer for the serial com­munication via RS232 or RS485 modularly in steps of 24 bytes. The maximum length for the transmit
and receive buffer for one COM port is 8 × 24 bytes = 192 bytes.

This sub module can only be used for COM ports which are used as pure RS232 or RS485 interface.

 Parameters

This sub module requires no configuration and has thus no parameters.

Process input data (s. p. 139)

Process value Offset Data type Description

Byte 0 %IB0 Byte First byte of the receive buffer block

%QX0.0 BOOL

……

Byte 23 %IB23 Byte Last byte of the receive buffer block

……

Process output data (s. p. 131)

Process value Offset Data type Description

Byte 0 %QB0 Byte First byte of the transmit buffer block

……

Byte 23 %QB23 Byte Last byte of the transmit buffer block

……

2018/03

31

Commissioning

Sub module "MB-Client RS232"

Sub module "MB-Client RS485"

The sub module "MB-Client RS232" can be plugged into slots 1 (COM 0) and slot 10 (COM 1). It
switches the COM port to the RS232 mode and activates the Modbus RTU Client function for this
COM port.

 Parameters (s. p. 118)

 Process input data (s. p. 135)

Process value Offset Data type

Reserved - not used for the Modbus RTU Client function %IB0…%IB3 USINT

MB-Server cycle time (*1 ms) %IB4 UINT

The sub module "RS485 simple" can be plugged into slots 1 (COM 0) and slot 10 (COM 1). It switches
the COM port to the RS485 mode and activates the Modbus RTU Client function for this COM port.

 Parameters (s. p. 118)

 Process input data (s. p. 135)

Process value Offset Data type

Reserved - not used for the Modbus RTU Client function %IB0…%IB3 USINT

MB-Server cycle time (*1 ms) %IB4 UINT

Sub module "MB-Server 1Reg. IN/1Reg. OUT”

Sub module "MB-Server 1Reg. IN/1Reg. OUT” can be plugged into slots 2…9 (COM 0) and slot
11…18 (COM 1). This sub module is used to configure connected Modbus RTU-Servers and to
exchange data with the connected servers. Eight Modbus RTU servers can be configured for each
COM port.

This sub module can only be used for COM ports which are used as Modbus RTU Clients.

 Parameters (s. p. 121)

 Process input data (s. p. 135)

Process value Offset Data type Description

Input register 0 %IW0 UINT Input register of the Modbus server

 Process output data (s. p. 140)

32

Process value Offset Data type Description

Output register 0 %QW0

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

UINT

Output register of the Modbus server

Sub module "MB-Server 12 Reg. IN/12 Reg. OUT"

The sub module "MB-Server 12Reg IN/12Reg. OUT" can be plugged into slots 2…9 (COM 0) and slot
11…18 (COM 1). This sub module is used to configure connected Modbus RTU-Servers and to
exchange data with the connected servers. Eight Modbus RTU servers can be configured for each
COM port.

This sub module can only be used for COM ports which are used as Modbus RTU Clients.

 Parameters (s. p. 121)

 Process input data (s. p. 135)

Process value Offset Data type Description

Input register 0 %IW0 UINT First input register of the Modbus server

……

Input register 11 %IW011 UINT Last input register of the Modbus server

 Process output data (s. p. 140)

Process value Offset Data type Description

Output register 0 %QW0 UINT First output register of the Modbus server

……

Output register 11 %QW11 UINT Last output register of the Modbus server

……

……

2018/03

33

Commissioning

Sub module"COM diagnostics"

The sub module "COM diagnostics" can be plugged into slot 19. This sub module provides diagnos­tic data for the COM ports via cyclic input data.

 Parameters

This sub module requires no configuration and has thus no parameters.

 Process input data (s. p. 145)

Process value Offset Data type

Diagnostics for COM 0 %IB0 USINT

Hardware error %IX0.0 BOOL

Parameterization error %IX0.1 BOOL

Overcurrent supply VAUX1 %IX0.7 BOOL

Modbus diagnostics for COM 0 %IB1

Error MB-server 0 %X1.0 BOOL

………

Error MB-server 7 %X1.7 BOOL

Diagnostics for COM 1 %IB0 USINT

Hardware error %IX0.0 BOOL

Parameterization error %IX0.1 BOOL

Overcurrent supply VAUX1 %IX0.7 BOOL

Modbus diagnostics for COM 1 %IB1

Error MB-server 0 %X1.0 BOOL

………

Error MB-server 7 %X1.7 BOOL

34

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

Sub module "MB-Server Status"

The sub module Sub module "MB-Server Status" can be plugged into slot 20. This sub module cycli­cally provides status data for the connected Modbus RTU servers.

 Parameters

This sub module requires no configuration and has thus no parameters.

 Process input data (s. p. 134)

Process value Offset Data type

COM 0 MB-Server Status %IB0 USINT

Error code

Error code bit 1 Ch0 %IX0.2 BOOL

Error code bit 2 Ch0 %IX0.2 BOOL

Error code bit 3 Ch0 %IX0.3 BOOL

Read error Ch0 %IX0.4 BOOL

Write error Ch0 %IX0.5 BOOL

Parity/format error Ch0 %IX0.6 BOOL

MODBUS timeout Ch0 %IX0.7 BOOL

COM 0 MB-Server Status %IB1 USINT

Valid read config. K0 %IX1.4 BOOL

Valid write config. Ch0 %IX1.5 BOOL

………

COM 0 MB-Server Status %IB14 USINT

Error code Bit 0 Ch7 %IX14.1 BOOL

Error code Bit 1 Ch7 %IX14.2 BOOL

Error code Bit 2 Ch0 %IX14.2 BOOL

bit 0 Ch0 %IX0.1 BOOL

2018/03

Error code Bit 3 Ch7 %IX14.3 BOOL

Read error Ch7 %IX14.4 BOOL

Write error Ch7 %IX14.5 BOOL

Parity/format error Ch7 %IX14.6 BOOL

MODBUS timeout Ch7 %IX14.7 BOOL

COM 0 MB-Server Status %IB15 USINT

Valid read config. K7 %IX15.4 BOOL

Valid write config. K7 %IX15.5 BOOL

COM 1 MB-Server Status %IB16 USINT

Error code bit 0 Ch0 %IX16.1 BOOL

Error code bit 1 Ch0

%IX16.2

BOOL

35

Commissioning

Process value Offset Data type

Error code bit 2 Ch0 %IX16.2 BOOL

Error code bit 3 Ch0 %IX16.3 BOOL

Read error Ch0 %IX16.4 BOOL

Write error Ch0 %IX16.5 BOOL

Parity/format error Ch0 %IX16.6 BOOL

MODBUS timeout Ch0 %IX16.7 BOOL

COM 1 MB-Server Status %IB17 USINT

Valid read config. K0 %IX17.4 BOOL

Valid write config. Ch0 %IX17.5 BOOL

………

COM 1 MB-Server Status %IB30 USINT

Error code Bit 0 Ch7 %IX30.1 BOOL

Error code Bit 1 Ch7 %IX30.2 BOOL

Error code Bit 2 Ch0 %IX30.2 BOOL

Error code Bit 3 Ch7 %IX30.3 BOOL

Read error Ch7 %IX30.4 BOOL

Write error Ch7 %IX30.5 BOOL

Parity/format error Ch7 %IX30.6 BOOL

MODBUS timeout Ch7 %IX30.7 BOOL

COM 1 MB-Server Status %IB31 USINT

Valid read config. K7 %IX31.4 BOOL

Valid write config. K7 %IX31.5 BOOL

NOTE

Description of the Modbus Exceptions Codes

http://www.modbus.org/docs/Modbus_Application_Protocol_V1_1b.pdf.

36

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

Sub module "MB-Server Timing"

The sub module Sub module "MB-Server Timing" can be plugged into slot 21. This sub module cycli­cally provides timing data for the connected Modbus RTU servers.

 Parameters

This sub module requires no configuration and has thus no parameters.

 Process input data (s. p. 135)

Process value Offset Data type

COM 0 MB-Server Timing (*1ms) Ch0 %IW0 UINT

……

COM 0 MB-Server Timing (*1ms) Ch0 %IW7 UINT

COM 1 MB-Server Timing (*1ms) Ch0 %IW8 UINT

………

COM 1 MB-Server Timing (*1ms) Ch0 %IW15 UINT

Sub module "DXP"

The sub module "DXP" can be plugged into slot 22. It provides parameters for the configuration as
well as process data for the four digital channels (Ch4…Ch7) of the module. The DXP channels can
be used as input or output without any configuration.

 Parameters (s. p. 127)

 Process input data (s. p. 135)

Process value Offset Data type

DXP %IB0 USINT

Input value Ch4

Input value Ch5 %IX0.5 BOOL

Input value Ch6 %IX0.6 BOOL

…

%IX0.4 BOOL

2018/03

Input value Ch7 %IX0.7 BOOL

 Process output data (s. p. 140)

Process value Offset Data type

DXP %QB0 USINT

Outp

ut value Ch4 %QX0.4 BOOL

Output value Ch5 %QX0.5 BOOL

Output value Ch6 %QX0.6 BOOL

Output value Ch7 %QX0.7 BOOL

37

Commissioning

Sub module "DXP diagnostics"

The sub module "DXP diagnostics" can be plugged into slot 23. The sub module cyclically provides
diagnostic data for the four digital channels.

 Parameters

This sub module requires no configuration and has thus no parameters.

 Process input data (s. p. 146)

Process value Offset Data type

DXP %IB0 USINT

Overcurrent VAUX2 K4/K5 %IX0.2 BOOL

Overcurrent VAUX2 K4/K5 %IX0.3 BOOL

DXP %IB1 USINT

Overcurrent output Ch4 %IX1.4 BOOL

Overcurrent output Ch5 %IX1.5 BOOL

Overcurrent output Ch6 %IX1.6 BOOL

Overcurrent output Ch7 %IX1.7 BOOL

Sub module "DIF pulses"

The sub module "DIF pulses” (DIF = Digital Input Filter) can be plugged into slots 24…27. It provides
parameters for the configuration as well as process data for the four digital channels (Ch4…Ch7) of
the module. One slot is assigned to each digital channel. Slot 24 is assigned to the digital channel 4
and slot 27 is assigned to the digital channel 7. This sub module is used to configure the filter times
and the pulse stretching for the digital channels.

 Parameters (s. p. 127)

 Process data

This sub module has no process data. The configured parameters affect the input process values
of the sub module "DXP" (slot 22).

38

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

Sub module "Module status"

The sub module "Module status" can be plugged into slot 28. This sub module cyclically provides
module status data.

 Parameters

This sub module requires no configuration and has thus no parameters.

 Process input data (s. p. 136)

Process value Offset Data type

Module status – byte

Undervoltage V1 %IX0.1 BOOL

Internal error %IX0.2 BOOL

Force Mode active %IX0.6 BOOL

Module status – byte 1 %IB1 USINT

Module diagnostics pending %IX1.0 BOOL

Undervoltage V2 %IX1.7 BOOL

0 %IB0 USINT

2018/03

39

Commissioning

7.2.5 PROFINET diagnostics

In addition to the diagnostic information mapped to the process image, the TBEN-S2-2COM-4DXP
supports the following event-based PROFINET diagnostics.

Module diagnostics PROFINET diagnostics

Diagnostics Channel Connector Error code Channel/slot

Undervoltage

V1 0.0 0x0002 0/0

V2 0.1 0x0002 1/0

DXP diagnostics channel Connector Error code Channel/slot

Overcurrent output DXP4 C2 0x0001 4/22

DXP5 C2 0x0001 5/22

DXP6 C3 0x0001 6/22

DXP7 C3 0x0001 7/22

Overcurrent VAUX2 K4/K5 DXP4/DXP5 C2 0x0162 4+5/22

Overcurrent VAUX2 K6/K7 DXP6/DXP7 C3 0x0163 6+7/22

COM channel diagnostics PROFINET diagnostics

Hardware error COM0 C0 0x0015 0/1

Parameterization error COM 0 C0 0x0010 0/1

Overcurrent supply VAUX1 COM0 C0 0x0100 0/1

Hardware error COM1 C1 0x0015 1/10

Overcurrent supply VAUX1 COM1 C1 0x0101 1/10

40

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

7.2.6 Description of the 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)

Description of the acyclic device user data

Index Name Data type r/w Comment

Dec. Hex.

1

2

3

4

5

6

7

8…23

0x08…

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

0x01

Module designation STRING r Designation assigned to the module

0x02

(Slot 0)

Module revision STRING r Firmware revision of the module

0x03

Vendor ID WORD r Ident no. Turck

0x04

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

0x05

ule

Module type STRING r Module type

0x06

Device ID WORD r Ident no. of the module

0x07

reserved

0x17

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

25…31 0x19 …

0x1F

32 0x20 Input list Array of byte r List of all input channels in the module

33 0x21 Output list Array of BYTE r List of all output channels in the module

34 0x22 Diag. list Array of BYTE r List of all I/O-channel diagnostics

reserved

2018/03

35 0x23 Parameter list Array of BYTE r List of all I/O-channel parameters

36…450390x24…

0xAFEF

45040 0xAFF0 I&M0-functions r Identification & Maintaining Services

45041 0xAFF1 I&M1-functions STRING

reserved

r/w I&M tag Function and location

[54]

41

Commissioning

Index Name Data type r/w Comment

Dec. Hex.

45042 0xAFF2 I&M2-functions STRING

[16]

45043 0xAFF3 I&M3-functions STRING

[54]

45044 0xAFF4 I&M4-functions STRING

[54]

45045…
45055

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

0xAFF5 ­0xAFFF

I&M5 to I&M15-func­tions

Description of the Acyclic I/O Channel User Data

Index Name Data type r/w Comment

Dec. Hex.

1

2

3

Module parameters specific r/w Parameters of the module

0x01

Module type ENUM

0x02

UINT8

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

0x03

r/w I&M tag Function and location

not supported

r Contains the module type

4

5…9

Module ID DWORD r Ident number of the I/O

0x04

reserved

0x05

…0x09

10

11…18

0x0B…0

0x0A

Slave controller
Version

reserved

UINT8
array [8]

r Version number of the slave

controller.

x12

19 0x13 Input data specific r Input data of the respective

I/O channel

20…22 0x14 …

0x16

23 0x17 Output data specific r/w Output data of the respective

… … reserved

reserved

I/O channel

42

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

7.3 Connecting the device to a Siemens PLC in PROFINET

The following example describes the connection of the devices to a Siemens OPLC in PROFINET by
means of the programming software SIMATIC STEP7 Professional V13 (TIA-Portal).

7.3.1 Used Hardware

The following hardware components are used in this example:

 Siemens PLC S7-1500

 Block module TBEN-S2-2COM-4DXP

 8 × Banner K50TGRYS1QP at COM 0 as Modbus server

7.3.2 Used Software

The following software tools are used in this example:

 SIMATIC STEP7 Professional V13 (TIA-Portal)

 GSDML file for TBEN-S2-2COM-4DXP (to be downloaded for free under

www.turck.com)

7.3.3 Prerequisites

 The programming software has been started.

 A new project has been created.

 The PLC has been added to the project.

2018/03

43

Commissioning

7.3.4 Installing the GSDML-file

The GSDML-file can be downloaded for free from www.turck.com .

Verfügung.
 Adding the GSDML-file: Click "Options"  "Manage general station description files (GSD)".

Fig. 27: Adding the GSDML-file

 Installing the GSDML-file: Define the source path for the GSDML-file.

 Select the GSDML-file to be installed and click "Install".

Fig. 28: Installing the GSDML-file

 The device is added to the Hardware catalog of the programming software.

44

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

7.3.5 Configuring the Device

 Select the TBEN-S2-2COM-4DXP from the Hardware catalog and drag it into the "Device & net-

works" editor.

 Configure the device per drag & drop depending on the application.

 Define the function of the two COM ports (slot 1 and 10) and define the other slots by assigning

the suitable sub modules.

NOTE

The PROFINET device model, the sub modu
tion options are described under PROFINET IO Device Model, page 24 and Structure of

the TBEN-S2-2COM-4DXP, page 24.

le functions as well as the possible configura-

Fig. 29: Configuring the Device

2018/03

45

Commissioning

7.3.6 Connecting the device to the PLC

 Connect the device to the PLC in the "Devices & networks" editor.

Fig. 30: Connecting the device to the PLC

46

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

7.3.7 Assigning PROFINET device name

 Select "Online access" … "Online & diagnostics".

 Select "Functions"  „Assign name”.

 Enter the desired PROFINET device name for the device.

Fig. 31: Assigning PROFINET device name

2018/03

47

Commissioning

7.3.8 Setting the IP address in TIA Portal

 Select the TBEN-S2-2COM-4DXP in the "Device view".

 Select "Ethernet addresses"  in the register tab "Properties".

 Assign the desired IP address.

Fig. 32: Assigning the IP address

48

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

7.3.9 Going online with the PLC

 Start the online mode (Go online).

Fig. 33: Starting the online mode

 The device has been successfully connected to the PLC.

2018/03

49

Commissioning

7.3.10 Setting Module Parameters

Fig. 34: Setting Module Parameters

 Select "Device view"  "Device overview".

 Select the slot to be parameterized.

 Click "Properties" "general" "Module parameters".

 Set the parameters.

50

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

7.4 Commissioning the Device in EtherNet/IP™

Features Description

QuickConnect < 500 ms

Device Level Ring

Number of TCP connections 3

Number of CIP connections 10

Input Assembly Instance 103

Output Assembly Instance 104

Configuration Assembly Instance 106

7.4.1 EDS-file

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

EDS-file ZIP-file

TBEN-S2-2COM-4DXP_Rx.x.eds TBEN-S_ETHERNETIP.zip

7.4.2 QuickConnect (QC)

QuickConnect enables a PLC to build up connections to EtherNet/IP™ nodes in less than 500 ms
after switching-on the power supply for the EtherNet/IP™ network. The fast start-up is necessary for
fast tool changing applications at robot arms
for example in the automobile industry.

The modules TBEN-S2-2COM-4DXP support QuickConnect, but the function can only be guaran­teed for the digital channels.

(DLR) yes

NOTE

Activating QuickConnect also activa

Autonegotiation

Transmission speed

Duplex

Topology

AutoMDIX

ted the automatic setting of all necessary port-properties:

= deactivated

= 100BaseT

= Full duplex

= linear

= deactivated

2018/03

51

Commissioning

Ethernet connection for QC-applications

QuickConnect in TBEN-S

Turck TBEN-S devices support QuickConnect.

NOTE

Please read Ethernet Connection for QC/FSU Applications, page 15 for information about
the correct Ethernet-cabling in QC-applications with TBEN-S,

QuickConnect can be activated via the EDS-file of the device, the
bute or the web server

 EDS-fileAssembly Class 0x04, Configuration Assembly 106, Bit 9 = 1 (see s. p. 57)

.

Assembly Class, Class Instance Attri-

52

Fig. 35: QuickConnect parameter in the EDS-file

 Class Instance Attribute in the

TCP/IP Interface Class

Class Instance Attributes Value

245 (0xF5) 1 (0x01) 12 (0x0C) 0 = activated (default)

1: activated

 Web server

QuickConnect can also be activated or deactivated using the device's web server.

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

7.4.3 Diagnostic messages via process data

The diagnostic messages of the COM and the DXP channels are directly mapped into the process
data (see Process Data Mapping, page 60.)

Additionally, the device's status word contains the module diagnostics: In the default setting of the
device, the status word is mapped before the device’s process input data (s. p. 60).

Status word The status word contains the module status.

Byte 1 (MSB) Byte 0 (LSB)

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

res.

Force
Mode

active

reserved

Control word

Internal

error

Under-

voltage V1res.

Under-

voltage

V2

res.

ARGEE
Program
Running

Module

Diagnostics

Available

 Evaluating Process Input Data –Module Status, page 136
or

Gateway Class (VSC 100), Object Instance 2, gateway Instance, page 70

In the default setting of the device, the control word is mapped before the device’s process output
data (s. p. 60).

The control word has no function.

2018/03

53

Commissioning

7.4.4 EtherNet/IP™-standard classes

The modules support the following EtherNet/IP™ Standard Classes in accordance with the CIP spec­ification.

Class Code Object name

Dec. Hex.

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

Identity Object (0x01)

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

2.1 by ODVA & ControlNet International Ltd. and adapted to the Turck products.

Class attributes

Attr. No. Attribute name Get/ Set Type Value

Dec. Hex.

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/

Dec. Hex.

Ethernet Link Object (0xF6)

Type Description

Set

54

1 0x01 VENDOR G UINT Contains the vendor ID. Turck = 48

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

Communications Adapter 12

3 0x06 PRODUCT CODE G UINT Identifier for a specific product of a device type.

default: 27247

4 0x04 REVISION

Major Minor

5 0x05 DEVICE STATUS G WORD See

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

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

GSTRUCT

OF: USINT
USINT

Revision of the item the Identity Object is repre­senting.
0x01
0x06

bytes of the MAC-ID).

Device Status

dec =

6A6F

= 0x0C

dez

Attr. No. Attribute name Get/

Set

Dec. Hex.

Type Description

7 0x07 PRODUCT NAME

LENGTH
NAME

GSTRUCT

OF:

USINT
STRING
[13]

Device Status

Bit Name Definition

0…1 reserved default = 0

2C

3 reserved default = 0

4…7 Extended Device

8…15 reserved default = 0

onfiguredTRUE = 1

The application of the device has been configured ( default­settings).

0011 = no I/O connection established

Status

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

Common services

e. g.:
TBEN-S2-2COM-4DXP

Service code

Dec. Hex.

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

Class

Instance Service name

Returns a

Starts the reset service for the device.

Returns the contents of a specified attribute.

Modifies a single attribute.

predefined list of the object‘s attributes.

2018/03

55

Commissioning

7.4.5 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 the Turck products.

Class attributes

Attr. No. Attribute name Get/ Set Type Value

Dec. Hex.

1 0x01 REVISION G UINT 2

2 0x02 MAX OBJECT INSTANCE G UINT 104

Instance attributes

Attr. No. Attribute name Get/

Dec. Hex.

3 0x03 DATA S ARRAY OF

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

Type Description

Set

BYTE

256 or variable

Common services

Service code Class Instance Service name

Dec. Hex.

01 0x01 yes yes Get_Attribute_All

14 0x0E no yes Get_Attribute_Single

56

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

Configuration Assembly (Instance 106)

The modules support Configuration Assembly. It enables an EDS-based configuration/parameter­ization of the devices in the PLC software (if supported by the PLC).

The Configuration Assembly contains:

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

+ 218 bytes (parameter data)

Byte Bit 7 Bit 6 Bit 5 Bit 4 Bit 3 Bit 2 Bit 1 Bit 0
Dec. Hex.
Device configuration data, see

0…9 0x00…

0x09

Parameter data

10 0x0A - Operation mode
11 0x0B

12 0x0C - Data rate
13 0x0D - Character format
14 0x0E - Stop bits
15 0x0F - EOF detection
16 0x10

17 0x11

18 0x12 - Power supply VAUX1
19 0x13 ­20 0x14
21 0x15
22 0x16
23 0x17
24 0x18 1st end delimiter
25 0x19 2nd end delimiter
26 0x20
27 0x1B

28 0x1C Server address
29 0x1D - Number reg./server write access
30 0x1E - Number reg./ server read access
31 0x1F Read access
32 0x20 Write access
33 0x21 ­34 0x22
35 0x23
36 0x24
37 0x25
38 to 47 0x26 to

0x2F

98 to 107 0x62 to

0x6B

Device configuration data, page 59

-

Setting Parameters, page 117

-

-

-

Character timeout

Response timeout

MB-Server cycle time (*1ms)

COM 0 – SCB 0.0

Setting Parameters – COM0/COM1, page 117

Start address for read access

Start address for write access

COM 0 – SCB 0.1

Assignment (similar to byte 29 to 37)

COM 0 – SCB 0.7

Assignment (similar to byte 29 to 37)

COM0

…

Eth 2

Port Setup

Eth 1

Port Setup

QuickCon-

nect

Swap A/B

line

Termination

active

Biasing

active

2018/03

57

Commissioning

Byte Bit 7 Bit 6 Bit 5 Bit 4 Bit 3 Bit 2 Bit 1 Bit 0
Dec. Hex.

COM 1

Setting Parameters – COM0/COM1, page 117

108 0x6C
109 0x6D

110 0x6E
111 0x6F
112 0x70
113 0x71
114 0x72

115 0x73

116 0x74
117 0x75
118 0x76
119 0x77
120 0x78
121 0x79
122 0x7A
123 0x7B
124 0x7C
125 0x7D

126 0x7E
127 0x7F
128 0x80
129 0x81
130 0x82
131 0x83
132 0x84
133 0x85
134 0x86
135 0x87

136 to

0x88 to

145

…

196 to

0xC4 to

205

206 0xCE

…
209 0xD1
210 0xD2

…
213 0xD5
214 0xD6
215 0xD7

216 0xD8

…
226 0xE2
227 0xE3

228 0xE4

Setting Parameters – Server Configuration Block (SCB), page 121

0x91

0xCD

DXP channels, Setting Parameters – DXP Channels, page 127

- Operation mode

-

- Data rate

- Character format

- Stop bits

-EOF detection

-

-

- Power supply VAUX1

-

Character timeout

Response timeout

1st end delimiter

2nd end delimiter

MB-Server cycle time (*1ms)

COM 0 – SCB 1.0

Server address

- Number reg./server write access

- Number reg./ server read access
Read access
Write access

-

Start address for read access

Start address for write access

COM 0 – SCB 1.1

Assignment (similar to byte 29 to 37)

…

COM 0 – SCB 1.7

Assignment (similar to byte 29 to 37)

-SRO4
…

-SRO7

-EN_DO4
…

-EN_DO7

- DIF pulses (DXP4)

Pulse stretching (DXP4)

…

- DIF pulses (DXP7)

Pulse stretching (DXP7)

Termination

filter (DXP4)

filter (DXP7)

Swap A/B

line

active

Biasing

active

Eingangs-

Eingangs-

58

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

Device configuration data

Default values are marked in bold.

Parameter name Value Meaning

QuickConnect 0 =

ETH x Port Setup 0 = Autonegotiation The port is set to autonegotiation.

deactivated

1 = activated QuickConnect is activated.

1 = 100BT/FD Defined setting of communication parameters

for the Ethernet port to:

– 100BaseT
– Full duplex

2018/03

59

Commissioning

Process data instances

Process Data Mapping

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…470 bytes
default: 470 bytes

– Output data:

Output Assembly Instance: 104
0…400 bytes
default: 400 bytes

The process data mapping of the TBEN-S2-2COM-4DXP for EtherNet/IIP™ corresponds to the pro­cess data mapping described in chapter Operating. But, in EtherNet/IP™, the status and the control
word are mapped before the process data.

 The mapping of the status and the control word can be deactivated via Gateway Class (VSC

100), GW Status Word, page 70 or Gateway Class (VSC 100), GW Control word, page 70.

ATTENTION!

Activating/deactivating the status and control word in EtherNet/IP™

Changes in the process data mapping

 Observe the changes in the process data mapping if the status and control word are

activated or deactivated.

IN Word

Offset

Status
word

Input
data

OUT 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

Control
word

Output
data

0

1

0

1

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

Module status

(s. p. 136)

Process input data

(

s. p. 129)

(without function)

Process output data

(

s. p. 137)

60

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

7.4.6 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 the Turck products.

Common services

Service code

Dec. Hex.

84 0x54 no yes FWD_OPEN_CMD

78 0x4E no yes FWD_CLOSE_CMD

82 0x52 no yes UNCONNECTED_SEND_CMD

Class

Instance Service name

(Ope

ns a connection)

(Closes a connection)

2018/03

61

Commissioning

7.4.7 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 the Turck products.

Class attributes

Attr. No. Attribute name Get/ Set Type Value

Dec. Hex.

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/

Dec. Hex.

1 0x01 STATUS G DWORD Interface status (s. p. 63, Interface Sta-

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

Type Description

Set

tus

)

G DWORD Interface Capability Flag (s.

uration Capability

G/S DWORD Interface Control Flag (s.

ration Control

GSTRUCT

UINT Number of 16 bit words: 0x02

Padded
EPATH

G Structure

of:

0x20, 0xF6, 0x24, 0x01

TCP/IP Network Interface Configuration (s.

p. 64)

)

p. 64, Configu-

)

p. 63, Config-

62

NAME SERVER G UDINT 0 = no server address configured

NAME SERVER 2 UDINT 0 = no secondary server address config-

ured

DOMAIN NAME G UDINT 0 = no domain name configured

6 0x06 HOST NAME G STRING 0 = no Host Name configured (s.

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

1 = activate

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

p. 64)

Common services

Service
code

Dec. Hex.

01 0x01 yes yes Get_Attribute_All

02 0x02 no

14 0x0E yes yes Get_Attribute_Single

16 0x10 no yes Set_Attribute_Single

 Interface Status

Class Instance Service name

no Set_Attribute_All

The Status attribute indicates the status of the TCP/IP network interface.
Refer to the state diagram, Fig. 36: 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 Name Definition

0-3 Interface Configuration Sta-

tu

s

4…31 reserved

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…15 = reserved

 Configuration Capability

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

Bit Name Definition Value

0 BOOTP Client The device is capable of

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.

obtaining its net-

1

0

1

2018/03

63

Commissioning

 Configuration Control

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

Bit 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…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.

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

64

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

The mechanism allows the DHCP client to transmit its host name to the DHCP server. The DHCP

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

server then updates the DNS records on behalf of the client.

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

2018/03

65

Commissioning

7.4.8 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 the Turck products.

Class attributes

Attr. No. Attribute name Get/ Set Type Value

Dec. Hex.

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/

Dec. Hex.

1 0x01 INTERFACE

SPEED

2 0x02 INTERFACE

FLAGS

3 0x03 PHYSICAL

ADDRESS

6 0x06 INTERFACE

CONTROL

7 0x07 INTERFACE TYPE

10 0x0A INTERFACE

LABEL

Type Description

Set

G UDINT Speed in megabit per second.

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

G DWORD see

G ARRAY OF

USINT

2 WORD Allows port-wise changes of the Ethernet-

Interface flags, s. p. 66

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

settings

Interface flags

Bit Name Definition Default value

0 Link Status Indicates whether or not the Ethernet communi-

cations interface is connected to an active net­work.
0 = inactive link
1 = active link

Depends on applica­tion

66

1 Half/full duplex 0 = half duplex

1 = full duplex
If the Link Status flag is 0, the value of the Half/
Full Duplex flag is indeterminated.

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

Depends on applica­tion

Bit Name Definition Default value

2 to 4 Negotiation Status Indicates the status of the automatic

Autonegotiation
0 = autonegotiation in progress
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.

5Manual Setting

Requires Reset

6 Local Hardware Fault 0 = interface detects no local hardware fault

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

1 = local hardware error detected

Common services

Service
code

Class Instance Service name

Depends on applica­tion

0

0

Dec. Hex.

01 0x01 yes yes Get_Attribute_All

14 0x0E

76 0x4C no yes Enetlink_Get_and_Clear

yes yes Get_Attribute_Single

2018/03

67

Commissioning

7.4.9 VSC-Vendor Specific Classes

In addition to supporting the above named CIP Standard Classes, the TBEN-S2-2COM-4DXP mod­ules support the vendor specific classes described in the following.

Class Code Name Description

Dec. Hex.

100 0x64 Gateway Class, s. p. 69 Data and parameters for the field bus specific

part of the device.

139 0x8B COM Class s.

140 0x8C RS Data/SCB Class s.

141 0x8D MB-Server Timing Timing data for connected Modbus servers.

142 0x8E DXP Class Data and parameters for the DXP channels of the

164 0xA4 Ext. DXP Functions Class Parameters for the extended digital functions of

Class Instance of the 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. Attribute name Get/

Dec. Hex.

p. 72 Data and parameters for the COM ports of the

device.

p. 75 Data of the connected serial devices, data and

parameters for the connected Modbus servers.

device.

the DXP channels.

Type Description

Set

68

100 0x64 Class revision G UINT Contains the revision number of the

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

101 0x65 Max. instance G USINT Contains the number of the highest

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

102 0x66 # of instances G USINT Contains the number of Object

Instances created in this class.

103 0x67 Max. class attribute G USINT Contains the number of the last class

attribute to be implemented.

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

Gateway Class (VSC 100)

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

 Class instance

NOTE

Please refer to section Class Instance
instance for the VSC.

 Object instance 1, boot instance

of the VSCs, page 68 for the description of the class

Attr. No. Attribute name Get/

Type Description

Set

Dec. Hex.

100 0x64 Max object attribute G USINT Contains the number of the last object

attribute to be implemented.

101 0x65 Hardware revision G STRUCT Contains the hardware revision number

of the module (USINT Maj./USINT Min.).

102 0x66 Firmware revision G STRUCT Contains the revision number of the

boot firmware (Maj./Min.).

103 0x67 Service tool ident

number

104 0x68 Hardware

Info

G UDINT Contains the BOOT ID number that

serves as an identification number for
the DTM-software.

G STRUCT Contains device 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

2018/03

69

Commissioning

 Object Instance 2, gateway Instance

Attr. No. Attribute name Get/

Set

Dec. Hex.

109 0x6D Status word

(Status register 2)

G STRUCT The Status Word contains general module

Type Description

status 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 active .

– Bit 13…bit 10: reserved

Voltage errors

– Bit 09: V1 too low

(< 18 V DC).

– Bit 08: reserved
– Bit 07: V2 too low

(< 14 VDC).

– Bit 06…bit 1: reserved

Warnings

– Bit 00: Module diagnostics pending

(DIAG). At least 1 channel sends diagnos­tics.

115 0x73 ON IO

CONNECTION
TIMEOUT

138 0x8A GW Status

Word

139 0x8B GW Control word Get/

140 0x8C Disable Protocols Get/

G/S ENUM USINT Reaction to the I/O connection exceeding

Get/
set

Set

set

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

DWORD Activates or deactivates the mapping of the

status word into the device's input data.

DWORD Activates or deactivates the mapping of the

control word into the device's output data.

UINT Deactivation of the used Ethernet protocol.

Bit assignment of protocols:

Bit 0 = EtherNet/IP™ (can not be

deactivated via the EtherNet/IP™ interface)

Bit 1 = Modbus TCP

Bit 2 = PROFINET

Bit 11…bit 14 = reserved

Bit 15 = Web server

70

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

 Object instance 4, COS/CYCLIC instance

Attr. No. Attribute name Get/ Set Type Description

Dec. Hex.

104 0x68 COS data

mapping

S ENUM USINT The actual data are loaded to the non-

G/

volatile memory of the device.
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 scan­ner)
2…7: reserved

2018/03

71

Commissioning

COM Class (VSC 139)

This class contains 2 object instances, one for COM0 and one for COM1.

NOTE

The chapters Configuring and Parameterizing and Operating contain detailed informa­tion concerning parameters or process data and diagnostics.

The chapter Operating contains further information about the transmit and receive
sequence (s. p. 141).

Attr. No. Attribute name Get/

Type Description

Set

Dec. Hex.

Parameters

1 0x01 Operation mode G/S USINT Operation mode of the COM0 or COM1

channel:
0 = RS485
1 = RS232
2 = MB-Client RS485
3 = MB-Client RS232

2 0x02 Swap A/B line

tauschen

3 0x03 Data rate G/S USINT Data rate of the serial interface

G/S USINT Changes the outputs polarity of the A/B

lines and switches the bias-level.
0 = no (A = pin 2, B = pin 4)
1 = yes (A = pin 4, B = pin 2)

0…3 = reserved
4 = 2400 bps
5 = 4800 bps
6 = 9600 bps
7 = 14400 bps
8 = 19200 bps
9 = 28800 bps
10 = 38400 bps
11 = 57600 bps
12 = 115200 bps
13 = 230400 bps

72

4 0x04 Character format G/S USINT Defines the parity and the number of

bits per sign.
0 = 7O
1 = 7E
2 = 8N
3 = 8O
4 = 8E

N: no parity
O: odd parity (1 bit error detection)
E: even (1 bit error detection)

5 0x05 Stop bits G/S USINT Defines the number of stop bits.

0 = 1 bit
1 = 2 bit

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

Attr. No. Attribute name Get/

Type Description

Set

Dec. Hex.

6 0x06 EOF detection G/S USINT 0 = character timeout

1 = 1 end delimiter
2 = 2 end delimiter
3 = framelength

7 0x07 Termination active G/S USINT 0 = yes

1 = no

8 0x08 Biasing active G/S USINT 0 = yes

1 = no

9 0x09 Power supply VAUX1 G/S USINT 0 = 0 V (High-Z)

1 = V1(24 VDC)
2 = +5 VDC

10 0x0A Character timeout G/S INT Character timeout in ms

11 0x0B response timeout G/S INT Response timeout in ms

12 0x0C 1st end delimiter G/S USINT default: 3

13 0x0D 2nd end delimiter G/S USINT

Is only interpreted if the parameter "EOF
detection" is set to 1 end delimiter or 2
end delimiter.

14 0x0E MB-Server cycle time

(* 1 ms)

Diagnostics

15 0x0F Hardware error G USINT 1 = error

16 0x10

17 0x11 Overcurrent supply

18 0x12 Error MB-server 0 G USINT

19 0x13 Error MB-server 1 G USINT

20 0x14 Error MB-server 2 G USINT

21 0x15 Error MB-server 3 G USINT

22 0x16 Error MB-server 4 G USINT

23 0x17 Error MB-server 5 G USINT

24 0x18 Error MB-server 6 G USINT

25 0x19 Error MB-server 7 G USINT

Status bits

26 0x1A Transmitter ready G USINT 0 = FALSE

Parameterization error G USINT

VAUX1

G/S INT default:

0 = best update time possible

GUSINT

1 = TRUE

2018/03

27

0x1B Receive complete G USINT The bit is set to TRUE after a message

was sent. The bit remains TRUE until the
bit "Receive" is set to FALSE.

73

Commissioning

Attr. No. Attribute name Get/

Type Description

Set

Dec. Hex.

28 0x1C Frame error G USINT 1 = er8 × Baror

29 0x1D Parity/format error G USINT 1 = error

30 0x1E Buffer overflow G USINT 1 = buffer overflow during receive

sequence

31 0x1F Timeout G USINT 1 = response timeout

This bit is only used in case of a response
time set to > 0.

32 0x20 Invalid TX length G USINT 1 = error

33 0x21 Invalid RX length G USINT 1 = error

34 0x22 Received frame length G USINT This byte contains the length of the last

message received.

35 0x23 MB-Server cycle time

(* 1 ms)

36 0x24 Transmit G USINT 1 = transmit sequence started

37 0x25 Receive G USINT 1 = receive sequence started

G UINT Update time [ms] with which the Mod-

bus RTU-Client requests data from all
connected Modbus RTU-Servers.

38 0x26 Transmitter frame length G USINT Number of the characters to be send in

bytes

39 0x27 Receiver frame length G USINT Number of the characters to be received

within the next message.

74

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

RS Data/SCB Class (VSC 140)

This class contains 2 object instances, one for COM0 and one for COM1.

NOTE

The chapters Conf
tion concerning parameters or process data and diagnostics.

iguring and Parameterizing and Operating contain detailed informa-

Attr. no. Attribute

name

Dec. Hex. Value

1 0x01 Server

address

2 0x02 Number reg./

server read
access

3 0x03 Number reg./

server write
access

4 0x04 Read access G/S USINT 0 deactivated

Get/

Type Description

Set

G/S USINT 0…

255

G/S USINT 0…

12

G/S USINT 0…

12

3 read holding registers (FC3)

4 read input registers (FC4)

23 read/write multiple registers (FC23)

Address of the connected Modbus RTU Servers
or
Start address of the first connected Modbus RTU
Server
default: 0x01

Number of registers to be read
or
Number of servers from which data have to be
read

Number of registers to be written
or
Number of servers to which data have to be writ­ten

128 Write extension

151 Multi server mode: read 1 holding registers (FC3)

132 Multi server mode: read 1 input register (FC 4)

151 Multi server mode: read/write 1 register (FC 23)

163 Multi server mode: read 2 holding registers (FC3)

164 Multi server mode: read 2 input register (FC 4)

183 Multi server mode: read/write 2 register (FC 23)

195 Multi server mode: read 3 holding registers (FC3)

4 0x04 Read access G/S USINT 196 Multi server mode: read 3 input register (FC 4)

215 Multi server mode: read/write 3 register (FC 23)

227 Multi server mode: read 4 holding registers (FC3)

228 Multi server mode: read 4 input register (FC 4)

247 Multi server mode: read/write 4 register (FC 23)

2018/03

75

Commissioning

Attr. no. Attribute

name

Dec. Hex. Value

5 0x05 Write access G/S USINT 0 deactivated

Get/

Type Description

Set

6 write single register (FC6)

16 write multiple registers (FC16)

23 read/write multiple registers (FC23)

128 write extension

134 Multi server mode: write single register (FC6)

144 Multi server mode: write 1 registers (FC16)

151 Multi server mode: read/write 1 register (FC 23)

176 Multi server mode: write 2 registers (FC16)

183 Multi server mode: read/write 2 register (FC 23)

208 Multi server mode: write 3 registers (FC16)

215 Multi server mode: read/write 3 register (FC 23)

240 Multi server mode: write 4 registers (FC16)

6 0x06 Start address

for Read
access

7 0x07 Start address

for Write
access

G/S UINT 0…

G/S UINT 0…

247 Multi server mode: read/write 4 register (FC 23)

Address of the 1st register from which data have

65535

65535

to be read

Address of the 1st register to which data have to
be written

76

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

Attr. no. Attribute

name

Dec. Hex. Value

Get/

Type Description

Set

8 0x08 Input register

0

9 0x09 Input register

1

10 0x0A Input register

2

11 0x0B Input register

3

12 0x0C Input register

4

13 0x0D Input register

5

14 0x0E Input register

6

15 0x0F Input register

7

16 0x10 Input register

8

17 0x11 Input register

9

G UINT Input data of the connected serial device (s. p. 131) or the

Modbus-Server, 1 or 12 register(s) per server (s. p. 135).

18 0x12 Input register

10

19 0x13 Input register

11

20 0x14 Output regis-

ter 0

21 0x15 Output regis-

ter 1

22 0x16 Output regis-

ter 2

23 0x17 Output regis-

ter 3

24 0x18 Output regis-

ter 4

25 0x19 Output regis-

ter 5

26 0x1A Output regis-

ter 6

27 0x1B Output regis-

ter 7

G UINT Output data of the connected serial device (s.

p. 139) or

the Modbus-Server, 1 or 12 register(s) per server (s. p.

140

).

2018/03

77

Commissioning

Attr. no. Attribute

name

Dec. Hex. Value

28 0x1C Output regis-

ter 8

29 0x1D Output regis-

ter 9

30 0x1E Output regis-

ter 10

31 0x1F Output regis-

ter 11

MB-Server Timing Class (VSC 141)

NOTE

The chapter Operating contains more detailed information concerning the process data.

Attr. no.

dec.
(hex.)

Attribute name Get/ Set Type Description

Get/

Type Description

Set

GUINT

1 (0x01) COM0 – MB-Server Timing,

server 0

2 (0x02) COM1 – MB-Server Timing,

server 0

3 (0x03) COM0 – MB-Server Timing,

server 1

4 (0x04) COM1 – MB-Server Timing,

server 1

……

15 (0x0F) COM0 – MB-Server Timing,

server 7

16 (0x010) COM1 – MB-Server Timing,

server 7

G UINT Update time [ms] of the connected

Modbus RTU-Servers at COM0 or
COM1.

GUINT

GUINT

GUINT

GUINT

GUINT

78

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

DXP Class (VSC 142)

NOTE

The chapters Conf
tion concerning parameters or process data and diagnostics.

Attr. no. Attribute name Get/ Set Type Description

Dec. Hex.

Parame­ters

1 0x01 DXP4 – Manual reset after overcurr. G/S USINT 0 = no

2 0x02 DXP5 – Manual reset after overcurr. G/S USINT 0 = no

3 0x03 DXP6 – Manual reset after overcurr. G/S USINT 0 = no

4 0x04 DXP7 – Manual reset after overcurr. G/S USINT 0 = no

5 0x05 DXP4 – Activate output G/S USINT 0 = no

iguring and Parameterizing and Operating contain detailed informa-

1 = yes

1 = yes

1 = yes

1 = yes

1 = yes

6 0x06 DXP5 – Activate output G/S USINT 0 = no

1 = yes

7 0x07 DXP6 – Activate output G/S USINT 0 = no

1 = yes

8 0x08 DXP7 – Activate output G/S USINT 0 = no

1 = yes

Status

9 0x09 Overcurrent VAUX2 Ch4/Ch5 G USINT Overcurrent at the

10 0x0A Overcurrent VAUX2 Ch6/Ch7 G USINT

11 0x0B DXP4 – overcurrent output G USINT

12 0x0C DXP5 – overcurrent output G USINT

13 0x0D DXP6 – overcurrent output G USINT

14 0x0E DXP7 – overcurrent output G USINT

15 0x0F DXP4 – Input value G USINT 1 = input signal at

16 0x10 DXP5 – Input value G USINT

17 0x11 DXP6 – Input value G USINT

supply voltage at C2
(channel 4/5) or C3
(channel 6/7)

DXP channel

2018/03

18 0x12 DXP7 – Input value G USINT

19 0x13 Output value G BYTE 0 = DXP4

1 = DXP5
2 = DXP6
3 = DXP7

79

Commissioning

7.4.10 Extended DXP Functions Class (VSC 164)

This class provides four instances, one per DXP-channel.

NOTE

The chapter Configuring and Parameterizing contains more detailed information con­cerning the parameters.

Attr. no. Attribute name Get/

Type Description

Set

Dec. Hex.

1 0x01 Extended

digital function

2 0x02 Input filter G/S USINT 0 = 0,2 ms

3 0x03 Impulse stretch

(* 10 ms)

G/S USINT 0 = deactivated

1 = input filter and pulse stretch

1 = 3 ms

G/S USINT 0…254

80

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

7.5 Connecting the device to an EtherNet/IP™ PLC

7.5.1 Used Hardware

The following hardware components are used in this example:

 Rockwell PLC ControlLogix 1756-L72

 Rockwell Scanner 1756-EN2TR

 Block module TBEN-S2-2COM-4DXP

 8 × Banner K50TGRYS1QP at COM 0 as Modbus server

7.5.2 Used Software

The following software tools are used in this example:

 Rockwell RS Logix

 EDS file for TBEN-S2-2COM-4DXP (can be downloaded for free under ww.turck.com).

7.5.3 Prerequisites

 The programming software has been started.

 A new project has been created with the PLC and the Scanner mentioned above.

 The PLC has been added to the project.

2018/03

81

Commissioning

7.5.4 Installing the EDS-file

The EDS-file can be downloaded for free from www.turck.com .

Adding the EDS-file: Click "Tools"  "EDS Hardware Installation Tool”

Fig. 37: Opening the "EDS Hardware Installation Tool”

 The installation assistant guides you through the installation process.

82

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

7.5.5 Connecting the device to the PLC

 Right-click "I/O Configuration"  "Ethernet".

 Select "New Module"

Fig. 38: Adding a new module

 Select Turck under "Module Type Vendor Files".

 Select TBEN-S2-2COM-4DXP.

2018/03

83

Commissioning

 Confirm the selection with "Create".

Fig. 39: Select TBEN-S2-2COM-4DXP.

 Assign a module name.

 Set the IP address of the device (example: 192.168.1.10).

84

Fig. 40: Setting module name and IP address

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

 Set the Integer data format for in- and output data: Click "Change". 

in the following dialog box select "INT".

Fig. 41: Setting the Integer data format for in- and output data

2018/03

85

Commissioning

 Optional: Setting the connection and the port configuration.

Fig. 42: Setting the connection parameters

86

Fig. 43: Setting the port configuration

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

 The device is added to the project tree.

Fig. 44: TBEN-S2-2COM-4DXP in the project tree

2018/03

87

Commissioning

7.5.6 Going online with the PLC

 Scan the network via the "who active"-button, select the PLC and set the communication path

via "Set Project Path".

Fig. 45: Setting the communication path

 The communication path is set

88

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

 Select the PLC.

 Click "Go online".

Fig. 46: Going online with the device

 Click "Download" In the following dialog (Connect To Go Online).

2018/03

Fig. 47: Clicking "Download"

 Confirm all following messages.

89

Commissioning

7.5.7 Reading Process Data

 Open the "Controller Tags" in the project tree by double-clicking the entry.

Fig. 48: "Controller Tags" in the project tree

 The access to the parameter data (TBEN_S2_2COM_4DXP:C), input data

(TBEN_S2_2COM_4DXP:I1) and output data (TBEN_S2_2COM_4DXP:O1) is possible.

Example: Process input data – input signal at Modbus-Server 1 (COM0)

90

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

In the following example an input signal at Modbus-Server 1 (COM0) is pending. The process data
can be interpreted by means of the mapping (s. p. 60).

Fig. 49: Process input data – example

2018/03

91

Commissioning

7.5.8 Parameterizing Devices via Class Instance Attribute

Prerequisites

 the software tool "RS_NetWorks for Ethernet/IP" runs.

Scanning the Network and Setting the Communication Path

 Scan the network using the "Online" button.

Fig. 50: RS NetWorks – scanning the network

92

Fig. 51: RS NetWorks – setting the communication path

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

 Right-click the TBEN-S2-2COM-4DXP and click "Class Instance Editor".

Fig. 52: RS NetWorks – opening the "Class Instance Editor"

 Confirm the following dialog with "yes".

 The Class Instance Editor is started.

Example: Parameterizing COM0 as "MB-Client RS485"

The description of the vendor specific classes can be found in chapter 7.4.9, VSC-Vendor Specific

Classes.

Parameters for the example parameterization:

 Class: COM Class 139 (0x8B)

 Instance: 1 (for COM0)

 Attribute: 0x01 = Operation mode

 Value (data): 02 = MB Client 485

 Select "Set Single Attribute" under "Service Code" for parameterizing

 Define the parameter under "Object Address" by means of "Class – Instance – Attribute".

2018/03

93

Commissioning

 Enter the value to be written in "Data sent to the device" and confirm the setting with "Execute".

Fig. 53: RS NetWorks – parameterization via Class Instance Editor

 The COM port COM0 is now set to "MB Client 485".

NOTE

Besides the parameterization using vendor specific classes (VSC) in RS NetWorks, the DTM
or the device internal web server are alternative options for parameterizing the devices
(example s. p. 109).

94

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