Balluff C0405 Cobalt HF RFID Reader User Manual C0405 Operator s Manual

BALLUFF inc Cobalt HF RFID Reader C0405 Operator s Manual

User Manual

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 oromissions 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®, the EscortMemory Systems logo, Subnet16™ and RFID AT WORK™.Third party product names mentioned herein are used for identification purposes onlyand may be trademarks and/or registered trademarks of their respective companies:Philips, Rockwell Automation, Texas Instruments, Infineon, Belden and Microsoft.ESCORT  MEMORY  SYSTEMSCobalt  C0405-SeriesC0405-XXX-01 RFID Controller - Operators ManualFor C0405-Series RFID ControllersPublication P/N: 17-1328 REV 02 (08/07)COPYRIGHT  ©  2007  ESCORT  MEMORY  SYSTEMS,  ALL  RIGHTS  RESERVED,  PUBLISHED  IN  USA.E
For C0405 models:•C0405-232-01•C0405-485-01•C0405-USB-01ESCORT  MEMORY  SYSTEMSCOBALT C0405-SERIESRFID CONTROLLERSHigh Frequency, Multi-Protocol, Passive RFID ControllersOPERATORSMANUALHow to Install, Configure and OperateCobalt C0405-Series RFID Controllers
REGULATORY COMPLIANCE -PENDINGFCC PART 15.105This 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 whichthe receiver is connected.•  Consult the dealer or an experienced radio/TV technician for help.FCC PART 15.21Users 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.”This product complies with CFR Title 21 Part 15.225.CEThis product complies with the following regulatory specifications: EN-300-330, EN-300-683, EN 60950, IEC 68-2-1, IEC 68-2-6, IEC 68-2-27 and IEC 68-2-28.TELECThis product complies with TELEC Regulations for Enforcement of the Radio LawArticle 6, section 1, No. 1. Cert #: (PENDING)
                                                                             CONTENTSP/N:  17-1328  REV  02  (08/07)           PAGE 5 OF 83CONTENTSCONTENTS  .................................................................................... 5LIST  OF TABLES................................................................................................8LIST  OF FIGURES ..............................................................................................9CHAPTER  1: GETTING  STARTED ................................................101.1 INTRODUCTION........................................................................................101.1.1 Company  Background ................................................................................................101.1.2 The C0405-Series  RFID  Controller ............................................................................. 101.1.3 C0405  RFID  Controller  Features.................................................................................111.1.4 Abou t  th is  Manu al.......................................................................................................111.1.5 HEX  Notation..............................................................................................................121.1.6 Contents of the C0405 Product Package ....................................................................121.1.7 Us er  Su pp lied  Compone nts........................................................................................131.2 COMMUNICATION OPTIONS .......................................................................141.2.1 Connection and Communication Interface Options......................................................141.2.2 C0405 Controllers - Interface Connectors ...................................................................14CHAPTER  2: INSTALLING  THE  C0405..........................................152.1 PREPARING  FOR INSTALLATION.................................................................152.1.1 Installation  Guidelines.................................................................................................152.1.2 C0 40 5  Co ntroller  D imens ions.....................................................................................162.1.3 Mounting  the  Contro ller...............................................................................................172.1.4 Proximity  to  Metal.......................................................................................................182.2 INSTALLING  THE C0405-232-01 CONTROLLER............................................192.2.1 Steps to Install the C0405-232-01...............................................................................192.2.2 C0405-232-01  Cabling  Inform ation ................ ........ ................ ................ ........ .............202.3 INSTALLING  THE C0405-485-01 CONTROLLER............................................222.3.1 Steps to Install the C0405-485-01...............................................................................222.3.2 C0405-485-01  Cabling  Inform ation ................ ........ ................ ................ ........ .............232.4 INSTALLING  THE C0405-USB-01 CONTROLLER ..........................................242.4.1 Steps to Install the C0405-USB-01..............................................................................242.4.2 C0405-USB-01  Cabling  Inform ation........ ........ ........ ........ ........ ........ ........ ........ ........ ....252.5 ANTENNA ENVIRONMENT..........................................................................262.5.1 Typical Read Range - Front View* for SLi 54x86mm RFID Tags .................................262.5.2 Typical Read Range - Side Profile* for SLi 54x86mm RFID Tags................................272.5.3 Typical Read Range - Front View* for HMS / Mifare RFID Tags..................................282.5.4 Typical Read Range - Side Profile* for HMS / Mifare RFID Tags.................................292.5.5 C0405 Antenna to EMS Tag Ranges ..........................................................................30CHAPTER  3: POWER  &  COMMUNICATION...................................313.1 POWER REQUIREMENTS ...........................................................................313.1.1 C0405-232-01/C0405-485-01 Power Requirements....................................................313.1.2 C0405-USB-01  Power  Requirements.... ....... .............. .............. .............. .............. .......31
                                                                             CONTENTSP/N:  17-1328  REV  02  (08/07)           PAGE 6 OF 833.2 HF-SERIES CONFIGURATION TAG..............................................................323.2.1 Co nfigura tion  Tag  Over view........................................................................................323.2.2 Configuration  Tag  Memory  Map.................................................................................. 333.2.3 Using  the  Configuration  Tag .......................................................................................33CHAPTER  4: LED  STATUS ..........................................................354.1 LED FUNCTIONS OVERVIEW .....................................................................354.1.1 LED  Descriptions........................................................................................................364.1.2 C0 405- 23 2  LED  Status...............................................................................................374.1.3 C0 405- USB  LED  Status ..............................................................................................374.1.4 C0 405- 48 5  LED  Status...............................................................................................384.2 SPECIAL LED OPERATION FUNCTIONS.......................................................404.2.1 Updating  the Controller’s Firmware.............................................................................404.2.2 Continuous Read Mode – LED Behavior.....................................................................414.3 LED DISPLAYED ERROR CODES ...............................................................42CHAPTER  5: RFID  TAGS .............................................................435.1 RFID TAG OVERVIEW ..............................................................................435.1.1 RFID  Standards.......................................................................................................435.2 EMS RFID TAGS ....................................................................................455.2.1 HMS-Series  Tags .......................................................................................................455.2.2 LRP-Series  Tags ........................................................................................................465.3 TAG EMBODIMENTS .................................................................................475.3.1 Printed Circuit Board RFID Tags.................................................................................475.3.2 Molded  RFID  Tags .....................................................................................................475.4 TAG MEMORY .........................................................................................485.4.1 Mapp ing  Tag  Memory.................................................................................................485.4.2 Creating an RFID Tag Memory Map ...........................................................................485.4.3 Opt im iz ing  Tag  Me mory..............................................................................................49CHAPTER  6: COMMAND  PROTOCOLS.........................................516.1 ABXCOMMAND PROTOCOL OVERVIEW ......................................................516.1.1 ABx  Command  Structures ........................ ........................................ ..........................526.1.2 ABx Protocols - Headers and Terminators ..................................................................526.1.3 AB x  Res po ns e  Stru cture s...........................................................................................526.2 ABXFAST COMMAND PROTOCOL..............................................................536.2.1 ABx Fast - Command / Response Procedure..............................................................536.2.2 ABx Fast - Command Packet Structure.......................................................................546.2.3 ABx Fast - Response Packet Structure.......................................................................556.2.4 ABx Fast - Command Packet Parameters...................................................................566.3 ABXSTANDARD COMMAND PROTOCOL......................................................586.3.1 ABx Standard - Command Packet Structure ...............................................................596.3.2 ABx Standard - Response Packet Structure................................................................596.3.3 ABx Standard - Command Example............................................................................60CHAPTER  7: RFID  COMMANDS  AND  ERROR  CODES ...................617.1 ABXFAST RFID COMMAND TABLE............................................................61
                                                                             CONTENTSP/N:  17-1328  REV  02  (08/07)           PAGE 7 OF 837.2 ABXSTANDARD RFID COMMAND TABLE ...................................................637.3 ERROR CODES ....................................................................................647.4 ABXERROR CODE TABLE........................................................................657.5 ABXFAST ERROR RESPONSE STRUCTURE.................................................667.6 ABXSTANDARD ERROR RESPONSE STRUCTURE.........................................67APPENDIX  A:   TECHNICAL  SPECIFICATIONS................................68APPENDIX  B:   MODELS  &  ACCESSORIES .....................................70EMS HARDWARE ............................................................................................70C0405- Series  RFID  Co ntro llers ..............................................................................................70Subnet16™  Gateway  Interface Modules................................................................................70Subnet16™  Hub  Interface  Modules ....................................................................................... 70SOFTWARE & DEMONSTRATION KITS.................................................................71Software  Applications............................................................................................................71Demonstration  Kits ................................................................................................................71CABLE  AND NETWORK ACCESSORIES ................................................................72Power  Supplies .....................................................................................................................73Escort Memory Systems’ RFID Tags .....................................................................................73APPENDIX  C:   NETWORK  DIAGRAMS ...........................................747.6.1 Subnet16 Gateway – ThickNet Network Diagram .....................................................757.6.2 Subnet16 Gateway – ThinNet Network Diagram.......................................................767.6.3 Subnet16 Hub – Network Diagram ...........................................................................77APPENDIX  D:   ASCII  CHART .........................................................78APPENDIX  E:   RFID  TERMINOLOGY..............................................80EMS  WARRANTY ..........................................................................83
                                                                             CONTENTSP/N:  17-1328  REV  02  (08/07)           PAGE 8 OF 83LIST  OF TABLESTable 1-1: C0405 Product Package Contents List................................................................12Table 1-2: Connection and Communication Interface Options..............................................14Table 1-3: C0405 Controllers - Interface Connectors...........................................................14Table 2-1: C0405-232-01 Interface Connector – Pinout.......................................................20Table 2-2: C0405-485-01 Interface Connector - Pinout........................................................23Table 2-3: C0405-USB-01 Interface Connector - Pinout.......................................................25Table 2-4: C0405 Antenna to EMS Tag Ranges..................................................................30Table 3-1: EMS Power  Supplies..........................................................................................31Table 3-3: Configuration Tag - Controller Defaults...............................................................33Table 4-1: Continuous Read Mode - LED Behavior .............................................................41Table 5-1: Tag Memory Map Example.................................................................................49Table 6-1: ABx Protocols - Headers and Terminators..........................................................52Table 6-2: ABx Fast - Command Packet Structure...............................................................54Table 6-3: ABx Fast - Response Packet Structure...............................................................55Table 6-4: ABx Standard - Command Packet Structure .......................................................59Table 6-5: ABx Standard - Response Packet Structure........................................................59Table 7-1: ABx Fast RFID Command Table.........................................................................62Table 7-2: ABx Standard RFID Command Table .................................................................63Table  7-3:  ABx  Error Codes ................................................................................................65Table 7-4: ABx Fast - Error Response Structure..................................................................66Table 7-5: ABx Standard - Error Response Structure...........................................................67
                                                                             CONTENTSP/N:  17-1328  REV  02  (08/07)           PAGE 9 OF 83LIST  OF FIGURESFigure 1-1: C0405 Package Contents Diagram....................................................................13Figure 2-1: C0405 RFID Controller Dimensions...................................................................16Figure 2-2: C0405 Controller Attached to Bracket with Cable Connected.............................17Figure 2-3: C0405 Proximity to Metal...................................................................................18Figure 2-4: RS232 Interface Cable Schematic.....................................................................21Figure  2-5:  CBL-1493  Connector......................................................................................... 21Figure 2-6: Typical Read Range - Front View* for SLi 54x86mm Tags.................................26Figure 2-7: Typical Read Range - Side Profile* for SLi 54x86mm Tags................................27Figure 2-8: Typical Read Range - Front View* for HMS / Mifare Tags..................................28Figure 2-9: Typical Read Range - Side Profile* for HMS / Mifare Tags.................................29Figure 3-1: Cobalt HF Configuration Tag.............................................................................32Figure 5-1: HMS125HT and HMS150HT tags......................................................................45Figure  5-2:  LRP-Series  Tags............................................................................................... 46Figure 5-3: Optimizing Tag Memory ....................................................................................50Figure 6-1: ABx Fast - Command Packet Structure .............................................................53Figure 6-2: ABx Standard - Command Packet Structure......................................................58Figure A–0-1: C0405-Series RFID Controller Dimensions....................................................69
                   CHAPTER  1:  GETTING  STARTEDP/N:  17-1328  REV  02  (08/07)           PAGE 10  OF 83Escort Memory Systems headquarters inScotts Valley, CA.CHAPTER  1:GETTING  STARTED1.1 INTRODUCTIONWelcome to the C0405-Series RFID Controllers - Operators Manual. This manualwill assist you in the installation, configuration and operation of Escort MemorySystems’ C0405-Series RFID Controllers.The C0405-Series product family is a complete line of passive high frequencyread/write Radio-Frequency Identification solutions. These devices are designed tobe compact, reliable and rugged, in order to meet and exceed the requirements ofthe industrial automation industry.1.1.1 CompanyBackgroundEscort Memory Systems is anindustry leader in providing RadioFrequency Identification (RFID)systems.By consistently delivering anextended selection of highquality, highly durable RFIDdevices, Escort Memory Systemshas built a solid reputation.1.1.2 The  C0405-SeriesRFID  ControllerEscort Memory Systems' C0405-Series RFID Controllers are the most compact inour line of passive RFID controllers. Through inductive coupling, RFID enabled tagsare able to utilize the Radio Frequency (RF) field from the controller’s integratedantenna to acquire power. By being able to receive power from the RFID controller,the tag, itself, does not require an internal power supply or battery - and is thereforesaid to be “passive”.Passive tags, however, must enter the antenna’s electromagnetic field to establish alink with the controller, and must remain within RF range during the entire datatransfer process. The C0405 Controller uses the internationally recognized ISM(Industrial, Scientific and Medical) frequency of 13.56 MHz to power thetag, while modulating side-band frequencies for communicating data.The entire RFID system works by attaching a tag to a product or itscarrier. The RFID tag acts as an electronic identifier, portable jobsheet, or real-time tracking database. Tags are identified, readand written to by issuing specific commands from a host computer.RFID tags can be read and written to through any nonconductive,non-metallic material, while moving or standing still, in or out of thedirect line of sight.
                   CHAPTER  1:  GETTING  STARTEDP/N:  17-1328  REV  02  (08/07)           PAGE 11  OF 83The C0405-Series controllers provide cost effective RFID data collection and controlsolutions to shop floor, item-level tracking and material handling applications. Theyare compatible with all LRP and HMS and T-Series RFID tags from Escort MemorySystems.1.1.3 C0405  RFID  Controller  Features§  High performance, low-cost, 13.56MHz RFID controller with integrated RFantenna§  Supports multiple RF, ABx, air and serial communications protocols§  Small controller size: approximately 40mm x 50mm - internal antennadimensions: 36mm x 36mm§  Flash memory for software updates and configuration storage§  Auto configurable / software programmable§  Eight LED indicators display power, COM port activity, RF activity, Subnet16Node ID, system diagnostics, error codes and controller status§  Reads/Writes ISO 14443A and ISO 15693 compatible RFID tags - range upto 50mm with ISO 144433 tags and 90mm with ISO 15693 tags§ Reads/Writes LRP, HMS, and T-Series tags from EMS§  FCC/CE/TELEC agency compliance certification (PENDING)§  IP67 rated M12 interface connector (8-pin for RS232, 5-pin for RS485/USB)§  Fully encapsulated electronics1.1.4 About  this  ManualThis manual provides guidelines and instructions on how to install and operateC0405-Series RFID Controllers. Also included are descriptions of the RFID commandset with instructions describing how to issue commands to the C0405-Series RFIDControllers.NOTE:Occasionally in this manual, the C0405-Series RFID Controller is referred to as theC0405 Controller, the C0405 or just simply the controller.Who  Should  Read  this  Manual?This manual should be read by those who will be installing, configuring and operatingC0405-Series RFID Controllers. This may include the following people:§  System Integrators§  Project Managers§  IT Personnel§  System and Database Administrators§  Software Application Engineers§  Service and Maintenance Engineers
                   CHAPTER  1:  GETTING  STARTEDP/N:  17-1328  REV  02  (08/07)           PAGE  12  OF 831.1.5 HEX  NotationThroughout 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.1.1.6 Contents  of  the  C0405  Product  PackageUnpack the C0405 hardware and accessories. Inspect each item for evidence ofdamage. If an item appears to be damaged, notify your distributor or EMS.The C0405 product package contains the following components:QTY DESCRIPTION1C0405-XXX-01 RFID Controller1C0405-XXX-01 RFID Controller – Installation Guide1Cobalt HF Configuration Tag (I-CODE SLi)1Mounting Bracket2Screws (M4, 20mm, PPH 18-8\302 SS)2Washers (M4 locking)2Nuts (M4, 18-8\302 SS)Table 1-1: C0405 Product Package Contents ListNote: XXX = 232, 485 or USB
                   CHAPTER  1:  GETTING  STARTEDP/N:  17-1328  REV  02  (08/07)           PAGE  13  OF 83Figure 1-1: C0405 Package Contents Diagram1.1.7 User  Supplied  ComponentsTo configure a complete RFID system, you will need to provide the following items:•HMS, LRP, or T-Series RFID tags•Controller-to-Host communication interface cable: (RS232, RS485 or USB)•Host device: (PC, PLC, MUX32, TCP/IP, Ethernet/IP, Subnet16 Gatewayor Hub)•LPS (Limited Power Source) power supply: 10~30VDC, 2.4W (100mA @24VDC) - per controller•Mating connectors: (when applicable)
                   CHAPTER  1:  GETTING  STARTEDP/N:  17-1328  REV  02  (08/07)           PAGE  14  OF 831.2 COMMUNICATION OPTIONSThere are three distinct versions of the C0405-Series RFID Controller. Each modelprovides support for one specific communication interface requirement.Through the Subnet16 protocol, multiple C0405-485-01 controllers can be networkedvia a single bus that is connected to an EMS Subnet16 Gateway or Hub interfacemodule.1.2.1 Connection  and  Communication  Interface  OptionsCONTROLLERMODEL CONNECTIONTYPE COMMUNICATIONINTERFACE MAX  CABLELENGTHC0405-232-01 RS232 Point-to-Point, Host/Controller  15 MetersC0405-485-01 RS485 Subnet16 Multidrop busarchitecture via Subnet16™Gateway or Hub300 MetersC0405-USB-01 USB 2.0 Point-to-Point, Host/Controller  5 MetersTable 1-2: Connection and Communication Interface Options1.2.2 C0405  Controllers  -  Interface  ConnectorsCONTROLLER  MODEL INTERFACE  CONNECTORC0405-232-01 8-pin, male M12 connectorC0405-485-01 5-pin, male M12 connectorC0405-USB-01 5-pin, male, reverse keyed M12 connectorTable 1-3: C0405 Controllers - Interface ConnectorsSee Appendix B: Models & Accessories for more information on model numbers,parts and accessories for all C0405-Series RFID Controllers.
   CHAPTER  2:  INSTALLING  THE  C0405P/N:  17-1328  REV  02  (08/07)           PAGE  15  OF 83CHAPTER  2:INSTALLING  THE  C04052.1 PREPARING  FOR INSTALLATIONC0405-Series RFID Controllers support direct connections for point-to-point(host/controller) applications (RS232, RS485 and USB). Up to 16 C0405-485 unitscan be networked via Subnet16 Gateway interface module and Escort MemorySystems’ Subnet16™ Multidrop Bus Architecture. Host/controller data transmission isachieved via 5-pin or 8-pin serial interface cable.2.1.1 Installation  Guidelines•Conduct a test phase where you will construct a small scale, independentnetwork that includes only the essential devices required to test your RFIDapplication. To avoid possible interference with other devices, do not initiallyconnect your RFID testing environment to an existing local area network.•RF performance and read/write range can be negatively impacted by theproximity of metallic objects. Avoid mounting the controller within 44mm (1.75inches) of any metallic object or surface.•If electrical interference is encountered (as indicated by a reduction inread/write performance), relocate the controller to an area free from potentialsources of interference.•Route cables away from other unshielded cables and away from wiringcarrying high voltage or high current. Avoid routing cables near motors andsolenoids.•Refrain from mounting the controller near sources of EMI (electro-magneticinterference) or near devices that generate high ESD (electro-staticdischarge) levels.•Always use adequate ESD prevention measures to dissipate potentially highvoltages. Cobalt controllers are designed to withstand 8kV of direct electro-static discharge (ESD) and 15kV of air gap discharge. However, it is notuncommon for some RFID applications to generate considerably higher ESDlevels.•For applications using multiple RFID controllers operating at the 13.56 MHzfrequency, maintain a minimum distance of at least 20 centimeters betweenadjacent RF devices.
   CHAPTER  2:  INSTALLING  THE  C0405P/N:  17-1328  REV  02  (08/07)           PAGE  16  OF 832.1.2 C0405  Controller  DimensionsThe images below contain the dimensions of the Cobalt C0405-Series RFIDControllers in millimeters and [inches].Figure 2-1: C0405 RFID Controller Dimensions
   CHAPTER  2:  INSTALLING  THE  C0405P/N:  17-1328  REV  02  (08/07)           PAGE  17  OF 832.1.3 Mounting  the  ControllerC0405-Series RFID Controllers can be mounted to wood or plastic fixtures. The units’ship with an L-shaped, polycarbonate, mounting bracket and the necessary hardwarerequired to fasten the controller to the bracket. The bracket is designed to help isolatethe RFID controller from metal surfaces and the affect of spurious noise electronicallyconducted through metal.NOTE: The controller may be mounted horizontally or vertically, but should be alignedin such a manner that the LED indicators can be seen during operation.1. Select a suitable location to mountthe C0405 Controller.2. Attach the C0405 Controller to themounting bracket using the two setsof M4 screws, washers and nutsprovided. Place the nuts in each ofthe two hex-shaped recessedcavities at the rear of the C0405.3. After aligning the mounting bracketwith the two mounting holes on thecontroller, insert both M4 screws(with washers) into the controllerfrom the underside and tightencompletely using a standard Phillips#2 head screwdriver.4. Fasten the other end of the mountingbracket to your work area.Torque  SpecificationTighten the two M4 screws used to fasten the controller to the bracket (and any userprovided screws used to mount the bracket to the work area) to the following torquesetting: 0.7 Nm or equivalent to 6 lbs / inchFigure 2-2: C0405 Controller Attached to Bracket with Cable Connected
   CHAPTER  2:  INSTALLING  THE  C0405P/N:  17-1328  REV  02  (08/07)           PAGE  18  OF 832.1.4 Proximity  to  MetalRFID devices can be negatively impacted by the presence of metallic objects. Avoidmounting the controller within 44mm (approximately 2 inches) of metal surfaces ornear sources of electro magnetic interference (EMI) and electrical noise.Figure 2-3: C0405 Proximity to Metal
   CHAPTER  2:  INSTALLING  THE  C0405P/N:  17-1328  REV  02  (08/07)           PAGE  19  OF 832.2 INSTALLING  THE C0405-232-01 CONTROLLERThe C0405-232-01 RFID Controller is designed for point-to-point RFID applications,where the distance from host to controller is less than 15 meters (50 feet). Thecontroller connects directly to a serial communications port on a host computer via anRS232-compatible interface cable.NOTE: review Section 2.1.1 Installation Guidelines prior to installing the controller.2.2.1 Steps  to  Install  the  C0405-232-011. Attach the controller to the mounting bracket and work area as noted in Section2.1.3 Mounting the Controller.2. Connect the 8-pin, female M12 connector from your serial interface cable (EMSP/N: CBL-1478) to the 8-pin, male M12 connector on the C0405-232-01.3. Connect the serial interface cable‘s female DE9 D-Sub connector to a COM porton the host computer. Tighten the cable’s two locking thumbscrews.4. Connect the 2.5mm DC power plug on the power supply transformer to the DCpower jack receptacle on the serial interface cable. Tighten the locking ring toprevent power from becoming disconnected during use.5. Plug the power supply transformer into a suitable AC power source. Apply powerto the controller after all cable connections have been made. The LEDs on theunit will flash. For the C0405-232 model, the amber Node 20 LED will remain lightto indicate that the controller is in RS232 mode.6. On the host computer, set COM port parameters to: 9600 baud, 8 data bits, 1stop bit, no parity and no handshaking.7. To verify operations, download the serial version of the Cobalt HF DashboardUtility software application from Escort Memory Systems’ website (www.ems-rfid.com). The Dashboard Utility allows users to send RFID commands to thecontroller for testing purposes.23 21PWR24422 20COMR FRF FIELDLED 20willilluminate toindicateRS232mode.
   CHAPTER  2:  INSTALLING  THE  C0405P/N:  17-1328  REV  02  (08/07)           PAGE  20  OF 832.2.2 C0405-232-01  Cabling  InformationThe C0405-232-01 has one 8-pin, male M12 interface connector.C0405-232-01  Interface  Connector  -  PinoutPIN  # DESCRIPTION110~30VDC POWER20VDC (POWER GROUND)3NOT CONNECTED4NOT CONNECTED5NOT CONNECTED6RX7TX8SGND (SIGNAL GROUND)Table 2-1: C0405-232-01 Interface Connector  PinoutC0405-232-01  Interface  Connector  -  DiagramCabling  Part  Numbers  for  the  C0405-232-01•CBL-1478: Cable Assembly (8-pin, female M12 to RS232; with 2.5mm DC powerjack, 2m)•CBL-1488-XX: Cable (8-pin, female M12 to bare wire leads)•CBL-1492-XX: Cable (8-pin, right-angle female M12 to bare wire leads)•CBL-1493: Connector (8-pos, straight female M12, field mountable) (XX = Cable Length in Meters)
   CHAPTER  2:  INSTALLING  THE  C0405P/N:  17-1328  REV  02  (08/07)           PAGE  21  OF 83RS232  Serial  Interface  Cable  SchematicIf you intend to assemble your own RS232 serial interface cable, follow the schematicbelow. Note that signals and electrical loads applied to Pin 6 (RX) and Pin 7 (TX)should conform to RS232 specifications. For bulk RS232 cable, see Belden cableP/N: 9941 (www.belden.com).Figure 2-4: RS232 Interface Cable SchematicCBL-1493:  Field  Mountable  ConnectorFigure 2-5: CBL-1493 ConnectorThe CBL-1493 field mountable connector is available for connecting the C0405-232to a host PC via bulk cable. (See Appendix B for more information regarding cablesand connectors for the entire line of C0405-Series RFID Controllers).
   CHAPTER  2:  INSTALLING  THE  C0405P/N:  17-1328  REV  02  (08/07)           PAGE  22  OF 832.3 INSTALLING  THE C0405-485-01 CONTROLLERThe C0405-485-01 RFID Controller supports RS485 communications and EscortMemory Systems’ Subnet16™ Multidrop bus architecture and RFID network protocol.Through the Subnet16 protocol, multiple C0405-485-01 units can be connected toone Subnet16™ RFID Gateway or Hub interface device. The Gateway or Hubassigns each attached C0405-485-01 a unique Node ID number through whichcommunication with a host PC and/or Programmable Logic Controller (PLC) isachieved.NOTE: review Section 2.1.1 Installation Guidelines prior to installing the controller.2.3.1 Steps  to  Install  the  C0405-485-011. Attach the controller to the mounting bracket and work area as noted in Section2.1.3  Mounting the Controller.2. Connect the 5-pin, female end of your Subnet16-compatible cable to the 5-pin,male M12 interface connector on the C0405-485. Connect the opposite end ofthis cable to an EMS Subnet16 Gateway or Hub device. Connect the Gateway orHub to a host computer via Category 5E Ethernet cabling*.3. Turn the power supply ON. The green power LED will illuminate when power isapplied to the unit. The five amber Node LEDs, when lit, display the Node IDvalue (in binary format from right to left) currently assigned to the C0405-485RFID Controller. Note: the default Node ID is Node 00; in which case none of theamber Node ID LEDs will be lit.4. To verify operations, download the TCP/IP version of the Cobalt HF DashboardUtility software application from Escort Memory Systems’ website (www.ems-rfid.com). The Cobalt HF Dashboard Utility allows Gateway/Hub users to sendRFID commands to any connected controller for testing purposes.*For more information regarding the installation of a Subnet16 Gateway or Subnet16Hub, refer to the Operator’s Manual for each product, available online at www.ems-rfid.com.RF FIELD24 22PWR23 21 20COMR FYellowNodeLEDs 20 24indicate NodeID for C0405-485 model
   CHAPTER  2:  INSTALLING  THE  C0405P/N:  17-1328  REV  02  (08/07)           PAGE  23  OF 832.3.2 C0405-485-01  Cabling  InformationThe C0405-485-01 has one 5-pin, male M12 interface connector.C0405-485-01  Interface  Connector  -  PinoutPIN  # DESCRIPTION1SGND (SIGNAL GROUND)210~30VDC POWER30V (POWER GROUND)4TX/RX+5TX/RX-Table 2-2: C0405-485-01 Interface Connector - PinoutC0405-485-01  Interface  Connector  -  Diagram
   CHAPTER  2:  INSTALLING  THE  C0405P/N:  17-1328  REV  02  (08/07)           PAGE  24  OF 832.4 INSTALLING  THE C0405-USB-01 CONTROLLERThe C0405-USB-01 RFID Controller is designed for point-to-point RFID applicationsthat support USB 2.0 communications. Host/controller data is transmitted viastandard USB cabling.NOTE: review Section 2.1.1 Installation Guidelines prior to installing the controller.2.4.1 Steps  to  Install  the  C0405-USB-011. Download the Cobalt USB driver software bundle from the Escort MemorySystems website (www.ems-rfid.com). Extract the .zip file archive to a separatefolder on the desktop of the host computer.2. Attach the controller to the mounting bracket and work area as noted in Section2.1.3  Mounting the Controller.3. Attach the, 5-pin, reverse keyed female M12 interface connector from a suitableUSB interface cable (EMS P/N: CBL-1525) to the 5-pin, reverse keyed male M12connector on the C0405-USB.4. Plug the remaining end of the USB interface cable into a USB port on the hostcomputer. The LEDs on the Cobalt should illuminate. For the C0405-USB model,the amber LED 22 will illuminate to indicate that the controller is in USB mode.5. Install the Cobalt USB driver. Refer to the Cobalt USB Driver InstallationInstructions (EMS Publication P/N: 17-3128) that are included in the CobaltUSB driver archive.6. To verify operations, download the serial version of the Cobalt HF DashboardUtility from the EMS website (www.ems-rfid.com). The Dashboard Utility allowsusers to send RFID commands to the controller for testing purposes.24 22PWR23 21 20COMR FRF FIELDLED 22willilluminateto indicateUSBmode.
   CHAPTER  2:  INSTALLING  THE  C0405P/N:  17-1328  REV  02  (08/07)           PAGE  25  OF 832.4.2 C0405-USB-01  Cabling  InformationThe C0405-USB-01 has one 5-pin, reverse keyed male M12 interface connector.C0405-USB-01  Interface  Connector  -  PinoutPIN  # DESCRIPTION1+5V2D-3D+4GND5SHIELDTable 2-3: C0405-USB-01 Interface Connector - PinoutC0405-USB-01  Interface  Connector  -  DiagramCabling  Part  Numbers  for  the  C0405-USB-01•CBL-1513: Cable Assembly (5-pin, reverse keyed male M12 to USB Type A, 3m)•CBL-1514: Connector (5-pin, reverse keyed male M12 connector for USB)•CBL-1525: Cable Assembly (5-pin, reverse keyed female M12 to USB Type A,3m)
   CHAPTER  2:  INSTALLING  THE  C0405P/N:  17-1328  REV  02  (08/07)           PAGE  26  OF 832.5 ANTENNA ENVIRONMENTThe antenna used to communicate with RFID tags is integrated within the C0405RFID Controller. Electro-magnetic interference (EMI) and the presence of metal nearthe antenna’s RF field can negatively affect the communication range of the RFIDcontroller.2.5.1 Typical  Read  Range  -  Front  View*  for  SLi  54x86mmRFID  TagsFigure 2-6: Typical Read Range - Front View* for SLi 54x86mm Tags*Approximate Free Air H-Field Pattern
   CHAPTER  2:  INSTALLING  THE  C0405P/N:  17-1328  REV  02  (08/07)           PAGE  27  OF 832.5.2 Typical  Read  Range  -  Side  Profile*  for  SLi  54x86mmRFID  TagsFigure 2-7: Typical Read Range - Side Profile* for SLi 54x86mm Tags*Approximate Free Air H-Field Pattern
   CHAPTER  2:  INSTALLING  THE  C0405P/N:  17-1328  REV  02  (08/07)           PAGE  28  OF 832.5.3 Typical  Read  Range  -  Front  View*  for  HMS  /  MifareRFID  TagsFigure 2-8: Typical Read Range - Front View* for HMS / Mifare Tags*Approximate Free Air H-Field Pattern
   CHAPTER  2:  INSTALLING  THE  C0405P/N:  17-1328  REV  02  (08/07)           PAGE  29  OF 832.5.4 Typical  Read  Range  -  Side  Profile*  for  HMS  /  MifareRFID  Tags024681024681008 246 2 4 6 8HF-0405 Antenna Field - Side ProfileMIFARE - HMS tags1 block = 1 sq. cm. Mifare IC -CreditCard TagHMS150HMS125Figure 2-9: Typical Read Range - Side Profile* for HMS / Mifare Tags*Approximate Free Air H-Field Pattern
   CHAPTER  2:  INSTALLING  THE  C0405P/N:  17-1328  REV  02  (08/07)           PAGE  30  OF 832.5.5 C0405  Antenna  to  EMS  Tag  RangesEMS  TAG RANGELRP125S Up to 38mmLRP250 Up to 60mmLRP525 (HTS) Up to 70mmLRP-C5486S Up to 74mmHMS125 Up to 25 mmHMS150 Up to 45mmTable 2-4: C0405 Antenna to EMS Tag Ranges
                                     CHAPTER  3: POWER & COMMUNICATIONP/N:  17-1328  REV  02  (08/07)           PAGE  31  OF 83CHAPTER  3:POWER  &  COMMUNICATION3.1 POWER REQUIREMENTS3.1.1 C0405-232-01/C0405-485-01  Power  RequirementsC0405-232-01 and C0405-485-01 RFID controllers requires an agency compliantLPS power supply capable of providing 10~30VDC, 2.4W (100mA @ 24VDC).EMS Power Supplies for C0405-232 and C0405-485 RFID ControllersPART  NUMBER DESCRIPTION00-1166 45W, 1.88A max @ 24VDC00-1167 100W, 4.17A max @ 24VDC00-1168 120W, 5.0A max @ 24VDCTable 3-1: EMS Power Supplies3.1.2 C0405-USB-01  Power  RequirementsThe C0405-USB-01 RFID Controller obtains power directly from the USB bus.Typical power consumption under normal conditions = 1W (200mA @ 5VDC).CAUTION:Do not connect or disconnect the C0405 while power is being applied. Turn the powersupply off at the source prior to connecting or disconnecting the unit. Reapply poweronly after the controller has been reconnected.Use only high quality, shielded cables for power and interface connections. SeeAppendix B for a list of compatible cables and network components.
                                     CHAPTER  3: POWER & COMMUNICATIONP/N:  17-1328  REV  02  (08/07)           PAGE  32  OF 833.2 HF-SERIES CONFIGURATION TAG3.2.1 Configuration  Tag  OverviewIn the past, RFID controllers had multiple jumpers and DIP-switches that were usedto set configuration parameters. C0405-Series RFID Controllers do not requirejumpers or DIP-switches because they are software configurable via commands sentfrom a host PC as well as through the use of a Cobalt HF Configuration Tag.Figure 3-1: Cobalt HF Configuration TagIn the event that serial communication parameters become improperly assigned,recycle power to the RFID controller while holding the Configuration Tag in thecontroller’s RF field. When power returns to the controller, factory default settings willbe read from the Configuration Tag and the controller’s internal configuration will bereset. For the C0405-485, this Configuration Tag can also be used manually to setthe device’s Node ID. It is recommended to write the product serial number on thetag and store it in a safe place.
                                     CHAPTER  3: POWER & COMMUNICATIONP/N:  17-1328  REV  02  (08/07)           PAGE  33  OF 833.2.2 Configuration  Tag  Memory  MapContaining a Philips I-CODE SLi IC, the Configuration Tag is a 112-byte ISO 15693compliant tag that has had much of its memory locked at the factory to preventimportant data from being erased or overwritten. Of the 112 bytes of memory, the first80 bytes (addresses 0x0000 – 0x0079) are allocated to storing factory defaultsettings, product ID and manufacturing information. The first 16-bytes (addresses0x0000 through 0x0015) contain specific data that the controller reads to identify thisspecial tag.You are welcome to experiment with the remaining 32 bytes available on this tag(addresses 0x0080 – 0x0111). All addresses on the Configuration Tag can be readand no user identifiable information is stored.3.2.3 Using  the  Configuration  TagResetting  the  Controller  to  Default  SettingsThe Configuration Tag can be used to reset factory defaults to all versions of theC0405. To restore factory defaults, cycle power to the controller or issue the resetcommand (Command 0x35) while the Configuration Tag is in the RF field. Twoseconds after power returns to the C0405, remove the Configuration Tag from the RFfield. The controller will be reset to the following default settings:CONFIGURATION  PARAMETER DEFAULT  SETTINGCommand Protocol ABx Fast – No ChecksumTag Type: ISO 15693 (I-Code SLi)Serial Communications 9600, N, 8, 1, N (C0405-232 model)Node ID 00 (C0405-485 model)Table 3-2: Configuration Tag - Controller DefaultsSetting  Node  ID  Manually  (C0405-485  only)To set the Node ID on C0405-485 models, cycle power to the controller or issue thereset command (Command 0x35) while the Configuration Tag is in the RF field. Twoseconds after power returns to the C0405, remove the Configuration Tag from the RFfield. This will set the Node ID value back to the default value of Node ID 00. (Note:see Section 4.1 - LED Functions Overview for LED positions and colors).•  All amber Node LEDs should be off.After power returns to the unit, move the Configuration Tag out of the RF field andthen back into the RF field to increment the Node ID from zero to one.•  Amber Node LED 20 should now be lit.Removing the Configuration Tag from the controller’s RF field and then bringing itback into the field will increment the Node ID value once each time the ConfigurationTag re-enters the RF field.•  The amber Node LEDs will display, in binary, the Node ID vale assigned tothe controller (See Chapter 4 for more information on LED status).
                                     CHAPTER  3: POWER & COMMUNICATIONP/N:  17-1328  REV  02  (08/07)           PAGE  34  OF 83This procedure can be used to cycle through all 16 possible Subnet Nodes. Note thatafter reaching Subnet Node 16, incrementing the Node ID value once more returnsthe controller to Node ID 0.After selecting the desired Node ID value, reset the C0405 with the Configuration Tagout of RF range to allow the unit to reset completely and resume operation under itsnew Node ID.Setting  Node  ID  Automatically  (C0405-485  only)To allow a Subnet16 Gateway or Hub to assign the Subnet Node ID to a C0405-485automatically, reset the controller to Node ID 00, connect the controller to the network,and apply power to the Subnet16 bus. When the Gateway or Hub comes on line,hold the Configuration Tag in the RF field of the controller for several seconds toallow the Gateway or Hub to assign the next available Node ID value. For moreinformation on using a Subnet16 Gateway and Hub product to auto-assign SubnetNode ID values, please refer to the Operator’s Manuals for theSubnet16 Gatewayand/or subnet16 Hub.
                                                         CHAPTER 4: LED STATUSP/N:  17-1328  REV  02  (08/07)           PAGE  35  OF 83CHAPTER  4:LED  STATUS4.1 LED FUNCTIONS OVERVIEWC0405-Series RFID Controllers have eight LED status indicators. The LEDs areconveniently located on the top panel of the device and display everything fromantenna RF and communications activity to Node ID, diagnostic information andpower status.LEDColor Red Green Amber Amber Amber Amber Amber GreenFunction RFActivityCOMActivityNode24(16)Node23(8)Node22(4)Node21 (2)Node20 (1)PowerOn
                                                         CHAPTER 4: LED STATUSP/N:  17-1328  REV  02  (08/07)           PAGE  36  OF 834.1.1 LED  DescriptionsRF LED: Color is red. The RF LED will illuminate while RF power is beingtransmitted by the antenna, and will stay ON during the entire RF operation. Bydefault, this occurs each time an RF command is being executed.COM LED: Color is green. The COM LED indicates that data is being transmittedbetween the host and the C0405. On receipt of a command, the COM LED willbegin flashing ON and OFF rapidly. After the controller generates the commandresponse, COM LED flashing will halt. When in Continuous Read mode, the COMLED will remain ON and will turn OFF briefly only while data is being read or writtento a tag.  Node LEDs: Colors are amber. These five LEDs indicate the serialcommunications type for C0405-232 and -USB models. For the C0405-485model, the five amber LEDs indicate (in binary from right to left) the current NodeID value assigned to the controller. The five amber LEDs also flash an error codewhen a fault occurs (see Section 4.3  LED Displayed Error Codes).Power LED: Color is green. The Power LED will remain ON while power isapplied to the C0405-Series Controller.
                                                         CHAPTER 4: LED STATUSP/N:  17-1328  REV  02  (08/07)           PAGE  37  OF 834.1.2 C0405-232  LED  StatusOn the C0405-232 model, the amber Node 20 LED will stay on indefinitely to indicatethat the controller is in RS232 mode.4.1.3 C0405-USB  LED  StatusOn the C0405-USB model, the amber Node 22 LED will stay on indefinitely to indicatethat the controller is in USB mode.23 21PWR24 22 20COMRFRF FIELDLED 2023 21PWR24 22 20COMR FRF FIELDLED 22
                                                         CHAPTER 4: LED STATUSP/N:  17-1328  REV  02  (08/07)           PAGE  38  OF 83Node 0(default) Node 1 Node 2Node 3 Node 4 Node 5Node 6 Node 7 Node 84.1.4 C0405-485  LED  StatusWhen used in conjunction with a Subnet16 Gateway or Subnet16 Hub, the fiveamber LEDs on the C0405-485 model indicate (in binary, weighted by powers of two,from right to left) the Node ID value currently assigned (for which there are 16).For example, 20 (0x01) = Node ID 1, 21 (0x02) = Node ID 2, 22 (0x04) = Node ID 4, 23(0x08) = Node ID 8, 24(0x10) = Node ID 16.By default, C0405-485 RFID Controllers ship with their Node ID value set to zero(none of the five amber Node LEDs will be lit). After the controller is connected to aSubnet16 bus and has been recognized by a Subnet16 Gateway or Hub, it will beautomatically assigned the next available Node ID (1 through 16). For configuring orresetting the Node ID using the Configuration Tag, see Chapter 3  Section 3.2: HF-Series Configuration Tag.Node  ID  Values  for  the  C0405-485PWR2423212220COMRFPWR2423212220COMRFPWR2423212220COMRFPWR2423212220COMRFPWR2423212220COMRFPWR2423212220COMRFPWR2423212220COMRFPWR2423212220COMRFPWR2423212220COMRF
                                                         CHAPTER 4: LED STATUSP/N:  17-1328  REV  02  (08/07)           PAGE  39  OF 83Node 9 Node 10 Node 11Node 12 Node 13 Node 14Node 15 Node 16PWR2423212220COMRFPWR2423212220COMRFPWR2423212220COMRFPWR2423212220COMRFPWR2423212220COMRFPWR2423212220COMRFPWR2423212220COMRFPWR2423212220COMRFNode ID 00 is the default NodeID for C0405-485 controllers.In this state, the controller willbe unable to performcommands until it has beeninitialized by a Gateway orHub, at which time it will beassigned a Node ID between 1and 16.
                                                         CHAPTER 4: LED STATUSP/N:  17-1328  REV  02  (08/07)           PAGE  40  OF 834.2 SPECIAL LED OPERATION FUNCTIONS4.2.1 Updating  the  Controllers  FirmwareUpdating Firmware(Part 1)With the PWR LED on theright, the remaining LEDs willilluminate one at a timesequentially from right to left toindicate that new firmwarecode is being copied tointernal memory.The LEDs will repeat this R toL sequence until the C0405has completely received thefirmware installation file.
                                                         CHAPTER 4: LED STATUSP/N:  17-1328  REV  02  (08/07)           PAGE  41  OF 834.2.2 Continuous  Read  Mode    LED  BehaviorThe table below describes the behavior of the LEDs when the unit is in ContinuousRead Mode (Command 0x0D).LED BEHAVIOR DESCRIPTIONPWR ON Controller is powered and functioningCOM ON Duplicate Read Delay  1 and a tag has entered the RF field.COM LED will remain ON while a tag is in the RF field.After the tag has exited the RF field the COM light will remainON for the duration of the Duplicate Read Delay before turningOFFCOM BLINKING  Duplicate Read Delay = 0 and a tag is in the RF fieldRF ON Continuous Read mode is enabledTable 4-1: Continuous Read Mode - LED BehaviorUpdating Firmware(Part 2)After the new firmware hasbeen copied to internalmemory, the LEDs will blinkON and OFF repeatedly duringwhich time the new code isbeing written to flash memory.Warning: do not cancel orabort this operation, AND donot unplug or remove powerfrom the controller under anycircumstance until thisprocedure is completed.
                                                         CHAPTER 4: LED STATUSP/N:  17-1328  REV  02  (08/07)           PAGE  42  OF 834.3 LED DISPLAYED ERROR CODESWhen an error occurs, other than a Timeout, the red RF LED and one or more amberNode LEDs will flash in unison. The amber Node LEDs flash a binary representationof the one-byte error code value of the fault that transpired. The COM LED will alsobe illuminated after an error occurs to help orient the binary LED positions. SeeChapter 8: ABx Error Codes for a complete list of errors and their descriptions.To display the single-byte error code in binary, the two left-most amber Node LEDs(LED 24and LED 23) represent the first or most significant digit (MSD) of the errorcode. The three remaining amber Node LEDs (LED 22, LED 21and LED 20) arecombined to represent the second or least significant digit (LSD) of the error code.Examples:•If the five amber Node LEDs (from L to R) =ON, OFF, OFF, OFF, ON, the first digit of theerror code is a “2 “ and the second digit is a“1,” meaning that error code 0x21 occurred(error code 0x21 = command syntax error).•If the five amber Node LEDs (from L to R) =ON, ON, OFF, ON, OFF, the first digit of theerror code is a “3 “ and the second digit is a“2,” meaning that error code 0x32 occurred(error code 0x32 = invalid programmingaddress).After an error has occurred, the red RF LED and one or more amber Node LEDs willcontinue to flash the error code until a valid command is received by the controller. Ifan unrecoverable error occurs, the LEDs will continuously flash the error code untilthe C0405 has been reset.PWR2423212220COMRFPWR2423212220COMRFPWR2423212220COMRFThis example depicts Error 0x21.When an error occurs, the greenCOM LED will remain ON to helporient the binary LED positions. Thegreen power LED will also be ONwhile power is applied to the C0405.
                                                            CHAPTER 5: RFID TAGSP/N:  17-1328  REV  02  (08/07)           PAGE  43  OF 83CHAPTER  5:RFID  TAGS5.1 RFID TAG OVERVIEWRFID tags, which are also referred to as transponders, smart labels, or inlays, comein a variety of sizes, memory capacities, read ranges, frequencies, temperaturesurvivability ranges and physical embodiments.C0405-Series Controllers are capable of reading Escort Memory Systems’ HMS, LRPand T-Series RFID tags as well as most tags made by other manufacturers.5.1.1 RFID  StandardsISO  14443ARFID integrated circuits (ICs) designed to meet ISO 14443A standards wereoriginally intended for use in smart cards used in secure transactions such as creditcards, passports, bus passes, ski lift tickets, etc. For this reason there are manysecurity authentication measures taken within the air protocol between the RFIDcontroller and the tag. Escort Memory Systems was the first company to adopt ISO14443A RFID ICs with this technology for industrial automation applications. Becausethese applications do not require the level of security monetary or passportapplications require, many of these features have not been implemented in currentcontrollers. It is important to understand the requirements of an ISO 14443Aapplication before assuming a C0405-Series controller is suitable.ISO 14443A compliant tags and controllers incorporate security authentication anduse software “keys” during each transfer of data to and from the tag. Both the RFIDcontroller and the tag must use the same security keys to authenticatecommunication. The C0405 Controller’s operating system manages these securityfeatures, making their existence transparent to the user. However, it is important tounderstand the implications associated with ISO 14443 when using anothermanufacturer’s tags. Because of these security “features,” an ISO 14443 tag madeby one manufacturer may not be readable by a C0405 Controller and an EscortMemory Systems ISO 14443 compliant tag might not be readable by anothermanufacturer’s RFID controller. C0405-Series Controllers support EMS’ security keysfor use on Mifare ISO 14443A tags.ISO  15693ISO 15693 was established at a time when the RFID industry identified that the lackof standards was preventing the market from growing. Philips Semiconductor andTexas Instruments were the major manufacturers producing RFID ICs for theIndustrial, Scientific, and Medical (ISM) frequency of 13.56MHz, but each used aunique protocol and modulation algorithm. Texas Instruments Tag-it™ and PhilipsSemiconductor’s I-CODE™ product lines were eventually standardized on themutually compatible ISO 15693 standard. After the decision was made to standardize,the door opened for other silicon manufacturers to enter the RFID business, many ofwhich have since contributed to RFID ISO definitions. This healthy competition hasled to rapid growth in the industry and has pushed the development of otherstandards, such as ISO 18000 for Electronic Product Code (EPC) applications.
                                                            CHAPTER 5: RFID TAGSP/N:  17-1328  REV  02  (08/07)           PAGE  44  OF 83ISO  18000-3.1The ISO 18000 standard has not been implemented in the C0405-Series Controllerat the time of publication of this manual. It is a planned product enhancement forfuture release. This will provide support for EPC and Unique Identification (UID) tagapplications.It is important to know that not all 13.56MHz RFID tags are compatible with theC0405 and even tags that are compliant to the ISO 15693 or ISO 14443 standardsmay not be compatible with RFID controllers compliant to the same standards. This ispartially because these ISO standards leave many features open to the discretionand interpretation of the RFID equipment manufacturers to implement or define.When using any tag other than those supplied by Escort Memory Systems, youshould ensure compatibility of those tags with your RFID system provider.
                                                            CHAPTER 5: RFID TAGSP/N:  17-1328  REV  02  (08/07)           PAGE  45  OF 835.2 EMS RFID TAGSAs of this publication, tags that contain the following RFID integrated circuits arecompatible with C0405-Series Controllers.5.2.1 HMS-Series  Tags•  Philips Mifare Classic, 1k-byte* + 32-bit ID (ISO 14443A)*Mifare 1 kilobyte total IC memory. Of this memory, 736-bytes are available for user data.•  Philips Mifare Classic, 4k-byte** + 32-bit ID (ISO 14443A)**Mifare 4 kilobytes total IC memory. Of this memory, 3,440-bytes are available for user data.Figure 5-1: HMS125HT and HMS150HT tags
                                                            CHAPTER 5: RFID TAGSP/N:  17-1328  REV  02  (08/07)           PAGE  46  OF 835.2.2 LRP-Series  Tags§  Philips I-CODE 1, 48-byte + 64-bit ID§  Philips I-CODE SLi, 112-byte + 64-bit ID (ISO 15693)§  Texas Instruments Tag-it, 32-byte + 64-bit ID (ISO 15693)§  Infineon My-D Vicinity, 1k-byte + 64-bit ID (ISO 15693)Figure 5-2: LRP-Series TagsThe HMS-Series and LRP-Series RFID tags listed in the above section are passivedevices, meaning that they require no internal batteries. These tags are fully readableand writeable, except for the tag’s unique ID number, which is read only.There are no serviceable or repairable parts inside these tags, yet most are capableof providing over 100,000 write cycles and 10 years of data retention. In fact, testsresulting in over one million write cycles have been recorded by some tags.Numerous tag-related factors can adversely affect RF range and data transmissionbetween the controller and the tag, including the tag’s integrated circuit (IC), the tag’santenna coil design, the tag’s antenna conductor material, the tag’s antenna coilsubstrate, the tag IC incorporated, the antenna coil bonding process and theembodiment material that is used.Additionally, the mounting environment of the tag and reader/writer can hinderperformance due to other materials affecting the tuning of either antenna. EscortMemory Systems has performed extensive testing to produce tags that obtainoptimum performance with our RFID devices. In most cases, optimal range will beobtained when mounting the tag and antenna in locations free from the influence ofmetals and EMI emitting devices.
                                                            CHAPTER 5: RFID TAGSP/N:  17-1328  REV  02  (08/07)           PAGE  47  OF 835.3 TAG EMBODIMENTSRFID tags are designed, produced and distributed in a variety of sizes and packages.5.3.1 Printed  Circuit  Board  RFID  TagsRFID tags that incorporate PrintedCircuit Board technology are designedfor encasement inside totes, pallets, orproducts that can provide the protectionnormally associated with injection-molded enclosures.These tags are made primarily frometched copper PCB materials (FR-4, forexample) and are die-bonded by meansof high quality wire bonding. Thisprocedure ensures reliable electricalconnections that are superior to flip-chipassembly methods. The RFID tag’sintegrated circuit is then encapsulatedin epoxy to protect it and the electricalconnections.5.3.2 Molded  RFID  TagsMolded tags utilize PCB tags and are the most rugged and reliable of the tags offeredby Escort Memory Systems. These tags are designed for closed-loop applicationswhere the tag is reused; thereby the cost of the tag can be amortized over the life ofthe production line. Typically, moldedtags will be mounted to a pallet orcarrier that transports (andaccompanies) the product through theentire production process. Otherapplications for these tags include (butare not limited to) embedding tagswithin concrete floors for locationidentification, shelf identification forstorage and retrieval systems, and toolidentification.Escort Memory Systems offers a widevariety of molded tags that have beendeveloped over the years for real worldapplications. High temperature tagsusing patented processes andspecialized materials allow tags tosurvive elevated temperatures, such asthose required for automotive paint andplating applications.
                                                            CHAPTER 5: RFID TAGSP/N:  17-1328  REV  02  (08/07)           PAGE  48  OF 835.4 TAG MEMORYTag memory addressing begins at address zero (0x0000), with the highestaddressable memory location equal to one less than the total number of bytes in thetag. Each address is equal to one byte (8-bits), where the byte is the smallestaddressable unit of data. So for example, writing 8-bytes to a tag beginning ataddress 0 will fill addresses 0 to 7 with 64-bits of data in all.Depending on the manufacturer, RFID labels, molded tags and embedded PCBs canhave differing memory storage capacities and organization. Tag memory is groupedinto blocks of bytes that can vary in organization from manufacturer to manufacturer.Even when compliant to ISO standards, byte memory addressing can differ from onemanufacturer to another (for example, tag memory can be organized in blocks of 4 or8 bytes, depending on the RFID IC). Additionally, a certain number of bytes may beallocated for storage of security data. For more information regarding a specific RFIDtag’s memory allocation, please refer to the IC manufacturer’s published datasheets.Escort Memory Systems has taken great care to simplify tag memory addressing.The mapping from logical address to physical address is handled by the C0405-Series Controller’s operating system. Users only need to identify the starting addresslocation on the tag and the number of bytes to be read or written. However, extraattention needs to be paid to the memory block structure when memory lockcommands are used. When data is locked, it cannot be altered. Caution should beexercised when using memory lock commands as locked data cannot be unlocked,even by Escort Memory Systems.5.4.1 Mapping  Tag  MemoryIs it a Byte or a Bit?Customers need to take into account that there are some RFID tag manufacturersthat measure and specify their tag memory sizes by the total number of bits, as thismethod generates a much larger (8X) overall number designed to inflate theirspecifications. Escort Memory Systems, on the other hand, prefers to specify total tagmemory sizes in terms of bytes (rather than in bits), as this method more closelyreflects how data is stored and retrieved from a tag and is typically what ourcustomers really want to know.5.4.2 Creating  an  RFID  Tag  Memory  MapCreating a tag memory map is much like creating a spreadsheet that outlines theactual data you plan to capture as well as the specific tag memory locations in whichyou wish to store said data. Tag memory maps should be carefully planned, simpleand straightforward. It is advisable to utilize more storage space than is initiallyrequired, as inevitably a need will arise to hold more data.
                                                            CHAPTER 5: RFID TAGSP/N:  17-1328  REV  02  (08/07)           PAGE  49  OF 83TA G  MEMORY  MA P  -  EXAMPLEIn the example below, 90-bytes of a 112-byte tag have been allocated to areas of thememory map (leaving roughly 20% free for future uses). Because a short paragraphof alphanumeric characters could quickly use all 90 bytes, creating an efficientmapping scheme, which utilizes all 720-bits out of the 90-bytes allocated, will providea better use of tag space.TAG ADDRESS DESCRIPTION OF USAGE00 - 15 Serial Number16 - 47 Model Number48 - 63 Manufacturing Date64 - 71 Lot Number72 - 89 Factory ID90 - 111 ReservedTable 5-1: Tag Memory Map Example5.4.3 Optimizing  Tag  MemoryIt should first be understood that data is always stored in tag memory in a binary form(1’s and 0’s). Binary numbers are notated using the hexadecimal numbering system(otherwise it would be too confusing looking at a screen full of 1’s and 0’s).Below is an example of how hexadecimal notation simplifies the expressing of bytevalues for the decimal number 52,882.DECIMAL BINARY HEXADECIMAL52,882 1100111010010010 CE92In the above example, instead of using 5-bytes of data to store the ASCII bytesrepresenting characters 5, 2, 8, 8, and 2 (ASCII bytes: 0x35, 0x32, 0x38, 0x38, 0x32)by simply writing two Hex bytes (0xCE and 0x92), 60% less tag memory is used tostore the same information.When an alphabetical character is to be written to a tag, the ASCII value of the givencharacter is written to the tag. For example, to write a capital “D” (ASCII value 0x44),the binary equivalent of the ASCII character 0x44 is written to the tag.Additionally, if a database with look up values is used in the RFID application, thelogic level of the individual bits in the tag can be used to maximize tag memory.(Note: refer to Appendix D in this document for a complete chart of ASCII charactersand their corresponding Hex values).
                                                            CHAPTER 5: RFID TAGSP/N:  17-1328  REV  02  (08/07)           PAGE  50  OF 83OPTIMIZING  TAG  MEMORY  -  EXAMPLEThe graphic below illustrates how a single byte(8-bits) can be efficiently used to track anautomobile’s inspection history at eightinspection stations.The number one (1) represents a requiredoperation and the number zero (0) representsan operation that is not required for thatparticular vehicle.Figure 5-3: Optimizing Tag Memory
                                          CHAPTER 6: COMMAND PROTOCOLSP/N:  17-1328  REV  02  (08/07)           PAGE  51  OF 83CHAPTER  6:COMMAND  PROTOCOLS6.1 ABXCOMMAND PROTOCOL OVERVIEWWhen an RFID command is issued, the host computer instructs the RFID controller toperform a given task. After performing that task, the RFID controller will normallyreply back with a Command Response message indicating the status or results of theattempted command. This response notifies the host as to whether the commandwas successfully completed or if the RFID controller failed to complete the command.To understand and execute RFID commands, the C0405 and the host must be ableto communicate using the same language. The language that is used tocommunicate RFID commands is referred to as the Command Protocol. The type ofCommand Protocol that is used is known as the ABx Command Protocol, of whichthere are three primary variations. The three versions of the ABx Command Protocolthat are supported by the C0405-Series RFID Controller are:•ABx Fast (default)•ABx ASCII•ABx StandardThe ABx Fast Command Protocol has a single-byte based packet structure thatpermits the execution of RFID commands while requiring the transfer of fewer totalbytes than ABx ASCII and ABx Standard. ABx Fast is the default command protocolused by C0405 RFID Controllers. It can be used with or without a checksum byte.The ABx ASCII Command Protocol also has a single-byte based packet structurethat supports the execution of RFID commands using the seven-bit ASCII characterset. By preventing data from interrupting communications when an ASCII controlcharacter is received, ABx ASCII can be useful in applications where flow control isrequired. This protocol can also be used with or without a checksum.The ABx Standard Command Protocol uses a double-byte, word based format thatshares a common syntax with most existing RFID systems produced by EscortMemory Systems. This protocol offers legacy support, which may be required byexisting PLC applications that only support a 2-byte word packet format. If yourapplication requires compatibility with existing or legacy RFID devices from EscortMemory Systems’, use ABx Standard. ABx Standard does not support the use of achecksum byte.NOTE:By default, the C0405 is configured to use the ABx Fast Command Protocol. ABx Fast(as the name suggests) is the faster and more efficient of the three ABx protocols,offering increased communication speed and error immunity.
                                          CHAPTER 6: COMMAND PROTOCOLSP/N:  17-1328  REV  02  (08/07)           PAGE  52  OF 836.1.1 ABx  Command  StructuresAll ABx-based RFID commands contain certain fundamental packet elements,including a Command Header, a Command ID, one or more CommandParameters (when applicable) and a Command Terminator.Command Packet Structure = [Command Header + Command ID + Command Parameters+ Command Terminator]6.1.2 ABx  Protocols  -  Headers  and  TerminatorsIn ABx Standard, commands begin with the one-byte command header "0xAA," andend with the two-byte command terminator "0xFF, 0xFF".In ABx Fast and ABx ASCII, commands begin with the two-byte command header“0x02, 0x02” and end with the one-byte command terminator “0x03.”See the table below for further clarification.ABx  Protocols  -  Headers  and  TerminatorsABX  PROTOCOL HEADER TERMINATORABx Fast 0x02, 0x02 0x03ABx ASCII 0x02, 0x02 0x03ABx Standard 0xAA 0xFF, 0xFFTable 6-1: ABx Protocols - Headers and TerminatorsWhen a command is issued by the host, the RFID controller stores the incoming datapacket in a buffer while it scans the data for a start character (0x02, 0x02 or 0xAA).When a start character is found, it checks for the proper terminator (0x03 or 0xFF,0xFF). Having identified a potentially valid command string, the controller will verifythe format of the data and either perform the requested function or generate an errormessage.6.1.3 ABx  Response  StructuresAfter completing an ABx command, the C0405 generates a host-bound, responsepacket that indicates the status and/or results of the attempted command. Theresponse packet structure for all ABx protocols consists of a Response Header, aCommand Echo, one or more Response Values (when applicable), and aResponse Terminator.Response Packet Structure = [Response Header + Command Echo + Response Values +Response Terminator]Note that for each ABx protocol, response header and response terminatorparameters are the same as their command header and command terminatorcounterparts.
                                          CHAPTER 6: COMMAND PROTOCOLSP/N:  17-1328  REV  02  (08/07)           PAGE  53  OF 836.2 ABXFAST COMMAND PROTOCOLThe default command protocol used by C0405-Series RFID Controllers for Point-to-Point data transmission is known as the ABx Fast Command Protocol. ABx Fasthas a single-byte oriented packet structure that permits the rapid execution of RFIDcommands while requiring the transfer of a minimal number of bytes.ABx Fast supports the inclusion of an optional checksum byte. When increased dataintegrity is required, the checksum should be utilized. See Section 6.2.4 for more onusing the checksum parameter.6.2.1 ABx  Fast  -  Command  /  Response  ProcedureAfter an RFID command is issued by the host, a packet of data, called the“Command Packet” is sent to the controller. The command packet containsinformation that instructs the controller to perform a certain task.The controller automatically parses the incoming data packet, searching for a specificpair of start characters, known as the “Command Header.” In ABx Fast, theCommand Header / Start Characters are 0x02, 0x02. When a valid CommandHeader is recognized, the controller then checks for proper formatting and for thepresence of a Command Terminator byte. In ABx Fast, the Command Terminatorbyte is 0x03.Having identified a valid command, the controller will attempt to execute the giveninstructions. After which the controller will generate a host-bound response messagecontaining EITHER the results of the attempted command or an error code if theoperation failed.Note that all commands generate a response from the controller. Before sending asecond or additional command to a C0405, allow the host to first process (removefrom memory) any pending response data.Figure 6-1: ABx Fast - Command Packet Structure
                                          CHAPTER 6: COMMAND PROTOCOLSP/N:  17-1328  REV  02  (08/07)           PAGE  54  OF 836.2.2 ABx  Fast  -  Command  Packet  StructureThe packet structure of all ABx Fast command contains certain basic elements,including Command Header, Command Size, Command ID and CommandTerminator. Additional options are available depending on the command beingperformed.COMMAND  PACKET  ELEMENT CONTENT SIZECOMMAND HEADER:The first two bytes of an ABx Fast command packet0x02, 0x02  2 bytesCOMMAND SIZE:This 2-byte integer defines the number of bytes in the packet(excluding header, command size, checksum andterminator).0x0007 +(number ofbytes ofadditionaldata)2-byteintegerCOMMAND ID:This single-byte value indicates the RFID command toexecute.0x06(Write Data)1 byteSTART ADDRESS:This two-byte parameter indicates the location of tag memorywhere a read or write operation shall begin.0x0000 2-byteintegerREAD/WRITE LENGTH:This two-byte parameter represents the number of bytes thatare to be retrieved from or written to the RFID tag.0x0001 2-byteintegerTIMEOUT VALUE:This two-byte parameter indicates the maximum length oftime for which the controller will attempt to complete thecommand. Measured in milliseconds, this value can have arange of 0x0001 to 0xFFFE or between 1 and 65,534 msecs.0x07D0(0x07D0 =2000 x .001 =2 seconds)2-byteintegerADDITIONAL DATA:This parameter uses one byte to hold a single character forfill operations and supports the use of multiple bytes whenseveral characters are needed for write commands (whenapplicable).0x00 One ormore bytes(whenapplicable)CHECKSUM:This optional parameter holds a single-byte checksum (onlyapplicable when using ABx Fast with Checksum).Optional  1 byte(whenapplicable)COMMAND TERMINATOR:Single-byte command packet terminator (always 0x03)0x03 1 byteTable 6-2: ABx Fast - Command Packet Structure
                                          CHAPTER 6: COMMAND PROTOCOLSP/N:  17-1328  REV  02  (08/07)           PAGE  55  OF 836.2.3 ABx  Fast  -  Response  Packet  StructureAfter performing a command, the C0405, in most cases, will generate a host-boundresponse packet. ABx Fast responses contain a Response Header, Response Size,Command Echo, one or more Response Values (when applicable), and aResponse Terminator.RESPONSE  PACKET  ELEMENT CONTENT SIZERESPONSE HEADER:First two bytes of an ABx Fast response packet0x02, 0x02  2 bytesRESPONSE SIZE:This two-byte integer defines the total number of bytesin the response packet (excluding header, size,checksum and terminator).0x0001 2-byte integerCOMMAND ECHO:The single-byte parameter identifies the command forwhich the response packet was generated.0x06 1 byteRETRIEVED DATA:This parameter is used to hold one or more bytes ofdata that was requested by the command (whenapplicable).Data 1 or more bytes(whenapplicable)CHECKSUM:This optional parameter holds a single-byte checksum(only applicable when using ABx Fast withChecksum).Optional 1 byte(whenapplicable)RESPONSE TERMINATOR:Single-byte response packet terminator (always 0x03)0x03 1 byteTable 6-3: ABx Fast - Response Packet Structure
                                          CHAPTER 6: COMMAND PROTOCOLSP/N:  17-1328  REV  02  (08/07)           PAGE  56  OF 836.2.4 ABx  Fast  -  Command  Packet  ParametersCommand  SizeThe ABx Fast protocol requires that the byte count, known as the Command Size,be specified as a two-byte integer. To calculate the command size, add the totalnumber of bytes within the command packet while excluding the header, commandsize, checksum (if present) and terminator (see example below).COMMAND  ELEMENT #  OF  BYTES INCLUDED  INCOMMAND  SIZE?Command Header 2NoCommand Size 2NoCommand ID 1YesStart Address 2YesRead/Write Length 2YesTimeout Value 2YesAdditional Data Bytes 1YesChecksum 1NoCommand Terminator  1 NoThe command size for this example is 0x0008.Start  AddressThe Start Address parameter holds a two-byte integer representing the tag memoryaddress location where a read or write operation will begin.Read/Write  LengthThe two-byte Read/Write Length integer indicates the number of bytes that are to beread from or written to the RFID tag.Timeout  ValueA two-byte Timeout Value parameter (measured in one-millisecond increments) isused to set the length of time that the controller will attempt to complete the specifiedoperation.The maximum supported timeout value is 0xFFFE or 65,534ms (slightly longer thanone minute). Setting a long timeout length does not necessarily mean that acommand will take any longer to execute. This value only represents the period oftime for which the controller will attempt to complete the command.IMPORTANT:During write commands, the tag must remain within the antenna’s RF field until thewrite operation completes successfully, or until the timeout value has expired. If a writeoperation is not completed before the tag leaves the controller’s RF field, data may beincompletely written.CommandSize =number ofbytes in thesefields
                                          CHAPTER 6: COMMAND PROTOCOLSP/N:  17-1328  REV  02  (08/07)           PAGE  57  OF 83ChecksumABx Fast and ABx ASCII Command Protocols support the inclusion of an additionalchecksum byte that is used to verify the integrity of data being transmitted betweenhost and controller.The checksum is calculated by adding together (summing) the byte values in thecommand packet (less the header, checksum and terminator), and then subtractingthe total byte sum from 0xFF. Therefore, when the byte values of each packetelement (from command size to checksum) are added together, the byte value sumwill equal 0xFF.CHECKSUM EXAMPLEThe following example depicts Command 0x05 (Read Data) using a checksum.COMMANDELEMENT CONTENTS USED  IN  CHECKSUMCommand Header  0x02, 0x02  n/aCommand Size 0x0007 0x00, 0x07Command ID 0x05 0x05Start Address 0x0001 0x00, 0x01Read Length 0x0004 0x00, 0x04Timeout Value 0x07D0 0x07, 0xD0Checksum 0x17 n/aCommand Terminator  0x03 n/aAdd the byte values from the command size, command ID, start address, read lengthand timeout value parameters together and subtract from 0xFF. Resulting value willbe the checksum.[0x07  +  0x05  +  0x01  +  0x04  +  0x07  +  0xD0]  = 0xE8The checksum equation is: [0xFF – 0xE8] = 0x17Checksum =[0xFF – (sumof thesefields)]
                                          CHAPTER 6: COMMAND PROTOCOLSP/N:  17-1328  REV  02  (08/07)           PAGE  58  OF 836.3 ABXSTANDARD COMMAND PROTOCOLThe ABx Standard Command Protocol is a binary, double-byte, “word” orientedprotocol where data is transmitted in 2-byte increments: a Most Significant Byte(MSB) or “High Byte” and a Least Significant Byte (LSB) or “Low Byte”.For ABx Standard commands, the first data word sent to the controller contains thecommand header and command ID, followed by parameters such as start address,read/write length and timeout value.Note that at no time can the complete command packet string (including terminator)exceed 50 words or 100 bytes.Figure 6-2: ABx Standard - Command Packet Structure
                                          CHAPTER 6: COMMAND PROTOCOLSP/N:  17-1328  REV  02  (08/07)           PAGE  59  OF 836.3.1 ABx  Standard  -  Command  Packet  StructureCOMMAND  PACKET  ELEMENT CONTENT BYTECOUNTCOMMAND HEADER:0xAA is always the MSB of the first word of an ABxStandard command.0xAA 1COMMAND ID:The command ID is always the LSB of the first wordand indicates the RFID command to execute.0x06(Write Data)1START ADDRESS:This two-byte parameter indicates the location of tagmemory where a read or write operation shall begin.0x0000 2READ/WRITE LENGTH:This two-byte parameter represents the number ofbytes that are to be retrieved from or written to theRFID tag.0x0001 2TIMEOUT VALUE:This two-byte integer indicates the maximum length oftime for which the controller will attempt to completethe command. Measured in milliseconds, this valuecan have a range of 0x0001 to 0xFFFE or between 1and 65,534 msecs (0x07D0 = 2000 x .001 = 2seconds).0x07D0 2ADDITIONAL DATA:This parameter uses two bytes to hold a singlecharacter (data to be written to the tag is included inthe LSB only, MSB = 0x00).0x00, 0x00  2 (or more whenapplicable)TERMINATOR:Double-byte command packet terminator0xFF, 0xFF  2Table 6-4: ABx Standard - Command Packet Structure6.3.2 ABx  Standard  -  Response  Packet  StructureRESPONSE  PACKET  ELEMENT CONTENT BYTECOUNTRESPONSE HEADER:0xAA is always the MSB of the first word of an ABxStandard response packet0xAA 1COMMAND ECHO:The command echo is always the LSB of the first wordand indicates the RFID command that was executed.0x06(Write Data)2ADDITIONAL DATA:This parameter uses two bytes to hold a singlecharacter of retrieved data (data is returned in the LSBonly, MSB = 0x00).0x00, 0x00  2 (or more whenapplicable)TERMINATOR:Double-byte command packet terminator0xFF, 0xFF  2Table 6-5: ABx Standard - Response Packet Structure
                                          CHAPTER 6: COMMAND PROTOCOLSP/N:  17-1328  REV  02  (08/07)           PAGE  60  OF 836.3.3 ABx  Standard  -  Command  ExampleThe example below depicts the packet structure of the ABx Standard command andresponse messages for Command 0x08 (Tag Search). In this example, the RFIDcontroller is instructed to search for a tag in the RF field. A Timeout Value of twoseconds (0x07D0) is set for the completion of this operation.Command from HostCOMMAND  ELEMENT CONTENTHeader and Command ID (MSB/LSB) 0xAA, 0x08 (Tag Search)Timeout Value 0x07D0Terminator 0xFF, 0xFFResponse from ControllerRESPONSE  ELEMENT CONTENTHeader and Command ID (MSB/LSB) 0xAA, 0x08 (Tag Search)Timeout 0x07D0Terminator 0xFF, 0xFF
                       CHAPTER  7:  RFID  COMMANDS  AND  ERROR  CODESP/N:  17-1328  REV  02  (08/07)           PAGE  61  OF 83CHAPTER  7:RFID  COMMANDS  AND  ERROR  CODES7.1 ABXFAST RFID COMMAND TABLEThe table below lists the ABx Fast RFID commands supported by C0405-SeriesRFID Controllers.COMMAND  ID COMMAND  NAME DESCRIPTIONSingle-Tag  RFID  Commands0x04 Fill  Tag Fills a specified tag address range with aone-byte value0x05 Read  Data Reads a specified length of data from acontiguous (sequential) area of tag memory0x06 Write  Data Writes a specified number of bytes to acontiguous area of tag memory0x07 Read  Tag  ID Retrieves a tag’s unique identification (TagID) number0x08 Tag  Search Instructs the controller to search for a tag inits RF field0x0D StartContinuousRead Instructs the controller to start or stopContinuous Read mode.0x0E Read  Tag  ID  andData Reads a tag’s ID number as well as aspecified number of bytes of tag memory0x0F StartContinuousRead  Tag  ID  andDataInstructs the controller to start or stopContinuous Read Tag ID and Data mode.0x27 Lock  MemoryBlock Write protects a block of tag memoryRFID  Controller  Commands0x35 Reset  Controller Resets power to the controller0x36 Set  ControllerConfigurationUsed to set (configure or modify) thecontroller’s configuration parameters andsettings0x37 Get  ControllerConfiguration Retrieves the controller’s configurationsettings0x38 Get  ControllerInfo Retrieves hardware, firmware and serialnumber information from the controller
                       CHAPTER  7:  RFID  COMMANDS  AND  ERROR  CODESP/N:  17-1328  REV  02  (08/07)           PAGE  62  OF 83COMMAND  ID COMMAND  NAME DESCRIPTION0x51 Set  ControllerTime Used to set the time for the controller0x72 ExecuteController  Macro Instructs the controller to execute one of itseight macrosMulti-Tag  RFID  Commands0x82 Multi-Tag  ReadID  and  Data  All Retrieves a contiguous segment of data andthe tag ID from all RFID tags in range0x85 Multi-Tag  BlockRead  All Retrieves a contiguous segment of datafrom all RFID tags in range0x86 Multi-Tag  BlockWrite  All Writes a contiguous segment of data to allRFID tags in range0x87 Multi-Tag  GetInventory Retrieves the tag ID from all RFID tags inrange0x88 Multi-Tag  SearchAll Checks for the presence of any RFID tagsin range0x95 Multi-Tag  BlockRead  by  ID Reads a contiguous segment of data from aspecific RFID tag identified by its tag ID0x96 Multi-Tag  BlockWrite  by  ID Writes a contiguous segment of data to aspecific RFID tag identified by its tag IDTable 7-1: ABx Fast RFID Command Table
                       CHAPTER  7:  RFID  COMMANDS  AND  ERROR  CODESP/N:  17-1328  REV  02  (08/07)           PAGE  63  OF 837.2 ABXSTANDARD RFID COMMAND TABLEThe table below lists the ABx Standard RFID commands supported by C0405-SeriesRFID Controllers.COMMAND  ID COMMAND  NAME DESCRIPTIONRFID Tag Commands0x04 Fill  Tag Fills a specified tag address range witha one-byte value0x05 Read  Data Reads a specified number of bytes froma contiguous (sequential) length of tagmemory0x06 Write  Data Writes a specified number of bytes to acontiguous length of tag memory0x07 Read  Tag  ID Retrieves a tag’s unique identification(Tag ID) number0x08 Tag  Search Instructs the controller to search for atag in its RF field0x0D Start  ContinuousRead Instructs the controller to start and stopContinuous Read mode.0x0E Read  Tag  ID  andData Retrieves the tag ID and a specifiednumber of bytes from the tag0x0F Start  ContinuousRead  Tag  ID  andDataInstructs the controller to start and stopContinuous Read Tag ID and Datamode.RFID Controller Commands0x35 Reset  Controller Resets power to the controller0x36 Set  ControllerConfiguration Used to modify and update theconfiguration settings of the controller0x37 Get  ControllerConfiguration Retrieves configuration settings from thecontroller0x38 Get  Controller  Info Retrieves hardware, firmware and serialnumber information from the controllerTable 7-2: ABx Standard RFID Command Table
                       CHAPTER  7:  RFID  COMMANDS  AND  ERROR  CODESP/N:  17-1328  REV  02  (08/07)           PAGE  64  OF 837.3 ERROR CODESIf the C0405 encounters a fault during operation, it will generate a response thatincludes a one-byte ABx error code. Entering an invalid Start Address for a ReadData command, for example, will generate ABx Error Code 0x32 (InvalidProgramming Address).To display the single-byte error code in binary, the two left-most amber Node LEDs(LED 24and LED 23) represent the first or most significant digit (MSD) of the errorcode. The three remaining amber Node LEDs (LED 22, LED 21and LED 20) arecombined to represent the second or least significant digit (LSD) of the error code.Examples:•If the five amber Node LEDs (from L to R) =ON, OFF, OFF, OFF, ON, the first digit of theerror code is a “2 “ and the second digit is a“1,” meaning that error code 0x21 occurred(error code 0x21 = command syntax error).•If the five amber Node LEDs (from L to R) =ON, ON, OFF, ON, OFF, the first digit of theerror code is a “3 “ and the second digit is a“2,” meaning that error code 0x32 occurred(error code 0x32 = invalid programmingaddress).The RF LED and amber Node LEDs will continue to flash until a valid command isreceived by the controller. The green COM LED will remain ON to help orient thebinary LED positions. If an unrecoverable error occurs, the LEDs will continuouslyflash the error code until the C1007 has been reset.PWR2423212220COMRFPWR2423212220COMRF
                       CHAPTER  7:  RFID  COMMANDS  AND  ERROR  CODESP/N:  17-1328  REV  02  (08/07)           PAGE  65  OF 837.4 ABXERROR CODE TABLEERRORCODE DESCRIPTION0x04 Fill Operation not Completed0x05 Read Operation not Completed0x06 Write Operation not Completed0x07 Read Tag ID Operation not Completed (Tag not Found)0x21 Command Syntax Error0x23 Unsupported Tag Type / Unsupported RF Command0x27 Memory Lock Operation not Complete (memory may be locked)0x30 Internal Error, Buffer Overflow0x31 Invalid Controller Type0x32 Invalid Programming Address0x33 Invalid CRC Value0x34 Invalid Software Version0x35 Invalid Reset0x36 Set Configuration Operation not Completed0x37 Get Configuration Operation not CompletedTable 7-3: ABx Error Codes
                       CHAPTER  7:  RFID  COMMANDS  AND  ERROR  CODESP/N:  17-1328  REV  02  (08/07)           PAGE  66  OF 837.5 ABXFAST ERROR RESPONSE STRUCTUREABx Fast error responses contain a two-byte Header, a two-byte Response Sizeparameter followed by a single-byte Error Flag (0xFF) and a single-byte Error Codeparameter, which identifies the error that occurred.ERROR  RESPONSE  ELEMENT CONTENTHeader 0x02, 0x02Response Size 0x0002Error Flag 0xFFError Code Single-byte Error CodeChecksum OptionalTerminator 0x03Table 7-4: ABx Fast - Error Response StructureABXFAST ERROR RESPONSE EXAMPLEBelow is an example of an ABx Fast error response for a failed Write Data command(error code 0x06).  ERROR  RESPONSE  ELEMENT CONTENTHeader 0x02, 0x02Response Size 0x0002Error Flag 0xFFError Code 0x06Checksum OptionalTerminator 0x03
                       CHAPTER  7:  RFID  COMMANDS  AND  ERROR  CODESP/N:  17-1328  REV  02  (08/07)           PAGE  67  OF 837.6 ABXSTANDARD ERROR RESPONSE STRUCTUREIn ABx Standard, the error code will be returned in the LSB of the second word of theresponse.Below is the structure of an ABx Standard error response.ERROR  RESPONSE  ELEMENT CONTENT  (MSB/LSB)Error Response Header (MSB/LSB) 0xAA, 0xFFError Code (MSB/LSB) 0x00, (1-byte error code value)Terminator (MSB/LSB) 0xFF, 0xFFTable 7-5: ABx Standard - Error Response StructureABXSTANDARD ERROR RESPONSE EXAMPLEBelow is an example of an ABx Standard error response message for a failed WriteData operation (error code: 0x06).ERROR  RESPONSE  ELEMENT CONTENT  (MSB/LSB)Error Response Header (MSB/LSB) 0xAA, 0xFFError Code (MSB/LSB) 0x00, 0x06Terminator (MSB/LSB) 0xFF, 0xFF
                                 APPENDIX  A: TECHNICAL  SPECIFICATIONSP/N:  17-1328  REV  02  (08/07)           PAGE  68  OF 83APPENDIX  A:TECHNICAL  SPECIFICATIONSELECTRICALSupply Voltage 10~30VDCPower Consumption:C0405-232-01 and C0405-485-012.4W (100mA @ 24VDC)Power Consumption:C0405-USB-011W (200mA @ 5VDC from USB bus)COMMUNICATIONCommunication Interfaces Point-to-Point: RS232, USBMulti-drop, Subnet16, MUX32: RS485RFID Interface Cobalt C0405-Series RFID SystemRF Output Power 100mWAir Protocols ISO 15693, ISO 14443AAir Protocol Speed 26.5k Baud / 106k Baud with CRC error detectionRS232/RS485 Baud Rates 9600 (default), 19.2k, 38.4k, 57.6k, 115.2kMECHANICALDimensions 40mm x 56mm x 25mm (1.6in x 2.2in x 1in)Weight 47g (1.7 oz)Enclosure PolycarbonateENVIRONMENTALOperating Temperature -20° to 50°C (-4° to 122°F),Storage Temperature -40° to 85°C (-40° to 185°)Humidity 100%Protection Class IP67Shock Resistance IEC 68-2-27 Test EA 30g, 11ms, 3 shocks each axisVibration Resistance IEC 68-2-6 Test FC 1.5mm; 10 to 55Hz;2 hours each axisNOTE: Specifications are subject to change without notice.
                                 APPENDIX  A: TECHNICAL  SPECIFICATIONSP/N:  17-1328  REV  02  (08/07)           PAGE  69  OF 83C0405-SERIES RFID CONTROLLER DIMENSIONSFigure A0-1: C0405-Series RFID Controller Dimensions
                                     APPENDIX B: MODELS & ACCESSORIESP/N:  17-1328  REV  02  (08/07)           PAGE  70  OF 83APPENDIX  B:MODELS  &  ACCESSORIESEscort Memory Systems designs, manufactures and distributes a wide range of highfrequency (HF) RFID equipment, including RFID controllers, network interfacemodules (Gateways and Hubs), RFID tags and the cables needed to make it all work.This portion of the manual lists the products and accessories available for the C0405-Series RFID product family. To purchase any of the items listed below contact yourEMS distributor, call us directly at (800) 626-3993 or visit our Web site:http://www.ems-rfid.com. Please let us know if you have any questions.EMS HARDWAREC0405-Series  RFID  ControllersThere are three models of the C0405-Series RFID Controller:§C0405-232-01§C0405-485-01§C0405-USB-01Each C0405 unit ships with the following accessories:EMS  P/N QTY DESCRIPTION00-3000 1  Configuration Tag for C0405 I-CODE SLI,20-1940 2  Screws, (M4, 20 PPH SS 18-8\302)20-5918 2  Hex Nuts, (M4 SS 18-8\302)20-3910 2  Washers, Flat (M4, 12MM OD, 4.3MMID)14-3137 1  Mounting Bracket for the C0405, NORYL, Black GTX830Subnet16  Gateway  Interface  ModulesGWY-01-TCP-01Subnet16™ TCP/IP GatewayGWY-01-IND-01Subnet16™ Industrial Ethernet GatewaySubnet16  Hub  Interface  ModulesHUB-04-TCP-01Subnet16™ 4-Port TCP/IP HubHUB-04-IND-01Subnet16™ 4-Port Industrial Ethernet Hub
                                     APPENDIX B: MODELS & ACCESSORIESP/N:  17-1328  REV  02  (08/07)           PAGE  71  OF 83SOFTWARE & DEMONSTRATION KITSSoftware  ApplicationsVisit the Escort Memory Systems website (www.ems-rfid.com) for downloadinstructions.Cobalt HF Dashboard Utility (for TCP/IP or Serial Connections)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 BuilderAn easy to use GUI-driven utility that provides rapid development and implementationof custom RFID command macros.Demonstration  Kits00-1203Gateway TCP Demo Kit (includes one GWY-01-TCP-01 TCP Gateway interfacemodule, one C0405-485-01 controller, one C1007-485-01 controller, one HF-0405-485-01 controller, LRP125S, LRP250 and T7036 RFID tags, interface cables, displayboard and power supply).00-1217C0405-USB-01 Demo Kit (includes one C0405-USB-01 controller, one CBL-1525USB interface cable, one LRP108I tag, one LRP125VS tag and one T7036 tag).00-1218Conveyor Demo Kit (includes one GWY-01-IND-01 Industrial Gateway interfacemodule, one C0405-485-01 controller, one C1007-485-01 controller, one HF-CNTL-485-01 controller, one HF-ANT-1010-01 antenna, one LRP108S tag, three LRP250Stags, one LRP525S tag, two T5050 tags, three T7036 tags, interface cables andpower supply).00-1219Gateway C0405-485 Demo Kit (includes one GWY-01-TCP-01 TCP Gatewayinterface module, three C0405-485-01 controllers, one HMS150 tag, one LRP125Stag, interface cables, carrying case, display board and power supply).
                                     APPENDIX B: MODELS & ACCESSORIESP/N:  17-1328  REV  02  (08/07)           PAGE  72  OF 83CABLE  AND NETWORK ACCESSORIESEMS  P/NXX  =LENGTH  INMETERSCOMPONENT DESCRIPTIONCBL-1478 Cable Assembly  8-pin, female M12 to RS232; with 2.5mm DC powerjack, 2mCBL-1480-XX Cable 5-pin, male M12 to 5-pin, female M12 (ThinNet)CBL-1481-XX Cable 5-pin, male M12 to 5-pin, male M12 (ThinNet)CBL-1481-02 Cable 5-pin, male M12 to 5-pin, male M12, 2m (ThinNet,Gateway to Drop-T)CBL-1482-XX Cable 5-pin, male M12 to 5-pin, female, right-angle M12(ThinNet)CBL-1483-XX Cable 5-pin, male 7/8–16 to 5-pin, female 7/8-16 (ThickNet)CBL-1484-XX Cable 5-pin, male, right-angle 7/8-16 to bare wire leads(ThickNet)CBL-1485 Drop-T Connector  5-pin, female 7/8-16 / female M12 / male 7/8-16(ThickNet to ThinNet)CBL-1486 Drop-T Connector  5-pin, female M12 / 5-pin, female M12 / 5-pin, maleM12 (ThinNet to ThinNet)CBL-1487 Field MountableConnector 5-pos, straight female M12CBL-1488-XX Cable 8-pin, female M12 to bare wire leadsCBL-1489 TerminationResistor Plug 5-pin, male 7/8-16 (ThickNet)CBL-1490 TerminationResistor Plug 5-pin, male M12 (ThinNet)CBL-1491 Field MountableConnector 5-pos, right-angle female M12CBL-1492-XX Cable 8-pin, right-angle female M12 to bare wire leadsCBL-1493 Field MountableConnector 8-pos, straight female M12CBL-1494-01 Cable 5-pin, female M12 to bare wire leads, 1m (ThinNet)CBL-1495-XX Cable 5-pin, female 7/8-16 to bare wire leads
                                     APPENDIX B: MODELS & ACCESSORIESP/N:  17-1328  REV  02  (08/07)           PAGE  73  OF 83CBL-1496 TerminationResistor Plug 5-pin, female M12 (ThinNet)CBL-1497 TerminationResistor Plug 5-pin, female 7/8-16 (ThickNet)CBL-1498-02 Cable 5-pin, male M12 to bare wire leads, 2m (ThinNet)CBL-1514 Connector 5-pin, straight male, reverse-keyed M12 (for USB)CBL-1515-05 Cable CAT5E shielded Ethernet to 5-Pin, male, D-Code M12,5mCBL-1524 Connector 5-pin, straight female, reverse-keyed M12CBL-1525 Cable Assembly  5-pin, female, reverse-keyed M12 to USB Type A, 3mBulk RS232 Cable    Belden Cable P/N: 9941Bulk RS422 cable Belden Cable P/N: 3109APower  Supplies00-116645W, 24VDC, 1.88A max, Universal Input (90-264VAC, 47-63Hz), 5.5x2.5mm plug, positive tip;requires country specific power cord to mate toIEC 320 power cord receptacle.00-1167100W, 24VDC, 4.17A max, Universal Input (90-264VAC, 47-63Hz), 5.5x2.5mm plug, positive tip;requires country specific power cord to mate withIEC 320 power cord receptacle.00-1168120W, 24VDC, 5.0A max, Universal Input (88-132VAC/176-264VAC switchselectable, 47-63Hz) DIN Rail Mount; AC wire receptacles are spring clamped fordirect wire connection.Escort  Memory  Systems  RFID  TagsEscort Memory Systems designs and manufactures several lines of RFID tags. LRP,HMS and T-Series passive read/write RFID tags are specially suited for the C0405-Series product line.
                                            APPENDIX C: NETWORK DIAGRAMSP/N:  17-1328  REV  02  (08/07)           PAGE  74  OF 83APPENDIX  C:NETWORK  DIAGRAMS§  Subnet16 Gateway - ThickNet Network Diagram§  Subnet16 Gateway - ThinNet Network Diagram§  Subnet16 Hub – Network Diagram
                                            APPENDIX C: NETWORK DIAGRAMSP/N:  17-1328  REV  02  (08/07)           PAGE  75  OF 837.6.1 Subnet16  Gateway    ThickNet  Network  Diagram
                                            APPENDIX C: NETWORK DIAGRAMSP/N:  17-1328  REV  02  (08/07)           PAGE  76  OF 837.6.2 Subnet16  Gateway    ThinNet  Network  Diagram
                                            APPENDIX C: NETWORK DIAGRAMSP/N:  17-1328  REV  02  (08/07)           PAGE  77  OF 837.6.3 Subnet16  Hub    Network  Diagram
                                                       APPENDIX D: ASCII CHARTP/N:  17-1328  REV  02  (08/07)           PAGE  78  OF 83APPENDIX  D:ASCII  CHART
                                                       APPENDIX D: ASCII CHARTP/N:  17-1328  REV  02  (08/07)           PAGE  79  OF 83
                                             APPENDIX E: RFID TERMINOLOGYP/N:  17-1328  REV  02  (08/07)           PAGE  80  OF 83APPENDIX  E:RFID  TERMINOLOGYTERM DEFINITIONAntenna The antenna is the part of the RFID controller that radiates RFenergy to, and receives energy from an RFID tag.ASCII American Standard Code for Information Interchange. A computercode consisting of 128 alphanumeric and control characters, eachencoded with 7 bits, used for the exchange of informationbetween computing devices.ASCII Protocol A protocol used to send ASCII character commands to thecontroller. It is possible to use a standard terminal emulatorprogram to send ASCII commands.Baud The rate at which a data channel transfers bits of information.Baud is measured in Bits Per Second (bps).Binary A numbering system in which numbers are expressed ascombinations of digits 0 and 1, based on powers of 2. Incomputing these can be represented electrically as 'on' or 'off'.Byte Eight bits of data.CaptureField/Area/Zone The region of the electromagnetic field, generated by the antenna,in which transponders will operate. Also called the “RF Field” inthis manual.Checksum An addition to the contents of a block of data. Data can then bechecked before and after transmission to determine whether anydata has been corrupted or lost.Continuous Read A mode of operation, in which the controller is instructed torepeatedly attempt to read any tag within RF range.EPC Electronic Product CodeHandshaking A mechanism for the regulation of the flow of data betweendevices. For example, handshaking can be used to prevent acontroller from temporarily overwhelming the host with CommandResponse data.Hexadecimal (Hex)A method of numerically representing data based on the number16. Hex notation uses the numbers 0 to 9 and letters A to F(where the decimal number 10 is represented in hexadecimal as'A'). In this manual Hex values are preceded by 0x, as in “address0xFF” (it is also considered correct to append Hex values with alower case h, as in interrupt 20h”).Host The computer or PLC that issues commands to and receivesresponses from the RFID controller.
                                             APPENDIX E: RFID TERMINOLOGYP/N:  17-1328  REV  02  (08/07)           PAGE  81  OF 83TERM DEFINITIONInterface An electrical or physical standard for the interconnection ofdevices.ISM Industry, Science & MedicalLED Light Emitting DiodeLSB Least Significant Byte. Also referred to as the Low Byte or secondbyte in a 2-byte “word.”MSB Most Significant Byte. Also referred to as the High Byte or firstbyte in a 2-byte “word.”Multidrop Multiple devices at various locations connected in parallel (oracting similar to parallel devices). RS-485 supports MultidropRFID controller configurations.MUX MultiplexerNoise Unwanted ambient electrical signals found in the operatingenvironment of RFID equipment.Orientation The alignment of a transponder with respect to the RFIDcontroller’s antenna.Parity A technique used to detect data transmission errors by adding anextra bit to each character. This bit is set to 1 or 0 to make thetotal number of bits ODD or EVEN, depending on the type ofparity in use.Passive Tags An RFID transponder that does not contain an internal powersource (such as a battery). It is powered by electromagneticsignals generated from an RFID antenna.PCB Printed Circuit BoardPLC Programmable Logic Controller (synonymous with Host).Protocol A set of rules governing the flow of information in acommunications system.Range (RF) The distance between the antenna and a tag or transponder in anRFID system at which signals can be properly received.Read The action of obtaining information contained in a tag.Reader A device containing digital electronics that can extract informationfrom a transponder and pass that data on to a host computer.Read Only A type of RFID tag that has been locked with certain informationwritten into it (usually during manufacturing) and thereafter canonly be read.
                                             APPENDIX E: RFID TERMINOLOGYP/N:  17-1328  REV  02  (08/07)           PAGE  82  OF 83TERM DEFINITIONRead/Write A type of RFID tag that allows a controller to retrieve or modifyexisting data or write new data to its memory.Reader/Writer An RFID device that can act as both reader and writer to a tag.(Synonymous with RFID controller).Response The string of data sent from the RFID controller to the host after acommand has been issued.RF Radio FrequencyRFID Radio Frequency IdentificationRFID Tag See TransponderRS232 A common physical interface standard specified by the EIA for theinterconnection of devices. The standard allows for single deviceto be connected, point-to-point, at recommended distances up to15 meters.RS485 An enhanced version of RS422, which permits multiple devices tobe attached to a twisted pair wire bus at recommended distancesup to 400 meters.Rx ReceiveTag See TransponderTransponder An electronic TRANSmitter / resPONDER which is attached to anobject to be identified and, when appropriate RF signals arereceived, transmits information as radio signals to an RFIDcontroller (synonymous with tag).Tx TransmitWrite The transfer of data to a tag.Write Length The number of contiguous bytes of tag memory that will bewritten.
                                                                      EMS WARRANTYP/N:  17-1328  REV  02  (08/07)           PAGE  83  OF 83EMS  WARRANTYscort Memory Systems warrants that all products of its own manufacturing conform toEscort Memory Systems’ specifications and are free from defects in material andworkmanship when used under normal operating conditions and within the serviceconditions for which they were furnished. The obligation of Escort Memory Systems hereundershall expire one (1) year after delivery, unless otherwise specified, and is limited to repairing,or at its option, replacing without charge, any such product that in Escort Memory Systems’sole opinion proves to be defective within the scope of this Warranty. In the event EscortMemory Systems is not able to repair or replace defective products or components within areasonable time after receipt thereof, Buyers shall be credited for their value at the originalpurchase price. Escort Memory Systems must be notified in writing of the defect ornonconformity within the warranty period and the affected product returned to Escort MemorySystems factory or to an authorized service center within thirty (30) days after discovery ofsuch defect or nonconformity. Shipment shall not be made without prior authorization by EscortMemory 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 liableto Buyer, in contract or in tort, for any special, indirect, incidental, or consequential damages,expenses, losses or delay however caused. Equipment or parts that have been subjected toabuse, misuse, accident, alteration, neglect, unauthorized repair or installation are not coveredby warranty. Escort Memory Systems shall make the final determination as to the existenceand cause of any alleged defect. No liability is assumed for expendable items such as lampsand fuses. No warranty is made with respect to equipment or products produced to Buyer’sspecification except as specifically stated in writing by Escort Memory Systems in the contractfor such custom equipment. This warranty is the only warranty made by Escort MemorySystems with respect to the goods delivered hereunder, and may be modified or amended onlyby a written instrument signed by a duly authorized officer of Escort Memory Systems andaccepted by the Buyer.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.COPYRIGHT  ©  2007  ESCORT  MEMORY  SYSTEMS,  ALL  RIGHTS  RESERVEDE

Navigation menu