COBALT UHF-SERIES Cobalt UHF Series Operator’s Manual For Models: UHF-CNTL-232/485/IND –02 EU UHF-CNTL-232/485/IND –02 US Datalogic Automation reserves the right to make modifications and improvements to its products and/or documentation without prior notification. Datalogic Automation shall not be liable for technical or editorial errors or omissions contained herein, nor for incidental or consequential damages resulting from the use of this material.
COBALT UHF-SERIES COBALT UHF-SERIES RFID CONTROLLERS Ultra High Frequency, Multi Protocol, Passive Radio Frequency Identification Controllers For Cobalt UHF-Series RFID Controller Models: UHF-CNTL-232-02 UHF-CNTL-485-02 UHF-CNTL-IND-02 O PERATOR ’ S M ANUAL How to Install, Configure and Operate the Cobalt UHF-Series RFID Controllers PAGE 3 OF 140
COBALT UHF-SERIES REGULATORY COMPLIANCE R EGULATORY C OMPLIANCE FCC Compliance Modifications or changes to this equipment without the expressed written approval of Datalogic could void the authority to use the equipment. This device complies with PART 15 of the FCC Rules. Operation is subject to the following two conditions: (1) This device may not cause harmful interference, and (2) this device must accept any interference received, including interference which may cause undesired operation.
COBALT UHF-SERIES REGULATORY COMPLIANCE ESPAÑOL Contacta la autoridad competente para la gestión de los dispositivos de radio frecuencia de tu país, para verificar cualesquiera restricciones o licencias posibles requerida. Además se puede encontrar mas información en el sitio Web: http://europa.eu.int/comm/enterprise/rtte/spectr.htm. Power Supply This product is intended to be installed by Qualified Personnel only.
COBALT UHF-SERIES CONTENTS CONTENTS L IST OF T ABLES ................................................................................................10 L IST OF F IGURES ...............................................................................................11 CHAPTER 1: 1.1 GETTING STARTED ............................................... 12 I NTRODUCTION ..................................................................................12 1.1.1 1.2 About this Manual.............................
COBALT UHF-SERIES 3.3 CONTENTS C ONFIGURING T HE C OBALT VIA “C ONFIGURATION T AG ” .......................38 3.3.1 Restoring Factory Defaults .............................................................................. 38 3.3.2 Manually Assigning Node ID (Cobalt -485 Model Only) ..................................... 39 3.3.3 Automatic Node ID Assignment via Gateway (Cobalt -485 Model Only) ............ 40 3.3.4 Automatic Node ID Assignment via Hub (Cobalt -485 Model Only) ....................
COBALT UHF-SERIES CHAPTER 6: CONTENTS ETHERNET/IP INTERFACE ..................................... 89 6.1 E THERNET /IP C ONFIGURATION O VERVIEW ...........................................89 6.2 HTML S ERVER & O N D EMAND PLC S UPPORT ......................................90 6.3 HTML S ERVER AND O N D EMAND U TILITIES ..........................................90 6.4 IP C ONFIGURATION VIA HTML S ERVER ...............................................91 6.
COBALT UHF-SERIES CONTENTS C OBALT UHF A NTENNAS - T ECHNICAL S PECIFICATIONS .....................................135 APPENDIX B: MODELS & ACCESSORIES .................................. 136 C OBALT UHF S ERIES A CCESSORIES .................................................................136 C OBALT UHF-S ERIES RFID C ONTROLLERS .......................................................136 C OBALT UHF-S ERIES A NTENNAS .....................................................................
COBALT UHF-SERIES LIST OF TABLES L IST OF T ABLES Table 1-1: Connection and Communication Interface Options __________________________ 14 Table 1-2: Cobalt Controllers - Interface Connectors _________________________________ 14 Table 1-3: Package Contents ___________________________________________________ 14 Table 1-4: Cobalt UHF RFID Antennas - Models and Sizes ____________________________ 17 Table 1-5: Controller-Antenna Cabling Information ___________________________________ 21 TTable 2-1: COM Port Pa
COBALT UHF-SERIES LIST OF FIGURES L IST OF F IGURES Figure 1-1: Cobalt UHF Controller Dimensions – Top View ____________________________ 15 Figure 1-2: Cobalt UHF Controller Dimensions – Front View ___________________________ 16 Figure 1-3: Cobalt UHF Controller Dimensions – Right View ___________________________ 16 Figure 1-4: UHF-ANT-2626-01-86 Antenna Dimensions_______________________________ 18 Figure 1-5: UHF-ANT-3030-01-91 Antenna Dimensions_______________________________ 19 Figure 1-6: Connecting t
COBALT UHF-SERIES CHAPTER 1: GETTING STARTED CHAPTER 1: GETTING STARTED 1.1 I NTRODUCTION Welcome to the Cobalt UHF-Series RFID Controllers - Operator’s Manual. This manual will assist you in the installation, configuration and operation of the Cobalt UHF RFID controllers.
COBALT UHF-SERIES CHAPTER 1: GETTING STARTED 1.2 C OBALT C ONTROLLER O VERVIEW 1.2.
COBALT UHF-SERIES 1.2.3 CHAPTER 1: GETTING STARTED Connection and Communication Interface Options There are three different models of the Cobalt HF-Series RFID Controllers. Each model is designed to support a specific communication protocol and interface connection option. The table below lists the three controller models, their respective connection types and supported communication interfaces.
COBALT UHF-SERIES CHAPTER 1: GETTING STARTED 1.3 C OBALT C ONTROLLER D IMENSIONS 1.3.
COBALT UHF-SERIES CHAPTER 1: GETTING STARTED Figure 1-2: Cobalt UHF Controller Dimensions – Front View Figure 1-3: Cobalt UHF Controller Dimensions – Right View PAGE 16 OF 140
COBALT UHF-SERIES CHAPTER 1: GETTING STARTED 1.4 C OBALT UHF RFID A NTENNAS 1.4.1 Cobalt UHF RFID Antennas - Features Long read range (up to 3 meters with the UHF-G2-525HT tag and depending on installation conditions) Right-hand circular polarization ensures capturing tag data when tag is at random orientations 3dB Beamwidth, 63° or 65°, providing a large reading zone Housed in rugged IP67 rated enclosure Mounting kit for easy installation available 1.4.
COBALT UHF-SERIES 1.4.
COBALT UHF-SERIES 1.4.
COBALT UHF-SERIES 1.4.5 CHAPTER 1: GETTING STARTED Connecting the Antenna to the Controller The Cobalt UHF Antennas are connected to the top of the Cobalt UHF-Series RFID Controller’s housing through a single coaxial cable. Figure 1-6: Connecting the Antenna to the Controller The Cobalt UHF antenna has one female, N-type connector located on its rear side. The Cobalt UHF Controller has one TNC-Reverse female connector located on the top of the Controller’s housing.
COBALT UHF-SERIES CHAPTER 1: GETTING STARTED The RF port on the Cobalt UHF controller connects directly to the RF port on the Cobalt UHF antenna via a compatible antenna feeder cable (see Table 1-6 below for cabling information).
COBALT UHF-SERIES CHAPTER 1: GETTING STARTED To connect the Cobalt UHF controller to the antenna, follow the steps below: 1.4.6 Attach the TNC-Reverse male plug of the controller-antenna coaxial cable to the TNC- Reverse female connector located on the top of the controller’s housing. Attach the N-type male plug of the coaxial cable to the N-type female connector located in the rear of the antenna’s body.
COBALT UHF-SERIES 1.5 CHAPTER 1: GETTING STARTED S UBNET 16™ M ULTIDROP P ROTOCOL The UHF-CNTL-485-02 model includes support for Escort Memory Systems’ Subnet16™ Multidrop RFID networking protocol. Under the Subnet16 protocol, up to 16 UHF-CNTL-485-02 controllers can be connected via a trunk and tap network to a Subnet16 Industrial Gateway (GWY-01-IND-1), a Subnet16 TCP/IP Gateway (GWY01-TCP-01) or a Subnet16 Serial Gateway (GWY-01-232-1).
COBALT UHF-SERIES CHAPTER 2: INSTALLING THE COBALT UHF CHAPTER 2: INSTALLING THE COBALT UHF 2.1 P REPARING FOR I NSTALLATION The Cobalt UHF-Series RFID Controllers support point-to-point serial connections (RS232 and RS485), multi-drop network connections (via Subnet16™ Gateway or Hub) and Ethernet connections (TCP/IP, Ethernet/IP, Modbus TCP). NOTE: Up to 16 UHF-CNTL-485-02 units can be networked via Subnet16 Gateway interface module and Escort Memory Systems’ Subnet16 Multidrop Bus Architecture. 2.1.
COBALT UHF-SERIES CHAPTER 2: INSTALLING THE COBALT UHF 2.2 I NSTALLING THE UHF-CNTL-232-02 The UHF-CNTL-232-02 RFID Controller is designed for point-to-point RFID applications, where the distance from host to controller is less than 15 meters (50 feet). The controller connects directly to a serial communications port on a host computer via an RS232-compatible serial interface cable.
COBALT UHF-SERIES 2.2.1 CHAPTER 2: INSTALLING THE COBALT UHF Steps to Install the UHF-CNTL-232-02 1. Select a suitable location for the Cobalt UHF Controller/Antenna. 2. Attach the Cobalt UHF Antenna to the Cobalt UHF Controller, as described in Section 1.4.5 “Connecting the Antenna to the Controller”. 3. Fasten the combined controller and antenna to your mounting fixture using two M5 (#10) diameter screws (not included) and secure them with appropriate washers and nuts. Tighten screws to 1.
COBALT UHF-SERIES 2.2.2 CHAPTER 2: INSTALLING THE COBALT UHF UHF-CNTL-232-02 Cabling Information The UHF-CNTL-232-02 has one 8-pin, male M12 RS232 connector located on the bottom of the Controller’s housing.
COBALT UHF-SERIES CHAPTER 2: INSTALLING THE COBALT UHF RS232 SERIAL INTERFACE CABLE SCHEMATIC If you intend to assemble your own RS232 serial interface cable, follow the schematic below. 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 cable P/N: 9941 (www.belden.com).
COBALT UHF-SERIES CHAPTER 2: INSTALLING THE COBALT UHF 2.3 I NSTALLING THE UHF-CNTL-485-02 The UHF-CNTL-485-02 RFID Controller supports RS485 communications and Escort Memory Systems’ Subnet16™ multi-drop bus architecture and RFID network protocol. Through the Subnet16 protocol, up to 16 UHF-CNTL-485-02 units can be connected to one Subnet16 Gateway and four UHF-CNTL-485-02 units can be connected to one Hub interface module.
COBALT UHF-SERIES 2.3.1 CHAPTER 2: INSTALLING THE COBALT UHF Steps to Install the UHF-CNTL-485-02 1. Select a suitable location for the Cobalt UHF Controller/Antenna. 2. Attach the Cobalt UHF Antenna to the Cobalt UHF Controller, as described in Section 1.4.5 “Connecting the Antenna to the Controller”. 3. Fasten the combined controller and antenna to your mounting fixture using two M5 (#10) diameter screws (not included) and secure them with appropriate washers and nuts. Tighten screws to 1.
COBALT UHF-SERIES 2.3.2 CHAPTER 2: INSTALLING THE COBALT UHF UHF-CNTL-485-02 Cabling Information The UHF-CNTL-485-02 has one 5-pin, male M12 RS485 connector located on the bottom of the Controller’s housing.
COBALT UHF-SERIES CHAPTER 2: INSTALLING THE COBALT UHF 2.4 I NSTALLING THE UHF-CNTL-IND-02 The UHF-CNTL-IND-02 RFID Controller supports TCP/IP and Industrial Ethernet communications. The UHF-CNTL-IND-02 can be connected to a LAN or Programmable Logic Controller (PLC) via CAT5E Ethernet cabling or it can be connected directly to a host computer by means of a standard Ethernet crossover cable.
COBALT UHF-SERIES 2.4.1 CHAPTER 2: INSTALLING THE COBALT UHF Steps to Install the UHF-CNTL-IND-02 1. Select a suitable location for the Cobalt UHF Controller/Antenna. 2. Attach the Cobalt UHF Antenna to the Cobalt UHF Controller, as described in Section 1.4.5 “Connecting the Antenna to the Controller”. 3. Fasten the combined controller and antenna to your mounting fixture using two M5 (#10) diameter screws (not included) and secure them with appropriate washers and nuts. Tighten screws to 1.
COBALT UHF-SERIES 2.4.2 CHAPTER 2: INSTALLING THE COBALT UHF UHF-CNTL-IND-02 Cabling Information The UHF-CNTL-IND-02 includes: a 4-pin, female M12, D-code connector for Ethernet communication a 5-pin, male M12 connector for power. These connectors are located on the bottom of the Controller’s housing.
COBALT UHF-SERIES CHAPTER 2: INSTALLING THE COBALT UHF PIN # DESCRIPTION 1 NOT CONNECTED 2 10~30VDC POWER 3 0VDC (POWER GROUND) 4 NOT CONNECTED 5 NOT CONNECTED Table 2-5: Power Connector - Pinout UHF-CNTL-IND-02 CABLING PART NUMBERS CBL-1515-05: Cable Assembly (CAT5E, RJ45S to 4-pin, male M12, D- Code, 5m) CBL-1487: Field Mountable Connector (5-pos, female M12) PAGE 35 OF 140
COBALT UHF-SERIES CHAPTER 3: CONFIGURING THE COBALT CHAPTER 3: CONFIGURING THE COBALT UHF Stored in the Cobalt’s flash memory is a group of settings, attributes and parameters known as the “Controller Configuration.” These parameters are related to the communication protocol and operating mode. The controller configuration can be modified by using Escort Memory Systems’ Cobalt Dashboard Utility (which can be downloaded from www.ems-rfid.
COBALT UHF-SERIES CHAPTER 3: CONFIGURING THE COBALT COBALT UHF CONFIGURATION EXAMPLE: UHF CONFIGURATION TAB One of the five different tabs shown in the Dashboard’s main display is the UHF Configuration Tab. This tab contains two different sections: EPC Read/Write and UHF Configuration Section. These sections provide configuration details and contains parameter options related to the UHF controller’s specific features.
COBALT UHF-SERIES CHAPTER 3: CONFIGURING THE COBALT Choose Nearest, Instruct the reader to return only the information of the tag with the stronger signal, which can be assumed is the “nearest” in space, even if in real world condition this might be not always true. Furthermore, users may retrieve or set the desired UHF configuration settings by clicking on the buttons “Get UHF Config” and “Set UHF Config”. 3.
COBALT UHF-SERIES CHAPTER 3: CONFIGURING THE COBALT The following factory default values will be restored on the controller: C O N F I G U R AT I O N P AR AM E T E R F AC T O R Y D E F AU L T V AL U E Continuous Read Mode Disabled Macros and Triggers Erased UHF Power 500 mW RF channel 0 Choose Nearest Disabled RS232 - Serial Communications 9600, N, 8, 1, N RS485 - Node ID 0 IND – TCP/IP Address 192.168.253.110 Table 3-2: Configuration Tag – Restored Factory Defaults 3.3.
COBALT UHF-SERIES 3.3.3 CHAPTER 3: CONFIGURING THE COBALT Automatic Node ID Assignment via Gateway (Cobalt -485 Model Only) For multi-drop network configurations (where up to 16 Cobalt UHF-CNTL-485-02 controllers are connected via one Subnet16 Gateway interface module), a Gateway module can be instructed, through the use of a Configuration Tag, to automatically assign each controller a separate Node ID number (between 1 and 16).
COBALT UHF-SERIES 3.3.4 CHAPTER 3: CONFIGURING THE COBALT Automatic Node ID Assignment via Hub (Cobalt -485 Model Only) Subnet16 Hub interface modules, which have four independent RFID controller ports, can automatically assign an attached UHF-CNTL-485-02 controller the corresponding Node ID number of the port to which it is connected. For example, if a controller is attached to port 1 on the Hub, it will be assigned Node ID 01.
COBALT UHF-SERIES CHAPTER 4: LED STATUS CHAPTER 4: LED STATUS 4.1 LED F UNCTIONS O VERVIEW 4.1.1 LED Behavior for Cobalt UHF-CNTL-232-02 Cobalt UHF-232 RFID Controller has three LED indicators conveniently located on the front of the device, that convey visual information to the operator.
COBALT UHF-SERIES 4.1.2 CHAPTER 4: LED STATUS LED Behavior for Cobalt UHF-CNTL-485-02 The Cobalt UHF-485 RFID Controller has eight LED indicators conveniently located on the front of the device, that convey visual information to the operator.
COBALT UHF-SERIES 4.1.3 CHAPTER 4: LED STATUS LED Behavior for Cobalt UHF-CNTL-IND-02 The Cobalt UHF-IND RFID Controller has five LED indicators conveniently located on the front of the device, that convey visual information to the operator. LED FUNCTION DEF IP Amber LED COLOR ACT IP Amber PWR RF COM Power On Activity Activity Green Red Green LEDs Description LED COLOR N AM E LED DESCRIPTION RED RF The RF LED illuminates when RF power is being transmitted by the antenna.
COBALT UHF-SERIES CHAPTER 5: COMMAND PROTOCOLS CHAPTER 5: COMMAND PROTOCOLS 5.1 C OMMAND P ROTOCOLS O VERVIEW In order to execute RFID commands properly, the Cobalt UHF and host computer must be able to communicate using the same language. The language that is used to communicate is referred to as the Command Protocol. When an RFID command is issued, the host computer instructs the RFID controller to perform a given task.
COBALT UHF-SERIES CHAPTER 5: COMMAND PROTOCOLS 5.
COBALT UHF-SERIES C O M M AN D I D CHAPTER 5: COMMAND PROTOCOLS C O M M AN D N AM E DESCRIPTION 0x56 Set Controller Trigger Used to set the parameters for one of the controller’s eight triggers 0x57 Get Controller Trigger Used to retrieve the parameters of one of the controller’s eight triggers 0x70 Set Controller Macro Used to set the parameters for one of the controller’s eight macros 0x71 Get Controller Macro Used to retrieve the parameters of one of the controller’s eight macros 0x72 Ex
COBALT UHF-SERIES 5.2.
COBALT UHF-SERIES CHAPTER 5: COMMAND PROTOCOLS 5.3 AB X C OMMAND P ROTOCOL O VERVIEW There are two versions of the ABx Command Protocol that are supported by the Cobalt UHF Serial Controller, they are: ABx Fast (default) ABx Standard The ABx Fast Command Protocol has a single-byte based packet structure that permits the execution of RFID commands while requiring the transfer of fewer total bytes than ABx Standard. ABx Fast is the default command protocol used by Cobalt UHF Serial RFID Controller.
COBALT UHF-SERIES CHAPTER 5: COMMAND PROTOCOLS When a command is issued by the host, the RFID controller stores the incoming data packet 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 verify the format of the data and either perform the requested function or generate an error message. 5.3.
COBALT UHF-SERIES CHAPTER 5: COMMAND PROTOCOLS 5.4 AB X F AST C OMMAND P ROTOCOL The default command protocol used by UHF-CNTL-232-02 RFID Controllers for Point-to-Point data transmission is known as the ABx Fast Command Protocol. ABx Fast has a single-byte oriented packet structure that permits the rapid execution of RFID commands while requiring the transfer of a minimal number of bytes. ABx Fast supports the inclusion of an optional checksum byte.
COBALT UHF-SERIES 5.4.2 CHAPTER 5: COMMAND PROTOCOLS ABx Fast - Command Packet Structure The packet structure of all ABx Fast RFID commands contains certain basic elements, including Command Header, Command Size, Command ID and Command Terminator. Packet element and parameter availability depends on the command being performed.
COBALT UHF-SERIES 5.4.3 CHAPTER 5: COMMAND PROTOCOLS ABx Fast – Command Packet Elements Command Size The ABx Fast protocol requires that the byte count, known as the Command Size, be specified as a two-byte integer within each command packet. To calculate the Command Size, add the total number of bytes within the command packet while excluding the two byte Command Header, the two byte Command Size, the one byte Checksum (if present) and the one byte Command Terminator (see example below).
COBALT UHF-SERIES CHAPTER 5: COMMAND PROTOCOLS Timeout Value Most ABx Fast commands include a two-byte Timeout Value, which is used to limit the length of time that the Cobalt UHF will attempt to complete the specified operation. The Timeout Value is measured in 1-millisecond increments and has a maximum supported value of 0xFFFE or 65,534 milliseconds (which is slightly longer than one minute). Setting a long Timeout Value does not necessarily mean that a command will take any longer to execute.
COBALT UHF-SERIES CHAPTER 5: COMMAND PROTOCOLS CHECKSUM EXAMPLE The following example depicts Command 0x05 (Read Data) when using a Checksum.
COBALT UHF-SERIES 5.4.4 CHAPTER 5: COMMAND PROTOCOLS ABx Fast - Multi-Tag Command Packet Structure Multi-tag (anti-collision) commands are used to communicate with one or more RFID tags, when numerous tags are simultaneously within RF range.
COBALT UHF-SERIES 5.4.5 CHAPTER 5: COMMAND PROTOCOLS ABx Fast - Multi-Tag Command Packet Elements Tag Limit The Tag Limit parameter holds a one-byte value that indicates the maximum number of tags expected simultaneously in RF range for the given command operation. This parameter allows users to limit the number of attempted read/write operations the controller will make per execution. Users do not have to wait for the timeout to expire.
COBALT UHF-SERIES 5.4.6 CHAPTER 5: COMMAND PROTOCOLS ABx Fast - Response Packet Structure After performing a command, the Cobalt UHF will generate a host-bound response packet. ABx Fast responses contain a Response Header, Response Size, Command Echo, one or more Response Values / Retrieved Data (when applicable), and a Response Terminator.
COBALT UHF-SERIES 5.4.7 CHAPTER 5: COMMAND PROTOCOLS ABx Fast Protocol: Error Response Packet Structure ABx Fast error responses contain a two-byte Response Header, a two-byte Response Size parameter followed by a single-byte Error Flag (0xFF), a single-byte Error Code, which identifies the error that occurred, and a single-byte Response Terminator.
COBALT UHF-SERIES CHAPTER 5: COMMAND PROTOCOLS SINGLE-TAG RFID COMMAND 0XC2: READ EPC CODE COMMAND 0XC2 – DESCRIPTION The Read EPC Command instructs the controller to retrieve the EPC memory area of a single tag UHF Class1 Gen2. COMMAND 0XC2 - ABX FAST EXAMPLE This example instructs the controller to read the EPC memory from a tag. A Timeout Value of 2 seconds (0x07D0 = 2000 x one-millisecond increments) is set for the completion of the command.
COBALT UHF-SERIES CHAPTER 5: COMMAND PROTOCOLS SINGLE-TAG RFID COMMAND 0XC3: WRITE EPC CODE COMMAND 0XC3 – DESCRIPTION The Write EPC Command instructs the controller to write the EPC memory area of a single tag UHF Class1 Gen2. COMMAND 0XC3 - ABX FAST EXAMPLE This example instructs the controller to write the specified bytes in the EPC memory of a tag. A Timeout Value of 2 seconds (0x07D0 = 2000 x one-millisecond increments) is set for the completion of the command.
COBALT UHF-SERIES CHAPTER 5: COMMAND PROTOCOLS MULTI-TAG RFID COMMAND 0XC4: READ EPC CODE COMMAND 0XC4 – DESCRIPTION The Multi-Tag Read EPC Code is used to retrieve the EPC data from all tags within RF range. A final termination packet is sent when the Timeout Value expires. COMMAND 0XC4 - ABX FAST EXAMPLE This example instructs the controller to read the EPC data from each tag in range. A Timeout Value of 3 seconds (0x0BB8 = 3000 x 1msec increments) is set for the completion of the command.
COBALT UHF-SERIES CHAPTER 5: COMMAND PROTOCOLS Final Termination Packet PARAMETER FIELD CONTENT Response Header 0x02, 0x02 Response Size 0x0004 Final Termination Packet Identifier 0xFF Number of Tags Read Status 0x0000 Response Terminator 0x03 PAGE 63 OF 140
COBALT UHF-SERIES CHAPTER 5: COMMAND PROTOCOLS CONTROLLER SPECIFIC COMMAND 0XC0: SET UHF CONFIGURATION COMMAND 0XC0 – DESCRIPTION The Set UHF Configuration command is used to set (configure or modify) the controller’s UHF configuration parameters and settings to the controller’s flash memory. IMPORTANT: it is recommended that users first run Command 0xC1: Get UHF Configuration and make note of their current controller configuration values prior to executing this command.
COBALT UHF-SERIES UHF Configuration Byte 9 This byte permits the user to enable/disable the Choose Nearest One property. If the Choose Nearest One property is disabled, an error response is generated whenever a single-tag read/write command is executed in a multi-tag environment. If the Choose Nearest One property is enabled, the read/write command is executed on the tag with the stronger signal.
COBALT UHF-SERIES CHAPTER 5: COMMAND PROTOCOLS CONTROLLER SPECIFIC COMMAND 0XC1: GET UHF CONFIGURATION COMMAND 0XC1 – DESCRIPTION The Get UHF Configuration Command instructs the controller to retrieve the controller’s UHF configuration parameters and settings stored in the unit’s flash memory. These are the same values that are set with Command 0xC0: Set UHF Configuration.
COBALT UHF-SERIES 5.5 CHAPTER 5: COMMAND PROTOCOLS CB X C OMMAND P ROTOCOL The CBx Command Protocol is based on a double-byte oriented packet structure where commands always contain a minimum of six data “words,” even when one or more parameters are not applicable to the command. CBx does not support the inclusion of a checksum byte.
COBALT UHF-SERIES 5.5.2 CHAPTER 5: COMMAND PROTOCOLS CBx - Command Packet Structure As noted, CBx commands contain a minimum of six words. Below is the structure of a standard CBx command packet. Table 5-12: CBx Command Packet Structure CBx Command Packet Structure (MSB = Most Significant Byte, LSB = Least Significant Byte) WORD # C O M M AN D P AC K E T E L E M E N T MSB LSB 01 Overall Length: 2-byte integer indicating the number of 16-bit “words” in the command packet.
COBALT UHF-SERIES CHAPTER 5: COMMAND PROTOCOLS 04 Timeout Value: 2-byte integer representing the length of time allowed for the completion of the command (when applicable). Measured in one-millisecond increments, the Timeout Value can have a value of 0x0001 to 0xFFFE (1 - 65,534 milliseconds).
COBALT UHF-SERIES 03 CHAPTER 5: COMMAND PROTOCOLS Instance Counter: in MSB (see description on following page) Node ID Echo: Value in LSB identifies the Node ID of the device that performed the command and/or generated the response (will always be 0x20 for Gateway/Hub, and 0x01 for Cobalt IND) 04 Month and Day Timestamp 05 Hour and Minute Timestamp 06 Second Timestamp in MSB Additional Data Len
COBALT UHF-SERIES 5.5.4 CHAPTER 5: COMMAND PROTOCOLS CBx Multi-Tag Command Packet Structure CBx Multi-tag Commands instruct a specified controller to read from or write to several tags at once when multiple tags are simultaneously within RF range. It is also possible to single-out and read from or write to one tag (identified by its unique tag ID number) when multiple tags are present in the RF field simultaneously. Below is the structure of a basic CBx multi-tag command packet.
COBALT UHF-SERIES CHAPTER 5: COMMAND PROTOCOLS 09 Additional Data Byte Values 1 & 2: holds 2 bytes of data used for fills, writes, etc. (when applicable) 10 Additional Data Byte Values 3 & 4: holds an extra 2-bytes for write operations if needed (when applicable) Table 5-15: CBx Multi-Tag Command Packet Structure 5.5.
COBALT UHF-SERIES 5.5.6 CHAPTER 5: COMMAND PROTOCOLS CBx Multi-Tag Response Packet Structures When executing multi-tag commands designed to retrieve information from several tags at once (for example CBx Command 0x92: Multi-Tag Read ID and Data All), the RFID controller will generate separate host-bound response packets for each tag that has been read. Below is the structure of a basic CBx multi-tag response packet generated by the controller at Node 01.
COBALT UHF-SERIES 5.5.7 CHAPTER 5: COMMAND PROTOCOLS CBx Multi-Tag Response Final Termination Packet Structure After the RFID controller has issued response packets for each tag identified and/or read, a final termination packet is generated. Below is the structure of a standard CBx multi-tag response final termination packet generated by the controller at Node 01.
COBALT UHF-SERIES 5.5.8 CHAPTER 5: COMMAND PROTOCOLS CBx Protocol: Error Response Packet Structure A one-byte Error Code will be returned in the MSB of the seventh data word of an error response packet (followed by 0x00 in the LSB). ERROR RESPONSE ELEMENT MSB LSB Overall Length: 2-byte value indicating the number of “words” in the Response Packet. This value will always be at least 7 words (6 + 1 for the error code). 0x00 0x07 Error Flag: 0xFF in the MSB indicates that an error occurred.
COBALT UHF-SERIES CHAPTER 5: COMMAND PROTOCOLS CBX SINGLE-TAG RFID COMMAND 0XC2: READ EPC CODE COMMAND 0XC2 - DESCRIPTION The Read EPC Command instructs the controller to retrieve the EPC memory area of a single tag UHF Class1 Gen2. COMMAND 0XC2 - CBX EXAMPLE This example instructs the controller to read the EPC memory from a tag. A Timeout Value of 2 seconds (0x07D0 = 2000 x one-millisecond increments) is set for the completion of the command.
COBALT UHF-SERIES CHAPTER 5: COMMAND PROTOCOLS Response from Controller (Tag Found) P AR AM E T E R F I E L D MSB LSB Overall Length of Response (in words) 0x00 0x0C 0xAA in MSB, Command Echo in LSB 0xAA 0xC2 Instance Counter in MSB, Node ID Echo in LSB 0x01 Month and Day Timestamp: (March 19 ) 0x03 0x13 Hour and Minute Timestamp: (10:11: AM) 0x0A 0x0B Seconds Timestamp in MSB: (:36 seconds) 0x24 0x0C EPC (bytes 1 & 2) 0xE0 0x04 EPC (bytes 3 & 4) 0x01 0x00 EPC (bytes 5 & 6)
COBALT UHF-SERIES CHAPTER 5: COMMAND PROTOCOLS CBX SINGLE-TAG RFID COMMAND 0XC3: WRITE EPC CODE COMMAND 0XC3 - DESCRIPTION The Write EPC Command instructs the controller to write the EPC memory area of a single tag UHF Class1 Gen2. COMMAND 0XC3 - CBX EXAMPLE This example instructs the controller to write the specified bytes in the EPC memory of a tag. A Timeout Value of 2 seconds (0x07D0 = 2000 x one-millisecond increments) is set for the completion of the command.
COBALT UHF-SERIES CHAPTER 5: COMMAND PROTOCOLS Response from Controller P AR AM E T E R F I E L D MSB LSB Overall Length of Response (in words) 0x00 0x06 0xAA in MSB 0xAA 0xC3 0x01 Month and Day Timestamp: th (March 19 ) 0x03 0x13 Hour and Minute Timestamp: (10:11: AM) 0x0A 0x0B Seconds Timestamp in MSB (:36 seconds) 0x24 0x00 Command Echo in LSB Instance Counter in MSB Node ID Echo in LSB 0x00 in LSB PAGE 79 OF 140
COBALT UHF-SERIES CHAPTER 5: COMMAND PROTOCOLS MULTI-TAG RFID COMMAND 0XC4: READ EPC CODE COMMAND 0XC4 - DESCRIPTION The Multi-Tag Read EPC Code is used to retrieve the EPC data from all tags within RF range. A final termination packet is sent when the Timeout Value expires. COMMAND 0XC4 - CBX EXAMPLE This example instructs the controller to read the EPC data from each tag in range. A Timeout Value of 3 seconds (0x0BB8 = 3000 x 1msec increments) is set for the completion of the command.
COBALT UHF-SERIES Seconds Timestamp in MSB (:36 seconds) CHAPTER 5: COMMAND PROTOCOLS 0X24 0X0C EPC ID (bytes 1 and 2) EPC ID (bytes 3 and 4) EPC ID (bytes 5 and 6) EPC ID (bytes 7 and 8) EPC ID (bytes 9 and 10) EPC ID (bytes 11 and 12) P AR AM E T E R F I E L D MSB LSB Overall Length of Response (in words) 0X00 0X07 0xAA in MSB, 0xFF in LSB 0XAA 0XFF Instance Counter in MSB 0X01 Month and Day T
COBALT UHF-SERIES CHAPTER 5: COMMAND PROTOCOLS CONTROLLER SPECIFIC COMMAND 0XC0: SET UHF CONFIGURATION COMMAND 0XC0 – DESCRIPTION The Set UHF Configuration command is used to set (configure or modify) the controller’s UHF configuration parameters and settings to the controller’s flash memory. IMPORTANT: it is recommended that users first run Command 0xC1: Get UHF Configuration and make note of their current controller configuration values prior to executing this command.
COBALT UHF-SERIES CHAPTER 5: COMMAND PROTOCOLS UHF Configuration Byte 7 in MSB * 0x00 UHF Configuration Byte 8 in LSB Byte 8 in LSB is partially reserved (see table below). This byte permits the user to select the specific UHF channel through which commands are transmitted. The user can write a value between o and 9 in bits from 4 to 7 UHF Config.
COBALT UHF-SERIES CHAPTER 5: COMMAND PROTOCOLS *Leave the default value retrieved through Command 0xC1: Get UHF Configuration Response from Controller P AR AM E T E R F I E L D MSB LSB Overall Length of Response (in words) 0x00 0x06 0xAA in MSB 0xAA 0xC0 0x01 Month and Day Timestamp: th (March 19 ) 0x03 0x13 Hour and Minute Timestamp: (10:11: AM) 0x0A 0x0B Seconds Timestamp in MSB (:36 seconds) 0x24 0x00 Command Echo in LSB Instance Counter in MSB Node ID Echo in LSB 0x00 in LSB
COBALT UHF-SERIES CHAPTER 5: COMMAND PROTOCOLS CONTROLLER SPECIFIC COMMAND 0XC1: GET UHF CONFIGURATION COMMAND 0XC1 – DESCRIPTION The Get UHF Configuration Command instructs the controller to retrieve the controller’s UHF configuration parameters and settings stored in the unit’s flash memory. These are the same values that are set with Command 0xC0: Set UHF Configuration.
COBALT UHF-SERIES CHAPTER 5: COMMAND PROTOCOLS UHF Configuration Bytes 1 & 2 UHF Configuration Bytes 3 & 4 UHF Configuration Bytes 5 & 6 UHF Configuration Bytes 7 & 8 UHF Configuration Bytes 9 & 10 0x00 These two bytes represent the Reader Output Power (0÷500 mW).
COBALT UHF-SERIES CHAPTER 5: COMMAND PROTOCOLS 5.
COBALT UHF-SERIES CHAPTER 5: COMMAND PROTOCOLS 0x89 SUBNET RESPONSE MALFORMED Internal Subnet Error – a controller returned a malformed response. 0x8A SUBNET RESPONSE TIMEOUT Internal Subnet Error – a controller was unable to generate a response before timeout was reached. 0x8B SUBNET RESPONSE INVALID CHECKSUM Internal Subnet Error – a controller generated a response that has an invalid checksum.
COBALT UHF-SERIES CHAPTER 6: ETHERNET/IP INTERFACE CHAPTER 6: ETHERNET/IP INTERFACE The Cobalt UHF-CNTL-IND-02 model is designed to support many common Industrial Ethernet protocols and can be implemented in a wide variety of existing host / PLC applications. One such popular Ethernet protocol is Ethernet/IP (EIP). This chapter focuses on the process of setting up the Cobalt Industrial RFID Controller to communicate (via Ethernet/IP) with a ControlLogix Programmable Logic Controller (PLC).
COBALT UHF-SERIES CHAPTER 6: ETHERNET/IP INTERFACE Sections 6.3 through 6.7 contain instructions that will help you accomplish the following: Assign the Cobalt an IP address via HTML Server Configure the Cobalt’s Subnet Node via OnDemand Utilities Create “Controller Tags” in the PLC Verify PLC and Cobalt Subnet Node connectivity 6.2 HTML S ERVER & O N D EMAND PLC S UPPORT Below is a partial list of the programmable logic controllers that are supported by EMS’ HTML Server and OnDemand Utilities.
COBALT UHF-SERIES 6.4 CHAPTER 6: ETHERNET/IP INTERFACE IP C ONFIGURATION VIA HTML S ERVER To configure the Cobalt for Ethernet communications, begin by assigning the controller a locally compatible IP address. Through a standard Web browser, you can utilize the Cobalt’s HTML Server to access an embedded suite of controller configuration tools, called the “OnDemand Utilities.
COBALT UHF-SERIES CHAPTER 6: ETHERNET/IP INTERFACE 4. Click the button labeled “EDIT”, located below “Network Settings.” The IP Configuration Page will be displayed. IP CONFIGURATION PAGE The IP Configuration Page is used to modify and save changes to the IP Address, Subnet Mask and (Network) Gateway IP Address. Figure 6-2: The IP Configuration Page 5. In the fields provided, enter your new IP configuration values for the Cobalt. 6.
COBALT UHF-SERIES 6.5 CHAPTER 6: ETHERNET/IP INTERFACE O N D EMAND C ONFIGURATION FOR E THERNET /IP Now that you have configured the Cobalt’s IP address, you will need to use the embedded HTML Server to access the Cobalt’s OnDemand Configuration Page. Through the use of the OnDemand Configuration Page, the Cobalt can be configured to communicate with a ControlLogix PLC. To configure the Cobalt’s OnDemand Configuration settings, follow the steps below: 1.
COBALT UHF-SERIES CHAPTER 6: ETHERNET/IP INTERFACE ONDEMAND CONFIGURATION PAGE The OnDemand Configuration Page allows you to modify the settings of the Cobalt’s Node. Figure 6-3: The OnDemand Configuration Page 3. In the upper portion of the OnDemand Configuration Page, select a PLC Type from the drop-down menu. 4. Enter the PLC’s IP address. 5. For the PLC Slot Number, enter a value between 0 and 255.
COBALT UHF-SERIES CHAPTER 6: ETHERNET/IP INTERFACE 6. In the Read Delay field, enter a value between 0 and 6000. This number specifies (in 10ms “ticks”) how frequently the Cobalt will poll the PLC for the presence of new data. (Note: a value of 6000 = 60 seconds; zero = disable). 7. In the column labeled “Enable Node,” place a check in the box for Node 01. Other Nodes listed on this page are not supported by the Cobalt –IND. 8.
COBALT UHF-SERIES CHAPTER 6: ETHERNET/IP INTERFACE 13. At the OnDemand Status Page, click the link labeled “Main Page” to return to the HTML Server – Main Page. 6.6 C ONFIGURING PLC C ONTROLLER T AGS After you have configured the Cobalt’s Node via the OnDemand Configuration Page, open your PLC program (i.e. RSLogix 5000) and, if you have not already done so, define two Controller Tags (a Write Tag and a Read Tag). Controller Tag Naming Controller Tags need to be assigned a name and size.
COBALT UHF-SERIES 6.7 CHAPTER 6: ETHERNET/IP INTERFACE C HECKING O N D EMAND S TATUS Now that you have configured the Cobalt’s Node and defined corresponding Write and Read Tags in the PLC, the last step is to check the communication status between the Cobalt and the PLC. Return to the Cobalt’s HTML Server - Main Page and click the link labeled “OnDemand Status.” The OnDemand Status Page will be displayed.
COBALT UHF-SERIES 6.8 CHAPTER 6: ETHERNET/IP INTERFACE V ERIFYING D ATA E XCHANGE WITH RSL OGIX 5000 At this point, communication between the Cobalt and the PLC should be properly configured and a connection established. You can verify the exchange of information between devices using RSLogix 5000. Figure 6-5: RSLogix 5000 6.8.
COBALT UHF-SERIES CHAPTER 6: ETHERNET/IP INTERFACE WRITE TAG (where responses are written by the Cobalt) EMS_Write1 [0] = (2) the Cobalt copies counter here to ACK EMS_Write1 [1] = (3) the Cobalt increments this counter to signal response available EMS_Write1 [2] = Data Size EMS_Write1 [3-102] = Data READ TAG (where commands are retrieved by the Cobalt) EMS_Read1 [0] = (4) PLC copies the counter here to ACK the response EMS_Read1 [1] = (1) PLC increments this counter after writing a command EMS_Read1 [2]
COBALT UHF-SERIES CHAPTER 6: ETHERNET/IP INTERFACE 4. After the PLC has processed the response information, it copies the counter from EMS_WRITE1 [1] to EMS_READ1 [0] which signals to the Cobalt that the PLC has retrieved the response data. 5. The data will then be cleared from EMS_WRITE1. After which the Cobalt will be ready to receive another command. 6.
COBALT UHF-SERIES CHAPTER 6: ETHERNET/IP INTERFACE Drive. This ensures that all devices with the same profile have a common look on the network. DAT A TYPE DEFINITION TABLE EtherNet/IP was designed by the Open Device Vendors Association (ODVA) as an open protocol. The following table contains a description of the data types used by ODVA that are also found in this chapter.
COBALT UHF-SERIES CHAPTER 6: ETHERNET/IP INTERFACE IDENTITY OBJECT (0X01 - 1 INSTANCE) Class Attributes Attribute ID Name / Description Data Type Default Data Value Access Rule 1 Revision UINT 1 Get Instance Attributes Attribute ID Name / Description Data Type Default Data Value Access Rule 1 Vendor Number UINT 50 DEC Get 2 Device Type UINT 0x0C Get 3 Product Code Number UINT 6102 DEC Get 4 Product Major Revision USINT 01 Get Product Minor Revision USINT 25 5 Status
COBALT UHF-SERIES CHAPTER 6: ETHERNET/IP INTERFACE ASSEMBLY OBJECT (0X04 - 3 INSTANCES) Class Attributes Attribute ID Name / Description Data Type Default Data Value Access Rule 1 Revision UINT 1 Get 2 Max Instance UINT 81 Get Instance 0x64 Attributes (Input Instance) Attribute ID Name / Description 3 Status Information: Data Type Default Data Value Access Rule Get Bitmap of Consume Instances with Data DINT 0 Bitmap of Produce Instances with Data DINT 0 User Datagram Protocol (
COBALT UHF-SERIES CHAPTER 6: ETHERNET/IP INTERFACE Instance 0x66 Attributes (Input Instance 3) Attribute ID Name / Description 3 Serial Produce Data: Data Type Default Data Value Access Rule Get Consume Data Seq.
COBALT UHF-SERIES CHAPTER 6: ETHERNET/IP INTERFACE Instance 0x81 Attributes (Heartbeat Instance – Input Only) This instance allows clients to monitor input data without providing output data. Common Services Service Code Implementation Service Name Class Level Instance Level 0x0E Yes Yes Get Attribute Single 0x10 No Yes Set Attribute Single CONNECTION MANAGER OBJECT (0X06) This object has no attributes.
COBALT UHF-SERIES 6 CHAPTER 6: ETHERNET/IP INTERFACE Get Host Name* Structure of: Host Name Size UINT 0 Host Name STRING 0 *See section 5-3.2.2.1 – 5-3.2.2.6 of “Volume 2: EtherNet/IP Adaptation of CIP” from ODVA for more information regarding these attributes.
COBALT UHF-SERIES 6.9.
COBALT UHF-SERIES CHAPTER 6: ETHERNET/IP INTERFACE … … … … … 82 Consume Data [20,000-20,249] UINT 0 Get / Set … … … … … 122 Consume Data [30,000-30,249] UINT 0 Get / Set … … … … … 126 Consume Data [31,000-31,249] UINT 0 Get / Set … … … … … 130 Consume Data [32,000-32,249] UINT 0 Get / Set 131 Consume Data [32,250-32,249] UINT 0 Get / Set 132 Consume Data [32,500-32,249] UINT 0 Get / Set 133 Consume Data [32,750-32,767] UINT 0 Get / Set Common Services
COBALT UHF-SERIES CHAPTER 6: ETHERNET/IP INTERFACE Instance Attributes (Instances 1-32) Attribute ID Name / Description Data Type Default Data Value Access Rule 1 Produce Data Size (in words) UINT 0 Get / Set 2 Produce Data [0-249] UINT 0 Get 3 Produce Data [250-499] UINT 0 Get 4 Produce Data [500-749] UINT 0 Get 5 Produce Data [750-999] UINT 0 Get 6 Produce Data [1,000-1,249] UINT 0 Get … … … … … 10 Produce Data [2,000-2,249] UINT 0 Get … … … … … 34 Prod
COBALT UHF-SERIES CHAPTER 6: ETHERNET/IP INTERFACE Common Services Service Code Implementation Service Name Class Level Instance Level 0x05 No Yes Reset* 0x0E Yes Yes Get Attribute Single 0x10 No Yes Set Attribute Single *This Service Code is used to flush all attributes to zero. 6.9.
COBALT UHF-SERIES 15 21 CHAPTER 6: ETHERNET/IP INTERFACE Write “Heartbeat” Timeout Measured in 10ms “ticks” 0 = disabled Max value: 6000 ticks Max Read Size in Words UINT 100 Get UINT 0 Get 0 – Disable Max Value: 100 22 Read Tag Name (ControlLogix Only) SHORT STRING 0 Get 23 Read File Number (SLC/PLC Only) UINT 7 Get UINT 0 Get UINT 100 Get NX:0 - Where “X” is the File Number 24 Read File Offset (SLC/PLC Only) N7:Y - Where “Y” is the File Offset 25 Read Poll Rate
COBALT UHF-SERIES CHAPTER 7: MODBUS TCP INTERFACE CHAPTER 7: MODBUS TCP INTERFACE One of the most popular and well-proven industrial automation protocols in use today is Modbus®. Modbus is an open client/server application protocol. Modbus TCP allows the Modbus protocol to be carried over standard Ethernet networks. Modbus TCP is managed by the Modbus-IDA User Organization. 7.1 M ODBUS TCP O VERVIEW Under the MODBUS® TCP protocol, the Cobalt acts as a Modbus Server and the PLC acts as a Modbus Client.
COBALT UHF-SERIES CHAPTER 7: MODBUS TCP INTERFACE HTML SERVER – MAIN PAGE Figure 7-1: The HTML Server - Main Page The HTML Server - Main Page lists the network settings (including the IP address) currently stored on the Cobalt. 4. Click the button labeled “EDIT”, located below “Network Settings.” The IP Configuration Page will be displayed.
COBALT UHF-SERIES CHAPTER 7: MODBUS TCP INTERFACE IP CONFIGURATION PAGE The IP Configuration Page is used to modify and save changes to the IP Address, Subnet Mask and (Network) Gateway IP Address. Figure 7-2: The IP Configuration Page 5. In the fields provided, enter your new IP configuration values for the Cobalt. 6. Click the “Save Settings” button to store your new IP configuration, then cycle power to the UHF-CNTL to store the changes in the main memory.
COBALT UHF-SERIES 7.2.2 CHAPTER 7: MODBUS TCP INTERFACE Modbus TCP - Command Packet Structure Consume Registers hold data that is destined for the Cobalt. Modbus TCP commands must be placed in the holding registers, starting at address 40001, of Device ID 01 (Node Input Page 01). Commands utilize at least six registers (doublebyte values or words).
COBALT UHF-SERIES 7.2.3 CHAPTER 7: MODBUS TCP INTERFACE Modbus TCP - Response Packet Structure Produce Registers hold data that is destined for the host or PLC.
COBALT UHF-SERIES CHAPTER 7: MODBUS TCP INTERFACE 13 RO MAC Address 1 (MSB) Example: 0x00 14 RO MAC Address 2 Example: 0x40 15 RO MAC Address 3 Example: 0x9D 16 RO MAC Address 4 Example: 0x12 17 RO MAC Address 5 Example: 0x34 18 RO MAC Address 6 (LSB) Example: 0x56 19 RO Link Status: 0 = No Link 1 = Link is OK 20 RO Ethernet Speed (10M or 100M bits) 21 RO Link Duplex: 0 = Half Duplex 1 = Full Duplex 22 RO Revision (Major/Minor) 23 – 1000 R/W Reserved 1001 RO (Input) Data
COBALT UHF-SERIES 7.3 CHAPTER 7: MODBUS TCP INTERFACE M ODBUS TCP - H ANDSHAKING Due to the process with which commands and responses are passed between the Cobalt and the host, a handshaking procedure is used to notify the host that returning data is available for retrieval. OVERALL LENGTH The handshaking process is governed by the changing of the “Overall Length” value within a data packet.
COBALT UHF-SERIES 7.3.1 CHAPTER 7: MODBUS TCP INTERFACE Modbus TCP - Host/Cobalt Handshaking When the host issues a command, it must first write the entire command to the Node Input Page, leaving the Overall Length value to be written last. For example, for the host to issue the 6-word command “Read Data,” it must first write the last five words of the command to Node Input Page 01, beginning at register 40002.
COBALT UHF-SERIES CHAPTER 7: MODBUS TCP INTERFACE 4. After the Cobalt executes its given command instructions, it will write the command response to the holding registers for Device ID 33 (Node Output Page 33). Again, the Overall Length value is written last to holding register 40001. NOTE: Host-bound data is always written to Device ID 33 (Node Output Page 33). 5.
COBALT UHF-SERIES CHAPTER 8: STANDARD TCP/IP INTERFACE CHAPTER 8: STANDARD TCP/IP INTERFACE 8.1 S TANDARD TCP/IP O VERVIEW Another means of communicating with the Cobalt is through the standard TCP/IP protocol. For this manual, the protocol is referred to as standard TCP/IP to distinguish it from other industrial protocols. In this environment, the Cobalt acts as the server and the host or PLC acts as client.
COBALT UHF-SERIES 8.2.1 CHAPTER 8: STANDARD TCP/IP INTERFACE Setting the IP Address of the Cobalt To set the Cobalt’s IP address using the HTML Server, follow the steps below: 1. Open a Web browser on the PC. 2. In the URL address field, enter the Cobalt’s IP address (192.168.253.110 = factory default). 3. Press ENTER. The HTML Server - Main Page will be displayed.
COBALT UHF-SERIES CHAPTER 8: STANDARD TCP/IP INTERFACE IP CONFIGURATION PAGE The IP Configuration Page is used to modify and save changes to the IP Address, Subnet Mask and (Network) Gateway IP Address. Figure 8-2: The IP Configuration Page 5. In the fields provided, enter your new IP configuration values for the Cobalt. 6. Click the “Save Settings” button to store your new IP configuration. The Cobalt will completely reset and your IP changes will be implemented. 7.
COBALT UHF-SERIES 8.3 CHAPTER 8: STANDARD TCP/IP INTERFACE S TANDARD TCP/IP - C OMMAND & R ESPONSE E XAMPLES In standard TCP/IP, RFID commands issued by the host resemble Modbus TCP commands. The Cobalt handles all handshaking tasks. Moreover, the command & response packets need an additional word at the beginning of the string: Protocol Header 0xFF in MSB, in LSB.
COBALT UHF-SERIES 8.3.1 CHAPTER 8: STANDARD TCP/IP INTERFACE Standard TCP/IP - Command Structure & Example In the following example, a 12-byte command has been issued to the Cobalt, instructing the controller to read six bytes from a tag within RF range. A Timeout Value of five seconds has been set for the completion of the command.
COBALT UHF-SERIES 8.3.
COBALT UHF-SERIES CHAPTER 9: RFID OVERVIEW CHAPTER 9: RFID OVERVIEW 9.1 RFID O VERVIEW Cobalt UHF-Series products are designed for use with passive RFID tags, which do not require batteries or contain an internal power supply. The tags collect the power necessary to operate from the RF field generated by the reader and through a process called backscattering they can reflect some of this power back to the reader, thus creating a communication channel.
COBALT UHF-SERIES CHAPTER 9: RFID OVERVIEW 9.2 O VERVIEW ON U LTRA H IGH F REQUENCY RFID A PPLICATIONS 9.2.1 UHF Standards and Regulations One of the most important aspects of a tag and reader coupling is the frequency at which it operates. Frequency of operation can vary based on the application, standards, and regulations. The most common RFID frequency ranges are Low Frequency (LF) at 135kHz or less, High Frequency (HF) at 13.56MHz, Ultra High Frequency (UHF) starting at 300MHz.
COBALT UHF-SERIES CHAPTER 9: RFID OVERVIEW There are different UHF operating frequency standards all over the world, regulated by governmental authorities in most countries: for instance, Federal Communications Commission (FCC) in the United States and ETSI (European Telecommunications Standards Institute) in Europe. Globally, each country has its own frequency allocation for RFID.
COBALT UHF-SERIES 9.2.2 CHAPTER 9: RFID OVERVIEW UHF Signal Propagation In general, the frequency defines the data transfer rate (speed) between the tag and the reader. For this reason, UHF systems feature long range, and high speed read/write rates. Small antennas and even smaller tags have proven this to be an effective frequency for tracking pallets through dock doors, as well as trucking and transportation applications.
COBALT UHF-SERIES CHAPTER 9: RFID OVERVIEW Furthermore, the Cobalt UHF antennas feature a 3dB Beamwidth, 63° or 65°, providing a large reading zone. 3 D B B E AM W I D T H A B 0.5 0.6 1.0 1.3 1.5 2.0 2.0 2.6 2.5 3.1 3.0 3.7 Figure 9-4: Circular Polarized Antenna’s Reading Range As considered above, the ability for signals to propagate within environment is dependent on the signal wavelength, and hence frequency.
COBALT UHF-SERIES CHAPTER 9: RFID OVERVIEW All materials reduce the power of the RF signal to some extent, but direct contact on metals and liquids can cause particular problems: Metals reflect the signal. A metal object may change the tuning of a tag (or frequency on which it can receive signals), reflecting the RF waves from a reader, or block communication from a specific antenna. Liquids (including atmospheric moisture) absorb the signal.
COBALT UHF-SERIES APPENDIX A: TECHNICAL SPECIFICATIONS APPENDIX A: TECHNICAL SPECIFICATIONS C OBALT UHF C ONTROLLERS - T ECHNICAL S PECIFICATIONS ELECTRICAL DC Input Voltage Range 12 – 30 VDC Power 6.7 W (280 mA @24 VDC) Reverse Polarity Protection Series Diode protection on DC power pins Tolerable Ripple 100 mVpp Over-current Protection 1 amp internal limit RADIO Transmitter Frequency 902 to 928 MHz (FCC part 15) 865.600 to 867.
COBALT UHF-SERIES APPENDIX A: TECHNICAL SPECIFICATIONS MECHANICAL Dimensions 163mm (6.4 inches) H x 112mm (4.4 inches) L x 48mm (1.9 inches) W Weight .56 KG (.97 lb.
COBALT UHF-SERIES APPENDIX A: TECHNICAL SPECIFICATIONS C OBALT UHF A NTENNAS - T ECHNICAL S PECIFICATIONS ELECTRICAL UHF-ANT-2626-01-86 Frequency Range 865 - 870 MHz Gain 8.5 dBic (min) - 9.
COBALT UHF-SERIES APPENDIX B: MODELS & ACCESSORIES APPENDIX B: MODELS & ACCESSORIES Datalogic Automation designs, manufactures and distributes a wide range of ultra high frequency (UHF) RFID equipment, including RFID controllers, network interface modules (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 Cobalt UHF-Series RFID product family.
COBALT UHF-SERIES APPENDIX B: MODELS & ACCESSORIES C OBALT UHF-S ERIES A NTENNAS (COMPATIBLE WITH THE UHF SERIES CONTROLLERS ABOVE) There are two models of the Cobalt UHF RFID Antenna: UHF-ANT-2626-01-86 26cm x 26cm, 868 MHz UHF-ANT-3030-01-91 30cm x 30cm, 915 MHz S UBNET 16 G ATEWAYS (COMPATIBLE WITH THE UHF-CNTL-485-02 CONTROLLER MODEL) There are four models of the Subnet16 Gateway: GWY-01-232-01 Subnet16™ RS232 Gateway GWY-01-IND-01 Subnet16™ Industrial Ethernet Gateway GWY-01-TCP-01 Subnet1
COBALT UHF-SERIES APPENDIX B: MODELS & ACCESSORIES 00-1168 5.0A max @ 24VDC (120W), Universal Input (88-132VAC/176-264VAC switch selectable, 47-63Hz) DIN Rail Mount (AC wire receptacles are spring clamped for direct wire connections). S OFTWARE A PPLICATIONS Visit the Escort Memory Systems website (www.ems-rfid.com) for download instructions. Cobalt Dashboard Communicate in real time with one or more readers directly or via Multi-drop network.
COBALT UHF-SERIES APPENDIX B: MODELS & ACCESSORIES CBL-1492-XX Cable: 8-pin, Right-Angle Female M12 / Bare Wires CBL-1493 Connector: 8-pos, Straight Female M12, Field Mountable CBL-1494-01 Cable: M12, 5P, F/Bare Wire Leads, ThinNet, 1M CBL-1495-XX Cable: 7/8-16, 5P F/Bare Wire Leads CBL-1496 Plug: Termination Resistor M12, 5P, F CBL-1497 Plug: Termination Resistor, 7/8-16, 5P, F CBL-1498-02 Cable: M12, 5P, M/Bare Wire Leads, ThinNet, 2M CBL-1513 Cable Assembly: M12, 5-Pin, Male, Reverse Keyed t
COBALT UHF-SERIES WARRANTY WARRANTY Datalogic Automation warrants that all EMS RFID products of its own manufacturing conform to Datalogic Automation’s specifications and are free from defects in material and workmanship when used under normal operating conditions and within the service conditions for which they were furnished.
