rfid interface tben-l…-4rfid-8dxp8.108.10.1testing and parameterizing rfid interfaces via the...

Your Global Automation Partner

Instructions for Use

TBEN-L…-4RFID-8DXPRFID Interface

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

V02.00 | 2020/08 3

Contents1 About these Instructions................................................................................................................... 7

1.1 Target groups................................................................................................................... 71.2 Explanation of symbols used ........................................................................................ 71.3 Other documents ............................................................................................................ 71.4 Feedback about these instructions.............................................................................. 7

2 Notes on the Product ......................................................................................................................... 82.1 Product identification..................................................................................................... 82.2 Legal requirements......................................................................................................... 82.3 Manufacturer and service .............................................................................................. 8

3 For Your Safety.................................................................................................................................... 93.1 Intended use..................................................................................................................... 93.2 General safety notes ....................................................................................................... 9

4 Product Description ......................................................................................................................... 104.1 Device overview ............................................................................................................ 104.1.1 Display elements............................................................................................................................ 104.1.2 Operating elements ...................................................................................................................... 104.2 Properties and features................................................................................................ 114.3 Operating principle....................................................................................................... 114.4 Functions and operating modes ................................................................................ 114.4.1 Multiprotocol technology........................................................................................................... 124.4.2 Data transfer to the PLC............................................................................................................... 134.4.3 RFID channels – operating modes........................................................................................... 144.4.4 RFID commands ............................................................................................................................. 164.4.5 Loop counter function ................................................................................................................. 174.4.6 Configurable digital channels – functions............................................................................ 174.4.7 Turck Field Logic Controller (FLC) ............................................................................................ 174.5 Technical accessories.................................................................................................... 17

5 Installing............................................................................................................................................. 185.1 Mounting the device outdoors................................................................................... 185.2 Grounding the device................................................................................................... 195.2.1 Equivalent wiring diagram and shielding concept ........................................................... 195.2.2 Shielding of the fieldbus and I/O level ................................................................................... 195.2.3 Grounding the device – I/O level and fieldbus level ......................................................... 20

6 Connection......................................................................................................................................... 226.1 Connecting the modules to Ethernet ........................................................................ 226.1.1 QuickConnect and Fast Start-Up applications .................................................................... 226.2 Connecting the power supply .................................................................................... 236.3 Connecting RFID read/write heads............................................................................ 246.3.1 Connecting read/write heads for the HF bus mode.......................................................... 256.4 Connecting digital sensors and actuators................................................................ 26

7 Commissioning ................................................................................................................................. 277.1 Setting the IP address................................................................................................... 277.1.1 Setting the IP address via switches at the device............................................................... 277.1.2 Setting the IP address via the Turck Service Tool............................................................... 297.1.3 Setting the IP address via the web server ............................................................................. 32

Contents


7.2 Connecting the device to a Modbus master ............................................................ 337.2.1 Connecting the device with the controller .......................................................................... 337.2.2 Renaming a Modbus slave.......................................................................................................... 377.2.3 Setting up network interfaces................................................................................................... 387.2.4 Modbus TCP slave – setting the IP address .......................................................................... 397.2.5 Defining Modbus channels (registers) ................................................................................... 397.2.6 Connecting the device online with the controller............................................................. 417.2.7 Reading out process data ........................................................................................................... 417.2.8 Modbus TCP – mapping .............................................................................................................. 427.3 Connecting a device to an EtherNet/IP controller .................................................. 487.3.1 Installing an EDS file...................................................................................................................... 497.3.2 Connecting the device with the controller .......................................................................... 537.3.3 Connecting the device online with the controller............................................................. 607.3.4 Reading out process data ........................................................................................................... 627.3.5 Activating QuickConnect (QC) .................................................................................................. 657.4 Connecting a device to a Siemens controller .......................................................... 687.4.1 Installing a GSDML file ................................................................................................................. 687.4.2 Connecting the device with the controller .......................................................................... 707.4.3 Assigning the PROFINET device name ................................................................................... 717.4.4 Set the IP address in the TIA Portal.......................................................................................... 727.4.5 Connecting the device online with the controller............................................................. 737.4.6 Setting module parameters ....................................................................................................... 74

8 Setting ................................................................................................................................................ 758.1 RFID channels – parameter data ................................................................................ 778.1.1 Meaning of the parameter bits ................................................................................................. 788.1.2 HF applications – selecting the tag type ............................................................................... 808.1.3 HF applications – setting the bridging time (bypass time) ............................................ 828.1.4 HF applications – setting HF bus mode................................................................................. 838.1.5 UHF applications – setting Continuous presence sensing mode ................................ 888.1.6 UHF applications – transferring read/write head settings.............................................. 898.2 RFID channels – process input data ........................................................................... 908.2.1 Meaning of the status bits .......................................................................................................... 938.2.2 Tag in detection range (TP) – using bit or pre-loading the command....................... 958.3 RFID channels – process output data ........................................................................ 968.3.1 Meaning of the command bits.................................................................................................. 998.4 Digital channels – setting parameter data ............................................................ 1018.4.1 Meaning of the parameter bits .............................................................................................. 1018.5 Digital channels – process input data .................................................................... 1028.5.1 Meaning of the status bits ....................................................................................................... 1028.6 Digital channels – process output data.................................................................. 1038.6.1 Meaning of the command bits............................................................................................... 1038.7 Digital channels – setting switchable VAUX power supply ............................... 1048.7.1 VAUX switchable power supply – parameter data ......................................................... 1048.7.2 VAUX switchable power supply – output data ................................................................ 1058.8 RFID channels – overview of commands ............................................................... 1068.8.1 Command: Idle............................................................................................................................. 1088.8.2 Command: Inventory................................................................................................................. 1098.8.3 Read command............................................................................................................................ 1128.8.4 Command: Write ......................................................................................................................... 1138.8.5 Command: Write and verify .................................................................................................... 1158.8.6 Command: Continuous mode................................................................................................ 1178.8.7 Command: Get data from buffer command (Continuous mode/Continuous

presence sensing mode) .......................................................................................................... 119

V02.00 | 2020/08 5

8.8.8 Command: Continuous presence sensing mode (UHF) ............................................... 1228.8.9 Command: End Continuous (presence sensing) mode ................................................ 1238.8.10 Command: Read/write head identification....................................................................... 1248.8.11 Command: Switch off HF read/write head ........................................................................ 1258.8.12 Command: HF read/write head tuning............................................................................... 1268.8.13 Command: Query HF read/write head address ............................................................... 1278.8.14 Command: Set HF read/write head address ..................................................................... 1288.8.15 Direct read/write head command ........................................................................................ 1298.8.16 Command: Set tag password.................................................................................................. 1348.8.17 Command: Set read/write head password........................................................................ 1368.8.18 Command: Reset read/write head password ................................................................... 1378.8.19 Command: Set tag protection................................................................................................ 1388.8.20 Command: Query HF tag protection status ...................................................................... 1408.8.21 Command: Set permanent lock (Lock)................................................................................ 1428.8.22 Command: Tag info.................................................................................................................... 1448.8.23 Command: Kill UHF tag............................................................................................................. 1468.8.24 Command: Restore UHF read/write head settings ......................................................... 1478.8.25 Command: Backup settings of the UHF read/write head............................................. 1488.8.26 Command: Query error/status of UHF read/write head ............................................... 1498.8.27 Command: Reset ......................................................................................................................... 1538.9 Setting RFID interfaces via the web server............................................................ 1548.9.1 Opening a web server ............................................................................................................... 1548.9.2 Processing settings in the web server ................................................................................. 1558.10 Testing and parameterizing RFID interfaces via the DTM.................................. 1658.10.1 Connecting the device with the PC...................................................................................... 1658.10.2 Editing parameter data with the DTM – online parameterization............................ 1688.10.3 Reading process input data with the DTM – measured value.................................... 1698.10.4 Changing process output data with the DTM – simulation ........................................ 1708.10.5 Evaluating diagnostics with the DTM.................................................................................. 1718.10.6 Example: Executing a Read command with the DTM.................................................... 1728.11 Setting UHF read/write heads.................................................................................. 174

9 Operation ......................................................................................................................................... 1759.1 Executing a command and calling data................................................................. 1759.1.1 Typical times for command processing via a controller ............................................... 1759.2 Using fragmentation ................................................................................................. 1779.2.1 Example: Using fragmentation in the web server – read ............................................. 1779.2.2 Example: Using fragmentation in the web server – write............................................ 1839.3 Using commands with a loop counter function ................................................... 1889.4 HF applications – using Continuous mode............................................................ 1899.5 HF applications – using HF Continuous bus mode .............................................. 1909.6 Using HF bus mode .................................................................................................... 1929.6.1 Executing commands in HF bus mode ............................................................................... 1929.6.2 Replacing bus-capable read/write heads........................................................................... 1929.6.3 HF Continuous bus mode – data query and speed........................................................ 1929.7 Query UID in HF Continuous bus mode ................................................................. 1949.8 Using NEXT mode....................................................................................................... 1959.8.1 Example: Using NEXT mode for a Read command ......................................................... 1959.9 Using the UHF password function .......................................................................... 1969.9.1 Access password ......................................................................................................................... 1969.10 Use CODESYS function blocks ................................................................................. 1979.11 Using function blocks for Siemens TIA portal....................................................... 206

Contents


9.12 Using Inventory command and Continuous (presence sensing) mode .......... 2109.13 LEDs............................................................................................................................... 2119.14 Software diagnostic messages ................................................................................ 2139.14.1 Diagnostic messages – gateway functions........................................................................ 2139.14.2 Diagnostic messages – RFID channels ................................................................................ 2139.14.3 Diagnostic messages – digital channels............................................................................. 2149.14.4 Diagnostic messages – module status ................................................................................ 2149.15 Example: Activating diagnostics via the PLC software ....................................... 2159.16 Reading error codes................................................................................................... 2189.17 Using extended diagnostics – time measurement for commissioning an

application................................................................................................................... 2239.18 Reset device (Reset) ................................................................................................... 226

10 Troubleshooting ............................................................................................................................. 22710.1 Eliminate parameterization errors.......................................................................... 227

11 Maintenance.................................................................................................................................... 22811.1 Executing the firmware update via FDT/DTM ...................................................... 228

12 Repair ................................................................................................................................................ 23212.1 Returning devices....................................................................................................... 232

13 Disposal ............................................................................................................................................ 232

14 Technical Data................................................................................................................................. 233

15 Appendix: Flow Charts Showing the Operation of the Device .............................................. 23615.1 Flow chart: Command processing........................................................................... 23615.2 Flow chart: Rapid command processing with loop counter .............................. 23715.3 Flow chart: Command processing with fragmentation ...................................... 23815.4 Flow chart: Continuous mode with interruption before reading data ............ 23915.5 Flow chart: Continuous mode without interruption before reading data...... 240

16 Appendix: EU Declaration of Conformity .................................................................................. 241

V02.00 | 2020/08 7

1 About these InstructionsThese operating instructions describe the structure, functions and the use of the product andwill help you to operate the product as intended. Read these instructions carefully before usingthe 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, passon these instructions as well.

1.1 Target groupsThese instructions are aimed at qualified personal and must be carefully read by anyonemounting, commissioning, operating, maintaining, dismantling or disposing of the device.

1.2 Explanation of symbols usedThe following symbols are used in these instructions:

DANGERDANGER indicates a dangerous situation with high risk of death or severe injury ifnot avoided.

WARNINGWARNING indicates a dangerous situation with medium risk of death or severe in-jury if not avoided.

CAUTIONCAUTION indicates a dangerous situation of medium risk which may result in minoror moderate injury if not avoided.

NOTICENOTICE indicates a situation which may lead to property damage if not avoided.

NOTENOTE indicates tips, recommendations and useful information on specific actionsand facts. The notes simplify your work and help you to avoid additional work.

u CALL TO ACTIONThis symbol denotes actions that the user must carry out.

a RESULTS OF ACTIONThis symbol denotes relevant results of actions.

1.3 Other documentsBesides this document the following material can be found on the Internet at www.turck.com:

n Data sheetn EU Declaration of Conformityn Approvals

1.4 Feedback about these instructionsWe 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 inthe document, please send your suggestions to [email protected].

http://www.turck.commailto:[email protected]

Notes on the ProductManufacturer and service


2 Notes on the Product

2.1 Product identificationThese instructions apply to the following compact RFID interfaces:

n TBEN-L4-4RFID-8DXPn TBEN-L5-4RFID-8DXP

2.2 Legal requirementsThe device is subject to the following EC directives:

n 2014/30/EU (electromagnetic compatibility)n 2011/65/EU (RoHS Directive)

2.3 Manufacturer and serviceHans Turck GmbH & Co. KG Witzlebenstraße 7 45472 Mülheim an der Ruhr Germany

Turck supports you with your projects, from initial analysis to the commissioning of your applic-ation. The Turck product database contains software tools for programming, configuration orcommissioning, data sheets and CAD files in numerous export formats. You can access theproduct 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-380n Technology: +49 208 4952-390

Outside Germany, please contact your local Turck representative.

http://www.turck.de/products

V02.00 | 2020/08 9

3 For Your SafetyThe product is designed according to state-of-the-art technology. However, residual risks stillexist. Observe the following warnings and safety notices to prevent damage to persons andproperty. Turck accepts no liability for damage caused by failure to observe these warning andsafety notices.

3.1 Intended useThese devices are designed solely for use in industrial areas.

The TBEN-L…-4RFID-8DXP 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 heads and transmitscommands from the controller to the read/write heads. Read data is sent to the controller viathe device.

The device supports the HF read/write heads from firmware version Vx.90 and UHF read/writeheads from firmware version FW 1.45.

In normal operation, up to four BL ident read/write heads can be connected to the device. InBus mode it is possible to connect up to 32 bus-capable HF read/write heads per channel. Eightconfigurable digital channels are also provided. The multiprotocol interfaces can be connectedto 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 notesn 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

regulations, 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

recommends using a secure password.

Product DescriptionDevice overview


4 Product DescriptionThe devices are designed with a fully encapsulated housing with degree of protection IP67/IP69K. Four RFID channels are provided for connecting read/write heads. It is also possible toconnect sensors and actuators via eight digital I/O channels, which can be configured as inputsor outputs as required. The terminals for the read/write heads and for digital I/Os are M12 sock-ets. An M12 socket is provided for the Ethernet connection.

The plug connectors are 4-pin (TBEN-L4) or 5-pin (TBEN-L5) 7/8” female connectors.

4.1 Device overview

218

230.5

C4C5C6C7

6.3

38.8

60.4

C0C1C2C3

2430.2

X2

X1

P2

P1

Fig. 1: Dimensions

4.1.1 Display elementsThe device has the following LED indicators:

n Power supplyn Group and bus errorsn Statusn Diagnostics

4.1.2 Operating elementsThe device is provided with the following operating elements:

n Rotary coding switch for setting the IP addressn Reset button for resetting to the default values

V02.00 | 2020/08 11

4.2 Properties and featuresn Glass fiber reinforced housingn Shock and vibration testedn Fully encapsulated module electronicsn Degree of protection IP65/IP67/IP69Kn Multiprotocol: EtherNet/IP device, Modbus TCP slave or PROFINET devicen PROFINET S2 system redundancyn Up to 128 bytes of user data per read/write cycle per channel as well as use of fragments for

larger data volumesn Data interface for convenient use of the RFID functionsn 4 or 5-pin 7/8” plug connector for the power supplyn Two 4-pin M12 connections for Ethernetn Four channels with M12 connection for RFIDn Mixed operation of HF and UHF read/write headsn Eight configurable digital channels as 2 A PNP inputs or outputsn Integrated Ethernet switch enables line topologyn 10 Mbps/100 Mbps transfer raten Integrated web servern LED indications and diagnostics

4.3 Operating principleThe interfaces are provided with a multiprotocol fieldbus interface for Modbus TCP, EtherNet/IPand PROFINET. The fieldbus interface connects the interface to an (existing) fieldbus system asan EtherNet/IP device, Modbus TCP slave or PROFINET device. The interfaces are provided witha fieldbus interface and fieldbus-independent I/O electronics with an RFID interface. Duringoperation, the process data is exchanged between the fieldbus and RFID system. The read/write heads are connected to the interfaces via the RFID interfaces. The interface signals ofsensors and actuators can also be processed via eight configurable digital channels.

4.4 Functions and operating modesThe 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 andmultitag applications), read, write and password protection. Additional functions are providedfor optimizing the speed, the self triggering of the system, as well as for backup and restoreoperations. In every write or read cycle, up to 128 bytes can be transferred on each channel tothe controller. The data must be fragmented in order to transfer more than 128 bytes.

Sensors and actuators can be connected to the configurable digital channels. Up to eight 3-wire PNP sensors or eight PNP DC actuators with a maximum output current of 2 A per outputcan be connected.

Product DescriptionFunctions and operating modes


4.4.1 Multiprotocol technologyThe devices can be used in the following three Ethernet protocols:

n Modbus TCPn EtherNet/IPn 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 andthe device is fixed to the selected protocol. With the other protocols, the device can only beaccessed read-only.

Protocol Dependent Functions

The device Supported the following Ethernet protocol specific functions:

PROFINET

n FSU - Fast Start-Up (prioritized startup)n Topology discoveryn Address assignment via LLDPn MRP (Media Redundancy Protocol)

EtherNet/IP

n QC – QuickConnectn Device Level Ring (DLR)

V02.00 | 2020/08 13

4.4.2 Data transfer to the PLCIn every write or read cycle, up to 128 bytes can be transferred on each channel. The data mustbe fragmented in order to transfer more than 128 bytes. The amount of data transferred perread or write cycle can be set as follows for different Ethernet protocols:

PROFINET EtherNet/IP Modbus TCP

n 8 bytesn 16 bytes

(default setting)n 32 bytesn 64 bytesn 128 bytes

Standard assemblies (default setting):n 103: adjustable,

max. 128 bytesn 104: adjustable,

max. 128 bytes

User-defined assemblies:n Compact:

16 bytes input data, 16 bytes output data(assemblies 120, 150)

n Mid-size: 56 bytes input data, 56 bytes output data(assemblies 121, 151)

n Extended: 80 bytes input data, 80 bytes output data(assemblies 122, 152)

n 128 bytes (permanently set)

Adjustable fragment size:n 8 bytesn 16 bytesn 32 bytesn 64 bytesn 128 bytes

(default setting)



4.4.3 RFID channels – operating modesFive different data interfaces can be selected for the RFID channels:

n HF compactn HF extendedn HF bus moden UHF compactn 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 possiblewith fragmentation to transfer more than the set data size per write or read cycle (example: 128bytes). The operating mode is suitable for single-tag and multitag applications.

NOTENot 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 executesthe commands autonomously. Different data is stored in the internal memory of the interface.The memory operates as a FIFO memory.

V02.00 | 2020/08 15

HF bus mode

In HF bus mode up to 32 bus-capable read/write heads per RFID channel can be connected tothe TBEN module. An additional power supply may be required depending on the number andpower consumption of connected read/write heads. A power consumption analysis of theconnected read/write heads is required in order to determine the additional power supplyrequired. A tool is provided at www.turck.com/hf-busmodus for calculating the power.

Every connected read/write head supplies a “Tag present” signal in HF bus mode. HF bus modeis suitable for static applications and very slow dynamic applications because a command canonly be processed by one read/write head at a time.

In Continuous HF bus mode, a command is performed simultaneously at all read/write heads ina bus topology. The logged data is stored in the ring memory of the module.

TBEN-L…-4RFID-8DXP-…

VT2-FKM5-FKM5-FSM5

RFID connection cable

(e.g. RK4.5T-0.3-RS4.5T/S2503)

TN-M18-H1147/C53

TN-CK40-H1147/C53

TN-M30-H1147/C53

up to 32 per port

Fig. 2: HF bus mode setup

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

n TN-M18-H1147/C53n TB-M18-H1147/C53n TN-M30-H1147/C53n TB-M30-H1147/C53n TN-CK40-H1147/C53n TNSLR-Q42TWD-H1147/C53n TB-Q08-0.15-RS4.47T/C53n TB-Q08-0.15-RS4.47T/C53n TN-Q14-0.15-RS4.47T/C53n 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.

https://pdb2.turck.de/repo/media/_de/Anlagen/Calculation_file_for_HF_Bus_Mode.xlsx



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 andmultitag applications. The user can set a command timeout to define the time for the executionof a command.

UHF extended mode enables the use of Presence sensing mode for the repeated execution ofan Inventory, Read or Write command. In Presence sensing mode the read/write heads areautomatically switched on or off and also carry out commands automatically. In this case, theread data is stored in the internal memory of the interface. The memory operates as a FIFOmemory.

4.4.4 RFID commandsThe device can perform the following commands and functions. A complete description of thecommands is provided in the section “Setting”.

n Idlen Inventoryn Readn Writen Write and verifyn Continuous moden Get data from buffer (Continuous mode)n Continuous presence sensing mode (UHF)n End Continuous (presence sensing) moden Read/write head identificationn Switch off HF read/write headn HF read/write head tuningn Query HF read/write head addressn Set HF read/write head addressn Direct read/write head commandn Set tag passwordn Set read/write head passwordn Reset read/write head passwordn Set tag protectionn Query HF tag protection statusn Set permanent lock (Lock)n Tag infon Kill UHF tagn Restore settings of the UHF read/write headn Backup settings of the UHF read/write headn Query error/status of UHF read/write headn Reset

V02.00 | 2020/08 17

4.4.5 Loop counter functionThe 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 [} 237]).This increments the loop counter to execute a command repeatedly. At least four PLC cyclesare required in conventional command processing. In order to execute a command repeatedlywith conventional command processing, a command has to be reset and then set again. Theloop counter function is provided for special commands. If the command was successfully ex-ecuted, the command code is output in the response data.

4.4.6 Configurable digital channels – functionsThe device is provided with eight digital channels, which can be configured as inputs or out-puts according to the application requirements. Up to eight 3-wire PNP sensors or eight PNPDC actuators with a maximum output current of 2 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. Thisenables the device to perform small to medium complexity control tasks in order to relieve theprocessing load on the central controller. The FLCs can be programmed in the ARGEE engineer-ing environment.

The ARGEE-FLC programming software can be downloaded free of charge fromwww.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 accessoriesAccessories for mounting, connecting and parameterizing can be found in product database orthe Accessories List for TBEN (D301367) under www.turck.com. The accessories are not part ofthe scope of delivery.

http://www.turck.comhttp://www.turck.com

InstallingMounting the device outdoors


5 Installing

NOTICEMounting on uneven surfacesDevice damage due to stresses in the housing Fix the device on a flat mounting surface. Use two M6 screws for mounting.

The device can be screwed onto a flat mounting plate.

Attach the module to the mounting surface with two M6 screws. The maximumtightening torque for the screws is 1.5 Nm.

Avoid mechanical stresses. Optional: Ground the device.

218 [5.58]

M6 (2x)max. 1.5 Nm

Fig. 3: Mounting the device onto a mounting plate

5.1 Mounting the device outdoorsThe device is UV-resistant according to DIN EN ISO 4892-2. Direct sunlight can cause materialabrasion 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.

V02.00 | 2020/08 19

5.2 Grounding the device

5.2.1 Equivalent wiring diagram and shielding concept

1 nF

2,2 MΩ

1 nF

2,2 MΩ

X1

C0

C1

C2

C3

P1

X2

C4

C5

C6

C7

P2

4 x 15 nF

Fig. 4: Equivalent circuit and shielding concept

5.2.2 Shielding of the fieldbus and I/O levelThe fieldbus and the I/O level of the modules can be grounded separately.

1

2

3

Fig. 5: Grounding clip (1), grounding ring (2) and metal screw (3)

The grounding ring (2) is the module grounding. The shielding of the I/O level is permanentlyconnected to the module grounding. The module grounding is only connected to the refer-ence potential of the installation when the module is mounted.

Shielding concept of the I/O modules (I/O level)

In the case of direct mounting on a mounting plate, the module grounding is connected to thereference potential of the system via the metal screw in the lower mounting hole (3). If modulegrounding is not desired, the electrical connection to the reference potential must be interrup-ted, e.g. by using a plastic screw.

InstallingGrounding the device


Shielding concept of the fieldbus level

On delivery, a grounding clip is provided on the connectors for the fieldbus connection.

When mounted directly on a mounting plate, the shielding of the fieldbus cables is routed dir-ectly to the module ground via the grounding clip and the metal screw in the lower mountinghole.

If direct grounding of the fieldbus shield is not desired, the grounding clip must be removed. Inthis case, the fieldbus shield is connected to the module ground via an RC element.

5.2.3 Grounding the device – I/O level and fieldbus levelThe grounding of the fieldbus level can either be connected directly via the grounding clip (1)or connected and routed indirectly via an RC element to the grounding of the I/O level. If thegrounding is to be routed via an RC element, the grounding clip must be removed.

1

2

3

Fig. 6: Grounding clamp (1)

Removing the grounding clip: disconnect the direct grounding of the fieldbus level

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

Fig. 7: Use a flat slotted screwdriver to push the grounding clip forwards and remove it.

V02.00 | 2020/08 21

Mounting the grounding clip: grounding the fieldbus level directly

Place the grounding clamp between the fieldbus connectors by using a screwdriver insuch way that the clamp contacts the metal housing of the connectors.

The shielding of the fieldbus cables is connected to the grounding clip.

Fig. 8: Mounting the grounding clip

Grounding the device – mounting on a mounting plate

For mounting onto a mounting plate: Fix the Device with an M6 metal screw through thelower mounting hole.

a The shielding of the M12 flanges for the I/O level is connected to the reference potentialof the installation via the M6 metal screw.

a With mounted grounding clip: The shielding of the fieldbus is connected to the referencepotential of the installation via the module grounding of the I/O level.

ConnectionConnecting the modules to Ethernet


6 Connection

NOTEThe connection cables and connectors must have a rated operating temperature ofmin. 75 °C.

6.1 Connecting the modules to EthernetThe device is provided with an integrated autocrossing switch with two 4-pin M12 Ethernetplug connectors for connecting to an Ethernet system. The maximum tightening torque is 0.6 Nm.

Fig. 9: M12 Ethernet plug connectors for connecting the fieldbus

Connect the device to the fieldbus according to the pin assignment below.

v

4

1 3

2

P1

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

flange = FE

v

4

1 3

2

P2

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

flange = FE

Fig. 10: Pin assignment of the Ethernet connec-tions

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

V02.00 | 2020/08 23

6.2 Connecting the power supplyFor the connection to the power supply, the device has two 5-pin 7/8" connectors. The powersupply connectors are designed as 4-pole (TBEN-L4) or 5-pole (TBEN-L5) 7/8" connectors. V1and V2 are galvanically isolated. The maximum tightening torque is 0.8 Nm.

Fig. 11: TBEN-L4... – 7/8” plug connectorfor connecting the power supply

Fig. 12: TBEN-L5... – 7/8” plug connectorfor connecting the power supply

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

w v

1

2

3

4

1 RD = 24 VDC V2

2 GN = 24 VDC V1

3 WH = GND V1

4 BK = GND V2

1

2

3

4

X1 X2

1 BK = GND V2

2 BU = GND V1

3 GNYE = FE

4 BN = 24 VDC V1

5 WH = 24 VDC V2

3

4

5

2

1

w v

3

4

5

2

1

X1 X2

Fig. 13: TBEN-L4-… – pin assignment power supply connectors

Fig. 14: TBEN-L5-… – pin assignment power supply connectors

Connector Function

X1 Power feed

X2 Continuation of the power to the next node

V1 System voltage: power supply 1 (incl. supply of electronics)

V2 Load voltage: power supply 2

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

ConnectionConnecting RFID read/write heads


6.3 Connecting RFID read/write headsThe device has four 5-pin M12 plug connectors for connecting RFID read/write heads. The max-imum tightening torque is 0.8 Nm.

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

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

4

1 3

2

5

v

1 = Vaux1

2 = Data B

3 = GND V1

4 = Data A

5 = FE/Shield

Fig. 16: RS485 – pin assignment of the read/write head connections

4

1 3

2

5

v

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

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

4

1 3

2

5

v

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


4

1 3

2

5

v

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


V02.00 | 2020/08 25

6.3.1 Connecting read/write heads for the HF bus modeIn HF bus mode up to 32 bus-capable read/write heads per RFID channel can be connected tothe device. The user must determine by means of a power consumption analysis whether anadditional power supply is required for the connected read/write heads (see information in thedata 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 box 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 feeding

in an additional power supplyn 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 spurline is 2 m.

Take the power supply into account, particularly at switch-on (see data sheet), as well asthe maximum current carrying capacity of the lines (4 A).

Take the voltage drop on the line into account. If necessary provide an additional powersupply 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.

TBEN-L…-4RFID-8DXP-…

VT2-FKM5-FKM5-FSM5

RFID connection cable

(e.g. RK4.5T-0.3-RS4.5T/S2503)

TN-M18-H1147/C53

TN-CK40-H1147/C53

TN-M30-H1147/C53

up to 32 per port

Fig. 20: HF bus mode setup

ConnectionConnecting digital sensors and actuators


6.4 Connecting digital sensors and actuatorsThe device has four 5-pin M12 plug connectors for connecting digital sensors and actuators.The maximum tightening torque is 0.8 Nm.

Fig. 21: M12 plug connectors for connecting digital sensors and actuators

Connect the sensors and actuators to the device as per the pin assignment below.

4

1 3

2

5

v

1 = Vaux2 2 = Signal In/Out 3 = GND V2 4 = Signal In/Out 5 = FE

C4...C7

5 FE 4 BK

1 BN +

3 BU –

3 BU –

2 WH

vC4…C7

Sensor

or

Actuator

Sensor

or

Actuator

Fig. 22: Connections for digital sensors andactuators – pin assignment

Fig. 23: Connections for digital sensors andactuators – wiring diagram

The channels are assigned to the sockets as follows:

Channel Socket Pin

DXP8 Ch8 C4 4

DXP9 Ch9 C4 2

DXP10 Ch10 C5 4

DXP11 Ch11 C5 2

DXP12 Ch12 C6 4

DXP13 Ch13 C6 2

DXP14 Ch14 C7 4

DXP15 Ch15 C7 2

V02.00 | 2020/08 27

7 CommissioningThe device is operational automatically once the cables are connected and the power supply isswitched on.

Connected HF read/write heads are switched on automatically. Connected UHF read/writeheads are switched off automatically and are activated automatically when a command isexecuted (apart from Idle mode).

In the default configuration the Idle command (0x0000) is active. If an HF read/write head isconnected and a tag is located in the detection range of the read/write head, the Tag presentbit is set and the UID is output in the input data.

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

7.1.1 Setting the IP address via switches at the deviceThe IP address can be set via three decimal rotary coding switches on the device.

The switches are located together with the Reset button under a cover.

Reset x 10 x 1x 100

098

76 5 4

3

2

1 098

76 5 4

3

2

1 098

76 5 4

3

2

1

Fig. 24: Switches for setting the IP address

Open the cover over the switches. Set the required rotary coding switches to the required position according to the table

below. Carry out a voltage reset. NOTICE! IP67 or IP69K protection is not guaranteed when the cover over the rotary

coding switches is opened. Device damage through penetrating foreign objects orliquids is possible. Close the cover over the switches securely.

CommissioningSetting the IP address


Addressing options

The IP address of the devices can be set in different ways. The following addressing options canbe selected via the switches on the device. Setting changes are activated after a voltage reset.

Setting option Rotary coding switch Description

Default address 000 IP address: 192.168.1.254Subnet mask: 255.255.255.0Gateway: 192.168.1.1

Rotary mode 1…254 In Rotary mode, the last byte of the IP address can be set manually onthe gateway. The other network settings can be stored retentively in thegateway memory and cannot be changed in Rotary mode. Addresses1…254 can be set.

BootP mode 300 In BootP mode, the complete IP address is assigned automatically by aBootP server in the network. The subnet mask assigned by the BootPserver and the default gateway address are stored retentively in thegateway memory.

DHCP mode 400 In DHCP mode, the complete IP address is assigned automatically by aDHCP server in the network. The subnet mask assigned by the DHCPserver and the default gateway address are stored retentively in thegateway memory. DHCP supports three types of IP address assignment:n Automatic address assignment: The DHCP server assigns a perman-

ent IP address to the client.n Dynamic address assignment: The IP address assigned by the server

is always only reserved for a specific period. After this time haselapsed or after the explicit release by a client, the IP address is reas-signed.

n Manual address assignment: A network administrator assigns an IPaddress to the client. DHCP is only used in this case to transfer theassigned IP address to the client.

PGM mode 500 In PGM mode, the complete IP address is assigned manually via theTurck Service tool, FDT/DTM or via a web server. In PGM mode, the set IPaddress and the subnet mask are stored in the gateway memory. Allnetwork settings (IP address, subnet mask, default gateway) are accep-ted by the internal EEPROM of the module.

PGM-DHCP mode 600 In PGM-DHCP mode, the gateway transmits DHCP requests until it is as-signed a fixed IP address. The DHCP client is automatically deactivated ifan IP address is assigned to the gateway via the DTM or a web server.

F_Reset 900 F_Reset mode resets all device settings to the default values and clearsall data in the internal flash memory of the device. The following valuesare reset or deleted:n IP address and subnet maskn Parameters

V02.00 | 2020/08 29

7.1.2 Setting the IP address via the Turck Service ToolThe device is factory set to IP address 192.168.1.254 and does not have a PROFINET devicename. The IP address can be set via the Turck Service Tool. The Turck Service Tool is availablefree of charge from www.turck.com.

Connect the device to a PC via the Ethernet interface. Launch the Turck Service Tool. Click Search or press F5.

Fig. 25: Turck Service Tool – start screen

The Turck Service Tool displays the connected devices.

Fig. 26: Turck Service Tool – found devices

http:%5C%5Cwww.turck.com



Click the required device. Click Change or press [F2].

Fig. 27: Turck Service Tool – selecting the device to be addressed

NOTEClicking the IP address of the device opens the web server.

V02.00 | 2020/08 31

Change the IP address and if necessary the network mask and gateway. Accept the changes by clicking Set in device.

Fig. 28: Turck Service Tool – changing the device configuration



7.1.3 Setting the IP address via the web server

NOTEThe device must be in PGM mode in order to set the IP address via the web server.

Open the web server. Log into the device as administrator. Click Network configuration. Change the IP address and if necessary also the subnet mask and default gateway. Write the new IP address, subnet mask and default gateway via Submit to the device.

Fig. 29: Setting the IP address via the web server

V02.00 | 2020/08 33

7.2 Connecting the device to a Modbus master

Prerequisites

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

7.2.1 Connecting the device with the controllerTo connect the device to the controller, the following components must be added in CODESYSfirst of all:

n Ethernet adaptern Modbus TCP mastern Modbus TCP slave

Adding an Ethernet adapter

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

Fig. 30: Project tree

CommissioningConnecting 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

V02.00 | 2020/08 35

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



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

V02.00 | 2020/08 37

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_L5_4RFID_8DXP)



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.26)

V02.00 | 2020/08 39

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.168.1.61)

7.2.5 Defining Modbus channels (registers)

Defining channel 0 (input data)

Double-click the Modbus TCP Slave. Select in the tab Modbus Slave Channel Ò Add channel. Enter the following values:

n Name of channeln Access type: Read holding registersn Offset: 0x0000n Length: 64 registers (128 bytes)

Confirm with OK.

Fig. 38: Defining READ registers



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 channeln Access type: Write multiple registersn Offset: 0x0800n 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 TCPSlave I/O Mapping tab. Enter the address in the corresponding table column.

Fig. 40: Changing channel addresses

V02.00 | 2020/08 41

7.2.6 Connecting the device online with the controller Select device. Click Online Ò Login.

7.2.7 Reading out process dataThe process data can be interpreted via the mapping if the device is connected online with thecontroller.

Double-click the Modbus TCP Slave. Click the Modbus TCPSlave I/O Mapping tab.a The process data is displayed.

Fig. 41: Process data



7.2.8 Modbus TCP – mapping

RFID channels – parameter data

Description Register Bit offset Bit length

Channel 0 Channel 1 Channel 2 Channel 3

Operating mode 0xB000 0xB012 0xB024 0xB036 0 8

Select tag type 0xB000 0xB012 0xB024 0xB036 8 8

Bridging time 0xB001 0xB013 0xB025 0xB037 0 16

HF: Multitag mode 0xB002 0xB014 0xB026 0xB038 4 1

HF: Heartbeat read/write head 0xB002 0xB014 0xB026 0xB038 5 1

RS 485 terminating resistor 0xB002 0xB014 0xB026 0xB038 6 1

Automatic tuning of read/write head 0xB002 0xB014 0xB026 0xB038 7 1

HF read/write head diagnosticsDeactivate tuning

0xB002 0xB014 0xB026 0xB038 8 1

Diagnostic input filter 0xB002 0xB014 0xB026 0xB038 15 1

HF Idle mode 0xB003 0xB015 0xB027 0xB039 0 8

Command repetitions in the event of an error

0xB004 0xB016 0xB028 0xB03A 0 8

HF: Command in Continuous mode 0xB004 0xB016 0xB028 0xB03A 8 8

HF: Length in Continuous mode 0xB005 0xB017 0xB029 0xB03B 0 16

HF: Address in Continuous mode 0xB006 0xB018 0xB02A 0xB03C 0 32

Length of read data 0xB010 0xB022 0xB034 0xB046 0 16

Length of write data 0xB011 0xB023 0xB035 0xB047 0 16

HF bus mode: Activate read/writehead 1

0xB00E 0xB020 0xB032 0xB044 0 1

… … … … … … 1


0xB00E 0xB020 0xB032 0xB044 15 1


0xB00F 0xB021 0xB033 0xB045 0 1

… … … … … … 1


0xB00F 0xB021 0xB033 0xB044 15 1

V02.00 | 2020/08 43

RFID channels – process input data



Response code 0x0000 0x004C 0x0098 0x00E4 0 16

Tag within the detection range 0x0002 0x004E 0x009A 0x00E6 0 1

HF read/write head switched on 0x0002 0x004E 0x009A 0x00E6 8 1

Continuous mode active 0x0002 0x004E 0x009A 0x00E6 9 1

Loop counter 0x0001 0x004D 0x0099 0x00E5 0 8

Read/write head detuned 0x0002 0x004E 0x009A 0x00E6 4 1

Parameter not supported by read/write head

0x0002 0x004E 0x009A 0x00E6 5 1

Read/write head reports error 0x0002 0x004E 0x009A 0x00E6 6 1

Expected read/write head not connected

0x0002 0x004E 0x009A 0x00E6 7 1

Length 0x0003 0x004F 0x009B 0x00E7 0 16

Error code 0x0004 0x0050 0x009C 0x00E8 0 16

Tag counter 0x0005 0x0051 0x009D 0x00E9 0 16

Data (bytes) available 0x0006 0x0052 0x009E 0x00EA 0 16

Read fragment no. 0x0007 0x0053 0x009F 0x00EB 0 8

Write fragment no. 0x0007 0x0053 0x009F 0x00EB 8 8

Read/write head 1 – Tag in detection range

0x000A 0x0056 0x00A2 0x00EE 0 1

… … … … … … 1


0x000A 0x0056 0x00A2 0x00EE 15 1


0x000B 0x0057 0x00A3 0x00EF 0 1

… … … … … … 1


0x000B 0x0057 0x00A3 0x00EF 15 1

Read data Byte 0 0x000C 0x0058 0x00A4 0x00F0 0 8

Read data Byte 1 0x000C 0x0058 0x00A4 0x00F0 8 8

Read data Byte 2 0x000D 0x0059 0x00A5 0x00F1 0 8

Read data Byte 3 0x000D 0x0059 0x00A5 0x00F1 8 8

… … … … … … 8

Read data Byte 14 0x0013 0x005F 0x00AB 0x00F7 0 8

Read data Byte 15 0x0013 0x005F 0x00AB 0x00F7 8 8

… … … … … … 8

Read data Byte 64 0x002C 0x0078 0x00C4 0x0110 0 8

Read data Byte 65 0x002C 0x0078 0x00C4 0x0110 8 8

… … … … … … 8

Read data Byte 126 0x004B 0x0097 0x00E3 0x012F 0 8

Read data Byte 127 0x004B 0x0097 0x00E3 0x012F 8 8



RFID channels – process output data



Command code 0x0800 0x084C 0x0898 0x08E4 0 16

Loop counter 0x0801 0x084D 0x0899 0x08E5 0 8

Memory area (only UHF) 0x0801 0x084D 0x0899 0x08E5 8 8

Start address 0x0802 0x084E 0x089A 0x08E6 0 32

Length 0x0804 0x0850 0x089C 0x08E8 0 16

Length UID/EPC 0x0805 0x0851 0x089D 0x08E9 0 8

Antenna no. 0x080A 0x0856 0x08A2 0x08EE 0 8

Timeout 0x0806 0x0852 0x089E 0x08EA 0 16

Read fragment no. 0x0807 0x0853 0x089F 0x08EB 0 8

Write fragment no. 0x0807 0x0853 0x089F 0x08EB 8 8

Write data Byte 0 0x080C 0x0858 0x08A4 0x08F0 0 8

Write data Byte 1 0x080C 0x0858 0x08A4 0x08F0 8 8

… … … … … … 8

Write data Byte 14 0x0813 0x085F 0x08AB 0x08F7 0 8

Write data Byte 15 0x0813 0x085F 0x08AB 0x08F7 8 8

… … … … … … 8

Write data Byte 64 0x082c 0x0878 0x08C4 0x0910 0 8

Write data Byte 65 0x082c 0x0878 0x08C4 0x0910 8 8

… … … … … … 8

Write data Byte 126 0x084B 0x0897 0x08E3 0x092F 0 8

Write data Byte 127 0x084B 0x0897 0x08E3 0x092F 8 8

V02.00 | 2020/08 45

RFID diagnostic data



Overvoltage at power supply terminal VAUX

0x0130 0x0142 0x0154 0x0166 7 1

Parameter error 0x0130 0x0142 0x0154 0x0166 6 1

Configuration via the DTM active 0x0130 0x0142 0x0154 0x0166 5 1

Memory full 0x0130 0x0142 0x0154 0x0166 4 1

Read/write head 1 not tuned 0x0132 0x0144 0x0156 0x0168 4 1


… … … … … … 1



Parameter not supported by read/write head 1

0x0132 0x0144 0x0156 0x0168 5 1


0x0132 0x0144 0x0156 0x0168 13 1

… … … … … … 1


0x0141 0x0153 0x0165 0x0177 5 1


0x0141 0x0153 0x0165 0x0177 13 1

Read/write head 1 reports error 0x0132 0x0144 0x0156 0x0168 6 1


… … … … … … 1



Expected read/write head 1 not connected

0x0132 0x0144 0x0156 0x0168 7 1

Expected read/write head 2 not connected

0x0132 0x0144 0x0156 0x0168 15 1

… … … … … … 1

Expected read/write head 31 notconnected

0x0141 0x0153 0x0165 0x0177 7 1

Expected read/write head 32 notconnected

0x0141 0x0153 0x0165 0x0177 15 1



Digital channels – input data


Input value channel 8 0x0178 8 1








Digital channels – output data


Output value channel 8 0x0930 8 1








V02.00 | 2020/08 47

Digital channels – diagnostic messages


Overvoltage at power supply terminal VAUX 8/9

0x0179 4 1


0x0179 5 1


0x0179 6 1


0x0179 7 1

Overvoltage at output (channel 8)

0x017A 8 1


0x017A 9 1


0x017A 10 1


0x017A 11 1


0x017A 12 1


0x017A 13 1


0x017A 14 1


0x017A 15 1

Module status – diagnostic messages


Force mode active in the DTM 0x017B 14 1

Undervoltage V1 0x017B 9 1

Undervoltage V2 0x017B 7 1

Module diagnostic available 0x017B 0 1

Internal error 0x017B 10 1

ARGEE program active 0x017B 1 1

CommissioningConnecting a device to an EtherNet/IP controller


7.3 Connecting a device to an EtherNet/IP controller

NOTEIn EtherNet/IP applications max. 496 bytes are available in the controller. Either up totwo channels with a maximum of 128 bytes or all four RFID channels each with amaximum of 80 bytes can be operated. A larger amount of read and write data canbe transferred by fragmentation in HF extended operating mode.

The device can be connected to the controller generically, with an EDS file or an L5K file. Thecomplete input data mapping is 496 bytes. The rest is not transferred if the input data and out-put data are more than this. Up to two channels (assembly 103 and 104) can be used to transfer128 bytes.

Input data:

n Assembly 103: up to 128 bytes (standard; only supported generically)n Assembly 120: 16 bytes (Compact)n Assembly 121: 56 bytes (Mid-size)n Assembly 122: 80 bytes (Extended) (RFID diagnostic data and digital channels can no longer

be used due to the limited data size with EtherNet/IP.)

Output data:

n Assembly 104: up to 128 bytes (standard; only supported generically)n Assembly 150: 16 bytes (Compact)n Assembly 151: 56 bytes (Mid-size)n Assembly 152: 80 bytes (Extended) (RFID diagnostic data and digital channels can no longer

be used due to the limited data size with EtherNet/IP.)

Prerequisites


V02.00 | 2020/08 49

7.3.1 Installing an EDS fileThe 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




The wizard for the installation of EDS files is started.

Click Next to select the EDS file.

Fig. 43: Starting the EDS Wizard

V02.00 | 2020/08 51

Select the Register an EDS file(s) option and confirm with Next.

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



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

V02.00 | 2020/08 53

7.3.2 Connecting the device with the controller Right-click I/O Configuration Ò Ethernet. Click New Module.

Fig. 46: Adding a new module



Select Turck under Module Type Vendor Filters. Select the TBEN-RFID module. Confirm the selection with Create.

Fig. 47: Selecting an EDS file for TBEN-L…-4RFID-8DXP

V02.00 | 2020/08 55

Assign a module name. Enter the IP address of the device.

Fig. 48: Setting the module name and IP address



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

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

V02.00 | 2020/08 57

Select an EDS assembly.

Fig. 50: Selecting an EDS assembly

Selection options:

Name Assembly Size Data per channel Note

Standard In: 103Out: 104

240240

max. 128 bytes adjustable; only supported generic-ally

Compact In: 120Out: 150

15683

16 bytes

Mid-size In: 121Out: 151

236163

56 bytes

Extended In: 122Out 152

209211

80 bytes RFID diagnostic data and DXPs canno longer be used due to the limiteddata size with EtherNet/IP.

NOTEUp to two channels (assembly 103 and 104) can be used to transfer 128 bytes.The data size is configured by the EDS with Compact, Mid-size and Extended.A larger amount of read and write data can be transferred by fragmentation in HFextended operating mode.

The mapping is performed dynamically from the selected setting.



Optional: Set the connection and port configuration.

Fig. 51: Setting the connection

Fig. 52: Setting the port configuration

V02.00 | 2020/08 59

The device appears in the project tree.

Fig. 53: TBEN-L…-4RFID-8DXP in the project tree



7.3.3 Connecting the device online with the controller Select the controller. Click Go online.

Fig. 54: Connecting the device online

V02.00 | 2020/08 61

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

Fig. 55: Click Download

Confirm all the following messages.



7.3.4 Reading out process data Select Controller Tags in the project tree.

Fig. 56: Controller tags in the project tree

Parameter data (tben_4rfid:C), input data (tben_4rfid:I1) and output data (tben_4rfid:O1) canbe accessed.

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

V02.00 | 2020/08 63

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. Theprocess data can be interpreted by means of the mapping. Refer to the web server or theassociated L5K file for the mapping of the used device.

Fig. 58: EDS file: Process input data – example



Fig. 59: L5K file: Process input data – example

V02.00 | 2020/08 65

7.3.5 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 less than 150 ms.

QuickConnect can be activated via the web server of the device or in RSLogix via the configura-tion assembly or class instance attributes.

NOTEThe activation of QuickConnect causes the automatic adaption of all necessary portproperties.

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 areprovided in the chapter [} 22].



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. 60: Configuring the configuration assembly in RSLogix (example: standard)

Name Assembly Size Data per channel Note

Standard In: 103Out: 104

240240

max. 128 bytes adjustable; only supported generic-ally

Compact In: 120Out: 150

15683

16 bytes

Mid-size In: 121Out: 151

236163

56 bytes

Extended In: 122Out 152

209211

80 bytes RFID diagnostic data and DXPs canno longer be used due to the limiteddata size with EtherNet/IP.

The configuration assembly is always 106.

V02.00 | 2020/08 67

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

Activating QuickConnect via the web server

Activate the Activate Quick Connect check box in the web server.

Fig. 61: Activating QuickConnect in the web server

CommissioningConnecting a device to a Siemens controller


7.4 Connecting a device to a Siemens controller

Prerequisites


7.4.1 Installing a GSDML fileThe 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. 62: Include the GSDML file


V02.00 | 2020/08 69

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. 63: Installing a GSDML file



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. 64: Connecting the device with the controller

V02.00 | 2020/08 71

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. 65: 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. 66: Assigning the IP address

V02.00 | 2020/08 73

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. 67: Online mode



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. 68: Setting module parameters

V02.00 | 2020/08 75

8 SettingThe device can be controlled, read and set via parameter data, process input data, processoutput 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 GW parameter

0…1 DiagnosticsGW

1 0 0…31 RFID parameters

0…23 RFID input data

0…23 RFID output data

0…36 RFID channel diagnostics

2 0 32…33 Length ofread data

24…151 Read data

3 0 34…35 Length ofwrite data

24…151 Write data






176…303 Read data


176…303 Write data






328…455 Read data








480…607 Read data



13 DiagCH0

608…643 DiagnosticsRFID channel 0

DiagCH1


DiagCH2


DiagCH3


14 8DXPBasic

144…147 DXP parameters

752…753 DXP input data

608…609 DXP output data

144…147 DXP diagnostics

Setting


Socket Channel Parameter data Process input data Process output data Diagnostic data

Bytes Meaning Bytes Meaning Bytes Meaning

15 8DXPDiag

754…757 DXP errormessages

16 VAUXcontrol

148…155 VAUX settings

610…611 VAUX output data

17 Modulestatus

758…759 Modulestatus

V02.00 | 2020/08 77

8.1 RFID channels – parameter data

Byte no. Bit

7 6 5 4 3 2 1 0

0 Operating mode (Mode)

1 Select tag type (TAGTYPE)

2 Bridging time (BYPASS)

3

4 AT TERM HB ANTI

5 DID DXD

6 HFIDLEMODE

7 Reserved

8 Command repetitions (CRET)

9 HF: Command in Continuous mode (CCM)

10 HF: Length in Continuous mode (LCM)

11

12 HF: Address in Continuous mode (ACM)

13

14

15

16 Reserved

17 …

18

19

20

21

22

23

24

25

26

27 Reserved

28 XCVR8 XCVR7 XCVR6 XCVR5 XCVR4 XCVR3 XCVR2 XCVR1




32 Length of write data (WDS)

33

34 Length of read data (RDS)

35

SettingRFID channels – parameter data


8.1.1 Meaning of the parameter bitsThe 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: Deactivated1: HF compact2: HF extended3: HF Bus Mode4: UHF compact5: UHF extended

Tag type (TAGTYPE) 0: Automatic detection1: NXP I-Code SLI/SL22: Fujitsu MB89R1183: TI Tag-it HFI Plus4: Infineon SRF55V02P5: NXP I-CODE SLI S6: Fujitsu MB89R1197: TI Tag-it HF-I8: Infineon SRF55V10P9: Reserved10: Reserved11: NXP I-CODE SLI L12: Fujitsu MB89R11213: EM4233SLICRead/write heads with firmware from V1.91 also support:14: NXP SLIX215: TI Tag-it HFI Pro16: Turck sensor tag17: Infineon SRF55V02S18: Infineon SRF55V10S19: EM423320: EM423721: EM4237 SLIC22: EM4237 SLIX23: EM4033

Bridging time (BYPASS) Bridging time in ms, adjustable from 4…1020 ms,default setting: 200 ms

Automatic tuning of read/write head (AT)

0: Automatic tuning off0: Automatic tuning on

RS 485 terminating resistor(TERM)

0: RS485 terminating resistor off1: RS485 terminating resistor onIn HF bus mode the RS485 bus terminating resistor is activated by default.

HF: Heartbeat read/write head(HB)

The device confirms its operational readiness via a signal which is sent at regularinte

rfid interface tben-l…-4rfid-8dxp8.108.10.1testing and parameterizing rfid interfaces via the...

Documents