0% found this document useful (0 votes)

303 views232 pages

RFID

Uploaded by

cuonghuynhjr

We take content rights seriously. If you suspect this is your content, claim it here.

Available Formats

Download as PDF, TXT or read online on Scribd

0% found this document useful (0 votes)

303 views232 pages

RFID

Uploaded by

cuonghuynhjr

We take content rights seriously. If you suspect this is your content, claim it here.

Available Formats

Download as PDF, TXT or read online on Scribd

You are on page 1/ 232

Your Global Automation Partner

TBEN-S2-2RFID-4DXP
Compact RFID Interface
Instructions for Use
2 Hans Turck GmbH & Co. KG | T +49 208 4952-0 | F +49 208 4952-264 | [email protected] | www.turck.com
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 Display elements............................................................................................................................ 10
4.2 Properties and features................................................................................................ 10
4.3 Operating principle....................................................................................................... 11
4.4 Functions and operating modes ................................................................................ 11
4.4.1 Multiprotocol technology........................................................................................................... 11
4.4.2 Data transfer to the PLC............................................................................................................... 12
4.4.3 RFID channels – Operating modes .......................................................................................... 12
4.4.4 RFID commands ............................................................................................................................. 14
4.4.5 Loop counter function ................................................................................................................. 14
4.4.6 Configurable digital channels – functions............................................................................ 15
4.4.7 Turck Field Logic Controller (FLC) ............................................................................................ 15
4.5 Technical accessories.................................................................................................... 15
5 Mounting............................................................................................................................................ 16
5.1 Mounting devices in combination ............................................................................. 16
5.2 Mounting onto a mounting plate .............................................................................. 17
5.3 DIN rail (TS35) mounting ............................................................................................. 17
5.4 Mounting the device outdoors................................................................................... 18
5.5 Grounding the device................................................................................................... 18
5.5.1 Grounding and shielding concept........................................................................................... 18
5.5.2 Ground the device (FE) ................................................................................................................ 19
6 Connection......................................................................................................................................... 20
6.1 Connecting the device to Ethernet ............................................................................ 20
6.1.1 QuickConnect and Fast Start-Up applications .................................................................... 20
6.2 Connecting the power supply .................................................................................... 21
6.3 Connecting RFID read/write heads............................................................................ 22
6.3.1 Connecting read/write heads for the HF bus mode.......................................................... 23
6.4 Connecting digital sensors and actuators................................................................ 24

05.00 | 2019/11 3
Contents

7 Commissioning ................................................................................................................................. 25
7.1 Setting the IP address................................................................................................... 25
7.2 Connecting the device to a Modbus master ............................................................ 28
7.2.1 Connecting the device with the controller .......................................................................... 29
7.2.2 Renaming a Modbus slave.......................................................................................................... 33
7.2.3 Setting up network interfaces................................................................................................... 34
7.2.4 Modbus TCP slave – Setting the IP address.......................................................................... 35
7.2.5 Defining Modbus channels (registers) ................................................................................... 36
7.2.6 Connecting the device online with the controller............................................................. 38
7.2.7 Reading out process data ........................................................................................................... 38
7.2.8 Modbus TCP – Mapping .............................................................................................................. 39
7.3 Connecting a device to an EtherNet/IP™ controller................................................ 44
7.3.1 Installing an EDS file...................................................................................................................... 45
7.3.2 Connecting the device with the controller .......................................................................... 49
7.3.3 Connecting the device online with the controller............................................................. 55
7.3.4 Reading out process data ........................................................................................................... 57
7.3.5 EtherNet/IP™ – Mapping ............................................................................................................. 59
7.3.6 Activating QuickConnect (QC) .................................................................................................. 65
7.4 Connecting a device to a Siemens PROFINET controller ....................................... 68
7.4.1 Installing a GSDML file ................................................................................................................. 69
7.4.2 Connecting the device with the controller .......................................................................... 71
7.4.3 Assigning the PROFINET device name ................................................................................... 72
7.4.4 Set the IP address in the TIA Portal.......................................................................................... 72
7.4.5 Connecting the device online with the controller............................................................. 73
7.4.6 Setting module parameters ....................................................................................................... 74
7.4.7 PROFINET – Mapping.................................................................................................................... 74
8 Setting ................................................................................................................................................ 75
8.1 RFID channels – Parameter data................................................................................. 76
8.1.1 Meaning of the parameter bits ................................................................................................. 77
8.1.2 HF applications – Selecting the tag type............................................................................... 79
8.1.3 HF applications – Setting the bridging time (bypass time)............................................ 81
8.1.4 HF applications – Setting HF bus mode ................................................................................ 82
8.1.5 UHF applications – Setting Continuous presence sensing mode................................ 88
8.1.6 UHF applications – Transferring read/write head settings ............................................. 88
8.2 RFID channels – Process input data ........................................................................... 89
8.2.1 Meaning of the status bits .......................................................................................................... 92
8.2.2 Tag in detection range (TP) – Using bit or pre-loading the command ...................... 94
8.3 RFID channels – Process output data ........................................................................ 95
8.3.1 Meaning of the command bits.................................................................................................. 98
8.4 Digital channels – Parameter data .......................................................................... 100
8.4.1 Meaning of the parameter bits .............................................................................................. 100
8.5 Digital channels – Setting advanced parameters (EXT LEAN) ........................... 100
8.5.1 Meaning of the parameter bits .............................................................................................. 100
8.6 Digital channels – Process input data .................................................................... 101
8.6.1 Meaning of the status bits ....................................................................................................... 101
8.7 Digital channels – Process output data.................................................................. 101
8.7.1 Meaning of the command bits............................................................................................... 101
8.8 RFID channels – Overview of commands............................................................... 102
8.8.1 Command: Idle............................................................................................................................. 104
8.8.2 Command: Inventory................................................................................................................. 105
8.8.3 Read command............................................................................................................................ 109
8.8.4 Command: Write ......................................................................................................................... 111

4 Hans Turck GmbH & Co. KG | T +49 208 4952-0 | F +49 208 4952-264 | [email protected] | www.turck.com
8.8.5 Command: Write and verify .................................................................................................... 113
8.8.6 Command: Continuous mode................................................................................................ 115
8.8.7 Command: Get data from buffer command (Continuous mode/Continuous
presence sensing mode) .......................................................................................................... 117
8.8.8 Command: Continuous presence sensing mode (UHF) ............................................... 120
8.8.9 Command: End Continuous (presence sensing) mode ................................................ 121
8.8.10 Command: Read/write head identification ....................................................................... 122
8.8.11 Command: Switch off HF read/write head ........................................................................ 123
8.8.12 Command: HF read/write head tuning............................................................................... 124
8.8.13 Command: Query HF read/write head address ............................................................... 125
8.8.14 Command: Set HF read/write head address ..................................................................... 126
8.8.15 Direct read/write head command ........................................................................................ 127
8.8.16 Command: Set tag password.................................................................................................. 131
8.8.17 Command: Set read/write head password........................................................................ 133
8.8.18 Command: Reset read/write head password ................................................................... 134
8.8.19 Command: Set tag protection................................................................................................ 135
8.8.20 Command: Query HF tag protection status ...................................................................... 137
8.8.21 Command: Set permanent lock (Lock)................................................................................ 139
8.8.22 Command: Tag info.................................................................................................................... 141
8.8.23 Command: Kill UHF tag............................................................................................................. 143
8.8.24 Command: Restore UHF read/write head settings ......................................................... 144
8.8.25 Command: Backup settings of the UHF read/write head............................................. 145
8.8.26 Command: Query error/status of UHF read/write head ............................................... 146
8.8.27 Command: Reset ......................................................................................................................... 149
8.9 Setting RFID interfaces via the web server............................................................ 150
8.9.1 Opening a web server ............................................................................................................... 150
8.9.2 Processing settings in the web server ................................................................................. 151
8.10 Testing and parameterizing RFID interfaces via the DTM.................................. 161
8.10.1 Connecting the device with the PC...................................................................................... 161
8.10.2 Editing parameter data with the DTM – Online parameterization ........................... 164
8.10.3 Reading process input data with the DTM – Measured value.................................... 165
8.10.4 Changing process output data with the DTM – Simulation........................................ 165
8.10.5 Evaluating diagnostics with the DTM.................................................................................. 166
8.10.6 Example: Executing a read command with the DTM..................................................... 167
8.11 Setting UHF read/write heads.................................................................................. 168
9 Operation ......................................................................................................................................... 169
9.1 Executing a command and calling data................................................................. 169
9.1.1 Typical times for command processing via a controller............................................... 169
9.2 Using fragmentation ................................................................................................. 171
9.2.1 Example: Using fragmentation in the web server – Read ............................................ 171
9.2.2 Example: Using fragmentation in the web server – Write ........................................... 177
9.3 Using commands with a loop counter function ................................................... 182
9.4 HF applications – Using Continuous mode ........................................................... 182
9.5 Using HF bus mode .................................................................................................... 183
9.5.1 Executing commands in HF bus mode ............................................................................... 183
9.5.2 Replacing bus-capable read/write heads........................................................................... 183
9.5.3 Continuous HF bus mode — Data retrieval ...................................................................... 184
9.6 HF applications — Using continuous HF bus mode ............................................ 185
9.7 Query UID in HF Continuous bus mode ................................................................. 187
9.8 Using NEXT mode....................................................................................................... 188
9.8.1 Example: Using NEXT mode for a read command .......................................................... 188
9.9 Using the UHF password function .......................................................................... 189

05.00 | 2019/11 5
Contents

9.9.1 Access password ......................................................................................................................... 189

9.10 Use CODESYS function blocks ................................................................................. 189
9.11 Using function blocks for Siemens TIA portal....................................................... 197
9.12 Using Inventory command and Continuous (presence sensing) mode .......... 201
9.13 LEDs............................................................................................................................... 202
9.14 Software diagnostic messages ................................................................................ 204
9.14.1 Diagnostic messages – Gateway functions ....................................................................... 204
9.14.2 Diagnostic messages – RFID channels ................................................................................ 204
9.14.3 Diagnostic messages – Digital channels ............................................................................ 205
9.14.4 Diagnostic messages – Module status ................................................................................ 205
9.15 Example: Activating diagnostics via the PLC software ....................................... 206
9.16 Reading error codes................................................................................................... 209
9.17 Using extended diagnostics – Time measurement for commissioning an
application................................................................................................................... 214
10 Troubleshooting ............................................................................................................................. 217
11 Maintenance.................................................................................................................................... 218
11.1 Executing the Firmware Update.............................................................................. 218
12 Repair................................................................................................................................................ 222
12.1 Returning devices....................................................................................................... 222
13 Disposal ............................................................................................................................................ 222
14 Technical data ................................................................................................................................. 223
15 Appendix: Flow charts showing the operation of the device ................................................ 226
15.1 Flow chart: Command processing........................................................................... 226
15.2 Flow chart: Rapid command processing with loop counter .............................. 227
15.3 Flow chart: Command processing with fragmentation ...................................... 228
15.4 Flow chart: Continuous mode with interruption before reading data ............ 229
15.5 Flow chart: Continuous mode without interruption before reading data...... 230
16 Appendix: Declaration of Conformity ........................................................................................ 231

6 Hans Turck GmbH & Co. KG | T +49 208 4952-0 | F +49 208 4952-264 | [email protected] | 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 in-
structions for future use during the service life of the product. If the product is passed on, pass
on these instructions as well.

1.1 Target groups

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

1.2 Explanation of symbols used

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

1.3 Other documents

Besides this document the following material can be found on the Internet at www.turck.com:
n Data sheet
n EC Declaration 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].

05.00 | 2019/11 7
Notes on the product
Manufacturer and service

2 Notes on the product

2.1 Product identification
These instructions apply to the following compact RFID interfaces:
n TBEN-S2-2RFID-4DXP

2.2 Scope of delivery

The scope of delivery includes:
n Compact RFID interface
n Closure caps for M12 connectors
n Quick-Start Guide

2.3 Legal requirements

The device is subject to the following EC directives:
n 2014/30/EU (electromagnetic compatibility)
n 2011/65/EU (RoHS Directive)

2.4 Manufacturer and service

Hans Turck GmbH & Co. KG
Witzlebenstraße 7
45472 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/products
For further inquiries in Germany contact the Sales and Service Team on:

n Sales: +49 208 4952-380

n Technology: +49 208 4952-390

Outside Germany, please contact your local Turck representative.

8 Hans Turck GmbH & Co. KG | T +49 208 4952-0 | F +49 208 4952-264 | [email protected] | 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

These devices are designed solely for use in industrial areas.
The TBEN-S2-2RFID-4DXP block module is an RFID interface for use in the Turck BL ident® 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 supports 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 two BL ident® read/write heads can be connected to the device. In
Bus mode it is possible to connect up to 32 bus-capable HF read/write heads per channel. Four
configurable digital channels are also provided. The multiprotocol interfaces can be connected
to the Ethernet fieldbus systems PROFINET, Modbus TCP and EtherNet/IP™.
The devices may only be used as described in these instructions. Any other use is not in accord-
ance with the intended use. Turck accepts no liability for any resulting damage.

3.2 General safety notes

n The device may only be assembled, installed, operated, parameterized and maintained by
professionally-trained personnel.
n The device may only be used in accordance with applicable national and international regu-
lations, standards and laws.
n The device only meets the EMC requirements for industrial areas and is not suitable for use
in residential areas.
n Change the default password of the integrated web server after the first login. Turck recom-
mends using a secure password.

05.00 | 2019/11 9
Product description
Properties and features

4 Product description
The devices are designed with a fully encapsulated housing with degree of protection IP65/
IP67/P69K. Two RFID channels are provided for connecting read/write heads. It is also possible
to connect sensors and actuators via four digital I/O channels, which can be configured as in-
puts or outputs as required. The terminals for the read/write heads and for digital I/Os are M12
sockets. An M8 socket is provided for the fieldbus connection.

4.1 Device overview

28 24 32

P1 C3 C2 C1 C0 X1
ø 4.6
32
17.9
P2 X2
132
144.3

Fig. 1: Dimensions

4.1.1 Display elements

The device has the following LED indicators:
n Power supply
n Group and bus errors
n Status
n Diagnostics

4.2 Properties and features

n PROFINET Device, EtherNet/IP™ Device or Modbus TCP Slave
n PROFINET S2 system redundancy
n Integrated Ethernet switch
n Supports 10 Mbps/100 Mbps
n Glass fiber reinforced housing
n Shock and vibration tested
n Fully encapsulated module electronics
n Degree of protection IP65/IP67/IP69K
n Integration in PLC systems without special function block
n Up to 128 bytes of user data per read/write cycle per channel as well as the use of fragments
for larger data volumes with 16 kB FIFO memory
n Data interface for convenient use of the RFID functions
n HF Continuous bus mode with up to 32 bus-capable read/write heads per channel
n Two channels with M12 connector for RFID
n Mixed operation of HF and UHF read/write heads
n Four configurable digital channels as 0.5 A PNP inputs or outputs
n Integrated web server
n LEDs and diagnostics
n Programmable with FLC/ARGEE

10 Hans Turck GmbH & Co. KG | T +49 208 4952-0 | F +49 208 4952-264 | [email protected] | www.turck.com
4.3 Operating principle
The BL ident® interfaces connect the RFID system with the higher-level controller system. The
interfaces are provided with a fieldbus interface and fieldbus-independent I/O electronics with
an RFID interface. The interface signals of up to four sensors and actuators can also be pro-
cessed via four configurable digital channels. The interfaces are provided with a multiprotocol
fieldbus interface for Modbus TCP, EtherNet/IP™ and PROFINET. The fieldbus interface connects
the RFID system to an (existing) fieldbus as an EtherNet/IP™ device, Modbus TCP slave or
PROFINET device. During operation, the process data is exchanged between the fieldbus and
RFID system and diagnostics information is also generated for the controller. The read/write
heads are connected to the interfaces via the RFID interfaces.

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 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. In all, up to four
3-wire PNP sensors or four PNP DC actuators with a maximum output current of 0.5 A can be
connected per input or output.

4.4.1 Multiprotocol technology

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

Automatic protocol detection

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

Manual Protocol Selection

The user can also define the protocol manually. In this case, the snooping phase is skipped and
the device is fixed to the selected protocol. With the other protocols, the device can only be ac-
cessed read-only.

05.00 | 2019/11 11
Product description
Functions and operating modes

Protocol Dependent Functions

The device Supported the following Ethernet protocol specific functions:
PROFINET
n FSU - Fast Start-Up (prioritized startup)
n Topology discovery
n Address assignment via LLDP
n MRP (Media Redundancy Protocol)
EtherNet/IP™
n QC – QuickConnect
n Device Level Ring (DLR)

4.4.2 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
n 8 bytes n 16 bytes n 128 bytes (permanently set)
n 16 bytes (default setting) n 64 bytes Adjustable fragment size:
n 32 bytes n 128 bytes (default setting) n 8 bytes
n 64 bytes n 16 bytes (default setting)
n 128 bytes n 32 bytes
n 64 bytes
n 128 bytes

4.4.3 RFID channels – Operating modes

Five different data interfaces selectable for RFID channels:
n HF compact
n HF extended
n HF bus mode
n UHF compact
n UHF 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.

12 Hans Turck GmbH & Co. KG | T +49 208 4952-0 | F +49 208 4952-264 | [email protected] | www.turck.com
HF bus mode
In HF bus mode, up to 32 bus-compatible read/write heads per RFID channel can be connected
to the TBEN module. Depending on the number of read/write heads connected and the power
consumption of the connected heads, an additional power supply may be required. In order to
determine whether an additional power supply is required, a power consumption analysis of
the connected read/write heads must be performed. A tool to help calculate the power con-
sumption of the read/write heads is available at www.turck.com/hf-busmodus.

Every connected read/write head supplies a "tag present" signal in HF bus mode. By default, a
command can only be processed by one read/write head, making HF bus mode suitable for
static applications and slow dynamic applications.
In Continuous HF bus mode, a command is performed simultaneously at all read/write heads in
a bus topology. The logged data is stored in the ring memory of the module.
RFID connection cable
(e.g. RK4.5T-0.3-RS4.5T/S2503)

TBEN-S2-2RFID-4DXP

VT2-FKM5-FKM5-FSM5

TN-M30-H1147/C53

TN-M18-H1147/C53 up to 32 per port

TN-CK40-H1147/C53

Fig. 2: HF bus mode setup

The following read/write heads can be used for HF bus mode:

n TN-M18-H1147/C53
n TB-M18-H1147/C53
n TN-M30-H1147/C53
n TB-M30-H1147/C53
n TN-CK40-H1147/C53
n TNSLR-Q42TWD-H1147/C53
n TB-Q08-0.15-RS4.47T/C53
n TB-Q08-0.15-RS4.47T/C53
n TN-Q14-0.15-RS4.47T/C53
n TNSLR-Q80WD-H1147/C53
HF bus mode supports the HF read/write heads from firmware version Vx.90. Continuous bus
mode supports HF read/write heads from firmware version Vx.93.
Firmware version V3.6.1.0 or higher is also required for Continuous bus mode on the TBEN-S
module.

05.00 | 2019/11 13
Product description
Functions and operating modes

UHF compact mode

UHF compact mode enables up to 128 bytes of data to be transferred in single-tag applications
(e.g. EPC).

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 of data. The operating mode is suitable for single-tag and
multitag 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”.
n Idle
n Inventory
n Read
n Write
n Write and verify
n Continuous mode
n Get data from buffer (Continuous mode)
n Continuous presence sensing mode (UHF)
n End Continuous (presence sensing) mode
n Read/write head identification
n Switch off HF read/write head
n HF read/write head tuning
n Query HF read/write head address
n Set HF read/write head address
n Direct read/write head command
n Set tag password
n Set read/write head password
n Reset read/write head password
n Set tag protection
n Query HF tag protection status
n Set permanent lock (Lock)
n Tag info
n Kill UHF tag
n Restore settings of the UHF read/write head
n Backup settings of the UHF read/write head
n Query error/status of UHF read/write head
n Reset

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 [} 227]).
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.

14 Hans Turck GmbH & Co. KG | T +49 208 4952-0 | F +49 208 4952-264 | [email protected] | www.turck.com
4.4.6 Configurable digital channels – functions
The device is provided with four digital channels, which can be configured as inputs or outputs
according to the application requirements. In all, up to four 3-wire PNP sensors or four PNP DC
actuators with a maximum output current of 0.5 A can be connected per input or output.

4.4.7 Turck Field Logic Controller (FLC)

The device supports logic processing with the Turck Field Logic Controller (FLC) function. This
enables the device to perform small to medium complexity control tasks in order to relieve the
processing load on the central controller. The FLCs can be programmed in the ARGEE engineer-
ing environment.
As of firmware version 3.6.0.0, the device supports the ARGEE 3 engineering environment.
The ARGEE-FLC programming software can be downloaded free of charge from
www.turck.com.
The Zip archive SW_ARGEE_Environment_Vx.x.zip also contains the documentation for the pro-
gramming environment in addition to the software.

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.

05.00 | 2019/11 15
Mounting
Mounting devices in combination

5 Mounting
The device can be mounted on a DIN rail according to EN 60715 (TS35) or screwed on a mount-
ing plate. Both combined mounting as well as single mounting are possible.

5.1 Mounting devices in combination

The TBNN-S0… adapters can be used to form groups of modules for mounting the devices in
combination.

1 1

2 2

3 3

4 4

Fig. 3: Module groups for mounting on a Fig. 4: Module groups for mounting on a DIN
mounting plate rail (TS35)
Undo locking lever (1) with a flat tool (e.g. screwdriver).
Fully open the locking lever (2).
Connect the TBEN-S module and adapter so that the spring of the adapter engages with
the groove of the TBEN-S module (3).
Push down the locking lever and close until the locking lever engages with an audible
click (4).
Repeat steps 1 to 4 until the module group is complete.

16 Hans Turck GmbH & Co. KG | T +49 208 4952-0 | F +49 208 4952-264 | [email protected] | www.turck.com
5.2 Mounting onto a mounting plate
The devices are fixed on a pre-drilled mounting plate with two M4 screws. The maximum tight-
ening torque for the M4 screws is 1.3 Nm
Mount the modules or the module composites according to the following figure.

Fig. 5: Mounting the device to a mounting plate.

5.3 DIN rail (TS35) mounting

The TBNN-S0-DRS adapters enable the device to be mounted individually or in a combination
on a DIN rail (TS35).

NOTICE
Incorrect mounting
Missing grounding may cause malfunction
Align the adapters so that the arrow on the locking lever points in the direction
of the M8 Ethernet sockets.
Connect the grounding contact of the adapter with the grounding contact of
the module.

Mount one spacer to the left and one to the right of the module.
Place the module/ the module-cluster onto the DIN-rail so that the cut-out in the spacer/
spacers enclose the DIN rail (1).
To activate the DIN rail lock, turn the pintle in the cover flap of every spacer by means of a
screw driver (2).
Optional: Ground the device.

Fig. 6: Mounting the module combination on a DIN rail

NOTE
To increase stability on the DIN rail, end brackets can be mounted on the right and
left of the module or the module combination.

05.00 | 2019/11 17
Mounting
Grounding the device

5.4 Mounting the device outdoors

The device is UV-resistant according to DIN EN ISO 4892-2. Direct sunlight can cause material
abrasion and color changes. The mechanical and electrical properties of the device are not af-
fected.
To avoid material abrasion and color changes: Protect the device from direct sunlight,
e.g. by using protective shields.

5.5 Grounding the device

5.5.1 Grounding and shielding concept
The fieldbus and I/O area of the TBEN-S modules can be grounded separately.

X1 X2

P1 P2

Fig. 7: Equivalent circuit, shielding concept

1
2
4
3

Fig. 8: rounding clip (1), Fig. 9: Grounding contact Fig. 10: Grounding the TB-
grounding ring (2) and metal NNS0-DRS… adapters
screw (3)
The grounding clip (1) on the M8 plug connectors for the fieldbus connection (P1, P2) connects
the shield of the fieldbus cables.
The grounding ring (2) provides the shield on the flange of the M8 plug connectors for the
fieldbus connection via an RC circuit.
By mounting the module on a mounting plate (with connectors of type TBNN-S0-STD) the
module is connected to the reference potential of the installation via a metal screw (3) through
the mounting hole. The TBNN-S0-DRS adapters for mounting the TBEN-S modules on a DIN rail
(TS 35) connect the grounding contact (4) of the modules with the DIN rail and thus FG.

18 Hans Turck GmbH & Co. KG | T +49 208 4952-0 | F +49 208 4952-264 | [email protected] | www.turck.com
5.5.2 Ground the device (FE)
Grounding clip and grounding ring are connected together.
If a common reference potential for I/O level and fieldbus level is not required: remove
the grounding clip to disconnect the fieldbus shield.

Grounding the device – Mounting on DIN rail

When mounting on a DIN rail with the TBNN-S0-DRS adapters fasten the supplied metal
screw on the lower mounting hole of the TBEN-S module.
a The shield of the fieldbus connection and the M8 flange of the I/O level are connected via
the DIN rail with the reference potential of the installation.

Grounding the device – Mounting on mounting plate

When mounting on a mounting plate, fasten with an M4 metal screw.
a The shield of the fieldbus connection and the M8 flange of the I/O level are connected via
the DIN rail with the reference potential of the installation.

Removing the grounding strip

Push the grounding clip forward with a flat slot-head screwdriver and remove.

Fig. 11: Removing the grounding strip

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.
a The shield of the fieldbus cables is connected to the grounding clip.

Fig. 12: Mounting the grounding clip

05.00 | 2019/11 19
Connection
Connecting the device to Ethernet

6 Connection
6.1 Connecting the device to Ethernet
The connection to Ethernet is realized via an auto-crossing switch is done using two 4-pin, D-
coded M8 x 1-Ethernet-connectors.

NOTICE
Interchanging of Ethernet- and power cables
Destruction of module electronic
Observe using the correct M8-connectors when connecting Ethernet- and
power cables:
- Ethernet: P1 and P2,
supply voltage: X1and X2

Fig. 13: M8 Ethernet connector

Connect the device to Ethernet according to the pin assignment.

v v
1 = TX + 1 = RX +
4 2 2 = RX + 4 2 2 = TX +
3 1 3 = RX – 3 1 3 = TX –
4 = TX – 4 = RX –
P1 P2

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

6.1.1 QuickConnect and Fast Start-Up applications

Do not use crossover cables in QuickConnect and Fast Start-Up applications.
Connect incoming Ethernet cables to P1.
Connect outgoing Ethernet cables to P2.

20 Hans Turck GmbH & Co. KG | T +49 208 4952-0 | F +49 208 4952-264 | [email protected] | www.turck.com
6.2 Connecting the power supply
The device is provided with two 4-pin M8 plug connectors for connecting the power supply. V1
and V2 are electrically isolated from each other.

Fig. 15: M8 plug connectors for connecting the power supply

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

w v
1 BN = V1 (+)
2 4 2 WH = V2 (+) 4 2
1 3 3 BU = GND V1 3 1
4 BK = GND V2
X1 X2

Fig. 16: Pin assignment of the power supply connections

Connection Meaning
X1 Incoming voltage supply
X2 Routing the voltage to the next node
V1 Supply voltage 1 (incl. electronics supply)
V2 Power supply 2

NOTE
The system voltage (V1) and the load voltage (V2) are supplied and monitored sep-
arately. If the voltage goes below the permissible lower limit, the sockets are discon-
nected according to the supply concept of the module type. If V2 goes below the
permissible minimum voltage, PWR LED changes from green to red. If V1 goes below
the permissible minimum, the LED goes out.

05.00 | 2019/11 21
Connection
Connecting RFID read/write heads

6.3 Connecting RFID read/write heads

The device has two 5-pin M12 plug connectors for connecting RFID read/write heads.

Fig. 17: M12 plug connector for connecting read/write heads

Connect the read/write heads to the device as per the pin assignment shown below.

v
2 1 = Vaux1
2 = Data B
1 3 3 = GND V1
4 = Data A
5 4 5 = FE/Shield

Fig. 18: RS485 – Pin assignment of the read/write head connections

v
2 1 = BN (+)
2 = BK (Data)
1 3 3 = BU (GND)
4 = WH (Data)
5 4
5 = shield

Fig. 19: …/S2500 connection cables – Pin assignment of the read/write head connections

v
2 1 = BN (+)
2 = WH (Data)
1 3 3 = BU (GND)
4 = BK (Data)
5 4
5 = shield

Fig. 20: …/S2501 connection cables – Pin assignment of the read/write head connections

v
2 1 = RD (+)
2 = BU (Data)
1 3 3 = BK (GND)
4 = WH (Data)
5 4 5 = shield

Fig. 21: …/S2503 connection cables – Pin assignment of the read/write head connections

22 Hans Turck GmbH & Co. KG | T +49 208 4952-0 | F +49 208 4952-264 | [email protected] | www.turck.com
6.3.1 Connecting read/write heads for the HF bus mode
In HF bus mode up to 32 bus-capable read/write heads per RFID channel can be connected to
the device. The user must determine by means of a power consumption analysis whether an
additional power supply is required for the connected read/write heads (see information in the
data sheet).

The maximum permissible length of the bus is 50 m.

The following accessories are required for the bus mode:

n The VT2-FKM5-FKM5-FSM5 (Ident-No. 6930573) junction boxes are required for connecting
several read/write heads to an RFID port
n RSE57-TR2/RFID bus terminating resistor (Ident-No. 6934908)
n Optional: VB2-FKM5-FSM5.205-FSM5.305/S2550 junction box (Ident-No. 6936821) for feed-
ing in an additional power supply
n RFID connection cables (e.g. RK4.5T-0.3-RS4.5T/S2503)

Connect the read/write head as per the figure below. The maximum length of the spur
line is 2 m.
Take the power supply into account, particularly at switch-on (see data sheet), as well as
the maximum current carrying capacity of the lines (4 A).
Take the voltage drop on the line into account. If necessary provide an additional power
supply between the read/write heads using junction box VB2-FKM5-FSM5.205-FSM5.305/
S2550.
Connect a terminating resistor (e.g. RSE57-TR2/RFID) behind the last read/write head.
RFID connection cable
(e.g. RK4.5T-0.3-RS4.5T/S2503)

TBEN-S2-2RFID-4DXP

VT2-FKM5-FKM5-FSM5

TN-M30-H1147/C53

TN-M18-H1147/C53 up to 32 per port

TN-CK40-H1147/C53

Fig. 22: HF bus mode setup

05.00 | 2019/11 23
Connection
Connecting digital sensors and actuators

6.4 Connecting digital sensors and actuators

The device has two 5-pin M12 plug connectors for connecting digital sensors and actuators.
Sensors and actuators can be connected to the DXP terminals in the following combinations:
n 2 digital inputs
n 2 digital outputs
n 1 digital input and 1 digital output

Fig. 23: M12 plug connector for connecting digital sensors and actuators

Connect the sensors and actuators to the device as per the pin assignment below.
v 3 BU –
4 BK Sensor
2 1 = Vaux2 5 FE or
2 = Signal In/Out
1 3 3 = GND V2 1 BN + Actuator
4 = Signal In/Out
5 4 5 = FE 2 WH Sensor
or
C2...C3 3 BU – Actuator
vC2…C3
Fig. 24: Connections for digital sensors and ac- Fig. 25: Connections for digital sensors and ac-
tuators – Pin assignment tuators – Wiring diagram
The channels are assigned to the slots as follows:
Channel Slot Pin
DXP (Ch4) C2 4
DXP (Ch5) C2 2
DXP (Ch6) C3 4
DXP (Ch7) C3 2

24 Hans Turck GmbH & Co. KG | T +49 208 4952-0 | F +49 208 4952-264 | [email protected] | www.turck.com
7 Commissioning
The device is operational automatically once the cables are connected and the power supply is
switched on.
Connected HF read/write heads are switched on automatically. Connected UHF read/write
heads are switched off automatically and are activated automatically when a command is ex-
ecuted (apart from Idle mode).
In the default configuration the idle command (0x0000) is active. If an HF read/write head is
connected, the Tag Present bit is set and the UID is output in the input data if a tag is located in
the detection range of the read/write head.
Set the IP address of the device in order to carry out further commands.

If a UHF read/write head is connected, the device must be set:

Set the IP address.
Send the command to the UHF read/write head.

7.1 Setting the IP address

The device is factory set to IP address 192.168.1.254 and does not have a PROFINET device
name. The IP address can be set via the Turck Service Tool, the DTM, the web server, a DHCP
server or PROFINET DCP. The following example shows the setting of the IP address via the
Turck Service Tool. The Turck Service Tool can be downloaded free of charge at
www.turck.com.
Connect the device to a PC via the Ethernet interface.
Launch the Turck Service Tool.
Click Search or press F5.

Fig. 26: Turck Service Tool – Start screen

05.00 | 2019/11 25
Commissioning
Setting the IP address

The Turck Service Tool displays the connected devices.

Fig. 27: Turck Service Tool – found devices

Click the required device.

Click Change or press [F2].

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

NOTE
Clicking the IP address of the device opens the web server.

26 Hans Turck GmbH & Co. KG | T +49 208 4952-0 | F +49 208 4952-264 | [email protected] | www.turck.com
Change the IP address and if necessary the network mask and gateway.
Accept the changes by clicking Set in device.

Fig. 29: Turck Service Tool – Change device configuration

05.00 | 2019/11 27
Commissioning
Connecting the device to a Modbus master

7.2 Connecting the device to a Modbus master

Hardware used
This example uses the following hardware components:
n TN-Q80-H1147 HF read/write head
n Turck HMI TX507-P3CV01 (Modbus master)
n TBEN-S2-2RFID-4DXP block module (IP address: 192.168.1.61)
n TN-Q80-H1147 HF read/write head

Software used
This example uses the following software:
n CODESYS 3.5.8.1 (download free of charge from www.turck.com)

Prerequisites
n The programming software has been started.
n A new project has been created.
n The PLC has been added to the project.

28 Hans Turck GmbH & Co. KG | T +49 208 4952-0 | F +49 208 4952-264 | [email protected] | www.turck.com
7.2.1 Connecting the device with the controller
To connect the device to the controller, the following components must be added in CODESYS
first of all:
n Ethernet adapter
n Modbus TCP master
n Modbus TCP slave

Adding an Ethernet adapter

Right-click Device (TX507-P3CV01) in the project tree.

Fig. 30: Project tree

05.00 | 2019/11 29
Commissioning
Connecting the device to a Modbus master

Select Add device.

Select an Ethernet adapter.
Click Add device.
a The Ethernet adapter appears as Ethernet (Ethernet) in the project tree.

Fig. 31: Adding an Ethernet adapter

30 Hans Turck GmbH & Co. KG | T +49 208 4952-0 | F +49 208 4952-264 | [email protected] | www.turck.com
Adding a Modbus master
Right-click Ethernet (Ethernet) in the project tree.
Select Add device.
Double-click the Modbus TCP Master.
a The Modbus master appears as Modbus_TCP_Master (Modbus TCP Master) in the pro-
ject tree.

Fig. 32: Adding a Modbus master

05.00 | 2019/11 31
Commissioning
Connecting the device to a Modbus master

Adding a Modbus slave

In the project tree right-click Modbus TCP Master (Modbus TCP Master).
Select Add device.
Double-click Modbus TCP Slave.
a The Modbus slave appears as Modbus_TCP_Slave in the project tree.

Fig. 33: Adding a Modbus slave

32 Hans Turck GmbH & Co. KG | T +49 208 4952-0 | F +49 208 4952-264 | [email protected] | www.turck.com
7.2.2 Renaming a Modbus slave
Click the Modbus slave in the project tree.
Press F2.
Adapt the name of the slave in the project tree of the application.

Fig. 34: Assigning a device name (here: TBEN-S2-2RFID_4DXP)

05.00 | 2019/11 33
Commissioning
Connecting the device to a Modbus master

7.2.3 Setting up network interfaces

Click Device Ò Scan network.
Select Modbus master and confirm with OK.

Fig. 35: Setting up a network interface to the Modbus master

Double-click Ethernet.
Open the Network Adapter dialog in the General tab via the … button.
Enter the IP address of the Modbus master.

Fig. 36: Modbus master – Entering the IP address (here: 192.168.1.60)

34 Hans Turck GmbH & Co. KG | T +49 208 4952-0 | F +49 208 4952-264 | [email protected] | www.turck.com
7.2.4 Modbus TCP slave – Setting the IP address
Double-click the Modbus TCP slave.
In the General tab enter the IP address of the slave.

Fig. 37: Modbus slave – Entering the IP address (here: 192.268.1.61)

05.00 | 2019/11 35
Commissioning
Connecting the device to a Modbus master

7.2.5 Defining Modbus channels (registers)

Fig. 38: Defining READ registers

36 Hans Turck GmbH & Co. KG | T +49 208 4952-0 | F +49 208 4952-264 | [email protected] | www.turck.com
Defining channel 1 (output data)
Double-click the Modbus TCP slave.
Select in the tab Modbus slave channel Ò Add channel.
Enter the following values:
n Name of channel
n Access type: Write multiple registers
n Offset: 0x0800
n Length: 64 registers (128 bytes)
Confirm with OK.

Fig. 39: Setting WRITE registers

Changing channel addresses

Double-click the Modbus TCP slave.
Click the Modbus TCP slave I/O image tab.
Enter the address in the corresponding table column.

Fig. 40: Changing channel addresses

05.00 | 2019/11 37
Commissioning
Connecting the device to a Modbus master

7.2.6 Connecting the device online with the controller

Select device.
Click Online Ò Login.

7.2.7 Reading out process data

The process data can be interpreted if the device is connected online with the controller.

Double-click the Modbus TCP slave.

Click the Modbus TCP slave I/O image tab.
a The process data is displayed.

Fig. 41: Process data

38 Hans Turck GmbH & Co. KG | T +49 208 4952-0 | F +49 208 4952-264 | [email protected] | www.turck.com
7.2.8 Modbus TCP – Mapping

RFID channels – Parameter data

Description Register Bit offset Bit length
Channel 1 Channel 2
Operating mode 0xB000 0xB012 0 8
Select tag type 0xB000 0xB012 8 8
Bridging time 0xB001 0xB013 0 16
HF: Multitag mode 0xB002 0xB014 4 1
HF: Heartbeat read/write head 0xB002 0xB014 5 1
RS 485 terminating resistor 0xB002 0xB014 6 1
Automatic tuning of read/write head 0xB002 0xB014 7 1
Deactivate diagnostic HF read/write 0xB002 0xB014 8 1
head tuning
Diagnostic input filter 0xB002 0xB014 15 1
HF Idle mode 0xB003 0xB015 0 8
Command repetitions in the event of 0xB004 0xB016 0 8
an error
HF: Command in Continuous mode 0xB004 0xB016 8 8
HF: Length in Continuous mode 0xB005 0xB017 0 16
HF: Address in Continuous mode 0xB006 0xB018 0 32
Length of read data 0xB010 0xB022 0 16
Length of write data 0xB011 0xB023 0 16
HF bus mode: Activate read/write 0xB00E 0xB020 0 1
head 1
… … … … 1
HF bus mode: Activate read/write 0xB00E 0xB020 15 1
head 16
HF bus mode: Activate read/write 0xB00F 0xB021 0 1
head 17
… … … … 1
HF bus mode: Activate read/write 0xB00F 0xB021 15 1
head 32

05.00 | 2019/11 39
Commissioning
Connecting the device to a Modbus master

40 Hans Turck GmbH & Co. KG | T +49 208 4952-0 | F +49 208 4952-264 | [email protected] | www.turck.com
RFID channels – Process output data
Description Register Bit offset Bit length
Channel 1 Channel 2
Command code 0x0800 0x084C 0 16
Loop counter 0x0801 0x084D 0 8
Memory area (only UHF) 0x0801 0x084D 8 8
Start address 0x0802 0x084E 0 32
Length 0x0804 0x0851 0 16
Length UID/EPC 0x0805 0x0851 0 8
Antenna no. 0x080A 0x0856 0 8
Timeout 0x0806 0x0852 0 16
Read fragment no. 0x0807 0x0853 0 8
Write fragment no. 0x0807 0x0853 8 8
Write data Byte 0 0x080C 0x0858 0 8
Write data Byte 1 0x080C 0x0858 8 8
… … … … 8
Write data Byte 14 0x0813 0x085F 0 8
Write data Byte 15 0x0813 0x085F 8 8
… … … … 8
Write data Byte 64 0x0813 0x0878 0 8
Write data Byte 65 0x0813 0x0878 8 8
… … … … 8
Write data Byte 126 0x084B 0x0897 0 8
Write data Byte 127 0x084B 0x0897 8 8

05.00 | 2019/11 41
Commissioning
Connecting the device to a Modbus master

RFID diagnostic data

Description Register Bit offset Bit length
Channel 1 Channel 2
Overvoltage at power supply ter- 0x098 0x00AA 7 1
minal VAUX
Parameter error 0x098 0x00AA 6 1
Configuration via the DTM active 0x098 0x00AA 5 1
Memory full 0x098 0x00AA 4 1
Read/write head 1 not tuned 0x09A 0x00AC 4 1
Read/write head 2 not tuned 0x09A 0x00AC 12 1
… … … 0 1
Read/write head 31 not tuned 0x00A9 0x00BB 4 1
Read/write head 32 not tuned 0x00A9 0x00BB 12 1
Parameter not supported by read/ 0x09A 0x00AC 5 1
write head 1.
Parameter not supported by read/ 0x09A 0x00AC 13 1
write head 2.
… … … … 1
Parameter not supported by read/ 0x00A9 0x00BB 5 1
write head 31.
Parameter not supported by read/ 0x00A9 0x00BB 13 1
write head 32.
Read/write head 1 reports error 0x09A 0x00AC 6 1
Read/write head 2 reports error 0x09A 0x00AC 14 1
… … … … 1
Read/write head 31 reports error 0x00A9 0x00BB 6 1
Read/write head 32 reports error 0x00A9 0x00BB 14 1
Expected read/write head 1 not con- 0x09A 0x00AC 7 1
nected
Expected read/write head 2 not con- 0x09A 0x00AC 15 1
nected
… … … … 1
Expected read/write head 31 not con- 0x00A9 0x00BB 7 1
nected
Expected read/write head 32 not con- 0x00A9 0x00BB 15 1
nected

Digital channels – Input data

Description Register Bit offset Bit length
Input value channel 4 0x00BC 4 1
Input value channel 5 0x00BC 5 1
Input value channel 6 0x00BC 6 1
Input value channel 7 0x00BC 7 1

42 Hans Turck GmbH & Co. KG | T +49 208 4952-0 | F +49 208 4952-264 | [email protected] | www.turck.com
Digital channels – Output data
Description Register Bit offset Bit length
Output value channel 4 0x0898 4 1
Output value channel 5 0x0898 5 1
Output value channel 6 0x0898 6 1
Output value channel 7 0x0898 7 1

Digital channels – diagnostic messages

Description Register Bit offset Bit length
Overvoltage at power supply ter- 0x00BD 2 1
minal VAUX channel 4/5
Overvoltage at power supply ter- 0x00BD 3 1
minal VAUX channel 6/7
Overvoltage at output (channel 4) 0x00BD 12 1
Overvoltage at output (channel 5) 0x00BD 13 1
Overvoltage at output (channel 6) 0x00BD 14 1
Overvoltage at output (channel 7) 0x00BD 15 1

Module status – Diagnostic messages

Description Register Bit offset Bit length
Force mode active in the DTM 0x00BE 14 1
Undervoltage V1 0x00BE 9 1
Undervoltage V2 0x00BE 7 1
Module diagnostic available 0x00BE 0 1
Internal error 0x00BE 10 1
ARGEE program active 0x00BE 1 1

05.00 | 2019/11 43
Commissioning
Connecting a device to an EtherNet/IP™ controller

7.3 Connecting a device to an EtherNet/IP™ controller

Hardware used
This example uses the following hardware components:
n Rockwell controller CompactLogix L30ER
n TBEN-S2-2RFID-4DXP block module
n TN-Q80-H1147 HF read/write head

Software used
This example uses the following software:
n Rockwell RS Logix
n EDS file for TBEN-S2-2RFID-4DXP (download free of charge from www.turck.com)

Prerequisites
n The programming software has been started.
n A new project has been created.
n The PLC has been added to the project.

44 Hans Turck GmbH & Co. KG | T +49 208 4952-0 | F +49 208 4952-264 | [email protected] | www.turck.com
7.3.1 Installing an EDS file
The EDS file is available free of charge for download from www.turck.com.
Include an EDS file: Click Tools Ò EDS Hardware Installation Tool.

Fig. 42: Opening the EDS Hardware Installation Tool

05.00 | 2019/11 45
Commissioning
Connecting a device to an EtherNet/IP™ controller

The wizard for the installation of EDS files is started.

Click Next to select the EDS file.

Fig. 43: Starting the EDS Wizard

46 Hans Turck GmbH & Co. KG | T +49 208 4952-0 | F +49 208 4952-264 | [email protected] | www.turck.com
Select the Register an EDS file(s) option and confirm with Next.

Fig. 44: Option selection – Registering an EDS file(s)

05.00 | 2019/11 47
Commissioning
Connecting a device to an EtherNet/IP™ controller

Select an EDS file: Select a single file or folder (example: single file).
Enter a path for the memory location of the EDS file.
Confirm with Next.
a The Installation wizard guides you through the installation.

Fig. 45: Selecting an EDS file

48 Hans Turck GmbH & Co. KG | T +49 208 4952-0 | F +49 208 4952-264 | [email protected] | www.turck.com
7.3.2 Connecting the device with the controller
Right-click I/O Configuration Ò Ethernet.
Click New Module.

Fig. 46: Adding a new module

05.00 | 2019/11 49
Commissioning
Connecting a device to an EtherNet/IP™ controller

Select Turck under Module Type Vendor Filters.

Select TBEN-S2-2RFID-4DXP.
Confirm the selection with Create.

Fig. 47: Selecting an EDS file for TBEN-S2-2RFID-4DXP

50 Hans Turck GmbH & Co. KG | T +49 208 4952-0 | F +49 208 4952-264 | [email protected] | www.turck.com
Assign a module name.
Enter the IP address.

Fig. 48: Setting the module name and IP address

05.00 | 2019/11 51
Commissioning
Connecting a device to an EtherNet/IP™ controller

Select an integer as a format for the input data and output data: Click Change Ò In the
following window select INT.

Fig. 49: Selecting an integer as a format for the input data and output data

52 Hans Turck GmbH & Co. KG | T +49 208 4952-0 | F +49 208 4952-264 | [email protected] | www.turck.com
Optional: Set the connection and port configuration.

Fig. 50: Setting the connection

Fig. 51: Setting the port configuration

05.00 | 2019/11 53
Commissioning
Connecting a device to an EtherNet/IP™ controller

The device appears in the project tree.

Fig. 52: TBEN-S2-2RFID-4DXP in the project tree

54 Hans Turck GmbH & Co. KG | T +49 208 4952-0 | F +49 208 4952-264 | [email protected] | www.turck.com
7.3.3 Connecting the device online with the controller
Select the controller.
Click Go online.

Fig. 53: Connecting the device online

05.00 | 2019/11 55
Commissioning
Connecting a device to an EtherNet/IP™ controller

In the following window click (Connect To Go Online) Download.

Fig. 54: Click Download

Confirm all the following messages.

56 Hans Turck GmbH & Co. KG | T +49 208 4952-0 | F +49 208 4952-264 | [email protected] | www.turck.com
7.3.4 Reading out process data
Select Controller Tags in the project tree.

Fig. 55: Controller tags in the project tree

Parameter data (tben_2rfid:C), input data (tben_2rfid:I1) and output data (tben_2rfid:O1) can
be accessed.

Fig. 56: Access to parameter data, input data and output data

05.00 | 2019/11 57
Commissioning
Connecting a device to an EtherNet/IP™ controller

Example: Process input data – Tag in detection range of read/write head

In the following example a tag is located in the detection range of the read/write head. The
process data can be interpreted by means of the mapping.

Fig. 57: Process input data – Example

58 Hans Turck GmbH & Co. KG | T +49 208 4952-0 | F +49 208 4952-264 | [email protected] | www.turck.com
7.3.5 EtherNet/IP™ – Mapping
Description Assembly instance Size (words)
Input 103 191
Output 104 154

RFID channels – Parameter data

Description Register Bit offset Bit length
Channel 1 Channel 2
Operating mode 0x000A 0x0041 0 8
Select tag type 0x000B 0x0042 0 8
Bridging time 0x000C 0x0043 0 16
HF: Multitag mode 0x000D 0x0044 0 1
HF: Heartbeat read/write head 0x000E 0x0045 0 1
RS 485 terminating resistor 0x000F 0x0046 0 1
Automatic tuning of read/write head 0x0011 0x0047 0 1
Deactivate diagnostic HF read/write 0x0012 0x0048 0 1
head tuning
Diagnostic input filter 0x0013 0x0049 0 1
Command repetitions in the event of 0x0014 0x004A 0 8
an error
HF: Command in Continuous mode 0x0015 0x004B 0 8
HF: Length in Continuous mode 0x0016 0x004C 0 16
HF: Address in Continuous mode 0x0018 0x004E 0 32
Length of read data 0x003C 0x0072 0 16
Length of write data 0x003E 0x0074 0 16
HF bus mode: Activate read/write 0x001C 0x0052 0 1
head 1
HF bus mode: Activate read/write 0x001D 0x0053 0 1
head 2
HF bus mode: Activate read/write 0x001E 0x0054 0 1
head 3
… … … … 1
HF bus mode: Activate read/write 0x003B 0x0071 0 1
head 32

05.00 | 2019/11 59
Commissioning
Connecting a device to an EtherNet/IP™ controller

60 Hans Turck GmbH & Co. KG | T +49 208 4952-0 | F +49 208 4952-264 | [email protected] | www.turck.com
RFID channels – Process output data
Description Word offset Bit offset Bit length
Channel 1 Channel 2
Command code 0x0001 0x004D 0 16
Loop counter 0x0002 0x004E 0 8
Memory area (only UHF) 0x0002 0x004E 8 8
Start address 0x0003 0x004F 0 32
Length 0x0005 0x0051 0 16
Length UID/EPC 0x0006 0x0052 0 8
Read/write head address 0x000B 0x0057 0 8
Timeout 0x0007 0x0053 0 16
Read fragment no. 0x0008 0x0054 0 8
Write fragment no. 0x0008 0x0054 8 8
Write data Byte 0 0x000D 0x0059 0 8
Write data Byte 1 0x000D 0x0059 8 8
… … … … 8
Write data Byte 14 0x0014 0x0060 0 8
Write data Byte 15 0x0014 0x0060 8 8
… … … … 8
Write data Byte 64 0x002D 0x0079 0 8
Write data Byte 65 0x002D 0x0079 8 8
… … … … 8
Write data Byte 126 0x004C 0x0098 0 8
Write data Byte 127 0x004C 0x0098 8 8

05.00 | 2019/11 61
Commissioning
Connecting a device to an EtherNet/IP™ controller

RFID diagnostic data

Description Register Bit offset Bit length
Channel 1 Channel 2
Overvoltage at power supply ter- 0x0099 0x00AB 7 1
minal VAUX
Parameter error 0x0099 0x00AB 6 1
Configuration via the DTM active 0x0099 0x00AB 4 1
Buffer full 0x0099 0x00AB 4 1
Read/write head 1 detuned 0x009B 0x00AD 4 1
Read/write head 2 detuned 0x009B 0x00AD 12 1
… … … 0 1
Read/write head 31 detuned 0x00AA 0x00BC 4 1
Read/write head 32 detuned 0x00AA 0x00BC 12 1
Parameter not supported by read/ 0x009B 0x00AD 5 1
write head 1.
Parameter not supported by read/ 0x009B 0x00AD 13 1
write head 2.
… … … … 1
Parameter not supported by read/ 0x00AA 0x00BC 5 1
write head 31.
Parameter not supported by read/ 0x00AA 0x00BC 13 1
write head 32.
Read/write head 1 reports error 0x009B 0x00AD 6 1
Read/write head 2 reports error 0x009B 0x00AD 14 1
… … … … 1
Read/write head 31 reports error 0x00AA 0x00BC 6 1
Read/write head 32 reports error 0x00AA 0x00BC 14 1
Expected read/write head 1 not con- 0x009B 0x00AD 7 1
nected
Expected read/write head 2 not con- 0x009B 0x00AD 15 1
nected
… … … … 1
Expected read/write head 31 not con- 0x00AA 0x00BC 7 1
nected
Expected read/write head 32 not con- 0x00AA 0x00BC 15 1
nected

62 Hans Turck GmbH & Co. KG | T +49 208 4952-0 | F +49 208 4952-264 | [email protected] | www.turck.com
DXP channels – Parameter data
Description Register Bit offset Bit length
DXP 4 – Manual reset of the output 0x0076 0 1
after an overcurrent
DXP 5 – Manual reset of the output 0x0077 0 1
after an overcurrent
DXP 6 – Manual reset of the output 0x0078 0 1
after an overcurrent
DXP 7 – Manual reset of the output 0x0079 0 1
after an overcurrent
DXP 4 – Active output 0x007A 0 1
DXP 5 – Active output 0x007B 0 1
DXP 6 – Active output 0x007C 0 1
DXP 7 – Active output 0x007D 0 1
DXP 4 – Extended digital function 0x007E 0 1
DXP 4 – Input filter 0x007E 0 1
DXP 4 – Pulse extension (*10 ms) 0x007F 0 8
DXP 5 – Extended digital function 0x0082 0 1
DXP 5 – Input filter 0x0083 0 1
DXP 5 – Pulse extension (*10 ms) 0x0084 0 8
DXP 6 – Extended digital function 0x0086 0 1
DXP 6 – Input filter 0x0087 0 1
DXP 6 – Pulse extension (*10 ms) 0x0088 0 8
DXP 7 – Extended digital function 0x008A 0 1
DXP 7 – Input filter 0x0139 0 1
DXP 7 – Pulse extension (*10 ms) 0x008B 0 8

Digital channels – Input data

Description Word offset Bit offset Bit length
Input value channel 4 0x00BD 4 1
Input value channel 5 0x00BD 5 1
Input value channel 6 0x00BD 6 1
Input value channel 7 0x00BD 7 1

Digital channels – Output data

Description Word offset Bit offset Bit length
Output value channel 4 0x0099 4 1
Output value channel 5 0x0099 5 1
Output value channel 6 0x0099 6 1
Output value channel 7 0x0099 7 1

05.00 | 2019/11 63
Commissioning
Connecting a device to an EtherNet/IP™ controller

Digital channels – diagnostic messages

Description Word offset Bit offset Bit length
Overvoltage at power supply ter- 0x00BE 2 1
minal VAUX channel 4/5
Overvoltage at VAUX power supply 0x00BE 3 1
terminal channel 6/7
Overvoltage at output (channel 4) 0x00BE 12 1
Overvoltage at output (channel 5) 0x00BE 13 1
Overvoltage at output (channel 6) 0x00BE 14 1
Overvoltage at output (channel 7) 0x00BE 15 1

Module status – Diagnostic messages

Description Word offset Bit offset Bit length
Module diagnostic available 0 0 1
ARGEE project active 0 1 1
Undervoltage V2 0 7 1
Undervoltage V2 0 9 1
Internal error 0 10 1
Force mode active in the DTM 0 14 1

64 Hans Turck GmbH & Co. KG | T +49 208 4952-0 | F +49 208 4952-264 | [email protected] | www.turck.com
7.3.6 Activating QuickConnect (QC)
The devices support QuickConnect. QuickConnect enables the controller to establish connec-
tions to EtherNet/IP™ nodes in less than 500 ms after the EtherNet/IP™ network is switched on.
This requires the fast startup of the devices, particularly with fast tool changers on robot arms,
e.g. in the automobile industry.
The startup time for the RFID interfaces is < 150 ms.
QuickConnect can be activated via the web server of the device or in RS Logix via the configura-
tion assembly or class instance attributes.

NOTE
The activation of QuickConnect causes the automatic adaption of all necessary port
properties.

Port property State

Autonegotiation Deactivated
Transmission speed 100BaseT
Duplex Full duplex
Topology linear
AutoMDIX Deactivated

Notes on the correct connection of the Ethernet cables in QuickConnect applications are
provided in [} 20]

05.00 | 2019/11 65
Commissioning
Connecting a device to an EtherNet/IP™ controller

Activating QuickConnect via the configuration assembly

The configuration assembly is part of the assembly class of the device.
Configure the configuration assembly in RSLogix.
Activate QuickConnect via byte 9, bit 0 = 1 in the controller tags.

Fig. 58: Configuring the configuration assembly in RSLogix

Activating QuickConnect via the class instance attribute

Activate QuickConnect via the class instance attribute as follows:
Class Instance Attribute Value
0xF5 0x01 0x0C 0: deactivated (default)
1: activated

66 Hans Turck GmbH & Co. KG | T +49 208 4952-0 | F +49 208 4952-264 | [email protected] | www.turck.com
Activating QuickConnect via the web server
Tick the Activate Quick Connect check box in the web server.

Fig. 59: Activating QuickConnect in the web server

05.00 | 2019/11 67
Commissioning
Connecting a device to a Siemens PROFINET controller

7.4 Connecting a device to a Siemens PROFINET controller

The following example describes the connection of the device to a Siemens controller in
PROFINET with the SIMATIC STEP7 Professional V13 programming software (TIA Portal).

Hardware used
This example uses the following hardware components:
n Siemens S7-1500 controller
n TBEN-S2-2RFID-4DXP block module
n TN-Q80-H1147 HF read/write head

Software used
This example uses the following software:
n SIMATIC STEP7 Professional V13 (TIA Portal)
n GSDML file for TBEN-S2-2RFID-4DXP (download free of charge from www.turck.com)

Prerequisites
n The programming software has been started.
n A new project has been created.
n The PLC has been added to the project.

68 Hans Turck GmbH & Co. KG | T +49 208 4952-0 | F +49 208 4952-264 | [email protected] | www.turck.com
7.4.1 Installing a GSDML file
The GSDML file is available free of charge for download from www.turck.com.
Include the GSDML file: Click Options Ò Manage general station description files
(GSD).

Fig. 60: Include the GSDML file

05.00 | 2019/11 69
Commissioning
Connecting a device to a Siemens PROFINET controller

Install a GSDML file: Enter the memory location of the GSDML file and click Install.
a The device is included in the hardware catalog of the programming software.

Fig. 61: Installing a GSDML file

70 Hans Turck GmbH & Co. KG | T +49 208 4952-0 | F +49 208 4952-264 | [email protected] | www.turck.com
7.4.2 Connecting the device with the controller
Select the RFID interface from the hardware catalog and drag it to the hardware window.
Connect the device with the controller in the hardware window.

Fig. 62: Connecting the device with the controller

05.00 | 2019/11 71
Commissioning
Connecting a device to a Siemens PROFINET controller

7.4.3 Assigning the PROFINET device name

Choose Online accesses Ò Online & diagnostics.
Choose Functions Ò Assign PROFINET device name.
Assign the required PROFINET device name.

Fig. 63: Assigning the PROFINET device name

7.4.4 Set the IP address in the TIA Portal

Choose Device View Ò Properties tab Ò Ethernet addresses.
Assign the required IP address.

Fig. 64: Assigning the IP address

72 Hans Turck GmbH & Co. KG | T +49 208 4952-0 | F +49 208 4952-264 | [email protected] | www.turck.com
7.4.5 Connecting the device online with the controller
Start online mode (connect online).
a The device was successfully linked to the controller.

Fig. 65: Online mode

05.00 | 2019/11 73
Commissioning
Connecting a device to a Siemens PROFINET controller

7.4.6 Setting module parameters

Choose Device view Ò Device overview.
Select the module to be set.
Click Properties Ò General Ò Module parameters.
Set the station parameters.

Fig. 66: Setting module parameters

7.4.7 PROFINET – Mapping

The PROFINET mapping is the same as the data mapping described in the “Settings” chapter.

74 Hans Turck GmbH & Co. KG | T +49 208 4952-0 | F +49 208 4952-264 | [email protected] | www.turck.com
8 Setting
The device can be controlled, read and set via parameter data, process input data, process out-
put data and diagnostic data. The following table shows the data mapping:
Socket Channel Parameter data Process input data Process output data Diagnostic data
Bytes Meaning Bytes Meaning Bytes Meaning
0 GW 0…1 Parameters 0…1 Diagnostics
GW GW
1 0 0…31 RFID para- 0…23 Input data 0…23 Output data 0…36 Diagnostics
meters RFID RFID RFID chan-
nel
2 0 32…33 Length of 24…151 Read data
read data
3 0 34…35 Length of 24…151 Write data
write data
4 1 36…37 RFID para- 152…175 Input data 152…175 Output data 36…76 Diagnostics
meters RFID RFID RFID chan-
nel
5 1 68…69 Length of 176…303 Read data
read data
6 1 70…71 Length of 176…303 Write data
write data
7 Diag 304…375 Diagnostics
CHx of RFID
channels
8 4DXP 72…73 Parameters 376…377 Input data 304…305 Output data 72…73 Diagnostics
Basic DXP DXP DXP DXP
9 4DXP 378…379 Error mes-
Diag sages DXP
10 EXT 74…75 Settings DXP
LEAN
11 EXT 76…77 Settings DXP
LEAN
12 EXT 78…79 Settings DXP
LEAN
13 EXT 80…81 Settings DXP
LEAN
14 Module 380…381 Module
status status

05.00 | 2019/11 75
Setting
RFID channels – Parameter data

76 Hans Turck GmbH & Co. KG | T +49 208 4952-0 | F +49 208 4952-264 | [email protected] | www.turck.com
8.1.1 Meaning of the parameter bits
The default values of the firmware, the DTM and the EDS file are shown in bold type. The de-
fault values for PROFINET may differ.
Designation Meaning
Operating mode (OMRFID) 0: Deactivated
1: HF compact
2: HF extended
3: HF bus mode
4: UHF compact
5: UHF extended
Tag type (TAGTYPE) 0: Automatic detection
1: NXP I-Code SLI/SL2
2: Fujitsu MB89R118
3: TI Tag-it HF-I Plus
4: Infineon SRF55V02P
5: NXP I-CODE SLI S
6: Fujitsu MB89R119
7: TI Tag-it HF-I
8: Infineon SRF55V10P
9: Reserved
10: Reserved
11: NXP I-CODE SLI L
12: Fujitsu MB89R112
13: EM4233SLIC
Read/write heads with firmware from V1.91 also support:
14: NXP SLIX2
15: TI Tag-it HFI Pro
16: Turck sensor tag
17: Infineon SRF55V02S
18: Infineon SRF55V10S
19: EM4233
20: EM4237
21: EM4237 SLIC
22: EM4237 SLIX
23: EM4033
Bridging time (BYPASS) Bridging time in ms, adjustable from 4…1020 ms, default setting: 200 ms
Automatic tuning of 0: Automatic tuning off
read/write head (AT) 1: Automatic tuning on
RS 485 terminating resistor 0: RS485 terminating resistor off
(TERM) 1: RS485 terminating resistor on
In HF bus mode the RS485 bus terminating resistor is activated by default.
HF: Heartbeat read/write head The device confirms its operational readiness via a signal which is sent at regular
(HB) intervals to the controller. NOTE: A heartbeat slows down the system since a
heartbeat and another command cannot be executed simultaneously.
0: Heartbeat read/write head off
1: Heartbeat read/write head on
HF: Multitag mode (ANTI) 0: Multitag mode off
1: Multitag mode on
Diagnostic input filter (DID) 0: All diagnostic messages on
1: Diagnostic messages off
Deactivate diagnostic HF read/ 0: Diagnostic messages of the read/write head on
write head tuning (DXD) 1: Diagnostic messages of the read/write head off

05.00 | 2019/11 77
Setting
RFID channels – Parameter data

Designation Meaning
HF: Idle mode (HFIDLEMODE) Defines which data is to be displayed in idle mode (not available in the EDS file)
0: UID
1: 8 bytes of user data memory
2: UID and 8 bytes of user memory
3: UID and 64 bytes of user memory
Command repetitions in the Number of command repetitions after an error message, default setting: 2
event of an error (CRET)
HF: Command in Continuous 0x01: Inventory
mode (CCM) 0x02: Read
0x03: Tag info
0x04: Write
HF: Length in Continuous mode Number of bytes that still have to be read or written in Continuous mode, default
(LCM) setting: 8
HF: Address in Continuous mode Start address of the USER memory area on the tag to be read or written, default
(ACM) setting: 0
HF bus mode: Activate read/ 0: Deactivate read/write head
write head (XCVR0…XCVR31) 1: Activate read/write head
In HF bus mode all connected and addressed read/write heads are deactivated
by default and must be activated in the parameters.
Length of write data (WDS) Size of the write data, default setting depends on the selected interface and field-
bus
Length of read data (RDS) Size of the read data, default setting depends on the selected interface and field-
bus

78 Hans Turck GmbH & Co. KG | T +49 208 4952-0 | F +49 208 4952-264 | [email protected] | www.turck.com
8.1.2 HF applications – Selecting the tag type
In multitag applications select a tag type for executing the read and write commands.
The automatic tag detection is not supported for the read and write commands in multi-
tag mode.
The tag types that can be selected depends on the firmware of the connected read/write head.
The firmware version of the read/write head can be read with the Read/write head identifica-
tion command.

NOTE
The firmware version of the interface up to 3.3.5.0 only displays in the web server, in
the associated DTM as well as in the catalog and GSDML files those tags that were
detected by read/write heads with a firmware version up to 1.90. The tags shown in
the table below can be detected irrespective of this.

If a tag is selected that is not supported by the firmware of the connected read/write head, the
RFID interface outputs the “Length outside of tag specification” error.
The tag type does not have to be selected in single tag applications and for inventory com-
mands in multitag applications if the read/write head detects the tags automatically.
Tag Firmware status Firmware status Selectable Automatic Indicated in the
Read/write head interface detection web server, DTM,
possible GSDML and
catalog files
1: NXP Icode SLIX ≥ V1.91 ≥ V3.4.1.0 x x x
≥ V1.91 ≤ V3.3.5.0 x x x
≤ V1.90 all x x x
2: Fujitsu ≥ V1.91 ≥ V3.4.1.0 x x x
MB89R118 ≥ V1.91 ≤ V3.3.5.0 x x x
≤ V1.90 all x x x
3: TI Tag-it HF-I ≥ V1.91 ≥ V3.4.1.0 x x x
Plus ≥ V1.91 ≤ V3.3.5.0 x x x
≤ V1.90 all x x x
4: Infineon SR- ≥ V1.91 ≥ V3.4.1.0 x x x
F55V02P ≥ V1.91 ≤ V3.3.5.0 x x x
≤ V1.90 all x x x
5: NXP Icode SLIX- ≥ V1.91 ≥ V3.4.1.0 x x x
S ≥ V1.91 ≤ V3.3.5.0 x x x
≤ V1.90 all x – x
6: Fujitsu ≥ V1.91 ≥ V3.4.1.0 x x x
MB89R119 ≥ V1.91 ≤ V3.3.5.0 x x x
≤ V1.90 all x – x
7: TI Tag-it HF-I ≥ V1.91 ≥ V3.4.1.0 x x x
≥ V1.91 ≤ V3.3.5.0 x x x
≤ V1.90 all x – x
8: Infineon SR- ≥ V1.91 ≥ V3.4.1.0 x x x
F55V10P ≥ V1.91 ≤ V3.3.5.0 x x x
≤ V1.90 all x – x

05.00 | 2019/11 79
Setting
RFID channels – Parameter data

Tag Firmware status Firmware status Selectable Automatic Indicated in the

Read/write head interface detection web server, DTM,
possible GSDML and
catalog files
11: NXP Icode ≥ V1.91 ≥ V3.4.1.0 x x x
SLIX-L ≥ V1.91 ≤ V3.3.5.0 x x x
≤ V1.90 all x – x
12: Fujitsu ≥ V1.91 ≥ V3.4.1.0 x x x
MB89R112 ≥ V1.91 ≤ V3.3.5.0 x x x
≤ V1.90 all x – x
13: EM4233SLIC ≥ V1.91 ≥ V3.4.1.0 x x x
≥ V1.91 ≤ V3.3.5.0 x x x
≤ V1.90 all x – x
14: NXP SLIX2 ≥ V1.91 ≥ V3.4.1.0 x x x
≥ V1.91 ≤ V3.3.5.0 – x –
≤ V1.90 all – – –
15: TI Tag-it HFI ≥ V1.91 ≥ V3.4.1.0 – x x
Pro ≥ V1.91 ≤ V3.3.5.0 – x –
≤ V1.90 all – – –
16: Turck sensor ≥ V1.91 ≥ V3.4.1.0 x x x
tag ≥ V1.91 ≤ V3.3.5.0 – x –
≤ V1.90 all – – –
17: Infineon SR- ≥ V1.91 ≥ V3.4.1.0 x x x
F55V02S ≥ V1.91 ≤ V3.3.5.0 – x –
≤ V1.90 all – – –
18: Infineon SR- ≥ V1.91 ≥ V3.4.1.0 x x x
F55V10S ≥ V1.91 ≤ V3.3.5.0 – x –
≤ V1.90 all – – –
19: EM4233 ≥ V1.91 ≥ V3.4.1.0 x x x
≥ V1.91 ≤ V3.3.5.0 – x –
≤ V1.90 all – – –
20: EM4237 ≥ V1.91 ≥ V3.4.1.0 x x x
≥ V1.91 ≤ V3.3.5.0 – x –
≤ V1.90 all – – –
21: EM4237 SLIC ≥ V1.91 ≥ V3.4.1.0 x x x
≥ V1.91 ≤ V3.3.5.0 – x –
≤ V1.90 all – – –
22: EM4237 SLIX ≥ V1.91 ≥ V3.4.1.0 x x x
≥ V1.91 ≤ V3.3.5.0 – x –
≤ V1.90 all – – –
23: EM4033 ≥ V1.91 ≥ V3.4.1.0 x x x
≥ V1.91 ≤ V3.3.5.0 – x –
≤ V1.90 all – – –

80 Hans Turck GmbH & Co. KG | T +49 208 4952-0 | F +49 208 4952-264 | [email protected] | www.turck.com
8.1.3 HF applications – Setting the bridging time (bypass time)
Due to the expansion of the HF transmission zone the tag may drop out momentarily during a
write or read operation and then later return again. The period between the dropout and the
return to the transmission zone must be bridged so that the write or read operation is com-
pleted. The bridging time is the time between the dropout and the return to the detection
range. The Bridging time parameter takes up 1 word in the parameter data image and is stated
in ms.
The bridging time can be set between 4…1020 ms. The bridging time parameter depends on
the components used, the write/read distances, the speed of the tag to the read/write head
and other external factors.
The following figure shows the typical characteristics of the detection range and the path
covered by the read/write head. A shows the section to be bridged:

Fig. 67: Detection range of a read/write head

Retaining the default setting

The default setting for the bridging time is 200 ms. In HF bus mode the default value is 48 ms.
Retaining the default setting: If the commissioning is successful, the parameter does not
have to be adjusted to the application. If the commissioning is not successful, an error
message will appear.
If an error message appears, adjust the bridging time. If the bridging time cannot be ad-
justed, reduce the speed or the data volume.

The information “Recommended distance” and “Maximum distance” is provided in the

product-specific data sheet as well as in the RFID engineering manual (D500024).

Adapting the bridging time to the application

Measure the required bridging time directly on location. The LEDs of the read/write head
and the TP status bit of process input data indicate whether the tag is in the detection
range or not.
Enter the required bridging time.

05.00 | 2019/11 81
Setting
RFID channels – Parameter data

8.1.4 HF applications – Setting HF bus mode

NOTE
In HF bus mode a command is only meant for one read/write head. While the com-
mand is being executed, there is no data communication with other read/write
heads.

HF bus mode supports the HF read/write heads from firmware version Vx.90. Continuous HF
bus mode supports HF read/write heads from firmware version Vx.93. The read/write heads can
be addressed as follows:
n Automatic addressing
n Manual addressing via the Set HF read/write head address command
n Manual addressing via the Turck Service Tool

The addresses must be assigned per channel from 1 to 32.

Addressing read/write heads automatically

NOTE
Turck recommends making the bus address of the read/write head visible on the
device.

Read/write heads with the default bus address 68 can be automatically addressed. For this the
corresponding XCVR bit must be set in the parameter data.
Switch on the RFID interface power supply.
Activate the required read/write heads in the parameter data via the appropriate XCVR
bit.
Connect the read/write heads to the interface in a line one by one.
a The read/write heads are automatically assigned addresses in ascending order in the or-
der of connection. The lowest address is automatically assigned to the next connected
read/write head with the default address 68.
a The addressing is successful if the LED of the read/write head is permanently lit.

82 Hans Turck GmbH & Co. KG | T +49 208 4952-0 | F +49 208 4952-264 | [email protected] | www.turck.com
Manually addressing read/write heads – Set read/write head address command

NOTE
Turck recommends making the bus address of the read/write head visible on the
device.

For information on addressing the read/write heads via the RFID interface with the Set HF read/
write head address command see page [} 126]. With manual addressing via the Set HF read/
write head address command, the read/write heads must not be activated until the addressing
is completed.
Activate the required read/write heads in the parameter data via the appropriate XCVR
bit.

HF RFID read/write head RFID interface PC / Notebook

e.g. TN-CK40-H1147/C53 TBEN-S2-2RFID-4DXP with Ethernet interface

RFID cable Ethernet cable

e.g. RK4.5T-…-RS4.5T/S2500 e.g. RSSD-RJ45…

Fig. 68: Connecting the read/write head to a PC via the RFID interface

05.00 | 2019/11 83
Setting
RFID channels – Parameter data

Addressing read/write heads manually via the Turck Service Tool

NOTE
Turck recommends making the bus address of the read/write head visible on the
device.

The following accessories are required to address the read/write heads in HF bus mode via the
Turck Service Tool. Accessories are not supplied with the device and must be ordered separ-
ately.
n STW-RS485-USB interface converter (Ident No. 7030354)
n STW-RS485-USB-PS power supply unit (Ident No. 7030355)

Connect the read/write head to the interface converter using a suitable connection cable
(e.g. RK4.5T-2/S2500) according to the following color coding:
STW-RS485-USB …/S2500 …/S2501 …/S2503
plug connectors plug connectors plug connectors
VCC Brown (BN) Brown (BN) Red (RD)
GND Blue (BU) Blue (BU) Black (BK)
RS485-A White (WH) Black (BK) White (WH)
RS485-B Black (BK) White (WH) Blue (BU)

Connect a USB cable to the interface converter (USB1.1 type B).

Connect the open end of the USB cable to a free USB port on the PC
(USB1.1 type A).
Set the switches on the side of the interface converter for the termination to [ON].
Connect the interface converter via the STW power supply unit to a power supply.

UHF RFID read/write head Interface converter PC / Notebook

e.g. TN-CK40-H1147/C53 STW-RS485-USB with USB-interface

RFID cable Power supply

e.g. RK4.5T/S2500 STW-RS485-USB-PS

Fig. 69: Connecting the read/write head via the interface converter with a PC

Launch the Turck Service Tool.

Click Actions or press [F4].
Click Set HF RFID Reader Bus Address.

84 Hans Turck GmbH & Co. KG | T +49 208 4952-0 | F +49 208 4952-264 | [email protected] | www.turck.com
Fig. 70: Function selection – Set HF RFID reader bus address

The HF-RFID Reader Setup Tool window opens.

05.00 | 2019/11 85
Setting
RFID channels – Parameter data

Select the COM port to which the interface converter is connected.

Click Read.
a The found read/write head is displayed in the status message.

Fig. 71: Window – HF-RFID Reader Setup Tool

Enter the required address.

Click Change.
a The new set address is displayed in the status message.

Fig. 72: Changing the read/write head

86 Hans Turck GmbH & Co. KG | T +49 208 4952-0 | F +49 208 4952-264 | [email protected] | www.turck.com
Activate the required read/write heads in the parameter data via the appropriate XCVR
bit.

05.00 | 2019/11 87
Setting
RFID channels – Parameter data

8.1.5 UHF applications – Setting Continuous presence sensing mode

Set adaptions to the Presence sensing behavior in the DTM.
Optional: Set the grouping of the EPCs via the Start address parameter:
0: Grouping inactive
1: Grouping active (same EPC is not recorded again, only the counter incremented in the
header)
Execute the Continuous presence sensing mode command.
a The read/write head is switched to Presence sensing mode and sends all received data to
the interface as soon as at least one tag is located in the detection range.
a The data received from the read/write head is stored in the FIFO memory of the interface.
Send the Idle command (0x0000) in order to then read data from the buffer of the inter-
face.

NOTE
The Continuous presence sensing mode command also stays active after the Idle
command is sent.

To pass on data from the FIFO memory of the interface to the controller, execute the Get
data from buffer (0x0011) command. The length of the data must be less than or equal
to the value of the available data bytes (BYFI). Depending on the length of the data, it is
no longer used for grouping.

NOTE
If Grouping is active: Only read data from the buffer if the number of available bytes
is stable. If stable data was fetched, the command can be terminated by means of a
reset since the grouping is no longer based on the fetched data and therefore old
EPCs can be detected again.

Do not carry out the reset until the data has been successfully read from the buffer.
To end Continuous presence sensing mode and clear the FIFO memory of the interface
send the Reset command (0x0800).

8.1.6 UHF applications – Transferring read/write head settings

The Backup function enables the settings of a UHF read/write head to be transferred, e.g. when
swapping a device.

Execute the Backup settings of the UHF read/write head command.

a The settings for the read/write head are saved in the interface.
Replace the read/write head.
Execute the Restore UHF read/write head settings command.
a The data stored in the interface is transferred to the read/write head.

88 Hans Turck GmbH & Co. KG | T +49 208 4952-0 | F +49 208 4952-264 | [email protected] | www.turck.com
8.2 RFID channels – Process input data

Process input data – HF compact and UHF compact modes

Byte no. Bit
PROFINET Modbus 7 6 5 4 3 2 1 0
EtherNet/
IP™
0 0 Response code (RESC)
1 1
2 2 Loop counter for rapid processing (RCNT)
3 3 Reserved
4 4 TNCx TREx PNSx XDx TP1
5 5 CMON TON
6 6 Length (LEN)
7 7
8 8 Error code (ERRC)
9 9
10 10 Tag counter (TCNT)
11 11
12 24 Read data Byte 0
13 25 Read data Byte 1
14 26 Read data Byte 2
15 27 Read data Byte 3
16 28 Read data Byte 4
17 29 Read data Byte 5
18 30 Read data Byte 6
19 31 Read data Byte 7
… … …
139 151 Read data Byte 127

05.00 | 2019/11 89
Setting
RFID channels – Process input data

Process input data – HF extended and UHF extended modes

Byte no. Bit
PROFINET Modbus 7 6 5 4 3 2 1 0
EtherNet/
IP™
0 0 Response code (RESC)
1 1
2 2 Loop counter for rapid processing (RCNT)
3 3 Reserved
4 4 TNCx TREx PNSx XDx TPx
5 5 CMON TON
6 6 Length (LEN)
7 7
8 8 Error code (ERRC)
9 9
10 10 Tag counter (TCNT)
11 11
12 12 Data (bytes) available (BYFI)
13 13
14 14 Read fragment no.
15 15 Write fragment no.
16 16 Reserved
17 17 Reserved
18 18 Reserved
19 19 Reserved
20 24 Read data Byte 0
21 25 Read data Byte 1
22 26 Read data Byte 2
23 27 Read data Byte 3
24 28 Read data Byte 4
25 29 Read data Byte 5
26 30 Read data Byte 6
27 31 Read data Byte 7
… … …
146 151 Read data Byte 127

90 Hans Turck GmbH & Co. KG | T +49 208 4952-0 | F +49 208 4952-264 | [email protected] | www.turck.com
Process input data – HF bus mode
Byte no. Bit
PROFINET 7 6 5 4 3 2 1 0
0 Response code (RESC)
1
2 Loop counter for rapid processing (RCNT)
3 Reserved
4 TNCx TREx PNSx XDx TP1
5 CMON TON
6 Length (LEN)
7
8 Error code (ERRC)
9
10 Tag counter (TCNT)
11
12 Data (bytes) available (BYFI)
13
14 Read fragment no.
15 Write fragment no.
16 Reserved
17 Reserved
18 Reserved
19 Reserved
20 TP8 TP7 TP6 TP5 TP4 TP3 TP2 TP1
21 TP16 TP15 TP14 TP13 TP12 TP11 TP10 TP9
22 TP24 TP23 TP22 TP21 TP20 TP19 TP18 TP17
23 TP32 TP31 TP30 TP29 TP28 TP27 TP26 TP25
24 Read data Byte 0
25 Read data Byte 1
26 Read data Byte 2
27 Read data Byte 3
28 Read data Byte 4
29 Read data Byte 5
30 Read data Byte 6
31 Read data Byte 7
… …
151 Read data Byte 127

05.00 | 2019/11 91
Setting
RFID channels – Process input data

8.2.1 Meaning of the status bits

Default values are shown in bold type.
Designation Meaning
Response code (RESC) Display of the last command executed
Loop counter for rapid Output of the command code requested by the loop counter
processing (RCNT)
Expected read/write head not 0: Read/write head expected by system connected
connected with address x (TNCx) 1: Read/write head expected by the system not connected (HF bus mode: Read/
write head at address x)
Read/write head at address x re- 0: No error
ports error (TREx) 1: Error message of the read/write head (HF bus mode: Read/write head at ad-
dress x)
Parameter not supported by 0: No error
read/write head at address x 1: Parameter not supported by read/write head (HF bus mode: Read/write head
(PNSx) at address x)
HF read/write head at address x 0: No error
detuned (XDx) 1: Read/write head detuned (HF bus mode: Read/write head at address x)
Tag within the detection range 0: No tag in detection range of read/write head
(TPx) 1: Tag in detection range of read/write head
HF read/write head switched on 0: Read/write head switched off
(TON) 1: Read/write head switched on
Continuous (presence sensing 0: Continuous mode not active
mode) active (CMON) 1: Continuous mode active
Length (LEN) Display of the length of the read data
Error code (ERRC) Display of the specific error code if the error bit (ERROR) is set
Tag counter (TCNT) Display of the detected tags. With HF multitag applications and UHF only tags
are counted that are read with an Inventory command. In HF single-tag applica-
tions all tags are counted that are detected by the read/write head. The tag
counter is reset by the following commands:
n Inventory (exception: HF single-tag applications)
n Continuous mode
n Continuous presence sensing mode
n Reset
Data (bytes) available (BYFI) Shows the number of bytes in the FIFO memory of the interface.
(only available with HF extended Ascending: New data from a tag read or received by the device
and UHF extended modes) Descending: Execution of a command completed
Error message 0xFFFF: Memory overfilled, data loss of new data likely
Read fragment no. (RFN) If the data to be read exceeds the size of the read data memory, the data is di-
(only available with HF extended vided in max. 256 fragments. The fragments are numbered consecutively from
and UHF extended modes) 1…255. From fragment number 256 numbering starts again at 1. The sending of
a fragment is confirmed by the device if the read fragment number appears in
the process input data. After the confirmation the next fragment is read.
0: No fragmentation
In Idle mode the size of fragments is stated. With a read command the number of
the fragments containing data is stated.

92 Hans Turck GmbH & Co. KG | T +49 208 4952-0 | F +49 208 4952-264 | [email protected] | www.turck.com
Designation Meaning
Write fragment no. (WFN) If the data to be written exceeds the size of the write data memory, the data is di-
vided in max. 256 fragments. The fragments are numbered consecutively from
1…255. From fragment number 256 numbering starts again at 1.
The sending of a fragment is confirmed by the device if the write fragment num-
ber appears in the process input data. After the confirmation the next fragment
is written.
0: No fragmentation
In Idle mode the size of fragments is stated. With a write command the number
of the fragments is stated that contain data.
TP1…TP32 Tag in detection range of the connected read/write head (only available in HF
bus mode)
Read data User-defined read data

05.00 | 2019/11 93
Setting
RFID channels – Process input data

8.2.2 Tag in detection range (TP) – Using bit or pre-loading the command
The Tag in detection range bit is set automatically if a read/write head detects a tag.

In HF applications the bit is set by default in all operating modes and in Idle mode. To set the
bit in Idle mode in UHF applications, the read/write head must be set to Presence sensing
mode via the DTM.

All commands can be sent irrespective of whether the Tag in detection range bit (TP) is set. If
no tag is present in the detection range when the command is sent, the command is executed
by a rising edge at TP. A command is executed immediately if there is a tag in the detection
range at the time of sending.

NOTE
If the read/write head detects a new tag in the detection range, the Tag in detection
range bit and the UID are indicated at the same time in Idle mode. If two tags are de-
tected in quick succession, the TP bit may remain set. The UID of the second tag is
displayed.

94 Hans Turck GmbH & Co. KG | T +49 208 4952-0 | F +49 208 4952-264 | [email protected] | www.turck.com
8.3 RFID channels – Process output data

Process output data – HF compact and UHF compact modes

Byte no. Bit
PROFINET Modbus 7 6 5 4 3 2 1 0
EtherNet/
IP™
0 0 Command code (CMDC)
1 1
2 2 Loop counter for rapid processing (RCNT)
3 3 Memory area (DOM) – only available with UHF applications
4 4 Start address (ADDR)
5 5
6 6
7 7
8 8 Length (LEN)
9 9
10 10 Length UID/EPC (SOUID)
11 11 Reserved
12 24 Write data Byte 0
13 25 Write data Byte 1
14 26 Write data Byte 2
15 27 Write data Byte 3
16 28 Write data Byte 4
17 29 Write data Byte 5
18 30 Write data Byte 6
19 31 Write data Byte 7
… … …
139 151 Write data Byte 127

05.00 | 2019/11 95
Setting
RFID channels – Process output data

Writing process output data – HF extended and UHF extended modes

Byte no. Bit
PROFINET Modbus 7 6 5 4 3 2 1 0
EtherNet/
IP™
0 0 Command code (CMDC)
1 1
2 2 Loop counter for rapid processing (RCNT)
3 3 Memory area (DOM) – only available with UHF applications
4 4 Start address (ADDR)
5 5
6 6
7 7
8 8 Length (LEN)
9 9
10 10 Length UID/EPC (SOUID)
11 11 Reserved
12 12 Timeout (TOUT)
13 13
14 14 Read fragment number (RFN)
15 15 Write fragment number (WFN)
16 16 Reserved
17 17 Reserved
18 18 Reserved
19 19 Reserved
20 24 Write data Byte 0
21 25 Write data Byte 1
22 26 Write data Byte 2
23 27 Write data Byte 3
24 28 Write data Byte 4
25 29 Write data Byte 5
26 30 Write data Byte 6
27 31 Write data Byte 7
… … …
139 151 Write data Byte 127

96 Hans Turck GmbH & Co. KG | T +49 208 4952-0 | F +49 208 4952-264 | [email protected] | www.turck.com
Writing process output data – HF bus mode
Byte no. Bit
7 6 5 4 3 2 1 0
0 Command code (CMDC)
1
2 Loop counter for rapid processing (RCNT)
3 Memory area (DOM) – only available with UHF applications
4 Start address (ADDR)
5
6
7
8 Length (LEN)
9
10 Length UID/EPC (SOUID)
11 reserved
12 Timeout (TOUT)
13
14 Read fragment number (RFN)
15 Write fragment number (WFN)
16 reserved
17 reserved
18 reserved
19 reserved
20 Read/write head address (ANTN) – only available with HF applications
21 reserved
22 reserved
23 reserved
24 Write data Byte 0
25 Write data Byte 1
26 Write data Byte 2
27 Write data Byte 3
28 Write data Byte 4
29 Write data Byte 5
30 Write data Byte 6
31 Write data Byte 7
… …
139 Write data Byte 127

05.00 | 2019/11 97
Setting
RFID channels – Process output data

8.3.1 Meaning of the command bits

Description Meaning
Command code (CMDC) Enter the command code
Loop counter for rapid pro- Loop counter for repeated processing of a command
cessing (LCNT) 0: Loop counter off
Memory area (DOM) – only use- 0: Kill password
ful for UHF applications (with HF 1: EPC
applications the setting has no 2: TID
effect) 3: USER area
4: Access password
5: PC (size of EPC)
Start address (ADDR) in bytes Enter the address where a command is to be sent (e.g. memory area of a tag)
Length (LEN) in bytes Enter the length of the data to be read or written
Length UID/EPC (SOUID) in bytes Inventory command:
0: The actual length (bytes) of the transferred UID or EPC is transferred with an in-
ventory.
> 0 in HF applications:
n 8: Return message 8 bytes UID
n 1…7: Return message of an abbreviated UID
n > 8: Error message
> 0 in UHF applications: EPC completely output.
-1: NEXT mode (only available in HF single-tag applications): An HF tag is always
only read, written or protected if the UID is different to the UID of the last read or
written tag.
Other commands:
Enter UID or EPC size in bytes, if a particular tag is read, written or protected. The
UID or EPC must be defined in the write data. (start byte: 0). The function of the
length of the UID/EPC depends on the command used.
0: No entry of a UID/EPC for executing the command. Only one tag can be loc-
ated in the detection range of the read/write head.
> 0: EPC length of the tag to be read, written or protected if an EPC is present in
the write data.
-1: NEXT mode (only available in HF single-tag applications): A tag is always only
read, written or protected if the UID/EPC is different to the UID/EPC of the last
read or written tag.
Timeout (TOUT) Time in ms in which one command is to be executed. If a command is not ex-
ecuted within the entered time, the device outputs an error message.
0: No timeout, command stays active until it is executed
0 (UHF application): No timeout, command stays active until the first tag was
read
1: Command is executed once (if there is already a tag in the detection range)
> 1…65535: Time in ms
HF Inventory: Command executed once in the specified time (exception: Con-
tinuous Mode)
UHF inventory: Command active for the entire specified time

98 Hans Turck GmbH & Co. KG | T +49 208 4952-0 | F +49 208 4952-264 | [email protected] | www.turck.com
Description Meaning
Read fragment no. (RFN) If the data to be read exceeds the size of the read data memory, the data is di-
vided in max. 256 fragments. The fragments are numbered consecutively from
1…255. From fragment number 256 numbering starts again at 1. The sending of
a fragment is confirmed by the device if the read fragment number appears in
the process input data. After the confirmation the next fragment is read.
0: No fragmentation
In Idle mode the size of fragments is stated. With a read command the number of
the fragments containing data is stated.
Write fragment no. (WFN) If the data to be written exceeds the size of the write data memory, the data is di-
vided in max. 256 fragments. The fragments are numbered consecutively from
1…255. From fragment number 256 numbering starts again at 1.
The sending of a fragment is confirmed by the device if the write fragment num-
ber appears in the process input data. After the confirmation the next fragment
is written.
0: No fragmentation
In Idle mode the size of fragments is stated. With a write command the number
of the fragments is stated that contain data.
Read/write head address HF bus mode: Address of the read/write head, if several bus-capable read/write
heads are connected
UHF: Values are ignored or set automatically.
Write data User-defined write data or entry of a UID or EPC to select a specific tag for the
command execution (if the Length of UID/EPC (SOUID) command parameter is
greater than 0)

05.00 | 2019/11 99
Setting
Digital channels – Setting advanced parameters (EXT LEAN)

8.4 Digital channels – Parameter data

Byte no. Bit
7 6 5 4 3 2 1 0
0 SRO7 SRO6 SRO5 SRO4
1 OE7 OE6 OE5 OE4

8.4.1 Meaning of the parameter bits

Default values are shown in bold type.
Designation Meaning
Manual reset of the output after 0: The output automatically switches back on after an overcurrent.
an overcurrent (SRO…) 1: The output only switches back on after the overcurrent after the overcurrent is
removed and the switch signal is reset.
OEx… 0: Output deactivated
1: Output activated

8.5 Digital channels – Setting advanced parameters (EXT LEAN)

Byte no. Bit
7 6 5 4 3 2 1 0
0 DIFT DMOD (Byte 1...7)
1 IST (Byte 0...8)

8.5.1 Meaning of the parameter bits

Default values are shown in bold type.
Designation Meaning
Input filter (DIFT) An input filter makes it possible to set how long a change in the input has to be
present until it is transferred to the input data.
0: 0.2 ms
1: 3 ms
Advanced digital function 0: deactivated
(DMOD) 1: Digital filter and pulse extension activated
Pulse extension (IST) Pulse extension: 0…2550 ms (adjustable in 10 ms steps), default value: 10 ms

100 Hans Turck GmbH & Co. KG | T +49 208 4952-0 | F +49 208 4952-264 | [email protected] | www.turck.com
8.6 Digital channels – Process input data
Byte no. Bit
7 6 5 4 3 2 1 0
0 DXP7 DXP6 DXP5 DXP4
1

8.6.1 Meaning of the status bits

Default values are shown in bold type.
Designation Meaning
DXP4 0: Digital channel 1 not active
1: Digital channel 1 active
DXP5 0: Digital channel 2 not active
1: Digital channel 2 active
DXP6 0: Digital channel 3 not active
1: Digital channel 3 active
DXP7 0: Digital channel 4 not active
1: Digital channel 4 active

8.7 Digital channels – Process output data

Byte no. Bit
7 6 5 4 3 2 1 0
0 DXP7 DXP6 DXP5 DXP4
1

8.7.1 Meaning of the command bits

Default values are shown in bold type.
Designation Meaning
DXP4 0: Switch off digital channel 1
1: Switch off digital channel 1
DXP5 0: Switch off digital channel 2
1: Switch on digital channel 2
DXP6 0: Switch off digital channel 3
1: Switch off digital channel 3
DXP7 0: Switch off digital channel 4
1: Switch on digital channel 4

05.00 | 2019/11 101

Setting
RFID channels – Overview of commands

8.8 RFID channels – Overview of commands

RFID commands are initiated via the command code in the process output data of an RFID
channel. The commands can be executed with or without a loop counter function. The loop
counter must be set individually for each new command.

NOTE
After commands are executed without the loop counter function, the device must
be reset to the Idle state before a new command is sent.
After a command is executed, send an idle command to the device.

Command Command code Possible for

hex. dec. HF HF HF UHF UHF
compact extended bus mode compact extended
Idle 0x0000 0 x x x x x
Inventory 0x0001 1 x x x x x
Fast inventory 0x2001 8193 x x x x x
Read 0x0002 2 x x x x x
Fast read 0x2002 8194 x x x x x
Write 0x0004 4 x x x x x
Fast write 0x2004 8196 x x x x x
Write and verify 0x0008 8 x x x x x
Continuous mode 0x0010 16 – x* – – x
Get data from buffer 0x0011 17 – x – – x
(Continuous mode)
Get data from buffer with fast com- 0x2011 8209 – x – – x
mand processing
(Continuous mode)
Continuous presence sensing mode 0x0020 32 – – – – x
End Continuous 0x0012 18 – x* – – x
(presence sensing) mode
Read/write head identification 0x0041 65 x x x x x
Switch off HF read/write head 0x0040 64 x x x – –
HF read/write head tuning 0x0080 128 x x x – –
Query HF read/write head 0x0070 112 – – x – –
address
Set HF read/write head address 0x0071 113 – – x – –
Direct read/write head command 0x0060 96 x x x x x
Direct read/write head command 0x2060 8288 x x x x x
with fast command processing
Set tag password 0x0102 258 x** x** x** x x
Set tag password with fast command 0x2102 8450 x** x** x** x x
processing
Set read/write head password 0x0100 256 x** x** x** x x
Reset read/write head password 0x0101 257 x** x** x** x x
Set tag protection 0x0103 259 x** x** x** x x
Set tag protection with 0x2103 8451 x** x** x** x x
fast command processing

102 Hans Turck GmbH & Co. KG | T +49 208 4952-0 | F +49 208 4952-264 | [email protected] | www.turck.com
Command Command code Possible for
hex. dec. HF HF HF UHF UHF
compact extended bus mode compact extended
Query HF tag 0x0104 260 x** x** x** x x
protection status
Set permanent lock (Lock) 0x0105 261 x x x x x
Set permanent lock with fast com- 0x2105 8453 x x x x x
mand processing
Tag info 0x0050 80 x x x x x
Tag info with fast command 0x2050 8272 x x x x x
processing
Kill UHF tag 0x0200 512 – – – x x

Kill UHF tag with 0x2200 8704 – – – x x

fast command
processing
Restore UHF read/write head settings 0x1000 4096 – – – x x
Backup settings of the UHF read/ 0x1001 4097 – – – x x
write head
Query error/status of UHF read/write 0x0042 66 – – – x x
head
Reset 0x8000 32768 x x x x x

* With automatic tag type detection Continuous mode only supports the inventory command.
** The command is only supported by the TW-R…-M-B146 tags.

05.00 | 2019/11 103

Setting
RFID channels – Overview of commands

8.8.1 Command: Idle

The Idle command switches the interface to Idle mode. The command execution is aborted. If a
tag is in the detection range of an HF read/write head and single-tag mode is set, the Tag in de-
tection range bit is set and the UID of the tag is indicated by default in the read data area.
Which data is to be displayed can be set via the DTM, PROFINET or Modbus register. The follow-
ing options are possible:
n UID
n 8 bytes of user data memory
n UID and 8 bytes of user memory
n UID and 64 bytes of user memory
n Deactivated
The read data is overwritten with the next tag in the detection range.

In UHF applications the EPC is indicated if the read/write head is set directly in Presence sensing
mode via the DTM.

Request
Loop counter Not required
Command code 0x0000 (hex.), 0 (dec.)
Read/write head address Not required
Length UID/EPC Not required
Start address Not required
Length Not required
Command timeout Not required
Write fragment no. Not required
Read fragment no. Not required
Write data Not required

Response
Loop counter See description of the input data, [} 92]
Response code 0x0000 (hex.), 0 (dec.)
Length Length of the UID/EPC of the tag in the detection range
Error code See description of the input data, [} 92]
Tag within the See description of the input data, [} 92]
detection range
Data (bytes) available See description of the input data, [} 92]
Tag counter See description of the input data, [} 92]
Write fragment no. Size of the fragments
Read fragment no. Size of the fragments
Read data, Bytes 0…n UID/EPC of the tag in the detection range

104 Hans Turck GmbH & Co. KG | T +49 208 4952-0 | F +49 208 4952-264 | [email protected] | www.turck.com
8.8.2 Command: Inventory
The Inventory command causes the read/write head to search for tags in the detection range
and read the UID, EPC of the tags, or if activated in the UHF read/write head, the RSSI. The In-
ventory command can be executed in single-tag mode and in multitag mode. NEXT mode is
only possible in single-tag mode.

NOTE
The command code for fast processing with the loop counter is 0x2001 (hex.) or
8193 (dec.).

Request
Loop counter See description of the output data, [} 98]
Command code 0x0001 (hex.), 1 (dec.)
Read/write head address See description of the output data, [} 98]
Length UID/EPC Not required
Start address 1: Grouping of the EPCs active (only UHF)
0: Grouping of the EPCs inactive (only UHF)
Length 0: The actual length (bytes) of the transferred UID or EPC is
transferred with an inventory.
> 0 in HF applications:
n 8: Return message 8 bytes UID
n 1…7: Return message of an abbreviated UID
n > 8: Error message
> 0 in UHF applications: EPC completely output.
-1: NEXT mode (only available in HF single-tag applications):
An HF tag is always only read, written or protected if the UID
is different to the UID of the last read or written tag.
Command timeout See description of the output data, [} 98]
Write fragment no. 0
Read fragment no. See description of the output data, [} 98]
Write data Not required

Response (HF)
Loop counter See description of the input data, [} 92]
Response code 0x0001 (hex.), 1 (dec.)
Length Length of the read data in bytes
Error code See description of the input data, [} 92]
Tag within the See description of the input data, [} 92]
detection range
Data (bytes) available See description of the input data, [} 92]
Tag counter Ascending
Write fragment no. 0
Read fragment no. See description of the input data, [} 92]
Read data, Bytes 0…n UID

05.00 | 2019/11 105

Setting
RFID channels – Overview of commands

Response (UHF)
Loop counter See description of the input data, [} 92]
Response code 0x0001 (hex.), 1 (dec.)
Length Length of the read data
Error code See description of the input data, [} 92]
Tag within the See description of the input data, [} 92]
detection range
Data (bytes) available See description of the input data, [} 92]
Tag counter Ascending
Write fragment no. 0
Read fragment no. See description of the input data, [} 92]
Read data, Bytes 0…n See example: UHF read data

Data format in UHF applications

The UHF read data is formatted by means of a header. The header has the following structure:
Type Name Meaning
uint8_t Size Data size
uint8_t Block type 1: UID/EPC/RSSI etc.
2: Read data
other values : reserved
uint8_t Data [size] EPC/RSSI etc. or read data

The size of EPC/RSSI etc. depends on the settings of the read/write head.

Reading out the RSSI value

The RSSI value is output in binary code in 2 bytes and corresponds to the two's complement of
the output binary code. Mapped to a signed integer, the 2 bytes output correspond to ten
times the actual RSSI value. Refer to the following table for an example of the RSSI value:

MSB…LSB MSB…LSB Two’s complement RSSI (dBm)

(decimal) (binary)
252 253 11111100 11111101 -771 -77.1

Example: UHF read data (header and EPC, grouping deactivated)

Type Name Meaning
uint8_t Size 12
uint8_t Block type 1
uint8_t Data [14] uint8_t EPC [12]

106 Hans Turck GmbH & Co. KG | T +49 208 4952-0 | F +49 208 4952-264 | [email protected] | www.turck.com
Example: UHF read data (header and EPC, grouping activated)
Type Name Meaning
uint8_t Size 14
uint8_t Block type 1
uint8_t Data [14] uint8_t EPC [12]
uint16_t Number of the read operations (LSB
Ò MSB) [2]

Example: UHF read data (header and EPC, grouping with RSSI activated)
Type Name Meaning
uint8_t Size 16
uint8_t Block type 1
uint8_t Data [18] uint8_t EPC [12]
uint16_t RSSI [2]
uint16_t Number of the read operations (LSB
Ò MSB) [2]

Byte Content Meaning

0 Data size (EPC + number of read opera- 2 bytes header
tions)
1 UHF memory range
3…13 EPC 12 bytes EPC
14 LSB 2 bytes RSSI
15 MSB
16 LSB 2 bytes Number of read operations
17 MSB

05.00 | 2019/11 107

Setting
RFID channels – Overview of commands

Example: UHF read data (header, EPC, grouping with RSSI, socket, time, phase activated)
Type Name Meaning
uint8_t Size 24
uint8_t Block type 1
uint8_t Data [24] uint8_t EPC [12]
uint16_t RSSI (LSB Ò MSB)
uint16_t Socket (LSB Ò MSB)
uint32_t Time (LSB Ò MSB)
uint16_t Phase (LSB Ò MSB)
uint16_t Number of the read operations (LSB
Ò MSB)

108 Hans Turck GmbH & Co. KG | T +49 208 4952-0 | F +49 208 4952-264 | [email protected] | www.turck.com
8.8.3 Read command
The Read command causes the read/write head to read the data of tags in the detection range.
128 bytes are transferred in a read operation by default. Larger data volumes can be transferred
in fragments. If a particular UID or EPC is entered, the read/write head only reads the appropri-
ate tags. All other tags in the detection range are ignored in this case.

NOTE
The command code for fast processing with the loop counter is 0x2002 (hex.) or
8194 (dec.).

Request
Loop counter See description of the output data, [} 98]
Command code 0x0002 (hex.), 2 (dec.)
Memory area See description of the output data, [} 98]
Read/write head address See description of the output data, [} 98]
Length UID/EPC Enter UID or EPC size in bytes, if a particular tag is to be read.
The UID or EPC must be defined in the write data. (start byte:
0). The function of the length of the UID/EPC depends on
the command used.
0: No entry of a UID/EPC for executing the command. Only
one tag can be located in the detection range of the read/
write head.
> 0: EPC length of the tag to be read if an EPC is present in
the write data
-1: NEXT mode: A tag is always only read if the UID/EPC is dif-
ferent to the UID/EPC of the last read or written tag.
Start address Start address of the memory area on the tag to be read
(entry in bytes)
Length Length of the data to be read in bytes
Command timeout See description of the output data, [} 98]
Write fragment no. 0
Read fragment no. See description of the output data, [} 98]
Write data, Byte 0…(size of the UID or EPC of the tag to be read
UID/EPC-1)
Write data, Byte (size of the EPC) Not required
…127

05.00 | 2019/11 109

Setting
RFID channels – Overview of commands

Response
Loop counter See description of the input data, [} 92]
Response code 0x0002 (hex.), 2 (dec.)
Length Length of the read data
Error code See description of the input data, [} 92]
Tag within the See description of the input data, [} 92]
detection range
Data (bytes) available Increases during command execution
Tag counter See description of the input data, [} 92]
Write fragment no. 0
Read fragment no. See description of the input data, [} 92]
Read data, Bytes 0…n Read data

110 Hans Turck GmbH & Co. KG | T +49 208 4952-0 | F +49 208 4952-264 | [email protected] | www.turck.com
8.8.4 Command: Write
The Write command causes the read/write head to write data to tags in the detection range.
128 bytes are transferred in a write operation by default. Larger data volumes can be trans-
ferred in fragments. If a particular UID or EPC is entered, the read/write head only reads the ap-
propriate tags. All other tags in the detection range are ignored in this case.

NOTE
With multitag applications enter the UID or EPC of the tag to be written.

NOTE
The command code for fast processing with the loop counter is 0x2004 (hex.) or
8196 (dec.).

Request
Loop counter See description of the output data, [} 98]
Command code 0x0004 (hex.), 4 (dec.)
Memory area See description of the output data, [} 98]
Read/write head address See description of the output data, [} 98]
Length UID/EPC Enter UID or EPC size in bytes, if a particular tag is to be writ-
ten. The UID or EPC must be defined in the write data. (start
byte: 0). The function of the length of the UID/EPC depends
on the command used.
0: No entry of a UID/EPC for executing the command. Only
one tag can be located in the detection range of the read/
write head.
> 0: EPC length of the tag to be written if an EPC is present in
the write data
-1: NEXT mode: A tag is always only written if the UID/EPC is
different to the UID/EPC of the last read or written tag.
Start address Start address of the memory area on the tag to be written
(entry in bytes)
Length Length of the data to be written in bytes
Command timeout See description of the output data, [} 98]
Write fragment no. 1: Using fragmentation
0: Do not use fragmentation
Read fragment no. 0
Write data, Byte 0…(size of the UID or EPC of the tag to be written
UID/EPC-1)
Write data, Byte (size of the EPC) Write data
…127

05.00 | 2019/11 111

Setting
RFID channels – Overview of commands

Response
Loop counter See description of the input data, [} 92]
Response code 0x0004 (hex.), 4 (dec.)
Length Length of the read data
Error code See description of the input data, [} 92]
Tag within the See description of the input data, [} 92]
detection range
Data (bytes) available Increases during command execution
Tag counter See description of the input data, [} 92]
Write fragment no. See description of the input data, [} 92]
Read fragment no. 0
Read data, Byte 0...127 Not required

112 Hans Turck GmbH & Co. KG | T +49 208 4952-0 | F +49 208 4952-264 | [email protected] | www.turck.com
8.8.5 Command: Write and verify
The Write and verify command writes a number of bytes defined by the user. The written data
is also sent back to the interface and verified. 128 bytes are transferred by default in a write op-
eration. Larger data volumes can be transferred in fragments. The written data is only verified in
the interface and is not sent back to the controller. If the verification fails, an error message is
output. If the command is processed without an error message, the data was verified success-
fully.

NOTE
With multitag applications enter the UID or EPC of the tag to be written.

NOTE
The command code for fast processing with the loop counter is 0x2008 (hex.) or
8200 (dec.).

Request
Loop counter See description of the output data, [} 98]
Command code 0x0008 (hex.), 8 (dec.)
Memory area See description of the output data, [} 98]
Read/write head address See description of the output data, [} 98]
Length UID/EPC Enter UID or EPC size in bytes, if a particular tag is to be writ-
ten. The UID or EPC must be defined in the write data. (start
byte: 0). The function of the length of the UID/EPC depends
on the command used.
0: No entry of a UID/EPC for executing the command. Only
one tag can be located in the detection range of the read/
write head.
> 0: EPC length of the tag to be written if an EPC is present in
the write data
-1: NEXT mode: A tag is always only written if the UID/EPC is
different to the UID/EPC of the last read or written tag.
Start address Start address of the memory area on the tag to be written
(entry in bytes)
Length Length of the data to be written in bytes
Command timeout See description of the output data, [} 98]
Write fragment no. 1: Using fragmentation
0: Do not use fragmentation
Read fragment no. 0
Write data, Byte 0…(size of the optional: UID or EPC of the tag to be written
UID/EPC-1)
Write data, Byte (size of the EPC) Write data
…127

05.00 | 2019/11 113

Setting
RFID channels – Overview of commands

Response
Loop counter See description of the input data, [} 92]
Response code 0x0008 (hex.), 8 (dec.)
Length Length of the read data
Error code See description of the input data, [} 92]
Tag within the See description of the input data, [} 92]
detection range
Data (bytes) available Increases during command execution
Tag counter See description of the input data, [} 92]
Write fragment no. See description of the input data, [} 92]
Read fragment no. 0
Read data, Not required
Byte 0…MIN (127, set length-1)

114 Hans Turck GmbH & Co. KG | T +49 208 4952-0 | F +49 208 4952-264 | [email protected] | www.turck.com
8.8.6 Command: Continuous mode

NOTE
Continuous mode is only available in HF applications for single-tag applications. The
repeated reading of the same tag is edge-triggered.

In Continuous mode, a user-defined command is sent to the read/write head and saved in the
read/write head. With HF the following values can be set: Write, read, inventory, tag info. With
UHF the commands write, read and inventory can be executed in Continuous mode. With UHF
applications the parameters for Continuous mode must be set via the DTM directly in the read/
write head.
The command is continuously executed until the user terminates Continuous mode. Continu-
ous mode can be terminated with a reset command.

NOTE
The reset command resets all read data.

Read/write heads in Continuous mode send all command related data to the interface. The
data is stored in the FIFO memory of the interface and can be queried by the controller via the
Get data from buffer command.
Commands in Continuous mode are triggered if the read/write head detects a tag. If there is a
tag in the detection range of the read/write head when Continuous mode is started, the com-
mand sent in Continuous mode is executed with the next tag.

NOTE
In Continuous mode the Tag in detection range signal is not updated.
Start address and length cannot be changed during the execution of Continuous
mode.
After Continuous mode is restarted, all data of the already running Continuous
mode is deleted.

Request
Loop counter See description of the output data, [} 98]
Command code 0x0010 (hex.), 16 (dec.)
Read/write head address See description of the output data, [} 98]
Length UID/EPC Not required
Start address UHF Inventory
1: Grouping of the EPCs active
0: Grouping of the EPCs inactive
>1: Not defined
HF bus mode
1: Grouping of the UIDs active
0: Grouping of the UIDs inactive
>1: Not defined
Length Not required
Command timeout Not required
Write fragment no. 0
Read fragment no. See description of the output data, [} 98]
Write data Not required

05.00 | 2019/11 115

Setting
RFID channels – Overview of commands

Response
Loop counter See description of the input data, [} 92]
Response code 0x0010 (hex.), 16 (dec.)
Length 0
Error code See description of the input data, [} 92]
Tag within the See description of the input data, [} 92]
detection range
Data (bytes) available Increases during command execution
Tag counter Increases with each read or written UID/EPC
Write fragment no. 0
Read fragment no. See description of the input data, [} 92]
Read data See description of the input data, [} 92]

116 Hans Turck GmbH & Co. KG | T +49 208 4952-0 | F +49 208 4952-264 | [email protected] | www.turck.com
8.8.7 Command: Get data from buffer command (Continuous mode/Continuous presence
sensing mode)

NOTE
The command code for fast processing with the loop counter is 0x2011 (hex.) or
8209 (dec.).

The Get data from buffer command (Continuous mode) passes on data stored in the interface
to the controller. The command is required to transfer read data to the controller in Continuous
mode or in Continuous presence sensing mode. The data is transferred to the controller in frag-
ments of up to 128 bytes. The size of the fragments can be set by the user. A UID or EPC is not
divided by fragment limits. If a UID or EPC does not fit completely in a fragment, it is automatic-
ally moved to the next fragment.

NOTE
The Get data from buffer command does not end Continuous mode.

Request
Loop counter See description of the output data, [} 98]
Command code 0x0011 (hex.), 17 (dec.)
Read/write head address See description of the output data, [} 98]
Length UID/EPC Not required
Start address Not required
Length Max. length of the data to be read by the device (≤ size of
the data that the device has actually stored), entered in
bytes
Command timeout See description of the output data, [} 98]
Write fragment no. 0
Read fragment no. See description of the output data, [} 98]
Write data Not required

Response
Loop counter See description of the input data, [} 92]
Response code 0x0011 (hex.), 17 (dec.)
Length Length of the read data. The data is stated in complete
blocks.
Error code See description of the input data, [} 92]
Tag within the See description of the input data, [} 92]
detection range
Data (bytes) available Is automatically decreased after the execution of the com-
mand
Tag counter See description of the input data, [} 92]
Write fragment no. 0
Read fragment no. See description of the input data, [} 92]
Read data Read data

05.00 | 2019/11 117

Setting
RFID channels – Overview of commands

Data format in UHF applications

The size of EPC/RSSI etc. depends on the settings of the read/write head.

Example: UHF read data (header and EPC, grouping deactivated)

Type Name Meaning
uint8_t Size 12
uint8_t Block type 1
uint8_t Data [14] uint8_t EPC [12]

Example: UHF read data (header and EPC, grouping activated)

Type Name Meaning
uint8_t Size 14
uint8_t Block type 1
uint8_t Data [14] uint8_t EPC [12]
uint16_t Number of the read operations (LSB
Ò MSB) [2]

118 Hans Turck GmbH & Co. KG | T +49 208 4952-0 | F +49 208 4952-264 | [email protected] | www.turck.com
Data format in HF applications
In HF applications the data is not formatted by means of a header. Some examples of HF data
are listed below.

Example: UID, grouping deactivated

Type Name Meaning
uint8_t Data [8] uint8_t UID [8]

Example: UID, grouping activated

Type Name Meaning
uint8_t Data [10] uint8_t UID [8]
uint16_t Number of the read operations

Example: Successful read command (64 bytes)

Type Name Meaning
uint8_t Data [64] uint8_t Read data [64]

Example: Successful write command

Type Name Meaning
uint8_t Data [2] uint16_t Error code 0x0000

Example: Error when writing data

Type Name Meaning
uint8_t Data [2] uint16_t Error code 0x0201

Example: UID, grouping deactivated, HF bus mode

Type Name Meaning
uint8_t Data [8] uint16_t UID [8]
uint8_t Reserved Reserved
uint8_t Address Address of the read/write head

Example: UID, grouping deactivated, HF bus mode

Type Name Meaning
uint8_t Data [64] uint16_t UID [64]
uint8_t Reserved Reserved
uint8_t Address Address of the read/write head

05.00 | 2019/11 119

Setting
RFID channels – Overview of commands

8.8.8 Command: Continuous presence sensing mode (UHF)

In Continuous presence sensing mode, a user-defined command (write, read, inventory) is sent
to the UHF read/write head and saved in the read/write head. The read/write heads are auto-
matically switched on in Continuous presence sensing mode as soon as a tag is located in the
detection range. The duration of the scan interval and the on time can be adjusted in the set-
tings of the UHF read/write head. The command is continuously executed until the user termin-
ates Continuous presence sensing mode by executing a reset command.

NOTE
The reset command resets all read data.

Read/write heads in Continuous presence sensing mode send all command related data to the
interface. The data is stored in the buffer of the interface and can be queried by the controller
via the Get data from buffer command. In Continuous presence sensing mode the Tag in de-
tection range signal is not permanently updated.
Request
Loop counter See description of the output data, [} 98]
Command code 0x0020 (hex.), 32 (dec.)
Read/write head address See description of the output data, [} 98]
Length UID/EPC Not required
Start address 0: Grouping inactive
1: Grouping active
>1: Not defined
Length Not required
Command timeout Not required
Write fragment no. 0
Read fragment no. See description of the output data, [} 98]
Write data Not required

Response
Loop counter See description of the input data, [} 92]
Response code 0x0020 (hex.), 32 (dec.)
Length Not required
Error code See description of the input data, [} 92]
Tag within the See description of the input data, [} 92]
detection range
Data (bytes) available Increases during command execution
Tag counter Increases with each read or written UID/EPC
Write fragment no. 0
Read fragment no. See description of the input data, [} 92]
Read data See description of the input data, [} 92]

120 Hans Turck GmbH & Co. KG | T +49 208 4952-0 | F +49 208 4952-264 | [email protected] | www.turck.com
8.8.9 Command: End Continuous (presence sensing) mode
Continuous and presence sensing mode can be stopped via the Shut down Continuous (pres-
ence sensing) mode command. The data in the buffer of the interface is not deleted after the
command is executed and can still be called up by the controller via the Get data from buffer
command.
Request
Loop counter See description of the output data, [} 98]
Command code 0x0012 (hex.), 18 (dec.)
Read/write head address Not required
Length UID/EPC Not required
Start address Not required
Length Not required
Command timeout See description of the output data, [} 98]
Write fragment no. 0
Read fragment no. See description of the output data, [} 98]
Write data Not required

Response
Loop counter See description of the input data, [} 92]
Response code 0x0012 (hex.), 18 (dec.)
Length Not required
Error code See description of the input data, [} 92]
Tag within the See description of the input data, [} 92]
detection range
Data (bytes) available See description of the input data, [} 92]
Tag counter See description of the input data, [} 92]
Write fragment no. 0
Read fragment no. See description of the input data, [} 92]
Read data Not required

05.00 | 2019/11 121

Setting
RFID channels – Overview of commands

8.8.10 Command: Read/write head identification

The Read/write head identification command scans the following parameters of the connec-
ted read/write head:
n Ident No.
n Serial number
n Hardware version
n Firmware status
The parameters are contained in the read/write head in the identification record.
Request
Loop counter See description of the output data, [} 98]
Command code 0x0041 (hex.), 65 (dec.)
Read/write head address See description of the output data, [} 98]
Length UID/EPC Not required
Start address Start address in the identification record, stated in bytes
Length Length of the data to be scanned
0: Read complete parameter set
Command timeout Not required
Write fragment no. Not required
Read fragment no. See description of the output data, [} 98]
Write data Not required

Response
Loop counter See description of the input data, [} 92]
Response code 0x0041 (hex.), 65 (dec.)
Length See description of the input data, [} 92]
Error code See description of the input data, [} 92]
Tag within the See description of the input data, [} 92]
detection range
Data (bytes) available See description of the input data, [} 92]
Tag counter Increases with each read or written UID/EPC
Write fragment no. 0
Read fragment no. See description of the input data, [} 92]
Read data, Byte 0...19 Ident No.: ARRAY [0…19] of BYTE
Read data, Byte 20...35 Serial number: ARRAY [0…15] of BYTE
Read data, Byte 36...37 Hardware version: INT16 (Little Endian)
Read data, Byte 38...41 Firmware status: ARRAY [0…] of BYTE: V (0x56), x, y, z (Vx.y.z)
Read data, Byte 42...119 Not required

122 Hans Turck GmbH & Co. KG | T +49 208 4952-0 | F +49 208 4952-264 | [email protected] | www.turck.com
8.8.11 Command: Switch off HF read/write head
The Switch off HF read/write head command enables HF read/write heads to be switched off
until a write or read command is present. The switching on and off of the read/write heads may
be necessary if the devices are mounted very closely together and the detection ranges over-
lap. When a command is executed the read/write heads are automatically reactivated. After the
command is executed, the read/write head is switched off again.
Request
Loop counter See description of the output data, [} 98]
Command code 0x0040 (hex.), 64 (dec.)
Read/write head address See description of the output data, [} 98]
Length UID/EPC Not required
Start address Not required
Length Not required
Command timeout See description of the output data, [} 98]
Write fragment no. 0
Read fragment no. See description of the output data, [} 98]
Write data Not required

Response
Loop counter See description of the input data, [} 92]
Response code 0x0040 (hex.), 64 (dec.)
Length Not required
Error code See description of the input data, [} 92]
Tag within the See description of the input data, [} 92]
detection range
Data (bytes) available See description of the input data, [} 92]
Tag counter See description of the input data, [} 92]
Write fragment no. 0
Read fragment no. See description of the input data, [} 92]
Read data Not required

05.00 | 2019/11 123

Setting
RFID channels – Overview of commands

8.8.12 Command: HF read/write head tuning

NOTE
The command is only available for the TNLR-… and TNSLR-… HF read/write heads.

The Read/write head tuning command enables HF read/write heads to be tuned automatically
to their ambient conditions. The tuning values are saved until the next voltage reset in the
read/write head.

HF read/write head tuning is carried out automatically by default after each voltage reset.
Request
Loop counter See description of the output data, [} 98]
Command code 0x0080 (hex.), 128 (dec.)
Read/write head address See description of the output data, [} 98]
Length UID/EPC Not required
Start address Not required
Length Not required
Command timeout See description of the output data, [} 98]
Write fragment no. 0
Read fragment no. See description of the output data, [} 98]
Write data Not required

Response
Loop counter See description of the input data, [} 92]
Response code 0x0080 (hex.), 128 (dec.)
Length 2
Error code See description of the input data, [} 92]
Tag within the See description of the input data, [} 92]
detection range
Data (bytes) available See description of the input data, [} 92]
Tag counter See description of the input data, [} 92]
Write fragment no. 0
Read fragment no. See description of the input data, [} 92]
Read data, Byte 0 Tuning value:
TNLR-…: 0x00…0x0F
TNSLR-…: 0x00…0x1F
Read data, Byte 1 empfangener Spannungswert (0x00…0xFF)

124 Hans Turck GmbH & Co. KG | T +49 208 4952-0 | F +49 208 4952-264 | [email protected] | www.turck.com
8.8.13 Command: Query HF read/write head address

NOTE
The command is only available in HF bus mode.

The interface can query the addresses of all connected HF read/write heads via the Query HF
read/write head address command. If a non-bus-compatible read/write head is connected, the
device outputs an error message.
Request
Loop counter See description of the output data, [} 98]
Command code 0x0070 (hex.), 112 (dec.)
Read/write head address Not required
Length UID/EPC Not required
Start address Not required
Length Not required
Command timeout See description of the output data, [} 98]
Write fragment no. 0
Read fragment no. See description of the output data, [} 98]
Write data Not required

Response
Loop counter See description of the input data, [} 92]
Response code 0x0070 (hex.), 112 (dec.)
Length Not required
Error code See description of the input data, [} 92]
Tag within the See description of the input data, [} 92]
detection range
Data (bytes) available See description of the input data, [} 92]
Tag counter See description of the input data, [} 92]
Write fragment no. 0
Read fragment no. See description of the input data, [} 92]
Read data, byte 0…[number of Addresses of the connected read/write heads (uint8_t)
the connected read/write heads]
Read data, byte [number of the Not required
connected read/write
heads] ...127

05.00 | 2019/11 125

Setting
RFID channels – Overview of commands

8.8.14 Command: Set HF read/write head address

NOTE
The command is only available in HF bus mode.
Only one bus-compatible read/write head can be connected to the interface during
command execution.
Deactivate read/write heads before manual addressing via the parameter data so
that automatic address assignment is not executed.

The address of HF bus-compatible read/write heads can be set via the Set HF read/write head
address command. Command execution does not depend on activation or an already set ad-
dress of a read/write head. An already existing read/write head address is overwritten.

Permissible values are 0, 1…32, 68.

If a non-bus-compatible read/write head is connected, the device outputs an error message.

Request
Loop counter See description of the output data, [} 98]
Command code 0x0071 (hex.), 113 (dec.)
Read/write head address Not required
Length UID/EPC Not required
Start address Not required
Length Not required
Command timeout See description of the output data, [} 98]
Write fragment no. 0
Read fragment no. See description of the output data, [} 98]
Write data, Byte 0 neue Schreib-Lese-Kopf-Adresse (uint8_t), zulässige Werte:
0, 1…32, 68
Write data, Byte 1...127 Not required

Response
Loop counter See description of the input data, [} 92]
Response code 0x0071 (hex.), 113 (dec.)
Length Not required
Error code See description of the input data, [} 92]
Tag within the See description of the input data, [} 92]
detection range
Data (bytes) available See description of the input data, [} 92]
Tag counter See description of the input data, [} 92]
Write fragment no. 0
Read fragment no. See description of the input data, [} 92]
Read data Not required

126 Hans Turck GmbH & Co. KG | T +49 208 4952-0 | F +49 208 4952-264 | [email protected] | www.turck.com
8.8.15 Direct read/write head command

NOTE
The command code for fast processing with the loop counter is 0x2060 (hex.) or
8288 (dec.).

A direct command enables commands from the read/write head protocol to be sent directly to
the read/write head. The commands are defined and interpreted by the entries in the write and
read data.

NOTE
The read/write head protocol is not part of this documentation and must be reques-
ted from Turck and specially released. Send any inquiries about the read/write head
protocol to Turck.

Request
Loop counter See description of the output data, [} 98]
Command code 0x0060 (hex.), 96 (dec.)
Read/write head address See description of the output data, [} 98]
Length UID/EPC 0
Start address Not required
Length Length of the description of the direct command in the
write data, entry in bytes
Command timeout See description of the output data, [} 98]
Write fragment no. 0
Read fragment no. See description of the output data, [} 98]
Write data Description of the direct command

Response
Loop counter See description of the input data, [} 92]
Response code 0x0060 (hex.), 96 (dec.)
Length Length of the description of the direct command in the
write data
Error code See description of the input data, [} 92]
Tag within the See description of the input data, [} 92]
detection range
Data (bytes) available See description of the input data, [} 92]
Tag counter See description of the input data, [} 92]
Write fragment no. 0
Read fragment no. See description of the input data, [} 92]
Read data Response to the direct command

05.00 | 2019/11 127

Setting
RFID channels – Overview of commands

Example: Direct command in HF applications (scan read/write head)

Request
Loop counter 0
Command code 0x0060
Read/write head address 0
Length UID/EPC 0
Start address 0
Length 2
Command timeout 200
Write fragment no. 0
Read fragment no. 0
Write data 0xE0 (CC), 0x00 (CI) – see BL ident® protocol

Response
Loop counter 0
Response code 0x0060
Length 6
Error code 0
Tag within the 0
detection range
Data (bytes) available 0
Tag counter 0
Write fragment no. 0
Read fragment no. 0
Read data 0xE0 (CC), 0x00 (CI), 0x04, 0x06, 0xA1, 0x77

The BL ident® protocol enables the following information to be scanned with the described
bytes:
n Byte 5 – read/write head ID: 4
n Byte 6 – Hardware version: 6
n Byte 7 – Software version x.y, y (A1)
n Byte 8 – Software version x.y, y (0x77)
n The entire software version information consists of Byte 7 and Byte 8 (A1v77).

128 Hans Turck GmbH & Co. KG | T +49 208 4952-0 | F +49 208 4952-264 | [email protected] | www.turck.com
Example: Direct command in UHF applications (scan read/write head version)
Request
Loop counter 0
Command code 0x0060
Read/write head address 0
Length UID/EPC 0
Start address 0
Length 2
Command timeout 200
Write fragment no. 0
Read fragment no. 0
Write data 0x02 (CMD), 0x00 (application) – see debus protocol

Response
Loop counter 0
Response code 0x0060
Length 12
Error code 0
Tag within the 0
detection range
Data (bytes) available 0
Tag counter 0
Write fragment no. 0
Read fragment no. 0
Read data 0x02, 0x00, 0x01, 0x02, 0x03, 0x04, 0x8B, 0x20, 0x00, 0x01,
0x00, 0x01

The debus protocol enables the read data to be interpreted as follows:

MSG ERR SNR0 SNR1 SNR2 SNR3 GTYP VERS HW
0x02 0x00 0x01 0x02 0x03 0x04 0x8B 0x00 0x00
0x20 0x01 0x01

n Serial number: 0x01020304

n Device type: 0x208B
n Software version: v1.00
n Hardware version: v1.00

Example: Direct command in UHF applications (set output power)

Read the set power from the RAM of the read/write head.
Request
Loop counter 0
Command code 0x0060
Read/write head address 0
Length UID/EPC 0

05.00 | 2019/11 129

Setting
RFID channels – Overview of commands

Request
Start address 0
Length 5
Command timeout 200
Write fragment no. 0
Read fragment no. 0
Write data 0x09 8A 4A 03 01

Change output power: Write “30 dBm” power in the RAM and flash memory of the read/
write head. The sixth byte of the write data sets the power in dBm as a hexadecimal
value.
Request
Loop counter 0
Command code 0x0060
Read/write head address 0
Length UID/EPC 0
Start address 0
Length 6
Command timeout 200
Write fragment no. 0
Read fragment no. 0
Write data 0x09 8A 3C 03 01 1E

The following table provides assistance in converting the power values from dBm to mW.
dBm mW dBm mW
1 1.25 16 40
2 1.6 17 50
3 2 18 63
4 2.5 19 80
5 3 20 100
6 4 21 125
7 5 22 160
8 6 23 200
9 8 24 250
10 10 25 316
11 13 26 400
12 16 27 500
13 20 28 630
14 25 29 800
15 32 30 1000

130 Hans Turck GmbH & Co. KG | T +49 208 4952-0 | F +49 208 4952-264 | [email protected] | www.turck.com
8.8.16 Command: Set tag password

NOTE
The command is only available for applications with UHF tags and the HF tags TW-
R…-M-B146.

NOTE
The command code for fast processing with the loop counter is 0x2102 (hex.) or
8450 (dec.).

The Set tag password command sets a password in the tag. Tag protection is not activated un-
til the Set tag protection command has also been carried out. When sending the command
only one tag can be located in the detection range of the read/write head. After the password is
sent, other commands (e.g. Set tag protection) can be sent to the tag. The Set tag password
command prevents a Kill password from being set in the tag.

The password function is only available in HF applications in single-tag mode. An error message
is output with multitag applications. For troubleshooting set the HF: multitag mode parameter
to 0: Set Multitag mode off.
Request
Loop counter See description of the output data, [} 98]
Command code 0x0102 (hex.), 258 (dec.)
Read/write head address See description of the output data, [} 98]
Length UID/EPC Enter UID or EPC size in bytes, if a particular tag is to be pro-
tected. The UID or EPC must be defined in the write data.
(start byte: 0). The function of the length of the UID/EPC de-
pends on the command used.
0: No entry of a UID/EPC for executing the command. Only
one tag can be located in the detection range of the read/
write head.
> 0: EPC length of the tag to be protected if an EPC is
present in the write data
-1: NEXT mode: A tag is always only protected if the UID/EPC
is different to the UID/EPC of the last read or written tag.
Start address Not required
Length 4 Byte
Command timeout See description of the output data, [} 98]
Write fragment no. 0
Read fragment no. See description of the output data, [} 98]
Write data, Byte 0...3 Password: ARRAY [0…3] OF BYTE
Write data, Byte 4...127 Not required

05.00 | 2019/11 131

Setting
RFID channels – Overview of commands

Response
Loop counter See description of the input data, [} 92]
Response code 0x0102 (hex.), 258 (dec.)
Length Not required
Error code See description of the input data, [} 92]
Tag within the See description of the input data, [} 92]
detection range
Data (bytes) available See description of the input data, [} 92]
Tag counter See description of the input data, [} 92]
Write fragment no. 0
Read fragment no. See description of the input data, [} 92]
Read data Not required

132 Hans Turck GmbH & Co. KG | T +49 208 4952-0 | F +49 208 4952-264 | [email protected] | www.turck.com
8.8.17 Command: Set read/write head password

NOTE
The command is only available for applications with UHF tags and the HF tags TW-
R…-M-B146.

The Set read/write head password command directly sets a password for write access, read ac-
cess or a kill command. The password is stored temporarily in the memory of the read/write
head. After the voltage of the read/write head is reset, the password must be set again in the
read/write head. With UHF applications, the password is stored in the memory of the interface.
The password stored in the read/write head is automatically sent with a write command, a read
command or a kill command so that the command can be carried out on a protected tag.

Response
Loop counter See description of the input data, [} 92]
Response code 0x0100 (hex.), 256 (dec.)
Length Not required
Error code See description of the input data, [} 92]
Tag within the See description of the input data, [} 92]
detection range
Data (bytes) available See description of the input data, [} 92]
Tag counter See description of the input data, [} 92]
Write fragment no. 0
Read fragment no. See description of the input data, [} 92]
Read data Not required

05.00 | 2019/11 133

Setting
RFID channels – Overview of commands

8.8.18 Command: Reset read/write head password

NOTE
The command is only available for applications with UHF tags and the HF tags TW-
R…-M-B146.

The Reset read/write head password command directly resets a password for write access,
read access or a kill command in the read/write head. The password function is switched off,
there is no password exchange between the read/write head and the tag.

Response
Loop counter See description of the input data, [} 92]
Response code 0x0101 (hex.), 257 (dec.)
Length Not required
Error code See description of the input data, [} 92]
Tag within the See description of the input data, [} 92]
detection range
Data (bytes) available See description of the input data, [} 92]
Tag counter See description of the input data, [} 92]
Write fragment no. 0
Read fragment no. See description of the input data, [} 92]
Read data Not required

134 Hans Turck GmbH & Co. KG | T +49 208 4952-0 | F +49 208 4952-264 | [email protected] | www.turck.com
8.8.19 Command: Set tag protection

NOTE
The command is only available for applications with UHF tags and the HF tags TW-
R…-M-B146.

NOTE
The command code for fast processing with the loop counter is 0x2103 (hex.) or
8451 (dec.).

The Set tag protection command defines password protection for the tag with a direct com-
mand. For this it has to be specified whether a write protection or a read protection should be
set and the area of the tag to which the password applies. Protection for all areas is defined
with one command. When sending the command only one tag can be located in the detection
range of the read/write head.

Write protection is always also contained in a read protection.

NOTE
A write protection for UHF tags cannot be undone.

Request
Loop counter See description of the output data, [} 98]
Command code 0x0103 (hex.), 259 (dec.)
Read/write head address See description of the output data, [} 98]
Length UID/EPC Enter UID or EPC size in bytes, if a particular tag is to be pro-
tected. The UID or EPC must be defined in the write data.
(start byte: 0). The function of the length of the UID/EPC de-
pends on the command used.
0: The command is executed for the tag which is located in
the detection range of the read/write head.
> 0: EPC length of the tag to be protected if an EPC is
present in the write data
-1: NEXT mode: A tag is always only protected if the UID/EPC
is different to the UID/EPC of the last read or written tag.
Start address Not required
Memory area Possible values:
n HF: USER memory (memory areas 1 and 3)
n UHF: PC and EPC (memory area 1), USER memory
(memory area 3)
UHF: The entire memory area selected is protected with a
password.
HF: Entry of the memory area not necessary. The pages of
the memory area are selected via Byte 0 of the write data. A
page consists of 4 blocks (16 bytes).
Length UHF: 0 byte
HF: 8 byte

05.00 | 2019/11 135

Setting
RFID channels – Overview of commands

Request
Command timeout See description of the output data, [} 98]
Write fragment no. 0
Read fragment no. See description of the output data, [} 98]
Write data, Byte 0 HF:
n Bit 0: Write protection, Page 0
n Bit 1: Write protection, Page 1
n Bit 2: Write protection, Page 2
n Bit 3: Write protection, Page 3
n Bit 4: Write protection, Page 4
n Bit 5: Write protection, Page 5
n Bit 6: Write protection, Page 6
n Bit 7: Write protection, Page 7
UHF: Not required
Write data, Byte 1 0
Write data, Byte 2 0
Write data, Byte 3 0
Write data, Byte 4 HF:
n Bit 0: Read protection, Page 0
n Bit 1: Read protection, Page 1
n Bit 2: Read protection, Page 2
n Bit 3: Read protection, Page 3
n Bit 4: Read protection, Page 4
n Bit 5: Read protection, Page 5
n Bit 6: Read protection, Page 6
n Bit 7: Read protection, Page 7
UHF: Not required
Write data, Byte 5 0
Write data, Byte 6 0
Write data, Byte 7 0
Write data, Byte 8...127 Not required

Response
Loop counter See description of the input data, [} 92]
Response code 0x0103 (hex.), 259 (dec.)
Length Not required
Error code See description of the input data, [} 92]
Tag within the See description of the input data, [} 92]
detection range
Data (bytes) available See description of the input data, [} 92]
Tag counter See description of the input data, [} 92]
Write fragment no. 0
Read fragment no. See description of the input data, [} 92]
Read data Not required

136 Hans Turck GmbH & Co. KG | T +49 208 4952-0 | F +49 208 4952-264 | [email protected] | www.turck.com
8.8.20 Command: Query HF tag protection status

NOTE
The command is only available for applications with the HF tags TW-R…-M-B146.

The Get HF tag protection status command queries with a direct command whether a specific
area of the tag is password protected. When sending the command only one tag can be loc-
ated in the detection range of the read/write head.

The password function is only available in HF applications in single-tag mode. An error message
is output with multitag applications. For troubleshooting set the HF: multitag mode parameter
to 0: Set Multitag mode off.
Request
Loop counter See description of the output data, [} 98]
Command code 0x0104 (hex.), 260 (dec.)
Read/write head address See description of the output data, [} 98]
Length UID/EPC Enter UID or EPC size in bytes, if a particular tag is to be pro-
tected. The UID or EPC must be defined in the write data.
(start byte: 0). The function of the length of the UID/EPC de-
pends on the command used.
0: The command is executed for the tag which is located in
the detection range of the read/write head.
> 0: EPC length of the tag to be protected if an EPC is
present in the write data
-1: NEXT mode: A tag is always only protected if the UID/EPC
is different to the UID/EPC of the last read or written tag.
Start address Not required
Length 8 Byte
Command timeout See description of the output data, [} 98]
Write fragment no. 0
Read fragment no. See description of the output data, [} 98]
Write data Not required

05.00 | 2019/11 137

Setting
RFID channels – Overview of commands

Response
Loop counter See description of the input data, [} 92]
Response code 0x0104 (hex.), 260 (dec.)
Length Not required
Error code See description of the input data, [} 92]
Tag within the See description of the input data, [} 92]
detection range
Data (bytes) available See description of the input data, [} 92]
Tag counter See description of the input data, [} 92]
Write fragment no. 0
Read fragment no. See description of the input data, [} 92]
Read data, Byte 0 HF:
n Bit 0: Write protection, Page 0
n Bit 1: Write protection, Page 1
n Bit 2: Write protection, Page 2
n Bit 3: Write protection, Page 3
n Bit 4: Write protection, Page 4
n Bit 5: Write protection, Page 5
n Bit 6: Write protection, Page 6
n Bit 7: Write protection, Page 7
UHF: Not required
Read data, Byte 1 0
Read data, Byte 2 0
Read data, Byte 3 0
Read data, Byte 4 HF:
n Bit 0: Read protection, Page 0
n Bit 1: Read protection, Page 1
n Bit 2: Read protection, Page 2
n Bit 3: Read protection, Page 3
n Bit 4: Read protection, Page 4
n Bit 5: Read protection, Page 5
n Bit 6: Read protection, Page 6
n Bit 7: Read protection, Page 7
UHF: Not required
Read data, Byte 5 0
Read data, Byte 6 0
Read data, Byte 7 0

138 Hans Turck GmbH & Co. KG | T +49 208 4952-0 | F +49 208 4952-264 | [email protected] | www.turck.com
8.8.21 Command: Set permanent lock (Lock)

NOTE
The command code for fast processing with the loop counter is 0x2105 (hex.) or
8453 (dec.).

The Set perma lock command permanently sets a complete memory block of the tag with a
direct command and permanently locks it. When sending the command only one tag can be
located in the detection range of the read/write head.

The function is only available in HF applications in single-tag mode. An error message is output
with multitag applications. For troubleshooting set the HF: multitag mode parameter to 0: Set
Multitag mode off.
Request
Loop counter See description of the output data, [} 98]
Command code 0x0105 (hex.), 261 (dec.)
Read/write head address See description of the output data, [} 98]
Length UID/EPC 0: The command is executed for the tag which is located in
the detection range of the read/write head.
> 0: EPC or UID length of the tag to be locked if an EPC or
UID is present in the write data
-1: NEXT mode: A tag is always only protected if the UID/EPC
is different to the UID/EPC of the last read or written tag.
Start address UHF: Not required
HF: Address of the first bit in the block to be locked (EEPROM
tag: 0, 4, 8, …, FRAM tag: 0, 8, 16, …)
Memory area Possible values:
n HF: USER memory (memory areas 1... 4)
n UHF: Kill password (memory area 1), PC and EPC (memory
area 1), USER memory (memory area 3) Access password
(memory area 4)
UHF: The entire memory area selected is permanently
locked.
HF: Entry of the memory area not necessary
Length HF: Length of the data to be locked in bytes. Only multiples
of the block size can be specified.
0: 1 Lock block
UHF: Not required
Command timeout See description of the output data, [} 98]
Write fragment no. 0
Read fragment no. See description of the output data, [} 98]
Write data Not required

05.00 | 2019/11 139

Setting
RFID channels – Overview of commands

Response
Loop counter See description of the input data, [} 92]
Response code 0x0105 (hex.), 261 (dec.)
Length Not required
Error code See description of the input data, [} 92]
Tag within the See description of the input data, [} 92]
detection range
Data (bytes) available See description of the input data, [} 92]
Tag counter See description of the input data, [} 92]
Write fragment no. 0
Read fragment no. See description of the input data, [} 92]
Read data Not required

140 Hans Turck GmbH & Co. KG | T +49 208 4952-0 | F +49 208 4952-264 | [email protected] | www.turck.com
8.8.22 Command: Tag info

NOTE
The command code for fast processing with the loop counter is 0x2050 (hex.) or
8272 (dec.).

The Tag info command enables the chip information of an HF tag to be queried. For HF applic-
ations the command is only available with automatic detection. In UHF applications the alloca-
tion class identifier, tag mask designer identifier and tag model number are queried. The data is
queried from the GSI record of the tag.
Request
Loop counter See description of the output data, [} 98]
Command code 0x0050 (hex.), 80 (dec.)
Read/write head address See description of the output data, [} 98]
Length UID/EPC Not required
Start address Start address in the GSI record
Length Length of the system data read (bytes)
0: All system data is read.
Command timeout Not required
Write fragment no. Not required
Read fragment no. See description of the output data, [} 98]
Write data Not required

Response (HF)
Loop counter See description of the input data, [} 92]
Response code 0x0050 (hex.), 80 (dec.)
Length See description of the input data, [} 92]
Error code See description of the input data, [} 92]
Tag within the See description of the input data, [} 92]
detection range
Data (bytes) available See description of the input data, [} 92]
Tag counter See description of the input data, [} 92]
Write fragment no. 0
Read fragment no. See description of the input data, [} 92]
Read data, Byte 0...7 UID, MSB (always 0xE0)
Read data, Byte 8 DSFID (data storage format identifier)
Read data, Byte 9 AFI (application identifier)
Read data, Byte 10 Memory size: Block number (0x00…0xFF)
Read data, Byte 11 Memory size: Byte/block (0x00…0x1F)
Read data, Byte 12 IC reference

05.00 | 2019/11 141

Setting
RFID channels – Overview of commands

Response (UHF)
Loop counter See description of the input data, [} 92]
Response code 0x0050 (hex.), 80 (dec.)
Length See description of the input data, [} 92]
Error code See description of the input data, [} 92]
Tag within the detection range See description of the input data, [} 92]
Data (bytes) available See description of the input data, [} 92]
Tag counter See description of the input data, [} 92]
Write fragment no. 0
Read fragment no. See description of the input data, [} 92]
Read data, Byte 0...3 First 32 bytes of the TID (tag class, manufacturer and chip
type)
Read data, Bytes 4…n EPC (length variable)

Chip information on the UHF tags

Name TID memory Size (Bits)
Allocation Tag mask Tag model EPC TID USER
class designer number
identifier
Alien Higgs-3 0xE2 0x003 0x412 96…480 96 512
Alien Higgs-4 0xE2 0x003 0x414 16…128 96 128
NXP U-Code G2XM 0xE2 0x006 0x003 240 64 512
NXP U-Code G2XL 0xE2 0x006 0x004 240 64 –
NXP U-Code G2iM 0xE2 0x006 0x80A 256 96 512
NXP U-Code G2iM+ 0xE2 0x006 0x80B 128…448 96 640…320
NXP U-Code G2iL 0xE2 0x006 0x806, 0x906, 0xB06 128 64 –
NXP U-Code G2iL+ 0xE2 0x006 0x807, 0x907, 0xB07 128 64 –
NXP U-Code 7 0xE2 0x806 0x890 128 96 –
NXP U-Code 7xm (2k) 0xE2 0x806 0xF12 448 96 2048
Impinj Monza 4E 0xE2 0x001 0x10C 496 96 128
Impinj Monza 4D 0xE2 0x001 0x100 128 96 32
Impinj Monza 4QT 0xE2 0x001 0x105 128 96 512
Impinj Monza 5 0xE2 0x001 0x130 128 96 –
Impinj Monza R6 0xE2 0x001 0x160 96 96 –
Impinj Monza R6-P 0xE2 0x001 0x170 128 96 64

142 Hans Turck GmbH & Co. KG | T +49 208 4952-0 | F +49 208 4952-264 | [email protected] | www.turck.com
8.8.23 Command: Kill UHF tag

NOTE
The command is only available for UHF applications.

NOTE
The command code for fast processing with the loop counter is 0x2200 (hex.) or
8704 (dec.).

The Kill UHF tag command makes the tag memory unusable. After a kill command, the tag can
neither be read nor written. A Kill command cannot be undone.
Request
Loop counter See description of the output data, [} 98]
Command code 0x0200 (hex.), 512 (dec.)
Read/write head address See description of the output data, [} 98]
Length UID/EPC Enter UID or EPC size in bytes if a particular tag is to be de-
leted. The UID or EPC must be defined in the write data.
(start byte: 0). The function of the length of the UID/EPC de-
pends on the command used.
0: No entry of a UID/EPC for executing the command. Only
one tag can be located in the detection range of the read/
write head.
> 0: EPC length of the tag to be deleted if an EPC is present
in the write data.
-1: NEXT mode: A tag is always only deleted if the UID/EPC is
different to the UID/EPC of the last read or written tag.
Start address Not required
Length 1 Byte
Command timeout See description of the output data, [} 98]
Write fragment no. 0
Read fragment no. See description of the output data, [} 98]
Write data, Byte 0...3 Password: ARRAY [0…3] OF BYTE
Write data, Byte 4...127 Not required

Response
Loop counter See description of the input data, [} 92]
Response code 0x0200 (hex.), 512 (dec.)
Length Not required
Error code See description of the input data, [} 92]
Tag within the See description of the input data, [} 92]
detection range
Data (bytes) available See description of the input data, [} 92]
Tag counter See description of the input data, [} 92]
Write fragment no. 0
Read fragment no. See description of the input data, [} 92]
Read data Not required

05.00 | 2019/11 143

Setting
RFID channels – Overview of commands

8.8.24 Command: Restore UHF read/write head settings

NOTE
The command is only available for UHF applications.

The Restore settings UHF read/write head command restores the parameters of a connected
UHF read/write head from a backup (e.g. after a device swap). Type and firmware version must
be identical for both read/write heads. To execute the command, a backup must be created be-
forehand via the Backup settings UHF read/write head command.
Request
Loop counter See description of the output data, [} 98]
Command code 0x1000 (hex.), 4096 (dec.)
Read/write head address See description of the output data, [} 98]
Length UID/EPC Not required
Start address Not required
Length Not required
Command timeout See description of the output data, [} 98]
Write fragment no. 0
Read fragment no. See description of the output data, [} 98]
Write data Not required

Response
Loop counter See description of the input data, [} 92]
Response code 0x1000 (hex.), 4096 (dec.)
Length Not required
Error code See description of the input data, [} 92]
Tag within the See description of the input data, [} 92]
detection range
Data (bytes) available See description of the input data, [} 92]
Tag counter See description of the input data, [} 92]
Write fragment no. 0
Read fragment no. See description of the input data, [} 92]
Read data Not required

144 Hans Turck GmbH & Co. KG | T +49 208 4952-0 | F +49 208 4952-264 | [email protected] | www.turck.com
8.8.25 Command: Backup settings of the UHF read/write head

NOTE
The command is only available for UHF applications.

The Backup settings of the UHF read/write head command saves the current settings of the
connected read/write head in the memory of the interface. The backup is retained also after the
voltage of the interface is reset. The Restore UHF read/write head settings command can re-
store the backup data when a device is swapped. Type and firmware version must be identical
for both read/write heads.
Request
Loop counter See description of the output data, [} 98]
Command code 0x1001 (hex.), 4097 (dec.)
Read/write head address See description of the output data, [} 98]
Length UID/EPC Not required
Start address Not required
Length Not required
Command timeout See description of the output data, [} 98]
Write fragment no. 0
Read fragment no. See description of the output data, [} 98]
Write data Not required

Response
Loop counter See description of the input data, [} 92]
Response code 0x1001 (hex.), 4097 (dec.)
Length Not required
Error code See description of the input data, [} 92]
Tag within the See description of the input data, [} 92]
detection range
Data (bytes) available See description of the input data, [} 92]
Tag counter See description of the input data, [} 92]
Write fragment no. 0
Read fragment no. See description of the input data, [} 92]
Read data Not required

05.00 | 2019/11 145

Setting
RFID channels – Overview of commands

8.8.26 Command: Query error/status of UHF read/write head

NOTE
The command is only available for UHF applications.

The Query error/status of UHF read/write head command enables error/status messages of a
connected UHF read/write head to be read.
Request
Loop counter See description of the output data, [} 98]
Command code 0x042 (hex.), 66 (dec.)
Read/write head address Not required
Length UID/EPC Not required
Start address Address in the Get Status response record
Length Length of the data to be read from the Get Status response
record
0: Read entire Get Status response record
Command timeout See description of the output data, [} 98]
Write fragment no. 0
Read fragment no. See description of the output data, [} 98]
Write data Not required

146 Hans Turck GmbH & Co. KG | T +49 208 4952-0 | F +49 208 4952-264 | [email protected] | www.turck.com
Response
Loop counter See description of the input data, [} 92]
Response code 0x042 (hex.), 66 (dec.)
Length See description of the input data, [} 92]
Error code See description of the input data, [} 92]
Tag within the See description of the input data, [} 92]
detection range
Data (bytes) available See description of the input data, [} 92]
Tag counter See description of the input data, [} 92]
Write fragment no. 0
Read fragment no. See description of the input data, [} 92]
Read data, Byte 0...(Length-1) n Status general: 1 byte general status
n RF status: 1 byte status of the RF module
n Device status: 1 byte device-specific status information
n RF mode: 1 byte, defines the reason for starting the read
operation
n Trigger status: 1 Byte, trigger number of RF mode
n I/O status: 1 byte, status of the inputs and outputs (0 =
low, 1 = high)
n Ambient temperature: 1 byte, ambient temperature in °C
(data format: 8 bit, two’s complement)
n PA temperature: 1 byte, PA temperature in °C (data
format: 8 bit, two’s complement)
n RF antenna temperature: 1 byte, ambient temperature in
°C (data format: 8 bit, two’s complement)
n Transmit power: 2 bytes, output power of the read/write
head in 1/10 dBm steps, LSB…MSB (data format: 16 bit,
two’s complement)
n Reverse power: 2 bytes, returned reverse power in 1/10
dBm steps, LSB…MSB (data format: 16 bit, two’s comple-
ment)
n Antenna DC resistance: 4 bytes, resistance at the antenna
port in Ω, LSB…MSB
n Jammer power: 2 bytes, input power at the RX port in
1/10 dBm steps, LSB…MSB (data format: 16 bit, two’s
complement)
n Channel: Number of the currently used channel (offset
from the next available channel)
Read data, byte (Length)...127 Not required

Evaluating read data – General status

Bit Meaning
7 Read/write head was reset (after reset)
6 Read/write head configuration damaged, default settings are used.
5 Test mode active
1 Tag present

05.00 | 2019/11 147

Setting
RFID channels – Overview of commands

Evaluating read data – RF status

Bit Meaning
4 Limit value for radiated power exceeded
3 No free channel present
2 Antenna resistance too high or too low
1 Reverse power too high
0 PLL not locked

Evaluating read data – Device status

Bit Meaning
4 Error in message generation (in Polling mode outside of memory area)
3 Temperature warning
2 Temperature too high
1 Communication error
0 Configuration invalid. Command execution not possible.

Evaluating read data – RF mode

Value Meaning
0x00 None (tag off)
0x01 Mode 1: Trigger is digital signal (edge), Timeout
0x02 Mode 2: Trigger is digital signal (edge), Timeout
0x03 Mode 3: Trigger is digital signal (level), Timeout
0x04 Trigger is a command
0x08 Reserved
0x10 DCU controlled read operation
0x20 Continuous mode
0x80 Automatic trigger (presence sensing mode)

Evaluating read data – I/O status

Value Meaning
7 Output 4
6 Output 3
5 Output 2
4 Output 1
3 Input 4
2 Input 3
1 Input 2
0 Input 1

148 Hans Turck GmbH & Co. KG | T +49 208 4952-0 | F +49 208 4952-264 | [email protected] | www.turck.com
8.8.27 Command: Reset
The Reset command resets the read/write head and interface. The input and output data and
the buffer are also cleared.
Request
Loop counter See description of the output data, [} 98]
Command code 0x8000 (hex.), 32768 (dec.)
Read/write head address See description of the output data, [} 98]
Length UID/EPC Not required
Start address 0: Software reset
1: Voltage reset
Length Not required
Command timeout See description of the output data, [} 98]
Write fragment no. 0
Read fragment no. See description of the output data, [} 98]
Write data Not required

Response
Loop counter See description of the input data, [} 92]
Response code 0x8000 (hex.), 32768 (dec.)
Length Not required
Error code See description of the input data, [} 92]
Tag within the See description of the input data, [} 92]
detection range
Data (bytes) available See description of the input data, [} 92]
Tag counter See description of the input data, [} 92]
Write fragment no. 0
Read fragment no. See description of the input data, [} 92]
Read data Not required

05.00 | 2019/11 149

Setting
Setting RFID interfaces via the web server

8.9 Setting RFID interfaces via the web server

NOTE
The web server always displays all setting options. All values are displayed as
decimal numbers.

The devices can be set and commands can be sent to the devices via the integrated web server.
To be able to open the web server with a PC, the device and the PC must be in the same IP net-
work.

8.9.1 Opening a web server

The web server can be opened via a web browser or via the Turck Service Tool. The procedure
for accessing the web server via the Turck Service Tool is described in the section "Setting the IP
address".

In the delivery state the device has the IP address 192.168.1.254. To open the web server via a
web browser, enter http://192.168.1.254 in the address bar of the web browser.

The start page shows status information and network settings.

Fig. 73: Example: Web server – Start pages (device IP address: 192.168.1.20)

150 Hans Turck GmbH & Co. KG | T +49 208 4952-0 | F +49 208 4952-264 | [email protected] | www.turck.com
8.9.2 Processing settings in the web server
A login is required to edit settings via the web server. The default password is "password".

NOTE
For security reasons, Turck recommends changing the password after the first login.

Enter the password in the login field on the start page of the web server.
Click Login

Fig. 74: Login field on the start page of the web server (marked in red)

05.00 | 2019/11 151

Setting
Setting RFID interfaces via the web server

After the login, write access to input, output and parameter data is possible.

Fig. 75: Web server – Start page after the login

152 Hans Turck GmbH & Co. KG | T +49 208 4952-0 | F +49 208 4952-264 | [email protected] | www.turck.com
Example: Setting the operating mode for channel 0
The operating mode of channel 0 is set to HF compact in the following example.
Click RFID control/status 0 in the navigation bar on the left of the screen.
Select Parameters.

Fig. 76: Setting parameters in the web server

05.00 | 2019/11 153

Setting
Setting RFID interfaces via the web server

Select the operating mode via the Operating mode drop-down menu.

Fig. 77: Drop-down-Menü – Operation Mode

Save the settings: Click Submit.

154 Hans Turck GmbH & Co. KG | T +49 208 4952-0 | F +49 208 4952-264 | [email protected] | www.turck.com
Example: Executing a read command
In the following example 8 bytes of a tag are read by a read/write head connected to channel 0
of the interface.

Click RFID control/status 0 in the navigation bar on the left of the screen.
Click Outputs.
Select the read command via the Command code drop-down menu: 0x0002 (read)
Enter in the Length entry field the number of bytes to be read.
Send the read command: Click Submit.

Fig. 78: Setting the read command in the web server

05.00 | 2019/11 155

Setting
Setting RFID interfaces via the web server

The receipt of the command is confirmed in the input data at Response code.
Call the input data: Click Inputs in the navigation bar on the left of the screen.

Fig. 79: Input data

Refresh the page manually to display the latest status.

156 Hans Turck GmbH & Co. KG | T +49 208 4952-0 | F +49 208 4952-264 | [email protected] | www.turck.com
The read command is executed as soon as there is a tag in the detection range of the read/
write head.

Fig. 80: Input data with successfully executed read command

05.00 | 2019/11 157

Setting
Setting RFID interfaces via the web server

The read data can be called at RFID Read Data Ò Inputs.

Fig. 81: Read data

158 Hans Turck GmbH & Co. KG | T +49 208 4952-0 | F +49 208 4952-264 | [email protected] | www.turck.com
Example: Executing a command in Bus mode
In the following example, the read/write head with address 2 is required in HF bus mode to
read eight bytes of a tag. Three read/write heads are connected to channel 0 of the interface.

Click RFID control/status 0 in the navigation bar on the left of the screen.
Select Parameters.
Set HF bus mode.
Activate connected read/write heads.

Fig. 82: Reading tags in HF bus mode – Parameters

05.00 | 2019/11 159

Setting
Setting RFID interfaces via the web server

Click RFID control/status 0 in the navigation bar on the left of the screen.
Click Outputs.
Select the read command (0x0002 Read).
Enter the length of the read data.
Enter the read/write head address in the read/write head address parameter.

Fig. 83: Reading tags in HF bus mode – Process output data

160 Hans Turck GmbH & Co. KG | T +49 208 4952-0 | F +49 208 4952-264 | [email protected] | www.turck.com
8.10 Testing and parameterizing RFID interfaces via the DTM
The device can be tested and assigned parameters with the DTM (Device Type Manager) via
PACTware™.
The different functions of the DTM are displayed by right-clicking the device in the project tree.
You can start the following functions:
n Parameters: Adapt parameters to the actual application
n Measured values: Display of the data read by the RFID interface
n Simulation: Set output parameter of the device for the function test
n Diagnostics: Display of the diagnostic messages of the device or the entire RFID system

8.10.1 Connecting the device with the PC

Launch PACTware™.
Right-click Host PC in the project tree.
Click Add device.
Select BL Service Ethernet.
Confirm selection with OK.

Fig. 84: Selecting an Ethernet adapter

05.00 | 2019/11 161

Setting
Testing and parameterizing RFID interfaces via the DTM

Right-click the Ethernet adapter in the project tree.

Click Add device.
Select TBEN-S2-2RFID-4DXP.
Confirm selection with OK.

Fig. 85: Selecting TBEN-S2-2RFID-4DXP

162 Hans Turck GmbH & Co. KG | T +49 208 4952-0 | F +49 208 4952-264 | [email protected] | www.turck.com
Enter the IP address of the device (example: 192.168.1.20).
Optional: Enter designation and device description.
Confirm entries with OK.

Fig. 86: Entering the IP address

ü The project tree is fully open.

Right-click the device in the project tree.
Click Connect.
a After connecting, read and write access to input, output and parameter data is possible.

Fig. 87: Complete project tree

05.00 | 2019/11 163

Setting
Testing and parameterizing RFID interfaces via the DTM

8.10.2 Editing parameter data with the DTM – Online parameterization

The online parameterization function enables parameter data to be changed and written to the
device.

Right-click the device in the project tree.

Click Online parameterization.

Fig. 88: Online parameterization

Example: Selecting the operating mode

Click the operating mode in the Online parameterization window.
Select the required operating mode from the drop-down menu.

Fig. 89: Example – Selecting the operating mode

164 Hans Turck GmbH & Co. KG | T +49 208 4952-0 | F +49 208 4952-264 | [email protected] | www.turck.com
8.10.3 Reading process input data with the DTM – Measured value
The measured value function of the DTM enables the reading of the process input data.

Right-click the device in the project tree.

Click Measured value.
Select in the middle window the required channel.
a The process input data is displayed in the window on the right-hand side (example: the
device is in Idle mode).

Fig. 90: Measured value function of the DTM

8.10.4 Changing process output data with the DTM – Simulation

The Simulation function of the DTM enables the process output data to be changed.

Right-click the device in the project tree.

Click Simulation.
Select in the middle window the required channel.
a The process output data is displayed in the window on the right-hand side (example: the
device is in Idle mode).

Fig. 91: Simulation function of the DTM

05.00 | 2019/11 165

Setting
Testing and parameterizing RFID interfaces via the DTM

8.10.5 Evaluating diagnostics with the DTM

The Diagnostics function of the DTM enables the diagnostics of all channels to be called.

Right-click the device in the project tree.

Click Diagnostics.
Select in the middle window the required channel.
a The process output data is displayed in the window on the right-hand side (example: No
diagnostics presents).

Fig. 92: Diagnostics function of the DTM

166 Hans Turck GmbH & Co. KG | T +49 208 4952-0 | F +49 208 4952-264 | [email protected] | www.turck.com
8.10.6 Example: Executing a read command with the DTM
In the following example 8 bytes of a tag are read by a read/write head connected to channel 0
of the interface.

Right-click the device in the project tree.

Click Simulation.
Select RFID channel 0 in the central window.
Set the length: Double-click the current value.
Confirm all the following messages.
a The DTM starts Force mode. In Force mode all entered values are written directly to the
connected device.
Enter the length in bytes (example: 8).
Select the command code from the drop-down menu (example: 0x0002 read).

Fig. 93: Executing a read command – Window: Simulation

The read data is displayed in the Measured value window. The data format is hexadecimal.

Fig. 94: Executing a read command – Window: Measured value

05.00 | 2019/11 167

Setting
Setting UHF read/write heads

8.11 Setting UHF read/write heads

UHF read/write heads can be assigned additional parameters via a DTM. No parameters can be
set in UHF read/write heads via the parameter data of the interface. The DTM for the specific
device is available for download from www.turck.com.

A comprehensive description of the settings for UHF read/write heads is provided in the oper-
ating instructions for the specific device.

168 Hans Turck GmbH & Co. KG | T +49 208 4952-0 | F +49 208 4952-264 | [email protected] | www.turck.com
9 Operation
NOTE
The read and write data stored in the module is reset after a power reset.

9.1 Executing a command and calling data

NOTE
A command is successful when the response code is the same as the command
code.

Set the parameters for the command.

Set command code.
a Set the command code. The command is successful when the response code is the same
as the command code and no error message is present.

9.1.1 Typical times for command processing via a controller

The values shown in the following table are approximate values. The typical times for com-
mand execution depend on the following factors:
n Hardware configuration
n Software configuration
n Number of bus stations
n Bus cycle times

HF applications
Command System cycle time Required time Dependence on factors such as
protocol, system etc.
Read 8 bytes 4 ms 10 ms ≤ 20 %
Write 8 bytes 4 ms 10 ms ≤ 20 %
Read 8 bytes 20 ms 60 ms ≤ 20 %
Write 8 bytes 20 ms 60 ms ≤ 20 %
Read 128 bytes 4 ms 40 ms ≤ 20 %
Write 128 bytes 4 ms 50 ms ≤ 20 %
Read 1 kByte 4 ms 700 ms ≤ 20 %
Write 1 kByte 4 ms 800 ms ≤ 20 %
Inventory (4 tags) 4 ms 300 ms ≤ 10 %

HF bus mode
The time required to cyclically process the command depends on how long the tag is in the de-
tection range of the read/write head (bypass time). The bypass time is set at 48 ms by default.
The bypass time can be set by the user. If the bypass time is set differently, the difference from
the time taken to process a command must be added or deducted.

The time taken for all read/write heads to be addressed once by the interface is calculated as
follows:
Number of read/write heads × bypass time
This time corresponds to the update rate for the Tag in detection range bit and must also be
taken into account when calculating the total time taken to process a command.

05.00 | 2019/11 169

Operation
Executing a command and calling data

The inventory command must be executed separately for all read/write heads.
Command System cycle time Time required Dependence on factors such as
protocol, system, etc.
Read UID on a read/write 4 ms 24 ms Depending on the system
head with rising edge at TP, cycle time, the bypass time
tag within the detection must be added.
range
Read UID on a read/write 20 ms 80 ms
head with rising edge at TP,
tag within the detection
range
Read 112 bytes from different 4 ms 180 ms per read/write The length of time for which
read/write heads one after head the individual read/write
the other, default bypass time heads are accessed varies.
(48 ms)

UHF applications
Command System cycle time Required time Dependence on factors such
as protocol, system etc.
Read 12 bytes EPC 4 ms 120…220 ms not detectable
Write 12 bytes EPC 4 ms 260…400 ms not detectable
Read 1 kByte 4 ms 2500 ms ≤ 20 %
Write 1 kByte 4 ms 7300 ms ≤ 20 %
Inventory (100 tags, read/ 4 ms 5500 ms ≤ 20 %
write head in report mode,
dynamic application)

170 Hans Turck GmbH & Co. KG | T +49 208 4952-0 | F +49 208 4952-264 | [email protected] | www.turck.com
9.2 Using fragmentation
If more data is read than the set size of the data interface, the fragment counter is incremented
in the input data.
To read more data, increase the fragment counter in the output data.
Repeat process until the read or write fragment no. in the input data equals 0.

If less data is read than the set size of the data interface, the fragment counter stays at 0.

9.2.1 Example: Using fragmentation in the web server – Read

The following example describes the reading of 500 bytes in fragments of 128 bytes each.
Open the web server of the device.
Log into the device as administrator.
Set the operating mode of the required channel via RFID control/status 0 Ò Paramet-
ers to HF extended (here: channel 0).
Save the set operating mode with Submit.

Fig. 95: Fragmentation – Selecting the operating mode

05.00 | 2019/11 171

Operation
Using fragmentation

Click RFID control/status 0 Ò Outputs in the navigation bar on the left of the screen.
Select the read command via the Command code drop-down menu: 0x0002 Read.
Enter in the Length entry field the total number of bytes to be read. Observe the size of
the tag.
Send the read command: Click Submit.
a The read command is executed as soon as there is a tag in the detection range of the
read/write head.

Fig. 96: Fragmentation – Setting the read command

172 Hans Turck GmbH & Co. KG | T +49 208 4952-0 | F +49 208 4952-264 | [email protected] | www.turck.com
Call the input data via RFID control/status 0 Ò Inputs.
The following information is displayed in the input data:
n Response code: Read command successfully executed
n Data (bytes) available: Number of bytes that are still stored on the TBEN module and are not
yet displayed in the read data
n Read fragment No.: Consecutive number of the next fragment to be read

Fig. 97: Fragmentation – Input data

05.00 | 2019/11 173

Operation
Using fragmentation

Call the input data via RFID read data Ò Inputs.

a The first 128 bytes of the input data are displayed.
Click RFID control/status 0 Ò Outputs in the navigation bar on the left of the screen.
Enter at Read fragment No. the consecutive number of the next fragment to be read
(here: 1).
Send the read command: Click Submit.

Fig. 98: Fragmentation – Read second fragment

174 Hans Turck GmbH & Co. KG | T +49 208 4952-0 | F +49 208 4952-264 | [email protected] | www.turck.com
Call the input data via RFID control/status 0 Ò Inputs.
The following information is displayed in the input data:
n Response code: Read command successfully executed
n Data (bytes) available: Number of bytes that are still stored on the TBEN module and are not
yet displayed in the read data
n Read fragment No.: Consecutive number of the next fragment to be read

Fig. 99: Fragmentation – Input data of the second fragment

05.00 | 2019/11 175

Operation
Using fragmentation

Call the input data via RFID read data Ò Inputs.

a The second 128 bytes of the input data are displayed.
Repeat the operation until no more data is present on the TBEN module.
a If no more data is present on the TBEN module, Read fragment No. will show the value 0.

Fig. 100: Fragmentation – No more data present on the TBEN module

176 Hans Turck GmbH & Co. KG | T +49 208 4952-0 | F +49 208 4952-264 | [email protected] | www.turck.com
9.2.2 Example: Using fragmentation in the web server – Write
The following example describes the writing of 500 bytes in fragments of 128 bytes each.
Open the web server of the device.
Log into the device as administrator.
Set the operating mode of the required channel via RFID control/status 0 Ò Paramet-
ers to HF extended (here: channel 0).
Save the set operating mode with Submit.

Fig. 101: Fragmentation – Selecting the operating mode

NOTE
The tag must not leave the detection range of the read/write head during the write
operation.

05.00 | 2019/11 177

Operation
Using fragmentation

Enter the first 128 bytes of write data via RFID write data 0 Ò Outputs.
Click RFID control/status 0 Ò Outputs in the navigation bar on the left of the screen.
Choose the write command via the Command code drop-down menu: 0x0004 (write).
Enter the total number of bytes to be written in the Length entry field. Observe the size
of the tag.
Enter the value 1 at Write fragment No.
Send the write command: Click Submit.
a The write command is executed as soon as there is a tag in the detection range of the
read/write head. If a tag is present in the detection range of the read/write head, the data
is written directly and not stored on the TBEN module.

Fig. 102: Fragmentation – Executing a write command

178 Hans Turck GmbH & Co. KG | T +49 208 4952-0 | F +49 208 4952-264 | [email protected] | www.turck.com
Call the input data via RFID control/status Ò Inputs.
The following information is displayed in the input data:
n Response code: 0x8004 Busy – Write (write command active)
n Data (bytes) available: Number of bytes that are still stored on the TBEN module and were
not yet written to the tag
n Write fragment No.: Consecutive number of the next fragment to be read

Fig. 103: Fragmentation – Input data

05.00 | 2019/11 179

Operation
Using fragmentation

Enter the second 128 bytes of write data at RFID write data 0 Ò Outputs.
Click RFID control/status 0 Ò Outputs in the navigation bar on the left of the screen.
Enter at Write fragment No. the consecutive number of the next fragment to be written
(here: 2).
Send the write command: Click Submit.
It is written directly if a tag is in the detection range. The data is stored in the TBEN module if
there is no tag in the detection range.
The tag must stay in the detection range until the command is fully executed. The device out-
puts an error message if the tag is removed from the detection range before the command has
been completed.

Fig. 104: Fragmentation – Write second fragment

180 Hans Turck GmbH & Co. KG | T +49 208 4952-0 | F +49 208 4952-264 | [email protected] | www.turck.com
Repeat the operation until all data is present on the TBEN module.
a If the data was successfully written to the tag, the Response code changes to 0x0004
Write.

Fig. 105: Fragmentation – No more data present on the TBEN module

05.00 | 2019/11 181

Operation
HF applications – Using Continuous mode

9.3 Using commands with a loop counter function

NOTE
The loop counter is only supported for fast execution commands.

Setting the command: Enter the command code.

Set the loop counter to 1.
a The command was successfully executed if the same command code appears in the pro-
cess input data as in the process output data. The RFID data is stored in the buffer of the
interface.

Repeating the command: Increase the loop counter in the output data by 1.
a The command was successfully executed if the same loop counter value appears in the
process input data as in the process output data. The RFID data is stored in the buffer of
the interface.

Setting a new command: Enter the new command code and set the loop counter to 0.

9.4 HF applications – Using Continuous mode

In Continuous mode (HF) the read/write head can read or write up to 64 bytes (see the table for
user data areas of the HF tags.
The following parameters must be set in Continuous mode:
n Tag info
n Command in Continuous mode
n Length in Continuous mode
n Start address

With read or write command: Enter the tag type. Automatic detection is not possible.
Select the command in Continuous mode (CCM): Inventory, read, tag info and write are
possible.
Enter the length in Continuous mode (LCM): Enter the length of the data to be read in
bytes.
Enter the start address for the command in Continuous mode (ACM). The start address
must be a multiple of the block size of the tag used. The addressing of an uneven byte
number is not possible.
For a write command enter the data to be written in the write data area.
Execute the Continuous mode command.
a The set command is preloaded and carried out for all active read/write heads as soon as a
tag is in the field.
The data received from the read/write head is queried cyclically and stored in the FIFO
memory of the interface.
Execute Idle command (0x0000).
To pass on data from the FIFO memory of the interface to the controller, execute the Get
data from buffer (0x0011) command. The length of the data must equal the value of the
available data bytes (BYFI).
To end Continuous mode, execute the End Continuous mode command (0x0012).
or
To end Continuous mode and clear the FIFO memory of the interface, send the Reset
command (0x0800).

182 Hans Turck GmbH & Co. KG | T +49 208 4952-0 | F +49 208 4952-264 | [email protected] | www.turck.com
9.5 Using HF bus mode
9.5.1 Executing commands in HF bus mode
Set the parameter data.
Select the HF bus mode operating mode.
Activate the connected read/write heads.
Set the input data.
Specify the command code.
Set the start address for the command.
Set the required read/write head address.
Send the command to the read/write head.

9.5.2 Replacing bus-capable read/write heads

Remove the faulty read/write head.
Connect the new read/write head with the default address 68 (delivered with …/C53).
If multiple read/write heads are being replaced: Replace the read/write heads in the or-
der in which they were connected.
a Addresses are allocated in ascending order to the read/write heads in the order in which
the heads were connected. The lowest address is automatically assigned to the next
read/write head with the default address 68 that is connected.
a If the LED on the read/write head is permanently lit, this indicates that the addressing is
complete.

05.00 | 2019/11 183

Operation
Using HF bus mode

9.5.3 Continuous HF bus mode — Data retrieval

All activated read/write heads are triggered within a time frame of bypass time + waiting time.
Within this time frame, the set command (e.g. inventory, read, write) is processed in Continuous
mode. While a command is being executed by all activated read/write heads, only one read/
write head sends data to the RFID interface. The other read/write heads store the read data for
subsequent retrieval. When a new tag is detected by the same read/write head, any data in the
buffer of the read/write head that has not yet been transferred to the RFID interface is overwrit-
ten.

NOTE
The repeated reading of the same tag is time-triggered. The grouping in the process
output data can be activated in order to prevent the storing of the same UID mul-
tiple times.

During the time between two requests and when sending data to the RFID interface, the read/
write heads do not recognize any tags. The required waiting times are given in the following
table:
Command Waiting time
Inventory 15 ms
Read 25 ms
Write 35 ms

By default, the bypass time in HF bus mode is 48 ms.

The following table shows when commands are executed (CMD) and data is exchanged (DATA).
n CMD: Command is being executed.
n DATA: Data is being exchanged.
n DATA or CMD: If data is stored on the read/write head, the data is sent to the TBEN module. If
no data is stored on the read/write head, the command is executed.
Read/write Sequence 1 Sequence 2 Sequence 3 Sequence n
head
Address 1 DATA None CMD None CMD None CMD None
or CMD Action Action Action Action
Address 2 CMD None DATA None CMD None CMD None
Action or CMD Action Action Action
Address 3 CMD None CMD None DATA None CMD None
Action Action or CMD Action Action
Address n CMD None CMD None CMD None DATA None
Action Action Action or CMD Action
Time Bypass time Waiting Bypass time Waiting Bypass time Waiting Bypass time Waiting
time time time time

184 Hans Turck GmbH & Co. KG | T +49 208 4952-0 | F +49 208 4952-264 | [email protected] | www.turck.com
9.6 HF applications — Using continuous HF bus mode
In HF Continuous mode the read/write head can read or write up to 64 bytes (see the table for
user data areas of the HF tags.
The following parameters must be set in Continuous mode:
n Tag Type
n Command in Continuous mode
n Length in Continuous mode
n Start address for the command in Continuous mode
n Optional: Start address in the process output data for activating the grouping

With read or write command: Enter the tag type. Automatic detection is not possible.
Select the command in Continuous mode (CCM): Inventory, read, tag info and write are
possible.
Enter the length in Continuous mode (LCM): Enter the length of the data to be read in
bytes. The start address must be a multiple of the block size of the tag used.
Enter the start address for the command in Continuous mode (ACM). The start address
must be a multiple of the block size of the tag used. Refer to the table below for the block
size of the tags. Uneven bytes cannot be addressed.
Set the grouping function via the Start address in the process output data parameter if
required: Set the value for the Start address parameter to 1. If the grouping function is
activated and a UID is still stored in the FIFO memory of the module, a UID after the first
read is no longer stored as a new read. With subsequent read operations only the address
of the read/write head that has last read the tag and the number of the read operations is
updated.
For a write command enter the data to be written in the write data area.
Execute the Continuous mode command.
a The set command is preloaded and carried out for all active read/write heads as soon as a
tag is in the field.
With the read command and when querying UIDs, the data received by the read/write
head is polled cyclically and stored in the FIFO memory of the interface:
Type Name Meaning
uint8_t data[8] uint8_t UID [8]
uint8_t Reserved
uint8_t Address Read/write head address
uint16_t Number of read operations (only if grouping is activ-
ated)

Execute Idle command (0x0000). The Idle command does not end Continuous mode.
To pass on data from the FIFO memory of the interface to the controller, execute the Get
data from buffer (0x0011) command. The address of the read/write head used is also
transferred in addition to the read data. The length of the available data in the FIFO
memory is displayed in the input data at Data (bytes) available (BYFI). The length of the
data must be consistent. Example: If UID, reserved byte and read/write head address are
written to the FIFO memory for each tag, at least 10 bytes of data must be read from the
buffer.

NOTE
Data in the FIFO memory is not overwritten until it was transferred to the controller.
New read operations are appended in the FIFO memory of the interface.

05.00 | 2019/11 185

Operation
HF applications — Using continuous HF bus mode

To end Continuous mode, execute the End Continuous mode command (0x0012).
or
To end Continuous mode and clear the FIFO memory of the interface, send the Reset
command (0x0800).

NOTE
The data must be passed on regularly from the device to the parent level. No other
data can be stored if the 16 KByte ring memory is full. The device outputs an error
message.

User data areas of HF tags

Chip type User data area Access Bytes per block
First block Last block Total memory
[Byte]
NXP SL2 SLI 0x00 0x1B 112 Read/write 4
NXP SL2 SLI-S 0x00 0x27 160 Read/write 4
NXP SL2 SLI-L 0x00 0x07 32 Read/write 4
Fujitsu MB89R118 0x00 0xF9 2000 Read/write 8
Fujitsu
MB89R118B
Fujitsu MB89R112 0x00 0xFF 8192 Read/write 32
TI Tag-it HFI Plus 0x00 0x3F 256 Read/write 4
TI Tag-it HFI 0x00 0x07 32 Read/write 4
infineon SR- 0x00 0x37 224 Read/write 4
F55V02P
infineon SR- 0x00 0xF7 992 Read/write 4
F55V10P
EM4233 0x00 0x33 208 Read/write 4
EM4233 SLIC 0x00 0x1F 128 Read/write 4

186 Hans Turck GmbH & Co. KG | T +49 208 4952-0 | F +49 208 4952-264 | [email protected] | www.turck.com
9.7 Query UID in HF Continuous bus mode
There are three ways of querying the UID in HF Continuous bus mode.
n Use HF bus mode in Idle
n Use the Inventory command in HF bus mode
n Use HF Continuous bus mode with the Inventory command

The following tables describe the benefits and disadvantages of the particular applications.
Application Functions Notes
Use HF bus mode n UID is automatically displayed in the input n If tags with different UIDs are present in the
in Idle data. detection range of different read/write
heads, the UID is overwritten with each de-
tection operation: Data loss possible.
n No commands required by the controller
n Grouping function only possible via the
controller
Use the Inventory n Inventory command must be sent individu- n No overwriting of data: Only one read/write
command in HF ally to each read/write head. head performs the particular command.
bus mode n UID is displayed in the input data. n Only useful for static applications: The bus
cycle time must be shorter than the time
until a new tag is in the field.
n Grouping function only possible via the
controller
Use Continuous HF n Inventory command must be sent once by n All read/write heads are activated and save
bus mode with In- the controller. data.
ventory command n All UIDs are stored with the read/write head n Grouping function possible as long as the
address in the ring memory of the TBEN data was not yet sent to the controller
module: No data loss.
n The Get data from buffer command trans-
fers the data to the controller.

05.00 | 2019/11 187

Operation
Using NEXT mode

9.8 Using NEXT mode

NEXT mode can only be used in HF single-tag applications. An HF tag is always only read, writ-
ten or protected if the UID is different to the UID of the last read or written tag.

9.8.1 Example: Using NEXT mode for a read command

ü Requirement: Tag A and tag B must have a different UID.
Set read command in the process output data.
Set NEXT mode: Enter the value -1 in the process output data at Length UID/EPC.
Tag A is located in the detection range of the read/write head. The controller sends a read com-
mand in NEXT mode to the RFID interface.
The read command tag is transferred from the interface to the read/write head. The read/write
head reads the data of tag A once.

The controller sends a second read command in NEXT mode to the RFID interface. The read
command is not transferred from the interface to the read/write head as long as tag A is in the
detection range of the read/write head.

The read command is transferred from the interface to the read/write head if tag B is in the de-
tection range of the read/write head. The read/write head reads the data of tag B.
PLC TBEN RW-head Tags

Read (next tag) Read Read

Tag A

Data Data Data

Read (next tag)

Tag A

Read Read

Tag B

Data Data Data

Fig. 106: NEXT mode (layout)

188 Hans Turck GmbH & Co. KG | T +49 208 4952-0 | F +49 208 4952-264 | [email protected] | www.turck.com
9.9 Using the UHF password function
9.9.1 Access password
A write or read protection for EPC and user memory can be set with an access password.
Write access password with the following parameters to the tag:
n Command code 0x0102 (set tag password)
n Password: 4 bytes in the output data
n Length: 4 bytes

Set access password with the following parameters in the read/write head:
n Command code 0x0100 (set read/write head password)
n Password: 4 bytes in the output data

Protect individual memory areas with the following parameters:

n Command code 0x0103 (set tag protection)
n Memory area: EPC or USER

Protect access password from read access:

n Command code 0x0105 (set permanent lock (Lock))
n Memory area: EPC or USER

NOTE
If an incorrect access password is used for write accesses, the appropriate area can-
not be written. The device outputs an error message.

9.10 Use CODESYS function blocks

Two function blocks are provided for the simple integration in (existing) CODESYS programs:
n FB_Compact
n FB_Extended

Function block Operating mode

FB_Compact HF compact
UHF compact
FB_Extended HF extended
UHF extended

The function blocks are part of the CODESYS package.

FB_Compact FB_Extended
BOOL xExecute xDone BOOL BOOL xExecute xDone BOOL
BOOL xAbort xBusy BOOL BOOL xAbort xBusy BOOL
UDINT udiTimeOut xError BOOL UDINT udiTimeOut xError BOOL
COMMAND eCommand xAborted BOOL COMMAND eCommand xAborted BOOL
REFERENCE TO Compact input_t rStatusMapping eError ERROR REFERENCE TO Extended input_t rStatusMapping eError ERROR
REFERENCE TO Compact output_t rContrlMapping xTP BOOL REFERENCE TO Extended output_t rContrlMapping xTP BOOL
UDINT udiStartAddress xRWHeadNotConnected BOOL UDINT udiStartAddress xRWHeadNotConnected BOOL
UINT uiDataLength uiDataRxLength UINT USINT usiUHFMemoryArea uiTagCounter UINT
POINTER TO BYTE pReadDataMapping UINT uiDataLength uiDataRxLength UINT
POINTER TO BYTE pWriteDataMapping SINT siLengthOfUidEpc
POINTER TO BYTE pDataTx POINTER TO BYTE pReadDataMapping
POINTER TO BYTE pDataRx POINTER TO BYTE pWriteDataMapping
POINTER TO BYTE pDataTx
POINTER TO BYTE pDataRx

Fig. 107: Function block FB_Compact Fig. 108: Function block FB_Extended

05.00 | 2019/11 189

Operation
Use CODESYS function blocks

Function blocks – Input variables

Name Data type Meaning
xExecute BOOL 0 Ò 1 Ò 0: Execute command
1 Ò 0 Ò 1: Reset outputs
The outputs can only be reset if an action was
ended beforehand or aborted by the user or if
an error occurred.
xAbort BOOL 0 Ò 1 Ò 0: Abort command execution. All
outputs are reset to the initial value.
udiTimeOut UDINT Time in µS, after which the function block
automatically ends command execution
eCommand COMMAND Command code in hexadecimal format,
[} 102]
rStatusMapping REFERENCE TO Start address of the process input data
Extended Input_t
rContrlMapping REFERENCE TO Start address of the process output data
Extended Out-
put_t
udiStartAddress UDINT Start address for the selected command, e.g.
start address in the memory of the tag
usiUHFMemoryArea USINT HF applications:
n Domain 0…5: User area of the tag
n Others: Reserved
UHF applications:
n Domain 0: Kill password
n Domain 1: EPC
n Domain 2: TID
n Domain 3: User memory
n Domain 4: Access password
n Domain 5: PC (size of EPC)
n Others: Reserved
uiDataLength UINT Length for the selected command, e.g. length
of the data to be read or written
siLengthOfUidEpc SINT Entry for the EPC or UID length for addressing
a specific tag to be read or written. The UID or
EPC must be defined in the write data.
0: Size of the EPC or UID not checked
-1: NEXT mode: A tag is always only read if the
UID/EPC is different to the UID/EPC of the last
read or written tag.
Only the values 0, -1 and 8 are possible in HF
applications.
pReadDataMapping POINTER TO BYTE Start address in the input data (ARRAY[..] OF
BYTE)
pWriteDataMapping POINTER TO BYTE Start address in the output data (ARRAY[..] OF
BYTE)
pDataTx POINTER TO BYTE Write data (ARRAY[..] OF BYTE)
pDataRx POINTER TO BYTE Read data (ARRAY [..] OF BYTE)

190 Hans Turck GmbH & Co. KG | T +49 208 4952-0 | F +49 208 4952-264 | [email protected] | www.turck.com
Function blocks – Output variables
Name Data type Meaning
xDone BOOL 1: Command successfully executed
0: Command not executed
xBusy BOOL 1: Command active
0: No command active
xError BOOL 1: Error detected, command execution aborted
0: No error detected
xAborted BOOL 1: Command execution aborted by user
0: Command execution not aborted
eError ERROR Error code, [} 209]
xTP BOOL 1: Tag within the detection range
0: No tag within the detection range
xRWHeadNotConnected BOOL 1: No read/write head connected
0: Read/write head connected
uiTagCounter UINT Shows the number of the detected tags. In HF
multitag applications and in UHF applications,
tags are only counted with an inventory com-
mand. In HF single-tag applications all tags are
counted that are detected by the read/write
head. The tag counter is reset after the follow-
ing commands:
n Inventory (exception: single-tag applica-
tions)
n Continuous mode
n Continuous presence sensing mode
n Reset
uiDataRxLength UINT Length for the selected command, e.g. length
of the data read or written
siLengthOfUidEpc SINT Entry for the EPC or UID length for addressing
a specific tag to be read or written. The UID or
EPC must be defined in the write data.
0: Size of the EPC or UID not checked
-1: NEXT mode: A tag is always only read if the
UID/EPC is different to the UID/EPC of the last
read or written tag.
Only the values 0, -1 and 8 are possible in HF
applications.
pReadDataMapping POINTER TO BYTE Start address in the input data (ARRAY[..] OF
BYTE)
pWriteDataMapping POINTER TO BYTE Start address in the output data (ARRAY[..] OF
BYTE)
pDataTx POINTER TO BYTE Write data (ARRAY[..] OF BYTE)
pDataRx POINTER TO BYTE Read data (ARRAY [..] OF BYTE)

05.00 | 2019/11 191

Operation
Use CODESYS function blocks

Example: Incorporating the function block

In order to run the function block, the package file for TBEN-RFID interfaces must be installed.
Call the Package Manager in CODESYS: Click Tools Ò Package Manager.

Fig. 109: Opening the Package Manager

Select the package file for TBEN-RFID interfaces and install.

Fig. 110: Installing a Package file

192 Hans Turck GmbH & Co. KG | T +49 208 4952-0 | F +49 208 4952-264 | [email protected] | www.turck.com
After the installation has been successfully completed, the Package file is displayed as follows
in the Package Manager:

Fig. 111: Display of the Package file in the Package Manager

Add the CODESYS library: Choose Add Library Ò Turck Ò Application Ò RFID Ò RFID
universal data interface.
Click OK to add the library to the project.

Fig. 112: Installing a CODESYS library

05.00 | 2019/11 193

Operation
Use CODESYS function blocks

Create program in which the function block can be called.

Add Box from the CODESYS ToolBox to the project.
Add FB_Compact or FB_Extended function block.

Fig. 113: Calling the function block

194 Hans Turck GmbH & Co. KG | T +49 208 4952-0 | F +49 208 4952-264 | [email protected] | www.turck.com
Create the required instances for the function block: Map inputs and outputs directly to
the addresses of the corresponding module registers.
Activate the function block.
In the following example 128 bytes can be read or written via the function block. The input and
output data and the write and read data is assigned in the example as follows:
Byte Meaning
IB100 Start address of the process input data
QB100 Start address of the process output data
IB116 Address of the read data as array
QB116 Address of the write data as array

Fig. 114: Activate the FB_Extended function block (example: Read or write 128 bytes)

05.00 | 2019/11 195

Operation
Use CODESYS function blocks

Fig. 115: FB_Extended function block – Overview of the inputs and outputs

NOTE
When using function blocks, the UID is not automatically displayed in Idle mode. The
device does not have to be reset to Idle mode between two identical commands.

196 Hans Turck GmbH & Co. KG | T +49 208 4952-0 | F +49 208 4952-264 | [email protected] | www.turck.com
9.11 Using function blocks for Siemens TIA portal
Two function blocks are provided for the simple integration in (existing) programs in the TIA
portal:
n RFID_COMPACT_Mode
n RFID_EXTENDED_Mode

Function block Operating mode

RFID_COMPACT_Mode HF compact
UHF compact
RFID_EXTENDED_Mode HF extended
UHF extended

The function blocks can be downloaded as elements of example programs free of charge at
www.turck.com. The example programs are available for TIA V14 and TIA V15 and the Siemens
S7-1200 and S7-1500 controllers.
The required command can be selected via the FC20 and FC30 functions. More parameters can
be set on function block FB10 (Compact) and FB11 (Extended).

FC10
BOOL xCmdRead wCMDC HEX
BOOL xCmdWrite
BOOL xCmdReset
BOOL xCmdInventory
BOOL xCmdTagInfo
BOOL xCmdDirectExecute
HEX wDirectCommandCode

Fig. 116: FC10 function block

FB10
DEC HwID_HFcompact RESC HEX
HEX CMDC BUSY BOOL
DEC RCNT ERROR BOOL
DEC DOM RCNT_F DEC
DEC ADDR TP1 BOOL
DEC LEN XDx BOOL
DEC SOUID PNSx BOOL
DEC HwID_Read016B TREx BOOL
DEC HwID_Write016B TNCx BOOL
POINTER WriteDataBuﬀer 16B TONx BOOL
CMON BOOL
LEN_F DEC
ERRC HEX
TCNT DEC
ReadDataBuﬀer 16B POINTER

Fig. 117: FB10 function block

05.00 | 2019/11 197

Operation
Using function blocks for Siemens TIA portal

FB11
DEC HwID_HFextended RESC HEX
HEX CMDC BUSY BOOL
DEC RCNT ERROR BOOL
DEC DOM RCNT_F DEC
DEC ADDR TP1 BOOL
DEC LEN XDx BOOL
DEC SOUID PNSx BOOL
DEC TOUT TREx BOOL
DEC RFN TNCx BOOL
DEC WFN TONx BOOL
DEC HwID_Read128B CMON BOOL
DEC HwID_Write128B LEN_F DEC
POINTER WriteDataBuﬀer 128B ERRC HEX
TCNT DEC
BYFI DEC
RFN_F DEC
WFN_F DEC
ReadDataBuﬀer 128B POINTER

Fig. 118: FB11 function block

Input variables – FC10 and FC11

Name Data type Meaning
xCmdRead BOOL 0 Ò 1 Ò 0: Executing a read command
xCmdWrite BOOL 0 Ò 1 Ò 0: Execute write command
xCmdReset BOOL 0 Ò 1 Ò 0: Reset command
xCmdInventory BOOL 0 Ò 1 Ò 0: Executing the Inventory command
xCmdTagInfo BOOL 0 Ò 1 Ò 0: Execute Tag info command
xCmdDirectExecute BOOL 0 Ò 1 Ò 0: Execute direct command
wDirectCommandCode HEX Command code of the direct command

Input variables – FB10 and FB11

Name Data type Meaning
HwID_HFcompact DEC Hardware identifier of the module
CMDC HEX Command code, see the description of the
output data, [} 98]
RCNT DEC Loop counter for fast processing, see descrip-
tion of the output data, [} 98]
DOM DEC Memory area (can only be used with UHF ap-
plications), see description of the output data,
[} 98]
ADDR DEC Start address in bytes, see description of the
output data, [} 98]
LEN DEC Length in bytes, see description of the output
data, [} 98]
SOUID DEC Length of UID/EPC in bytes, see description of
the output data, [} 98]
TOUT DEC Timeout, see description of the output data,
[} 98]

198 Hans Turck GmbH & Co. KG | T +49 208 4952-0 | F +49 208 4952-264 | [email protected] | www.turck.com
Name Data type Meaning
RFN DEC Read fragment no., see description of the out-
put data, [} 98]
WFN DEC Write fragment no., see description of the out-
put data, [} 98]
HwID_Read016B DEC Hardware identifier for the read data
(RFID_COMPACT_Mode)
HwID_Read128B
(RFID_EXTENDED_Mode)
HwID_Write016B DEC Hardware identifier for the write data
(RFID_COMPACT_Mode)
HwID_Write128B
(RFID_EXTENDED_Mode)
WriteDataBuffer16B POINTER Write data
(RFID_COMPACT_Mode)
WriteDataBuffer128B
(RFID_EXTENDED_Mode)

Output variables – FB10 and FB11

Name Data type Meaning
RESC HEX Response code, see description of the input
data, [} 92]
BUSY BOOL Status of the command execution, see descrip-
tion of the input data, [} 92]
ERROR BOOL Error, see description of the input data, [} 92]
RCNT_F DEC Loop counter for fast processing, see descrip-
tion of the input data, [} 92]
TP1 BOOL Tag present, see description of the input data,
[} 92]
XDx BOOL HF read/write head at address x not tuned, see
description of the input data, [} 92]
PNSx BOOL Parameter of read/write head at address x not
supported, see description of the input data,
[} 92]
TREx BOOL Read/write head at address x reports error, see
description of the input data, [} 92]
TNCx BOOL Expected read/write head with address x not
connected, see description of the input data,
[} 92]
TONx BOOL HF read/write head switched on, see descrip-
tion of the input data, [} 92]
CMON BOOL Continuous (Presence sensing mode) active,
see description of the input data, [} 92]
LEN_F DEC Length, see description of the input data,
[} 92]
ERRC HEX Error code, see description of the input data,
[} 92]
TCNT DEC Tag counter, see description of the input data,
[} 92]

05.00 | 2019/11 199

Operation
Using function blocks for Siemens TIA portal

Name Data type Meaning

BYFI DEC Data (bytes) available, see description of the
(RFID_EXTENDED_Mode) input data, [} 92]
RFN_F DEC Read fragment no., see description of the input
(RFID_EXTENDED_Mode) data, [} 92]
WFN_F DEC Write fragment no., see description of the in-
(RFID_EXTENDED_Mode) put data, [} 92]
ReadDataBuffer 16B DEC Read data
(RFID_COMPACT_Mode)
ReadDataBuffer 128B
(RFID_EXTENDED_Mode)

200 Hans Turck GmbH & Co. KG | T +49 208 4952-0 | F +49 208 4952-264 | [email protected] | www.turck.com
9.12 Using Inventory command and Continuous (presence sensing) mode
The Inventory command and Continuous (presence sensing) mode transfer data to the PLC in
different ways. Continuous mode is suitable for high-speed applications, in which a command
(e.g. read or write) is to be performed repetitively. Repeated execution of the same command
by the controller is unnecessary.

The following lists the most important differences between an Inventory command and Con-
tinuous mode:
Inventory Continuous mode Continuous presence sensing
mode
Triggered reading of UID or n Repeated reading of UIDs n UHF read/write head
EPC and EPCs switches on as soon as a tag
n Automatic repetition of the is detected
same command (e.g. In- n Repeated reading of UIDs
ventory, read, write) and EPCs
n Automatic repetition of the
same command (e.g. In-
ventory, read, write)
Data is displayed in the read Data must be read from the Data must be read from the
data after the command has memory of the interface with a memory of the interface with a
ended. separate command. separate command.
Grouping of EPCs possible Grouping of EPCs possible Grouping of EPCs possible
No buffering on the read/write No buffering on the read/write No buffering on the read/write
head head head
Terminate command: Terminate command: Terminate command:
1. Timeout 1. Timeout 1. Timeout
2. Automatically after com- 2. Separate command 2. Separate command
mand execution

05.00 | 2019/11 201

Operation
LEDs

9.13 LEDs
The device has the following LED indicators:
n Power supply
n Group and bus errors
n Status
n Diagnostics

PWR LED
LED green LED red Meaning
Off Off No voltage or undervoltage at V1
Lit Off Voltage at V1 and V2 ok
Off Lit No voltage or undervoltage at V2

BUS LED
LED green LED red Meaning
Off Off No voltage present
Lit Off Logical connection to a master established
Flashes 3 × green in Off ARGEE/FLC active
2 s
Flashing (1 Hz) Lit Device is operational
Off Lit IP address conflict or Modbus connection timeout
Off Flashing (1 Hz) Wink command active: A Wink command enables the identification of
nodes on an Ethernet network. If a device is an Ethernet node and re-
ceives a Wink command, it responds with an optical signal (e.g. flashing
LED).
Flashing (1 Hz) Flashing (1 Hz) Auto-negotiation and/or DHCP/BootP search of the settings

ERR LED
LED green LED red Meaning
Off Off No voltage present
Lit Off No diagnostics, device running error-free
Off Lit Diagnostics present

ETH 1 and ETH2 LED

LED green LED red Meaning
Off Off No Ethernet connection
Lit Off Ethernet connection established, 100 Mbit/s
Flashing Off Data transfer, 100 Mbit/s
Off Lit Ethernet connection established, 10 Mbit/s
Off Flashing Data transfer, 10 Mbit/s

202 Hans Turck GmbH & Co. KG | T +49 208 4952-0 | F +49 208 4952-264 | [email protected] | www.turck.com
RFID channel LEDs Ident 0 and Ident 1
TP… LED green TP… LED red Meaning
Off Off No tag within the detection range
Lit Off Tag within the detection range
Flashing Off Tag in the detection range, command is processed
Flashing (1 Hz) Flashing (1 Hz) Connection with DTM. No connection to controller active.
Off Lit Diagnostics present
CMD… LED green CMD... LED red
Off Off Read/write head switched off
Lit Off Read/write head switched on
Flashing Off BUSY (command active)
Off Flashing Interface memory full
Off Lit Error in the data interface
TP… and CMD… flash red simultan- Overload of the auxiliary voltage
eously
TP… and CMD… flash red alternately Parameter error

DXP channel LEDs

LED green LED red Meaning (input) Meaning (output)
Off Off Input level below max. input level Output not active
Lit Off Input level above max. input level Output active (max. 0.5 A)
Off Lit – Actuator overload
Off Flashing Overload of the auxiliary voltage

With a Wink command the DXP7 LED flashes white.

05.00 | 2019/11 203

Operation
Software diagnostic messages

9.14 Software diagnostic messages

9.14.1 Diagnostic messages – Gateway functions
Byte no. Bit
7 6 5 4 3 2 1 0
0 V2 ARGEE DIAG
1 FCE COM V1

Meaning of the diagnostic bits

Designation Meaning
V2 Undervoltage at power supply connection V2
ARGEE ARGEE project active
DIAG Module diagnostics present
FCE Force mode in the DTM active
COM Internal error
V1 Undervoltage at power supply connection V1

Meaning of the diagnostic bits

Designation Meaning
VAUX Overvoltage at power supply terminal VAUX
PRMER Parameter error
DTM Configuration via the DTM active
FIFO Buffer full
TNC… Expected read/write head not found
TRE… Read/write head reports error
PNS… Parameter not supported by read/write head
XD… Read/write head not tuned

204 Hans Turck GmbH & Co. KG | T +49 208 4952-0 | F +49 208 4952-264 | [email protected] | www.turck.com
9.14.3 Diagnostic messages – Digital channels
Byte no. Bit
7 6 5 4 3 2 1 0
0 VAUX VAUX
1 ERR7 ERR6 ERR5 ERR4

Meaning of the diagnostic bits

Designation Meaning
VAUX Overvoltage at power supply terminal VAUX
ERR... Error message on channel x

9.14.4 Diagnostic messages – Module status

Meaning of the diagnostic bits

Byte no. Bit

7 6 5 4 3 2 1 0
0 V2 ARGEE DIAG
1 FCE COM V1

05.00 | 2019/11 205

Operation
Example: Activating diagnostics via the PLC software

9.15 Example: Activating diagnostics via the PLC software

The following example describes the activation of diagnostic messages with CODESYS 3 in
PROFINET.
Include the device in an existing project and connect to the controller (example: Turck
TX510-P3CV01 HMI).
Right-click an empty slot.
Click Plug device.

Fig. 119: Selecting an empty slot for diagnostics

206 Hans Turck GmbH & Co. KG | T +49 208 4952-0 | F +49 208 4952-264 | [email protected] | www.turck.com
Click RFID diagnostics.

Fig. 120: Selecting RFID diagnostics

05.00 | 2019/11 207

Operation
Example: Activating diagnostics via the PLC software

Do not close the window.

Select the next free slot.
Select DXP diagnostics and confirm with Plug device.

Fig. 121: Selecting DXP diagnostics

The diagnostics can be read via the PLC program.

208 Hans Turck GmbH & Co. KG | T +49 208 4952-0 | F +49 208 4952-264 | [email protected] | www.turck.com
9.16 Reading error codes
The error codes are part of the process input data.
Error code (hex.) Error code (dec.) Meaning
0x8000 32768 Channel not active
0x8001 32769 Read/write head not connected
0x8002 32770 Memory full
0x8003 32771 Block size of the tag not supported
0x8004 32772 Length exceeds the size of the read fragment
0x8005 32773 Length larger than the size of the write fragment
0x8006 37774 Read/write head does not support HF bus mode
0x8007 32775 Only one read/write head should be connected for addressing.

0x8100 33024 Parameter undefined

0x8101 33025 Operating mode parameter outside of the permissible range
0x8102 33026 Tag type parameter outside of the permissible range
0x8103 33027 Operating mode parameter in Continuous mode outside of the permiss-
ible range
0x8104 33028 Length parameter in Continuous mode outside of the permissible range
0x8105 33029 Size of the write fragment outside of the permissible range
0x8106 33030 Size of the read fragment outside of the permissible range
0x81FD 33021 Bridging time parameter outside of the permissible range
0x81FE 33022 “Address” parameter in Continuous mode outside of the permissible
range
0x81FF 33023 No read/write head selected

0x8200 33280 Command code unknown

0x8201 33281 Command not supported
0x8202 33282 Command not supported in HF applications
0x8203 33283 Command not supported in UHF applications
0x8204 33284 Command for multitag application with automatic tag detection not sup-
ported
0x8205 33285 Command for applications with automatic tag detection not supported
0x8206 33286 Command only supported for applications with automatic tag detection
0x8207 33287 Command not supported for multitag application
0x8208 33288 Command not supported in HF bus mode
0x8209 33289 “Length” parameter outside of the permissible range
0x820A 33290 Address outside of the permissible range
0x820B 33291 Length and address outside of the permissible range
0x820C 33292 No tag found
0x820D 33293 Timeout
0x820E 33294 Next command not supported in multitag mode
0x820F 33295 Length of the UID outside of the permissible range
0x8210 33296 Length outside of the tag specification
0x8211 33297 Address outside of the tag specification

05.00 | 2019/11 209

Operation
Reading error codes

Error code (hex.) Error code (dec.) Meaning

0x8212 33298 Length and address outside of the tag specification
0x8213 33299 Memory area of the tag outside of the permissible range
0x8214 33300 Read/write head address outside of the permissible range
0x8215 33301 Value for timeout outside of the permissible range
0x8216 33302 Command only possible in HF bus mode
0x8217 33303 HF read/write head address invalid

0x8300 33536 Continuous mode command not activated

0x8301 33537 Grouping not supported in HF applications
0x8302 33538 Grouping not supported with read commands
0x8304 33540 Grouping not supported with write commands
0x8305 33541 HF: Length in Continuous mode violates the block limits
0x8306 33542 HF: Address in Continuous mode violates the block limits
0x8307 33543 HF: Length in Continuous mode outside of the permissible range

0x0801 2049 Write or read error

0x2000 8192 Kill command not successful

0x2200 8704 Automatic tuning active
0x2201 8705 Automatic tuning failed
0x2202 8706 Read/write head detuned

0x2500 9472 Password function not supported by tag

0x2501 9473 Password function not supported by read/write head
0x2900 10496 Address outside of the block limits
0x2901 10497 Length outside of the block limits

0xC000 49152 Internal error (response of the read/write head too short)
0xC001 49153 Command not supported by read/write head version

0xB0… 45… HF read/write head reports error

0xB048 45128 Error when switching on the HF read/write head
0xB049 45129 Error when switching off the HF read/write head
0xB060 45152 Error with the extended parameter setting of the HF read/write head
0xB061 45153 Error with the parameter setting of the HF read/write head
0xB062 45154 Read/write head error when executing an Inventory command
0xB067 45159 Read/write head error when executing a lock block command
0xB068 45160 Read/write head error when executing a read multiple block command
0xB069 45161 Read/write head error when executing a write multiple block command
0xB06A 45162 Error when reading the system information
0xB06B 45163 Error when reading the protection status of the tags
0xB0AD 45229 Error when setting the read/write head address
0xB0BD 45245 Error when setting the transfer rate

210 Hans Turck GmbH & Co. KG | T +49 208 4952-0 | F +49 208 4952-264 | [email protected] | www.turck.com
Error code (hex.) Error code (dec.) Meaning
0xB0DA 45274 Error with the “Tag in detection range” function
0xB0E0 45280 Error when reading the read/write head version
0xB0E1 45281 Error when reading the extended read/write head version
0xB0F1 45297 Error with automatic read/write head tuning
0xB0F8 45304 Error when resetting a command in Continuous mode
0xB0FA 45306 Error when outputting the response code
0xB0FF 45311 Error when resetting the read/write head
0xB0B3 45235 Error when setting the tag password
0xB0B6 45238 Error when setting the write or read protection
0xB0B8 45240 Error when reading the protection status of the memory area on the tag
0xB0C3 45251 Error when setting the password in the read/write head

0xD0… 53… UHF read/write head reports error

0xD001 53249 Error when resetting the UHF read/write head
0xD002 53250 Error when reading the read/write head version
0xD003 53251 Error when reading the read/write head version when a tag is in the detec-
tion range
0xD004 53252 Error when setting the read/write head address
0xD009 53257 Error with the parameter setting of the UHF read/write head
0xD00A 53258 Error when setting the transfer speed and the operating mode of the UHF
read/write head
0xD00B 53259 Error when polling
0xD00D 53261 Error when reading the device status
0xD00E 53262 Error when resetting the internal status bit
0xD00F 53263 Error when setting the read/write head outputs and/or LEDs
0xD011 53265 Error when reading the internal malfunctions
0xD014 53268 Diagnostics error
0xD016 53270 Error with the heartbeat message
0xD017 53271 Error when outputting the user settings
0xD01B 53275 Error when emptying the message memory in Polling mode
0xD081 53377 Error when switching the UHF tag on or off
0xD083 53379 Error when reading from a tag
0xD084 53380 Error when writing to a tag
0xD085 53381 Software trigger error
0xD088 53384 Error when outputting a command according to EPC Class1 Gen2

0xD100 53504 Error with the Backup function

0xD101 53505 Error with the Backup function (required memory not available)
0xD102 53506 Error when restoring a backup
0xD103 53507 Error when restoring a backup (no backup present)
0xD104 53508 Error when restoring a backup (backup data damaged)
0xD105 53509 Error when restoring the default settings
0xD106 53510 Error with the tag function

05.00 | 2019/11 211

Operation
Reading error codes

Error code (hex.) Error code (dec.) Meaning

0xF0… 61… ISO -15693 error

0xF001 61441 ISO -15693 error: Command not supported
0xF002 61442 ISO -15693 error: Command not detected, e.g. incorrect input format
0xF003 61443 ISO -15693 error: Command option not supported
0xF00F 61455 ISO-15693 error: undefined error
0xF010 61456 ISO-15693 error: Addressed memory area not available
0xF011 61457 ISO-15693 error: Addressed memory area locked
0xF012 61458 ISO -15693 error: Addressed memory area locked and not writable
0xF013 61459 ISO -15693 error: Write operation not successful
0xF014 61460 ISO -15693 error: Addressed memory area could not be locked
0xF0A0…0xF0DF 61600…61663 Air interface error

0xF101 61697 Air interface error: CRC error

0xF102 61698 Air interface error: Timeout
0xF103 61699 Air interface error: UHF tag error
0xF108 61704 Air interface error: UHF tag outside of the detection range, before all com-
mands could be executed
0xF110 61712 Air interface error: Tag does not have the expected UID.

0xF201 61953 HF read/write head faulty

0xF202 61954 HF read/write head: Error in command execution
0xF204 61956 HF read/write head: Transmission error, check syntax
0xF208 61960 Power supply of the HF read/write head too low
0xF20A 61962 HF read/write head: Command code unknown

0xF8… 63… UHF read/write head error

0xF820 63520 UHF read/write head: Command not supported
0xF821 63521 UHF read/write head: unspecified error
0xF822 63522 UHF read/write head: A valid password is expected before the command
is accepted.
0xF824 63524 UHF read/write head: Read operation not possible (e.g. invalid tag)
0xF825 63525 UHF read/write head: Write operation not possible (e.g. tag can only be
read)
0xF826 63526 UHF read/write head: Write or read error
0xF827 63527 UHF read/write head: Access to unknown address (e.g. memory area out-
side of range)
0xF828 63528 UHF read/write head: The data to be sent is not valid.
0xF82A 63530 UHF read/write head: The command requires a long time for execution.
0xF82C 63532 UHF read/write head: The requested object is not in the persistent
memory.
0xF82D 63533 UHF read/write head: The requested object is not in the volatile memory.
0xF835 63541 UHF read/write head: The command is temporarily not permissible.

212 Hans Turck GmbH & Co. KG | T +49 208 4952-0 | F +49 208 4952-264 | [email protected] | www.turck.com
Error code (hex.) Error code (dec.) Meaning
0xF836 63542 UHF read/write head: The opcode is not valid for this type of configuration
memory.
0xF880 63616 UHF read/write head: no tag in the field
0xF881 63617 UHF read/write head: The EPC of the command does not match the EPC in
the detection range.
0xF882 63618 UHF read/write head: Incorrect tag type specified in the command
0xF883 63619 Write command to a block failed

0xFFFE 65534 Timeout on the RS485 interface

0xFFFF 65535 Command aborted

05.00 | 2019/11 213

Operation
Using extended diagnostics – Time measurement for commissioning an application

9.17 Using extended diagnostics – Time measurement for commissioning an

application
The time of the transmission from the tag to the interface is taken as the time measurement.
The data transmission to a controller is not included.

If a particular tag is selected in the HF: Select tag type parameter, the time measurement for
the write command is already started with its activation. The time measurement is carried out
irrespective of whether a tag is present in the detection range. The time measurement function
is available for read/write heads from firmware version 1.91.

The following values can be displayed in the web server or in the DTM for extended diagnostics
and for system tests. Actual as well as minimum and maximum values are available.
n Time in which the Tag present bit is set
n Duration of an Inventory command
n Duration of a read command
n Duration of a write command
n Cycle time of HF bus mode
n Cycle time of HF Continuous bus mode

214 Hans Turck GmbH & Co. KG | T +49 208 4952-0 | F +49 208 4952-264 | [email protected] | www.turck.com
Example: Opening extended diagnostics with the PACTware™ FDT/DTM frame application
Open Diagnose in PACTware™.
Select the RFID channel (here: Channel 0).
a The Expert mode on/off button is displayed in the menu bar.
Activate Expert mode.
The time measurement is shown.

Fig. 122: Time measurement in the DTM

05.00 | 2019/11 215

Operation
Using extended diagnostics – Time measurement for commissioning an application

Example: Opening extended diagnostics in the web server

Open the web server.
Log into the device.
Choose Station Ò RFID measurements.

Fig. 123: Time measurement in the web server

216 Hans Turck GmbH & Co. KG | T +49 208 4952-0 | F +49 208 4952-264 | [email protected] | www.turck.com
10 Troubleshooting
If the device does not function as expected, first check whether ambient interference is present.
If there is no ambient interference present, check the connections of the device for faults.
If there are no faults, there is a device malfunction. In this case, decommission the device and
replace it with a new device of the same type.

05.00 | 2019/11 217

Maintenance
Executing the Firmware Update

11 Maintenance
Ensure that the plug connections and cables are always in good condition.
The devices are maintenance-free, clean dry if required.

11.1 Executing the Firmware Update

The firmware of the device can be updated via FDT/DTM. The PACTware™ FDT frame applica-
tion, the DTM for the device and the current firmware are available as downloads free of charge
from www.turck.com.

NOTICE
Interruption of the power supply during the firmware update
Risk of device damage due to faulty firmware update
Do not interrupt the power supply during the firmware update.
During the firmware update do not reset the power supply.

Example: Update the Firmware with the PACTware™ FDT Frame Application
Launch PACTware™.
Right-click Host PC Ò Add device.

Fig. 124: Adding a Device in PACTware™

218 Hans Turck GmbH & Co. KG | T +49 208 4952-0 | F +49 208 4952-264 | [email protected] | www.turck.com
Select BL Service Ethernet and confirm with OK.

Fig. 125: Selecting the Ethernet interface

Double-click the connected device.

a PACTware™ opens the busaddress management.

Fig. 126: Opening the busaddress management

05.00 | 2019/11 219

Maintenance
Executing the Firmware Update

Search for connected Ethernet devices: Click the Search icon.

Select the required device.

Fig. 127: Selecting the device

220 Hans Turck GmbH & Co. KG | T +49 208 4952-0 | F +49 208 4952-264 | [email protected] | www.turck.com
Click Firmware Download to start the firmware update.

Fig. 128: Starting the firmware update

05.00 | 2019/11 221

Maintenance
Returning devices

Select the storage location and confirm with OK.

a PACTware™ shows the progress of the firmware update with a green bar at the bottom of
the screen.

Fig. 129: Firmware update in progress

12 Repair
The device must not be repaired by the user. The device must be decommissioned if it is faulty.
Observe our return acceptance conditions when returning the device to Turck.

12.1 Returning devices

Returns to Turck can only be accepted if the device has been equipped with a Decontamination
declaration enclosed. The decontamination declaration can be downloaded from
https://www.turck.de/en/retoure-service-6079.php
and must be completely filled in, and affixed securely and weather-proof to the outside of the
packaging.

13 Disposal
The devices must be disposed of correctly and must not be included in normal
household garbage.

222 Hans Turck GmbH & Co. KG | T +49 208 4952-0 | F +49 208 4952-264 | [email protected] | www.turck.com
14 Technical data
Technical data
Power supply
Power supply voltage 24 VDC
Permissible range 18…30 VDC
Total current max. 4 A per voltage group
Total current V1 + V2 max. 5.5 A at 70 °C per
module
Voltage supply connection 2 × M8, 4-pin
Operating current V1: max. 120 mA
V2: max. 30 mA
RFID power supply Sockets C0…C1 from V1 short-circuit proof,
1.2 A ≤ 55 °C, 55 °C < 0.5 A ≤ 70 °C per channel
Sensor/actuator supply Sockets C2…C3 from V2 short-circuit proof,
0.14 A < 55 °C, 55 °C < 0.05 A < 70 °C
Potential isolation Galvanic isolation of V1 and V2 voltage group
Voltage proof up 500 VDC
System data
Ethernet transfer rate 10 Mbit/s / 100 Mbit/s
Ethernet connection technology 2 × M8, 4-pin, D-coded
Protocol detection Automatic
Web server Default: 192.168.1.254
Service interface Ethernet via P1 or P2
Field Logic Controller (FLC)
ARGEE firmware version 3.3.5.0
ARGEE engineering version 2.0.26.0
Modbus TCP
Addressing Static IP, BOOTP, DHCP
Supported function codes FC1, FC2, FC3, FC4, FC5, FC6, FC15, FC16, FC23
Number of TCP connections 8
Input register start address 0 (0x0000)
Output register start address 2048 (0x0800)
EtherNet/IP™
Addressing As per EtherNet/IP™ specification
Quick Connect (QC) < 500 ms
Device Level Ring (DLR) Supported
Class 3 connections (TCP) 3
Class 1 connections (CIP) 10
Input assembly instance 103
Output assembly instance 104
Configuration assembly instance 106
PROFINET
Addressing DCP
Conformity class B (RT)

05.00 | 2019/11 223

Technical data

Technical data
MinCycleTime 1 ms
Fast start-up (FSU) < 500 ms
Diagnostics According to PROFINET Alarm Handling
Topology detection Supported
Automatic addressing Supported
Media redundancy protocol (MRP) Supported
System redundancy S2
RFID
No. of channels 2
Connection technology M12
Power supply 1.2 A ≤ 55 °C, 55 °C < 0.5 A ≤ 70 °C per channel,
short-circuit proof
Operation per channel 1 × HF or UHF read/write head, up to 32 bus-
capable HF read/write heads with suffix / C53
(if necessary additional power feed required)
RFID data interface HF and UHF
Cable length max. 50 m
Digital inputs
No. of channels 4
Connection technology of inputs M12, 5-pin
Input type pnp
Type of input diagnostics Channel diagnostics
Switch threshold EN 61131-2 Type 3, PNP
Signal voltage Low signal <5V
Signal voltage High signal > 11V
Signal current Low signal <1.5 mA
Signal current High signal > 2 mA
Input delay 0.05 ms
Potential isolation Galvanic isolation from the fieldbus, voltage
proof up to 500 VDC
Digital outputs
No. of channels 4
Connection technology of outputs M12, 5-pin
Output type pnp
Type of input diagnostics Channel diagnostics
Output voltage 24 VDC from potential group V2
Output current per channel 0.5 A, short-circuit resistance
Utilization factor 1 (0.03 > 55 °C)
Load type EN 60947-5-1: DC-13
Short-circuit protection Yes
Potential isolation Galvanic isolation from the fieldbus, voltage
proof up to 500 VDC

224 Hans Turck GmbH & Co. KG | T +49 208 4952-0 | F +49 208 4952-264 | [email protected] | www.turck.com
Technical data
Conformity with standard/directive
Vibration test according to EN 60068-2-6, acceleration up to
20 g
Shock testing Acc. to EN 60068-2-27
Drop and topple Acc. to IEC 60068-2-31/IEC 60068-2-32
EMC (electromagnetic compatibility) Acc. to EN 61131-2
Approvals and certificates CE
FCC
UV resistant acc. to DIN EN ISO 4892-2A (2013)
UL certificate cULus LISTED 21 W2, Encl.type 1 IND.CONT.EQ.
General information
Dimensions (W × L × H) 32 × 144 × 31 mm
Operating temperature -40…+70 °C
Storage temperature -40…+70 °C
Operating height max. 5000 m
Protection class IP65/IP67/IP69K
MTTF 179 years acc. to SN 29500 (Ed. 99) 20 °C
Housing material PA6-GF30
Housing color Black
Material of label Polycarbonate
Halogen-free Yes
Mounting 2 fixing holes, Ø 4.6 mm

05.00 | 2019/11 225

Appendix: Flow charts showing the operation of the device
Flow chart: Command processing

15 Appendix: Flow charts showing the operation of the device

The flow charts explain the operation of the device as well as the processing of commands.

15.1 Flow chart: Command processing

Start

idle:
out.commandCode := 0
out.loopCount := 0

in.responseCode <> 0

initiate command:
out.commandCode :=
0x0002 READ

in.responseCode ≤ 0

busy

yes no
in.responseCode < 0x4000

done done
in.errorCode = 0x0000 in.errorCode = [0x0001…0xﬀﬀ ]

new command desired?

Fig. 130: Flow chart for command processing

226 Hans Turck GmbH & Co. KG | T +49 208 4952-0 | F +49 208 4952-264 | [email protected] | www.turck.com
15.2 Flow chart: Rapid command processing with loop counter

Start

idle:
out.commandCode := 0
out.loopCount := 0

in.loopCout <> 0
or
in.responseCode <> 0

select command:
out.commandCode :=
0x2002 LOOP_READ

initiate command:
out.loopCount :=
out.loopCount+1

(in.loopCount <> out.loopCount)

or
in.responseCode ≤ 0
busy

yes no
in.responseCode < 0x4000

done done
in.errorCode = 0x0000 in.errorCode = [0x0001…0xﬀﬀ ]

new command desired?

Fig. 131: Flow chart for fast command processing with loop counter

05.00 | 2019/11 227

Appendix: Flow charts showing the operation of the device
Flow chart: Command processing with fragmentation

15.3 Flow chart: Command processing with fragmentation

Start

idle:
out.loopCount := 0
out.commandCode := 0
out.writeFragmentNo := 0
out.readFragmentNo := 0

in.loopCount <> 0
or
in.responseCode <> 0

initiate command and send 1st fragment:

out.loopCount = out.loopCount+1
out.commandCode := [0x0001…0x3FFF]
out.length = length of writedata
out.writeFragmentNo := 1
out.writeData := part 1

in.write FragmentNo <> out.writeFragmentNo

no
more than one fragment left

yes
send next fragment:
out.writeFragmentNo := out.writeFragmentNo+1
out.writeData := part 2…(n-1)

in.writeFragmentNo <> out.writeFragmentNo

send last fragment:

out.writeFragmentNo := 0
out.readFragmentNo := 0
out.writeData := part n

in.responseCode < 0

busy

yes no
in.responseCode < 0x4000

in.errorCode = 0x0000 error

in.lengst = length of read data in.errorCode = [0x0001…0xﬀﬀ ]
in.readData = part 1

acknowledge 1st fragment

out.readFragmentNo := in.readFragmentNo

no
in.readFragmentNo <> 0
yes

out.readFragmentNo == in.readFragmentNo

in.readData = part 2…(n)

acknowledge next fragment

out.readFragmentNo := in.readFragmentNo

done

new command desired?

Fig. 132: Flow chart for command processing with fragmentation

228 Hans Turck GmbH & Co. KG | T +49 208 4952-0 | F +49 208 4952-264 | [email protected] | www.turck.com
15.4 Flow chart: Continuous mode with interruption before reading data
Idle:
Command Code = 0
Response Code = 0
Yes

Set output parameter:

- „Start address“ = 1
(Grouping EPCs for UHF)
- e.g. timeout

Set command:
Command Code = 0x0010

ERROR= TRUE
Response Code = Command Code Error Code

Manual stop OR Automatic stop

after timeout
Set command:
Command Code = 0x0012 „Continous mode active“ = False

Set parameter:
„Length“ := data (bytes) available

Set command:
Command Code := 0x0011

Read-Fragment +1
No
Data bytes available = 0

Yes

Done

Fig. 133: Flow chart for Continuous mode with interruption before reading data

05.00 | 2019/11 229

Appendix: Flow charts showing the operation of the device
Flow chart: Continuous mode without interruption before reading data

15.5 Flow chart: Continuous mode without interruption before reading data
Idle:
Command Code = 0
Response Code = 0
Yes

Set output parameter:

- „Start address“ := 1
(Grouping EPCs for UHF)

Set command:
Command Code := 0x0010

ERROR= TRUE
Response Code = Command Code Error Code

Set parameter:
„Length“ : deﬁne value

Set command:
Command Code := 0x0011

Read-Fragment +1
No
Data bytes available = 0

Yes

Set command:
Command Code := 0x0010

Set command:
Command Code := 0x0012

*) After increasing the Read Fragment No., the new data will be shown in the read data input.

Fig. 134: Flow chart for Continuous mode without interruption before reading data

230 Hans Turck GmbH & Co. KG | T +49 208 4952-0 | F +49 208 4952-264 | [email protected] | www.turck.com
16 Appendix: Declaration of Conformity
EU-Konformitätserklärung Nr.: 5035-2M
EU Declaration of Conformity No.:

Wir/ We: HANS TURCK GMBH & CO KG

WITZLEBENSTR. 7, 45472 MÜLHEIM A.D. RUHR
erklären in alleiniger Verantwortung, dass die Produkte
declare under our sole responsibility that the products

Kompakte I/O Module in IP20/IP67: Typen / types: FDN20-*, FDNL-*, FDNP-*, FDP20-*, FGDP-*, FGEN-*,
Compact I/O modules in FLDP-*, FLIB-*, FXEN-*, SDPX-*, TBDP-*, TBEN-*, TBIL-*, TBPN-*
IP20/IP67:

auf die sich die Erklärung bezieht, den Anforderungen der folgenden EU-Richtlinien durch Einhaltung der
folgenden Normen genügen:
to which this declaration relates are in conformity with the requirements of the following EU-directives by compliance with the following
standards:

EMV - Richtlinie /EMC Directive 2014 / 30 / EU 26.02.2014

EN 61131-2:2007 (Abschnitte / section 8, 9, 10)

RoHS – Richtlinie /RoHS Directive 2011 / 65 / EU 08.06.2011

Weitere Normen, Bemerkungen:

additional standards, remarks:

Zusätzliche Informationen:
Supplementary infomation:

Mülheim, den 13.07.2018

i.V. Dr. M. Linde, Leiter Zulassungen /Manager Approvals
Ort und Datum der Ausstellung / Name, Funktion und Unterschrift des Befugten /
Place and date of issue Name, function and signature of authorized person

05.00 | 2019/11 231

Over 30 subsidiaries and over
60 representations worldwide!

D500064 | 2019/11

D500064 www.turck.com

10GEPHY RTL8261N Brief Datasheet 0.1 20211029 TEMP (55429)
0% (1)
10GEPHY RTL8261N Brief Datasheet 0.1 20211029 TEMP (55429)
75 pages
A Hand Book On IOT: Dr. S. Arumuga Perumal
No ratings yet
A Hand Book On IOT: Dr. S. Arumuga Perumal
58 pages
Engineering - USB - HandWiki
No ratings yet
Engineering - USB - HandWiki
19 pages
8051 LAB Manual New
100% (2)
8051 LAB Manual New
189 pages
Bluetooth Modules - Martyn Currey PDF
100% (1)
Bluetooth Modules - Martyn Currey PDF
64 pages
DefCon22: All Your Badges Are Belong To Us
100% (2)
DefCon22: All Your Badges Are Belong To Us
46 pages
Communication Protocols
No ratings yet
Communication Protocols
10 pages
EEE 141 Lab Manuals
100% (1)
EEE 141 Lab Manuals
45 pages
120-21 TM RF Handbook
No ratings yet
120-21 TM RF Handbook
164 pages
Projects For Students: List of Silver Class Projects
80% (5)
Projects For Students: List of Silver Class Projects
64 pages
Atmega32 Dev Board - EFY March11 PDF
100% (3)
Atmega32 Dev Board - EFY March11 PDF
7 pages
Rfid Based Vehicle Monitoring and Toll Collection System
0% (1)
Rfid Based Vehicle Monitoring and Toll Collection System
38 pages
Basics of The Communication Protocol
100% (1)
Basics of The Communication Protocol
19 pages
Ebook - HardWare - RFID ISO 18000-6 SCS PDF
No ratings yet
Ebook - HardWare - RFID ISO 18000-6 SCS PDF
58 pages
Emerson Av Catalog 4825
No ratings yet
Emerson Av Catalog 4825
124 pages
Bluetooth Cia
No ratings yet
Bluetooth Cia
4 pages
RS485 Communications Interface: Technical Manual
No ratings yet
RS485 Communications Interface: Technical Manual
74 pages
BlackCatUSB Flash Memory Compatibiltiy
0% (1)
BlackCatUSB Flash Memory Compatibiltiy
3 pages
Portable DVD: Service Manual
No ratings yet
Portable DVD: Service Manual
47 pages
RF Controlled Appliance
No ratings yet
RF Controlled Appliance
14 pages
400amp True RMS AC/DC Clamp Meter: Model EX613
No ratings yet
400amp True RMS AC/DC Clamp Meter: Model EX613
14 pages
OP25 Windows 10 Virtual Machine Setup Guide July 10, 2022
No ratings yet
OP25 Windows 10 Virtual Machine Setup Guide July 10, 2022
30 pages
E Instruction Sk3010 3320
No ratings yet
E Instruction Sk3010 3320
16 pages
Backpack Anti-Theft Alarm: Instructables
No ratings yet
Backpack Anti-Theft Alarm: Instructables
31 pages
Ether Net IP
No ratings yet
Ether Net IP
91 pages
Mosfet Basics
No ratings yet
Mosfet Basics
14 pages
Wireless Sensor Network and Contiky OS
No ratings yet
Wireless Sensor Network and Contiky OS
144 pages
Manual IDEAL Series 700
No ratings yet
Manual IDEAL Series 700
17 pages
Nvite: Multi-Technology Reader
No ratings yet
Nvite: Multi-Technology Reader
2 pages
Capcom CPS2 Security Programming Guide
No ratings yet
Capcom CPS2 Security Programming Guide
19 pages
S8254A E.en - PT
No ratings yet
S8254A E.en - PT
24 pages
BM235 Manual EEVblog PDF
No ratings yet
BM235 Manual EEVblog PDF
30 pages
Wireless Technologies For Iot: Unit 3
No ratings yet
Wireless Technologies For Iot: Unit 3
24 pages
Rfid Readers Smart Card Readers
No ratings yet
Rfid Readers Smart Card Readers
1 page
Tablas Usadas en Seguridad Sap Erp
0% (1)
Tablas Usadas en Seguridad Sap Erp
3 pages
TOPEX SIMSERVER Installation en
No ratings yet
TOPEX SIMSERVER Installation en
50 pages
Home Automation Using Mobile
No ratings yet
Home Automation Using Mobile
19 pages
SQL Server Security Audit
100% (1)
SQL Server Security Audit
13 pages
Operating Instructions: AC Motors DR..71 - 315, DRN80 - 315
No ratings yet
Operating Instructions: AC Motors DR..71 - 315, DRN80 - 315
236 pages
USB in A NutShell
No ratings yet
USB in A NutShell
33 pages
Serial and Parallel Communication
No ratings yet
Serial and Parallel Communication
82 pages
Rs232 Serial Communication
100% (1)
Rs232 Serial Communication
4 pages
An Introduction To Virtualization
No ratings yet
An Introduction To Virtualization
27 pages
Rfid Reader Rs 232
No ratings yet
Rfid Reader Rs 232
11 pages
Android Security Lock Synopsis
No ratings yet
Android Security Lock Synopsis
13 pages
Battery Charger Solutions
No ratings yet
Battery Charger Solutions
32 pages
SCIO Access Control
No ratings yet
SCIO Access Control
21 pages
Remote Site Management Alarm & Control Brochure
No ratings yet
Remote Site Management Alarm & Control Brochure
3 pages
Triacs and Diacs
No ratings yet
Triacs and Diacs
4 pages
Mobile Remote Access Via Expressway Deployment Guide X8 11 4 PDF
No ratings yet
Mobile Remote Access Via Expressway Deployment Guide X8 11 4 PDF
75 pages
Hubs Are Used To Build A LAN by Connecting Different Computers in A Star/hierarchal Network
No ratings yet
Hubs Are Used To Build A LAN by Connecting Different Computers in A Star/hierarchal Network
4 pages
CAN-BUS Shield - Wiki
No ratings yet
CAN-BUS Shield - Wiki
9 pages
Testing A MOSFET
No ratings yet
Testing A MOSFET
5 pages
Virtual Ground Circuits
No ratings yet
Virtual Ground Circuits
11 pages
Why Mosfets Fail
No ratings yet
Why Mosfets Fail
2 pages
Manual Master
No ratings yet
Manual Master
147 pages
Your Electronics Open Source: DIY Bug - FM Audio Transmitter (Micro Spy)
No ratings yet
Your Electronics Open Source: DIY Bug - FM Audio Transmitter (Micro Spy)
7 pages
Simatic OPC UA Server and Client en
No ratings yet
Simatic OPC UA Server and Client en
24 pages
Biolite Mobile: Mobile Time Management System
No ratings yet
Biolite Mobile: Mobile Time Management System
2 pages
OS X Commands
No ratings yet
OS X Commands
4 pages
SDANDR696: Double DIN Android Stereo Receiver & Camera DVR System
100% (1)
SDANDR696: Double DIN Android Stereo Receiver & Camera DVR System
32 pages
Network Protcols: Throughput
No ratings yet
Network Protcols: Throughput
16 pages
Can Open Magic Manual
No ratings yet
Can Open Magic Manual
59 pages
Hands-On Lab Configure A System To Authenticate Using Kerberos
100% (1)
Hands-On Lab Configure A System To Authenticate Using Kerberos
10 pages
NetBackup 5240 Appliance Product Description - 3.0 Revision 2
No ratings yet
NetBackup 5240 Appliance Product Description - 3.0 Revision 2
66 pages
(New) Cisco 500-220 Practice Questions - Guaranteed Success On Your First Attempt!
No ratings yet
(New) Cisco 500-220 Practice Questions - Guaranteed Success On Your First Attempt!
7 pages
RHCE
No ratings yet
RHCE
5 pages
Sitrain Sitrain: Pleas Scroll Down For English Version
No ratings yet
Sitrain Sitrain: Pleas Scroll Down For English Version
7 pages
Serenity Guide
100% (1)
Serenity Guide
535 pages
Basic Principal of Communication - 2
No ratings yet
Basic Principal of Communication - 2
81 pages
Guidance Software Tableau TD3 User Guide PDF
No ratings yet
Guidance Software Tableau TD3 User Guide PDF
112 pages
Mid Term Paper 2019 Arnav Secondry Study of IoT Tech Globally
No ratings yet
Mid Term Paper 2019 Arnav Secondry Study of IoT Tech Globally
15 pages
15A04704 Data Communications & Networking
No ratings yet
15A04704 Data Communications & Networking
2 pages
Rubytech fgs-2924
No ratings yet
Rubytech fgs-2924
309 pages
B Qradar System Notifications
No ratings yet
B Qradar System Notifications
72 pages
HPE Networking Comware Switch Series 5945 Data sheet-PSN1010907030INEN
No ratings yet
HPE Networking Comware Switch Series 5945 Data sheet-PSN1010907030INEN
4 pages
Redp5011 BlueMixPoV
No ratings yet
Redp5011 BlueMixPoV
10 pages
Equallogic ps4100
No ratings yet
Equallogic ps4100
47 pages
Attia 2011
No ratings yet
Attia 2011
6 pages
What Is Cyber Propaganda? Cyber Propaganda Goals Cyber Propaganda Tactics Defending Against Cyber Propaganda
No ratings yet
What Is Cyber Propaganda? Cyber Propaganda Goals Cyber Propaganda Tactics Defending Against Cyber Propaganda
3 pages
T-BERD - MTS-4000 V2 Customer Presentation
No ratings yet
T-BERD - MTS-4000 V2 Customer Presentation
17 pages
Lecture 6 - Network Layer - Internet Protocol
No ratings yet
Lecture 6 - Network Layer - Internet Protocol
21 pages
Data Communication April 2021
No ratings yet
Data Communication April 2021
3 pages
Read/Write Head For Bus Line Topology With TBEN - TN-CK40-H1147/C53
No ratings yet
Read/Write Head For Bus Line Topology With TBEN - TN-CK40-H1147/C53
10 pages
TLP-CLEAR MIVD AIVD Advisory COATHANGER
No ratings yet
TLP-CLEAR MIVD AIVD Advisory COATHANGER
10 pages
Manual The Dude
No ratings yet
Manual The Dude
3 pages
Wireless Application Protocol: Rohan Pattnaik
No ratings yet
Wireless Application Protocol: Rohan Pattnaik
22 pages
Email Template Guide 2
No ratings yet
Email Template Guide 2
3 pages
Lighttpd
From Everand
Lighttpd
Andre Bogus
4/5 (2)
BeagleBone For Dummies
From Everand
BeagleBone For Dummies
Rui Santos
No ratings yet
Raspberry Pi 3 Model B for Beginners: Explore What Raspberry Pi 3 Model B Can Do
From Everand
Raspberry Pi 3 Model B for Beginners: Explore What Raspberry Pi 3 Model B Can Do
Jeffrey S. Waller
No ratings yet
Software-defined radio Second Edition
From Everand
Software-defined radio Second Edition
Gerardus Blokdyk
No ratings yet
Mobile Learning Smartphones A Complete Guide
From Everand
Mobile Learning Smartphones A Complete Guide
Gerardus Blokdyk
No ratings yet
Energy harvesting Third Edition
From Everand
Energy harvesting Third Edition
Gerardus Blokdyk
No ratings yet

RFID

Uploaded by

RFID

Uploaded by

Your Global Automation Partner

9.9.1 Access password ......................................................................................................................... 189

1.1 Target groups

1.2 Explanation of symbols used

1.3 Other documents

1.4 Feedback about these instructions

2 Notes on the product

2.2 Scope of delivery

2.3 Legal requirements

2.4 Manufacturer and service

n Sales: +49 208 4952-380

Outside Germany, please contact your local Turck representative.

3.1 Intended use

3.2 General safety notes

4.1 Device overview

4.1.1 Display elements

4.2 Properties and features

4.4 Functions and operating modes

4.4.1 Multiprotocol technology

Automatic protocol detection

Manual Protocol Selection

Protocol Dependent Functions

4.4.2 Data transfer to the PLC

4.4.3 RFID channels – Operating modes

TN-M18-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:

UHF compact mode

UHF extended mode

4.4.4 RFID commands

4.4.5 Loop counter function

4.4.7 Turck Field Logic Controller (FLC)

4.5 Technical accessories

5.1 Mounting devices in combination

Fig. 5: Mounting the device to a mounting plate.

5.3 DIN rail (TS35) mounting

Fig. 6: Mounting the module combination on a DIN rail

5.4 Mounting the device outdoors

5.5 Grounding the device

Fig. 7: Equivalent circuit, shielding concept

Grounding the device – Mounting on DIN rail

Grounding the device – Mounting on mounting plate

Removing the grounding strip

Fig. 11: Removing the grounding strip

Mounting the grounding clip

Fig. 12: Mounting the grounding clip

Fig. 13: M8 Ethernet connector

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

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

6.1.1 QuickConnect and Fast Start-Up applications

Fig. 15: M8 plug connectors for connecting the power supply

Fig. 16: Pin assignment of the power supply connections

6.3 Connecting RFID read/write heads

Fig. 17: M12 plug connector for connecting read/write heads

Fig. 18: RS485 – Pin assignment of the read/write head connections

The maximum permissible length of the bus is 50 m.

The following accessories are required for the bus mode:

TN-M18-H1147/C53 up to 32 per port

Fig. 22: HF bus mode setup

6.4 Connecting digital sensors and actuators

If a UHF read/write head is connected, the device must be set:

7.1 Setting the IP address

Fig. 26: Turck Service Tool – Start screen

The Turck Service Tool displays the connected devices.

Fig. 27: Turck Service Tool – found devices

 Click the required device.

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

Fig. 29: Turck Service Tool – Change device configuration

7.2 Connecting the device to a Modbus master

Adding an Ethernet adapter

Fig. 30: Project tree

 Select Add device.

Fig. 31: Adding an Ethernet adapter

Fig. 32: Adding a Modbus master

Adding a Modbus slave

Fig. 33: Adding a Modbus slave

Connect the device to Ethernet according to the pin assignment.

Click the required device.

Select Add device.

Double-click the Modbus TCP slave.

Select Turck under Module Type Vendor Filters.

In the following window click (Connect To Go Online) Download.

Confirm all the following messages.