USER MANUAL RFID SYSTEMSET-SETUP WITH...

USER MANUAL RFID SYSTEM

SET-UP WITH EtherNet/IPTM

S1644/01

All brand and product names are trademarks or registered trade marks of the owner concerned.

Edition 02/08

© Hans Turck GmbH, Mülheim an der Ruhr

All rights reserved, including those of the translation.

No part of this manual may be reproduced in any form (printed, photocopy, microfilm or any other process) or processed, duplicated or distributed by means of electronic systems without written permission of Hans Turck GmbH & Co. KG, Mülheim an der Ruhr.

Subject to alterations without notice.

Content

0 About this manual

Introduction ..................................................................................................................... 0-2

Preface............................................................................................................................. 0-3

BLxx gateway firmware ..................................................................................................................0-3Document organization...................................................................................................................0-3Reference documentation ..............................................................................................................0-3Trademarks.....................................................................................................................................0-3

Description of symbols used............................................................................................ 0-4

1 Gateway Communication

Gateway Communication structure.................................................................................. 1-2

Gateway Data Structure................................................................................................... 1-3

Gateway Input Data Map................................................................................................................1-3Gateway Output Data Map.............................................................................................................1-4RFID Interface.................................................................................................................................1-5RFID Object Data Format .............................................................................................................1-14

2 BL67 Gateway Configuration

Example of the gateway configuration............................................................................. 2-2

Step 1 – Define Project Requirements............................................................................................2-2Step 2 – Assemble and Initialize Gateway......................................................................................2-3Step 3 – Set gateway IP address ...................................................................................................2-3Step 4 - Configure controller ..........................................................................................................2-5

3 Configure CIP Generic SupportStep 1 – Configure “READ_TAG” message....................................................................................3-2Step 2 – Configure Receive Data Tag ............................................................................................3-4Step 3 – Configure “WRITE_TAG” message ..................................................................................3-5Step 4 – Configure Transmit Tag....................................................................................................3-7Managing CIP Data.........................................................................................................................3-9Controller Tags .............................................................................................................................3-10Program Tags ...............................................................................................................................3-11

RFID Module Flowchart.................................................................................................. 3-12

Class 1 and 3 read........................................................................................................................3-12Class 1 and 3 write .......................................................................................................................3-13

D101644 0208 - BL ident EtherNet/IPTM i

D101644 0208 - BL ident EtherNet/IPTMii

Warning!Dangerous electrical voltage!

Before commencing the installation

Disconnect the power supply of the device.

Ensure that devices cannot be accidentally restarted.

Verify isolation from the supply.

Earth and short circuit.

Cover or enclose neighbouring units that are live.

Follow the mounting instructions (AWA) of the device concerned.

Only suitably qualified personnel in accordance with EN 50 110-1/-2 (VDE 0 105 Part 100) may work on this device/system.

Before installation and before touching the device ensure that you are free of electrostatic charge.

The functional earth (FE) must be connected to the protective earth (PE) or to the potential equalisation. The system installer is responsible for implementing this connection.

Connecting cables and signal lines should be installed so that inductive or capacitive interference do not impair the automation functions.

Install automation devices and related operating elements in such a way that they are well protected against unintentional operation.

Suitable safety hardware and software measures should be implemented for the I/O interface so that a line or wire breakage on the signal side does not result in undefined states in the automation devices.

Ensure a reliable electrical isolation of the low voltage for the 24 volt supply. Only use power supply units complying with IEC 60 364-4-41 (VDE 0 100 Part 410) or HD 384.4.41 S2.

Deviations of the mains voltage from the rated value must not exceed the tolerance limits given in the specifications, otherwise this may cause malfunction and dangerous operation.

Emergency stop devices complying with IEC/EN 60 204-1 must be effective in all operating modes of the automation devices. Unlatching the emergency-stop devices must not cause restart.

Devices that are designed for mounting in housings or control cabinets must only be operated and controlled after they have been installed with the housing closed. Desktop or portable units must only be operated and controlled in enclosed housings.

Measures should be taken to ensure the proper restart of programs interrupted after a voltage dip or failure. This should not cause dangerous operating states even for a short time. If necessary, emergency-stop devices should be implemented.

Wherever faults in the automation system may cause damage to persons or property, external measures must be implemented to ensure a safe operating state in the event of a fault or malfunction (for example, by means of separate limit switches, mechanical interlocks etc.).

The electrical installation must be carried out in accordance with the relevant regulations (e. g. with regard to cable cross-sections, fuses, PE).

All work relating to transport, installation, commissioning and maintenance must only be carried out by qualified personnel. (IEC 60 364 and HD 384 and national work safety regulations).

All shrouds and doors must be kept closed during operation.

D101644 0208 - BL ident EtherNet/IPTM iii

D101644 0208 - BL ident EtherNet/IPTMiv

0 About this manual

Introduction .........................................................................................................................2

Preface.................................................................................................................................3

BLxx gateway firmware ..................................................................................................................... 3Document organization...................................................................................................................... 3Reference documentation ................................................................................................................. 3Trademarks........................................................................................................................................ 3

Description of symbols used................................................................................................4

D101644 0208 - BL ident EtherNet/IPTM 0-1

About this manual

Introduction

The purpose of the document is to guide you through the configuration procedure of the BL20 and BL67 EtherNet/IPTM gateways with the RFID modules run by Allen Bradley family of ControlLogixTM PLC's. The device and network configuration example is provided for the BL67 gateway. Identical procedure is used for the BL20 gateway. The tools for the device and network configuration and PLC programming are standard Rockwell Software tools: RSLinxTM, RSNetWorxTM for EtherNet/IPTM and RSLogix5000TM.

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

Warning

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

Warning

It is imperative that all respective safety measures and accident protection guidelines be adhered to.

D101644 0208 - BL ident EtherNet/IPTM0-2

Preface

BLxx gateway firmware

RFID support over EtherNet/IPTM is provided by BL20-GW-EN-IP and BL67-GW-EN-IP gateways with major firmware revision 2.xxx and higher. Associated EDS files are available for download at:

http://www.turck-usa.com/Support/Networks/Configuration_Files.htm.

Document organization

The document is organized in the following sections:

Gateway communication description

Gateway data format

Configuration of BL67 gateway

Configuring CIP Generic messages

Controller and program tags

The application example shows utilization of Class 1 connection (I/O data exchange) and CIP Generic (explicit) messages used as follows:

RFID commands and status information is transmitted over Class 1 connection (I/O data exchange)

Tag data is read / written using CIP Generic

Reference documentation

Following publications provide related information and technical description of the system components used by the BL ident system:

BL ident Modular RFID System

BL ident DeviceNet User Guide

BL67 User Manual for EtherNet/IPTM

BL67 IO User Manual

BL20 User Manual for EtherNet/IPTM

BL20 IO User Manual

IO-ASSISTANT- configuration software

Trademarks

BL ident ® is registered trademark of TURCK, Inc. EtherNet/IPTM is registered trademark of Open DeviceNet Vendor Association.

RSLinxTM, RSNetWorxTM and RSLogix5000TM are registered trademarks of Rockwell Automation.


http://www.turck-usa.com/Support/Networks/Configuration_Files.htm

About this manual

Description of symbols used

Warning

This sign can be found next to all notes that indicate a source of hazards. This can refer to danger to personnel or damage to the system (hardware and software).

This sign means for the operator: work with extreme caution.

Attention

This sign can be found next to all notes that indicate a potential hazard.

This can refer to possible danger to personnel or damage to the system (hardware and software) and facility.

Note

This sign can be found next to all general notes that supply important information about one or more operating stages.

These specific notes are intended to make operation easier and avoid unnecessary work due to incorrect operation.


1 Gateway Communication

Gateway Communication structure......................................................................................2

Gateway Data Structure.......................................................................................................3

Gateway Input Data Map................................................................................................................... 3Gateway Output Data Map................................................................................................................ 4RFID Interface.................................................................................................................................... 5– RFID Command Interface .............................................................................................................. 5– RFID Command Codes .................................................................................................................. 8– RFID Status Interface ................................................................................................................... 10– RFID Error Codes ......................................................................................................................... 13RFID Object Data Format ................................................................................................................ 14– Read Data Request ...................................................................................................................... 14– Read Data Response ................................................................................................................... 15– Write Data Request ...................................................................................................................... 15– Write Data Response ................................................................................................................... 16– Example: Write Command ........................................................................................................... 16– Example: Read Command ........................................................................................................... 16


Gateway Communication

Gateway Communication structure

The gateway communication, using I/O data connection and explicit messages is show on the Figure 1:. I/O data connection is used for sending RFID commands and receiving RFID status information. The explicit read (Get_Atrribute_Single) and write (Set_Attribute_Single) messages are used for reading and writing of tag data, utilizing "Message" instruction set (CIP Generic).

Figure 1:I/O data connection and CIP Generic communication

��

��

��

�� !��

��

��"�#��


Gateway Data Structure

The following section provides description of:

Gateway generic IO data map: input and output data

Data format of the RFID command and status interface

Data format of the RFID object and explicit messages

Gateway Input Data Map

The gateway input data map (produced data) consists of the following fields:

The data size of the gateway input data map is fixed 128 words. Some of fields may be omitted or not configured. If node, for example, has only RFID module(s) in the architecture, then “IO Input Data” field is omitted. The gateway calculates actual size of IO fields during its initialization.

Table 1:Gateway Input Data Map

Data Length

Field Name Usage Default setup

Description

1 word GW Status Register

Optional Enabled Register provides general status of the gateway. This field is omitted when GW Status Register is disabled.

Variable IO module Input Data

Deter-mined during initi-alization

Not appli-cable

Input data map of non-RFID module(s): 0 words, when no other IO module is present.N words, use IO-ASSISTANT tool to generate IO data map.

Variable RFID Status Interface


Not appli-cable

3 words, when RFID module is present0 words, when RFID module is not present

Variable Summarized Diagnostics

Optional Disabled Contains diagnostic information for all modules:ARRAY OF STRUCT: USINT SLOT #:Indicates the slot number (module position) with diag-nostic messages.BYTE SLOT FLAGS:Offers slot-related information.Bit 7 = module missingBit 6 = false module pluggedDWORD DIAG:Contains the module diagnostic information. Module diagnostic bits that are not used are indi-cated by a "0".



Gateway Output Data Map

The gateway output data map (consumed data) consists of the following fields:

The data size of the gateway output data map is fixed 128 words. Some of fields may be omitted or not configured. If node, for example, has only RFID module(s) in the architecture, then “IO Input Data” field is omitted. The gateway calculates actual size of IO fields during its initialization.

Table 2:Gateway Output Data Map

Data Length

Field Name Usage Default setup

Description

1 word GW Control Register

Optional Enabled This field is omitted when GW Control Register is disabled.

Variable IO module Output Data


Not appli-cable

Output data map of non-RFID module(s): 0 words, when no other IO module is present.N words, Use IO-ASSISTANT tool to generate IO data map.

Variable RFID Command Interface


Not appli-cable

3 words, when RFID module is present0 words, when RFID module is not present



RFID Interface

RFID Command Interface

The commands to different channels are sent successively, each one identified by the channel number. Successive commands to the same channels should be interleaved with the IDLE command in between. For example the sequence to read from address 5, followed by read from address 10, followed by write to address 7 should look like the following:

Read, Idle, Read, Idle, Write, Idle ….

The data format of the RFID command interface is:

Table 3:Command interface

Structureof

Bit Name Description

Word 0 Command code Identifies the required action.Command is executed when ‘Command Code’ changes from 0 to any other value. Command related data must be constant and consistent until status interface bit [Execution channel x] or status interface bit [Error channel x] is set.Exception:In order to cancel a pending command, the RESET CHANNEL command must be assi-gned until status interface bit [Execution channel x] resets and status inter-face bit [Error channel x] resets. Afterwards a new command can be issued immediately.In order to set a new command (aborting current) assign the new command instead of RESET CHANNEL.Command parameters of Command Interface always may be edited safely, if Status Inter-face::CmdCodeIndicatorFlag flag is 0 and Command Interface::Command Code is 0.

1 Command code

2 Command code

3 Command code

4 Command version Distinguishes current command structure from possible future command structures.(must be set to 0)5 Command version

6 Command version

7 Command version

8 Channel number Indicates the channel to which the command is assigned. Allows for up to 15 channels (1..15), even though the BLxx RFID module shall support only up to 8 channels. Coding: { 1..8 }

9 Channel number

10 Channel number

11 Channel number

12 to15

reserved



Word 0 Address (LSB) Addresses a byte within the tag memory to which the command shall be executed, e.g. write data to byte 428 (and following) of the tag.Allows addressing for tag memory of up to 64 Kbytes, even though currently the BLxx RFID module shall be compatible with tag memories of only up to 2 Kbytes.Coding: { 0..65535 }

1 Address

2 Address

3 Address

4 Address

5 Address

6 Address

7 Address

8 Address (MSB)

9 Address

10 Address

11 Address

12 Address

13 Address

14 Address

15 Address

Table 3: (Cont.)Command interface

Structureof




(*)Meaning of these bytes depends on defined command.

Word 0 Data length (LSB) Indicates the length in bytes of the data to which the command refers, e.g. write 128 bytes to the tag.Allows data length of up to 64 Kbytes, even though the amount of data is currently limited by the maximal tag memory of 2 Kbytes.Coding: { 0..65535 }

1 Data length

2 Data length

3 Data length

4 Data length

5 Data length

6 Data length

7 Data length

8 Data length (MSB)

9 Data length

10 Data length

11 Data length

12 Data length

13 Data length

14 Data length

15 Data length

Array of USINT

0-512

according command:- Tag Write Data or- Tag Fill Data(1. byte)

0, 2, 4,..64 bytes of Tag Write Data. (Default: 0 byte)If Tag Fill Command is set, the first byte is used only. Gives the value for the fill command. Allows for fill values in the range of 0-255.Using this polled interface, a single write command is limited to this data size. (max. 64 bytes)= 0, when CIP Generic Write is used.

Table 3: (Cont.)Command interface

Structureof




RFID Command Codes

Table 4:Command Codes

Code Function Required Command Interface WORD size

BYTE[..] Data Interpretation

Description

0 <idle state> 1 Idle

1 READ TAG DATA

3 CmdCode, Version,AddrL, AddrH, LengthL, LengthH

Read LengthL/H bytes of data from tag starting from AddrL/H

2 WRITE TAG DATA

3 +n CmdCode, Version,AddrL, AddrH, [ LengthL, LengthH ]Data[..]

Write LengthL/H bytes of data to tag starting from AddrL/H. Word LengthL/H is not mapped using CIP, resp. Expl. Msgs. Using CIP, the LengthL/H is dermined by the total length of the message.

3 ABORT COMMAND

1 CmdCode, Version

Cancel pending command for the indicated channel.

4 RESET CHANNEL

1 CmdCode, Version

Reset tag channel.

5 FILL TAG 4 CmdCode, Version,AddrL, AddrH, LengthL, LengthHFillDataByte

Fill LengthL/H bytes of tag data area starting from AddrL/H with FillDataByte

6 EXTENDED SERVICE PRIMITIVE

2 +n CmdCode, Version,{SERVICE PRIMITIVE DATA}

Issues native RFID module/transceiver commands. Detailed knowledge of supported RFID command set and data mapping is required.

7 CLEAR ERRORS

1 CmdCode, Version

Clears error messages.

8 - 15

Reserved Reserved for future use



Command codes examples:

*All commands except “COS CHx” refer to RFID module. “COS CHx” is not used with CIP Generic messaging.

Table 5:Command codes Examples

CHANNEL IDLE READ TAG

COS CHx*

WRITE TAG

ABORT CMD

RESET CHANNEL

FILL TAG

CLEAR ERRORS

1 0x100 0x101 0x1100 0x102 0x103 0x104 0x105 0x107

2 0x200 0x201 0x2200 0x202 0x203 0x204 0x205

3 0x300 0x301 0x3300 0x302 0x303 0x304

4 0x400 0x401 0x4400 0x402 0x403

5 0x500 0x501 0x5500 0x502

6 0x600 0x601 0x6600

7 0x700 0x701

8 0x800



RFID Status Interface

The RFID status interface data format is:

Table 6:Status Interface

Byte Bit Name Description

0 0 Data avail. channel number

Indicates the RFID channel, which holds data to be read. The channel numbers are indicated in sequence as data appears. That is, the oldest data is indicated. Updated, if READ COMMAND is executed or COS was charged or channel was reset. Coding { 1..8 }

1 Data avail. channel number



4 Status version Distinguishes current status structure from possible future status structures.Coding { 0 }5 Status version

6 Status version

7 CmdCodeIndica-torFlag

Handshake flag:0=Command Interface::Command Code == 01=Command Interface::Command Code <> 0This flag may be used to control fast command sequences. Flag follows given command code value. If 0, a subsequent written command code will be accepted and indicated by a raising CmdCodeIndi-catorFlag flag.Command parameters of Command Interface always may be edited safely, if CmdCodeIndicatorFlag flag is 0 and Command Interface::Command Code is 0.

1 0 Tag present channel 1

Indicates the presence of a tag in the transmission zone.A bit per channel.

1 Tag present channel 2









2 0 Execution channel 1

Indicates the command status. Is high if command is currently executed or if a command is in the buffer. Is low if the last command was completed and no new command is stored in the buffer.A bit per channel.

1 Execution channel 2







3 0 Error channel 1 Indicates if there has occurred an error.A bit per channel.

1 Error channel 2

2 Error channel 3

3 Error channel 4

4 Error channel 5

5 Error channel 6

6 Error channel 7

7 Error channel 8

Table 6: (Cont.)Status Interface




4 0 Error channel number

Indicates the number of the channel to which the following error code related.Coding: { 1..8 }

1 Error channel number



4 Reserved Reserved for future use.

5 Reserved

6 Reserved

7 Reserved

5 0 Error code Provides more detailed information regarding an error that has occurred.

1 Error code

2 Error code

3 Error code

4 Error code

5 Error code

6 Error code

7 Error code

Table 6: (Cont.)Status Interface




RFID Error Codes

Table 7:Error Codes

Error code

Name Description

0 OK No error occurred, idle.

1 PROCESSING CMD A command was issued, accepted and processing is not finished yet. This is not an error, but a busy indication.

2 COMMAND VERSION NOT SUPPORTED

A command version > 0 was defined. Currently version 0 is supported only.

3 CHANNEL ALREADY BUSY

Aborting a command was not finished while a new one is issued.

4 CHANNEL NOT PRESENT

Channel (“module”) is not present. Two channels per module are supported. Four RFID modules max.

5 CHANNEL NOT INITIA-LIZED

Gateway could not initialize the RFID module state machine. The channel cannot be used. The chan-nels are initialized automatically. If explicit command RESET CHANNEL fails bringing up this error, it might be caused by hardware problems.

6 CHANNEL ACCESS TIMEOUT

RFID channel state machine does not respond. Might be caused by hardware problems.

7 UNKNOWN COMMAND Command issued is not supported

8 COMMAND EXEC ERROR

Error occurred while processing a command. (E. g., a TAG, brought into reception area, vanished before command could be finished)

9 INSUFFICIENT DATA The amount of data given is not sufficient to process the command.

10-15 <reserved>



RFID Object Data Format

CIP Generic utilizes “Get_Attribute_Single” (GET) and “Set_Attribute_Single” (SET) services to READ and WRITE data from an object. In essence, this section defines explicit communication between the controller and the gateway. The gateway supports two objects per each channel where tag data is read or written. Each object is defined by its “Class”, “Instance” and “Attribute” designators. These designators are used in conjunction with:

GET service which is used to read the tag data from the gateway

SET service which is used to write the tag data to the gateway

Each service is determined by its request and response messages.

Read Data Request

The controller must instantiate an explicit connection to read data from the gateway. The following table provides “Class”, “Instance” and “Attribute” designators of the gateway that are used in the “Read or Get_Attribute_Single” request:

The format of the Get_Attribute_Single message is part of the “MSG” instruction which is described in corresponding controller documentation.

Table 8:Read Data Reques

Service / Data Code (decimal) Code (hexadecimal)

Description

GET request 14 0x0E Get_Attribute_Single request

Class 120 0x0078 RFID Object

Instance 1…8 1…8 Channel {1...8}

Attribute 113 0x0071 Read TAG Data Attribute



Read Data Response

The gateway responds to “Get_Attribute_Single” request with a response message that contains two fields:

Tag header, which is inserted by the gateway and contains the information of the tag origin and data length

Tag data that represents actual data read from the tag

* Segment data length is native RFID module data length and cannot be modified.

Write Data Request

The controller must instantiate an explicit connection to write data to the gateway. The following table provides “Class”, “Instance” and “Attribute” designators of the gateway that are used in the “Write or Set_Attribute_Single” request:

Table 9:Tag header and Tag data

Byteaddress

WORD address

Data Remark

TA

G H

ead

er

0 0 command Bit 7-0: command codeBit 15-8: error code

1 error code

2 1 LSB byte start address

TAG byte data offset address.

3 MSB byte start address

4 2 LSB remaining byte length (L)

L = 0: no further data segmentsL > 0: there is more data available(L bytes left) which will be issued with concluding read accesses*

5 LSB remaining byte length (L)

TA

G D

ata

6 3 TAG data

7

... … TAG data

N n TAG data may be partially filled

Table 10:Write data request

Service designatorsand data

Code (decimal)

Code (hexadecimal)

Description

SET request 16 0x10 Set_Attribute_Single request

Class 120 0x0078 RFID Object

Instance 1…8 1..8 RFID Channel {1..8}

Attribute 114 0x0072 Write TAG Data Attribute

Data [i] Data array [I = 0, 1, …, n]



The format of the data of the write request data consists of two fields:

Tag header field, which is used by the gateway to perform “write” function

Tag data field, which contains actual data that is written to the tag

* Segment data length is native RFID module data length and cannot be modified.

To avoid any confusion:

N – is the number of bytes or data size of “Set_Attribute_Single” message instruction

“N-6” is effective data length of tag data

Write Data Response

The response message contains a flag that indicates status of the message instruction execution and error code in case of an error. Refer to MSG instruction help for explanation of error codes.

Table 11:Tag data and tag header

DATA Byteaddress

WORD address

Data Remark

TA

G H

ead

er

0 0 Command Bit7-0: command code, ref. „RFID Command Codes” page 1-8

1 Command version Bit15-8: Not used

2 1 LSB Byte start address

TAG byte data offset address

3 MSB Byte start address

TA

G D

ata

4 2 LSB byte length (N)

N = 0: no further data segmentsN > 0: there is more data available(N bytes left) which will be issued with concluding read accesses (*)

5 MSB byte length (N)

6 3 TAG data[0]

7

... … TAG data[1]...

...

N n+3 TAG data[n] May be partially filled


2 BL67 Gateway Configuration

Example of the gateway configuration.................................................................................2

Step 1 – Define Project Requirements............................................................................................... 2Step 2 – Assemble and Initialize Gateway......................................................................................... 3Step 3 – Set gateway IP address ...................................................................................................... 3Step 4 - Configure controller ............................................................................................................. 4


BL67 Gateway Configuration

Example of the gateway configuration

Following section provides an example of the gateway configuration based on assumption that there are two BLxx-2RFID-A BL ident modules in the node architecture and the tag data size is 64 bytes.

The gateway configuration is described in the following steps:

Define project requirements

Assemble and initialize the gateway

Set the gateway IP address

Configure controller and add gateway to the EtherNet/IPTM network

Step 1 – Define Project Requirements

Controller: ControlLogixTM

Configuration tool: RSNetWorxTM for EtherNet/IPTM

Programming tool: RSLogix5000TM

Program sample: Read tags using channels 1, 2 and 3 and write tag using channel 4.

Tag data size: 64 ASCII characters

BL67 node assembly: BL67-GW-EN-IP set to IP address: 192.168.1.10

Figure 2:Configuration



Step 2 – Assemble and Initialize Gateway

Assemble and power-up the gateway

Press and hold “SET” switch (D) for 10 seconds to initialize the gateway

A power supplyB EthernetC n.c.D SET-buttonE service-interfaceF rotary coding switchesG module bus LEDH designationI status LEDJ LEDs for supply voltage monitoringK n.c.L Ethernet LEDs

Step 3 – Set gateway IP address

The gateway factory default IP address is set to 192.168.1.254 when the address rotary switches are set to position 0,0,0. The gateway IP address may be recovered at any time by using the default IP address settings.

The “BL67 User Manual for EtherNet/IPTM” provides detailed description on how to set the IP address in 4 different ways. To change IP address of the gateway:

Use rotary switches to set the host address between 1 and 254, when default subnet address does not change (192.168.1.x)

Figure 3:Assemble and initialize

A

B

C

D

EF G

H

I

JKL

x 10

x 1

12

3456

7

89 0

12

3456

7

89 0

12

3456

7

89 0

000: 192.168.1.2541 - 254: static rotary300: BootP400: DHCP500: PGM600: PGM-DHCP

x 100



Use “BOOTP-DHCP Server” to set the subnet address that differs from the default. This tool comes in the Rockwell Software package or it can be downloaded from the Rockwell Automation web site. Set rotary switches to 300 (BOOTP) and power-up. Start BOOTP application and follow help instructions of the tool.

If subnet address is set to the C address range, dial rotary switches to match host address and cycle power to the gateway. The address may be changed in range 1..254.

If subnet address is set to A or B address range, dial rotary switches to PGM mode (500) and then cycle power to the gateway. The rotary switches must stay in PGM mode at all times.

IP address recovery mode: Set the rotary switches to 0,0,0 position and power-up device. The device responds with IP address 192.168.1.254.



Step 4 - Configure controller

Create RSLogix5000 new project and configure the controller “C1”

Configure the ControlLogix IO module(s) “1756-ENBT/A” named as “E1”.

Add BLxx_GW-EN-IP to the network. Select “New Module” under the “Ethernet” path

Expand “Communication” tree, select “Generic Ethernet Module” and hit “OK”

Figure 4:I/O Configuration

Figure 5:Add BLxx-GW-EN-IP

Figure 6:Select Module



Enter BLxx-GW-EN-IP address, select “Comm Format”, set IO data size and “RPI”

The gateway IO data is mapped to the controller tags with the following tag association

Figure 7:New module - parameters

Figure 8:Module properties

Figure 9:Tag association input data



Figure 10:Tag association output data




3 Configure CIP Generic Support

Step 1 – Configure “READ_TAG” message....................................................................................... 2Step 2 – Configure Receive Data Tag ............................................................................................... 4Step 3 – Configure “WRITE_TAG” message ..................................................................................... 5Step 4 – Configure Transmit Tag....................................................................................................... 7Managing CIP Data............................................................................................................................ 9Controller Tags ................................................................................................................................ 10Program Tags .................................................................................................................................. 11

RFID Module Flowchart......................................................................................................12

Class 1 and 3 read........................................................................................................................... 12Class 1 and 3 write .......................................................................................................................... 13


Configure CIP Generic Support

Two CIP Generic messages are used for explicit reading and writing of tag data. Each message instruction requires two controller’s tags:

One that performs the function of a message execution control

The second one that represent receive buffer (read data) or transmit buffer (write data) in the controller’s memory.

The RFID tag is hereafter referred to as the “data carrier” to make distinction from the controller tag.

The gateway configuration is described in the following steps:

1 Define “Read_Tag” tag used for “Get_Attribute_Single” message execution control

2 Define “Receive_Data” tag to store data from the gateway

3 Define “Write_Tag” tag used for “Set_Attribute_Single” message execution control

4 Define “Transmit_Data” tag that contains data to be written to the gateway

Step 1 – Configure “READ_TAG” message

Create a new controller tag associated with Get_Attribute_Single message instruction.

Enter a tag name “Read_Tag”, select data type “Message” and check “Open Configuration” checkbox.

Figure 11:Create a new controller tag

Figure 12:Name and data type


Enter in the “Communication” page the path of “Read_Tag” as “BL67_RFID”. Use “Browse” feature to create path to the target object

Enter in the “Configuration” page:

– Service type: “Get_Attrribute_Single”

– Channel 1 designator “Class, Instance, Attribute” in hexadecimal numbers

– Receive data buffer tag name in the “Destination” field: “Receive_Data”

Figure 13:Message configuration



Step 2 – Configure Receive Data Tag

Enter a new controller tag name “Receive Data” in the “Destination” field and define its format. It will store data from the gateway (receive buffer). Refer to “Read Data Response” section for data format:

Figure 14:New controller tag name

Figure 15:Select data type


Step 3 – Configure “WRITE_TAG” message

Create a new controller tag associated with Set_Attribute_Single message instruction

Enter the tag name, select data type “Message” and check “Open MESSAGE Configuration” box

Figure 16:Create a new controller tag

Figure 17:Tag properties



Configure message to write to channel 4:

Open communication page and define path to the BLxx gateway. Use “Browse” feature to set path.

Do not check “Connected” checkbox.

Figure 18:Message configuration

Figure 19:Message configuration - communication


Step 4 – Configure Transmit Tag

Enter name, select the data format in the “Data Type” field as SINT and press button

Figure 20:Name and type of the Transmit_Data tag



Enter the data length 100 into “Dim 0” field and hit OK. The actual requirement will be 69 bytes:

– 5 bytes, the RFID data carrier header + 64 bytes, the RFID data carrier data

Check “Write Data Request” section of the document for exact data format.

Enter source element name and data size in the Configuration page, and save all data.

Figure 21:Data type and dimensions

Figure 22:Configuration


Managing CIP Data

The message instructions “Read_Tag” and “Write_Tag” read/write channel 1 data by default. Use program control to modify the content of the message instructions as follows:

To read/write data from other channels, modify the content of :

– “Read_Tag.Instance” in range {1..8}

– “Write_Tag.Instance” in range {1..8}

To read/write data from other BLxx nodes, modify the node address in string content of “Read_Tag.Path” and “Write Tag Path” or define new MSG instruction. Use the controller documentation to calculate maximum number of used TCP connections that the controller can handle at the same time.

Figure 23:Controller tags



Controller Tags

BLxx-GW-EN-IP input data: size 128 words

BLxx-GW-EN-IP output data: size 128 words

Read Tag response data format:

Figure 24:Input data

Figure 25:Output data

Figure 26:Receive_data


Write Tag data format:

Program Tags

RFID status interface: size 6 bytes

RFID command interface: size 6 bytes

Storage space used for keeping data carrier data of each channel is 64 bytes long:

Following program example, based on RSLogix5000TM V16.00 environment, is associated with this document:

It is a demo program only and does not provide any inclusive or exclusive guarantee for functionality of a control system.

Figure 27:Transmit_Data

Figure 28:RFID_Status

Figure 29:RFID_Command

Figure 30:RFID_TAG_CH

Figure 31:Programm example



RFID Module Flowchart

The flowchart shows the sequence of events related to data communication between a scanner and the gateway. It consists of poll requests (RFID commands sent from scanner to BLxx-GW) and poll responses (RFID status sent from the gateway to the scanner). The flowchart is using notification that has following meaning:

CMD - RFID command interface data contained in the Poll request sent by a scanner

STAT - RFID status interface data contained in the Poll response sent by the gateway

CIP RD/WR – explicit message execution

It is assumed that data carrier is not present when the “READ” command is sent to the gateway. Every command is acknowledged by rising command status flag for a single response message that immediately follows command.

Class 1 and 3 read

Figure 32:Flowchart read

��

��

��

��

� ��

� ��

��

��

��

��

��

��

��

��

��

��


RFID Module Flowchart

Class 1 and 3 write

Figure 33:Flowchart write

��

��

��

��

��

��

��

��

��

��

��




D10

1644

020

8*D

1016

40ßß

0407

*

Hans Turck GmbH & Co. KG45472 Mülheim an der Ruhr GermanyWitzlebenstraße 7Tel. +49 (0) 208 4952-0Fax +49 (0) 208 4952-264E-Mail [email protected] www.turck.com

www.turck.com

Date post:	19-Apr-2020
Category:	Documents
Upload:	others
View:	14 times
Download:	0 times

USER MANUAL RFID SYSTEMSET-SETUP WITH...

Documents