turck TBEN-L5-4RFID-8DXP-CDS User manual

Your Global Automation Partner
Instructions for Use
TBEN-L…-4RFID-8DXP-
CDS…
Compact RFID Interface

2Hans Turck GmbH & Co. KG | T [phone] | F [phone] | [email protected] | www.turck.com

V02.00 | 2018/08 3
Contents
1 About these Instructions 7
1.1 Target groups 7
1.2 Explanation of symbols used 7
1.3 Other documents 7
1.4 Feedback about these instructions 7
2 Notes on the Product 8
2.1 Product identification 8
2.2 Scope of delivery 8
2.3 Legal requirements 8
2.4 Manufacturer and Service 8
3 For Your Safety 9
3.1 Intended use 9
3.2 General safety notes 9
4 Product Description 10
4.1 Device overview 10
4.1.1 Indication elements 10
4.1.2 Operating elements 10
4.2 Properties and features 11
4.3 Operating principle 11
4.4 Functions and operating modes 12
4.4.1 Multiprotocol function 12
4.4.2 Data transfer to the PLC 12
4.4.3 RFID channels – Operating modes 13
4.4.4 RFID commands 15
4.4.5 Loop counter function 15
4.4.6 Configurable digital channels – Functions 16
4.4.7 USB host port 16
4.4.8 USB device port 16
4.4.9 Compatible CODESYS versions 16
4.5 Technical Accessories 16
5 Mounting 17
5.1 Grounding the device 18
5.1.1 Grounding and shielding concept 18
5.1.2 Grounding the device (FG) 19
6 Connection 20
6.1 Connecting modules to Ethernet 20
6.2 Connecting the power supply 21
6.3 Connecting RFID read/write heads 22
6.4 Connecting digital sensors and actuators 23
7 Commissioning 24
7.1 Setting the IP address 24
7.1.1 Setting the IP address via switches on the device 24
7.1.2 Setting the IP address via the Turck Service Tool 26
7.1.3 Setting the IP address via the web server 28
7.2 Connecting the device to a Modbus master 29

Contents
4Hans Turck GmbH & Co. KG | T [phone] | F [phone] | [email protected] | www.turck.com
7.2.1 Connecting the device with the controller 30
7.2.2 Renaming a Modbus slave 34
7.2.3 Setting up network interfaces 35
7.2.4 Setting Modbus channels (registers) 37
7.2.5 Setting the I/O mapping 39
7.2.6 Writing the application to the device 45
7.2.7 Connecting the device online with the controller 51
7.2.8 Reading out process data 51
7.3 Connecting a device to an EtherNet/IP™ controller 52
7.3.1 Configuring the device in CODESYS as an EtherNet/IP™ slave 53
7.3.2 Setting up the network interface 61
7.3.3 Installing an EDS file 65
7.3.4 Connecting the device with the controller 69
7.3.5 Reading out process data 72
7.4 Connecting a device to a Siemens controller 73
7.4.1 Configuring the device in CODESYS as a PROFINET device 74
7.4.2 Setting up the network interface 82
7.4.3 Connecting a device to a Siemens controller in the TIA Portal 86
7.4.4 Reading out process data 92
7.5 Starting the device as the Modbus master 93
7.5.1 Setting up the network interface 99
7.5.2 Setting Modbus channels (registers) 103
7.5.3 Reading out process data 105
8 Setting 106
8.1 RFID channels – Setting parameter data 108
8.1.1 Meaning of the parameter bits 109
8.1.2 HF applications – Selecting the tag type 111
8.1.3 HF applications – Setting the bridging time 113
8.1.4 HF applications – Setting Continuous mode 114
8.1.5 HF applications – Setting HF bus mode 115
8.1.6 UHF applications – Setting Continuous presence sensing mode 120
8.1.7 UHF applications – Transferring read/write head settings 120
8.2 RFID channels – Evaluating process input data 121
8.2.1 Meaning of the status bits 124
8.2.2 Using “Tag in detection range” bit (TP) or "pre-loading" the command 125
8.3 RFID channels – Writing process output data 126
8.3.1 Meaning of the command bits 129
8.4 Digital channels – Setting parameter data 131
8.4.1 Meaning of the parameter bits 131
8.5 Digital channels – Evaluating process input data 132
8.5.1 Meaning of the status bits 132
8.6 Digital channels – Writing process output data 133
8.6.1 Meaning of the command bits 133
8.7 Digital channels – Setting switchable VAUX power supply 134
8.7.1 VAUX switchable power supply – Parameter data 134
8.7.2 VAUX switchable power supply – Output data 135
8.8 RFID channels – Overview of commands 136
8.8.1 Idle command 138
8.8.2 Inventory command 139
8.8.3 Read command 142
8.8.4 Write command 143
8.8.5 Write and verify command 145

V02.00 | 2018/08 5
8.8.6 Continuous mode 147
8.8.7 “Get data from buffer” command (Continuous mode/“Continuous presence sensing
mode”) 149
8.8.8 “Continuous presence sensing mode” command (UHF) 152
8.8.9 “Stop continuous (presence sensing) mode” command 153
8.8.10 Read/write head identification command 154
8.8.11 Switch off HF read/ command 155
8.8.12 Tune read/write head command 156
8.8.13 “Get HF read/write head address” command 157
8.8.14 “Set HF read/write head address” command 158
8.8.15 Direct read/write head command 159
8.8.16 Set tag password command 164
8.8.17 Set read/write head password command 166
8.8.18 Reset read/write head password command 167
8.8.19 Set tag protection command 168
8.8.20 Get HF tag protection status command 170
8.8.21 Set perma lock command 172
8.8.22 Tag info command 174
8.8.23 Kill UHF tag 176
8.8.24 Restore settings UHF read/write head command 177
8.8.25 Backup settings UHF read/write head command 178
8.8.26 “Get UHF read/write head error/status” command 179
8.8.27 Reset command 182
8.9 Setting RFID interfaces via the web server 183
8.9.1 Opening a web server 183
8.9.2 Editing settings in the web server 184
8.10 Testing and parameterizing RFID interfaces via the DTM 190
8.10.1 Connecting the device with the PC 190
8.10.2 Editing parameter data with the DTM – Online parameterization 193
8.10.3 Reading process input data with the DTM – Measured value 194
8.10.4 Changing process output data with the DTM – Simulation 195
8.10.5 Evaluating diagnostics with the DTM 196
8.10.6 Example: Executing a read command with the DTM 197
8.11 Setting UHF read/write heads 199
8.12 Opening WebVisu 199
8.13 Using SFTP access 200
9 Operation 201
9.1 Executing a command and calling data 201
9.1.1 Typical times for command processing 201
9.2 Using fragmentation 203
9.3 Using commands with a loop counter function 203
9.4 Using NEXT mode 204
9.4.1 Example: Using NEXT mode for a read command 204
9.5 Using Inventory command and Continuous (presence sensing) mode 205
9.6 Executing commands in HF bus mode 205
9.7 LEDs 206
9.8 Software diagnostic messages 208
9.8.1 Diagnostic messages – Gateway functions 208
9.8.2 Diagnostic messages – RFID channels 208
9.8.3 Diagnostic messages – Digital channels 209
9.8.4 Diagnostic messages – Module status 209
9.9 Reading error codes 210

Contents
6Hans Turck GmbH & Co. KG | T [phone] | F [phone] | [email protected] | www.turck.com
9.10 Using the USB Host port 216
9.10.1 USB Host port – Function overview 217
9.10.2 Executing USB functions 219
9.10.3 USB functions – Behavior of the RUN LED in the event of an error 220
9.11 Reset device (Reset) 220
10 Troubleshooting 221
11 Maintenance 222
11.1 Executing the firmware update via FDT/DTM 222
11.2 Executing the firmware update via the USB interface 226
12 Repair 227
12.1 Returning devices 227
13 Disposal 227
14 Technical Data 228
15 Appendix: Flow charts showing the operation of the device 231
15.1 Flow chart: Command processing 231
15.2 Flow chart: Rapid command processing with loop counter 232
15.3 Flow chart: Command processing with fragmentation 233
15.4 Flow chart: Continuous mode with interruption before reading data 234
15.5 Flow chart: Continuous mode without interruption before reading data 235
16 Appendix: EU conformity declaration 236

V02.00 | 2018/08 7
1 About these Instructions
These operating instructions describe the structure, functions and the use of the product and
will help you to operate the product as intended. Read these instructions carefully before using
the product. This is to avoid possible damage to persons, property or the device. Retain the in-
structions for future use during the service life of the product. If the product is passed on, pass
on these instructions as well.
1.1 Target groups
This document is written for specially trained personnel , and must be read carefully by anyone
who is responsible for the mounting, commissioning, operation, maintenance, disassembly or
disposal of the device.
1.2 Explanation of symbols used
The following symbols are used in these instructions:
DANGER
DANGER indicates a dangerous situation with high risk of death or severe injury if
not avoided.
WARNING
WARNING indicates a dangerous situation with medium risk of death or severe in-
jury if not avoided.
CAUTION
CAUTION indicates a dangerous situation of medium risk which may result in minor
or moderate injury if not avoided.
NOTICE
NOTICE indicates a situation which may lead to property damage if not avoided.
NOTE
NOTE indicates tips, recommendations and useful information on specific actions
and facts. The notes simplify your work and help you to avoid additional work.
uCALL TO ACTION
This symbol denotes actions that the user must carry out.
aRESULTS OF ACTION
This symbol denotes relevant results of actions.
1.3 Other documents
Besides this document the following material can be found on the Internet at www.turck.com:
nData sheet
nOperating instructions
nDeclaration of Conformity
1.4 Feedback about these instructions
We make every effort to ensure that these instructions are as informative and as clear as pos-
sible. If you have any suggestions for improving the design or if some information is missing in
the document, please send your suggestions to [email protected].

Notes on the Product
8Hans Turck GmbH & Co. KG | T [phone] | F [phone] | [email protected] | www.turck.com
2 Notes on the Product
2.1 Product identification
These instructions apply to the following compact RFID interfaces:
nTBEN-L4-4RFID-8DXP-CDS
nTBEN-L5-4RFID-8DXP-CDS
nTBEN-L4-4RFID-8DXP-CDS-WV
nTBEN-L5-4RFID-8DXP-CDS-WV
2.2 Scope of delivery
nCompact RFID interface
nClosure caps for M12 connectors
2.3 Legal requirements
The device is subject to the following EC directives:
n2014/30/EU (electromagnetic compatibility)
n2011/65/EU (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 applic-
ation. The Turck product database contains software tools for programming, configuration or
commissioning, data sheets and CAD files in numerous export formats. You can access the
product database at the following address: www.turck.de/produkte
For further inquiries in Germany contact the Sales and Service Team on:
nSales: [phone]
nTechnology: [phone]
Outside Germany, please contact your local Turck representative.

V02.00 | 2018/08 9
3 For Your Safety
The product is designed according to state-of-the-art technology. However, residual risks still
exist. Observe the following warnings and safety notices to prevent damage to persons and
property. Turck accepts no liability for damage caused by failure to observe these warning and
safety notices.
3.1 Intended use
These devices are designed solely for use in industrial areas.
The TBEN-L…-4RFID-8DXP-CDS block module is an RFID interface for use in the Turck RFID sys-
tem. The device is connected between the controller and the read/write head and transmits
commands from the controller to the read/write heads. Read data is sent to the controller via
the device. The device can take over autonomous controller and diagnostic functions in order
to relieve the load on the controller. The device functions can be programmed in accordance
with IEC 61131- 3 using CODESYS V3.
The multiprotocol interfaces can be used as an EtherNet/IP™ device, Modbus TCP Turck slave,
or PROFINET RT device. In Modbus TCP systems the devices can also be used as masters.
The devices support the HF read/write heads from firmware version Vx.90 and UHF read/write
heads from firmware version FW 1.45.
In normal operation, up to four BL ident® read/write heads can be connected to the device. In
Bus mode it is possible to connect up to 32 HF read/write heads per channel for static applica-
tions. Eight configurable digital channels are also provided.
The devices may only be used as described in these instructions. Any other use is not in accord-
ance with the intended use; Turck accepts no liability for any resulting damage.
3.2 General safety notes
nThe device may only be assembled, installed, operated, parameterized and maintained by
professionally-trained personnel.
nThe device may only be used in accordance with applicable national and international regu-
lations, standards and laws.
nThe device only meets the EMC requirements for industrial areas and is not suitable for use
in residential areas.

Product Description
10 Hans Turck GmbH & Co. KG | T [phone] | F [phone] | [email protected] | www.turck.com
4 Product Description
The devices are designed with a fully encapsulated housing with degree of protection IP67/
IP69K. Four RFID channels are provided for connecting read/write heads. It is also possible to
connect sensors and actuators via eight digital I/O channels, which can be configured as inputs
or outputs as required. The terminals for the read/write heads and for digital I/Os are M12 sock-
ets. An M12 socket is provided for the Ethernet connection. The plug connectors are 4-pin
(TBEN-L4) or 5-pin (TBEN-L5) 7/8” female connectors.
The TBEN-L…-4RFID-8DXP-WV block modules are supplied with a complete WebVisu license.
4.1 Device overview
218
230.5
C4C5C6C7
6.3
38.8
60.4
C0C1C2C3
24
30.2
X2
X1
P2
P1
Fig.1: Dimensions
4.1.1 Indication elements
The devices are provided with multi-color LEDs for displaying information:
nPower supply
nGroup and bus errors
nStatus
nDiagnostics
4.1.2 Operating elements
The devices are provided with the following operating elements:
nRotary coding switches and DIP switch for setting the IP address
nSET button for activating the write accesses of the USB Host port functions

V02.00 | 2018/08 11
4.2 Properties and features
nGlass fiber reinforced housing
nShock and vibration tested
nFully encapsulated module electronics
nDegree of protection IP65/IP67/IP69K
nMultiprotocol: EtherNet/IP™ device, Modbus TCP slave or PROFINET device
nUp to 128 bytes of user data per read/write cycle per channel as well as use of fragments for
larger data volumes
nData interface for convenient use of the RFID functions
n4 or 5-pin 7/8” plug connector for the power supply
nTwo 4-pin M12 terminals for Ethernet
nFour channels with an M12 terminal for RFID
nMixed operation of HF and UHF read/write heads
nEight digital channels can be configured as 2 A pnp inputs or outputs
nIntegrated Ethernet switch enables line topology
n10 Mbps/100 Mbps transfer rate
nIntegrated web server
nLEDs and diagnostics
4.3 Operating principle
When used as slaves, the RFID interfaces connect the RFID system with the higher-level control-
ler system. The interfaces are provided with a fieldbus interface and fieldbus-independent I/O
electronics with an RFID interface. The interfaces can also process signals of sensors and actuat-
ors via eight configurable digital channels. The interfaces are provided with a multiprotocol
fieldbus interface for Modbus TCP, EtherNet/IP™ and PROFINET. The fieldbus interface connects
the interface to an (existing) fieldbus system as an EtherNet/IP™ device, Modbus TCP slave or
PROFINET device. During operation, the process data is exchanged between the fieldbus and
RFID system. The read/write heads are connected to the interfaces via the RFID interfaces.
When used as Modbus TCP master, the RFID interfaces connect the RFID system with other sys-
tems communicating via TCP/IP. The interfaces are provide with an Ethernet interface and RFID
interfaces.
The RFID system can be linked via the TCP/IP interface to a third-party system, such as an ERP
system. The read/write heads are connected to the interfaces via the RFID interfaces. The inter-
faces can also process signals of sensors and actuators via eight configurable digital channels.

Product Description
12 Hans Turck GmbH & Co. KG | T [phone] | F [phone] | [email protected] | www.turck.com
4.4 Functions and operating modes
The compact RFID interfaces transfer the data between the RFID level (read/write head and tag)
and the controller level. HF and UHF read/write heads can be connected to the RFID channels.
Parallel operation of HF and UHF read/write heads on the same device is also possible.
The devices can be used as an EtherNet/IP™ device, Modbus TCP Turck slave, or PROFINET RT
device. The devices can also be used as masters in the Modbus TCP fieldbus system.
The device enables the execution of different commands such as inventory (single-tag and
multitag applications), read, write and password protection. Additional functions are provided
for optimizing the speed, the self triggering of the system, as well as for backup and restore op-
erations. In every write or read cycle, up to 128 bytes can be transferred on each channel to the
controller. The data must be fragmented in order to transfer more than 128 bytes.
Sensors and actuators can be connected to the configurable digital channels. Up to eight 3-
wire PNP sensors or four PNP DC actuators with a maximum output current of 2 A can be con-
nected per output.
The device can take over autonomous controller and diagnostic functions in order to relieve
the load on the controller. The devices can be programmed using the IEC61131-3 compliant
CODESYS 3 programming software.
The TBEN-L…4RFID- 8DXP-CDS-WV block modules are provided with a complete WebVisu li-
cense.
4.4.1 Multiprotocol function
The I/O modules combine three Ethernet protocols in a single device:
nModbus TCP
nEtherNet/IP™
nPROFINET
The Ethernet protocol used must be selected in the CODESYS project.
Manual protocol selection
The protocol must be defined manually in the CODESYS program. The other protocols only al-
low read access to the device. Manual protocol selection thus also provides an additional per-
manent locking feature.
4.4.2 Data transfer to the PLC
In every write or read cycle, up to 128 bytes can be transferred on each channel. The data must
be fragmented in order to transfer more than 128 bytes. The amount of data transferred per
read or write cycle can be set as follows for different Ethernet protocols:
PROFINET EtherNet/IP™ Modbus TCP
n8 bytes
n16 bytes (default setting)
n32 bytes
n64 bytes
n128 bytes
n16 bytes
n64 bytes
n128 bytes (default setting)
n128 bytes (permanently set)
Adjustable fragment size:
n8 bytes
n16 bytes (default setting)
n32 bytes
n64 bytes
n128 bytes

V02.00 | 2018/08 13
4.4.3 RFID channels – Operating modes
Five different data interfaces can be selected for the RFID channels:
nHF compact
nHF extended
nHF bus mode
nUHF compact
nUHF extended
Different functions are available to the user, depending on the selected data interface.
HF compact mode
HF compact mode is suitable for transferring smaller data volumes of up to 128bytes (e.g. UID)
in single-tag applications.
HF extended mode
HF extended mode contains all the functions provided in HF compact mode. It is also possible
to transfer more than 128 bytes by fragmenting the data. The operating mode is suitable for
single-tag and multitag applications.
NOTE
Not all commands are supported in Multitag mode.
The user can set a command timeout to define the time for the execution of a command.
“HF extended” mode enables the use of Continuous mode for the repeated execution of an in-
ventory, tag info, read or write command. In Continuous mode the read/write head executes
the commands autonomously. Different data is stored in the internal memory of the interface.
The memory operates as a FIFO memory.

Product Description
14 Hans Turck GmbH & Co. KG | T [phone] | F [phone] | [email protected] | www.turck.com
HF bus mode
In HF bus mode up to 32 bus-capable read/write heads per RFID channel can be connected to
the TBEN module. Depending on the number of connected read/write heads, an addition
power supply may be required. A power consumption analysis of the connected read/write
heads is required in order to determine the additional power supply required. Every connected
read/write head supplies a “Tag present” signal in HF bus mode. The HF bus mode can be used
for static applications because a command can only be processed by one read/write head at a
time.
TBEN-L…-4RFID-8DXP-…
VT2-FKM5-FKM5-FSM5
RFID connection cable
(e.g. RK4.5T-0.3-RS4.5T/S2503)
TN-M18-H1147/C53
TN-CK40-H1147/C53
TN-M30-H1147/C53
up to 32 per port
Fig.2: HF bus mode setup
The following read/write heads can be used for HF bus mode:
nTN-M18-H1147/C53
nTB-M18-H1147/C53
nTN-M30-H1147/C53
nTB-M30-H1147/C53
nTN-CK40-H1147/C53
nTNSLR-Q42TWD-H1147/C53
nTB-Q08-0.15-RS4.47T/C53
nTB-Q08-0.15-RS4.47T/C53
nTN-Q14-0.15-RS4.47T/C53
nTNSLR-Q80WD-H1147/C53
HF bus mode supports the HF read/write heads from firmware version Vx.90.
UHF compact mode
UHF compact mode enables up to 128 bytes of data to be transferred in single-tag applications
(e.g. EPC).

V02.00 | 2018/08 15
UHF extended mode
UHF extended mode contains all the functions provided in UHF compact mode. It is also pos-
sible to transfer more than 128 bytes. The operating mode is suitable for single-tag and multi-
tag applications. The user can set a command timeout to define the time for the execution of a
command.
UHF extended mode enables the use of presence sensing mode for the repeated execution of
an inventory, read or write command. In Presence sensing mode the read/write heads are auto-
matically switched on or off and also carry out commands automatically. In this case, the read
data is stored in the internal memory of the interface. The memory operates as a FIFO memory.
4.4.4 RFID commands
The device can perform the following commands and functions. A complete description of the
commands is provided in the section “Setting”.
nIdle
nInventory
nRead
nWrite
nWrite and verify
nContinuous mode
nGet data from buffer (Continuous mode)
nContinuous presence sensing mode (UHF)
nEnd Continuous (presence sensing) mode
nRead/write head identification
nHF read/write head off
nTune HF read/write head
nQuery HF read/write head address
nSet HF read/write head address
nDirect read/write head command
nSet tag password
nSet read/write head password
nReset read/write head password
nSet tag protection
nGet HF tag protection status
nSet perma lock
nTag info
nKill UHF tag
nRestore settings of the UHF read/write head
nBackup settings of the UHF read/write head
nQuery error/status of UHF read/write head
nReset
4.4.5 Loop counter function
The loop counter function is provided for rapid command processing. The loop counter func-
tion only requires two PLC cycles to execute a command repeatedly (flow chart see p. [}232]).
This increments the loop counter to execute a command repeatedly. At least four PLC cycles
are required in conventional command processing. In order to execute a command repeatedly
with conventional command processing, a command has to be reset and then set again. The
loop counter function is provided for special commands. If the command was successfully ex-
ecuted, the command code is output in the response data.

Product Description
16 Hans Turck GmbH & Co. KG | T [phone] | F [phone] | [email protected] | www.turck.com
4.4.6 Configurable digital channels – Functions
The device is provided with eight digital channels, which can be configured as inputs or out-
puts according to the application requirements. Up to eight 3-wire PNP sensors or eight PNP
DC actuators with a maximum output current of 2 A can be connected per input or output.
4.4.7 USB host port
The device is provided with a USB host port for connecting USB memory sticks. The USB host
port is a USB2.0 A socket. The USB functions enable CODESYS applications and user data to be
saved, restored and transferred. The firmware of the devices can also be updated via the USB
interface. Memory expansion via the USB host port is not possible.
4.4.8 USB device port
The device is provided with a USB device port for connecting USB cables. The USB device port is
designed as a mini USB-B socket. The USB device port can be used as a service interface for the
device DTM or as a programming interface. The use of the USB device port requires an RNDIS
driver. This is automatically installed with the installation of the DTM.
4.4.9 Compatible CODESYS versions
The device is compatible with the following CODESYS versions:
CODESYS
programming environ-
ment
CODESYS
runtime
Firmware
update
CODESYS
package
3.5.8.10 3.5.8.10 1.0.1.0 1.0.1.0
3.5.12.10 3.5.11.20 1.1.4.0 1.1.4.0
4.5 Technical Accessories
Accessories for mounting, connecting and parameterizing can be found in product database or
the Accessories List for TBEN (D301367) under www.turck.com. The accessories are not part of
the scope of delivery.

V02.00 | 2018/08 17
5 Mounting
Fasten the devices on a level, pre-drilled and grounded mounting surface.
Fasten the module on the mounting surface with the two M6 screws. The maximum
tightening torque for fastening the screws is 1.5Nm.
218 [5.58]
M6 (2x)
max. 1.5 Nm
Fig.3: Fixing a device on a mounting plate

Mounting
18 Hans Turck GmbH & Co. KG | T [phone] | F [phone] | [email protected] | www.turck.com
5.1 Grounding the device
5.1.1 Grounding and shielding concept
The grounding and shielding concept of the TBEN-S modules enables the separate grounding
of the fieldbus and I/O sections.
1 nF
2,2 MΩ
X1
C0
C1
C2
C3
P1
X2
C4
C5
C6
C7
P2
4 x 15 nF
Fig.4: Equivalent circuit, shielding concept
1
2
3
Fig.5: Grounding components
The grounding clip (1) on the M12 plug connectors for the fieldbus connection (P1, P2) con-
nects the shield of the fieldbus cables. The metal ring (2) is fitted underneath the grounding
strip and connects the functional ground of the 7/8” plug connectors (Pin 3) for the power sup-
ply with the functional ground of the M12 plug connectors (Pin 5) for connecting the read/
write heads, sensors and actuators. A metal screw (3) connects the device with the reference
potential of the system.

V02.00 | 2018/08 19
5.1.2 Grounding the device (FG)
Grounding strip and metal ring are connected to each other. A fixing screw through the bottom
mounting hole of the module connects the shield of the fieldbus cables with the functional
ground of the power supply and connected devices as well as the reference potential of the
system. If a common reference potential is not required, remove the grounding clip to discon-
nect the fieldbus shield or fasten the module with a plastic screw.
Removing the grounding clip
Lever up the grounding strip with a flat slot-head screwdriver and remove.
Fig.6: Removing the grounding clip
Mounting the grounding clip
Use a screwdriver to insert the grounding clip between the fieldbus connectors so that
contact is made with the metal housing of the plug connectors.
aThe shield of the fieldbus cables is connected to the grounding clip.
Fig.7: Mounting the grounding clip

Connection
20 Hans Turck GmbH & Co. KG | T [phone] | F [phone] | [email protected] | www.turck.com
6 Connection
6.1 Connecting modules to Ethernet
The device is provided with an integrated autocrossing switch with two 4-pin M12 Ethernet
plug connectors for connecting to an Ethernet system. The maximum tightening torque is
0.6Nm.
Fig.8: M12 Ethernet plug connectors for connecting the fieldbus
Connect the device to the fieldbus according to the pin layout below.
v
4
13
2
P1, P2
1 = TX +
2 = RX +
3 = TX –
4 = RX –
ange = FE
Fig.9: Pin layout of the Ethernet connections