RFID Systems

Bulletin Number 56RF

User Manual Original Instructions

RFID Systems User Manual

Important User Information

Read this document and the documents listed in the additional resources section about installation, configuration, and
operation of this equipment before you install, configure, operate, or maintain this product. Users are required to familiarize
themselves with installation and wiring instructions in addition to requirements of all applicable codes, laws, and standards.

Activities including installation, adjustments, putting into service, use, assembly, disassembly, and maintenance are required to
be carried out by suitably trained personnel in accordance with applicable code of practice.

If this equipment is used in a manner not specified by the manufacturer, the protection provided by the equipment may be
impaired.

In no event will Rockwell Automation, Inc. be responsible or liable for indirect or consequential damages resulting from the use
or application of this equipment.

The examples and diagrams in this manual are included solely for illustrative purposes. Because of the many variables and
requirements associated with any particular installation, Rockwell Automation, Inc. cannot assume responsibility or liability for
actual use based on the examples and diagrams.

No patent liability is assumed by Rockwell Automation, Inc. with respect to use of information, circuits, equipment, or software
described in this manual.

Reproduction of the contents of this manual, in whole or in part, without written permission of Rockwell Automation, Inc., is
prohibited.

Throughout this manual, when necessary, we use notes to make you aware of safety considerations.

WARNING: Identifies information about practices or circumstances that can cause an explosion in a hazardous environment,
which may lead to personal injury or death, property damage, or economic loss.

ATTENTION: Identifies information about practices or circumstances that can lead to personal injury or death, property
damage, or economic loss. Attentions help you identify a hazard, avoid a hazard, and recognize the consequence.

IMPORTANT Identifies information that is critical for successful application and understanding of the product.

These labels may also be on or inside the equipment to provide specific precautions.

SHOCK HAZARD: Labels may be on or inside the equipment, for example, a drive or motor, to alert people that dangerous
voltage may be present.

BURN HAZARD: Labels may be on or inside the equipment, for example, a drive or motor, to alert people that surfaces may
reach dangerous temperatures.

ARC FLASH HAZARD: Labels may be on or inside the equipment, for example, a motor control center, to alert people to
potential Arc Flash. Arc Flash will cause severe injury or death. Wear proper Personal Protective Equipment (PPE). Follow ALL
Regulatory requirements for safe work practices and for Personal Protective Equipment (PPE).

The following icon may appear in the text of this document.

Identifies information that is useful and can help to make a process easier to do or easier to understand.

2 Rockwell Automation Publication 56RF-UM001E-EN-P - October 2022

 Table of Contents
Who Should Use this Manual . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9
Purpose of this Manual. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9
Summary of Changes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9
Abbreviations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9
Additional Resources . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10

Chapter 1
Introduction RFID Defined . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11
International Standard Compliance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11
FCC Caution . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12
Taiwan NCC Warning Statement . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12
Backward Compatibility. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13
System Setup . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13

Chapter 2
RFID Components Interface Block . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15
Status Indicators . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16
Transceivers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17
Status Indicators. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17
Transceiver Power-up Sequence . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18
RFID Tags. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18
Tag Memory Structure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18
SLI . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20
Smart Label IC – Secure (SLI-S). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21
Smart Label IC – Lean (SLI-L). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22
Ferroelectric Random Access Memory (FRAM). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23
Product Selection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24
Main Components . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24
Accessories . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25

Chapter 3
Electrical Installation Cable Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27
Auxiliary Power Connection. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27
Power Connection Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28
Example 1: Daisy Chain the Power Connections . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28
Example 2: System Needs More Than 4 A. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28
Transceiver Connection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29
Digital Input Connection. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29
Digital Output Connection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29
EtherNet/IP Connection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30

Rockwell Automation Publication 56RF-UM001E-EN-P - October 2022 3

Table of Contents

Chapter 4
EtherNet/IP Addressing Star Topology . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31
Linear Topology . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31
Device Level Ring (DLR) Topology . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32
Setting the Network Address. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33
Fundamental IP Addresses: 192.168.1.xxx. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33
Advanced IP Addresses . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34
Change IP Address from One Advanced Address to Another Advanced Address . . . . . 37
IP Address 888 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39

Chapter 5
Mechanical Installation Fastening . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41
Spacing Between Transceivers. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41
Spacing Next to Metal Surfaces . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 42
Transceiver Field Maps . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 42
Approximate Dimensions. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 44

Chapter 6
Add Your RFID Interface Block to Procedure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45
an RSLogix 5000 Program General Tab . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47
MAC Address . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47
Module Definition . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 48
Connection Tab. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 48
Module Info Tab. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49
Internet Protocol Tab . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 50
Port Configuration Tab. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 50

Chapter 7
RSLogix 5000 Controller Tags Configuration Image Table and Tags . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 54
Input Image Table and Tags . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 55
Input Channel Tags. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 56
Output Image Table and Tags . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 57
Output Channel Tags . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 58

Chapter 8
Commands Summary RFID Commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 61

Chapter 9
Add-On Instruction Introduction. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 63
Supported Modules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 63
High-frequency Transceivers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 63
High-frequency Tags . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 64
AOI Specification. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 64
AOI Input Tags . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 64
AOI Output Tags. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 66
AOI Interface Tags. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 67
Support Command . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 68

4 Rockwell Automation Publication 56RF-UM001E-EN-P - October 2022

 Table of Contents

Error Codes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 68
Environment Setup . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 69
5069-SERIAL Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 69
AOI Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 70
Important Notes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 71
ADDR Setting Restriction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 71
Initial State of R/W Status Indicator. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 72
AOI Sample Code Precondition . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 72

Chapter 10
RSLogix 5000 Code Examples Main Routine . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 73
Example Command Routines - Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 73
Rung 0 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 74
Rung 1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 74
Rung 2. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 74
Rung 3. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 74
Rung 4. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 75
Clear Multiple Bytes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 75
Example Routine . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 75
Example Results . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 76
Get Multiple Block Security Status . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 77
Example Routine . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 77
Example Results . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 78
Get System Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 79
Example Routine . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 79
Example Results . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 80
Get Version Information. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 81
Example Routine . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 81
Example Results . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 82
Inventory . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 82
Example Routine . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 83
Example Results . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 83
Lock AFI . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 85
Example Routine . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 85
Example Results . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 86
Lock Block . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 86
Example Routine . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 86
Example Results . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 87
Lock DSFID. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 88
Example Routine . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 88
Example Results . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 89
Read Byte Command . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 89
Example Routine . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 89
Example Results . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 90
Multi-tag Block Read. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 91
Example Routine . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 91
Example Results . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 92

Rockwell Automation Publication 56RF-UM001E-EN-P - October 2022 5

Table of Contents

Read Multiple Blocks. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 93

Example Routine . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 93
Example Results . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 94
Read Single Block . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 95
Example Routine . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 95
Example Results . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 96
Read Transceiver Settings. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 97
Example Routine . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 97
Example Results . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 98
Write AFI. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 98
Example Routine . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 98
Example Results . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 99
Write Byte Command . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 99
Example Routine . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 100
Example Results . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 100
Write DSFID . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 101
Example Routine . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 101
Example Results . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 102
Write Multiple Blocks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 102
Example Routine . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 103
Example Results . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 103
Multi-tag Block Write . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 105
Example Routine . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 105
Example Results . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 106
Write Single Block. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 107
Example Routine . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 108
Example Results . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 108
Continuous Read Mode. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 109
Stop Continuous Read . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 109
Teach Continuous Read . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 109

Chapter 11
SLC Code Examples Read Byte Routine. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 111
Example Routine . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 111
Example Routine . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 112

Chapter 12
MicroLogix 1400 Code Examples Read Byte. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 115
Example Routine . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 116
Write Byte . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 117
Example Routine . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 117
Read Multiple Blocks. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 117
Example Routine . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 118
Write Multiple Blocks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 118
Example Routine . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 118
Input Image Layout. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 118
Output Image Layout . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 118

6 Rockwell Automation Publication 56RF-UM001E-EN-P - October 2022

 Table of Contents

Chapter 13
RFID Tag Speed Continuous Read Mode. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 120
Command Objective . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 120
Operation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 120
Modes of Operation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 121
Mode Overview. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 121
Command Structure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 121
Teach Continuous Read . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 122
Command Objective . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 122
Operation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 122
Command Structure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 123

Chapter 14
RFID Interface Block Webpage Home . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 125
Diagnostics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 125
Network Settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 126
Ethernet Statistics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 126
I/O Connections . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 126
Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 127
Device Identity . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 127
Network Configuration. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 127
Device Services. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 128

Appendix A
Error Codes for RFID Interface Error Codes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 129
Block
Appendix B
CIP Information Product Codes and Name Strings. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 131
CIP Explicit Connection Behavior . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 131
CIP Objects . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 131
Identity Object Class Code 0x0001 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 131
Assembly Object Class Code 0x0004 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 133
Read the Input Image Table of a 56RF-IN-IPD22 Interface Block
with a MicroLogix 1400. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 134
Input Image (56RF-IN-IPD22 Interface Block) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 135
Input Image (56RF-IN-IPD22A Interface Block) . . . . . . . . . . . . . . . . . . . . . . . . . . . . 136
Input Image (56RF-IN-IPS12 Interface Block). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 137
Write to the Output Image Table of a 56RF-IN-IPD22 Interface Block
with a MicroLogix 1400. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 138
Input Image (56RF-IN-IPD22 Interface Block) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 139
Input Image (56RF-IN-IPD22A Interface Block) . . . . . . . . . . . . . . . . . . . . . . . . . . . . 139
Input Image (56RF-IN-IPS12 Interface Block). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 140
Read the Input Image Table of a 56RF-IN-IPD22 Interface Block with an SLC-5/05 . 140
Class 1 Connections . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 142
Exclusive Owner Connection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 142
Input Only Connection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 142
Listen-only Connection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 143
Class 3 Connections . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 143

Rockwell Automation Publication 56RF-UM001E-EN-P - October 2022 7

Table of Contents

Discrete Input Point Object Class Code 0x0008 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 143

Discrete Output Point Object Class Code 0x0009. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 145

Appendix C
Install the Add-on Profile Introduction. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 147

Appendix D
Troubleshooting Common Solutions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 149

8 Rockwell Automation Publication 56RF-UM001E-EN-P - October 2022

 Preface

Who Should Use this Manual Use this manual if you are responsible for design, installation, programming, or
troubleshooting of control systems that use Bulletin 56RF RFID products.

You must have a basic understanding of electrical circuitry and familiarity with relay logic. If
you do not, obtain the proper training before using this product.

Purpose of this Manual This quick start guide assumes you have some familiarity with RSLogix™ software. This guide
provides an example of steps to follow to configure and make functional a 56RF RFID system.
The reader must refer to the appropriate user manuals for other details. You must use this
manual to accomplish the following:
• Learn how to install and wire an example RFID system
• Install and configure the module in an RSLogix 5000® program
• Built a simple program to receive and transmit data to an RFID tag

Summary of Changes This publication contains the following new or updated information. This list includes
substantive updates only and is not intended to reflect all changes.
Topic Page
Updated Abbreviations section 9
Updated Additional Resources section 10
Added Approximate Dimensions section 44
Added Add-On Instruction chapter 63
Updated Error Codes section 129

Abbreviations
Abbreviation Definition Abbreviation Definition
AFI Application Family Identifier International Organization for
ISO
AOI Add On Instruction Standardization
AOP Add-on Profile JTC Joint Technical Committee
DFSID Data Storage Format Identifier Media Access Control (Ethernet)
MAC address
DHCP Dynamic Host Configuration Protocol address
DNS Domain Name Server MACID Media Access Control Identification
DoS Disk Operating System QD Quick Disconnect
EAS Electronic Article Surveillance RFID Radio Frequency Identification
FE Functional Earth SB Subcommittee
Ferroelectric Random Access
FRAM SINT Signed, single-byte integer
Memory
International Electrotechnical UID Unique Identifier
IEC Commission UUID Universally Unique Identifier
INT Signed, two byte integer

Rockwell Automation Publication 56RF-UM001E-EN-P - October 2022 9

Additional Resources These documents contain additional information concerning related products from Rockwell
Automation.
Resource Description
High Frequency 13.56 MHz RFID EtherNet/IP Interface Block Provides information that is required to install RFID
Installation Instructions, publication 56RF-IN008 interface blocks.
Bulletin 56RF RFID Square 40x40 mm Transceiver Provides information that is required to install
Installation Instructions, publication 56RF-IN009 40x40 mm transceivers.
Bulletin 56RF Rectangular 80x90 mm Transceiver Provides information that is required to install
Installation Instructions, publication 56RF-IN010 80x90 mm transceivers.
High Temperature ICODE Tag (High Frequency RFID 13.56 Provides information that is required to install high
MHz) Installation Instructions, publication 56RF-IN011 temperature ICODE tags.
Bulletin 56RF RFID 30 mm Cylindrical Transceiver Provides information that is required to install 30 mm
Installation Instructions, publication 56RF-IN013 cylindrical transceivers.
RFID Specifications Technical Data, Provides specifications for 56RF products.
publication 56RF-TD001
This manual describes how to use EtherNet/IP
EtherNet/IP Network Devices User Manual, publication communication modules in Logix 5000™ control
ENET-UM006 systems.
A glossary of industrial automation terms and
Allen-Bradley Industrial Automation Glossary, AG-7.1 abbreviations.
This publication describes DLR network operation,
EtherNet/IP Device Level Ring Application Technique, topologies, configuration considerations, and
publication ENET-AT007 diagnostic methods.
Industrial Automation Wiring and Grounding Guidelines, Provides general guidelines for installing a Rockwell
publication 1770-4.1 Automation® industrial system.
Provides declarations of conformity, certificates, and
Product Certifications website, rok.auto/certifications other certification details.

You can view or download publications at rok.auto/literature.

10 Rockwell Automation Publication 56RF-UM001E-EN-P - October 2022

 Chapter 1

Introduction

RFID Defined RFID (Radio Frequency Identification) is a method to communicate information from one point
to another point by the use of electromagnetic waves (radio waves). RFID has unique
characteristics that make it attractive for use in industrial systems.

For example, you have a shipping carton that must be loaded with various goods to meet the
specific purchase order of a customer. You can attach a tag to the carton. Before attaching
the tag, you fill the tag with the specific items that the customer wants. Then, as the carton
moves to the filling stations, each station places the required objects into the carton. If the tag
does not require an item, the station is skipped.

Each filling station has an RFID transceiver. The transceiver reads and writes to the tag. When
the tag approaches the RFID transceiver, the transceiver reads the contents of the tag. Based
on the information that is received, the packaging process adds items (or skips this step) and
then writes to the tag that one or more items were added. The carton moves to the next filling
station.

This scenario is a common use of RFID technology. The Bulletin 56RF product line is unique
because of its conformance to the open international standards: ISO15693 and ISO18000-3 M1.

International Standard ISO/IEC 15693 is an ISO standard for vicinity tags. Vicinity tags, commonly referred to as ICODE
tags, can be read from a greater distance than proximity tags and closed couple tags. ISO/IEC
Compliance 15693 systems operate at the 13.56 MHz frequency, and offer a maximum read distance of
1…1.5 m (3.3…4.9 ft), depending on the transceiver. Library applications with large antennas
are capable of these distances. Most industrial applications are less than
203.2 mm (8 in.) for a read/write range.

The ICODE compatible tags permit you to use lower-cost tags than proprietary systems
currently provide. You can use tag configuration options from multiple vendors.

ISO/IEC 15693 forms part of a series of International Standards that specify non-contact tags.
The tags can be attached to objects, like cartons, bags, and valuable items, which can then be
tracked while in the vicinity of a reading device. ISO/IEC 15693-2:2006 defines the power and
communications interface between the vicinity card and the reading device. Other parts of
ISO/IEC 15693 define the physical dimensions of the card and the commands that the card and
reader interpret.

An AC field that is produced in the transceiver couples power to the tag. The powering field has
a frequency of 13.56 MHz and is one of the industrial, scientific, and medical (ISM) frequencies
available for worldwide use. When the tag receives sufficient power, it is able to respond to
commands sent from the coupler. The coupler sends commands to the card by modulating the
powering field and by using a modulation system that is known as pulse position modulation.
The position of one pulse relative to a known reference point codes the value of a nibble or
byte of data. This process allows the card to draw the maximum energy from the field almost
continuously. Tags, which have no power source, can be energized at ranges of up to 1 m
(3.3 ft) from a coupler that can only transmit power within the limits that international radio
frequency (RF) regulations permit.

Rockwell Automation Publication 56RF-UM001E-EN-P - October 2022 11

Chapter 1 Introduction

A tag only responds when it receives a valid command that selects one tag from a possible
collection of cards within range of the coupler. This process of collision detection and
selection, also known as anti-collision, is made possible by detecting the unique identification
number encoded into every tag. Anti-collision, and the commands that are used, are defined in
ISO/IEC 15693-3. The tag responds to the transceiver by drawing more or less power from the
field and generates one or two subcarriers of around 450 kHz that are switched on and off to
provide special-encoded data that the transceiver detects.

This device complies with Part 15 of the FCC Rules. Operation is subject to the following two
conditions:
1. This device causes no harmful interference.
2. This device must accept any interference received, including interference that can
cause undesired operation.

FCC Caution
Changes or modifications that are not expressly approved by the party responsible for
compliance can void the authority of the user to operate the equipment.

IMPORTANT This equipment has been tested and found to comply with the limits for
a Class A digital device, according to part 15 of the FCC Rules. These
limits are designed to provide reasonable protection against harmful
interference when the equipment is operated in a commercial
environment. This equipment generates, uses, and can radiate radio
frequency energy and, if not installed and used in accordance with the
instruction manual, can cause harmful interference to radio
communications. Operation of this equipment in a residential area is
likely to cause harmful interference, in which case the user is required
to correct the interference at their own expense. This device must be
installed and operated keeping at minimum 200 mm (0.79 in.) away
from bodies.

Taiwan NCC Warning Statement

《䖤㻤뀿阮僈⛓⡜⸆桧㼙걽㐼勞ꬌ竤呍ⲥⰗ぀㉂贫䧴⢪欽罏㖳♶䖤乲
荈隶刿걽桧⸈㣐⸆桧䧴隶刿⾲鏤鎙⛓暶䚍⿻⸆腋
⡜⸆桧㼙걽㐼勞⛓⢪欽♶䖤䕧갠굳菕㸞⿻䎁仠ざ岁鸒⥌竤涮植剤䎁仠
植韍儘䥰用⽰⨢欽⚛佖㊥荛搂䎁仠儘倰䖤糒糵⢪欽
⵹鶤ざ岁鸒⥌䭸⣜ꨶ⥌盘椚岁鋊㹁⡲噠⛓搂箁ꨶ鸒⥌
⡜⸆桧㼙걽㐼勞갭䗾「ざ岁鸒⥌䧴䊨噠猰㷸⿻ꄴ派欽ꨶ岚鱖㼙䚍ꨶ堥鏤⪔
⛓䎁仠

Date of manufacture (year/month) is written on package.

12 Rockwell Automation Publication 56RF-UM001E-EN-P - October 2022

 Chapter 1 Introduction

This device must be installed with a DC power cable that is under 3 m (9.84 ft) long. If the DC
power cable of the radio and/or the ancillary equipment is less than or equal to 3 m (9.84 ft) in
length, there is no need to conduct an emission test.

Backward Compatibility The 56RF RFID system is offered on EtherNet/IP™ and is backward compatible with the
previous offering of 56RF ICODE products. The transceivers and interface blocks are a
matched pair so they cannot be interchanged. However, the tags can be interchanged with
either system if they are ICODE tags. Both systems can read and write these tags seamlessly.

System Setup Figure 1 shows a simple RFID system. This user manual describes the setup, installation, and
programming that is required to get this system running.
Figure 1 - RFID System

1783-US05T
MS NS

56RF transceiver
LINK

ETHERNET/IP

Ethernet switch

1769-L35E
1
CompactLogix™ P
W
R

2
Tracked
3
object

56RF transceiver
Computer 4

1783-US05T
5

56RF interface 56RF tag

block

Tags are attached to objects that must be tracked. The tags hold important information about
the object. An RF transceiver reads and/or writes information to the tags when the tag moves
within the transmission envelope of the transceiver (dotted ellipse). The physical size of the
transceiver is directly related to the size of the transmission field. The larger the transceiver,
the longer and wider the antenna field is. See the transceiver installation instructions for
antenna field sizes (see Additional Resources on page 10).

The transceivers are connected to a special RFID EtherNet/IP interface block. The distribution
block has an Ethernet connection to an Ethernet switch. A 1759-L35E CompactLogix controller
and a personal computer also have Ethernet connections to the Ethernet switch.

Rockwell Automation Publication 56RF-UM001E-EN-P - October 2022 13

Chapter 1 Introduction

Notes:

14 Rockwell Automation Publication 56RF-UM001E-EN-P - October 2022

 Chapter 2

RFID Components

Interface Block Three different interface blocks are available. Table 1 shows the type of ports for each catalog
number.
Table 1 - Type of Ports
Transceiver Ports Input Ports Output Ports Cat. No.
1 1 1 56RF-IN-IPS12
2 1 1 56RF-IN-IPD22
2 2 0 56RF-IN-IPD22A

Figure 2 identifies the connections for the EtherNet/IP™, RF transceivers, input devices,
output devices, and power.
Figure 2 - Connections
Functional Earth (1)

EtherNet/IP D-Code M12 Connector EtherNet/IP D-Code M12 Connector

5-pin Convex 5-pin Concave

Status indicators

Node Address Switches

M12 RFID Transceiver Interface

5-pin Concave

M12 RFID Transceiver Interface

(IPD22, IPD22A) 5-pin Concave

M12 Input Connector

5-pin Concave

M12 Output Connector (IPS12, IPD22)

M12 Input Connector (IPD22A) Concave

Auxiliary Power M12 4-pin Convex Auxiliary Power M12

4-pin Concave

Rockwell Automation Publication 56RF-UM001E-EN-P - October 2022 15

Chapter 2 RFID Components

Status Indicators When the status indicator is flashing, all flashes are 0.25 s on and 0.25 s off.

This block has the seven status indicators.

Figure 3 - Status Indicators

Link 1 Link 2

MOD

NET

Transceiver Ports

Standard Input/Output

Auxiliary Power

Table 2 - Status Indicators

Status Status Indicator Indicates
Indicator State
Name
Off No link
Green 100 Mbps
Link1 and Link2 Flashing green 100 Mbps/active
Yellow 10 Mbps
Flashing yellow 10 Mbps/active
Off There is no power applied to the block.
Flashing red/ Device in self-test
green
Green The block is operating in a normal condition.
Flashing green Standby. The device is not communicating with the interface block. Normal
MOD (Module) state when only power has been applied to the transceiver.
Recoverable fault. Most often occurs when data is corrupted between interface
Flashing red block and transceiver. CRC failures and so on. Recommended solution is to
remove electrical noise near cabling or reduce communication rate between
transceiver and interface block.
Red The transceiver has an unrecoverable fault; can need replacing.
Off There is no power or no IP address.
Flashing red/ Device in self-test
green
Green The block is operating in a normal condition.
Standby. The device is not communicating with the interface block. Normal
Flashing green state when
NET (Network) only power has been applied to the transceiver.
Connection timeout. Most often occurs when data is corrupted between
Flashing red interface block and transceiver. CRC failures and so on. Recommended
solution is to remove electrical noise near cabling or reduce communication
rate between transceiver and interface block.
Duplicate IP address. The transceiver has an unrecoverable fault; can need
Red replacing.

16 Rockwell Automation Publication 56RF-UM001E-EN-P - October 2022

 Chapter 2 RFID Components

Table 2 - Status Indicators (Continued)

Status Status Indicator Indicates
Indicator State
Name
Outputs inactive
Off Inputs inactive
Outputs active
Yellow Inputs active
Standard I/O Flashing green Outputs are idled and not faulted.
Flashing red Output faulted
Inputs faulted
Outputs forced off
Red Inputs unrecoverable fault
Off No power is applied.
Aux Power Steady green The applied voltage is within specifications.
Steady yellow The input power is out of specification.
Off No power
Flashing green No tag present, but communicating.
RFID Port Green Communicating
Flashing red No transceiver is connected.
Amber Tag present

Transceivers Status Indicators

Figure 4 - Indicators

Power Module
Status Operation Read/Write
Status

Table 3 - Status Indicators

Status
Status
Indicator Name Indicator Indicates
State
Off There is no power applied to the block.
Module Status Green The block is operating in a normal condition.
Red The transceiver has an unrecoverable fault; can need replacing.
Off There is no power applied to the device.
The EtherNet/IP interface block is communicating with the transceiver, but no tag
Read/Write Green is present. No errors received.
Status
Amber A tag is present within the antenna field.
Red A communication error has occurred. Examples are: bad read/write, corrupt CRC(1)
(1) If a read/write command is not completed while the tag is within the field, an error occurs.

Rockwell Automation Publication 56RF-UM001E-EN-P - October 2022 17

Chapter 2 RFID Components

Transceiver Power-up Sequence

1. Both status indicators off.
2. Power status indicator turns green. R/W status turns green for 0.25 s.
3. R/W status indicator turns red for 0.25 s.
4. R/W status indicator turns off for 3…5 s.
5. R/W status indicator turns amber for 0.5 s.
6. R/W status indicator turns green.

RFID Tags RF tags come in many shapes and sizes. In general, the bigger the tag, the longer the sensing
distance from the transceiver. Table 4 summarizes the size of the memory for each type of
tag.
Table 4 - Memory

Total Tag User Memory

Tag Type Memory No. of Bytes No. of Blocks Bytes Per Block
SLI 128 bytes 112 bytes 28 4
SLI-S 256 bytes 160 bytes 40 4
SLI-L 64 bytes 32 bytes 8 4
FRAM 2048 bytes 2 kB 250 8

Tag Memory Structure

There are five types of tag memory structure:
• Universally Unique Identifier (UUID)
• Application Family Identifier (AFI)
• Data Storage Format Identifier (DSFID)
• Electronic Article Surveillance (EAS)
• Smart Label Integrated Circuit (SLI)

Universally Unique Identifier (UUID)

Each tag has a unique 64 bit hexadecimal UUID that is programmed during the production
process according to ISO/IEC 15693-3 and cannot be changed afterwards.

The numbering of the 64 bits is done according to ISO/IEC 15693-3; numbering starts with the
least significant bit (LSB) 1 and ends with the most significant bit (MSB) 64. This way is in
contrast to the general used bit numbering within a byte (starts with LSB 0).
Byte 5 (bit 41…48) is the tag type. Byte 6 (bit 49…56) is the manufacturer code, which coincides
with the number of bytes/block.
Table 5 shows the structure of our RFID tags.
Tag Structure

Table 5 - Tag Structure

Byte 7 6 5 4 3 2 1 0
Name UID 7 UID 6 UID 5 UID 4 UID 3 UID 2 UID 1 UID 0
Bit 64…57 56…49 48…41 40…1
SLI E0 04 01 Unique Serial Number
SLI-S E0 04 02 Unique Serial Number
Value
SLI-L E0 04 03 Unique Serial Number
FRAM E0 08 01 Unique Serial Number

18 Rockwell Automation Publication 56RF-UM001E-EN-P - October 2022

 Chapter 2 RFID Components

Application Family Identifier (AFI)

The AFI represents the type of application targeted. AFI is coded on 1 byte, which constitutes
two nibbles of 4 bits each. The most significant nibble of AFI is used to code one specific or all
application families, as defined in
Table 6. The least significant nibble of AFI is used to code one specific or all application
subfamilies. Subfamily codes different from 0 are proprietary.
AF

Table 6 - AFI Examples

AFI Most AFI Least Meaning Examples/Notes
Significant Nibble Significant Nibble
0 0 All families and subfamilies No applicative preselection
X 0 All subfamilies of family X Wide applicative preselection
X Y Only the Yth subfamily of family X —
0 Y Proprietary subfamily Y only —
1 0, Y Transport Mass transit, bus, airline
2 0, Y Financial IEP, banking, retail
3 0, Y Identification Access control
4 0, Y Telecommunication Public telephony, GSM
5 0, Y Medical —
6 0, Y Multimedia Internet service
7 0, Y Gaming —
8 0, Y Data storage Portable files
EAN-UCC (European Article
9 0, Y Numbering-Uniform Code Council) Managed by ISO/IECJTC 1/SC 31
system for application identifiers
Data Identifiers as defined in ISO/
A 0, Y Managed by ISO/IEC JTC 1/SC 31
IEC 15418
B 0, Y UPU Managed by ISO/IEC JTC 1/SC 31
IATA (International Air Transport
C 0, Y Managed by ISO/IEC JTC 1
Association)
D 0, Y Reserved for Future Use Managed by ISO/IEC JTC 1/SC 17
E 0, Y Reserved for Future Use Managed by ISO/IEC JTC 1/SC 17
F 0, Y Reserved for Future Use Managed by ISO/IEC JTC 1/SC 17

X = ‘1’ to ‘F’, Y = ‘1’ to ‘F’

Data Storage Format Identifier (DSFID)

The DSFID indicates how data is structured in the tag memory. The respective commands can
program and lock it. It is coded on 1 byte. It allows for instant knowledge on the logical
organization of the data.

Electronic Article Surveillance (EAS)

EAS is a technology that is typically used to help prevent shoplifting in retail establishments.
An EAS detection system detects active tags and sets off an alarm.
EAS status is 1-bit data (LSB side), which is stored in the system area of a tag. The initial value
is 1. EAS bit 1 means goods-monitoring status, and EAS bit 0 means that goods-monitoring
status is cleared.

Rockwell Automation Publication 56RF-UM001E-EN-P - October 2022 19

Chapter 2 RFID Components

Smart Label Integrated Circuit (SLI)

SLI tags use an EEPROM (electrically erasable programmable read-only memory) to store data.
The 1024-bit EEPROM memory is divided into 32 blocks. Each block consists of 4 bytes
(1 block = 32 bits). Bit 0 in each byte represents the least significant bit (LSB) and bit 7 the
most significant bit (MSB), respectively.
SLI Tags

Table 7 - SLI Tags

Block Byte 0 Byte 1 Byte 2 Byte 3 Description
-4 UID0 UID1 UID2 UID3 Unique identifier (lower bytes)
-3 UID4 UID5 UID6 UID7 Unique identifier (higher bytes)
-2 Internally used EAS AFI DSFID EAS, AFI, DSFID
-1 00 00 00 00 Write access conditions
0
1
2
:
: User Data
:
22
23
27

SLI

EAS Function

The LSB of Byte 1 in Block -2 holds the EAS bit (Electronic Article Surveillance mode active – the
label responds to an EAS command)
EAS

Table 8 - EAS
Block -2, Byte 1
MSB LSB
X X X X X X X e

EAS: e = 1 (EAS enabled) e = 0 (EAS disabled)

IMPORTANT Only change the EAS Configuration in a secure environment. The label
must not be moved out of the communication field of the antenna
during writing. We recommend putting the label close to the antenna
and not to remove it during the operation.

Application Family Identifier

The ICODE system offers the feature to use an AFI at the inventory command and the two
custom commands inventory read and fast inventory read (this feature allows, for example,
the creation of label families).

This 8-bit value is at Byte 2 in Block -2 as shown in Table 9 and is only evaluated if the AFI flag
is set in the reader command.
AFI

Table 9 - AFI
Block -2, Byte 2
MSB LSB
X X X X X X X X

20 Rockwell Automation Publication 56RF-UM001E-EN-P - October 2022

 Chapter 2 RFID Components

Data Storage Format Identifier

The Data Storage Format Identifier (DSFID) is at Byte 3 in Block -2.

DSFID

Table 10 - DSFID
Block -2, Byte 3
MSB LSB
X X X X X X X X

Write Access Conditions

The Write Access Condition bits in Block -1 determine the write access conditions for each of
the 28 user blocks and the special data block. These bits can be set only to 1 with a lock
command (and never be changed back to 0), that is, already write-protected blocks can never
be written to from this moment on.
In Block -2, each byte can be individually locked.
Table 11 - Write Access
Block -1
Byte 0 Byte 1
MSB LSB MSB LSB
Condition 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
Write Access
for Block 3 2 1 0 -2 (3) -2 (2) -2 (1) -2 (0) 11 10 9 8 7 6 5 4
Number

Block -1
Byte 2 Byte 3
MSB LSB MSB LSB
Condition 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
Write Access
for Block 19 18 17 16 15 14 13 12 27 26 25 24 23 22 21 20
Number

Block -1
Byte 2 Byte 3
MSB LSB MSB LSB
Condition 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
Write Access
for Block 19 18 17 16 15 14 13 12 27 26 25 24 23 22 21 20
Number

IMPORTANT Only change the Write Access conditions in a secure environment. The
label must not be moved out of the communication field of the antenna
during writing. We recommend putting the label close to the antenna
and not to remove it during operation.

Smart Label IC – Secure (SLI-S)

The 2048-bit EEPROM memory is divided into 64 blocks. A block is the smallest access unit.
Each block consists of 4 bytes (1 block = 32 bits). Four blocks are summed up to one page for
password protection. Bit 0 in each byte represents the least significant bit (LSB) and bit 7 the
most significant bit (MSB), respectively.

Rockwell Automation Publication 56RF-UM001E-EN-P - October 2022 21

Chapter 2 RFID Components

The memory is divided into two parts:

• Configuration Area
This memory area stores all required information, such as UID, EPC data, write
protection, access control information, passwords. Direct access to this memory area
is not possible.
• User Memory
This memory area stores user data. Direct read/write access to this part of the memory
is possible depending on the related security and write protection conditions.

Table 12 on page 22 shows the memory organization of an SLI-S tag.

SLI-S Memory Organization

Table 12 - SLI-S Memory Organization

Page Block Byte 0 Byte 1 Byte 2 Byte 3 Description
-6 -24
-23
-22
-21
Configuration area for internal use
: : : : : :
: : : : : :
: : : : : :
: : : : : :
-1 -4
-3
-2
-1
0 0
1
2
3 User Memory
: : : : : : 10 pages
4 blocks per page
: : : : : : 4 bytes per block
9 36 Total: 160 bytes
37
38
39

Smart Label IC – Lean (SLI-L)

The SLI-L is used in applications that require smaller memory size. The 512 bit EEPROM
memory is divided into 16 blocks. A block is the smallest access unit. Each block consists of 4
bytes (1 block = 32 bits). Four blocks are summed up to one page. Bit 0 in each byte represents
the least significant bit (LSB) and bit 7 the most significant bit (MSB), respectively.

The memory is divided into two parts:

• Configuration Area
This memory area stores all required information, such as UID, write protection,
passwords. Direct access to this memory area is not possible.
• User Memory
This memory area stores user data. Direct read/write access to this part of the memory
is possible depending on the related write protection conditions.

22 Rockwell Automation Publication 56RF-UM001E-EN-P - October 2022

 Chapter 2 RFID Components

Table 13 shows the memory organization of an SLI-L tag.

SLI-L Memory Organization

Table 13 - SLI-L Memory Organization

Page Block Byte 0 Byte 1 Byte 2 Byte 3 Description
-2 -8
-7
Configuration area for internal use
-6
-5
-1 -4
-3
-2
-1
0 0
1
2 User Memory
3 2 pages
4 blocks per page
4 4 bytes per block
5 Total: 32 bytes
6
7

Ferroelectric Random Access Memory (FRAM)

FRAM is a nonvolatile memory that uses ferroelectric film as a capacitor for storing data. FRAM
offers high-speed access, high endurance in write mode, low power consumption, non-
volatility, and excellent tamper resistance. The FRAM tags have 2000 bytes for use as user
area and 48 bytes for use as system area.

The FRAM tag memory areas consist of a total of 256 blocks (250 blocks of user area and 6
blocks of system area). Each block can store 64 bits (8 bytes) of data.

The block is the unit that is used for the writing and reading of FRAM data. The memory
configuration of FRAM is shown in Table 14 on page 23.
Table 14 - FRAM Memory Configuration
Area Block No. Details Data Read Data Write
User area 00H to F9H User area Yes Yes
(2000 bytes)
FAH UUID (64 bits) Yes No
System area FBH AFI, DSFID, EAS,
(48 bytes) Yes Limited
security status
FCH to FFH Block security status Yes No

Blocks 00H…F9H are user area, which is defined as an area that can be accessed when the
corresponding block address is specified. While Blocks FAH…FFH are system area, which is
defined as an area that can be accessed only with a specific command.

The system area consists of six blocks and contains UUID, AFI, DSFID, EAS bits, and security
status (can write or cannot write) data for individual block. UID is fixed and cannot be updated.
AFI, DSFID, and EAS bits are written at the factory, and can be updated and locked (disable to
write) with commands (only EAS bit cannot be locked).

Rockwell Automation Publication 56RF-UM001E-EN-P - October 2022 23

Chapter 2 RFID Components

As shown in Table 14, FAH holds the UUID, and FCH…FFH hold the security status information on
individual user areas. The configuration of FBH …FFH blocks is shown in Table and Table 16.
FBH block is used for EAS status, AFI and DSFID data, the security status data of AFI and DSFID.
Blocks FCH…FFH contain security status data.
St

Table 15 - Structure of FBH

MSB LSB
64 57 56 33 32 25 24 17 16 9 8 1
Reserved for DSFID Lock
EAS Status AFI Lock Status DSFID AFI
future use Status
St

Table 16 - Structure of FCH to FFH

MSB LSB
FCH 3F 3E 3D 3C 3B 3A 39 03 02 01 00
FDH 7F 7E 7D 7C 7B 7A 79 43 42 41 40
FEH BF BE BD BC BB BA B9 83 82 81 80
FFH Reserved for future use (6 bits) F9 C3 C2 C1 C0

The security status of the user area is stored in the block security status bit in system area
blocks of FCH…FFH per bit in each block. A user area is unlocked when the corresponding block
security status bit is 0; it is locked (disable to write state) when the corresponding block
security status bit is 1.

EAS bit is one bit, and it is used for setting EAS status. It is possible to
read/write data of two blocks at one time in the user area (if Read Multiple Blocks Unlimited
command is used, up to 256 blocks can be accessed at one time).

Product Selection Table 17…Table 22 on page 26 show the catalog numbers for the components in the
Bulletin 56RF product family.

Main Components
Table 17 - EtherNet/IP Interface Blocks
Transceiver Ports Input Ports Output Ports Cat. No.
1 1 1 56RF-IN-IPS12
2 1 1 56RF-IN-IPD22
2 2 0 56RF-IN-IPD22A

Table 18 - Transceivers
Recommended Sensing Sensing Distance, Max
Dimensions [mm (in.)] Cat. No.
Distance [mm (in.)] (1) [mm (in.)] (1)
Rectangular 100 (3.9) 168 (6.6) 56RF-TR-8090
[80 x 90 (3.14 x 3.54)]
Square 50 (2) 85 (3.3) 56RF-TR-4040
[40 x 40 (1.57 x 1.57)]
Cylindrical M30 35 (1.4) 60 (2.4) 56RF-TR-M30
Cylindrical M18 18 (0.7) 30 (1.2) 56RF-TR-M18
(1) Range reference for a 50 mm (2 in.) diameter tag.

24 Rockwell Automation Publication 56RF-UM001E-EN-P - October 2022

 Chapter 2 RFID Components

Table 19 - Tags
Total Memory User Memory Dimensions
Outline Type Cat. No.
Size [B] Size [B] [mm (in.)]
16 (0.6) 56RF-TG-16
20 (0.8) 56RF-TG-20
SLI 128 112
30 (1.2) 56RF-TG-30
Disc
50 (2) 56RF-TG-50
SLI-S 64 32 16 (0.6) 56RF-TG-16-64B
SLI-L 256 160 10 (0.4) 56RF-TG-10-256B
Disc – High Impact SLI 128 112 35 (1.4) 56RF-TG-35HIR
Resistant
20 (0.8) 56RF-TG-20MOM
Disc – Mount on Metal SLI 128 112
50 (2) 56RF-TG-50MOM
20 (0.8) 56RF-TG-20-2KB
Disc – FRAM FRAM 2048 2 kB 30 (1.2) 56RF-TG-30-2KB
50 (2) 56RF-TG-50-2KB
54 x 86 56RF-TG-5486
(2.1 x 3.4)
Label SLI 128
50 x 50
(2 x 2) 56RF-TG-5050
112
54 x 86
Smart Cards SLI 128 56RF-TG-5486SC
(2.1 x 3.4)
Square – High 50 x 50
SLI 128 56RF-TG-50HT
Temperature (2 x 2)

Accessories
Table 20 - Transceiver
Wire Size
Style Connector Type No. of Pins Shield Cat. No.
[mm² (AWG)]
Concave straight to
convex straight 889D-F5FCDM-Jx (1)
Concave straight to
convex right angle 889D-F5FCDE-Jx (1)
DC Micro (M12)
Concave right angle 4 Shielded 0.34 (22)
Patchcords 889D-R5FCDM-Jx (1)
to convex straight
Concave right angle
to convex right 889D-R5FCDE-Jx (1)
angle
Concave straight 889D-F5FC-Jx (2)
DC Micro (M12) Concave right angle 889D-R5FC-Jx (2)
4 Shielded 0.34 (22)
Patchcords Convex straight 889D-M5FC-Jx (2)
Convex right angle 889D-E5FC-Jx (2)
Concave straight 871A-TS5-D1
M12 Terminal Concave right angle 0.34…0.75 871A-TR5-D1
4 —
Chambers Convex straight (22…18) 871A-TS5-DM1
Convex right angle 871A-TR5-DM1
(1) Replace x with OM3 (0.3 m [1 ft]), 1 (1 m [3.3 ft]), 2 (2 m [6.6 ft]), 5 (5 m [16.4]), or 10 (10 m [32.8 ft]).
(2) Replace x with 2 (2 m [6.6 ft]), 5 (5 m [16.4]), or 10 (10 m [32.8 ft]).

Rockwell Automation Publication 56RF-UM001E-EN-P - October 2022 25

Chapter 2 RFID Components

Table 21 - Auxiliary Power

Wire Size
Style Connector Type No. of Pins Shield Cat. No.
[mm² (AWG)]
Concave straight to
convex straight 889D-F4ACDM-x (1)
Concave straight to
convex right angle 889D-F4ACDE-x (1)
DC Micro (M12) 4 Unshielded 0.34 (22)
Patchcords Concave right angle 889D-R4ACDM-x (1)
to convex straight
Concave right angle
to convex right 889D-R4ACDE-x (1)
angle
Concave straight 889D-F4AC-x (2)
DC Micro (M12) Concave right angle 889D-R4AC-x (2)
4 Unshielded 0.34 (22)
Patchcords Convex straight 889D-M4AC-x (2)
Convex right angle 889D-E4AC-x (2)
Concave straight 871A-TS4-D
M12 Terminal Concave right angle 871A-TR4-D
4 — 0.34 (22)
Chambers Convex straight 871A-TS4-DM
Convex right angle 871A-TR4-DM
(1) Replace x with OM3 (0.3 m [1 ft]), 1 (1 m [3.3 ft]), 2 (2 m [6.6 ft]), 5 (5 m [16.4]), or 10 (10 m [32.8 ft]).
(2) Replace x with 2 (2 m [6.6 ft]), 5 (5 m [16.4]), or 10 (10 m [32.8 ft]).

Table 22 - EtherNet/IP
Wire Size
Style Connector Type No. of Pins Shield Cat. No.
[mm² (AWG)]
Convex straight to
convex straight 1585D-M4TBDM-x (1)
Convex straight to
M12 D Code
convex right angle 4 Unshielded 0.25 (24) 1585D-M4TBDE-x (1)
Patchcords
Convex right angle
to convex right 1585D-E4TBDE-x (1)
angle
Convex straight to
convex straight 1585D-M4UBDM-x (1)
Convex straight to
M12 D Code convex right angle 4 Shielded 0.14 (26) 1585D-M4UBDE-x (1)
Patchcords
Convex right angle
to convex right 1585D-E4UBDE-x (1)
angle
(1) Replace x with OM3 (0.3 m [1 ft]), 1 (1 m [3.3 ft]), 2 (2 m [6.6 ft]), 5 (5 m [16.4]), 10 (10 m [32.8 ft]), or 15 (15 m [49.2 ft]).
Increments of 5 m (16.4 ft) up to 75 m (246.1 ft) are also available.

26 Rockwell Automation Publication 56RF-UM001E-EN-P - October 2022

 Chapter 3

Electrical Installation

Cable Overview The Ethernet switch must be mounted inside a control panel. The Bulletin 56RF interface block
and Bulletin 56RF transceivers can be mounted on the machine.
Figure 5 - Transceiver Mounting
Mounted in a Mounted on
Cabinet the Machine

1
1
P
W
R

4
2
1783-US05T

1783-US05T 56RF Interface 56RF Transceivers

Ethernet Switch Block

Figure 5 shows the three types of cables that are needed.

1. An Ethernet cable, RJ45 to M12-QD patchcord.
2. A 5-pin M12 to 5-pin M12 patchcord. The cable includes a shield that connects to the
functional earth point on the interface block.
3. A 4-pin concave micro QD cordset that connects power to the interface block.

Auxiliary Power Connection Attach a micro-style 4-pin concave to the micro-style 4-pin convex receptacle as shown in
Figure 6 on page 28. The concave side is used to daisy chain the power to another device. The
power connection is limited to 4 A. When the daisy chain approach is used, the total power that
is consumed by each block determines the maximum number of interface blocks that can be
connected.

IMPORTANT Power must be connected to the convex connector first. Do not connect
power to the concave connector and leave the convex connector
exposed. The pins in the convex connector have 24V DC potential for
short circuit.

Rockwell Automation Publication 56RF-UM001E-EN-P - October 2022 27

Chapter 3 Electrical Installation

Figure 6 - Pin Connections for the Aux Power Connectors

2 Module Power +

1 Output Power +
Module Power - 3
4 Output Power -
Convex

Module Power + 2

Output Power + 1
3 Module Power -
Output Power - 4
Concave

The power for the output port is separate from the power to the remaining portions of the
interface block. This configuration allows the output device to be turned off, while maintaining
power to the transceivers, the input port, and the EtherNet/IP™ connection. When the output is
connected to the safety-related portion of the machine control system, an actuator can be
turned off, while diagnostic information is still available to the machine control system.

Power Connection Options Each interface block is limited to 4 A total consumption.

Example 1: Daisy Chain the Power Connections

The example in Figure 7 allows for a simple and easy way to distribute power to the RFID
system. This approach is preferred when the total current of the RFID system is less than 4 A.
Figure 7 - Power Option 1
56RF Interface Blocks

889D-R4AC-5
1606-XL120D 889D-F4ACDM-5

889D-F4AC-5
889D-R4ACDE-5

Example 2: System Needs More Than 4 A

If multiple blocks are required on a machine and the current consumption exceeds 4 A, then a
combination of mini-style and micro-style connections can be used to distribute the power. In
the example shown in Figure 8 on page 29, mini-style cordsets, patchcords, and tees are used
to configure the power. A mini-to-micro style patchcord connects each 56RF interface block
with the tee. In this example, the power supply is a catalog number 1606-XLDNET8, which can
supply up to 8 A to the RFID system.

28 Rockwell Automation Publication 56RF-UM001E-EN-P - October 2022

 Chapter 3 Electrical Installation

Figure 8 - Power Option 2

56RF Interface Blocks

1606-XLDNET8 889D-R4AENM-D2 889D-F4AENM-D2 889D-R4AENM-D2

DC 24V/8 A
889N-F4AF-20F 889N-F4AFNU-20F

898N-43PB-N4KF 898N-43PB-N4KF

Transceiver Connection
The following shows the M12 QD concave connector for the transceivers. Pin 5 is the cable
shield connection and is connected only at the block to functional earth (FE).

Pin Function
2
1 24V DC power
1 3 2 Data +
3 24V common
5
4 4 Data -
5 Shield/FE

Digital Input Connection

The following shows the concave M12 QD input connector.

Pin Function
2 1 24V DC power
2 Not used
1 3
3 24V common
5 4 Digital input
4
5 Shield/FE

Digital Output Connection

The following shows the concave M12 QD output connector.

Pin Function
2 1 Not used
2 Not used
1 3 3 24V common
5 4 Digital output
4
5 Shield/FE

Rockwell Automation Publication 56RF-UM001E-EN-P - October 2022 29

Chapter 3 Electrical Installation

EtherNet/IP Connection
The following shows the D-Code M12 connector on the interface block.

Pin Function
4
1 Tx+
2 Rx+
3 5 1 3 Tx-
4 Rx-
2
5 Connector shell connected to FE

Use the catalog number 1585D-M4DC-H (polyamide small body unshielded) or catalog number
1585D-M4DC-SH (zinc die-cast large body shielded) mating connectors for the D-Code M12
concave network connector.

Use two twisted-pair Cat 5E UTP or STP cables.

D-Code M12 Pin Wire Color Signal 8-Way Modular RJ45 Pin
1 White-Orange Tx+ 1
2 White-Green Rx+ 3
3 Orange Tx- 2
4 Green Rx- 6

The 56RF interface block encoders can be connected in the following network topologies:
• Star Topology on page 31
• Linear Topology on page 31
• Device Level Ring (DLR) Topology on page 32

30 Rockwell Automation Publication 56RF-UM001E-EN-P - October 2022

 Chapter 4

EtherNet/IP Addressing

Star Topology The star topology consists of a number of devices that connect to the central switch. When
this topology is used, only one Ethernet connection can be made to the Bulletin 56RF interface
block – this connection is made to the Link 1 connector. The Link 2 connection must remain
unused.
Figure 9 - Star Topology

RFID Transceivers RFID Transceivers

RFID Interface RFID Interface
Block Block

Linear Topology The linear topology uses the embedded switching capability to form a daisy-chain style
network that has a beginning and an end. Linear topology simplifies installation and reduces
wiring and installation costs, but a break in the network disconnects all devices downstream
from the break. When this topology is used, both Ethernet connections are used. The network
connection to Link 1 or Link 2 does not matter.

Rockwell Automation Publication 56RF-UM001E-EN-P - October 2022 31

Chapter 4 EtherNet/IP Addressing

Figure 10 - Linear Topology

RFID Interface RFID Interface
Block RFID Block RFID
Transceivers Transceivers

Device Level Ring (DLR) A DLR network is a single-fault tolerant ring network that is intended for the interconnection of
automation devices. DLR topology is advantageous as it can tolerate a break in the network. If
Topology a break is detected, the signals are sent out in both directions. When this topology is used,
both Ethernet connections are used. The network connection to Link 1 or Link 2 does not
matter.

We recommend that you use no more than 50 nodes on one DLR, or linear, network. If your
application requires more than 50 nodes, we recommend that you segment the nodes into
separate, but linked, DLR networks.

Smaller networks provide the following benefits:

• There is better management of traffic on the network.
• The networks are easier to maintain.
• There is a lower likelihood of multiple faults.

Additionally, on a DLR network with more than 50 nodes, network recovery times from faults
are higher. The maximum cable length between devices cannot exceed 100 m (328 ft).

For more information on DLR network design and configuration, see publication ENET-AP007.

32 Rockwell Automation Publication 56RF-UM001E-EN-P - October 2022

 Chapter 4 EtherNet/IP Addressing

Figure 11 - DLR Topology

RFID Interface
Block RFID
Transceivers

RFID
Transceivers RFID Interface
Block

Setting the Network Before using the 56RF interface block in an EtherNet/IP™ network, configure it with an IP
address, subnet mask, and optional Gateway address. This chapter describes these
Address configuration requirements and the procedures for providing them. The address can be set in
one of three ways:
• Use the Network Address switches.
• Use the BootP/DHCP utility (version 2.3 or greater), which ships with RSLogix 5000®
software.
• Use RSLinx® software.

IP network addresses have a format of xxx.xxx.xxx.xxx. You must know what values are being
used for the network. If your network has the fundamental 192.168.1.xxx scheme, then you can
simply use the three network address switches. If your network is something other than
192.168.1.xxx, you must use advanced tools, such as the BootP/DHCPserver, to assign an IP
address. After the address is set, you can use RSLinx software to change the address.

Fundamental IP Addresses: If your network scheme is 192.168.1.xxx, then you can adjust the network address switches to
set the IP address. Remove the covers of the three network address screws. Use a screwdriver
192.168.1.xxx to rotate the switches. Align the small notch on the switch with the number setting you wish to
use. Valid settings range from 001…254.

When the switches are set to a valid number, the IP address of the interface block is
192.168.1.xxx (where xxx represents the number set on the switches). Cycle the power and the
valid setting becomes effective immediately.

Figure 12 on page 34 shows an address setting of 192.168.1.123.

Rockwell Automation Publication 56RF-UM001E-EN-P - October 2022 33

Chapter 4 EtherNet/IP Addressing

Figure 12 - Address Setting Example

The subnet mask of the interface block is automatically set to 255.255.255.0 and the gateway
address is set to 0.0.0.0. When the interface block uses the network address set on the
switches, the interface block does not have an assigned host name or use a Domain Name
Server (DNS).

Advanced IP Addresses step 1…step 6 show how to change the IP address from the fundamental 192.168.1.xxx to an
advanced address. This procedure assumes that the 56RF interface block was already
configured with an IP address using the network address switches. The following examples
show the change process using specific addresses. You are not limited to these addresses;
you can select any address that meets their needs. In the following example, we change from
192.168.1.115 to 192.168.2.115.
1. Set address switches to 888 and cycle the power.
On the 56RF interface block, the address switches had previously been to 115. Set the
address switch settings to 888. Cycle the power and wait until the MOD indicator is
flashing red. The MOD indicator flashes red once, green once, then steady red for a
short while, then flashes green once, and finally flashes red continuously (about once
each second). This process takes about 10 seconds after power is restored. The
interface block is reset to its factory setting.
2. Set the address switches to 999 and cycle the power.
On the 56RF interface block, set the address switch settings to 999. Cycle the power and
wait until the MOD indicator is steady green. The MOD indicator flashes red once, green
once, steady red for a short while and finally turns steady green. This process takes
about 10 seconds after power is restored. The interface block IP address is reset.
3. Use BootP/DHCP Server to set new valid address.
a. From the Start menu, select Programs > Rockwell Software > BOOTP-DHCP Server >
BOOTP-DHCP Server.

b. When power is restored, the interface block repeatedly broadcasts its MAC ID and
requests an IP address. The BOOTP-DHCP server displays the MAC ID in the Request
History panel.

34 Rockwell Automation Publication 56RF-UM001E-EN-P - October 2022

 Chapter 4 EtherNet/IP Addressing

c. Double-click one of the Ethernet addresses (MAC) of the device. The New Entry dialog
appears, which shows the Ethernet address (MAC) of the device.

d. Type in the IP address, host name, and description and click OK. The host name and
description are optional fields; they can be left blank.
The device is added to the Relation List, which displays the Ethernet address (MAC) and
corresponding IP address, host name, and description.
When the address is assigned to the 56RF interface block, the Status message is
updated and the IP address appears in the Request History window.

IMPORTANT Wait for the Status message to show “Sent 192.168.2.115 to

Ethernet address 00:00:BC:E5:D0:1D.” This process can take up
to 30 seconds.
4. At this point, the IP addresses of other devices are changed.
5. Change the Network Adapter to 192.168.2.1.
a. Open the network connections of the host computer.
b. Highlight the Internet Protocol (TCP/IP) connection.
c. Click Properties. In the IP address field, set the IP address to 192.168.2.1. Click OK.
d. Click Close to close the Local Area Connection window (this window must be closed
to apply the new address).

Rockwell Automation Publication 56RF-UM001E-EN-P - October 2022 35

Chapter 4 EtherNet/IP Addressing

6. Disable DHCP.
a. Set the rotary switches to 0 0 0.

b. To highlight the interface block, single-click it in the Relation List.

c. Then, click Disable BOOTP/DHCP. This action instructs the 56RF interface block to
retain the IP address at the next power cycle.
Wait for the Status message to show that the command was successfully sent. If not,
repeat this step.

d. Click File > Save As to save the relationship, if desired.

e. Cycle the power to the 56RF interface block. You no longer see the 56RF interface
block in the Request History panel.
f. From a DoS prompt, you can ping the new address. The response must be four
packets sent, four packets received, and zero lost.

36 Rockwell Automation Publication 56RF-UM001E-EN-P - October 2022

 Chapter 4 EtherNet/IP Addressing

Change IP Address from The easiest way to change the IP address from one non-simple address to another non-simple
address is to use RSLinx. In this case, the three network switches on the 56RF interface block
One Advanced Address to are set to 999, and the address has been previously set using the BootP/DHCP server. The
Another Advanced Address following example shows how to change the IP address from 192.168.2.115 to 192.168.3.115.

After you open RSLinx:

1. Click the RS-Who icon.
2. Expand the Ethernet connection.
3. Right-click the RFID Adapter.
4. Click Module Configuration.

After the Configuration window appears:

1. Click the Port Configuration tab.
2. Set the Network Configuration Type to Static (if not already done).
3. Change the IP address to the new address. In this example, the address is changed from
192.168.2.115 to 192.168.3.115.

a. Click Yes to confirm the change.

Rockwell Automation Publication 56RF-UM001E-EN-P - October 2022 37

Chapter 4 EtherNet/IP Addressing

b. To close the configuration window, click OK.

RSLinx places an X over the RFID adapter because it can no longer communicate with it.

c. Use the same steps to change the IP address of the other devices on the network.
Change the Network adapter address to 192.168.3.1.
d. Close and reopen the RSWho window. The older addresses are not available and the
new addresses (192.168.3.115 and 192.168.3.214) appear.

IMPORTANT If DHCP is not disabled, the 56RF interface block shows two
requests in the DHCP Server at each 56RF interface block power-
up.
In the following example, power was cycled to the 56RF interface block at 7:45:16,
7:47:47, 7:49:06, and again at 10:56:00. Each time power was applied, the 56RF interface
block notified the BootP/DHCP server of its IP address, which indicates that DHCP has
not been disabled. If DHCP is disabled, the 56RF interface block would show nothing.

38 Rockwell Automation Publication 56RF-UM001E-EN-P - October 2022

 Chapter 4 EtherNet/IP Addressing

IP Address 888 Address 888 is used to reset the interface block to the factory defaults. Rotate the address
switches to 888 and cycle the power. The interface block clears out the current assigned IP
address.

The MOD indicator flashes the following pattern: flashes red once, green once, then steady red,
then flashes green once, and final flashes continuous red about once each second. The reset
process takes about 10 seconds.

Rockwell Automation Publication 56RF-UM001E-EN-P - October 2022 39

Chapter 4 EtherNet/IP Addressing

Notes:

40 Rockwell Automation Publication 56RF-UM001E-EN-P - October 2022

 Chapter 5

Mechanical Installation

Each transceiver generates a similar but unique RF field.

Fastening Attach the transceiver to the flat plate with M5 screws. The tightening torque must be 1.5 N•m
(13.3 lb•in) for the M5 screw.

Spacing Between The installation of multiple transceivers causes radio frequency interference and can result in
tag communication difficulty. Keep a sufficient distance between the transceivers as shown in
Transceivers Figure 13.
Figure 13 - Spacing Between Transceivers [mm (in.)]

≥300 (11.8) ≥300 (11.8)

Square Transceiver

≥600 (23.6)

≥600 (23.6)

Rectangular Transceiver

Rockwell Automation Publication 56RF-UM001E-EN-P - October 2022 41

Chapter 5 Mechanical Installation

Spacing Next to Metal For the square transceiver, the communication distance drops significantly when the distance
between the transceiver and any surrounding metal is 30 mm (1.2 in.) or less.
Surfaces
For the rectangular transceiver, the communication distance drops significantly when the
distance between the transceiver and any surrounding metal is 50 mm (2 in.) or less.
Figure 14 - Transceiver Spacing with Metal Surfaces
Metal Metal

≥30 (1.2) ≥50 (2)

Square Transceiver

Rectangular Transceiver

Transceiver Field Maps The transceiver has a three-dimensional RF field that emanates from its sensing surface. The
field consists of a main center lobe and a secondary side lobe.

The RF tags must enter the RF field once, stay long enough to complete the read and write
cycles, and then to leave the field smoothly and efficiently.

Ideally, the RFID tag must pass through the widest section of the main lobe. This arrangement
maximizes the time that the transceiver has for reading and writing. Avoid the top of the field,
and avoid the side lobes.

The preferred direction of travel is for the tag to pass across the RFID sensor surface. The tag
can also approach the sensor surface directly and then move away directly backwards or to
the side.

Figure 15 on page 43 shows the field map of the 65 x 65 mm (2.6 x 2.6 in.) transceiver.

42 Rockwell Automation Publication 56RF-UM001E-EN-P - October 2022

 Chapter 5 Mechanical Installation

Figure 15 - 65 x 65 mm (2.6 x 2.6 in.) Transceiver

RFID Tag

Alte1rnate
Direction of Travel
100

OFF OFF

Preferred
Direction of
RFID Tag Travel Ideal Acceptable
50 Sensing Sensing
ON

Sensing Distance [mm]

Range Range

Side Lobe Side Lobe

OFF
0
-80 -40 0 40 80
Misalignment [mm]
Referenced for a 50 mm (2 in.) disk tag

The field map for the 80 x 90 mm (3.1 x 3.5 in.) transceiver, which is shown in Figure 16, is
similar.
Figure 16 - 80 x 90 mm (3.1 x 3.5 in.) Transceiver
RFID Tag

Alte1rnate
Direction of Travel

150
OFF OFF
Preferred
Direction of
RFID Tag Travel Ideal Acceptable
100 Sensing Sensing
ON Range Range
Sensing Distance [mm]

50
Side Lobe Side Lobe

OFF
0
-150 -100 -50 0 50 100 150
Misalignment [mm]
Referenced for a 50 mm (2 in.) disk tag

Rockwell Automation Publication 56RF-UM001E-EN-P - October 2022 43

Chapter 5 Mechanical Installation

Approximate Dimensions Figure 17 - Square/Rectangular Transceivers

12 46 (1.81) 94
5.4 (0.47) 40 (1.57) (3.7)
(0.21)
65
7.5 (0.3) (2.56)

30 40
(1.18) (1.57) 65 83
(2.56) (3.27)

73.5 (2.89)
106.5
(4.19)

40 40
(1.57) (1.57)
30
(1.18)
0.2
(0.01)
40 x 40 mm 80 x 90 mm
(1.6 x 1.6 in.) (3.1 x 3.5 in.)

Figure 18 - Cylindrical Transceivers

73 (2.9)
7
73 (2.9) (0.28)
7
63 (2.5)
(0.28)
63 (2.5)
12.2 35.8 (1.41)
12.2 (0.48)
(0.48) 35.8 (1.41)

16.6 dia 16.6 dia 28 28

(0.65) (0.65) (1.10) (1.10)
dia dia

Read/Write Module M12x1 M12x1

M18x1 Status LED M30x1.5
Status LED LED
M18 M30

44 Rockwell Automation Publication 56RF-UM001E-EN-P - October 2022

 Chapter 6

Add Your RFID Interface Block to an

RSLogix 5000 Program

Procedure 1. Open RSLogix 5000® software.

2. Click File>New.

3. Enter the new controller information.

4. Right-click the Ethernet port of the controller.

Rockwell Automation Publication 56RF-UM001E-EN-P - October 2022 45

Chapter 6 Add Your RFID Interface Block to an RSLogix 5000 Program

5. Click New Module.

6. Select the desired 56RF module and click OK.

46 Rockwell Automation Publication 56RF-UM001E-EN-P - October 2022

 Chapter 6 Add Your RFID Interface Block to an RSLogix 5000 Program

General Tab The General tab describes the device, its definition, and its IP address. Make the changes that
are shown Figure 19 and click Apply.
Figure 19 - General Tab

1. Enter a name for the module. In this example, the name is RFID_1. You can have multiple
modules, so be sure to give it a brief but descriptive name. The name that you assign to
the module appears in the Controller Organizer navigation pane. The name also appears
in the description of the tags, which are described later.
2. Enter a description of the module or its function.
3. The Data Format can be left as SINT (preferred) or changed to INT (for compatibility
with non-Rockwell Automation® RFID tags).
A SINT is a signed single-byte integer, which can represent numbers from
-255…255 in decimal format (-F…FF in hexadecimal format). An INT is a signed 2
byte integer, which can represent numbers from -65535…65535 in decimal format
(-FFFF…FFFF in hexadecimal format).
4. Set the MAC address for the module. In this example, the address is 192.168.1.115. The 115
reflects the address of the three rotary switches on the Bulletin 56RF interface block.

MAC Address
When the controller is offline, the MAC address can be set. You have three options.
• When a Private Network is used, click Private Network. Enter a value for the last octet
between 1…254. Be sure not to duplicate the address of an existing device. In the
following example, the address of the RFID block is 192.168.1.115.

• When multiple networks exist, you can elect to set the address to some other value.
When offline, simply click IP address and enter the desired address.

Rockwell Automation Publication 56RF-UM001E-EN-P - October 2022 47

Chapter 6 Add Your RFID Interface Block to an RSLogix 5000 Program

• Click Host Name and type in the name of the host. In the following example, the host
name is QPACK4.

Module Definition You do not need to change the default values. If necessary, changes can be made by clicking
Change.

You can change the Series, Revision, Electronic Keying, Connection, and Data Format. Click the
down arrow on the Data Format field and select SINT.

Click OK to accept the changes (or Cancel to retain the original settings). Click Help for more
info.

Connection Tab You do not need to change any settings on this tab.

Setting Description
Specify the number of milliseconds between requests for information from the
Requested Packet controller to the RFID block. The block can provide data on a shorter interval, but if no
Interval data is received, the controller asks the RFID block for a status update. Minimum
setting is 2. Maximum setting is 750.
When checked, the RFID block is not polled for information, and the controller ignores
Inhibit Module any information that is provided.
Major Fault on Controller
If Connection Fails While Check this box if a connection failure is considered a major fault.
In Run Mode
Use Unicast Connection Unicast connections are point-to-point connections. Multicast connections are
over EtherNet/IP considered one-to-many. Unicast reduces the amount of network bandwidth used.
Module Fault Fault messages appear in this box.

48 Rockwell Automation Publication 56RF-UM001E-EN-P - October 2022

 Chapter 6 Add Your RFID Interface Block to an RSLogix 5000 Program

Module Info Tab The Module Info tab contains read-only data that is populated when the controller goes online
(a program is downloaded to or uploaded from the controller).

In the left panel, the Add-on Profile (AOP) shows the vendor, product type, product code.
Revision level, serial number, and product name.

In the right panel, the AOP shows the fault status, internal state (Run mode), and whether the
file is owned and Module Identity.

The Refresh and Reset Module buttons are active when the controller is online.
• Refresh
Click to refresh the data in the window.
• Reset Module
Click with care as it disconnects the module momentarily and control is interrupted.
The following warning window appears.

Click Yes or No as needed. Click Help for further information.

Rockwell Automation Publication 56RF-UM001E-EN-P - October 2022 49

Chapter 6 Add Your RFID Interface Block to an RSLogix 5000 Program

Internet Protocol Tab For the purposes of this user manual, you are expected to use a Private Address, that is, an
address of 192.168.1.xxx. This window is automatically populated with the data.

Port Configuration Tab

Changes to the fields on the Port Configuration tab are not required for the Quick Start
process. These fields only become active when the controller is online.

The number of ports that are shown in this window varies depending on the block used. There
are either one or two ports.

The following window shows two ports. Port 1 is active, while Port 2 is inactive.

50 Rockwell Automation Publication 56RF-UM001E-EN-P - October 2022

 Chapter 6 Add Your RFID Interface Block to an RSLogix 5000 Program

Click the ellipsis (…) under the Port Diagnostics. The following window appears, which shows
the communication that takes place between the controller and the transceiver that is
connected to the port.

Rockwell Automation Publication 56RF-UM001E-EN-P - October 2022 51

Chapter 6 Add Your RFID Interface Block to an RSLogix 5000 Program

Notes:

52 Rockwell Automation Publication 56RF-UM001E-EN-P - October 2022

 Chapter 7

RSLogix 5000 Controller Tags

During the module installation, the RFID_1 tags are automatically loaded as controller tags,
which makes the tags available to all programs.

In the Controller Organizer, click the Controller Tags.

Three categories of tags appear. The tag name is composed of the module name followed by:
• “:C” for Configuration
• “:I” for Input
• “:O” for Output.

Rockwell Automation Publication 56RF-UM001E-EN-P - October 2022 53

Chapter 7 RSLogix 5000 Controller Tags

Configuration Image Table Expand the RFID_1:C by clicking “+” to show the configuration image table, which has the
following tags:
and Tags

Tag Description
The communication rate for Channel 0 from the RFID block to the RFID transceiver is
Ch0BaudRate stored in this tag. Allowable communication rates are 9600, 19200, 38400, and 115200.
The default value is 115200.
The communication rate for Channel 1 from the RFID block to the RFID transceiver is
Ch1BaudRate stored in this tag. Allowable communication rates are 9600, 19200, 38400, and 115200.
The default value is 115200.
The Configuration Revision Number is used internally with RSLogix™ for configuration
CRN information. You do not need to use this tag.
The Pt00FaultMode is used with FaultValue to configure the state of output 0 when a
communications fault occurs. A value of 0 means that, if there is a communications
Pt00FaultMode fault, the value in FaultValue is used (OFF or ON). A value of 1 means that the last state is
held. By default this value is 0.
The Pt00FaultValue is used with FaultMode to configure the state of output 0 when a
Pt00FaultValue communications fault occurs. A value of 0 is OFF; a value of 1 is ON. By default the value
is 0.
The Pt00FilterOffOn is used to determine the OFF- to ON-delay time for input point 0
before the interface considers the input point ON or True. A value of 0 indicates that
Pt00FilterOffOn there is no delay from an OFF condition to an ON condition; the only delay would be a
hardware delay. A value >0 would delay the input turning ON by the configured value in
milliseconds. By default this value is 0.
The Pt00FilterOnOff is used to determine the ON- to OFF-delay time for input point 0
before the interface considers the input point OFF or False. A value of 0 indicates that
Pt00FilterOnOff there is no delay from an ON to OFF condition; the only delay would be a hardware delay.
A value >0 would delay the input turning OFF by the configured value in milliseconds. By
default this value is 0.
The Pt00NoLoadEn is used to enable or disable No Load diagnostic detection for output
Pt00NoLoadEn 0. A value of 1 means that No Load diagnostic detection is enabled; a value of 0 means
that No Load diagnostic detection is disabled. By default this value is 0.
The Pt00OpenWireEn is used to enable or disable the open wire detection for input
Pt00OpenWireEn point 0. A value of 1 means that open wire detection is enabled; a value of 0 means that
open wire detection is disabled. By default this value is 1.
Pt00OutputShortCircuitE The Pt00OutputShortCircuitEn is used to enable or disable the short circuit detection
for output point 0. A value of 1 means that short circuit detection is enabled; a value of
n 0 means that short circuit detection is disabled. By default this value is 0.
The Pt00ProgMode is used with ProgValue to configure the state of output 0 when the
controller is in Program mode. A value of 0 means that the ProgValue (OFF or ON) is
Pt00ProgMode used when the controller is in Program mode. A value of 1 means that the last state is
held. By default this value is 0.
The Pt00ProgValue is used with ProgMode to configure the state of output 0 when the
Pt00ProgValue controller is in Program mode. A value of 0 is OFF; a value of 1 is ON. By default this
value is 0.
The Pt00ShortCircuitEn is used to enable or disable the short circuit detection for input
Pt00ShortCircuitEn point 0. A value of 1 means that short circuit detection is enabled; a value of 0 means
that short circuit detection is disabled. By default this value is 0.

54 Rockwell Automation Publication 56RF-UM001E-EN-P - October 2022

 Chapter 7 RSLogix 5000 Controller Tags

Input Image Table and Tags Expand the RFID_1:I by clicking “+” to show the input image table, which has the following tags:

Tag Description
The AuxPwrFault bit indicates if there is no auxiliary power detected. A value of 0
AuxPwrFault indicates no fault; a value of 1 indicates a fault condition.
The Block Fault bit indicates if any of the RFID channels or input/output points is in a
fault condition. A value of 0 indicates that the RFID channels and input/output points
BlockFault are functioning correctly. A value of 1 indicates one or more of the RFID channels and/or
input/output points are in a fault condition. Individual RFID channel fault bits are
contained within each associated Channel[x] input word.
Channel See Input Channel Tags on page 56.
The Fault word is a 4-byte value that stores the connection status between the
Fault interface and the controller. A value of 0 indicates that a connection has been
established; a value of -1 indicates no connections.
The Module status is a 4-byte value that contains the overall status of the module. A
value of 0 or 1 indicates that the module is functioning with no faults; a value greater
ModuleStatus than 1 indicates that a fault condition exists. The ModuleStatus word varies slightly
based on the configured unit.
The Pt00Data bit indicates if the status of input point 0. A value of 0 indicates open; a
Pt00Data value of 1 indicates closed.
The Pt00InputFault bit indicates if the input point 0 has a fault condition. Input faults
Pt00InputFault would be Open Wire and/or Short Circuit. A value of 0 indicates no fault condition; a
value of 1 indicates a fault condition.
The Pt00InputShortCircuit bit indicates if the input point 0 has a short condition. A
Pt00InputShortCircuit value of 0 indicates no fault; a value of 1 indicates a fault condition. Short circuit
detection can be enabled or disabled during configuration.
The Pt00NoLoad bit indicates if the output point 0 has a no load condition; No load
detection only occurs when the output point is OFF. A value of 0 indicates no fault; a
Pt00NoLoad value of 1 indicates a fault condition. No load detection can be enabled or disabled
during configuration.
The Pt00OpenWire bit indicates if the input point 1 has an open wire condition. A value
Pt00OpenWire of 0 indicates no fault; a value of 1 indicates a fault condition. Open wire detection can
be enabled or disabled during configuration.
The Pt00OutputFault bit indicates if the output point 0 has a fault condition. Output
Pt00OutputFault faults would be No Load and/or Short Circuit. A value of 0 indicates no fault; a value of 1
indicates a fault condition.
The Pt00OutputShortCircuit bit indicates if the output point 0 has a short condition. A
value of 0 indicates no fault; a value of 1 indicates a fault condition; output short-circuit
Pt00OutputShortCircuit detection only occurs when the output is ON. Short circuit detection can be enabled or
disabled during configuration.
The Pt00Readback bit indicates the status of the output point Pt00Data. If the output
Pt00Readback bit Pt00Data is 1, indicating that the output has been commanded to turn ON, then when
the output point turns ON Pt00Readback contains the value of 1.
The Run bit indicates if the block is in run or program mode. A value of 1 indicates that
Run the block is in run mode; a value of 0 indicates that the block is in program mode.

Rockwell Automation Publication 56RF-UM001E-EN-P - October 2022 55

Chapter 7 RSLogix 5000 Controller Tags

Input Channel Tags Expand the RFID_1:Channel by clicking “+” to show that two channels exist (Channel[0] and
Channel[1]). Expand the RFID_1:Channel[0] by clicking “+”. Each channel has the following tags:

Tag Description
The channel Busy bit indicates the status of an RFID channel. A value of 0 indicates that
Busy the RFID channel is not executing a command. A value of 1 indicates that a command is
in the process of executing on that channel.
The channel ChError is a 1-byte word that contains the last error code for that channel.
ChError A value of 0 indicates no error, a value >0 indicates some error. See
Error Codes for RFID Interface Block on page 129 for a list of the error codes.
The channel command word is a 2-byte value that stores the last command that the
Command channel received; at power-up this value must be 0. The allowable commands are listed
in Table 23 on page 57.
The channel ContReadMode bit indicates the status of Continuous Read Mode for an
RFID channel. A value of 0 indicates that the RFID channel is not in continuous read
ContReadMode mode; a value of 1 indicates that the RFID channel is in continuous read mode. While in
Continuous Read Mode, the interface ignores all other commands except a Stop
Continuous Read.
The channel counter word is a 2-byte value that increments its value by 1 after the
Counter interface has completed execution of a command. This value rolls over to 0 after it
counts to 65535 and starts again; at power-up this value must be 0.
Depending on the Data Format, the channel Data word is an array of either 2-byte
values or an array of 1-byte values that total 160 bytes in length. This array is used to
store information that is returned from the RFID interface. Upon completion a
Data command, reply data is deposited in this array and the length of the reply (in 16-bit word
increments) is placed within the associated length field; at power-up this value must be
0.
The channel fault bit indicates the fault status of the RFID channel. A value of 0
Fault indicates that the channel is operating normally; a value of 1 indicates that the channel
has faulted.
The channel length word is a 2-byte value that indicates the data length for specific
Length commands. Upon completion of a command, this word is populated with the number of
16-bit words that are returned to the data field; at power-up this value must be 0.
The channel reset bit indicates the reset status of the RFID channel. A value of 0
Reset indicates that the channel is not in reset; a value of 1 indicates that the channel has
completed a reset.
The channel ResetInProg bit indicates the status of an RFID channel reset. A value of 0
ResetInProgress indicates that the RFID channel is not currently undergoing a reset; a value of 1
indicates a reset in progress on that channel.
The channel TagPresent bit indicates the status of a tag at the RFID channel. A value of
TagPresent 0 indicates that there is not tag present at the transceiver; a value of 1 indicates one or
more tags have been detected at the transceiver.

56 Rockwell Automation Publication 56RF-UM001E-EN-P - October 2022

 Chapter 7 RSLogix 5000 Controller Tags

Table 23 - Allowable Commands

Value Command Description
1 Read Single Block Reads one block of user data.
2 Read Multiple Blocks Reads multiple blocks of user data from a tag.
3 Multi-tag Block Read Reads information from up to four tags.
4 Read Byte Reads bytes of user data from a tag.
5 Start Continuous Read Initiates continuous read mode.
6 Stop Continuous Read Stops continuous read mode.
Allow you to set the best time to start reading in continuous read
8 Teach Continuous Read mode automatically.
10 Write SingleBlock Writes one block of user data.
11 Write Multiple Blocks Writes multiple blocks of user data to a FRAM tag.
12 Multi-tag Block Write Writes multiple blocks of user data to up to four tags.
13 Clear Multiple Bytes Clears multiple bytes of user data in a tag.
14 Write Byte Writes bytes of data to a tag.
Counts the number of blocks in the field (up to four) and returns
20 Inventory the UUID of the first tag in the field.
31 Read Transceiver Settings Read communication rate, Device ID,Retry Time, and Gain.
33 Get Version Information Retrieves the firmware revision from the transceiver.
Gets Info Flags,UUID, DSFID, AFI,Memory Size, and IC Reference
34 Get System Information from Tag.
40 Lock Block Locks blocks of memory.
41 Write AFI Write the AFI byte to the tag.
42 Lock AFI Locks the AFI byte from future changes.
43 Write DSFID Writes the DSFID byte to the tag.
44 Lock DSFID Locks the DSFID byte from future changes.
45 Get Multiple Block Security Status Retrieves that security status of multiple blocks within a tag.

Output Image Table and Expand the RFID_1:O by clicking “+” to show the output image table, which has the following
tags:
Tags

Tag Description
Channel See Output Channel Tags on page 58.
The Pt00Data bit is used to turn output point 0 either ON or OFF. A value of 0 is used to
Pt00Data turn OFF the output point; a value of 1 is used to turn ON the output point.
The Run bit is used to place the RFID block into run or program mode. A value of 0 is
used for program mode; a value of 1 is used for run mode. When in program mode, the
Run interface maintains the connection to the processor but does not execute commands.
The discrete output point follows the mode of the processor and the Run bit, with the
Run bit overriding.

Rockwell Automation Publication 56RF-UM001E-EN-P - October 2022 57

Chapter 7 RSLogix 5000 Controller Tags

Output Channel Tags Expand the RFID_1:Channel by clicking “+” to show that two channels exist (Channel[0] and
Channel[1]). Expand the RFID_1:Channel[0] by clicking “+”. Each channel has the following tags:

Tag Description
The channel Address word is a 2-byte value that contains the address or block value
Address within the RFID tag that the command executes on.
The channel BlockSize word is a 2-byte value that stores the expected Block Size for the
BlockSize tag. Valid values are 0 bytes, 4 bytes, or 8 bytes per block. A value of 0 defaults to a
Block Size of 4 bytes per block.
The channel Command word is a 2-byte value that stores the next command for the
interface to process. The RFID interface executes the command once when this value
Command changes. If a command must be repeated, then set the value to zero first and then
change it again to the desired command. Use a MOV or COP instruction to store the
command value in this tag. The allowable commands are listed in Table 24 on page 59.
Depending on the Data Format, the channel Data word is either an array of 2-byte
values or an array of 1-byte values that total 112 bytes in length per channel. This array
is used to store information that is directed to the RFID interface. Some commands,
Data such as reading, do not require the use of this data field. Writing to tags uses this
information with the length field to inform the RFID interface what values it must write.
The size of this word allows the writing of up to 28 blocks of data to a tag at a time, with
each block being 4 bytes in length.
The channel length word is a 2-byte value that indicates the data length for specific
Length commands. Upon completion of a command, this word is populated with the number of
16-bit words that are returned to the data field; at power-up this value must be 0.
The channel reset bit is used to command an RFID channel reset. A value of 0 indicates
Reset that the channel is not being commanded to reset; a value of 1 indicates a request to
reset the channel.
This value determines how long the interface waits for a command response from the
Timeout (1) transceiver before indicating a message timeout. The default value is 0, which sets the
timeout at 750 ms. You can enter a timeout value in milliseconds.
The channel UID word is an 8-byte value that contains the UUID information for specific
commands that allows the command to be targeted to a specific tag in the field. Under
UIDHi normal circumstances, this value is 0, which tells the RFID interface to perform an
action regardless of what tag it is. Any value other than 0 attempts to direct the
command to that specific tag. The UIDHi value contains bytes 0…1 and 6…7 of the UID.
UIDLow The UIDLow value contains bytes 2…5 of the UID.
(1) A low timeout value can cause command failures by timing out before the command would otherwise have successfully
completed.

58 Rockwell Automation Publication 56RF-UM001E-EN-P - October 2022

 Chapter 7 RSLogix 5000 Controller Tags

Table 24 - Allowable Commands

Value Command Description
1 Read Single Block Reads one block of user data.
2 Read Multiple Blocks Reads multiple blocks of user data from a tag.
3 Multi-tag Block Read Reads information from up to four tags.
4 Read Byte Reads bytes of user data from a tag.
5 Start Continuous Read Initiates continuous read mode
6 Stop Continuous Read Stops continuous read mode
Allows you to set the best time to start reading in continuous
8 Teach Continuous Read read mode automatically.
10 Write SingleBlock Writes one block of user data.
11 Write Multiple Blocks Writes multiple blocks of user data to a FRAM tag
12 Multi-tag Block Write Writes multiple blocks of user data to up to four tags.
13 Clear Multiple Bytes Clears multiple bytes of user data in a tag.
14 Write Byte Writes bytes of data to a tag.
Counts the number of blocks in the field (up to four) and returns
20 Inventory the UUID of the first tag in the field.
31 Read Transceiver Settings Read communication rate, Device ID and Retry Time.
33 Get Version Information Retrieves the firmware revision from the transceiver.
Gets Info Flags,UUID, DSFID, AFI,Memory Size, and IC Reference
34 Get System Information from Tag
41 Write AFI Write the AFI byte to the tag
42 Lock AFI Locks the AFI byte from future changes.
43 Write DSFID Writes the DSFID byte to the tag.
44 Lock DSFID Locks the DSFID byte from future changes.
45 Get Multiple Block Security Status Retrieves that security status of multiple blocks within a tag.

Rockwell Automation Publication 56RF-UM001E-EN-P - October 2022 59

Chapter 7 RSLogix 5000 Controller Tags

Notes:

60 Rockwell Automation Publication 56RF-UM001E-EN-P - October 2022

 Chapter 8

Commands Summary

RFID Commands This section provides a summary of the commands that the RFID transceiver supports. Detail
of the commands can be found in RSLogix 5000 Code Examples on page 73. This guide
assumes familiarity with RSLogix 5000®. The *.ACD file must already be downloaded into the
PLC and working properly.

Table 25 assumes the following:

• You have configured the RSLogix 5000 Add-on Profile (AOP) with Data Format set to
SINT.
• The RFID tag has blocks that are only 4 bytes each.
• The Universally Unique Identifier (UUID) is set to zero (unless specified).
A UUID can be specified in xx.O.Channel[0].UIDLow and xx.O.Channel[0].UIDHi for
most commands to operate on a specific tag. If xx.O.Channel[0].UIDLow and
xx.O.Channel[0].UIDHi are set to 0, the command operates on the first tag in the
transceiver field. All other Output values must be set to 0 where not specified.

Table 25 - Commands
Output Input
Command Description xx.O.Channel[0] xx.I.Channel[0]
Option Flag 0 Command = 20 Data[0] = # of tags
Returns number of tags in field Length = 0 Data[2…9, 10…17, 18…25, 26…33] = UUID of up
Returns Universally Unique Identifier (UUID) of first tag in field Data[0] = 0 to four tags
Inventory Option Flag 1 Data[0] = # of tags
Command = 20
Returns number of tags in field Data[2, 12, 22, 32] = AFI of up to 4 tags
Returns Application Family Identifier (AFI) of first tag in field Length =1 Data[4…11, 13…21, 24…31, 34…41] = UUID of up
Data[0] =1
Returns Universally Unique Identifier (UUID) of first tag in field to four tags
Option Flag 0 Command = 1 Data[0…3] = User data (4 bytes)
Reads one block of user data from a tag Data[0] = 0
Read Single
Block Option Flag 1 Command = 1 Data[0…3] = User data (4 bytes)
Reads one block of user data from a tag Data[0] = 1 Data[4] = Security status
Returns security status of the block
Command = 10
Write Single Length =Block size
Writes one block of user data to a tag All data bytes are zero
Block BlockSize = Block size
Data[0…1] = User data (4 bytes)
Command = 40
Lock Block Locks one block of user data, preventing writing UIDLow = UIDLow All data bytes are zero
UIDHi = UIDHi
Command = 2
Option Flag 0 Data[0…3] = Block x
Length = Number of blocks
Reads multiple blocks of user data from a tag Data[4…7] = Block x+1
Data[0] = 0
Read Multiple
Blocks Data[0…3] = Block x
Option Flag 1 Command = 2 Data[4] = Security status of block x
Reads multiple blocks of user data from a tag Length = Number of blocks Data[6…9] = Block x+1
Returns security status of the blocks Data[0] = 1 Data[10] = Security status of block x+1
Command = 11
Write Multiple Length = Number of bytes (multiple of 8) All data bytes are zero
Writes multiple blocks of user data to an FRAM tag
Blocks BlockSize = Block size
Data[0…3] = User data (8 bytes)

Rockwell Automation Publication 56RF-UM001E-EN-P - October 2022 61

Chapter 8 Commands Summary

Table 25 - Commands (Continued)

Output Input
Command Description xx.O.Channel[0] xx.I.Channel[0]
Writes 1 byte of information into the AFI area that is contained Length = 1 = 41
Command
Write AFI All data bytes are zero
within block -2 Data[0] = 00xx
Command = 42
Locks the 1 byte of information for the AFI area, preventing it UIDLow = UIDLow
Lock AFI All data bytes are zero
from being modified UIDHi = UIDHi
Command = 43
Write DSFID Writes 1 byte of information in the DSFID area Length = 1 All data bytes are zero
Data[0] = 00xx
Command = 44
Locks the 1 byte of information for the DSFID area, preventing UIDLow = UIDLow
Lock DSFID All data bytes are zero
it from being modified UIDHi = UIDHi
Data[0] = 00xx
Returns the following system information of the tag: Data[0] = Info_Flag
Info_Flags Data[2] = DSFID
UUID Data[4] = AFI
Get System DSFID Command = 34 Data[6…13] = UUID
Information AFI Data[14] = Max Block Number Data[15] = Max
Memory Size (Max Block Number +1 * Max Byte per Block +1) Byte Number in Block
IC Reference Data[16] = IC Ref
Get Multiple Data[0…7] = UUID
Command = 45
Block Security Retrieves the security status of multiple blocks within a tag Data[8] = Security status of block x
Length = Number of blocks
Status Data[10] = Security status of block x+1
Command = 4
Option Flag 0 Address = Starting byte Data[0…] = User data
Reads bytes of user data from a tag Length = Number of bytes to read
Data[0] = 0
Read Byte
Command = 4
Option Flag 1 Address = Starting byte Data[0…7] = UUID
Reads the UUID from a tag Length = Number of bytes to read Data[8…] = User data
Reads bytes of user data from a tag Data[0] = 1
Command = 14
Address = Starting byte
Write Byte Writes bytes of user data to a tag Data[0…7] = UUID
Length = Number of bytes to write
Data[0] = Start of User data
Command = 13
Clear Multiple Address = Starting byte
Clears multiple bytes of user data in a tag All data bytes are the cleared byte value
Bytes Length = Number of bytes to clear
Data[0] = Cleared byte value
Reads the following information from up to four tags in the Data[0] = Number of tags
Command = 3
field: Data[2…9] = UUID of first tag
Multi-tag Block Address = First block to read
Number of tags Data[10…*] = User data of first tag
Read Length = Number of blocks to read for
UUID Data[*…*] = UUID of second tag
each tag
Multiple blocks of user data Data[*…*] = User data of second tag
Command = 12 Data[0] = Number of tags
Writes multiple blocks of user data to up to four tags in the Length = Number of bytes to write to Data[2…9] = UUID of first tag
Multi-tag Block field each tag Data[10…17] = UUID of second tag
Write Returns number of tags in the field BlockSize = Block size Data[18…25] = UUID of third tag
Retrieves UUID of tags Data[0] = Block x Data[26…33] = UUID of fourth tag
Data[4…7] = Block x+1
Retrieves the following information from the transceiver: Data[0…1] = Device ID
Read Transceiver Communication rate Data[2…5] = Communication rate
Command = 31
Settings Device ID Data[6…7] = Retry setting
Retry time Data[8…9] = Gain
Get Version Retrieves the firmware revision from the transceiver Command = 33 Data = firmware revision
Information

62 Rockwell Automation Publication 56RF-UM001E-EN-P - October 2022

 Chapter 9

Add-On Instruction

Introduction This chapter explains the proposed 56RF system with an Add-On Instruction (AOI) library
applied that controls the 56RF transceiver module by Neo serial IO (Cat. No. 5069-SERIAL or
5094-SERIAL).
Figure 20 - Proposed 56RF System
CompactLogix™ 5380 56RF Transceiver
Controller 5069-SERIAL

Personal Computer
Studio 5000® RS-485

120 Ω
AOI for
56RF
Common

+ -
24V DC
Power Supply

This AOI is designed to work with the following configuration, other configurations are not
considered and tested:
• Studio 5000 Logix Designer® version 28 or later
• 5069-SERIAL on Slot1 of backplane, also use CH0 as RS-485 port
• 56RF tags

AOI code and Sample application code are considered user modified. The original AOI designer
does not take responsibility for the application code of the final customer.

Supported Modules High-frequency Transceivers

Table 26 - Supported High-frequency Transceiver

Cat. No. (1) Type

56RF-TR-8090 Rectangular 80 x 90 mm (3.1 x 3.5 in.) transceiver
56RF-TR-4040 Square 40 x 40 mm (1.6 x 1.6 in.) transceiver
56RF-TR-M18 M18 cylindrical transceiver
56RF-TR-M30 M30 cylindrical transceiver
(1) See Approximate Dimensions on page 44 for transceiver dimensions.

Rockwell Automation Publication 56RF-UM001E-EN-P - October 2022 63

Chapter 9 Add-On Instruction

High-frequency Tags
Table 27 - Supported High-frequency Tags
Block Size and Security Feature
Cat. No. CHIP Memory Size Number (Privacy Mode)
56RF-TG-20 ICODE-SLI (SL2ICS20) 128 Bytes 4 Bytes x32 Yes
56RF-TG-30 ICODE-SLI 128 Bytes 4 Bytes x32 Yes
56RF-TG-35HIR ICODE-SLI 128 Bytes 4 Bytes x32 Yes
56RF-TG-50 ICODE-SLI 128 Bytes 4 Bytes x32 Yes
56RF-TG-50MOM ICODE-SLI 128 Bytes 4 Bytes x32 Yes
56RF-TG-50HT ICODE-SL2 128 Bytes 4 Bytes x32 Yes
56RF-TG-20-2KB FRAM (MB89R118C) 2k Bytes 8 Bytes x256 No
56RF-TG-30-2KB FRAM (MB89R118C) 2k Bytes 8 Bytes x256 No
56RF-TG-50-2KB FRAM (MB89R118C) 2k Bytes 8 Bytes x256 No
56RF-TG-50-2KBMOM FRAM (MB89R118C) 2k Bytes 8 Bytes x256 No
9k Byte:
56RF-TG-30-8KB FRAM (MB89R112) User - 8k Bytes 32 Bytes x256 (User) No
System - 1k Bytes
56RF-TG-5050 ICODE-SLIx — — Yes
56RF-TG-5486 ICODE-SLI — — Yes
56RF-TG-5486SC ICODE-SLI — — Yes

IMPORTANT ISO15693 can support up to 8k Byte tag.

AOI Specification Figure 21 - AOI Interface

Add-On Profile (AOI)
Local Parameter

In / Out

NEO-Serial AOI
IO-Tag Interface-Tag

User

AOI Input Tags

Table 28 - RF_AOI_INTERFACE:C
Name Data Type Default Value Description
The communication rate for Channel 0 from the RFID block to
the RFID transceiver is stored in this tag. Allowable
Ch0BaudRate DINT — communication rates are 9600, 19200, 38400, and 115200.
The default value is 115200.
The communication rate for Channel 1 from the RFID block to the
RFID transceiver is stored in this tag. Allowable communication
Ch1BaudRate DINT — rates are 9600, 19200, 38400, and 115200.
The default value is 115200.

64 Rockwell Automation Publication 56RF-UM001E-EN-P - October 2022

 Chapter 9 Add-On Instruction

Table 29 - RF_AOI_INTERFACE:I
Name Data Type Default Value Description
AB:56RF_IN_
Channel0 — See Table 30 on page 65.
AOI_Struct_In:I:0
AB:56RF_IN_
Channel1 — See Table 30 on page 65.
AOI_Struct_In:I:0

Table 30 - AB:56RF_IN_AOI_Struct_In:I:0
Name Data Type Default Value Description
Channel[0]: AB:56RF_IN_AOI_Struct_In:I:0
The channel Busy bit indicates the status of an RFID channel.
A value of 0 indicates that the RFID channel is not executing a
Busy BOOL 0 command. A value of 1 indicates that a command is in the
process of executing on that channel.
The channel ChError is a 1-byte word that contains the last
error code for that channel. A value of 0 indicates no error, a
ChError SINT 0 value >0 indicates some error. See Error Codes for RFID
Interface Block on page 129 for a list of the error codes.
The channel command word is a 2-byte value that stores the
last command that the channel received; at powerup this
Command INT 0 value must be 0. The allowable commands are listed in
Table 36 on page 68.
The channel ContReadMode bit indicates the status of
Continuous Read Mode for an RFID channel. A value of 0
indicates that the RFID channel is not in continuous read
ContReadMode BOOL 0 mode; a value of 1 indicates that the RFID channel is in
continuous read mode. While in Continuous Read Mode, the
interface ignores all other commands except a Stop
Continuous Read.
The channel counter word is a 2-byte value that increments
its value by 1 after the interface has completed execution of a
Counter INT 0 command. This value rolls over to 0 after it counts to 65535
and starts again; at powerup this value must be 0.
Depending on the Data Format, the channel Data word is an
array of either 2-byte values or an array of 1-byte values that
total 160 bytes in length. This array is used to store
information that is returned from the RFID interface. Upon
Data SINT[160] 0 completion a command, reply data is deposited in this array
and the length of the reply (in 16-bit word increments) is
placed within the associated length field; at powerup this
value must be 0.
The channel fault bit indicates the fault status of the RFID
channel. A value of 0 indicates that the channel is operating
Fault BOOL 0 normally; a value of 1 indicates that the channel does not
detect a 56RF transceiver via the AOI requested command.
The channel length word is a 2-byte value that indicates the
data length for specific commands. Upon completion of a
Length INT 0 command, this word is populated with the number of 16-bit
words that are returned to the data field; at powerup this
value must be 0.
The channel reset bit indicates the reset status of the RFID
channel. A value of 0 indicates that the channel is not in reset;
Reset BOOL 0 a value of 1 indicates that the channel has completed a reset.
If an unexpected error occurs, you can recover by setting the
reset bit to 1.
The channel ResetInProg bit indicates the status of an RFID
channel reset. A value of 0 indicates that the RFID channel is
ResetInProgress BOOL 0
not currently undergoing a reset; a value of 1 indicates a reset
in progress on that channel.
The channel TagPresent bit indicates the status of a tag at the
RFID channel. A value of 0 indicates that there is not tag
TagPresent BOOL 0 present at the transceiver; a value of 1 indicates one or more
tags have been detected at the transceiver. This tag is
updated after the AOI command is executed.

Rockwell Automation Publication 56RF-UM001E-EN-P - October 2022 65

Chapter 9 Add-On Instruction

Table 31 - Support tag value of AB:56RF_IN_AOI_Struct_In:I:0

Interface Block
Name Data Type AOI (56RF-IN-IPS12, 56RF-IN-IPD22, and
56RF-IN-IPD22A)
Channel[0]: AB:56RF_IN_AOI_Struct_In:I:0
Busy BOOL 0, 1 0, 1
ChError SINT 0, 3, 4, 5, 7, 16 0…15
1, 4, 10, 14, 20, 34, 41, 43, 99, 100
Command INT 1…6,8,10…14,20,31,33,34,40…45
(See Table 28 on page 64)
ContReadMode BOOL — 0, 1
Counter INT 0…65535 0…65535
Data SINT[160] 0…159 0…159
Fault BOOL 0, 1 0, 1
Length INT 0…255 0…255
Reset BOOL 0, 1 0, 1
ResetInProgress BOOL 0, 1 0, 1
TagPresent BOOL 0, 1 0, 1

AOI Output Tags

Table 32 - RF_AOI_INTERFACE:O
Name Data Type Default Value Description
Channel0 AB:56RF_IN_AOI_Struct_Out:O:0 — See Table 33.
Channel1 AB:56RF_IN_AOI_Struct_Out:O:0 — See Table 33.
Set this bit to 1 before activating the AOI
Run BOOL 0 command.

Table 33 - AB:56RF_IN_AOI_Struct_Out:O:0
Name Data Type Default Value Description
Channel[0]: AB:56RF_IN_AOI_Struct_Out:O:0
The channel Address word is a 2-byte value that contains the
Address INT 0 address or block value within the RFID tag that the command
executes on.
The channel BlockSize word is a 2-byte value that stores the
expected Block Size for the tag. Valid values are 0 bytes, 4 bytes,
or 8 bytes per block. A value of 0 defaults to a Block Size of 4
bytes per block. When executing WriteSingleBlock, this setting is
BlockSize INT 0
invalid and the target tag block size is reflected automatically
after the WriteSingleBlock command is completed because AOI
automatically commands ReadSingleBlock to get BlockSize
information from the target tag.
The channel Command word is a 2-byte value that stores the
next command for the interface to process. The AOI executes
the command once when this value changes, and this value is
Command INT 0 cleared to 0 after completing the command. If a command must
be repeated, then set the value to the desired command after
waiting 0 clear. The allowable commands are listed in Table 36
on page 68.
Depending on the Data Format, the channel Data word is either
an array of 2-byte values or an array of 1-byte values that total
112 bytes in length per channel. This array is used to store
information that is directed to the RFID interface. Some
Data SINT[112] 0 commands, such as reading, do not require the use of this data
field. Writing to tags uses this information with the length field
to inform the RFID interface what values it must write. The size
of this word allows the writing of up to 28 blocks of data to a tag
at a time, with each block being 4 bytes in length.
The channel length word is a 2-byte value that indicates the
data length for specific commands. Upon completion of a
Length INT 0 command, this word is populated with the number of 16-bit
words that are returned to the data field; at powerup this value
must be 0.

66 Rockwell Automation Publication 56RF-UM001E-EN-P - October 2022

 Chapter 9 Add-On Instruction

Table 33 - AB:56RF_IN_AOI_Struct_Out:O:0 (Continued)

Name Data Type Default Value Description
The channel reset bit is used to command an RFID channel
reset. A value of 0 indicates that the channel is not being
Reset BOOL 0 commanded to reset; a value of 1 indicates a request to reset
the channel.
This value determines how long the interface waits for a
command response from the transceiver before indicating a
Timeout INT 0 message timeout. The default value is 0, which sets the timeout
at 750 ms. You can enter a timeout value in milliseconds.
The channel UID word is an 8-byte value that contains the UUID
information for specific commands that allows the command to
be targeted to a specific tag in the field. Under normal
UIDHi DINT 0 circumstances, this value is 0, which tells the RFID interface to
perform an action regardless of what tag it is. Any value other
than 0 attempts to direct the command to that specific tag. The
UIDHi value contains bytes 4…7 of the UID.
UIDLow DINT 0 The UIDLow value contains bytes 0…3 of the UID.

Table 34 - Support tag value of AB:56RF_IN_AOI_Struct_Out:O:0

Interface Block
Name Data Type AOI (56RF-IN-IPS12, 56RF-IN-IPD22, and
56RF-IN-IPD22A)
Channel[0]: AB:56RF_IN_AOI_Struct_Out:O:0
Address INT 0…32767 0…32767
BlockSize INT 0, 4, 8, 32 0, 4, 8
Command INT 1, 4, 10, 14, 20, 34, 41, 43, 99, 100 1…6, 8, 10…14, 20, 31, 33, 34, 40…45
Data SINT[112] 0…111 0…111
Length INT 0…255 0…255
Reset BOOL 0, 1 0, 1
Timeout INT 0…750 0…750
UIDHi DINT 4…7 4…7
UIDLow DINT 0…3 0…3

AOI Interface Tags

Table 35 defined tags are necessary to use target AOI on your system. These tags are
automatically defined after importing the AOI library (L5X).
Table 35 - AOI Interface Tags on Controller Tags
Name Data Type Default Value Description
Controller Tags
AOI_Main AOI_Main — AOI library tag
Tag to store calculated checksum (FCS). Do not change
DATA_TOTAL DINT 0 value by user program.
Tag to store block size of RFID tag that the
ReadData_Length SINT 0 ReadSingleBlock command checks. Do not change value
by user program.
Tag that indicates completion of pre-processing
ReadSingleBlock_DN BOOL 0 command for WriteSingleBlock. Do not change value by
user program.
Tag that indicates step of AOI process. While executing
RUNG LINT 0 AOI, this tag is changed to other than 0. Do not change
value by user program.
Tag that indicates the wait time limit from command to
Time1 DINT 500 response. Do not change value by user program.
Tag that indicates the wait time from response to error
Time2 DINT 10 judgment. Do not change value by user program.

Rockwell Automation Publication 56RF-UM001E-EN-P - October 2022 67

Chapter 9 Add-On Instruction

Support Command
Table 36 - Support Command
ISO15693 Device Control Macro Command
Value Command Description AOI Support Command Command
1 Read Single Block Reads one block of user data. Yes Yes (Optional) — —
2 Read Multiple Blocks Reads multiple blocks of user data from a tag. — Yes (Optional) — —
3 Multi-tag Block Read Reads information from up to four tags. — — — Yes
4 Read Byte Reads bytes of user data from a tag. Yes — — Yes
5 Start Continuous Read Initiates continuous read mode — — — —
6 Stop Continuous Read Stops continuous read mode — — — —
Allows you to set the best time to start reading in
8 Teach Continuous Read — — — —
continuous read mode automatically.
10 Write Single Block Writes one block of user data. Yes Yes (Optional) — —
11 Write Multiple Blocks Writes multiple blocks of user data to a FRAM tag — Yes (Optional) — —
12 Multi-tag Block Write Writes multiple blocks of user data to up to four tags. — — — Yes
13 Clear Multiple Bytes Clears multiple bytes of user data in a tag. — — — Yes
14 Write Byte Writes bytes of data to a tag. Yes — — Yes
Counts the number of blocks in the field (up to four)
20 Inventory Yes Yes (Mandatory) — —
and returns the UUID of the first tag in the field.
31 Read Transceiver Settings Read communication rate, Device ID and Retry Time. — — Yes —
33 Get Version Information Retrieves the firmware revision from the transceiver. — — Yes —
Get System Information Gets Info Flags, UUID, DSFID, AFI, Memory Size, and IC
34 Yes Yes (Optional) — —
Reference from Tag
40 Lock Block Locks blocks of memory. — Yes (Optional) — —
41 Write AFI Write the AFI byte to the tag. Yes Yes (Optional) — —
42 Lock AFI Locks the AFI byte from future changes. — Yes (Optional) — —
43 Write DFSID Writes the DSFID byte to the tag. Yes Yes (Optional) — —
44 Lock DFSID Locks the DSFID byte from future changes. — Yes (Optional) — —
Get Multiple Block Security Retrieves that security status of multiple blocks within
45 — Yes (Optional) — —
Status a tag.
Change communication rate of internal serial
communication. The Write Setting (CMD: 0x64) and
Read Setting commands (CMD: 0x63) accomplish this
operation. When sending the Write Setting command,
setting any communication rate for
46 Change BaudRate Yes — Yes —
RF_AOI_INTERFACE_C.Ch0BaudRate. After changing to
the communication rate set in
RF_AOI_INTERFACE_C.Ch0BaudRate, it is necessary to
match the communication rate of 5069-SERIAL from
the properties.

Error Codes See Error Codes for RFID Interface Block on page 129 for more information.

68 Rockwell Automation Publication 56RF-UM001E-EN-P - October 2022

 Chapter 9 Add-On Instruction

Environment Setup 5069-SERIAL Configuration

IMPORTANT Configure the 5069-SERIAL as shown in this section.

If Importing the AOI before the following settings, the data type of the
tag that is required for this library is not defined and an error occurs.
Figure 22 - Module Setting (1 of 5)

Figure 23 - Module Setting (2 of 5)

Figure 24 - Module Setting (3 of 5)

Figure 25 - Module Setting (4/5)

Rockwell Automation Publication 56RF-UM001E-EN-P - October 2022 69

Chapter 9 Add-On Instruction

Figure 26 - Module Setting (5/5)

AOI Installation
Import the L5K file that includes the AOI into the setup environment via the Studio 5000
environment.
1. Right-click Main Task and select Import Program.

2. Select the L5X file and open.

70 Rockwell Automation Publication 56RF-UM001E-EN-P - October 2022

 Chapter 9 Add-On Instruction

3. Select OK on the Import Configuration screen.

IMPORTANT When importing, if Overwrite for Operation is selected, the existing

project is overwritten. Select Use Existing to keep the existing project.

If the import is successful, it is reflected in all Controller Tags, MainProgram, and Add-
On Instructions.

Important Notes ADDR Setting Restriction

Do not change the ADDR value from default value (0x01), because the M18 and M30 cylindrical
transceivers do not support an ADDR value change from default.

Rockwell Automation Publication 56RF-UM001E-EN-P - October 2022 71

Chapter 9 Add-On Instruction

Initial State of R/W Status Indicator

After the power cycle of the high-frequency transceiver, the R/W status indicator keeps
flashing red/green until the AOI command sends the first command. The AOI sends a command
to the high-frequency transceiver only when you explicitly demand it.

AOI Sample Code Precondition

Sample application program for this AOI designed to use with following condition
• 5069 CompactLogix as PLC Controller
• 5069-SERIAL CH0 as RS-485 interface, which is installed on Slot 1 of the 5069 Controller
backplane

72 Rockwell Automation Publication 56RF-UM001E-EN-P - October 2022

 Chapter 10

RSLogix 5000 Code Examples

This chapter contains examples of routines that run in the RSLogix 5000® program.

The examples are written for an RF transceiver that is connected to the “0” connector on the
RF interface block. A momentary switch is connected to the Digital Input connector. The
switch is used to enable the routine to allow you to repeat the routine easily.
In the examples, the RFID block is identified as “_RFID1”

Main Routine

A partial listing of the Main Routine is shown in the Example Command Routines - Overview.
The Main Routine sets the run bit. In program mode, the run bit is 0; and 1 for run mode. The
remaining blocks jump to the various subroutines to execute the commands. In Rung 1, the
momentary switch turns on Digital Output 0, which turns on a status indicator to confirm that
you have pressed the momentary switch.

Example Command Many of the example routines (not the Main Routine) use the same Ladder Logic. Rung 0 on
page 74…Rung 4 on page 75 explain the Ladder Logic.
Routines - Overview

Rockwell Automation Publication 56RF-UM001E-EN-P - October 2022 73

Chapter 10 RSLogix 5000 Code Examples

Rung 0
Rung 0 initiates the routine. A sensor or momentary switch, which is connected to the input
connection of the RFID interface block, senses that an object (with an RFID tag attached) is
approaching and enables the execution of the read routine. The sensor is the Examine If
Closed (XIC) bit labeled _RFID_1:I:Pt00Data. When the sensor detects the object, the instruction
latches ON.

Rung 1
Rung 1 initializes the output image table in preparation for command. Execution begins when
the transceiver is not already busy reading a tag and a tag is present in the RF field.

This XIC instruction is latched ON by the sensor in Rung 0.

RFID_1:I:Channel[0]Busy – This Examine If Open (XIO) instruction prevents the rung from
executing when the transceiver is busy executing a command.

RFID_1:I:Channel[0].TagPresent – This XIC instruction closes when a tag is present in the RF

field of the transceiver that is connected to Channel[0].

MOV variable to RFID_1:O:Channel[0]:variable – Moves data from a Controller tag to the output
image table variable.

MOV 0 to RFID_1:0:Channel[0].Command – Initializes the output command to 0.

IMPORTANT The transceiver executes a command when the command value

changes. When repeating a command, set the command value to 0 first
and then reset it to the same desired value.

Start – Latches a tag that indicates the function has started.

Unlatch – Unlatches (turns OFF) the instruction from Rung 0 and readies the routine for the
next RFID tag.

Rung 2
Start – With the output channel properly initialized, the Start bit enables the rung to begin
execution.

EQU RFID_1:I:Command[0].Command =0 – When an output command is updated, the interface

block returns that command back to the input command. If the input command is zero (it was
set in Rung 1), then the EQU output goes HI and enables the subsequent MOV command.

MOV x to RFID_1:O:Command[0].Command – Moving a nonzero value into the output command

byte instructs the RFID block to execute the command.

Rung 3
Rung 3 verifies that another command is not initiated while a command is busy.

Start – The Start bit enables the rung to begin execution.

RFID_1:I:Channel[0].Busy – When the command begins execution, the Busy bit goes HI. This
contact closes and the rung is executed.

InProgress – When command begins execution, an In-Progress bit is latched ON.

Start – This contact is opened, as the command has transitioned from start to busy.

74 Rockwell Automation Publication 56RF-UM001E-EN-P - October 2022

 Chapter 10 RSLogix 5000 Code Examples

Rung 4
Rung 4 confirms the completion of the command, as the interface block moves a value into the
input channel command location.

InProgress – This contact closes when the read command begins execution.
RFID_1:I:Channel[0].Busy – This contact is open while the command is in process.

EQU RFID_1:I:Channel[0].Command – Upon completion of the command the interface block

copies the value from output command to the input command. If the input command value
equals the value of the command, the EQU output goes HI.

InProgress – This bit is unlatched when the command is successfully completed. The routine is
now ready for the next RFID tag or other routine.

Clear Multiple Bytes The Clear Multiple Bytes command clears multiple bytes of user data in an RFID tag. You can
specify the number of bytes to clear and the address from which to begin. Similar to a “copy”
command, it copies the value that you specify in the output data image Data[0] location to the
addresses you specify.
Set the following values in the output image table:
a. xx:O.Channel[0].Command = 13
b. xx:O.Channel[0].Address = starting address
c. xx:O.Channel[0].BlockSize = 0
d. xx:O.Channel[0].Data[0] = 0 (or value that is used to clear the byte)
e. xx:O.Channel[0].Length = the number of bytes to clear
f. xx:O.Channel[0].Reset = 0
g. xx:O.Channel[0].Timeout = 0
h. xx:O.Channel[0].UIDLow = 0 (or UIDLow)
i. xx:O.Channel[0].UIDHi = 0 (or UIDHi)

Unless a UUID is specified, this command operates on the first tag in the field. Specify a UUID
in xx:O.Channel[0].UIDLow and xx:O.Channel[0].UIDHi to perform the command on a specific
tag.

Example Routine
In the following example routine, the initialization in Rung 1 sets the address, length data, the
value that is used to clear the fields and sets the command value to 0. The BlockSize, Reset,
Timeout, UIDLow, and UIDHi are set to 0 in the output image table. The value to be copied is
initially stored in the controller tag CMB_Data. In the following example, CMB_Data is set to 0,
but you can set this value to be any valid SINT value.

Rockwell Automation Publication 56RF-UM001E-EN-P - October 2022 75

Chapter 10 RSLogix 5000 Code Examples

Example Results
To demonstrate the results, the Read Byte command was executed on an RFID tag. The data in
this tag was a simple list of numbers starting from 1. The counter is 31.

The Clear Multiple Byte command is executed successfully as the ChError = 0 and all data
bytes are zero. The counter increments to 32.

The tag is read again (command = 4) to confirm the clearing. Data bytes 2...4 are successfully
set to 0.

76 Rockwell Automation Publication 56RF-UM001E-EN-P - October 2022

 Chapter 10 RSLogix 5000 Code Examples

Get Multiple Block Security The Get Multiple Block Security Status command retrieves the security status of multiple
blocks within a tag. It also displays the Universally Unique Identifier (UUID) of the RFID tag.
Status
Set the following values in the output image table:
a. xx:O.Channel[0].Command = 45
b. xx:O.Channel[0].Address = the first block to read
c. xx:O.Channel[0].Block = 0
d. xx:O.Channel[0].Data[0] = 0
e. xx:O.Channel[0].Length = the number of blocks to read.
f. xx:O.Channel[0].Reset = 0
g. xx:O.Channel[0].Timeout = 0
h. xx:O.Channel[0].UIDLow = 0 (or UIDLow)
i. xx:O.Channel[0].UIDHi = 0 (or UIDHi)

Unless a UUID is specified, this command operates on the first tag in the field. Specify a UUID
in xx:O.Channel[0].UIDLow and xx:O.Channel[0].UIDHi to perform the command on a specific
tag.

Example Routine
In the following example routine, the initialization in Rung 1 sets the address, length data, the
Data[0] value that is used to clear the fields and sets the command value to 0. The BlockSize,
Reset, Timeout, UIDLow, and UIDHi are set to 0 in the output image table. The starting address
is block 0. The command reads 28 blocks (all blocks of this RFID tag).

Rockwell Automation Publication 56RF-UM001E-EN-P - October 2022 77

Chapter 10 RSLogix 5000 Code Examples

Example Results
The following example shows the security status for the first three blocks. Blocks 0 and 2 are
locked. Block 1 is not locked.

78 Rockwell Automation Publication 56RF-UM001E-EN-P - October 2022

 Chapter 10 RSLogix 5000 Code Examples

The following information is displayed:

• xx:I.Channel[0].Data[0…7] = UUID
• xx:I.Channel[0].Data[8…9] = Security status of block x
• xx:I.Channel[0].Data[10…11] = Security status of block x+1

Get System Information The Get System Information command returns the following RFID tag information:
• Info_Flag
• Data Storage Format Identifier (DSFID)
• Application Family Identifier (AFI)
• Universally Unique Identifier (UUID)
• Memory Size
• IC Reference

Set the following values in the output image table:

a. xx:O.Channel[0].Command = 34
b. xx:O.Channel[0].Address = 0
c. xx:O.Channel[0].BlockSize = 0
d. xx:O.Channel[0].Data[0] = 0
e. xx:O.Channel[0].Length = 0
f. xx:O.Channel[0].Reset = 0
g. xx:O.Channel[0].Timeout = 0
h. xx:O.Channel[0].UIDLow = 0 (or UIDLow)
i. xx:O.Channel[0].UIDHi = 0 (or UIDHi)

Unless a UUID is specified, this command operates on the first tag in the field. Specify a UUID
in xx:O.Channel[0].UIDLow and xx:O.Channel[0].UIDHi to perform the command on a specific
tag.

Example Routine
In the following example routine, the initialization in Rung 1 sets the address, length data, the
Data[0] value that is used to clear the fields and sets the command value to 0. Because the
address, length and data[0] can only be 0, the source in the MOV instruction can be set to 0.
The BlockSize, Reset, Timeout, UIDLow, and UIDHi are set to 0 in the output image table.

Rockwell Automation Publication 56RF-UM001E-EN-P - October 2022 79

Chapter 10 RSLogix 5000 Code Examples

Example Results
The Info Flag contains data that is used to determine what parameters are passed back.

The DSFID, AFI, and UUID follow.

The tag being read was catalog number 56RRF-TG-30. This tag has 28 blocks. The maximum
block number is 27, as the first block is 0. Each block has 4 bytes. The maximum byte number
is 3, as the first byte is 0.

The IC Ref is the last byte reported.

80 Rockwell Automation Publication 56RF-UM001E-EN-P - October 2022

 Chapter 10 RSLogix 5000 Code Examples

Get Version Information The Get Version Information command retrieves the firmware revision information from the
transceiver.

Set the following values in the output image table:

a. xx:O.Channel[0].Command = 33
b. xx:O.Channel[0].Address = 0
c. xx:O.Channel[0].BlockSize = 0
d. xx:O.Channel[0].Data[0] = 0
e. xx:O.Channel[0].Length = 0
f. xx:O.Channel[0].Reset = 0
g. xx:O.Channel[0].Timeout = 0
h. xx:O.Channel[0].UIDLow = 0
i. xx:O.Channel[0].UIDHi = 0

Example Routine
In the following example routine, the initialization in Rung 1 sets the address, length data, the
Data[0] value that is used to clear the fields and sets the command value to 0. Because the
address, length and data[0] can only be 0, the source in the MOV instruction can be set to 0.
The BlockSize, Reset, Timeout, UIDLow, and UIDHi are set to 0 in the output image table.

Rockwell Automation Publication 56RF-UM001E-EN-P - October 2022 81

Chapter 10 RSLogix 5000 Code Examples

Example Results
The results are stored in Data [0…3]. In this example, the version is de20007 (version 2.07).

Inventory The inventory command returns the UUID and DSFID information from the RFID tags in the
field. This command can read up to a maximum of four tags. The more tags in the field, the
more time the tags must be in the field to complete the inventory command. By setting the
output image fields to specific values, the Inventory command returns the following
information:
1. Returns the number of tags in the field and the UUID of each tag. Set Address =0, Length
= 0 and Data[0] = 0
2. Returns the number of tags in the field, the UUID, and the DSFID of each tag. Set Address
=0, Length = 1 and Data[0] = 0
3. Returns the number of tags in the field, the UUID, and the DSFID of each tag that meets
the specified AFI. Set Address =1, Length = 1 and Data[0] = AFI value. If the AFI value is 0,
then all tags are reported.

Set the following values in the output image table:

a. xx:O.Channel[0].Command = 20
b. xx:O.Channel[0].Address = 0 (or 1) (a)
c. xx:O.Channel[0].Block = 0
d. xx:O.Channel[0].Data[0] = 0 (or 1) (b)
e. xx:O.Channel[0].Length = 0 (or 1) (c)
f. xx:O.Channel[0].Reset = 0
g. xx:O.Channel[0].Timeout = 0
h. xx:O.Channel[0].UIDLow = 0
i. xx:O.Channel[0].UIDHi = 0

(a) Set Address = 0 to get all tags in the RF field.

Set Address = 1 to get all tags that have the AFI value specified in the Data[0] location.
(b) Set Data[0] = 0 to return all tags in the RF field.
Set Data[0] = AFI value (but not zero) to return only those tags that have that AFI value
(c) Set Length = 0 to get only the UUID for each tag.
Set Length = 1 to get both the UUID and the DSFID for each tag.

82 Rockwell Automation Publication 56RF-UM001E-EN-P - October 2022

 Chapter 10 RSLogix 5000 Code Examples

Example Routine
In the following example routine, the initialization in Rung 1 sets the address, length data, the
Data[0] value that is used to clear the fields and sets the command value to 0. The BlockSize,
Reset, Timeout, UIDLow, and UIDHi are set to 0 in the output image table.

The example ladder diagram is initially set for Address =0, Length = 0 and Data[0] = 0. These
values are then changed to obtain example results for the three versions of the Inventory
command.

Example Results
In example 1, the Address = 0, Length = 0 and Data[0] = 0. Four RFID tags were in the RF field at
the time the read command was executed. The controller tag values are shown in the following
example. The data shows the number of tags in the RF field and the UUID for each tag.

Rockwell Automation Publication 56RF-UM001E-EN-P - October 2022 83

Chapter 10 RSLogix 5000 Code Examples

In example 2, the length was changed to 1, the Address = 0, Length = 1 and Data[0] = 0. Four
RFID tags were in the RF field at the time the read command was executed. The controller tag
values are shown in the following example. The data shows the number of tags in the RF field,
the DSFID, and the UUID for each tag.

In example 3, we get the tag information for only those tags that have a specific AFI. In this
example, the AFI is 57. Address = 1, Length = 1 and Data[0] = 57. Two of the four RFID tags that
were present in the RF field at the time the read command was executed had AFI set to 57. The
controller tag values are shown in the following example. The data shows the number of tags
in the RF field, the DSFID, and the UUID for each of these tags.

84 Rockwell Automation Publication 56RF-UM001E-EN-P - October 2022

 Chapter 10 RSLogix 5000 Code Examples

Lock AFI The Lock AFI command locks the 1 byte of information for the AFI, preventing it from being
modified in the future.

IMPORTANT Once the AFI byte is locked, it cannot be unlocked.

The AFI is used to group RFID tags by application. This configuration allows the transceiver to
send out an AFI and target only the tags that meet the application criteria.
Set the following values in the output image table:
a. xx:O.Channel[0].Command = 42
b. xx:O.Channel[0].Address = 0
c. xx:O.Channel[0].BlockSize = 0
d. xx:O.Channel[0].Data[0] = 0
e. xx:O.Channel[0].Length = 0
f. xx:O.Channel[0].Reset = 0
g. xx:O.Channel[0].Timeout = 0
h. xx:O.Channel[0].UIDLow = UIDLow
i. xx:O.Channel[0].UIDHi = UIDHi

The UIDLow and UIDHi bytes must be specified to lock the AFI value. The UUID can be found by
performing the Inventory command.

Example Routine
In the following example routine, the initialization in Rung 1 sets the address, length, the
Data[0, UIDLow and UIDHi values used to lock the AFI and sets the command value to 0. The
BlockSize, Reset, and Timeout are set to 0 in the output image table.

Rockwell Automation Publication 56RF-UM001E-EN-P - October 2022 85

Chapter 10 RSLogix 5000 Code Examples

Example Results
Figure 27 shows an example of results on the input image table. The Command is showing 42
and the ChError is showing 0. The input data bytes are all zero.
Figure 27 - Input Image Table

Errors

The following ChErrors are generated:

• 0 – AFI was successfully locked.
• 4 – A tag with the wrong UUID entered the RF field.
• 8 – A tag that has already been locked entered the RF field.

Lock Block The Lock Block command locks one block of user data, preventing future writing. The
transceiver automatically determines the block size of the RFID tag.

IMPORTANT Once the block is locked, the block cannot be unlocked.

Set the following values in the output image table:

a. xx:O.Channel[0].Command = 40
b. xx:O.Channel[0].Address = the number of the block to lock
c. xx:O.Channel[0].BlockSize = 0
d. xx:O.Channel[0].Data[0] = 0
e. xx:O.Channel[0].Length = 0
f. xx:O.Channel[0].Reset = 0
g. xx:O.Channel[0].Timeout = 0
h. xx:O.Channel[0].UIDLow = UIDLow
i. xx:O.Channel[0].UIDHi = UIDHi
The UIDLow and UIDHi bytes must be specified to lock the block values. The UUID can be found
by performing the Inventory command.

Example Routine
In the following example routine, the initialization in Rung 1 sets the address, length, the
Data[0], UIDLow, and UIDHi values used to lock the block and sets the command value to 0.
The BlockSize, Reset, and Timeout are set to 0 in the output image table.

In the example routine, rung 1 initializes the output image table. The UUID is stored in a
controllers tags UIDLow and UIDHi. Block 26 is locked. This tag has a total of 27 blocks.

86 Rockwell Automation Publication 56RF-UM001E-EN-P - October 2022

 Chapter 10 RSLogix 5000 Code Examples

Example Results
Figure 28 shows address 26, which is the second to last block of the catalog number 56RF-TG-
30 tag. The command is 40. The UUID must be specified to lock any blocks.
Figure 28 - Input Image Table

After completion of the lock block command, the input image table shows that the command is
40 and the ChError is 0.

Errors

The ChErrorfield is 8 if you try to lock a block that is already locked.

Rockwell Automation Publication 56RF-UM001E-EN-P - October 2022 87

Chapter 10 RSLogix 5000 Code Examples

Lock DSFID The Lock DSFID command locks the 1 byte of information for the Data Storage Format
Identifier (DSFID) area of the tag, preventing it from being modified.

IMPORTANT Once the DSFID byte is locked, it cannot be unlocked.

Set the following values in the output image table:

a. xx:O.Channel[0].Command = 44
b. xx:O.Channel[0].Address = 0
c. xx:O.Channel[0].Data[0] = 0
d. xx:O.Channel[0].Length = 0
e. xx:O.Channel[0].Reset = 0
f. xx:O.Channel[0].Timeout = 0
g. xx:O.Channel[0].UIDLow = UIDLow
h. xx:O.Channel[0].UIDHi = UIDHi

The UIDLow and UIDHi bytes must be specified to lock the DSFID value. The UUID can be found
by performing the Inventory command.

Example Routine
In the following example routine, the initialization in Rung 1 sets the address, length, the
Data[0], UIDLow, and UIDHi values used to lock the DSFID and sets the command value to 0.
The BlockSize, Reset, and Timeout are set to 0 in the output image table.

88 Rockwell Automation Publication 56RF-UM001E-EN-P - October 2022

 Chapter 10 RSLogix 5000 Code Examples

Example Results
When successful, the results shown in the input image table show ChError = 0 and the
Command number =44.

If you try to lock the DSFID on an RFID tag that is already locked, the ChError is equal to 8.

Read Byte Command The Read Byte command reads a user-specified number of bytes from a tag, starting at a
user-specified address. An Option Flag can be set to return the UUID of the tag. The maximum
number of bytes that can be read at a time is 160 bytes using option flag 0, and 152 bytes using
option flag 1.
• Option Flag 0
Returns the specified user data. Set xx:O.Channel[0].Data[0] = 0.
• Option Flag 1
Returns the UUID of the RFID tag and the specified user data. Set
xx:O.Channel[0].Data[0] = 1.

Set the following values in the output image table:

a. xx:O.Channel[0].Command = 4
b. xx:O.Channel[0].Address = starting address to read
c. xx:O.Channel[0].BlockSize = 0
d. xx:O.Channel[0].Data[0] = Option Flag
e. xx:O.Channel[0].Length = the number of bytes to read
f. xx:O.Channel[0].Reset = 0
g. xx:O.Channel[0].Timeout = 0
h. xx:O.Channel[0].UIDLow = 0
i. xx:O.Channel[0].UIDHi = 0

This command operates only on the first tag in the field.

Data[1] must also be set to 0.

Example Routine
The following example routine is to read all data and the UUID in a catalog number 56RF-TG-30
ICODE tag. This tag holds a maximum of 112 bytes of data.

Rockwell Automation Publication 56RF-UM001E-EN-P - October 2022 89

Chapter 10 RSLogix 5000 Code Examples

In the following example routine, the initialization in Rung 1 sets the address, length, the
Data[0]to the Option Flag, and sets the command value to 0. The BlockSize, Reset, Timeout,
UIDLow, and UIDHi are set to 0 in the output image table.

Example Results
Figure 29 shows an example of results where the Option Flag was set to 1, which reads the
UUID.

The UUID is loaded into Data[0] through Data[7]. The user data (1, 2, 3, 4, 5, 6…) begins in
Data[8]. Figure 29 only shows a partial listing of the user data. The command read in 112 bytes
of data.
Figure 29 - Input Image Table - User Data

90 Rockwell Automation Publication 56RF-UM001E-EN-P - October 2022

 Chapter 10 RSLogix 5000 Code Examples

In Figure 30, the command was repeated with the Starting Address set to 2 and the number of
bytes set to 3.
Figure 30 - Input Image Table - Repeated Command

Multi-tag Block Read The Multi-tag Block Read command reads multiple blocks of user data from multiple tags in
the RF field. The transceiver automatically determines the block size. All RFID tags in the field
will have the same block size.

This command can read up to four tags. Adequate time must be allowed to read all tags in the
RF field.

Set the following values in the output image table:

a. xx:O.Channel[0].Command = 3
b. xx:O.Channel[0].Address = the first block to read
c. xx:O.Channel[0].BlockSize = 0
d. xx:O.Channel[0].Data[0] = 0
e. xx:O.Channel[0].Length = the number of blocks to read
f. xx:O.Channel[0].Reset = 0
g. xx:O.Channel[0].Timeout = 0
h. xx:O.Channel[0].UIDLow = 0 (or UIDLow)
i. xx:O.Channel[0].UIDHi = 0 (or UIDHi)

Unless a UUID is specified, this command operates on the first four tags in the field. Specify a
UUID in xx:O.Channel[0].UIDLow and xx:O.Channel[0].UIDHi to perform the command on a
specific tag.

Example Routine
In the following example routine, the initialization in Rung 1 sets the address, length, the
Data[0] value that is used to read multiple tags and sets the command value to 0. The
BlockSize, Reset, Timeout, UIDLow, and UIDHi are set to 0 in the output image table.

The example ladder diagram is initially set for Address = 25 and the Length = 2. The command
reads blocks 25 and 26.

Rockwell Automation Publication 56RF-UM001E-EN-P - October 2022 91

Chapter 10 RSLogix 5000 Code Examples

Example Results
The input image data fields are populated with the number of tags, followed by the UUID and
block data of each tag.

In the following example, four catalog number 56RF-TG-30 RFID tags were read. These tags
hold 4 bytes per block. Since two blocks (25 and 26) were read, a total of eight data fields are
used to store the user data. The image only shows the information from two of the four RFID
tags.

92 Rockwell Automation Publication 56RF-UM001E-EN-P - October 2022

 Chapter 10 RSLogix 5000 Code Examples

Read Multiple Blocks The Read Multiple Blocks command reads multiple blocks of user data from an RFID tag. Option
Flags can be set to return just the data in the blocks or return the data and the security status
for each block of data. The maximum number of blocks that can be read at one time is 10.
• Option Flag 0
Returns multiple blocks of user data. Set xx:O.Channel[0].Data[0] = 0.
• Option Flag 1
Returns multiple blocks of user data and the security status of each block. Set
xx:O.Channel[0].Data[0] = 1.

Set the following values in the output image table:

a. xx:O.Channel[0].Command = 2
b. xx:O.Channel[0].Address = the first block to read
c. xx:O.Channel[0].BlockSize = 0
d. xx:O.Channel[0].Data[0] = the Option Flag
e. xx:O.Channel[0].Length = the number of blocks to read
f. xx:O.Channel[0].Reset = 0
g. xx:O.Channel[0].Timeout = 0
h. xx:O.Channel[0].UIDLow = 0 (or UIDLow)
i. xx:O.Channel[0].UIDHi = 0 (or UIDHi)

Unless a UUID is specified, this command operates on the first tag in the field. Specify a UUID
in xx:O.Channel[0].UIDLow and xx:O.Channel[0].UIDHi to perform the command on a specific
tag.

Example Routine
In the following example routine, the initialization in Rung 1 sets the address, length, and
Data[0] values used to read multiple blocks and sets the command value to 0. The BlockSize,
Reset, Timeout, UIDLow, and UIDHi are set to 0 in the output image table.

The example ladder diagram is initially set for Address =25, the Length = 2. Data[0] is set to
Option Flag 0 (return just the data). The command reads blocks 25 and 26. The example is
repeated with Option Flag set to 1.

Rockwell Automation Publication 56RF-UM001E-EN-P - October 2022 93

Chapter 10 RSLogix 5000 Code Examples

Example Results
This first example uses Option Flag = 0; return only the data in the blocks. With a starting block
number of 25 and two blocks to read, data from Blocks 25 and 26 are returned. The tag was a
catalog number 56RF-TG-30, which has only 4 bytes per block. The data appears in the input
channel Data[0…7].

This second example shows the results for Option Flag = 1; return the data and the security
status. With a starting block number of 25 and two blocks to read, data from Blocks 25 and 26
are returned. The tag was a catalog number 56RF-TG-30, which has only 4 bytes per block.

The data for the first block appears in the input channel Data[0…3]. The security status
appears in Data[4]. The value of 0 indicates that the block is not locked.

94 Rockwell Automation Publication 56RF-UM001E-EN-P - October 2022

 Chapter 10 RSLogix 5000 Code Examples

The data for the second block appears in the input channel Data[6…9]. The security status
appears in Data[10]. The value of 1 indicates that the block is locked.

Read Single Block The Read Single Block command reads one block of user data from a tag. Option Flags can be
set to return information the UUID and security status of the block.
• Option Flag 0
Returns one block of user data. Set xx:O.Channel[0].Data[0] = 0.
• Option Flag 1
Returns one block of user data and the security status of that block. Set
xx:O.Channel[0].Data[0] = 1.

Set the following values in the output image table:

a. xx:O.Channel[0].Command = 1
b. xx:O.Channel[0].Address = the block number to read.
c. xx.O.Channel[0].BlockSize = 0
d. xx:O.Channel[0].Data[0] = the Option Flag value
e. xx:O.Channel[0].Length = 0
f. xx:O.Channel[0].Reset = 0
g. xx:O.Channel[0].Timeout = 0
h. xx:O.Channel[0].UIDLow = 0 (or UIDLow)
i. xx:O.Channel[0].UIDHi = 0 (or UIDHi)

Unless a UUID is specified, this command operates on the first tag in the field. Specify a UUID
in xx:O.Channel[0].UIDLow and xx:O.Channel[0].UIDHi to perform the command on a specific
tag.

Example Routine
In the following example routine, the initialization in Rung 1 sets the address, length, and
Data[0] values used to read multiple blocks and sets the command value to 0. The BlockSize,
Reset, Timeout, UIDLow, and UIDHi are set to 0 in the output image table.

The example ladder diagram is initially set for Address =26. Data[0] is set to Option Flag 0
(return just the data). The command reads blocks 25 and 26. The example is repeated with
Option Flag set to 1.

Rockwell Automation Publication 56RF-UM001E-EN-P - October 2022 95

Chapter 10 RSLogix 5000 Code Examples

Example Results
• Option Flag 0
This first example uses Option Flag = 0; return only the data in the block. The block
number is 26. The tag was a catalog number 56RF-TG-30, which has only 4 bytes per
block. The data appears in the input channel Data[0…3].

• Option Flag 1
The second example demonstrates the results when Option Flag = 1. Data[0] shows the
security status of the block. The 1 indicates that the block has been locked. A zero
indicates that the block is unlocked. The data appears in Data[1…4].

96 Rockwell Automation Publication 56RF-UM001E-EN-P - October 2022

 Chapter 10 RSLogix 5000 Code Examples

Read Transceiver Settings The Read Transceiver Settings command retrieves the following information from the
transceiver:
• Device ID
• Communication rate
• Retry time
• Gain

Set the following values in the output image table:

a. xx:O.Channel[0].Command = 31
b. xx:O.Channel[0].Address = 0
c. xx:O.Channel[0].BlockSize = 0
d. xx:O.Channel[0].Data[0] = 0
e. xx:O.Channel[0].Length = 0
f. xx:O.Channel[0].Reset = 0
g. xx:O.Channel[0].Timeout = 0
h. xx:O.Channel[0].UIDLow = 0
i. xx:O.Channel[0].UIDHi = 0

Example Routine
In the following example routine, the initialization in Rung 1 sets the address, length, data, and
command. Because the address, length and Data[0] can only be 0, the source in the MOV
instruction can be set to 0. The UIDLow, UIDHi, BlockSize, Reset, and Timeout are set to 0 in the
output image table.

Rockwell Automation Publication 56RF-UM001E-EN-P - October 2022 97

Chapter 10 RSLogix 5000 Code Examples

Example Results
The following information is displayed:
• xx:I.Channel[0].Data[0…1] = Device ID
• xx:I.Channel[0].Data[2…5] = Communication rate
• xx:I.Channel[0].Data[6…7] = Retry setting
• xx:I.Channel[0].Data[8…9] = Gain

Gain is 0…3, with 0 being the highest gain.

Write AFI The Write AFI command writes 1 byte of information into the AFI. The AFI is used to group RFID
tags by application. This configuration allows the transceiver to read and write only to those
tags with the specified AFI value.

Set the following values in the output image table:

a. xx:O.Channel[0].Command = 41
b. xx:O.Channel[0].Address = 0
c. xx:O.Channel[0].BlockSize = 0
d. xx:O.Channel[0].Data[0] = AFI value
e. xx:O.Channel[0].Length = 1
f. xx:O.Channel[0].Reset = 0
g. xx:O.Channel[0].Timeout = 0
h. xx:O.Channel[0].UIDLow = 0 (or UIDLow)
i. xx:O.Channel[0].UIDHi = 0 (or UIDHi)

Unless a UUID is specified, this command operates on the first tag in the field. Specify a UUID
in xx:O.Channel[0].UIDLow and xx:O.Channel[0].UIDHi to perform the command on a specific
tag.

Example Routine
In the following example routine, the initialization sets the address, length data, and
command. The BlockSize, Reset, Timeout, UIDLow, and UIDHi are set to 0 in the output image
table.

98 Rockwell Automation Publication 56RF-UM001E-EN-P - October 2022

 Chapter 10 RSLogix 5000 Code Examples

Example Results
Figure 31 shows an example of results on the input image table. The Command is showing 41
and theChError is showing 0. The data bytes are all zero. Confirmation that the AFI was written
can be observed in the Get_System_Information_Routine.
Figure 31 - Input Image Table

Write Byte Command The Write Byte command writes bytes of user data to a tag. You must specify the data, the
start byte, and the number of bytes to write.
a. xx:O.Channel[0].Command = 14
b. xx:O.Channel[0].Address = starting address to write
c. xx:O.Channel[0].BlockSize = 0
d. xx:O.Channel[0].Data[0…111] = the data to write
e. xx:O.Channel[0].Length = the number of bytes to write
f. xx:O.Channel[0].Reset = 0
g. xx:O.Channel[0].Timeout = 0
h. xx:O.Channel[0].UIDLow = 0 (or UIDLow)
i. xx:O.Channel[0].UIDHi = 0 (or UIDHi)

Rockwell Automation Publication 56RF-UM001E-EN-P - October 2022 99

Chapter 10 RSLogix 5000 Code Examples

Unless a UUID is specified, this command operates on the first tag in the field. Specify a UUID
in xx:O.Channel[0].UIDLow and xx:O.Channel[0].UIDHi to perform the command on a specific
tag.

Example Routine
In the following example routine, the initialization in Rung 1 sets the address, length, and
Data[0] values used to read multiple blocks and sets the command value to 0. The BlockSize,
Reset, Timeout, UIDLow, and UIDHi are set to 0 in the output image table.

The example ladder diagram is initially set for Address =0, the Length = 10. Data[0…9] are set
to a sequential list of numbers starting with 11.

Example Results
Figure 32 shows the output image table with the 10 bytes of data that is written to the RFID tag.
The sequence is 11, 12, 13, 14, 15, 16, 17, 18, 19, and 20.
Figure 32 - Output Image Table

100 Rockwell Automation Publication 56RF-UM001E-EN-P - October 2022

 Chapter 10 RSLogix 5000 Code Examples

After successful completion of the Write Byte command, the input image table shows the UUID
of the tag.

The Read_Byte_Routine can be used to read the data. The data is stored in the input channel
data, starting at location 0.

Write DSFID The Write DSFID (Data Storage Format Identifier) command writes 1 byte of information in the
Data Storage Format Identifier (DSFID) of the RFID tag.
Set the following values in the output image table:
a. xx:O.Channel[0].Command = 43
b. xx:O.Channel[0].Address = 0
c. xx:O.Channel[0].Data[0] = DSFID value
d. xx:O.Channel[0].Length = 1
e. xx:O.Channel[0].Reset = 0
f. xx:O.Channel[0].Timeout = 0
g. xx:O.Channel[0].UIDLow = 0 (or UIDLow)
h. xx:O.Channel[0].UIDHi = 0 (or UIDHi)

If UIDLow and UIDHI are set to 0, this command operates on the first tag in the field. Specify a
UUID in xx:O.Channel[0].UIDLow and xx:O.Channel[0].UIDHi to perform the command on a
specific tag.

Example Routine
In the following example routine, the initialization in Rung 1 sets the address, length, and
Data[0] values used to read multiple blocks and sets the command value to 0. The BlockSize,
Reset, Timeout, UIDLow, and UIDHi are set to 0 in the output image table.

The example ladder diagram is initially set for Address =0, the Length = 0. Data[0] is set to the
DSFID value.

Rockwell Automation Publication 56RF-UM001E-EN-P - October 2022 101

Chapter 10 RSLogix 5000 Code Examples

Example Results
The command is executed successfully if the ChError = 0, the
Command value = 43 and all Data bytes are 0.
Use the Get System Information command or the Inventory command to read the DSFID.

Write Multiple Blocks The Write Multiple Blocks command writes to either one or two blocks of user data to a FRAM
tag. This command only works on FRAM tags. Catalog number 56RF-TG-2KB is a FRAM tag.
a. xx:O.Channel[0].Command = 11
b. xx:O.Channel[0].Address = starting block to write
c. xx:O.Channel[0].BlockSize = number of bytes per block
d. xx:O.Channel[0].Data[0…xxx] = data to write
e. xx:O.Channel[0].Length =the number of blocks to write
f. xx:O.Channel[0].Reset = 0
g. xx:O.Channel[0].Timeout = 0
h. xx:O.Channel[0].UIDLow = 0 (or UIDLow)
i. xx:O.Channel[0].UIDHi = 0 (or UIDHi)

If UIDLow and UIDHi are set to 0, this command operates on the first tag in the field. Specify a
UUID in xx:O.Channel[0].UIDLow and xx:O.Channel[0].UIDHi to perform the command on a
specific tag.

102 Rockwell Automation Publication 56RF-UM001E-EN-P - October 2022

 Chapter 10 RSLogix 5000 Code Examples

Table 37 shows the valid values for length, block size, and the number of bytes written or each
combination.
Table 37 - Valid Values
Description Value
Length 1 1 1 2 2 2
Block Size 0 4 8 0 4 8
Bytes Written 4 4 8 8 8 16

Example Routine
In the following example routine, the initialization in Rung 1 sets the address, length, and block
size values that are used to write multiple blocks and sets the command value to 0. The
BlockSize, Reset, Timeout, UIDLow, and UIDHi are set to 0 in the output image table.

Example Results
Figure 33 on page 104 shows the output image table with the data that is written (a simple
numeric sequence starting at 2). Two blocks of 8 bytes each is written to the tag. The data is
written to address locations 3 and 4.

Rockwell Automation Publication 56RF-UM001E-EN-P - October 2022 103

Chapter 10 RSLogix 5000 Code Examples

Figure 33 - Output Image Table

If the Write Multiple Blocks command is executed properly, the input table image results show
ChError = 0, Command = 11 and Data[0-xxx] =0.

Use the Read Multiple Block command (=2) to read the data.

104 Rockwell Automation Publication 56RF-UM001E-EN-P - October 2022

 Chapter 10 RSLogix 5000 Code Examples

Multi-tag Block Write The Multi-tag Block Write command writes one or more blocks of user data to multiple tags in
the transceiver field. The maximum number of tags in the RF field is limited to four and all tags
must have the same block size.

Set the following values in the output image table:

a. xx:O.Channel[0].Command = 12
b. xx:O.Channel[0].Address = starting address to write
c. xx:O.Channel[0].BlockSize = number of bytes/block
d. xx:O.Channel[0].Data[0…xxx] = data to write
e. xx:O.Channel[0].Length = number of blocks to write
f. xx:O.Channel[0].Reset = 0
g. xx:O.Channel[0].Timeout = 0
h. xx:O.Channel[0].UIDLow = 0 (or UIDLow)
i. xx:O.Channel[0].UIDHi = 0 (or UIDHi)

If UIDLow and UIDHi are set to 0, this command operates on the first tag in the field. Specify a
UUID in xx:O.Channel[0].UIDLow and xx:O.Channel[0].UIDHi to perform the command on a
specific tag.

IMPORTANT Length must be in 4-byte increments (for example, 4, 8, 12…) for

ISO15693 tags or 8-byte increments (for example, 8, 16, 24…) for FRAM
tags.

IMPORTANT The BlockSize field is used to specify the number of bytes/block of the
tag. Valid values are:
• 0 = 4 bytes/block
• 4 = 4 bytes/block
• 8 = 8 bytes/block
Typically, ISO15693 tags have a block size of 4 bytes/block, and FRAM
tags have a block size of 8 bytes/block.

Example Routine
In the following example, data is written to two blocks, starting with Block 3. The data is loaded
into the output channel image table. Block three is populated with Data[0…3] = 11, 13, 15 and 17.
Block 4 is populated with Data[4…7] = 19, 21, 23, 25.

Rockwell Automation Publication 56RF-UM001E-EN-P - October 2022 105

Chapter 10 RSLogix 5000 Code Examples

Example Results
The input channel image table shows the number of RFID tags that were written and the UUID
of each RFID tag.

106 Rockwell Automation Publication 56RF-UM001E-EN-P - October 2022

 Chapter 10 RSLogix 5000 Code Examples

Use the Read Multi Tag Block command (=3) to read the blocks and confirm that the data was
written.

Write Single Block The Write Single Block command writes one block of user data to an RFID tag.
Set the following values in the output image table:
a. xx:O.Channel[0].Command = 10
b. xx:O.Channel[0].Address = starting address to write
c. xx:O.Channel[0].BlockSize = 0, 4, or 8
d. xx:O.Channel[0].Data[0…112] = data to write
e. xx:O.Channel[0].Length = 0, 4, or 8
f. xx:O.Channel[0].BlockSize = 0, 4, or 8
g. xx:O.Channel[0].Reset = 0
h. xx:O.Channel[0].Timeout = 0
i. xx:O.Channel[0].UIDLow = 0 (or UIDLow)
j. xx:O.Channel[0].UIDHi = 0 (or UIDHi)
If UIDLow and UIDHi are set to 0, this command operates on the first tag in the field. Specify a
UUID in xx:O.Channel[0].UIDLow and xx:O.Channel[0].UIDHi to perform the command on a
specific tag.

The Length and Block Size fields are used to specify the number of bytes/block of the tag.
Valid values are:
• 0 = 4 bytes/block
• 4 = 4 bytes/block
• 8 = 8 bytes/block
Typically, ISO15693 tags have a block size of 4 bytes/block, and FRAM tags have a block size of
8 bytes/block.
Rockwell Automation Publication 56RF-UM001E-EN-P - October 2022 107
Chapter 10 RSLogix 5000 Code Examples

Example Routine
In the following example, 4 bytes of data is written to Block 3. The data is loaded into the
output channel image table. Block three is populated with Data[0…3] = 41, 42, 43, and 44.

Example Results
The output image table shows that the address is set to Block 3; the block size is 4 and the
command is 10. The data to be written to block 3 is 41, 42, 43, and 44.

Upon successful completion of the write block command, the Input Image table shows that
Command = 10 and ChError = 0. The input channel data fields are all zero.

108 Rockwell Automation Publication 56RF-UM001E-EN-P - October 2022

 Chapter 10 RSLogix 5000 Code Examples

Use the Read Single Block command (=1), with option flag set to zero, to read the contents of
the tag in block 3.

Continuous Read Mode The Continuous Read command is used for specialty applications that require high line speeds
(up to 3 ms). See Continuous Read Mode on page 120 for details on this command.

Stop Continuous Read The Stop Continuous Read command is used with the Continuous Read command for specialty
applications that require high line speeds (up to 3 ms). See Continuous Read Mode on page 120
for details on this command.

Teach Continuous Read The Teach Continuous Read command is used to train the interface for Continuous Read
operations. See Teach Continuous Read on page 122 for details on this command.

Rockwell Automation Publication 56RF-UM001E-EN-P - October 2022 109

Chapter 10 RSLogix 5000 Code Examples

Notes:

110 Rockwell Automation Publication 56RF-UM001E-EN-P - October 2022

 Chapter 11

SLC Code Examples

This sample code example uses an SLC-5/05 with a catalog number 56RF-IN-IPD22 interface
block.

Read Byte Routine The Read Byte command (value =4) reads a user-specified number of bytes from a tag,
starting at a user-specified address. Additionally, an Option Flag can be set to return the UUID
of the tag.
• Option Flag 0
Returns the specified user data
• Option Flag 1
Returns the UUID of the tag and the specified user data

IMPORTANT This command operates only on the first tag in the field.

Example Routine
The following example code is for an SLC-5/05.

Rockwell Automation Publication 56RF-UM001E-EN-P - October 2022 111

Chapter 11 SLC Code Examples

Example Routine
Rung Description
Place RFID interface into the Run mode. The bit must be highlighted in green. If the bit is not green,
0000 right-click it and click Toggle Bit.
Read Input Image. Double-click the EEM box to enter the setup screen. Input Size is 116 bytes (58
words). Click the MultiHop tab to configure an EtherNet/IP™ device.

0001

Write Output Image. Double-click the MSG box to enter the setup screen. Output size is 124 bytes (62
words). Click the MultiHop tab to configure an EtherNet/IP device.

0002

The Tag Present bit is highlighted in green when a tag is present. When a tag is present, clear the
0003 command value.

112 Rockwell Automation Publication 56RF-UM001E-EN-P - October 2022

 Chapter 11 SLC Code Examples

Rung Description
When the command value has been cleared, load in the instruction parameters contained in N104
(Read Byte). N101 (Read Single Block) could be used in place of N104.

0004 Block
Command Address Length
Size

Timeout UIDLow0-Hi1

Wait for the read command to run. The Read in Progress bit is highlighted in green when the
command is running. When the command has completed, the Read in Progress bit returns to its
0005 original state. When the command has been executed and completed, copy the data that is read into
N100.
0006 If there was an error with the operation, then N100:0 contains the error code.

Rockwell Automation Publication 56RF-UM001E-EN-P - October 2022 113

Chapter 11 SLC Code Examples

Notes:

114 Rockwell Automation Publication 56RF-UM001E-EN-P - October 2022

 Chapter 12

MicroLogix 1400 Code Examples

Read Byte The Read Byte command (value =4) reads a user-specified number of bytes from a tag,
starting at a user-specified address. Additionally, an Option Flag can be set to return the
Universally Unique Identifier (UUID) of the tag.
• Option Flag 0
Returns the specified user data
• Option Flag 1
Returns the UUID of the tag and the specified user data

IMPORTANT This command operates only on the first tag in the field.

Rockwell Automation Publication 56RF-UM001E-EN-P - October 2022 115

Chapter 12 MicroLogix 1400 Code Examples

Example Routine
Rung Description
Place RFID interface into the Run Mode. The bit must be highlighted in green. If the bit is not green,
0000 right-click it and click Toggle Bit.
Read Input Image. Double-click the MSG box to enter the setup screen. Input size is 116 bytes (58
words). Click the MultiHop tab to configure an EtherNet/IP™ device.

0001

Write Output Image. Double-click the MSG box to enter the setup screen. Output size is 124 bytes (62
words). Click the MultiHop tab to create an EtherNet/IP device.

0002

The Tag Present bit is highlighted in green when a tag is present. When a tag is present, clear the
0003 command value.
0004 When the command value has been cleared, load in the instruction parameters contained in N104
(Read Byte). N101 (Read Single Block) could be used in place of N104.
Wait for the read command to run. The Read in Progress bit is highlighted in green when the
command is running. When the command has completed, the Read in Progress bit returns to its
0005 original state. When the command has been executed and completed, copy the data that is read into
N100.
0006 If there was an error with the operation, then N100:0 contains the error code.

116 Rockwell Automation Publication 56RF-UM001E-EN-P - October 2022

 Chapter 12 MicroLogix 1400 Code Examples

Write Byte The Write Byte command (value = 14) writes bytes of user data to a tag. You can specify the
data, the start byte, and the number of bytes to write.

IMPORTANT This command operates only on the first tag in the field.

Example Routine
Rung Description
Place RFID interface into the Run Mode. The bit must be highlighted in green. If the bit is not
0000 green, right-click it and click Toggle Bit.
Read Input Image. Double-click the MSG box to enter the Setup Screen. Input Size is 116 bytes
0001 (58 words). Click the MultiHop tab to configure an EtherNet/IP device.
Write Output Image. Double-click the MSG box to enter the Setup Screen. Output Size is 124
0002 bytes (62 words). Click the MultiHop tab to configure an EtherNet/IP device.
The Tag Present bit is highlighted in green when a tag is present. When a tag is present, clear
0003 the command value.
When the command value has been cleared, load in the instruction parameters contained in
0004 N114 (Write Byte). N110 (Write Single Block) could be used in place of N114.
Wait for the write command to run. The Write in Progress bit is highlighted in green when the
command is running. When the command has completed, the Write in Progress bit returns to
0005 its original state. When the command has been executed and completed, copy the data that
is read into N100.
0006 If there was an error with the operation, then N100:0 contains the error code.

Read Multiple Blocks The Read Multiple Blocks command (value = 2) reads multiple blocks of user data from a tag.
Additionally, Option Flags can be set to return information such as the UUID or the Data
Storage Format Identifier (DSFID) of the tag.
• Option Flag 0
Rockwell Automation Publication 56RF-UM001E-EN-P - October 2022 117
Chapter 12 MicroLogix 1400 Code Examples

Returns multiple blocks of user data

• Option Flag 1
Returns multiple blocks of user data and the security status of each block

IMPORTANT Unless a UUID is specified, this command operates on the first tag in
the field.

Example Routine
Rung Description
Place RFID interface into the Run Mode. The bit must be highlighted in green. If the bit is not green,
0000 right-click it and click Toggle Bit.
Read Input Image. Double-click the MSG box to enter the Setup Screen. Input Size is 116 bytes (58
0001 Words.) Click the MultiHop tab to configure an EtherNet/IP device.
Write Output Image. Double-click the MSG box to enter the Setup Screen. Output Size is 124 bytes (62
0002 Words). Click the MultiHop tab to configure an EtherNet/IP device.
The Tag Present bit is highlighted in green when a tag is present. When a tag is present, clear the
0003 command value.
When the command value has been cleared, load in the instruction parameters contained in N102
0004 (Read Multiple Blocks).
Wait for the read command to run. The Read in Progress bit is highlighted in green when the command
0005 is running. When the command has completed, the Read in Progress bit returns to its original state.
When the command has been executed and completed, copy the data that is read into N100.
0006 If there was an error with the operation, then N100:0 contains the error code.

Write Multiple Blocks The Write Multiple Blocks command (value = 11) writes multiple blocks of user data to an FRAM
tag.

IMPORTANT This command only works on FRAM tags. Unless a UUID is specified, this
command operates on the first tag in the field.

Example Routine
Rung Description
Place RFID interface into the Run Mode. The bit must be highlighted in green. If the bit is not green,
0000 right-click it and click Toggle Bit.
Read Input Image. Double-click the MSG box to enter the Setup Screen. Input Size is 116 bytes (58
0001 Words.) Click the MultiHop tab to configure an EtherNet/IP device.
Write Output Image. Double-click the MSG box to enter the Setup Screen. Output Size is 124 bytes (62
0002 Words). Click the MultiHop tab to configure an EtherNet/IP device.
The Tag Present bit is highlighted in green when a tag is present. When a tag is present, clear the
0003 command value.
When the command value has been cleared, load in the instruction parameters contained in N111
0004 (Write Multiple Blocks).
Wait for the write command to run. The Write in Progress bit is highlighted in green when the
command is running. When the command has completed, the Write in Progress bit returns to its
0005 original state. When the command has been executed and completed, copy the data that is read into
N100.
0006 If there was an error with the operation, then N100:0 contains the error code.

Input Image Layout See CIP Information on page 131 for details on the Input Image Layout.

Output Image Layout See CIP Information on page 131 for details on the Output Image Layout.

118 Rockwell Automation Publication 56RF-UM001E-EN-P - October 2022

 Chapter 13

RFID Tag Speed

Table 38…Table 41 on page 120 are guides to help determine the amount of information that
can be written to/read from an RFID tag, which is based on the speed of your application. For
example, to read 8 bytes consistently from a tag using the square transceiver, your line speed
must be 0.827 ms or slower.

If you have a high-speed application, it is best to choose the largest transceiver, larger tag,
which provides the largest antenna range. The larger tag provides the longest time that the tag
is in the field for read/write functions and also helps with tag misalignment issues.

If your tag is stopped when all read/write functions occur, and tag misalignment is not an
issue, you can use smaller transceivers.

IMPORTANT We recommend that the tag is stopped if large amounts of data are
written to/read from the tag.

Table 38 - Rectangular (80x90) Transceiver

Max Tag Speed (ms)
Bytes
Read Write
4 1.488095 1.328609
8 1.378676 1.121915
16 1.202887 0.8566533
32 0.9578544 0.5811701
64 0.6802721 0.3535235
112 0.4743833 0.2227833
160 0.3641661 0.1626369
2000 0.03674939 0.01432665

Table 39 - Square (40x40) Transceiver

Max Tag Speed (ms)
Bytes
Read Write
4 0.8928571 0.7971656
8 0.8272058 0.6731489
16 0.7217322 0.513992
32 0.5747126 0.348702
64 0.4081633 0.2121141
112 0.28463 0.13367
160 0.2184996 0.09758213
2000 0.02204964 0.008595988

Rockwell Automation Publication 56RF-UM001E-EN-P - October 2022 119

Chapter 13 RFID Tag Speed

Table 40 - M18 Transceiver

Max Tag Speed (ms)
Bytes
Read Write
4 0.1984127 0.1771479
8 0.1838235 0.1495886
16 0.1603849 0.1142204
32 0.1277139 0.07748935
64 0.09070295 0.04713646
112 0.06325111 0.02970444
160 0.04855547 0.02168492
2000 0.004899919 0.00191022

Table 41 - M30 Transceiver

Max Tag Speed (ms)
Bytes
Read Write
4 0.3373016 0.3011515
8 0.3125 0.2543007
16 0.2726544 0.1941748
32 0.2171137 0.1317319
64 0.154195 0.08013199
112 0.1075269 0.05049755
160 0.0825443 0.03686436
2000 0.008329863 0.003247374

Continuous Read Mode Command Objective

Perform tag read operations as fast as possible.

Operation
Command 5 is issued from the controller to place an interface RFID channel into continuous
read mode; no additional commands are required from the controller to retrieve information
from a tag. The read type that is issued would be a Read Multiple Block or a Read Single Block
depending on the number of blocks requested. The maximum number of blocks that can be
read at one time is 10. Each time the interface reads a tag successfully, the counter value
increments by 1. If there was an issue reading the tag, the counter value does not increment
and the ChError indicates the error code value.

While the interface is in this mode, it rejects all other commands sent to it for that channel
except a Stop Continuous Read. The interface does not perform its normal poll cycle on that
channel while it is in this mode of operation. During Continuous Read Mode, the ContReadMode
and Busy bit is set to true.

When the interface receives a stop command, Command 6, it reverts to the normal mode of
operation and resume the polling cycle. Continuous Read mode can also be canceled by
issuing a channel reset (reset bit in the output image word set to 1).

When using a 50 mm (1.97 in.) disk tag, catalog number 56RF-TR-8090 transceiver, and reading
4 bytes of data, it can be possible to achieve a line speed of up to 3 ms.

120 Rockwell Automation Publication 56RF-UM001E-EN-P - October 2022

 Chapter 13 RFID Tag Speed

Modes of Operation
Only one type of mode of operation can be used on each channel. To change modes you must
issue a Stop Continuous Read, and then reissue a Start Continuous Read with the new mode.
Both channels can be configured for the same mode or different modes simultaneously. Modes
of operation are limited based on the model number of the interface.

56RF-IN-IPS12 Interface Block

• One RFID channel (Channel 0)
• One discrete input and one discrete output
• Support modes 0 and 1 only

56RF-IN-IPD22 Interface Block

• Two RFID channels (Channel 0, Channel 1)
• One discrete input and one discrete output
• Support modes 0, and 1 only.

The single input can be used for either channel.

56RF-IN-IPD22A Interface Block

• Two RFID channels (Channel 0, Channel 1)
• Two discrete inputs
• Support modes 0, 1, 2, and 3
The same input can be used for either channel.

Mode Overview
Mode Description
The interface waits for the delay time, sends out a read, obtains data, and returns that data
1. Mode 0 back to the PLC. This cycle repeats until a Stop Continuous Read command is issued.
The interface waits for input point 0 to turn ON, waits for the delay timer to expire then sends
2. Mode 1 out a read, obtains data, and returns that data back to the PLC. This cycle repeats until a Stop
Continuous Read command is issued.
The interface waits for input point 1 to turn ON, waits for the delay timer to expire then sends
3. Mode 2 out a read, obtains data, and returns that data back to the PLC. This cycle repeats until a Stop
Continuous Read command is issued.
The interface waits for both input point 0 and 1 to turn ON, waits for the delay timer to expire
4. Mode 3 then sends out a read, obtains data, and returns that data back to the PLC. This cycle repeats
until a Stop Continuous Read command is issued.

Command Structure
a. xx:O.Channel[0].Reset =0
b. xx:O.Channel[0].Command = 5
c. xx:O.Channel[0].BlockSize = Bytes per Block in the tag
d. xx:O.Channel[0].Address = Starting Block
e. xx:O.Channel[0].Length = Number of blocks to read
f. xx:O.Channel[0].Timeout = Delay time between sending commands
g. xx:O.Channel[0].UIDLow = 0
h. xx:O.Channel[0].UIDHi = 0
i. xx:O.Channel[0].Data[0] = Mode x
j. xx:O.Channel[0].Data[1] = Option Flag

Rockwell Automation Publication 56RF-UM001E-EN-P - October 2022 121

Chapter 13 RFID Tag Speed

Table 42 - Commands
Command Description
Address Block within the tag to start read operations from.
BlockSize Size in bytes per block of the tag.
Length Number of blocks to read
Delay time between sending command attempts in Mode 0.
Timeout Delay time after input condition is true before sending commands in modes 1…3.
Can be used to target only a specific tag for read operations, otherwise this value would be 0
UIDLow/UIDHigh to read any tag.
Mode x Specifies the mode of operation for the Continuous Read.
Used to specify the mode of one or more Read Multiple/Read Single Block commands.
A zero value would only read the data that is requested starting at the address that is
specified, for the number of blocks specified in the Length field. A value of 1 would read and
return both the security block status and the tag data.
Option Flag For modes 1…3, you can either set the delay time on their own or they can train the interface
and the transceiver so that the value is determine automatically based on their system setup
and line speed. A delay time of 0 causes the interface to send out the command as soon as it
sees that the input condition goes true. For mode 0, there is no ability to train the system.

Teach Continuous Read Command Objective

This operation is valid only for modes 1…3 and is used to train the interface to the approximate
delay time that must be used before it sends out the read command, which is based on input
conditions and tag speeds.

Operation
Command 8 is issued from the Controller to place an RFID interface channel into teach mode.
When first entering Teach Mode (Phase 1), the interface waits for one or more input conditions
to go true, and then poll for tag detection. Once 10 good detections have occurred, the unit
enters phase 2.

During Phase 2, the unit waits for one or more input conditions to go true, then issues the Read
Multiple/Read Single Block command after the predetermined time delay and adjusts the delay
time as necessary. Once 10 good reads in a row have occurred, the unit exits teach mode and
reports back the average and recommended delay time in milliseconds.

If the interface is unable to obtain 10 good reads in a row, it decrements the delay time by 1 ms
and starts again in phase 2. If the delay time has been decremented more than 30 ms from the
average, the interface exits teach mode and reports back the recommended delay time of -1. A
-1 value indicates that the interface cannot determine what the best delay time would be due
to variations in tag speed.

Phase progression in teach mode can be monitored by viewing the counter value in the input
image table. Phase 1 is always a value <10, Phase 2 is always a value >10. Once the counter
reaches 20, the interface exits teach mode and reports the average and recommended delay
times. You must load the recommended delay time value into the Timeout field before
initiating a continuous read.

During Teach Mode, the ContReadMode and Busy bit are set to true.

An issued channel reset can cancel Teach mode (reset bit in the output image word set to 1).

122 Rockwell Automation Publication 56RF-UM001E-EN-P - October 2022

 Chapter 13 RFID Tag Speed

Command Structure
a. xx:O.Channel[0].Reset =0
b. xx:O.Channel[0].BlockSize =Bytes per Block in the tag
c. xx:O.Channel[0].Command = 8
d. xx:O.Channel[0].Address = Starting Block
e. xx:O.Channel[0].Length = Number of Blocks
f. xx:O.Channel[0].Timeout = 0
g. xx:O.Channel[0].UIDLow = 0
h. xx:O.Channel[0].UIDHi = 0
i. xx:O.Channel[0].Data[0] = Mode x
j. xx:O.Channel[0].Data[1] = Option Flag

Rockwell Automation Publication 56RF-UM001E-EN-P - October 2022 123

Chapter 13 RFID Tag Speed

Notes:

124 Rockwell Automation Publication 56RF-UM001E-EN-P - October 2022

 Chapter 14

RFID Interface Block Webpage

The RFID interface block webpage provides diagnostic and configuration for the RFID interface
block. You can access the webpage by entering the IP address of the interface block into a
web browser. The interface block must have Ethernet connectivity and power to be viewable
on the webpage.

Home The home page allows you to view basic information about the interface block. Data cannot be
changed on the home page. The Device Description and Device Location are specified and can
be changed on the Device Identity tab in the Configuration section.

Diagnostics The Diagnostic page has three tabs of view-only detailed information on the status of the
interface block. The tabs show Diagnostic Overview, Network Settings, and Ethernet Statistics.
The I/O Connections tab contains a field that allows you to change the webpage refresh rate.

Rockwell Automation Publication 56RF-UM001E-EN-P - October 2022 125

Chapter 14 RFID Interface Block Webpage

Network Settings

Ethernet Statistics

I/O Connections

126 Rockwell Automation Publication 56RF-UM001E-EN-P - October 2022

 Chapter 14 RFID Interface Block Webpage

Configuration To access the configuration section of the RFID interface block webpage, a username and
password are required. The default username is Admin, and there is no password by default.
The username and password can be changed on the Device Services tab.

IMPORTANT If the username and password are lost, the interface block must be
reset to default before it can be accessed again. The username and
password are reset to the default values.

Device Identity Change the device name, description, or location. Changes take place after power to the
interface block has been cycled.

Network Configuration

Rockwell Automation Publication 56RF-UM001E-EN-P - October 2022 127

Chapter 14 RFID Interface Block Webpage

Device Services

128 Rockwell Automation Publication 56RF-UM001E-EN-P - October 2022

 Appendix A

Error Codes for RFID Interface Block

Error Codes The error codes for the RFID interface block are stored in the input for each channel. In the
examples in the manual, the error codes are stored in the image table
RFID_1:I:Channel[0].ChError and RFID_1:I:Channel[1].ChError.
Error Codes Status Word Binary
0 OK 0000
1 Transceiver not found 0001
2 Invalid Response 0010
3 Invalid Parameter 0011
4 No Tag Detected 0100
5 Instruction Timed Out 0101
6 Block Access Error 0110
7 Format Error 0111
8 Tag Communications Error 1000
9 Address Error 1001
10 Mismatch Error 1010
11 Internal Channel Error 1011
12 Malformed Packet 1100
13 Unit in Program Mode 1101
14 Reserved 1110
15 Module Error 1111
16 Internal Error 10000

• OK (Decimal 0)
Indicates that there are no issues with the channel in question when the decimal value
of these bits is equal to zero.
• Transceiver not found (Decimal 1)
Indicates that communication with the transceiver for the specified channel has been
lost.
• Invalid Response (Decimal 2)
Indicates that the response to a command is not what was expected.
• Invalid Parameter (Decimal 3)
Indicates that either a passed or received parameter was out of bounds.
• No Tag Detected (Decimal 4)
Indicates that a command was attempted on a channel but no tag was detected in the
field.
• Instruction Timed Out (Decimal 5)
Indicates that the timeout value that is associated with a command was exceeded
before a response could be obtained.

Rockwell Automation Publication 56RF-UM001E-EN-P - October 2022 129

Appendix A Error Codes for RFID Interface Block

• Block Access Error (Decimal 6)

Indicates that either:
- A read command attempted to read a block but was denied access.
- A write command attempted to write to a block but was denied access.
• Format Error (Decimal 7)
Indicates that the format of the command or response was invalid.
• Tag Communications Error (Decimal 8)
Indicates that the interface block was not able to complete command execution with a
tag before the tag left the field or the Output Channel Timeout is set too short. For
example, set the Output Channel Timeout to 100 ms and then try to read 112 bytes of
data from a catalog number 56RF-TG-30 tag. This occurs when the address in Read/
Write Byte is out of the supported range.
• Address Error (Decimal 9)
Indicates that the block address value was out of bounds for the tag.
• Mismatch Error (Decimal 10)
Indicates that there are more tags that are detected in the field than the unit can
process.
• Internal Channel Error (Decimal 11)
Indicates that there is some internal issue with channel (hardware fault).
• Malformed Packet (Decimal 12)
Indicates an issue with the command packet that the transceiver received.
• Unit in Program Mode (Decimal 13)
Indicates that a command was issued but the module is in program mode.
• Module Error (Decimal 15)
Indicates that there is some internal issue interface block (hardware fault).
• Internal Error (Decimal 16)
AOI specific error.

130 Rockwell Automation Publication 56RF-UM001E-EN-P - October 2022

 Appendix B

CIP Information

Product Codes and Name Figure 43 lists the product codes and name strings for the EtherNet/IP™ interface block.
Strings Table 43 - Product Codes and Name Strings
Product Type Product Code Cat. No. Identity Object Name String
139 4 56RF-IN-IPS12 RFID Adapter 1 Port + 1In/1 Out
139 5 56RF-IN-IPD22 RFID Adapter 2 Port + 1In/1 Out
139 6 56RF-IN-IPD22A RFID Adapter 2 Port + 2In/0 Out

CIP Explicit Connection The RFID interface block allows connected explicit messages to drive user outputs when no I/
O connection exists, or when an I/O connection exists in the idle state. One EtherNet/IP Class 3
Behavior explicit connection is allowed to send explicit control messages via an Active Explicit
connection. An EtherNet/IP Class 3 explicit connection becomes the explicit control
connection when it becomes the first EtherNet/IP Class 3 explicit connection to send a set
service to one of the following:
• The Value attribute of any DOP instance (class code 0x09).
• The Data attribute of any output (consumed) Assembly Instance (class code 0x04).
• Attribute 3 or 4 of the Control Supervisor Object (class code 0x29).

CIP Objects The following CIP™ objects are covered in the following subsections. CIP objects provide a
window into the devices properties that can be read/written to. Each CIP Class contains
instances (copies of a class structure), and attributes for each instance. Most devices have
only one instance of a class.
Class Object
0x0001 Identity Object
0x0004 Assembly Object
0x0008 Discrete Input Point Object
0x0009 Discrete Output Point Object

Identity Object Class Code This Identity Object provides identification of and general information about the device.
0x0001 Instance 1 of the Identity Object contains the following attributes:
Attribute ID Access Rule Name Data Type Value
1 Get Vendor UINT 1
2 Get Device Type UINT 139
3 Get Product Code UINT 4, 5, or 6
Revision Structure of: The initial release is Major Rev. 1, Minor
4 Get Major Revision USINT Rev. 1.
Minor Revision USINT
5 Get Status WORD See Table 44 on page 133.
6 Get Serial Number UDINT Unique number for each device
Product Name Structure of:
7 Get String Length USINT Product Code specific
ASCII String STRING

Rockwell Automation Publication 56RF-UM001E-EN-P - October 2022 131

Appendix B CIP Information

The following common services are implemented for Instance 1.

Implemented for:
Service Code Service Name
Class Instance
0x01 Yes Yes Get_Attributes_All
0x05 No Yes Reset
0x0E Yes Yes Get_Attributes_Single

To access the Identity Object, the creation of a Message Instruction (MSG) to be configured as
a CIP Generic type is required.

• Service Code: 1- Get Attribute All

• Class: 1 - Identity Object
• Instance: 1 - First instance
• Attribute: 1 - First attribute
• Destination: CIP_Data - a SINT[100] array to hold the data

• CIP_Data[0]…[1]= Vendor (1=Allen-Bradley)

• CIP_Data[2]…[3]= Device Type (139=RFID)
• CIP_Data[4]…[5]=Device Code (5=56RF-IN-IPS12)
• CIP_Data[6]= Major Revision (1)
• CIP_Data[7]= Minor Revision (1)
• CIP_Data[8]…[9]= Status (100 decimal, 000000001100100 binary)
• CIP_Data[10]…[13]= Serial Number (A000B955)
• CIP_Data[14]= Product Name Length (32 bytes)
• CIP_Data[15]-[n]= Product Name

132 Rockwell Automation Publication 56RF-UM001E-EN-P - October 2022

 Appendix B CIP Information

Device Status (CIP_Data[8…9])

Table 44 - Device Status (CIP_Data[8…9])

Bits Name Description
0 Owned 0=Not Owned, 1=Owned by a Master
1 Reserved Reserved
2 Configured 0=Not configured, 1=Configured
3 Reserved Reserved
4…7 Extended Device Status See Table 45
8 Minor Recoverable Fault 1=Detected a recoverable minor fault
9 Minor Unrecoverable Fault 1=Detected a nonrecoverable minor fault
10 Major Recoverable Fault 1=Detected a recoverable major fault
11 Major Unrecoverable Fault 1=Detected a nonrecoverable major fault
12…15 Reserved Reserved
Values for the Extended Device Status (Bits 4…7)

Table 45 - Values for the Extended Device Status (Bits 4…7)

Value Description
0 Self-Testing or Unknown
1 Firmware Update in Progress
2 At least one faulted I/O connection
3 No I/O connections established
4 Non-Volatile Configuration Bad
5 Major Fault
6 At least one I/O connection in run mode
7 At least one I/O connection is established, all in idle mode
8&9 Reserved
10…15 Vendor specific

Assembly Object Class Code The Assembly Object binds attributes of multiple objects, which allows data to be sent to or
received from each object over one connection. Controllers that cannot create and establish a
0x0004 class 1 (scheduled) connection can use the Assembly Object in a message instruction to obtain
both the input and output assemblies of the RFID interface.

The following services are implemented for the Assembly Object:

Implemented for:
Service Code Service Name
Class Instance
0x0E Yes Yes Get_Attribute_Single
0x10 No Yes Set_Attribute_Single
0x18 No Yes Get_Member

Different connection instances are needed for each RFID interface, which is based on the
model. These class 3 connection instances are different than the class 1 instances that are
used by a ControlLogix® or CompactLogix™ processor due to the limitations within the SLC™
and MicroLogix™ for handling Send and Receive data.

Use Table 46 to determine the class 3 connection instance and Send/Receive size for your
unit.
Class 3 Connection Instances with Size (in bytes)

Table 46 - Class 3 Connection Instances with Size (in bytes)

Cat. No. Input Size Output Size Config Size
56RF-IN-IPS12 120 64 130 64 103 16
56RF-IN-IPD22 121 116 131 124 109 20
56RF-IN-IPD22A 122 116 132 124 112 24

Rockwell Automation Publication 56RF-UM001E-EN-P - October 2022 133

Appendix B CIP Information

Read the Input Image Table

of a 56RF-IN-IPD22
Interface Block with a
MicroLogix 1400

• N10:0 is the data table address where the input image is stored and spans
N10:0…N10:57.
• The number of bytes to receive is 116 (58 words).
• The extended routing file (RIX11:0) is used to store the Multi-Hop routing information.
• Service is type Read Assembly
• Class 4 is the Assembly Instance Class
• Instance 79h is the input image connection instance.
• Attribute 3 is the assembly attribute for the input image table

The Multi-Hop information is used to configure the communications path from the MicroLogix
to the RFID interface.

134 Rockwell Automation Publication 56RF-UM001E-EN-P - October 2022

 Appendix B CIP Information

Input Image (56RF-IN-IPD22 Interface Block)

Word Description Word Description
N10:0 – N10:1 Module Connection Status N10:9 Length
N10:2 Module Status N10:10 – N10:31 Data
N10:3 Reserved N10:32 Channel[1] Diagnostics
N10:4 Block Status N10:33 Command Value
N10:5 I/O Data N10:34 Counter Value
N10:6 Channel[0] Diagnostics N10:35 Length
N10:7 Command Value N10:36 – N10:57 Data
N10:8 Counter Value

Module Status
Bit Definition Bit Definition
0 Run Status 8 Reserved
1 Block Fault 9 Reserved
2 Aux Power Fault 10 Reserved
3 Reserved 11 Reserved
4 Pt00 Input Fault 12 Pt00 Output Fault
5 Pt00 Open Wire 13 Pt00No Load
6 Pt00 Input Short Circuit 14 Pt00 Output Short Circuit
7 Reserved 15 Reserved

I/O Data
Bit Definition Bit Definition
0 Pt00 Data 8 Pt00 Readback
1 Reserved 9 Reserved
2 Reserved 10 Reserved
3 Reserved 11 Reserved
4 Reserved 12 Reserved
5 Reserved 13 Reserved
6 Reserved 14 Reserved
7 Reserved 15 Reserved

Channel[n] Diagnostics
Bit Definition Bit Definition
0 Reset 8 Error Code
1 Fault 9 Error Code
2 Tag Present 10 Error Code
3 Busy 11 Error Code
4 Reset in Progress 12 Reserved
5 Continuous Read Mode 13 Reserved
6 Reserved 14 Reserved
7 Reserved 15 Reserved

Rockwell Automation Publication 56RF-UM001E-EN-P - October 2022 135

Appendix B CIP Information

Input Image (56RF-IN-IPD22A Interface Block)

Word Description Word Description
N10:0 – N10:1 Module Connection Status N10:9 Length
N10:2 Module Status N10:10 – N10:31 Data
N10:3 Reserved N10:32 Channel[1] Diagnostics
N10:4 Block Status N10:33 Command Value
N10:5 I/O Data N10:34 Counter Value
N10:6 Channel[0] Diagnostics N10:35 Length
N10:7 Command Value N10:36 – N10:57 Data
N10:8 Counter Value

Module Status
Bit Definition Bit Definition
0 Run Status 8 Pt01 Input Fault
1 Block Fault 9 Pt01 Open Wire
2 Aux Power Fault 10 Pt01 Input Short Circuit
3 Reserved 11 Reserved
4 Pt00 Input Fault 12 Reserved
5 Pt00 Open Wire 13 Reserved
6 Pt00 Input Short Circuit 14 Reserved
7 Reserved 15 Reserved

I/O Data
Bit Definition Bit Definition
0 Pt00 Data 8 Reserved
1 Pt01 Data 9 Reserved
2 Reserved 10 Reserved
3 Reserved 11 Reserved
4 Reserved 12 Reserved
5 Reserved 13 Reserved
6 Reserved 14 Reserved
7 Reserved 15 Reserved

Channel[n] Diagnostics
Bit Definition Bit Definition
0 Reset 8 Error Code
1 Fault 9 Error Code
2 Tag Present 10 Error Code
3 Busy 11 Error Code
4 Reset in Progress 12 Reserved
5 Continuous Read Mode 13 Reserved
6 Reserved 14 Reserved
7 Reserved 15 Reserved

136 Rockwell Automation Publication 56RF-UM001E-EN-P - October 2022

 Appendix B CIP Information

Input Image (56RF-IN-IPS12 Interface Block)

Word Description Word Description
N10:0 – N10:1 Module Connection Status N10:6 Channel[0] Diagnostics
N10:2 Module Status N10:7 Command Value
N10:3 Reserved N10:8 Counter Value
N10:4 Block Status N10:9 Length
N10:5 I/O Data N10:10 – N10:31 Data

Module Status
Bit Definition Bit Definition
0 Run Status 8 Reserved
1 Block Fault 9 Reserved
2 Aux Power Fault 10 Reserved
3 Reserved 11 Reserved
4 Pt00 Input Fault 12 Pt00 Output Fault
5 Pt00 Open Wire 13 Pt00 No Load
6 Pt00 Input Short Circuit 14 Pt00 Output Short Circuit
7 Reserved 15 Reserved

I/O Data
Bit Definition Bit Definition
0 Pt00 Data 8 Pt00 Readback
1 Reserved 9 Reserved
2 Reserved 10 Reserved
3 Reserved 11 Reserved
4 Reserved 12 Reserved
5 Reserved 13 Reserved
6 Reserved 14 Reserved
7 Reserved 15 Reserved

Channel[n] Diagnostics
Bit Definition Bit Definition
0 Reset 8 Error Code
1 Fault 9 Error Code
2 Tag Present 10 Error Code
3 Busy 11 Error Code
4 Reset in Progress 12 Reserved
5 Continuous Read Mode 13 Reserved
6 Reserved 14 Reserved
7 Reserved 15 Reserved

Rockwell Automation Publication 56RF-UM001E-EN-P - October 2022 137

Appendix B CIP Information

Write to the Output Image

Table of a 56RF-IN-IPD22
Interface Block with a
MicroLogix 1400

• N20:0 is the data table address to store the output image and spans N20:0…N20:61.
• The number of bytes to send is 124 (62 words).
• The extended routing file (RIX12:0) is used to store the Multi-Hop routing information.
• Service is type Write Assembly
• Class 4 is the Assembly Instance Class
• Instance 83h is the output image connection instance.
• Attribute 3 is the assembly attribute for the output image table

The Multi-Hop information is used to configure the communications path from the MicroLogix
to the RFID interface.

138 Rockwell Automation Publication 56RF-UM001E-EN-P - October 2022

 Appendix B CIP Information

Input Image (56RF-IN-IPD22 Interface Block)

Word Description Word Description
N20:0 Module Data N20:12…N10:31 Data
N20:1 Reserved N20:32 Channel[1] Reset
N20:2 Channel[0] Reset N20:33 Block Size
N20:3 Block Size N20:34 Command
N20:4 Command N20:35 Address
N20:5 Address N20:36 Length
N20:6 Length N20:37 Timeout
N20:7 Timeout N20:38…N20:39 UIDLow
N20:8…N20:9 UIDLow N20:40…N20:41 UIDHi
N20:10…N20:11 UIDHi N20:42…N20:61 Data

Module Data
Bit Definition Bit Definition
0 Run Mode 8 Pt00 Data
1 Reserved 9 Reserved
2 Reserved 10 Reserved
3 Reserved 11 Reserved
4 Reserved 12 Reserved
5 Reserved 13 Reserved
6 Reserved 14 Reserved
7 Reserved 15 Reserved

Input Image (56RF-IN-IPD22A Interface Block)

Word Description Word Description
N20:0 Module Data N20:12…N10:31 Data
N20:1 Reserved N20:32 Channel[1] Reset
N20:2 Channel[0] Reset N20:33 Block Size
N20:3 Block Size N20:34 Command
N20:4 Command N20:35 Address
N20:5 Address N20:36 Length
N20:6 Length N20:37 Timeout
N20:7 Timeout N20:38…N20:39 UIDLow
N20:8…N20:9 UIDLow N20:40…N20:41 UIDHi
N20:10…N20:11 UIDHi N20:42…N20:61 Data

Module Data
Bit Definition Bit Definition
0 Run Mode 8 Reserved
1 Reserved 9 Reserved
2 Reserved 10 Reserved
3 Reserved 11 Reserved
4 Reserved 12 Reserved
5 Reserved 13 Reserved
6 Reserved 14 Reserved
7 Reserved 15 Reserved

Rockwell Automation Publication 56RF-UM001E-EN-P - October 2022 139

Appendix B CIP Information

Input Image (56RF-IN-IPS12 Interface Block)

Word Description Word Description
N20:0 Module Data N20:6 Length
N20:1 Reserved N20:7 Timeout
N20:2 Channel[0] Reset N20:8…N20:9 UIDLow
N20:3 Block Size N20:10…N20:11 UIDHi
N20:4 Command N20:12…N10:31 Data
N20:5 Address

Module Data
Bit Definition Bit Definition
0 Run Mode 8 Pt00 Data
1 Reserved 9 Reserved
2 Reserved 10 Reserved
3 Reserved 11 Reserved
4 Reserved 12 Reserved
5 Reserved 13 Reserved
6 Reserved 14 Reserved
7 Reserved 15 Reserved

Read the Input Image Table

of a 56RF-IN-IPD22
Interface Block with an
SLC-5/05

The main difference between the MicroLogix 1400 and the SLC-5/05 is that the SLC uses an
EEM instruction instead of an MSG instruction, but the setup is similar. The routing information
for the EEM is stored within the Control Block address (N30:0)
• N10:0 is the data table address where the input image is stored and spans
N10:0…N10:57.
• The size in words is 58 (116 bytes).
• Service is type Read Assembly
• Class 4 is the Assembly Instance Class
• Instance 79h is the input image connection instance.
• Attribute 3 is the assembly attribute for the input image table

140 Rockwell Automation Publication 56RF-UM001E-EN-P - October 2022

 Appendix B CIP Information

• N20:0 is the data table address to store the output image and spans N20:0…N20:61.
• The Send Data size is 62 (124 bytes).
• Service is type Write Assembly
• Class 4 is the Assembly Instance Class
• Instance 83h is the output image connection instance.
• Attribute 3 is the assembly attribute for the output image table

Rockwell Automation Publication 56RF-UM001E-EN-P - October 2022 141

Appendix B CIP Information

Class 1 Connections Class 1 connections are used to transfer I/O data, and can be established to the Assembly
Object instances. Each Class 1 connection establishes two data transports, one consuming and
one producing. The heartbeat instances are used for connections that can access only inputs.
Class 1 uses UDP transport.
• Total number of supported Class 1 connections equals 2 (total for: exclusive owner +
input only + listen-only)
• Supported API: 2…3200 ms (The minimum API can be higher if processor resources
become a problem)
• T->O Connection type: Point-to-point, multicast
• O->T Connection type: Point-to-point
• Supported trigger type: Cyclic, change of state

The producing instance can be assigned to multiple transports, with any combination of
multicast and point-to-point connection types.

Only one Exclusive-owner connection is supported at each time. If an Exclusive-owner

connection is already established and an originator tries to establish a new Exclusive-owner
connection, an Ownership conflict (general status = 0x01, extended status = 0x0106) error code
is returned.

For a connection to be established, the requested data sizes must be an exact match of the
connections points that the connection tries to connect to. If the requested and actual sizes
do not match, an Invalid connection size (general status = 0x01, extended status = 0x0109)
error code is returned.

Exclusive Owner This connection type is used for controlling the outputs of the module and must not be
dependent on any other condition. Only one exclusive owner connection can be opened
Connection against the module.

If an exclusive owner connection is already opened a Connection in use (general status = 0x01,
extend status = 0x0100) error code is returned.
• Connection point O -> T must be Assembly Object, Instance 3, 162 or 166 (162 for product
codes <= 0x100 only, 166 for product codes > 0x100 only).
• Connection point T -> O must be Assembly Object, Instance 52, 150 or 151 (150 for
product codes <= 0x100 only, 151 for product codes > 0x100 only).

Input Only Connection This connection is used to read data from the module without controlling the outputs. This
connection is not dependent on any other connection.

It is recommended that the originator sets the data size in the O->T direction of the
Forward_Open to zero.

IMPORTANT If an exclusive owner connection is opened against the module and

times out, the input only connection times out as well. If the exclusive
owner connection is properly closed, the input only connection is not be
affected.

• Number of supported input only connections equals two (shared with exclusive owner
and listen-only connection).
• Connection point O -> T must be Assembly Object, Instance 191 (Input only heartbeat).
• Connection point T -> O must be Assembly Object, Instance 52, 150, or 151 (150 for
product codes <= 0x100 only, 151 for product codes > 0x100 only).

142 Rockwell Automation Publication 56RF-UM001E-EN-P - October 2022

 Appendix B CIP Information

Listen-only Connection This connection is dependent on another connection to exist. If that connection(exclusive
owner or input only) is closed, the listen-only connection must be closed as well.

It is recommended that the originator sets the data size in the Forward_Open to zero.
• Number of supported listen-only connections equals two (shared with exclusive owner
and listen-only connection).
• Connection point O -> T must be Assembly Object, Instance 192 (listen-only heartbeat)
• Connection point T -> O must be Assembly Object, Instance 52, 150 or 151 (150 for
product codes <= 0x100 only, 151 for product codes > 0x100 only)

Class 3 Connections Class 3 connections are used to establish connections to the message router. The connection
is used for Explicit Messaging. Class 3 connections use TCP connections.
• Three concurrent encapsulation sessions are supported
• Six concurrent Class 3 connections are supported
• Multiple Class 3 connections per encapsulation session are supported
• Supported API: 100…10000 ms
• T->O Connection type: Point-to-point
• O->T Connection type: Point-to-point
• Supported trigger type: Application

Discrete Input Point Object The following class attributes are currently supported for the Discrete Input Point Object:
Class Code 0x0008 Attribute ID Access Rule Name Data Type Value
1 Get Revision 0xC7 2
2 Get Max Instance UINT 4

Two instances of the Discrete Input Point Object are supported. All instances contain the
following attributes.
Attribute ID Access Rule Name Data Type Value
3 Get Value BOOL 0 = OFF, 1 = ON
0 = No delay
1000 = 1 ms
2000 = 2 ms
5 FilterOffOn 0xC7 4000 = 4 ms
8000 = 8 ms
16000 = 16 ms
0 = No delay
1000 = 1 ms
2000 = 2 ms
6 FilterOnOff 0xC7 4000 = 4 ms
8000 = 8 ms
16000 = 16 ms

The following common services are implemented for the Discrete Input Point Object.
Implemented for:
Service Code Service Name
Class Instance
0x0E Yes Yes Get_Attribute_Single
0x10 No Yes Set_Attribute_Single

Rockwell Automation Publication 56RF-UM001E-EN-P - October 2022 143

Appendix B CIP Information

To obtain the status of an input point (ON or OFF), configure a CIP message as shown in
Figure 34
Figure 34 - Obtain Status of Input

Instance 1 is the first input (Pt00), if the RFID interface supports two inputs, then Pt01 would be
instance 2.

The return value in CIP_Data[0] is either 0 (Input OFF) or 1 (Input ON).

To obtain the Input Filter Off/On value of an input point, configure a CIP message as shown in
Figure 35:
Figure 35 - Obtain Input Filter Off/On Value

Instance 1 is the first input (Pt00), if the RFID interface supports two inputs, then Pt01 would be
instance 2.

The return value contains the filter time in milliseconds.

144 Rockwell Automation Publication 56RF-UM001E-EN-P - October 2022

 Appendix B CIP Information

Discrete Output Point Object The following class attributes are supported:
Class Code 0x0009 Attribute ID Access Rule Name Data Type Value
1 Get Revision 0xC1 1
2 Get Max Instance UINT 4 or 10

Two instances of the Discrete Output Point Object are supported. All instances contain the
following attributes.
Attribute ID Access Rule Name Data Type Value
3 Get Value BOOL 0 = OFF, 1 = ON
0 = Use Fault Value
5 Get/Set FaultMode BOOL 1 = Hold Last State
0 = OFF
6 Get/Set FaultValue BOOL 0 = ON
0 = Use Program Value
7 Get/Set ProgMode BOOL 1 = Hold Last State
0 = OFF
8 Get/Set ProgValue BOOL 1 = ON

The following common services are implemented for the Discrete Output Point Object.
Implemented for:
Service Code Service Name
Class Instance
0x0E Yes Yes Get_Attribute_Single
0x10 No Yes Set_Attribute_Single

To obtain the state of an output point, configure a CIP message as shown in Figure 36:
Figure 36 - Obtain State of Output

The return value contains the state of the output (0=Off, 1=On)

To set the state of an output point, configure a CIP message as shown in Figure 37 on
page 146:

Rockwell Automation Publication 56RF-UM001E-EN-P - October 2022 145

Appendix B CIP Information

Figure 37 - Set State of Output

CIP_Data_Source is a SINT that contains the value to set the output too
(0=Off, 1=On).

146 Rockwell Automation Publication 56RF-UM001E-EN-P - October 2022

 Appendix C

Install the Add-on Profile

Introduction This appendix goes through the Add-on Profile (AOP) of the RFID transceivers with the RSLogix
5000® program. AOPs are files that you add to your Rockwell Automation® library. These files
contain the pertinent information for configuring a device that is added to the Rockwell
Automation network.
The AOP simplifies the setup of devices. The AOP presents the necessary fields in an organized
fashion, which allows you to create and configure your system in a quick and efficient manner.

The AOP is a folder that contains numerous files for the device. It comes as an installation
package. Follow the on-screen instructions to install the AOP.
1. In the File Explorer, locate the directory where the installation files were extracted.
2. Click MPSetup.exe

3. The window identifies the module profiles and the firmware revision. Click Next.

Rockwell Automation Publication 56RF-UM001E-EN-P - October 2022 147

Appendix C Install the Add-on Profile

4. Accept the terms of the license agreement and click Next.

5. With Install selected, click Next.

6. The profile name appears in the left-hand box and its details appear in the right-hand
box. Verify that the module name is correct.
Click Install.

148 Rockwell Automation Publication 56RF-UM001E-EN-P - October 2022

 Appendix D

Troubleshooting

Common Solutions Table 47 lists common problems and solutions for the RFID system.
Table 47 - Problems/Solutions
Problem Solution
The RFID interface is shipped with DHCP/BootP enabled and does have an
I just hooked this unit up assigned EtherNet/IP™ address unless the MAC address of the RFID is in the
out-of-the-box and cannot see relationship list. There are three rotary switches on the RFID interface (all set
the RFID interface in the RSLinx to 0 by default), adjust the switches to a valid IP address in the range of
software. 192.168.1.xxx where xxx is the position of the three rotary switches. Once the
switches are in place, cycle power to the RFID interface.
Open the properties of the RFID interface in the RSLogix 5000® software and
verify:
The Inhibit Module box in the connection tab is not checked.
The IP address in the General Tab is the same as the IP address configured in
I am getting a yellow triangle in the RFID interface.
the RSLogix 5000 software for my The IP address of the RFID interface is on the same subnet as the Ethernet
RFID interface. module in the Logix rack.
Also, verify that the RFID interface has power by checking that the Aux Power
status indicator is steady green, the MOD status indicator is steady green, the
Link 1 status indicator is flashing green, and the NET status indicator is steady
green.
My RFID channel[x] status Flashing red indicates no communications between the interface and the
indicator is flashing red on the transceiver. Check cables between the RFID interface and transceiver. Verify
interface. that the power status indicator on the transceiver is green.
When I put a tag in the RFID field When one or more RFID tags are detected in the field, the status indicators on
the status indicator on my the interface and transceiver turn amber, which indicates tag presence. When
transceiver and interface turns no tags are detected, the status indicators turn green indicating that no tags
amber. are detected but communications are healthy.
When I put a tag in the RFID field
the power status indicator on the
transceiver is steady green, the Verify that the RFID tag is an ICODE compatible or SL2 style tag. The RFID
R/W Status status indicator is interface is not to detect proprietary tag types.
steady green, and the status
indicator for that channel is
steady green.

Rockwell Automation Publication 56RF-UM001E-EN-P - October 2022 149

Appendix D Troubleshooting

Notes:

150 Rockwell Automation Publication 56RF-UM001E-EN-P - October 2022

 Index

Numerics Class Code 0x0001

identity object 131
5069-SERIAL Class Code 0x0004
configuration 69 assembly object 133
888
Class Code 0x0008
IP address 39
discrete input point object 143
Class Code 0x0009
A discrete output point object 145
clear
accessory multiple bytes 75
product selection 25 code
Add-On instruction 63
product 131
ADDR command
setting restriction 71 read byte 89
address routine 73
MAC 47 write byte 99
advanced IP address 34 command objective 120, 122
AFI command structure 121, 123
definition 9 commands
lock 85 RFID 61
write 98 compatibility
AOI 63 backward 13
definition 9 configuration 127
input tag 64
installation 70 5069-SERIAL 69
image table and tag 54
interface tag 67
network 127
output tag 66
connection
sample code precondition 72
specification 64 Class 1 142
AOP Class 3 143
digital input 29
definition 9
digital output 29
assembly object
EtherNet/IP 30
Class Code 0x0004 133 exclusive owner 142
auxiliary power connection 27 I/O 126
input only 142
listen-only 143
B transceiver 29
backward compatibility 13 connection tab 48
block continuous read
interface 15 mode 120
lock 86 teach 122
block read continuous read mode 109
multi-tag 91
block write
multi-tag 105
D
bytes daisy chain
clear multiple 75 power connection 28
default
password 127
C username 127
cable definition
overview 27 module 48
change device
IP address 37 service 128
CIP device identity 127
explicit connection behavior 131 device level ring topology 32
CIP object 131 DFSID
Class 1 connection 142 definition 9
Class 3 connection 143 DHCP
definition 9

Rockwell Automation Publication 56RF-UM001E-EN-P - October 2022 151

Index

diagnostics 125 I
digital input
I/O
connection 29
connection 126
digital output
identity
connection 29
device 127
discrete input point object
identity object
Class Code 0x0008 143
Class Code 0x0001 131
discrete output point object
IEC
Class Code 0x0009 145
definition 9
DLR 32
image table
DNS configuration 54
definition 9 input 55
DOS output 57
definition 9 indicator
DSFID status 16, 17
lock 88 initial state
write 101 R/W status indicator 72
input
E image table and tag 55
input channel tag 56
EAS input image
definition 9 layout 118
environment setup 69 input image table
error code 129 read
Ethernet with MicroLogix 1400 134
statistics 126 read with SLC-5/05 140
EtherNet/IP 24 input only connection 142
connection 30 input tag
interface block product selection 24 AOI 64
exclusive owner connection 142 installation
explicit connection behavior AOI 70
CIP 131 INT
definition 9
interface block 15, 24
F interface tag
fastening 41 AOI 67
FE internet protocol tab 50
definition 9 inventory 82
ferroelectric random access memory 23 IP address
field map 888 39
transceiver 42 advanced 34
FRAM 23 change 37
definition 9 fundamental 33
fundamental IP address 33 ISO
definition 9

G
J
general tab 47
get JTC
multiple block security status 77 definition 9
system information 79
version information 81 L
layout
H input image 118
high-frequency output image 118
lean (SLI-L) 22
tag 64
transceiver 63 Linear topology 31
home 125 listen-only connection 143
lock
AFI 85
block 86
DSFID 88

152 Rockwell Automation Publication 56RF-UM001E-EN-P - October 2022

 Index

M overview
cable 27
MAC address 47
mode 121
definition 9
MACID
definition 9 P
main components
password
product selection 24
default 127
main routine 73
port configuration tab 50
memory structure
power connection
tag 18
auxiliary 27
metal surface
daisy chain 28
spacing next to 42 option 28
mode power up
continuous read 109, 120 transceiver 18
overview 121 product code 131
mode of operation 121
product selection 24
module definition 48
module info tab 49
modules Q
supported (AOI) 63 QD
multiple block
definition 9
read 93
multiple block security status
get 77 R
multiple blocks
read
read 117
input image table
write 102, 118 with MicroLogix 1400 134
multiple bytes
with SLC-5/05 140
clear 75 multiple block 93
multi-tag multiple blocks 117
block write 105 single block 95
multi-tag block read 91 transceiver setting 97
read byte 115
command 89
N routine 111
name string 131 resource 10
network restriction
configuration 127 ADDR setting 71
network address RFID
set 33 defined 11
network setting 126 definition 9
tag 18
RFID commands 61
O routine
command 73
object main 73
CIP 131 read byte 111
operation 120, 122
mode 121
option S
power connection 28 sample code precondition
output
AOI 72
image table and tag 57 SB
output channel tag 58
definition 9
output image secure (SLI-S) 21
layout 118 security status
output image table get multiple block 77
write service
with MicroLogix 1400 138
device 128
output tag
set
AOI 66
network address 33
setting
network 126

Rockwell Automation Publication 56RF-UM001E-EN-P - October 2022 153

Index

setting restriction transceiver 17

ADDR 71 connection 29
setup field map 42
environment 69 high-frequency 63
system 13 power up sequence 18
single block product selection 24
read 95 read setting 97
write 107 spacing 41
SINT status indicator 17
definition 9
SLI 20 U
SLI-L 22
UID
SLI-S 21
definition 9
smart label IC 21, 22 username
spacing default 127
next to metal surface 42 UUID
transceiver 41 definition 9
specification
AOI 64
Star topology 31 V
statistics version information
Ethernet 126 get 81
status indicator
initial state 72
interface block 16 W
transceiver 17
structure warning statement
command 121, 123 Taiwan NCC 12
support command 68 write
supported modules AFI 98
DSFID 101
AOI 63 multiple blocks 102, 118
system output image table
more than 4 A 28 with MicroLogix 1400 138
setup 13 single block 107
system information write byte 117
get 79 command 99

T
tab
connection 48
general 47
internet protocol 50
module info 49
port configuration 50
tag
configuration 54
high-frequency 64
input 55
input channel 56
memory structure 18
output 57
output channel 58
product selection 25
RFID 18
Taiwan NCC warning statement 12
teach
continuous read 122
topology
device level ring 32
Linear 31
Star 31

154 Rockwell Automation Publication 56RF-UM001E-EN-P - October 2022

 RFID Systems User Manual

Notes:

Rockwell Automation Publication 56RF-UM001E-EN-P - October 2022 155

Rockwell Automation Support
Use these resources to access support information.
Find help with how-to videos, FAQs, chat, user forums, Knowledgebase, and product
Technical Support Center rok.auto/support
notification updates.
Local Technical Support Phone Numbers Locate the telephone number for your country. rok.auto/phonesupport
Quickly access and download technical specifications, installation instructions, and user
Technical Documentation Center rok.auto/techdocs
manuals.
Literature Library Find installation instructions, manuals, brochures, and technical data publications. rok.auto/literature
Product Compatibility and Download Center Download firmware, associated files (such as AOP, EDS, and DTM), and access product rok.auto/pcdc
(PCDC) release notes.

Documentation Feedback
Your comments help us serve your documentation needs better. If you have any suggestions on how to improve our content, complete the
form at rok.auto/docfeedback.

Waste Electrical and Electronic Equipment (WEEE)

At the end of life, this equipment should be collected separately from any unsorted municipal waste.

Rockwell Automation maintains current product environmental compliance information on its website at rok.auto/pec.

Allen-Bradley, CompactLogix, ControlLogix, expanding human possibility, Logix 5000, MicroLogix, Rockwell Automation, Rockwell Software, RSLinx, RSLogix, RSLogix 5000, SLC, Studio 5000, and
Studio 5000 Logix Designer are trademarks of Rockwell Automation, Inc.
CIP and EtherNet/IP are trademarks of ODVA, Inc.
Trademarks not belonging to Rockwell Automation are property of their respective companies.
Rockwell Otomasyon Ticaret A.Ş. Kar Plaza İş Merkezi E Blok Kat:6 34752, İçerenköy, İstanbul, Tel: +90 (216) 5698400 EEE Yönetmeliğine Uygundur

Publication 56RF-UM001E-EN-P - October 2022

Supersedes Publication 56RF-UM001D-EN-P - November 2021 Copyright © 2022 Rockwell Automation, Inc. All rights reserved. Printed in the U.S.A.