HUB-04-CP-01T - Balluffusa.balluff.com/manuals/Balluff_EMS RFID(Former Datalogic)/HUB-04... · EMS...

scort Memory Systems reserves the right to make modifications andimprovements to its products and/or documentation without prior notification.Escort Memory Systems shall not be liable for technical or editorial errors or

omissions contained herein, nor for incidental or consequential damages resultingfrom the use of this material.

The text and graphic content of this publication may be used, printed and distributedonly when all of the following conditions are met:

• Permission is first obtained from Escort Memory Systems.

• The content is used for non-commercial purposes only.

• Copyright information is clearly displayed (Copyright © 2007, Escort MemorySystems, All Rights Reserved).

• The content is not modified.

The following are trademarks and/or registered trademarks of Escort MemorySystems, a Datalogic Group Company: Escort Memory Systems®, and the EscortMemory Systems logo, Subnet16™, Cobalt HF™, RFID AT WORK™, C-Macro™, C-MacroBuilder™, CBx™ and Cobalt HF Dashboard™.

Third party product names mentioned herein are used for identification purposes onlyand may be trademarks and/or registered trademarks of their respective companies:Philips, Texas Instruments, Infineon, Belden, and Microsoft.

ESCORT MEMORY SYSTEMS

HUB-04-TCP-01Subnet16 TCP/IP Hub - Operator s ManualFor the HUB-04-TCP-01 TCP/IP Hub Interface Module

Publication P/N: 17-1309 REV 02 (06/07)

COPYRIGHT © 2005-2007 ESCORT MEMORY SYSTEMS, ALL RIGHTS RESERVED, PUBLISHED IN USA.

E

ESCORT MEMORY SYSTEMS

HUB-04-TCP-01Subnet16 TCP/IP Hub Interface Module

OPERATOR S MANUALHow to Install, Configure and Operate

Escort Memory Systems

Subnet16 TCP/IP Hub

H U B - 0 4 - T C P - 0 1 R E G U L A T O R Y C O M P L I A N C EO P E R A T O R S M A N U A L

REGULAT ORY COMPLIANCE

F C C P A R T 1 5 . 1 0 5This equipment has been tested and found to comply with the limits for a Class Bdigital device, pursuant to part 15 of the FCC Rules. These limits are designed toprovide reasonable protection against harmful interference in a residential installation.This equipment uses, generates, and can radiate radio frequency energy and, if notinstalled and used in accordance with these instructions, may cause harmfulinterference to radio communications. However, there is no guarantee thatinterference will not occur in a particular installation. If this equipment does causeharmful interference to radio or television reception, which can be determined byturning the equipment off and on, the user is encouraged to try to correct theinterference by one or more of the following measures:

• Reorient or relocate the receiving antenna.

• Increase the separation between the equipment and receiver.

• Connect the equipment into an outlet on a circuit different from that to which thereceiver is connected.

• Consult your dealer or an experienced radio/TV technician for assistance.

F C C P A R T 1 5 . 2 1Users are cautioned that changes or modifications to the unit not expressly approvedby Escort Memory Systems may void the user’s authority to operate the equipment.

This device complies with Part 15 of the FCC Rules. Operation is subject to thefollowing two conditions: (1) This device may not cause harmful interference, and (2)this device must accept any interference that may cause undesired operation.”

C EThis product is compliant to CE requirements and has been tested and complies withEN 60950

T E L E CThis product complies with TELEC Regulations for Enforcement of the Radio LawArticle 6, section 1, No. 1. (PENDING)

H U B - 0 4 - T C P - 0 1 C O N T E N T SO P E R A T O R S M A N U A L

P / N : 1 7 - 1 3 0 9 R E V 0 2 ( 0 6 / 0 7 ) P A G E 5 O F 7 4

CONTENTS

CONTENTS .................................................................................... 5

LIST OF TABLES ............................... ............................... ............. 8

LIST OF FIGURES.......................................................................... 9

CHAPTER 1: GETTING STARTED ................................................ 101.1 INTRODUCTION.......................................................................................10

1.1.1 Company Background ............................................................................ 101.1.2 EMS Subnet16™ Hubs ........................................................................... 10

1.2 SUBNET16 HUB FEATURES......................................................................111.3 ABOUT THIS MANUAL..............................................................................12

1.3.1 Who Should Read this Manual? .............................................................. 121.3.2 HEX Notation......................................................................................... 12

1.4 HUB DIMENSIONS ...................................................................................131.5 INSTALLATION GUIDELINES .....................................................................14

1.5.1 Hardware Requirements ......................................................................... 141.5.2 Installation Precautions .......................................................................... 141.5.3 Network & Power Considerations ............................................................ 14

1.6 INSTALLING THE HUB ..............................................................................15

CHAPTER 2: HUB OVERVIEW...................................................... 172.1 OPERATING MODES ................................................................................17

2.1.1 Subnet16™ ........................................................................................... 172.1.2 Mux32™................................................................................................ 17

2.2 LED INDICATORS ...................................................................................182.2.1 Active and Presence LEDs ..................................................................... 192.2.2 HUB Status LEDs .................................................................................. 202.2.3 I/O LEDs ............................................................................................... 212.2.4 Ethernet Port LEDs ................................................................................ 21

2.3 DIP-SWITCH SETTINGS ...........................................................................222.3.1 DIP-Switch 1: “Run Mode / Idle Mode” ..................................................... 232.3.2 DIP-Switch 2: “Operating Mode”.............................................................. 232.3.3 DIP-Switches 3-8 ................................................................................... 242.3.4 DIP-Switch Position Status Table ............................................................ 25

2.4 EXTERNAL CONNECTORS ........................................................................262.4.1 Power Connector ................................................................................... 272.4.2 Ethernet Connector ................................................................................ 272.4.3 Subnet16 Controller Port Connectors ...................................................... 282.4.4 Digital Inputs and Outputs ...................................................................... 28

2.5 DIGITAL I/O WIRING ...............................................................................292.5.1 Digital Inputs ......................................................................................... 292.5.2 Digital Outputs....................................................................................... 29


P / N : 1 7 - 1 3 0 9 R E V 0 2 ( 0 6 / 0 7 ) P A G E 6 O F 7 4

2.6 DIGITAL I/O EXAMPLES ...........................................................................302.6.1 Input from Sourcing Contact ................................................................... 302.6.2 Input from Sinking Contact ..................................................................... 312.6.3 Input from NPN Sensor .......................................................................... 312.6.4 Input from PNP Sensor........................................................................... 322.6.5 Sourcing Output “Contact” ...................................................................... 322.6.6 Sinking Output “Contact” ........................................................................ 332.6.7 Sinking Output LED Driver...................................................................... 33

2.7 POWER & WIRING ..................................................................................342.7.1 Power Requirements .............................................................................. 342.7.2 Total System Current ............................................................................. 342.7.3 Cable Voltage Drop................................................................................ 352.7.4 Subnet16 Hub Hardware Details ............................................................. 35

2.8 NODE ID CONFIGURATION & MANAGEMENT ...............................................362.9 HUB AND SUBNET NODE NAMING .............................................................382.10 CONFIGURATION TOOLS ........................................................................39

2.10.1 Cobalt HF TCP/IP Dashboard................................................................ 392.10.2 C-Macro Builder ................................................................................... 40

CHAPTER 3: RFID COMMAND MACROS....................................... 41

CHAPTER 4: COMMAND MAPPING .............................................. 434.1 MAPPING COMMAND & RESPONSE DATA ...................................................43

4.1.1 Node Input Pages .................................................................................. 434.1.2 Node Output Pages................................................................................ 444.1.3 Node Input/Output Page - Allocation Formula........................................... 444.1.4 Node 1-4 Input/Output Pages Table ........................................................ 444.1.5 Hub Node Input/Output Page Table ......................................................... 444.1.6 Data Producer vs. Data Consumer .......................................................... 45

4.2 CBX COMMAND PROTOCOL .....................................................................464.2.1 CBx - Command Packet Structure ........................................................... 464.2.2 CBx - Response Packet Structure ........................................................... 474.2.3 CBx - Controller Command Example ....................................................... 484.2.4 CBx - Controller Response Example........................................................ 484.2.5 CBx - Hub Command Example ................................................................ 494.2.6 CBx - Hub Response Example ................................................................ 49

4.3 NOTIFICATION MESSAGES .......................................................................514.3.1 Notification Message Table..................................................................... 524.3.2 Notification Mask Example...................................................................... 534.3.3 Notification Message - Packet Structure .................................................. 53

CHAPTER 5: STANDARD TCP/IP INTERFACE ......... . . . . . . .. . . . . . . .. . . . . . 545.1 STANDARD TCP/IP OVERVIEW.................................................................545.2 STANDARD TCP/IP: COMMAND & RESPONSE EXAMPLES ...........................55

5.2.1 Standard TCP/IP Controller Command Example ....................................... 555.2.2 Standard TCP/IP Controller Response Example ....................................... 565.2.3 Standard TCP/IP Hub Command Example ............................................... 575.2.4 Standard TCP/IP Hub Response Example................................................ 58


P / N : 1 7 - 1 3 0 9 R E V 0 2 ( 0 6 / 0 7 ) P A G E 7 O F 7 4

CHAPTER 6: RFID COMMANDS AND ERROR CODES ........ .. . . . . . . . .. 596.1 RFID COMMANDS TABLE ........................................................................596.2 ERROR CODE TABLE ..............................................................................636.3 ERROR RESPONSE PACKET STRUCTURE ...................................................656.4 ERROR RESPONSE EXAMPLE ...................................................................66

APPENDIX A: HUB SPECIFICATIONS ....... .. . . . . . . .. . . . . . . .. . . . . . . .. . . . . . . .. . . 67

APPENDIX B: MODELS & ACCESSORIES ..................................... 68SUBNET16 HUB MODELS ................................................................................68RFID CONTROLLERS ......................................................................................68SUBNET16 CABLES & CONNECTORS ................................................................69SOFTWARE UTILITIES .....................................................................................70POWER SUPPLIES ..........................................................................................70

APPENDIX C: NETWORK DIAGRAM.............................................. 71

APPENDIX D: ASCII CHART ......................................................... 72

EMS WARRANTY .......................................................................... 74

H U B - 0 4 - T C P - 0 1 L I S T O F T A B L E SO P E R A T O R S M A N U A L

P / N : 1 7 - 1 3 0 9 R E V 0 2 ( 0 6 / 0 7 ) P A G E 8 O F 7 4

LIST OF TABLESTable 2-1: Active and Presence LED Descriptions...............................................................19

Table 2-2: Hub Status LED Descriptions .............................................................................20

Table 2-3: Ethernet Port LEDs.............................................................................................21

Table 2-4: DIP-Switch Position Status Table........................................................................25

Table 2-5: User Defined Hub and Node Name Reference Table..........................................38

Table 4-1: Nodes 1-4 Input/Output Pages............................................................................44

Table 4-2: Hub Node Input/Output Page Table ....................................................................44

Table 4-3: CBx Command Packet Structure ........................................................................46

Table 4-4: CBx Response Packet Structure.........................................................................47

Table 4-5: Node Status Byte Definition Table ......................................................................50

Table 4-6: Notification Message Table.................................................................................52

Table 4-7: Notification Message - Packet Structure .............................................................53

Table 6-1: RFID Commands Table......................................................................................62

Table 6-2: Error Code Table................................................................................................64

Table 6-3: CBx Error Response Packet Structure................................................................65

Table B-0-1: Subnet16 Cables & Connectors ......................................................................69

H U B - 0 4 - T C P - 0 1 L I S T O F F I G U R E SO P E R A T O R S M A N U A L

P / N : 1 7 - 1 3 0 9 R E V 0 2 ( 0 6 / 0 7 ) P A G E 9 O F 7 4

LIST OF FIGURESFigure 1-1: Hub Dimensions................................................................................................13

Figure 1-2: EMS RFID Controller Model #: HF-0405-485-01 ................................................15

Figure 2-1: Hub's Front Panel LEDs ....................................................................................18

Figure 2-2: Node Active and Presence LEDs.......................................................................19

Figure 2-3: The Hub's LEDs illuminate brightly in the dark ...................................................19

Figure 2-4: The Three Hub Status LEDs..............................................................................20

Figure 2-5: Four Individual Input and Output LEDs ..............................................................21

Figure 2-6: Ethernet Port LEDs ...........................................................................................21

Figure 2-7: Hub DIP-Switch Blocks......................................................................................22

Figure 2-8: Power, I/O & Ethernet Connections ...................................................................26

Figure 2-9: Power Connector (Three-wire, Screw-Down Terminal Block) .............................27

Figure 2-10: Ethernet Connector - RJ45 Socket with Shielded CAT5E Cable.......................27

Figure 2-11: Four Subnet16 Controller Port Connectors with Attached Cables.....................28

Figure 2-12: Four Input and Four Output Ports ....................................................................28

Figure 2-13: Input from Sourcing Contact ............................................................................30

Figure 2-14: Input from Sinking Contact ..............................................................................31

Figure 2-15: Input from NPN Sensor ...................................................................................31

Figure 2-16: Input from PNP Sensor....................................................................................32

Figure 2-17: Sourcing Output "Contact"...............................................................................32

Figure 2-18: Sinking Output "Contact" .................................................................................33

Figure 2-19: Sinking Output LED Driver...............................................................................33

Figure 2-20: HF-Series Configuration Tag ...........................................................................36

Figure 2-21: Cobalt HF TCP/IP Dashboard..........................................................................39

Figure 2-22: C-Macro Builder ..............................................................................................40

H U B - 0 4 - T C P - 0 1 C H A P T E R 1 :O P E R A T O R S M A N U A L G E T T I N G S T A R T E D

P / N : 1 7 - 1 3 0 9 R E V 0 2 ( 0 6 / 0 7 ) P A G E 1 0 O F 7 4

CHAPTER 1:GETTING STARTED

1.1 INTRODUCTION

Welcome to the HUB-04-TCP-01 - Operator s Manual. This manual will assist you inthe installation, configuration and operation of the Subnet16 TCP Hub InterfaceModule.

Subnet16™ Hubs cancontrol up to four passive,high frequency read/writeRFID controllers. The Hubis designed to be compact,reliable and rugged, inorder to meet and exceedthe requirements of theindustrial automationindustry.

1 .1 .1 Compa nyBackgrou nd

Escort Memory Systemshas long been an industryleader in providing RadioFrequency Identification (RFID) devices, building a solid reputation by consistentlydelivering an extended selection of quality, durable industrial RFID systems.

1 .1 .2 EMS Subnet16 Hubs

Escort Memory Systems' Subnet16 Hubs provide Ethernet connectivity to four RFIDControllers over a Subnet16 bus.

Subnet16™ Hubs are available in two versions:

§ HUB-04-TCP-01 for commercial TCP/IP connectivity

§ HUB-04-IND-01 for industrial Ethernet environments (Modbus/TCP,Ethernet/IP) and commercial TCP/IP connectivity

Many of EMS’ earlier generation RFID Controllers with MUX32™ capability can alsobe connected to the Subnet16 Hubs, although the full Subnet16 protocol feature setis not supported by all legacy products.


P / N : 1 7 - 1 3 0 9 R E V 0 2 ( 0 6 / 0 7 ) P A G E 1 1 O F 7 4

1.2 SUBNET16 HUB FEATURES

• Controls up to four Cobalt or HF-0405-Series RFID Controllers

• Four Digital Inputs / Four Digital Outputs

• Supports Controller Macro Functions

• Flash memory for software updates

• Real-time Calendar/Date Functionality

• Supports the TCP/IP set of protocols

• OnDemand Utilities for legacy support of PLC5E and RA SCL5/05Programmable Logic Controllers (PLCs)

• Downward Compatible with most EMS Mux32™ compliant products

• Auto configuration of HF-Series RFID Controllers(Automatic Node ID Assignment)

• 10/100M baud

• Node Fault Detection

• Sources up to 2.5Acurrent

• Isolated power and businterfaces

• ARM7 processing power

• 21 LED status indicator lights

• FCC/CE Agency compliance


P / N : 1 7 - 1 3 0 9 R E V 0 2 ( 0 6 / 0 7 ) P A G E 1 2 O F 7 4

1.3 ABOUT THIS MANUAL

This document provides guidelines and instructions for installing, configuring andoperating Escort Memory Systems’ Subnet16 TCP/IP Hub Interface Module (HUB-04-TCP-01).

This document does NOT include explicit details regarding each of the Hub’s RFIDcommands. Specific RFID command related information is available in the CBxCommand Protocol Reference Manual, which is available at www.ems-rfid.com.

However, this manual does explain the process of issuing commands from a host PCto a Subnet16 Hub, Subnet network and attached RFID controllers.

1 .3 .1 Who Should Read th i s M anual?

This manual should be read by those who will be installing, configuring and operatingthe Subnet16 Hub. This may include (but is not limited to) the following people:

• Hardware Installers / System Integrators

• Project Managers

• IT Personnel

• System and Database Administrators

• Software Application Engineers

• Service and Maintenance Engineers

1 .3 .2 HEX Notat ion

Throughout this manual, numbers expressed in Hexadecimal notation are prefacedwith “0x”. For example, the number "10" in decimal is expressed as "0x0A" inhexadecimal. See Appendix D for a chart containing Hex values, ASCII charactersand their corresponding decimal integers.

http://www.ems-rfid.com


P / N : 1 7 - 1 3 0 9 R E V 0 2 ( 0 6 / 0 7 ) P A G E 1 3 O F 7 4

1.4 HUB D IMENSIONS

Figure 1-1: Hub Dimensions


P / N : 1 7 - 1 3 0 9 R E V 0 2 ( 0 6 / 0 7 ) P A G E 1 4 O F 7 4

1.5 INSTALLATION GUIDELINES

1 .5 .1 Hardware Requi rem ents

The following devices are required for a complete RFID system:

§ One Subnet16 TCP/IP Hub

§ One host PC with an Ethernet network connection

§ One to four RFID controllers (Cobalt or HF-0405-Series)

§ One to four male to female, 5-pin, M12 ThinNet cables

§ One Category 5E Ethernet Cable

§ A suitable power supply capable of providing sufficient power to the Hub andits RFID controllers

§ EMS’ HMS-Series, LRP-Series or T-Series RFID tags

1 .5 .2 Ins ta l la t i on Precaut ions

The Hub is designed to withstand 8kV of direct electro-static discharge (ESD) and15kV of air gap discharge. However, it is not uncommon for some applications togenerate considerably higher ESD levels.

§ Avoid mounting the Hub or its RFID controllers near sources of EMI (electro-magnetic interference) or near devices that generate high ESD levels.

§ Use adequate ESD prevention measures to dissipate potentially highvoltages.

§ Do not route cables near unshielded cables or near wiring carrying highvoltage or high current.

§ Avoid routing cables near motors and solenoids.

§ Cables should only cross at perpendicular intersections.

1 .5 .3 Network & Power Con sidera t ions

§ Refer to the network diagram in Appendix C.

§ Construct your network using only EMS approved Subnet16 cables andaccessories.

§ Review the power requirements of your RFID network and provide a suitablepower supply. (See Appendix B for power supplies offered by EMS).

§ See Chapter 2, Section 2.7, Power & Wiring for more information.


P / N : 1 7 - 1 3 0 9 R E V 0 2 ( 0 6 / 0 7 ) P A G E 1 5 O F 7 4

1.6 INSTALLING THE HUB

F o l l ow t h e S t e p s B el o w t o I n s t a l l t h e H u b

1 Note the Installation Guidelines in Chapter 1, Section 1.5.

2 Securely mount the Hub to your chosen location using two M5 (#10) screws, lockwashers and nuts. The Hub may be mounted in any orientation, but should bealigned in such a mannerthat the LED indicatorscan be seen duringoperation.

3 Attach the male end of a5-pin, male-to-female,M12 cable to one of thefour available Subnet16Controller Ports on theHub. Connect the femaleend of the cable to the 5-pin, male, M12 connectoron a -485-based RFIDcontroller.

Figure 1-2: EMS RFID Controller Model #: HF-0405-485-01

4 Repeat Step 3 for each RFID controller to be installed.

5 Connect the Hub to the host viaCategory 5E Ethernet cabling.

Note: a crossover cable may berequired if connecting the Hub directlyto a host PC or PLC (rather than to aswitch, hub or router).


P / N : 1 7 - 1 3 0 9 R E V 0 2 ( 0 6 / 0 7 ) P A G E 1 6 O F 7 4

6 Connect your power supply cable to the 3-pin,power connection terminal on the Hub asfollows:

• Connect the positive lead to Pin 1 (V+24VDC)

• Connect the ground or reference lead to Pin2 (V- 0VDC)

• Connect the cable shield or drain wire toPin 3 (SHEILD GND)

7 Turn the power supply ON. Upon initial power-up, the LEDs on the Hub willsimultaneously flash several times. The Hub will then cycle a pattern in whicheach LED is briefly illuminated one at a time.

The Hub will continueto cycle through theLEDs in this mannerfor 15 to 30 seconds,during which time theHub is continuing toboot up.

After initialization, thegreen PWR (power)LED will remain lit toindicate normaloperating status.

IP ADDRESS INFORMATION:

The TCP/IP Hub interface module is designed to receive its IP address via DHCP. Afteryour DHCP server has assigned an IP address to a TCP/IP Hub, the IP address can beacquired through the use of the “Digi Device Discovery” software tool. “Digi DeviceDiscovery” is a separate utility available at www.ems-rfid.com (filename: “GWY TCPdgdiscvr.zip”) that identifies the IP address of EMS’ TCP/IP interface modules.


H U B - 0 4 - T C P - 0 1 C H A P T E R 2 :O P E R A T O R S M A N U A L H U B O V E R V I E W

P / N : 1 7 - 1 3 0 9 R E V 0 2 ( 0 6 / 0 7 ) P A G E 1 7 O F 7 4

CHAPTER 2:HUB OVERVIEW

2.1 OPERATING MODES

Subnet16 Hubs have two basic modes of operation: Subnet16™ and Mux32™.Operating mode is set via DIP-switch #2 on the main board. (Refer to Section 2.3 forDIP-switch access and settings).

§ DIP-switch 2 ON = Subnet16 (Default Setting)

§ DIP-switch 2 OFF = Mux32

2 .1 .1 Subnet16

Subnet16™ is an advanced, feature-rich network protocol that supports a subset ofthe EMS Mux32 legacy protocol. The advanced features implemented in theSubnet16 protocol allow the Hub to assign Subnet Node ID values automatically toeach RFID controller connected to Hub. Subnet16 also allows the Hub to detectwhen a new controller is connected or when a controller is no longer responding.

Through the Subnet16 protocol, the Hub is able to store a backup copy of each RFIDcontroller’s custom configuration settings. In the event that an RFID controller fails,the stored configuration settings can be automatically reassigned to a replacementcontroller.

Real-time clock functionality is supported in Subnet16 mode. Host-bound datapackets are automatically Time/Date stamped as they pass through the Hub and onto the host.

Many of the RFID commands supported by the Hub and RFID controllers will onlyfunction when the Hub is in Subnet16 mode.

2 .1 .2 Mux32

Mux32 is a well-established, multi-drop protocol incorporated into many of EMS’ priorproducts including HMS-Series and LRP-Series RFID Controllers. Most, but not all,HMS and LRP commands supported by Mux32 are also supported by the Hub (whenin Mux32 mode). Legacy Mux32 controllers must support the “ABx Fast” commandprotocol to work with the Hub in Mux32 mode. For more information regarding ABxFast, please see the ABx Fast Protocol Reference Manual available online atwww.ems-rfid.com.

Many advanced Subnet16 features are not available when the Hub is running inMux32 mode. RFID controllers must be assigned a unique Node ID number (viaConfiguration Tag) prior to being attached to the Hub.



P / N : 1 7 - 1 3 0 9 R E V 0 2 ( 0 6 / 0 7 ) P A G E 1 8 O F 7 4

2.2 LED INDICATORS

The HUB has 21 LED indicators. Nineteen LEDs are located on the front panel of theunit and two LEDs are located within the Ethernet port just above the RJ45connector. The LEDs display everything from bus and Ethernet activity, to diagnosticinformation, power and I/O status.

Figure 2-1: Hub's Front Panel LEDs


P / N : 1 7 - 1 3 0 9 R E V 0 2 ( 0 6 / 0 7 ) P A G E 1 9 O F 7 4

2 .2 .1 Active and Presenc e LEDs

L E D N a m e L E D C o l o r D e s c r i p t i o n

ACTIVE

(Node 1 4)

Am b e r ACTIVE LEDs flash ON and OFF toindicate that data is being transmittedbetween the Hub and one of the fourSubnet Nodes.

PRESENCE

(Node 1 4)

G r e e n PRESENCE LEDs becomeindividually lit when a tag enters theRF-field of the controller (requiresTag Presence to be enabled on theHF-Series Controller).

Table 2-1: Active and Presence LED Descriptions

Figure 2-2: Node Active and Presence LEDs

Figure 2-3: The Hub's LEDs illuminate brightly in the dark


P / N : 1 7 - 1 3 0 9 R E V 0 2 ( 0 6 / 0 7 ) P A G E 2 0 O F 7 4

2 .2 .2 HUB Sta tus LEDs

Figure 2-4: The Three Hub Status LEDs

H u b S t a t u s L E D D es c r i p t i o n s

L E D N a m e L E D C o l o r D e s c r i p t i o n

E T H E RN E T Am b e r The ETHERNET LED will flash ONand OFF to indicate that data isbeing transmitted between the hostand the Hub.

E R R O R R e d The ERROR LED will become litwhen an error condition occurs. Itwill remain ON until the next validcommand is received.

P O W E R G r e e n The POWER LED will remain ONwhile power is applied to the Hub.

Table 2-2: Hub Status LED Descriptions


P / N : 1 7 - 1 3 0 9 R E V 0 2 ( 0 6 / 0 7 ) P A G E 2 1 O F 7 4

2 .2 .3 I /O LE Ds

The bottom row of eight LEDs, display the status of the unit’s I/O ports. LEDs that areON indicate that the I/O port is set or enabled. LEDs that are OFF indicate that theI/O port is cleared or disabled.

Figure 2-5: Four Individual Input and Output LEDs

2 .2 .4 Ethernet Por t LEDs

There are two LEDs located within the Ethernet port just above the RJ45 connectorthat are used to display Ethernet connection status and data traffic activity.

Figure 2-6: Ethernet Port LEDs

L E D C o l o r D e s c r i p t i o n

Am b e r The AMBER LED on the left is the 10/100 Indicator LED,which will turn ON whenever an Ethernet link isestablished and will remain ON for the duration of theconnection.

G r e e n The GREEN LED on the right is the Ethernet Data LED,which will flash ON and OFF when Ethernet traffic isdetected by the Hub (regardless of origin anddestination).

Table 2-3: Ethernet Port LEDs

Amber LED:Ethernet LinkEstablished

Green LED:Ethernet Traffic

Detected


P / N : 1 7 - 1 3 0 9 R E V 0 2 ( 0 6 / 0 7 ) P A G E 2 2 O F 7 4

2.3 DIP-SWITCH SETTINGS

Certain parameters and features are configured by setting DIP-switches on the unit’scircuit board assembly. To access these DIP-switches, remove the four screwssecuring the lid to the base of the enclosure. After removing the lid, locate the mainDIP-switch block containing eight small DIP-switches.

Figure 2-7: Hub DIP-Switch Blocks

Do not modifythis block ofDIP-switches

Main DIP-switches # 1-8


P / N : 1 7 - 1 3 0 9 R E V 0 2 ( 0 6 / 0 7 ) P A G E 2 3 O F 7 4

2 .3 .1 DIP-Swi tch 1 : Run Mode / Id le M ode

The first DIP-switch selects whether the Hub powers-up in “Run Mode” or in “IdleMode.”

• ON (Default Setting): when thisDIP-switch is ON, the Hub willpower-up in Run Mode, in whichcase it will immediately begin“polling” the Subnet network in anattempt to ready the connected RFIDcontrollers to start receivingcommands.

• OFF: when this DIP-switch is OFF,the Hub will power-up in Idle Mode.This option forces the Hub to “wait”for the host to establish theconnection, after which users mustissue CBx Command 0x70 - StartSubnet before the Hub canprocess commands to the Subnet.

2 .3 .2 DIP-Swi tch 2 : Operat ing Mode

The second DIP-switch selects the Hub’s Operating Mode, thereby determiningwhether the unit powers-up in Subnet16 mode or in Mux32 mode.

• ON (Default Setting): when this DIP-switch is ON, upon power-up, the Hub willenter Subnet16 mode, enabling the Subnet16 protocol and expanded feature set.

• OFF: when this DIP-switch is OFF, upon power-up, the Hub will enter Mux32mode.

ON

OFF


P / N : 1 7 - 1 3 0 9 R E V 0 2 ( 0 6 / 0 7 ) P A G E 2 4 O F 7 4

2 .3 .3 DIP-Swi tches 3 -8

DIP-switch 3 is reserved and dipswitches 4-8 enable/disable a 3-pin main boardserial connection terminal that is used by EMS’ Manufacturing during the initialfirmware installation process. Users should NOT modify these DIP-switches.

D I P -S w i t c h

D e f a u l tP o s i t i o n

3 OFF

4 OFF

5 OFF

6 OFF

7 ON

8 ON

ON

OFF


P / N : 1 7 - 1 3 0 9 R E V 0 2 ( 0 6 / 0 7 ) P A G E 2 5 O F 7 4

2 .3 .4 DIP-Swi tch Posi t ion Stat us Table

D I P -S w i t c h

P o s i t i o n F u n c t i o n

ON Enable RUN mode @ Power-Up (default)1

OFF Enable IDLE mode @ Power-Up

ON Enable Subnet16 mode @ Power-Up (default)2

OFF Enable MUX32 mode @ Power-Up

ON Reserved3

OFF Reserved (default)

ON Reserved4

OFF Default

ON Reserved5

OFF Default

ON Reserved6

OFF Default

ON Default7

OFF Reserved

ON Default8

OFF Reserved

Table 2-4: DIP-Switch Position Status Table


P / N : 1 7 - 1 3 0 9 R E V 0 2 ( 0 6 / 0 7 ) P A G E 2 6 O F 7 4

2.4 EXTERNAL CONNECTORS

The Hub has the following external connectors:

• Power Connector (3-wire, screw-down terminal block)

• Ethernet Connector (standard 8-pin, RJ45 socket)

• Subnet16 Controller Port Connectors (four individual 5-pin, female,M12)

• Digital Input Connectors (four individual)

• Digital Output Connectors (four individual)

Figure 2-8: Power, I/O & Ethernet Connections


P / N : 1 7 - 1 3 0 9 R E V 0 2 ( 0 6 / 0 7 ) P A G E 2 7 O F 7 4

2 .4 .1 Power Connect or

Figure 2-9: Power Connector (Three-wire, Screw-Down Terminal Block)

2 .4 .2 Ethernet Connect or

Figure 2-10: Ethernet Connector - RJ45 Socket with Shielded CAT5E Cable


P / N : 1 7 - 1 3 0 9 R E V 0 2 ( 0 6 / 0 7 ) P A G E 2 8 O F 7 4

2 .4 .3 Subnet16 Con tro l ler Por t Connectors

Figure 2-11: Four Subnet16 Controller Port Connectors with Attached Cables

2 .4 .4 Digi t a l Inputs and Outputs

Figure 2-12: Four Input and Four Output Ports

The four Digital Inputs and four Digital Outputs are equipped with individual portscontaining screw down terminal blocks for V+, V- and SHIELD connections.


P / N : 1 7 - 1 3 0 9 R E V 0 2 ( 0 6 / 0 7 ) P A G E 2 9 O F 7 4

2.5 D IGITAL I/O W IRING

The Digital Inputs and Digital Outputs are optically isolated circuits. Inputs can beconfigured for sensors with a PNP or an NPN output. Outputs can be used in currentsourcing or sinking configurations.

2 .5 .1 Digi t a l Inputs

Voltage Range: 4.5 ~ 30VDCMaximum Current: 25mA

The V+ (+IN) terminal must be at a higher positive potential than the V- (-IN)terminal for current to be sensed correctly.

2 .5 .2 Digi t a l Outputs

Voltage Range: 0 ~ 30VDCMaximum Current: 500mA

A device that operates at 200mA may damage the Digital Output due to inrushcurrent if a current limiting device is not used and the current exceeds 500mA (e.g.an incandescent light). The inductive "kick" that occurs when a relay is released(back EMF from a collapsing magnetic field) can impose a voltage higher than30VDC that may damage the output transistor. To avoid this potential issue, employa diode to clamp the back EMF.


P / N : 1 7 - 1 3 0 9 R E V 0 2 ( 0 6 / 0 7 ) P A G E 3 0 O F 7 4

2.6 D IGITAL I/O EXAMPLES

The following examples illustrate different connections for common input and outputdevices.

2 .6 .1 Input f rom Sourc in g Contact

The switch is connected on the positive side; the negative side is grounded. This is a"Dry" contact (current is limited to 15mA), a high quality sealed switch should beused.

Figure 2-13: Input from Sourcing Contact


P / N : 1 7 - 1 3 0 9 R E V 0 2 ( 0 6 / 0 7 ) P A G E 3 1 O F 7 4

2 .6 .2 Input f rom Sink ing Contact

The switch is connected on the negative side; the positive side is connected to thepositive supply. This configuration requires a high quality sealed contact.

Figure 2-14: Input from Sinking Contact

2 .6 .3 Input f rom NPN Sen sor

An Open Collector NPN output from a photo sensor is switching to ground. Thisconfiguration can be wired as a sinking or low-side contact.

Figure 2-15: Input from NPN Sensor


P / N : 1 7 - 1 3 0 9 R E V 0 2 ( 0 6 / 0 7 ) P A G E 3 2 O F 7 4

2 .6 .4 Input f rom PNP Sensor

An Open Collector PNP output from a photo sensor is switching to the positivesupply. This configuration can be wired as a sourcing or high-side contact.

Figure 2-16: Input from PNP Sensor

2 .6 .5 Sou rc ing Output ContactA relay is connected as a current sourcing "Contact." The relay is grounded and the+OUT terminal is connected to the positive supply.

It is essential to use a 1N4001 or similar diode across the relay coil to protect theoutput circuit and reduce noise along the wiring. It should be connected at the relayto minimize the length of wiring that could radiate noise.

Figure 2-17: Sourcing Output "Contact"


P / N : 1 7 - 1 3 0 9 R E V 0 2 ( 0 6 / 0 7 ) P A G E 3 3 O F 7 4

2 .6 .6 Sink ing Output Contact

A "Contact" sinking current from a relay, the -OUT terminal is grounded and the relayis connected to the positive supply. This configuration also requires a diode placedacross the relay coil to protect the circuit and reduce noise.

Figure 2-18: Sinking Output "Contact"

2 .6 .7 Sink ing Output LED Dri ver

The LED and current limiting resistor are in series between the positive supply andthe +OUT terminal. The -OUT terminal is grounded. The resistor in series with theLED sets the forward current (1.2K will provide 20mA LED current when run from24VDC).

Figure 2-19: Sinking Output LED Driver


P / N : 1 7 - 1 3 0 9 R E V 0 2 ( 0 6 / 0 7 ) P A G E 3 4 O F 7 4

2.7 POWER & W IRING

The information presented below is provided to assist the installer in determining theamount of power required by the Hub and its Subnet network.

2 .7 .1 Power R equi rem ents

The Hub requires a power supply capable of providing enough power for the Hub andeach of the four possible RFID controllers.

The Hub power supply circuit accepts 18~30VDC input and has protection for overvoltage and miss wiring. The input voltage is isolated and regulated as required bythe circuit.

2 .7 .2 Tota l System Curren t

Maximum Hub Current = 250mA @ 24VDC (6W)

Maximum RFID Controller Current = (refer to controller’s specifications formore information)

• HF-0405-485 controllers = 150mA

• C0405-485 controllers = 80mA

• C1007-485 controllers = 150mA

• Cobalt HF-CNTL-485 controllers = 400mA

Maximum Current Rating - Hub Power Feed = 2.5A

CA L C U L A T I N G TO T A L SY S T E M CU R R E NT CO N S U MP T I O N

To calculate the total amount of current required to operate the Hub and any numberof attached RFID controllers, follow the formula below.

Total System Current Consumption =[Maximum Hub Current + (Maximum Controller Current xNumber of Controllers)] x 1.1 (to add a 10% safety margin)

TO T A L SY S T E M CU R R E N T CO N S U M P T I ON EX A M P L E

For a Subnet16 Hub network with four HF-0405-485 RFID ControllersTotal Current Required = [0.250A + (0.150A X 4)] x 1.1 = 0.935A


P / N : 1 7 - 1 3 0 9 R E V 0 2 ( 0 6 / 0 7 ) P A G E 3 5 O F 7 4

2 .7 .3 Cable Vol tage Drop

Each RFID controller will experience a certain amount of voltage drop depending onthe length of its cable.

Subnet16 (ThinNet) Cable Resistance per Meter = 0.05413

CA L C U L A T I N G VO L T A G E DR O P

The following calculation should be conducted on the RFID controller farthest fromthe Hub, as it will experience the greatest voltage drop.

Voltage Drop = [(Max Controller Current X Number of Controllers) X (CableResistance/Meter X Cable Length in meters)]

VO L T A G E C A L C U L A T I O N EX A M P L E

For a network with four HF-0405-485 RFID Controller at a cable length of 20 metersVoltage Drop = (0.150A X 4) X (.05413 X 20) = 0.6495VDC

It is recommended that the voltage drop calculation be conducted on the RFIDcontroller that is farthest from the Hub, as it will experience the greatest voltage drop.

CU R R E N T RA T I N G F O R CA B L E S

• ThinNet Cable Current Rating = 6.4A

• 12mm Connector Current Rating = 3A

2 .7 .4 Subnet16 Hub Hardware Deta i ls

The Hub interface module incorporates an ARM7 micro-controller, a power supplycircuit (with protected input and output circuits), a real- time clock and an opto-isolated Subnet16™ interface (with diagnostic functionality). Subnet16™ serialcommunication is protected by EMI filters and diodes for fault tolerance.

The outer housing of the Hub is a fabricated stainless steel enclosure that is ratedNEMA 1 and IP30. A mounting bracket is incorporated into the enclosure to provideease of installation. Four Philips head screws secure the cover to the base.Removing these four screws and the cover is required to access the DIP-switch block.

NOTE:

IP30 – Ingress Protection against solid objects over 2.5mm (tools and wires)

-Ingress Protection (IP) ratings are developed by the European Committee for ElectroTechnical Standardization (CENELEC) - IEC/EN Publication 60529

NEMA Type 1 - Enclosures are constructed for indoor use, provide a degree ofprotection to personnel against incidental contact with the enclosed equipment andprovide a degree of protection against falling dirt.

- NEMA Standards Publication 250-2003


P / N : 1 7 - 1 3 0 9 R E V 0 2 ( 0 6 / 0 7 ) P A G E 3 6 O F 7 4

2.8 NODE ID CONFIGURATION & MANAGEMENT

Each RFID controller connected to a Hub’s Subnet network must be assigned aunique Node ID value between one and four.

When an HF-SeriesRFID Controller isconnected to one ofthe Hub’s SubnetNode connectors forthe first time, theHub will query thecontroller to ensurethat the Node IDvalue stored incontroller matchesthe Node ID valuethat it is attached toon the Hub.

If the configurationsmatch, the Hub“allows” the RFIDcontroller onto theSubnet network. Ifthe RFID controller’sNode ID value doesNOT match, the Hubwill then attempt tooverwrite thecontroller’sconfiguration, forcingit to accept the NodeID value assigned bythe Hub.

Figure 2-20: HF-Series Configuration Tag


P / N : 1 7 - 1 3 0 9 R E V 0 2 ( 0 6 / 0 7 ) P A G E 3 7 O F 7 4

Before the Hub can dynamically override a Node ID value stored on a controller, thecontroller must first be initialized, which sets the Node ID value to zero. Node ID 0 isthe equivalent of having no Node ID assigned (note: Cobalt and HF-SeriesControllers ship with their Node ID value set to 0).

When an RFID controller is set to Node ID 0 and is connected to the Hub, it will notinitially be recognized by the Hub until a Cobalt HF Configuration Tag is placed in theantenna’s RF field and power to the controller is cycled. Each Cobalt and HF-SeriesRFID Controller is shipped with a Configuration Tag included.

A few seconds after cycling power to the controller while the Configuration Tag iswithin RF range, the LEDs on the controller will begin to flash. It is during this flashingof the LEDs that the RFID controller is receiving its Node ID configuration from theHub. When this procedure has finished, the controller will display its new assignedNode ID value in binary code from right to left using the five amber LEDs on thecontroller.

Because the Hub stores a backup of each Subnet Node’s configuration, should anRFID controller ever fail, a replacement controller can be installed quickly and easily.The new controller will be automatically assigned the same Node ID value andconfiguration as the replaced controller.

(For further instructions on setting the Node ID using a Cobalt or HF-SeriesConfiguration Tag, see the Cobalt HF-Series or HF-0405 Series RFID Controller Operator s Manuals available online at www.ems-rfid.com).



P / N : 1 7 - 1 3 0 9 R E V 0 2 ( 0 6 / 0 7 ) P A G E 3 8 O F 7 4

2.9 HUB AND SUBNET NODE NAMING

The Hub can store a 64-byte ASCII string for each of the four Subnet Nodes and one64-byte ASCII string for the Hub itself. These text strings can be used to assignlogical or friendly names to the Hub and the four Subnet Nodes.

For example, you could assign the Hub a logical name such as “PRODUCTION LINE1” and then name the RFID controller connected to Subnet Node 01 “PRODUCTIONSTATION 1.” The controller at Subnet Node 02 could then be named “PRODUCTIONSTATION 2” (and so forth).

Hub and Subnet Node/controller names can be edited and retrieved by issuingspecific commands to the Hub (CBx Command 0x11 Get Hub Name, CBxCommand 0x21 Set Hub Name, CBx Command 0x30 Get Controller Name, CBxCommand 0x40 Set Controller Name).

Hub and Subnet Node/controller naming can also be accomplished through the useof the Cobalt HF TCP/IP Dashboard software utility (for more information, seeChapter 2, Section 2.10.1 Cobalt HF TCP/IP Dashboard ).

US E R DE F I N E D HU B A N D NO D E NA M E RE F E R E N C E TA B L E

After defining names for the Hub and Subnet Nodes, you can enter their values in thetable provided below. You may want to print an extra copy of this page and store it forfuture reference.

S u b n e tN o d e

F r i e n d l yN a m e

H a r d w a r eS e r i a lN u m b e r

I P A d d r e s s

1 N/A

2 N/A

3 N/A

4 N/A

HUB

Table 2-5: User Defined Hub and Node Name Reference Table


P / N : 1 7 - 1 3 0 9 R E V 0 2 ( 0 6 / 0 7 ) P A G E 3 9 O F 7 4

2.10 CONFIGURATION TOOLS

Escort Memory Systems offers the following powerful RFID configuration utilities forMicrosoft Windows XP and Windows 2000 based systems:

• Cobalt HF TCP/IP Dashboard• C-Macro Builder

Both configuration tools can be downloaded from the EMS website:


2 .10 .1 Cobal t HF TCP/ IP Dashboard

The Cobalt HF TCP/IP Dashboard utility is a Windows-based software applicationthat provides users with complete control over their EMS RFID solution. TheDashboard allows system operators to monitor the health of their RFID system fromanywhere on their network. Users can check the status of their Subnet16 networkfrom the tag level, to the RFID Controller, to the Hub, and to the host.

Figure 2-21: Cobalt HF TCP/IP Dashboard

C O B A L T H F T C P / IP D A S H B O A R D F E A T U R E S :• Complete Subnet Node management and configuration

• Data packet inspection and Subnet network health monitoring

• Simplified installation routines for upgrading firmware for Subnet16 Hubs andCobalt / HF-0405-Series RFID Controllers

• Improved Hub and Subnet Node naming for quickly and easily assigninglogical or “friendly” names to each device



P / N : 1 7 - 1 3 0 9 R E V 0 2 ( 0 6 / 0 7 ) P A G E 4 0 O F 7 4

2 .10 .2 C-Macro Bui lder

C-Macro Builder is an easy to use GUI-driven utility for Windows that allows usersto create powerful RFID macro programs.

Figure 2-22: C-Macro Builder

When used in conjunction with the Dashboard, users can easily produce, download,backup and manage multiple RFID macros for each Subnet Node.

See Chapter 3, RFID Macros for more on macros.

NOTE:

For specific information regarding the configuration and use of the Cobalt HF TCP/IPDashboard or C-Macro Builder utility, please refer to the accompanying documentationincluded when downloading each software application.

H U B - 0 4 - T C P - 0 1 C H A P T E R 3 :O P E R A T O R S M A N U A L R F I D C O M M A N D M A C R O S

P / N : 1 7 - 1 3 0 9 R E V 0 2 ( 0 6 / 0 7 ) P A G E 4 1 O F 7 4

CHAPTER 3:RFID COMMAND MACROS

What are RFID Command Macros?

RFID Command Macros are a powerful feature of EMS’ Cobalt and HF-0405-SeriesControllers. Macros are simple programs that direct a controller to execute multiplepre-programmed instructions.

Because macros reside within the Cobalt or HF-0405-Series Controller’s internalmemory, they can be programmed to instruct the controller to automatically readand/or write a specified set of data to an RFID tag without the controller ever havingto receive a command from the host. In fact, the controllers do not even require aconnection to a host in order to execute macros.

Each macro can contain up to 255 bytes of data and each supported controller canstore up to eight macros at a time. Though they are stored locally on the controller,macros are also backed up in the Hub’s flash memory as well.

Why use macros?

The power of macros is in distributed intelligence, the reduction in network bus trafficand the ability to accelerate routine decision making at the point of data collection.

What can macros do?

In addition to the automated reading and writing of data, macro capabilities include:

• The ability to write time stamps to RFID tags

• The ability to filter command responses to only those of interest to the host(such as when an error occurs or when a tag has arrived in the RF field)

• The ability to harness powerful logic and triggering capabilities such as; read,write, start/stop continuous read, data compare, branch, transmit customstring, and set outputs.

What is a macro trigger?

Macros are initiated by “triggers.” Triggers can be configured in numerous ways. Asimple command from the host, such as “execute macro number three” can beconsidered a trigger.

Triggers can be configured, for example, to activate a macro when a tag enters orleaves a controller’s RF field. When used with the Subnet16™ Hubs, triggers can beconfigured to change the state of any of the four digital outputs. Changes of state canbe either positive or negative logic, and can be defined as edge, level, or one-timeevents.

EMS RFID controllers can store up to eight separate triggers in addition to the eightmacros they can also house. Any trigger can activate any of the eight stored macros.

H U B - 0 4 - T C P - 0 1 C H A P T E R 3 :O P E R A T O R S M A N U A L R F I D C O M M A N D M A C R O S

P / N : 1 7 - 1 3 0 9 R E V 0 2 ( 0 6 / 0 7 ) P A G E 4 2 O F 7 4

How are macros created?

Macros are created using the powerful, yet simple, C-Macro Builder™ utility fromEMS. The tool’s easy to use GUI allows the user to create powerful RFID macroprograms quickly and easily.

When used with EMS’ Cobalt HF Dashboard™ utility, users can effortlessly download,erase, and manage their macros and triggers, as well as set the operationalconfigurations of their RFID controllers and Subnet16™ Hubs.

Which communication interfaces support the use of macros?

Macros (and the Dashboard and C-Macro Builder utilities) support communicationswith Cobalt and HF-0405-Series Controllers across Ethernet, USB, RS232, RS422and RS485 interfaces.

What happens to existing Macros if a controller must be replaced?

When using a Subnet16 Hub, users do not need to worry. Macros and triggersnormally residing in an RFID controller’s flash memory are always backed up in theHub’s flash memory as well. Therefore, if a controller should ever requirereplacement, all existing macro and trigger settings are automatically exported fromthe Hub to the new RFID controller.

In short, when an RFID controller is initially connected to the Hub, macro and triggerdata from the controller’s flash memory is compared to the macro and trigger databacked up in the Hub from the previous RFID controller. If the data does not matchthat which is stored on the Hub, the controller’s flash memory will be overwritten withthe backed up data stored in the Hub’s flash memory.

How can I learn more about the Dashboard and C-Macro Builder?

More information regarding macros, triggers, uploading, downloading, configuringand monitoring EMS RFID equipment is available in the respective User’s Manualsfor these products, which are available on the EMS website at: www.ems-rfid.com.


H U B - 0 4 - T C P - 0 1 C H A P T E R 4 :O P E R A T O R S M A N U A L C O M M A N D M A P P I N G

P / N : 1 7 - 1 3 0 9 R E V 0 2 ( 0 6 / 0 7 ) P A G E 4 3 O F 7 4

CHAPTER 4:COMMAND MAPPING

Commands are initiated by a host PC or Programmable Logic Controller (PLC) andare distributed to the Hub over an Ethernet connection. Once issued, the command isthen either executed directly by the Hub or is otherwise routed to the appropriateRFID controller, which is specified by its numerical “Node ID” value (for which thereare four). Each RFID controller is assigned the Node ID value of the Subnet16Controller Port to which it is attached (between one and four).

In general, there are two types of commands that can be issued:

• Controller Commands - commands intended for one of the attached RFIDcontrollers. “Read Data” and “Write Data” are two common Controller Commands.

• Hub Commands - commands intended for the HUB itself. Hub Commands arethose commands that query the Hub for information or instruct the Hub toperform a task. The commands “Get Node Status List” and “Set Hub Name” areexamples of Hub Commands.

4.1 MAPPING COMMAND & RESPONSE DATA

In order to properly distribute RFID commands to the intended RFID controller (andto correctly return the controller’s response to the host), the Hub separates input data(Commands) from output data (Responses) by assigning each Subnet Node a NodeInput Page and a Node Output Page. Each “page” is actually a small block ofmemory used to temporarily hold command or response data.

4 .1 .1 Nod e Input Pages

The Hub assigns each controller a Node Input Page that corresponds numerically toits assigned Node ID value. Thus, commands directed to the controller at Node 01,for example, will be written to Node Input Page 01. Node Input Pages hold Hub andcontroller-bound command data generated by the host.

N O D E I N P U T P A G E V A L U E S

Nodes 01 thru 04 are assigned Node Input Pages 01 thru 04 respectively. The Hub,itself, is assigned Node Input Page 32.


P / N : 1 7 - 1 3 0 9 R E V 0 2 ( 0 6 / 0 7 ) P A G E 4 4 O F 7 4

4 .1 .2 Nod e Output Pages

The Hub also assigns each controller a Node Output Page used to hold host-boundresponse data generated by the Hub or one of the RFID controllers after executing acommand.

A controller’s numerical Node Output Page value is always 32 page values greaterthan its corresponding Node Input Page value. Therefore, response data from thecontroller at Node 01, for example, will be written to Node Output Page 33 (as NodeOutput Page 33 is 32 page values greater than its corresponding Node Input Page of01).

N O D E O U T P U T P A G E V A L U E S

Nodes 01 thru 04 are assigned Node Output Pages 33 thru 36 respectively. The Hubis assigned Node Output Page 64.

4 .1 .3 Nod e Input/ Output Page - A l locat ion F ormula

In the example above, a command was directed to the RFID controller at Node 01.Command packet data was written to Node Input Page 01 and the controller’sresponse packet data was written to Node Output Page 33.

Therefore, command packet data intended for Node ID [N] will be written to NodeInput Page [N]. Corresponding response packet data will be written to Node OutputPage [N + 32].

4 .1 .4 Nod e 1-4 Inpu t /Ou tput Pages Table

N O D E I D N O D E I N P U T P A G E N O D E O U T P U T P A G E

Node 01 Node Input Page 01 Node Output Page 33




Table 4-1: Nodes 1-4 Input/Output Pages

4 .1 .5 Hub Nod e Input /Output Page T able

Commands intended for the Hub are written to Node Input Page 32 and Hubresponses are written to Node Output Page 64.

N O D E I D N O D E I N P U T P A G E N O D E O U T P U T P A G E


Table 4-2: Hub Node Input/Output Page Table


P / N : 1 7 - 1 3 0 9 R E V 0 2 ( 0 6 / 0 7 ) P A G E 4 5 O F 7 4

4 .1 .6 Data Pr oducer vs . Dat a Con sumer

Each time a command is issued or a response is generated, data is being producedand consumed. For every data packet transmitted across the network, there is a DataProducer and Data Consumer.

• Data Producer refers to the physical piece of hardware on the network thatinitiated or generated the data packet.

• Data Consumer refers to the physical piece of hardware for which agenerated data packet is intended (the data recipient).

For example, when the host issues an RFID command, it is said to be acting as aData Producer. However, when the host retrieves a response packet, the host is saidto be acting as a Data Consumer.

When an RFID controller executes an assigned command, it is said to be acting as aData Consumer. Yet when the same controller generates its response packet, it isacting as a Data Producer.


P / N : 1 7 - 1 3 0 9 R E V 0 2 ( 0 6 / 0 7 ) P A G E 4 6 O F 7 4

4.2 CBX COMMAND PROTOCOL

The CBx Command Protocol is an advanced protocol that supports Multi-dropSubnet16 networking with TCP/IP and Industrial Ethernet applications. It is based ona double-byte oriented packet structure where commands always contain a minimumof six data “words” (12 bytes) - even when one (or more) packet elements orparameters are not applicable to the command.

NOTE: The CBx packet structures described herein can be implemented the same forall TCP/IP-based RFID applications.

4 .2 .1 CBx - Command Packet St ructu re

Below is the packet structure of a standard CBx command.

W O R D C O M M A N D P A C K E T E L E M E N T M S B L S B

00 CBx Header in MSB: 0xFF

Node ID in LSB

0xFF <Node ID>

01 Overall Length: 2-byte value indicating thenumber of “words” in the command packet.This value will always be at least 6 words.

0x00 0x06 + (numberof any additionalwords)

02 0xAA in MSB, Command ID in LSBindicates the command to perform.

0xAA <Command ID>

03 0x00 in MSB, Node ID in LSB indicates theNode ID of the device for which thecommand is intended.

0x00 <Node ID>

04 Timeout Value: 2-byte integer for the lengthof time allowed for the completion of thecommand, measured in 1 millisecond units,where 0x07D0 = 2000 x .001 = 2 seconds.

0x07 0xD0

05 Start Address: 2-byte integer indicating thelocation of tag memory where a Read/Writeoperation will begin (when applicable).

<StartMSB>

<Start LSB>

06 Block Size: 2-byte integer indicating thenumber of bytes that are to be Read/Writtenbeginning at the Start Address (whenapplicable).

<Size MSB> <Size LSB>

07 Additional Data Byte Values 1 & 2: holds 2bytes of data used for Fills, Writes, etc.(when applicable)

<D1> <D2>

08 Additional Data Byte Values 3 & 4: (whenapplicable)

<D3> <D4>

Table 4-3: CBx Command Packet Structure


P / N : 1 7 - 1 3 0 9 R E V 0 2 ( 0 6 / 0 7 ) P A G E 4 7 O F 7 4

4 .2 .2 CBx - Response Pack et S t ructure

After performing a command, the Hub or RFID controller will issue a host-boundresponse packet. Below is the packet structure of a standard CBx response message.

W O R D R E S P O N S E P A C K E TE L E M E N T

M S B L S B

00 CBx Header in MSB: 0xFFNode ID Echo in LSBNOTE: These first two bytes will not bereturned in the response packet when acommand is performed by Node 01

0xFF <Node ID Echo >

01 Overall Length: 2-byte integer indicatingthe number of “words” in the responsepacket. This value will always be at least 6(+ number of any data words retrieved).

0x00 0x06 + (numberof any retrievedwords)

02 0xAA in MSB

Command Echo in LSB

0xAA <CommandEcho>

03 Instance Counter: 1-byte value indicatingthe number of responses generated by theNode ID identified in the LSB (see detailsbelow).

Node ID Echo: 1-byte value indicating theNode ID of the controller that performed thecommand.

<IC> <Node ID Echo>

04 Month and Day Timestamp <Month> <Day>

05 Hour and Minute Timestamp <Hour> <Minute>

06 Second Timestamp in MSB

Additional Data Length in LSB indicatesnumber of additional bytes retrieved.

<Second> <N-bytes>

07 Retrieved Bytes 1 and 2: holds 2 bytes ofretrieved data from tag Reads, serialnumbers, etc. (when applicable)

<B1> <B2>

Table 4-4: CBx Response Packet Structure

IN S T A N C E CO U N T ER

The Instance Counter is a one-byte value used by the Subnet16 Hub to track thenumber of responses generated by the controller at a given Node ID. The Hub tallies,in its internal RAM, separate Instance Counter values for each Node ID.

A Node ID’s Instance Counter will be incremented by one following each response. If,for example, the controller at Node 01 has generated 10 responses, its InstanceCounter value will read 0x0A. However, when the Hub is rebooted or power-cycled,the Instance Counter values for all Node IDs will be reset to zero (0x00).


P / N : 1 7 - 1 3 0 9 R E V 0 2 ( 0 6 / 0 7 ) P A G E 4 8 O F 7 4

4 .2 .3 CBx - Contro l ler Command Example

In the example below, CBx Command 0x05 (Read Data) is issued to the RFIDcontroller at Node 01. The controller will be instructed to read four bytes of data froma tag beginning at tag address 0x20. The Timeout Value, measured in milliseconds,will be set to two seconds for the completion of this command (0x07D0 = 2000 x .001= 2 seconds).

W O R D P A C K E T E L E M E N T M S B L S B

00 CBx Header in MSB: 0xFFNode ID in LSB

0xFF 0x01

01 Overall Length of Command (in “words”) 0x00 0x06

02 0xAA in MSBCommand ID in LSB: (0x05 - Read Data)

0xAA 0x05

03 0x00 in MSBNode ID in LSB: (0x01)

0x00 0x01

04 Timeout Value: (2 seconds) 0x07 0xD0

05 Start Address: (0x20) 0x00 0x20

06 Read Length: (4 bytes) 0x00 0x04

4 .2 .4 CBx - Cont rol l er Response Ex ample

Below is a controller’s typical response after successfully completing the Read Datacommand (as issued in the previous example).

Because this example command was performed by the controller at Node 01, theensuing response will NOT contain the two-byte CBx Header of 0xFF and the NodeID in the first word, as would be the case for all other Node ID responses.

W O R D P A C K E T E L E M E N T M S B L S B

01 Overall Length of Response (in “words”) 0x00 0x08

02 0xAA in MSBCommand Echo in LSB: (0x05 - Read Data)

0xAA 0x05

03 Instance Counter in MSBNode ID Echo in LSB

<IC> 0x01

04 Month and Day Timestamp: (March 19th) 0x03 0x13

05 Hour and Minute Timestamp: (10:11: AM) 0x0A 0x0B

06 Seconds Timestamp in MSB: (36 seconds)Additional Data Length in LSB: (4 bytes)

0x24 0x04

07 Retrieved Data (bytes 1 and 2) <B1> <B2>

08 Retrieved Data (bytes 3 and 4) <B3> <B4>


P / N : 1 7 - 1 3 0 9 R E V 0 2 ( 0 6 / 0 7 ) P A G E 4 9 O F 7 4

4 .2 .5 CBx - Hub Command Example

In this example, the host issues Command 0x13 (Get Node Status List), whichretrieves from the Hub, a list indicating the operating status of the four Nodes.

W O R D D E S C R I P T I O N M S B L S B

00 CBx Header, Node ID 0xFF 0x20

01 Overall Length of Command (in “words”) 0x00 0x06

02 0xAA in MSBCommand ID in LSB: (0x13 -Get Node Status List)

0xAA 0x13

03 0x00 in MSBNode ID in LSB: (0x20 –Hub Node 32)

0x00 0x20

04 Not Used: 0x00, 0x00 (default) 0x00 0x00



Note that even though the last three words (6-bytes) of this command are not used,these parameters still require zero’s (0x00, 0x00) and are to be included whencalculating the Overall Length.

4 .2 .6 CBx - Hub Respon se Ex ample

Below is the Hub response to the command “Get Node Status List (as issued in theprevious example).

W O R D D E SC RI P T I O N M S B L S B

00 CBx Header in MSB: 0xFFNode ID Echo in LSB

0xFF 0x20

01 Overall Length of Response (in words, notincluding the previous 2-bytes CBx Header andNode ID Echo)

0x00 0x08

02 0xAA in MSBCommand Echo in LSB: (0x13)

0xAA 0x13

03 Instance Counter in MSBNode ID Echo in LSB (0x20 = Hub Node 32)

<IC> 0x20

04 Month and Day Timestamp: (March 19th) 0x03 0x13

05 Hour and Minute Timestamp: (10:11: AM) 0x0A 0x0B

06 Seconds Timestamp in MSB: (36 seconds)Additional Data Length in LSB: (4 bytes)

0x24 0x04

07 Status of Nodes 1 and 2 0x00 0x00

08 Status of Nodes 3 and 4 0x04 0x00

In this example, the Node Status Byte “0x04” (meaning “Controller Healthy”) wasreported for Node 03, indicating that the Hub recognizes a functioning RFID controllerat Node 03. See the Node Status Byte Definition Table on the following page.


P / N : 1 7 - 1 3 0 9 R E V 0 2 ( 0 6 / 0 7 ) P A G E 5 0 O F 7 4

Node Status Byte Definition Table

N O D ES T A T U SB Y T E

N O D ES T A T U S

S T AT U S D E S C R I P T I O N

0x00 CONTROLLERINACTIVE

The controller at this node has not responded to a pollfor at least 40 seconds.If a controller does eventually respond at this NodeID, its status will be changed to “0x04 - CONTROLLERHEALTHY”

0x01 CONTROLLERSTOPPEDRESPONDING

The controller at this node has not responded to a pollin over 10 seconds.If the controller does not respond to a poll withinanother 30 seconds, its status will be changed to “0x00- CONTROLLER INACTIVE”If the controller does eventually respond to a poll, itsstatus will be changed back to “0x04 - CONTROLLERHEALTHY”

0x02 CONTROLLERHAS PROBLEM

The controller at this node has missed at least 3consecutive polls.If the controller does not respond to a poll withinanother 10 seconds, its status will be changed to “0x01- CONTROLLER STOPPED RESPONDING”If the controller does eventually respond to a poll, itsstatus will be changed back to “0x04 - CONTROLLERHEALTHY”

0x03 CONTROLLEREXPECTEDSOON

This Node Status indicates that a controller istemporarily disconnected or that it is being moved toanother Node ID.Because a controller is “expected” to appear soon, theHub will poll this node more frequently than other‘inactive’ nodes.

0x04 CONTROLLERHEALTHY

The controller at this node is healthy and responding topolls.However, if the controller misses 3 consecutive polls,its status will be changed to “0x02 - CONTROLLERHAS PROBLEM.”

0x05 CONTROLLERDOWNLOADING

This status is only applied to a controller that iscurrently downloading and installing new firmware to itsflash memory.To optimize polling and allow for the fastest possiblefirmware installation, the Hub will temporarily halt thepolling of this node until the controller has finished itsinstallation.

Table 4-5: Node Status Byte Definition Table


P / N : 1 7 - 1 3 0 9 R E V 0 2 ( 0 6 / 0 7 ) P A G E 5 1 O F 7 4

4.3 NOTIFICATI ON MESSAGES

Notification Messages are small host-bound informational packets of data that areissued by the Hub when a specified Notification Event (or series of events) occurswithin the Hub or on the Subnet16 network.

The Hub stores 13 different Notification Messages internally, each of which can beenabled or disabled by setting a corresponding bit within the 16-bit NotificationMask. By default all Notification Messages are disabled.

When a Notification Message is enabled and its corresponding Notification Eventoccurs, the Notification Message will be generated by the Hub and will be written tothe Node Output Page of affected Subnet Node (i.e., the Node that triggered thenotification). Triggered Notification Messages are provided immediately to the host.

Within the 16-bit Notification Mask, bits 01 through 13 each represent one of theNotification Events. A bit is either set to “1” (ON = enabled) or “0” (OFF = disabled). Ifa bit is turned ON, the corresponding Notification Message will be generated whenthe specified event occurs.

NOTE:

For Notification Messages, a similar handshaking process of enabling and clearingspecific bits of the Output Data Ready Mask is implemented. Notification Messages arealways written to the Node Output Page of the Subnet Node that triggered theNotification Message. Notification Messages are also written to the same holdingregisters as standard responses.

To enable all 13 Notification Messages, the 2-byte Notification Mask is:

0x1FFF.

16-bit Notification Mask - Binary Representation-when enabling all 13 Notification Messages:

(0 0 0 1 1 1 1 1) (1 1 1 1 1 1 1 1) = 0x1FFF[Bit 16 - - Bit 09] [Bit 08 - - Bit 01]


P / N : 1 7 - 1 3 0 9 R E V 0 2 ( 0 6 / 0 7 ) P A G E 5 2 O F 7 4

4 .3 .1 Not i f ica t ion Message T able

The following table contains a listing of the 13 possible Notification Messages.

B I T N OT IF I CAT I O NMESSAGE

E V E NT D E S CR I P T I O N

1 CONTROLLER IS HEALTHY Sent whenever the status of a controller changesto ‘Healthy’

2 CONTROLLER HASPROBLEM

Sent whenever a controller is marked ‘HasProblem’

3 CONTROLLER STOPPEDRESPONDING

Sent whenever a controller is marked ‘StoppedResponding’

4 CONTROLLERDEACTIVATED

Sent whenever a controller is deactivated (ismarked ‘Inactive’)

5 CONTROLLER MISSED POLL Sent whenever a controller misses a poll

6 CONTROLLER ADDRESSCONFLICT

Sent whenever the Hub detects a Node ID conflict

7 CONTROLLERCONFIGURATION FAILURE

Sent whenever the Hub fails to configure acontroller

8 TAG PRESENT AT NODE* Sent whenever a tag is first recognized in the RFfield of the specified node

9 TAG NOT PRESENT ATNODE*

Sent when no tag is recognized or when apreviously recognized tag is no longeracknowledged in the specified node’s RF field

10 INPUT SET Sent when one of the four Inputs has been set

11 INPUT CLEARED Sent when one of the four Inputs has beencleared

12 OUTPUT SET Sent when one of the four Outputs has been set

13 OUTPUT CLEARED Sent when one of the four Outputs has beencleared

* Requires Tag Presence at Node enabled on the RFID controller.

Table 4-6: Notification Message Table


P / N : 1 7 - 1 3 0 9 R E V 0 2 ( 0 6 / 0 7 ) P A G E 5 3 O F 7 4

4 .3 .2 Not i f ica t ion Mask Example

In this example, a controller is attached to Subnet16 Controller Port #4 on Hub. Whenpower is applied to the controller, it will be immediately recognized by the Hub andwill be assigned Node ID 04.

If bit 01 in the Notification Mask was set to 1 (ON), the Hub would automatically issuea Notification Message to the host indicating that a new controller has beenrecognized at Node 04 and is functioning properly (i.e. the controller is healthy).

If, on the other hand, the recently connected controller does not power-up, or fails toinitialize properly, and bit 02 in the Notification Mask is enabled, the Hub will issuethe second Notification Message indicating that the controller at Node 04 has aproblem.

In either scenario, the Notification Message will be written to Node Output Page 36.

4 .3 .3 Not i f ica t ion Message - Packet S t ruc ture

D E S C R I P T I O N M S B L S B

CBx Header in MSB: 0xFF

Node ID Echo in LSB

0xFF 0x04

Overall Length of NotificationMessage (in “words”)

0x00 0x06

0xFE in MSB = NotificationMessage Flag

Notification Event in LSB

0xFE <Notification Event>

Instance Counter in MSB: (aNotification Message is considereda response; therefore the InstanceCounter will be incremented by one)

Node ID Echo in LSB: (the devicethat triggered the notification)

<IC> 0x04

Month and Day Timestamp <Month> <Day>

Hour and Minute Timestamp <Hour> <Minute>

Seconds Timestamp in MSB

0x00 in LSB (default)

<Second> 0x00

Table 4-7: Notification Message - Packet Structure

H U B - 0 4 - T C P - 0 1 C H A P T E R 5 :O P E R A T O R S M A N U A L S T A N D A R D T C P / I P I N T E R F A C E

P / N : 1 7 - 1 3 0 9 R E V 0 2 ( 0 6 / 0 7 ) P A G E 5 4 O F 7 4

CHAPTER 5:STANDARD TCP/IP INTERFACE

5.1 STANDARD TCP/IP OVERVIEW

Another means of communicating with the Hub is through the typical TCP/IP protocol.For this manual, the protocol is referred to as Standard TCP/IP.

In this environment the Hub acts as the server and the host PC acts as client andmust provide the client side software.

NOTE:

The TCP/IP Client (host PC) must connect to the TCP/IP Server (HUB) on port 50200.

Maximum number of words transferred to/from an RFID tag per read/write cycle 100Words / 200 Bytes

Standard TCP/IP sessions are established between the host and the Hub via TCP/IPclient software. A session generally consists of three stages: connection setup, datatransactions and connection termination.

All connections to the Hub are initiated by client side software only. If, for example,an existing connection terminates unexpectedly, the Hub will not attempt to contactthe client software or re-establish a connection. The client is responsible for opening,maintaining, and closing all TCP/IP sessions.

After establishing a successful connection, communications between the clientsoftware and the Hub can proceed. When communication is no longer necessary, it isthe responsibility of the client side application to terminate the connection.


P / N : 1 7 - 1 3 0 9 R E V 0 2 ( 0 6 / 0 7 ) P A G E 5 5 O F 7 4

5.2 STANDARD TCP/IP:COMMAND & RESPONSE EXAMPLES

In standard TCP/IP, RFID commands issued by the host resemble Modbus TCPcommands; however in standard TCP/IP an additional two-byte header is required(0xFF in the MSB, and the target Node ID number in the LSB). These two bytes areinserted in front of the standard Modbus TCP command string. The Hub handles allhandshaking tasks.

NOTE: Standard TCP/IP response packets contain the two-byte header (0xFF in theMSB and the Node ID Echo in the LSB), UNLESS the command was executed byNode 01, in which case there will be no additional 2-byte header in the response.

5 .2 .1 Stand ard T CP/ IP Con tro l ler Command Example

In the following example, a 14-byte Read Data command has been issued to Node02, instructing the controller to retrieve six bytes from a tag starting at address0x0001. A Timeout Value of two seconds has been set for the completion of thecommand.

W O R D # M S B L S B D E S C R I P T I O N

00 0xFF 0x02 “Standard TCP/IP” 2-byte Command Header:MSB = 0xFFLSB = Node ID: 0x02

01 0x00 0x06 Overall Length 2-byte value indicatingnumber of “words” in the packet, not includingthe preceding 2-byte header

02 0xAA 0x05 0xAA in MSB

Command ID in LSB: (0x05 - Read DataCommand)

03 0x00 0x02 0x00 in MSB

Node ID in LSB: Must be same as specified inheader (0x02 for this example)

04 0x00 0x14 Timeout Value: measured in .10 secondincrements (0x0014 = 20 x .10 or 2 seconds)

05 0x00 0x01 Start Address: 0x0001

06 0x00 0x06 Block Size: (6 bytes)


P / N : 1 7 - 1 3 0 9 R E V 0 2 ( 0 6 / 0 7 ) P A G E 5 6 O F 7 4

5 .2 .2 Standard T CP/ IP Con tro l ler R espo nse Example

The following is the response to the Read Data command issued in the previousexample:


00 0xFF 0x02 “Standard TCP/IP” 2-byte Response Header:MSB = 0xFFLSB = Node ID Echo: 0x02

(NOTE: There is no 2-byte response headerwhen a command is executed by Node 01)

01 0x00 0x09 Overall Length of Response Packet (notincluding the 2-byte header)


Command Echo in LSB: (0x05 - Read Data)

03 <IC> 0x02 Instance Counter in MSB

Node ID Echo in LSB

04 0x05 0x1B Time Stamp (Month – Day)

05 0x01 0x0C Time Stamp (Hour – Minute)

06 0x21 0x06 Time Stamp (Seconds) in MSB

Additional Data Length in LSB

07 <B1> <B2> Retrieved Data - bytes 1 & 2




P / N : 1 7 - 1 3 0 9 R E V 0 2 ( 0 6 / 0 7 ) P A G E 5 7 O F 7 4

5 .2 .3 Stand ard T CP/ IP Hub Command E xample

This example retrieves, from the Hub, the user-defined “Hub Name.” Note that theHub is always assigned Node ID 32 (in Hex, Node 32 = 0x20).


00 0xFF 0x20 Standard TCP/IP Header in MSB:0xFF

Node ID in LSB

01 0x00 0x06 Overall Length of Command Packet (notincluding the 2-byte header)


Command ID in LSB: (0x11 – Get Hub Name)

03 0x00 0x20 0x00 in MSB

Node ID in LSB: Must be same as specified inheader (0x20 for this example)

04 0x00 0x00 Timeout Value: N/A for this command

05 0x00 0x00 Start Address: N/A for this command

06 0x00 0x00 Block Size / Read Length: N/A for thiscommand


P / N : 1 7 - 1 3 0 9 R E V 0 2 ( 0 6 / 0 7 ) P A G E 5 8 O F 7 4

5 .2 .4 Stand ard T CP/ IP Hub R esp onse Example

Below is the response to the previous Hub command example.

W o r d M S B L S B D e s c r i p t i o n

00 0xFF 0x20 Standard TCP/IP Header in MSB:0xFF

Node ID Echo in LSB

01 0x00 0x0C Overall Length of Response Packet (notincluding the 2-byte header)


Command Echo in LSB: (0x11 – Get HubName)

03 0x07 0x20 Instance Counter in MSB

Node ID Echo in LSB

04 0x05 0x1B Time Stamp (Month – Day)

05 0x0D 0x03 Time Stamp (Hour – Minute)

06 0x18 0x0C Time Stamp (Seconds) in MSB

Additional Data Length in LSB (12 bytes)

07 0x45 0x4D Retrieved Data - bytes 1 and 2

08 0x53 0x20 Retrieved Data - bytes 3 and 4

09 0x52 0x46 Retrieved Data - bytes 5 and 6

0A 0x49 0x44 Retrieved Data - bytes 7 and 8

0B 0x20 0x48 Retrieved Data - bytes 9 and 10

0C 0x55 0x42 Retrieved Data - bytes 11 and 12

The 12-bytes of retrieved data spell (in ASCII) “EMS RFID HUB.”

H U B - 0 4 - T C P - 0 1 C H A P T E R 6 :O P E R A T O R S M A N U A L R F I D C O M M A N D S A N D E R R O R C O D E S

P / N : 1 7 - 1 3 0 9 R E V 0 2 ( 0 6 / 0 7 ) P A G E 5 9 O F 7 4

CHAPTER 6:RFID COMMANDS AND ERROR CODES

RFID commands are initiated by the host and are directed to the Hub or to one of theHub’s Subnet Nodes, which, in turn, instructs the corresponding RFID controller toperform or execute an operation.

ATTENTION:

For complete command and response packet structures and examples of each RFIDcommand, please refer to the CBx Command Protocol Reference Manual availableat www.ems-rfid.com.

6.1 RFID COMMANDS TABLE

The table below lists the CBx protocol RFID commands supported by the Hub andEMS’ RFID Controllers.

COMMAND ID COMMAND NAME DESCRIPTION

RFID Tag Commands

0x02 L o c k M em o r y B l o c k Write protects a block of tagmemory

0x04 F i l l T a g Writes a specified data byte valueto all defined tag addresses

0x05 R e a d D a t aReads a specified length of datafrom a contiguous (sequential)area of tag memory

0x06 Wr i t e D a t aWrites a specified number ofbytes to a contiguous area of tagmemory

0x07 R e a d T a g I D Reads a tag’s unique tag IDnumber

0x08 T a g S e a r c h Instructs the controller to searchfor a tag in its RF field

0x0C E x ec u t e M a c r o Instructs the controller to executeone of its eight possible macros

0x0D S t a r t C o nt i n u o usR e a d

Instructs the controller to start orstop Continuous Read mode.

0x0E R e a d T a g I D a n dD a t a

Reads a tag’s ID and therequested number of bytes fromtag memory



P / N : 1 7 - 1 3 0 9 R E V 0 2 ( 0 6 / 0 7 ) P A G E 6 0 O F 7 4


0x0FS t a r t C o nt i n u o usR e a d T a g I D a n dD a t a

Places the controller into (or outof) Continuous Read mode and(when evoked) will retrieve a tag’sID.

Hub Information Commands

0x10 G e t H u b S o f t w a r eV e r s i o n

Retrieves the version number ofthe firmware code installed on theHub

0x11 G e t H ub N am e Retrieves the Hub’s user-definedASCII name

0x12 G e t D i p s wi t c hS e t t i n g s

Retrieves the status of the Hubconfiguration dipswitches

0x13 G e t N o de S t a t u sL i s t

Retrieves the operational status ofthe Hub Subnet Nodes

0x14 G e t N o t i f i c a t i o nM a s k

Retrieves the user-defined 16-bit“Notification Mask” thatdetermines for which events theHub notifies the host PC

0x15 G e t L a s t H u b E r r o rRetrieves information from theHub regarding the last or mostrecent error that was experienced

0x16 G e t H ub T im e Retrieves the current date andtime as set internally on the Hub

0x1A G e t H ub I n p u t s Retrieves the status of the Hub’sfour digital inputs

0x1B G e t H ub O u t p u t s Retrieve the status of the Hub’sfour digital outputs

0x1C G e t S u bn e t B a udR a t e

Retrieves the baud rate of theSubnet network

0x21 S e t H u b N a m eWrites to flash memory, a user-defined “friendly” name for theHub

0x24 S e t N o t i f i c a t i o nM a s k

Used to customize or modify theHub’s 16-bit Notification Mask

0x26 S e t H ub T im e Used to set the Hub’s internalclock and calendar

0x2A S e t / C l e a r H u bO u t p u t s

Used to set and/or clear any or allof the Hub’s four digital outputs


P / N : 1 7 - 1 3 0 9 R E V 0 2 ( 0 6 / 0 7 ) P A G E 6 1 O F 7 4


0x2C S e t S u b ne t B a u dR a t e

Used to modify and store changesto the Subnet network baud rate

RFID Controller Commands

0x30 G e t C on t r o l l e rN am e

Retrieves the controller’s user-defined name

0x33 G e t C on t r o l l e rC o nf i g u r a t i o n

Retrieves the controller’sconfiguration settings

0x38 G e t C on t r o l l e r I n f oRetrieves hardware, firmware andserial number information fromthe controller

0x40 S e t C o nt r o l l e rN am e

Used to set (create or modify) theuser-defined name for thecontroller

0x43 S e t C o nt r o l l e rC o nf i g u r a t i o n

Used to set (configure or modify)the controller’s configurationparameters and settings

0x4E S e t C on t r o l l e r T im e Used to set the time for thecontroller

0x53 I n i t i a l i ze C o nt r o l l e r Removes all configurationsettings stored for the controller

0x54 R e s et C o nt r o l l e r Resets power to the controller

Hub Subnet Commands

0x60 I n i t i a l i ze H u bClears all Subnet Nodeconfiguration information stored inthe Hub’s flash memory

0x61 R e s e t H u b Performs an electrical reset of theHub

0x62 I n i t i a l i ze A l l N o de s

Removes all stored configurationinformation for all nodes andreconfigures them to factorydefaults

0x63 I n i t i a l i ze A l l N o deM a c r os

Removes all stored macros fromall nodes

0x70 S t a r t S u b ne t Instructs the Hub to begin“polling” the Subnet network


P / N : 1 7 - 1 3 0 9 R E V 0 2 ( 0 6 / 0 7 ) P A G E 6 2 O F 7 4


0x79 C l e a r P e n d i n gR e s p o n s e

Deletes all pending or bufferedresponses in the Hub and resetsall Instance Counters to zero

Multi-Tag RFID Commands

0x92 M u l t i - T a g R e a d I Da n d D a t a A l l

Retrieves the tag ID number and acontiguous segment of data from allRFID tags in range

0x95 M u l t i - T a g B l o c kR e a d A l l

Retrieves a contiguous segment ofdata from all RFID tags in range

0x96 M u l t i - T a g B l o c kW r i t e A l l

Writes a contiguous segment of datato all RFID tags in range

0x97 M u l t i - T a g G e tI n v e n t o r y

Retrieves the tag ID number from allRFID tags found in range

0x98 M u l t i - T a g S e a r c hA l l

Checks for the presence of RFID tagsin RF range and returns only thenumber of tags found

0xA5 M u l t i - T a g B l o c kR e a d b y I D

Reads a contiguous segment of datafrom a specific RFID tag identified byits tag ID

0xA6 M u l t i - T a g B l o c kW r i t e b y I D

Writes a contiguous segment of datato a specific RFID tag identified by itstag ID

Table 6-1: RFID Commands Table


P / N : 1 7 - 1 3 0 9 R E V 0 2 ( 0 6 / 0 7 ) P A G E 6 3 O F 7 4

6.2 ERROR CODE TABLE

E r r o rC o d e

E r r o r D e s c r i p t i o n

0x04 FILL TAG FAILED Fill Tag Command Failed

0x05 READ DATA FAILED Read Data Command Failed

0x06 WRITE DATA FAILED Write Data Command Failed

0x07 READ TAG ID FAILED / TAGSEARCH FAILED

Read Tag ID Command Failed, TagSearch Command Failed (Tag NotFound)

0x21 INVALID SYNTAX Command Contained a Syntax Error

0x23 INVALID TAG TYPE Invalid Tag Type Specified

0x30 INTERNAL CONTROLLERERROR

Generic Internal Controller Error

0x31 INVALID CONTROLLER TYPE Invalid Controller Type (when settingconfiguration)

0x34 INVALID VERSION Invalid Software Version Specified (whensetting configuration)

0x35 INVALID RESET Invalid Hardware Reset

0x36 WRITE CONFIGURATIONFAILED

Set Configuration Command Failed

0x37 READ CONFIGURATIONFAILED

Get Configuration Command Failed

0x80 UNKNOWN HUB ERROR Generic Hub Error – an undeterminederror occurred.

0x81 COMMAND MALFORMED Generic Command Syntax Error

0x82 COMMAND PROTOCOLMISMATCH

An invalid protocol value was specified inthe command

0x83 COMMAND INVALID OPCODE An invalid Opcode (Command IDnumber) was specified in the command

0x84 COMMAND INVALIDPARAMETER

A parameter specified in the commandwas invalid

0x85 COMMAND INVALIDCONTROLLER ID

A Controller ID (Node ID) specified in thecommand was invalid, or no controllerdetected/present at the specified node

0x86 COMMAND INACTIVECONTROLLER ID

A Controller ID (Node ID) specified in thecommand is currently inactive.

0x87 SUBNET DEVICE SELECTFAILED

Internal Subnet Error – the specifiedSubnet device failed.


P / N : 1 7 - 1 3 0 9 R E V 0 2 ( 0 6 / 0 7 ) P A G E 6 4 O F 7 4

0x88 SUBNET DEVICE FAILED TOACKNOWLEDGE

Internal Subnet Error - the specifiedSubnet device failed to respond to theHub’s polling.

0x89 SUBNET RESPONSEMALFORMED

Internal Subnet Error – a controllerreturned a malformed response.

0x8A SUBNET RESPONSETIMEOUT

Internal Subnet Error – a controller wasunable to generate a response beforetimeout was reached.

0x8B SUBNET RESPONSE INVALIDCHECKSUM

Internal Subnet Error – a controllergenerated a response that has an invalidchecksum.

0x8C SUBNET DEVICE CONFLICTDETECTED

Internal Subnet Error – a Node IDconflict has been detected

0x8D BUFFER OVERFLOW Internal Hub Error – Hub buffer limit wasexceeded

0x8E FLASH FAILURE Internal Hub Error – Hub flash memoryfailure

0x92 SUBNET16 ONLY COMMAND A Subnet16-only command was issuedwhen in MUX32 mode.

0x93 NODE MISMATCH ERROR The Node ID specified in the commanddid not match the Node to which thecommand was sent.

0x94 CRC ERROR Cyclic Redundancy Check Error

0x95 PROTOCOL ERROR Internal Communications Error

Table 6-2: Error Code Table


P / N : 1 7 - 1 3 0 9 R E V 0 2 ( 0 6 / 0 7 ) P A G E 6 5 O F 7 4

6.3 ERROR RESPONSE PACKET STRUCTURE

Below is the packet structure of a CBx error response. Note that the one-byte ErrorCode value is returned in the MSB of the seventh data word.

ERROR RESPONSE ELEMENT MSB LSB

Overall Length: 2-byte value indicating thenumber of “words” in the Response Packet.This value will always be at least 7 words (6 +1 for the error code).

0x00 0x07

Error Flag: 0xFF in the MSB indicates that anerror occurred.Error Information Byte: 0xFF in the LSBindicates that a controller-based erroroccurred. Any value other than 0xFF indicatesthat a Hub-based error occurred (and indicatesthe command that was attempted when theerror occurred).

0xFF 0xFF

Instance Counter: This 1-byte value tallies thenumber of responses from a given Node ID.Node ID Echo: The 1-byte LSB value indicatesthe Node ID of the controller for which thecommand was intended.

<IC> 0x01

Month and Day Timestamp <Month> <Day>

Hour and Minute Timestamp <Hour> <Minute>

Seconds Timestamp in MSBAdditional Data Length in LSB (0x01 forError Code )

<Seconds> 0x01

Error Code: 1-byte Error Code in MSB0x00 in LSB

<Error Code> 0x00

Table 6-3: CBx Error Response Packet Structure


P / N : 1 7 - 1 3 0 9 R E V 0 2 ( 0 6 / 0 7 ) P A G E 6 6 O F 7 4

6.4 ERROR RESPONSE EXAMPLE

Below is an example of a typical controller generated error response following afailed Read Data Command. For this example, a “tag not found” error was generated.

ERROR RESPONSE ELEMENT MSB LSB

0x00 in MSBOverall Length of Response in LSB(in words)

0x00 0x07

Error Flag in MSBError Information Byte in LSB

0xFF 0xFF

0x00 in MSBNode ID Echo in LSB

0x00 0x01

Month and Day Timestamp:(March 19th)

0x03 0x13

Hour and Minute Timestamp(9:30: AM)

0x09 0x1E

Seconds Timestamp in MSB(:03 seconds)Additional Data Length in LSB (0x01 for ErrorCode )

0x03 0x01

Error Code in MSB: (0x07 = Tag not Found )0x00 in LSB

0x07 0x00

H U B - 0 4 - T C P - 0 1 A P P E N D I X A :O P E R A T O R S M A N U A L H U B S P E C I F I C A T I O N S

P / N : 1 7 - 1 3 0 9 R E V 0 2 ( 0 6 / 0 7 ) P A G E 6 7 O F 7 4

APPENDIX A:HUB SPECIFICATIONS

E L E C T R I C AL

Supply Voltage 10~30VDC

Power Consumption 250mA @ 24VDC (6W)

C O M M U N I C AT I O N

Communication Interfaces Point-to-Point: RS485

Multi-drop: Subnet16, MUX32, RS485

Ethernet: TCP/IP

RFID Interface: HUB HF-Series RFID System

RF Output Power: 1W

Air Protocols ISO 15693, ISO 14443 A

Air Protocol Speed: 26.5kBaud / 106kBaud with CRC error detection

RS485 Baud Rates 9600 (default), 19.2k, 38.4k, 57.6k, 115.2k

M E C H A N I C A L

Dimensions 185mm x 89mm x 32mm (7.3” x 3.5” x 1.25”)

Weight 475 grams (16.75 ounces)

Enclosure: Stainless Steel 304 (18-8)

E N V I R O N M E N T A L

Operating Temperature -20° to 50°C (-4° to 122°F),

Storage Temperature -40° to 85°C (-40° to 185°)

Humidity 90% Non-Condensing

Protection Class IP31

Shock Resistance IEC 68-2-27 Test EA 30g, 11 milliseconds, 3 shockseach axis

Vibration Resistance IEC 68-2-6 Test FC 1.5mm; 10 to 55Hz;2 hours each axis

NOTE: Specifications are subject to change without notice.

H U B - 0 4 - T C P - 0 1 A P P E N D I X B :O P E R A T O R S M A N U A L M O D E L S & A C C E S S O R I E S

P / N : 1 7 - 1 3 0 9 R E V 0 2 ( 0 6 / 0 7 ) P A G E 6 8 O F 7 4

APPENDIX B:MODELS & ACCESSORIES

Escort Memory Systems designs, manufactures and distributes a wide range of High-Frequency RFID equipment including RFID controllers, Industrial and TCP/IP RFIDHubs, RFID tags and the cables needed to make it all work. This section of themanual lists some of the products and accessories available for the Hub. Topurchase any of the items listed below see your EMS distributor, visit www.ems-rfid.com or contact us directly at (800) 626-3993. Please let us know if you have anyquestions.

SUBNET16 HUB MODELS

HUB-04-IND-01

Subnet16™ Industrial Ethernet Hub for Ethernet/IP, Modbus TCP and TCP/IPapplications

HUB-04-TCP-01

Subnet16™ TCP/IP Hub for commercial Ethernet (TCP/IP) applications

RFID CONTROLLERS

RS485-based RFID controllers supported by the Subnet16 Hub include:

HF-0405-485-01 for RS485 interface connections

HF-CNTL-485-01 for RS485 interface connections

C0405-485-01 for RS485 interface connections

C1007-485-01 for RS485 interface connections


P / N : 1 7 - 1 3 0 9 R E V 0 2 ( 0 6 / 0 7 ) P A G E 6 9 O F 7 4

SUBNET16 CABLES & CONNECTORS

E M S P / N D E S C R I P T I O N

CBL-1480-XX Cable: M12, 5-pin, Male/Female, ThinNet

CBL-1482-XX Cable: M12, 5-pin, Male/Right-Angle Female, ThinNet

CBL-1487 Field Mountable Connector: 5-pos, Straight Female M12,

CBL-1491 Connector: 5-pos, Right-Angle Female M12, Field Mountable

CBL-1494-01 Cable: M12, 5P, F/Bare Wire Leads, ThinNet, 1M

CBL-1498-02 Cable: M12, 5P, M/Bare Wire Leads, ThinNet, 2M

Table B-0-1: Subnet16 Cables & Connectors


P / N : 1 7 - 1 3 0 9 R E V 0 2 ( 0 6 / 0 7 ) P A G E 7 0 O F 7 4

SOFTWARE UTILITIES

Cobalt HF TCP/IP Dashboard

Communicate in real time with one or more readers directly or via Multi-drop network.Allows users to configure, monitor and control their RFID devices from anywhere ontheir network.

C-Macro Builder

An easy to use, GUI-driven utility that provides rapid development andimplementation of custom RFID macros.

TCP/IP Devices IP Address Retrieval Utility

This utility is used to retrieve the DHCP-assigned IP address of the TCP/IP Hub. Filename: GWY TCP dgdiscvr.zip.

NOTE:

Software utilities and User’s Manuals are available at www.ems-rfid.com

POWER SUPPLIES

00-1166

1.88A max @ 24VDC (45W), Universal Input (90-264VAC, 47-63Hz), 5.5x2.5mmplug, positive tip; Note: Requires country specific power cord to mate to IEC 320power cord receptacle.

00-1167

4.17A max @ 24VDC (100W), Universal Input (90-264VAC, 47-63Hz), 5.5x2.5mmplug, positive tip; Note: Requires country specific power cord to mate to IEC 320power cord receptacle.

00-1168

5.0A max @ 24VDC (120W), Universal Input (88-132VAC/176-264VAC switchselectable, 47-63Hz) DIN Rail Mount; Note: AC wire receptacles are spring clamp fordirect wire connection.


H U B - 0 4 - T C P - 0 1 A P P E N D I X C :O P E R A T O R S M A N U A L N E T W O R K D I A G R A M

P / N : 1 7 - 1 3 0 9 R E V 0 2 ( 0 6 / 0 7 ) P A G E 7 1 O F 7 4

APPENDIX C:NETWORK DIAGRAM

Subnet16 Hub Ethernet Network Diagram

H U B - 0 4 - T C P - 0 1 A P P E N D I X D :O P E R A T O R S M A N U A L A S C I I C H A R T

P / N : 1 7 - 1 3 0 9 R E V 0 2 ( 0 6 / 0 7 ) P A G E 7 2 O F 7 4

APPENDIX D:ASCII CHART

H U B - 0 4 - T C P - 0 1 A P P E N D I X D :O P E R A T O R S M A N U A L A S C I I C H A R T

P / N : 1 7 - 1 3 0 9 R E V 0 2 ( 0 6 / 0 7 ) P A G E 7 3 O F 7 4

H U B - 0 4 - T C P - 0 1 E M S W A R R A N T YO P E R A T O R S M A N U A L

P / N : 1 7 - 1 3 0 9 R E V 0 2 ( 0 6 / 0 7 ) P A G E 7 4 O F 7 4

EMS WARRANTYEscort Memory Systems warrants that all products of its own manufacturing conform to EscortMemory Systems’ specifications and are free from defects in material and workmanship whenused under normal operating conditions and within the service conditions for which they werefurnished. The obligation of Escort Memory Systems hereunder shall expire one (1) year afterdelivery, unless otherwise specified, and is limited to repairing, or at its option, replacingwithout charge, any such product that in Escort Memory Systems’ sole opinion proves to bedefective within the scope of this Warranty.

In the event Escort Memory Systems is not able to repair or replace defective products orcomponents within a reasonable time after receipt thereof, Buyers shall be credited for theirvalue at the original purchase price. Escort Memory Systems must be notified in writing of thedefect or nonconformity within the warranty period and the affected product returned to EscortMemory Systems factory or to an authorized service center within thirty (30) days afterdiscovery of such defect or nonconformity. Shipment shall not be made without priorauthorization by Escort Memory Systems.

This is Escort Memory Systems' sole warranty with respect to the products deliveredhereunder. No statement, representation, agreement or understanding oral or written, made byan agent, distributor, representative, or employee of Escort Memory Systems which is notcontained in this warranty, will be binding upon Escort Memory Systems, unless made inwriting and executed by an authorized Escort Memory Systems employee.

Escort Memory Systems makes no other warranty of any kind what so ever, expressed orimplied, and all implied warranties of merchantability and fitness for a particular use whichexceed the aforementioned obligation are here by disclaimed by Escort Memory Systems andexcluded from this agreement.

Under no circumstances shall Escort Memory Systems be liable to Buyer, in contract or in tort,for any special, indirect, incidental, or consequential damages, expenses, losses or delayhowever caused. Equipment or parts that have been subject to abuse, misuse, accident,alteration, neglect, unauthorized repair or installation are not covered by warranty. EscortMemory Systems shall make the final determination as to the existence and cause of anyalleged defect. No liability is assumed for expendable items such as lamps and fuses.

No warranty is made with respect to equipment or products produced to Buyer’s specificationexcept as specifically stated in writing by Escort Memory Systems in the contract for suchcustom equipment. This warranty is the only warranty made by Escort Memory Systems withrespect to the goods delivered hereunder, and may be modified or amended only by a writteninstrument signed by a duly authorized officer of Escort Memory Systems and accepted by theBuyer.

Extended warranties of up to four years are available for purchase for most Escort MemorySystems products. Contact Escort Memory Systems or your distributor for more information.

EMS™ and the Escort Memory Systems logo are registered trademarks of Escort MemorySystems, a Datalogic Group Company.

Copyright © 2005-2007 Escort Memory Systems, ALL RIGHTS RESERVED

Date post:	19-Jan-2019
Category:	Documents
Upload:	truongliem
View:	215 times
Download:	0 times

HUB-04-CP-01T - Balluffusa.balluff.com/manuals/Balluff_EMS RFID(Former Datalogic)/HUB-04... · EMS...

Documents