OPERATOR'S MANUAL LRP830-Series Long-Range Passive Reader/Writers Manual Revision 3, July, ‘00 Publication #17-1271
Escort Memory Systems Warranty Escort Memory Systems warrants that all products of its own manufacture conform to Escort Memory Systems 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.
TABLE OF CONTENTS 1 GETTING STARTED 1.1 1.2 2 4 Dimensions . . . . . . . . . . . . . . . . . . . . . . . . . 4 RF Range and Orientation . . . . . . . . . . . . . . . . . 7 Mounting Guidelines . . . . . . . . . . . . . . . . . . . 12 Guidelines . . . . . . . . . . . . . . . . . . . . . . . . . 13 POWER AND ELECTRICAL INTERFACE 3.1 3.2 3.3 3.4 3.5 3.6 3.7 3.8 3.9 4 Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 1 Unpacking and Inspection . . . . . . . . . . . . . . . . .
5 MENU CONFIGURATION 5.1 5.2 5.3 5.4 5.5 6 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . RFID INTERFACE 6.1 6.2 6.3 6.4 iv How to Enter Menu Configuration Set-up Operating Parameters . . . Set COM1 Parameters. . . . . . . Set COM2 Parameters. . . . . . .
6.5 6.6 ABxS Command 88 (88H): Tag Search All . . . . . . . 74 ABxS Command 89 (89H): EAS Set/Reset All. . . . . . 75 ABxS Command 8A (8AH): EAS Start/Stop . . . . . . . 76 ABxS Command 8D (8DH): Continuous Read All . . . . 78 ABxS Command 8E (8EH): Memory Lock All. . . . . . 80 ABxS Command 94 (94H): SN Fill . . . . . . . . . . . . 82 ABxS Command 95 (95H): SN Block Read . . . . . . 84 ABxS Command 96 (96H): SN Block Write . . . . . . . 86 ABxS Command 97 (97H): SN Block Read All . . . . .
7 LRP830 DEVICENET INTERFACE 7.1 7.2 7.2.1 7.2.2 7.2.3 7.2.4 7.2.5 7.2.6 7.2.7 7.2.8 7.2.9 vi Introduction . . . . . . . . . . . . . . . . . . . . Scan Rates . . . . . . . . . . . . . . . . . . . . . COM1 LED Indicator . . . . . . . . . . . . . . . DeviceNet Interface . . . . . . . . . . . . . . . . Interface Board Monitor Mode . . . . . . . . . . Enter Interface Board Monitor . . . . . . . . . . . Downloading Firmware to the Interface Board . . Downloading with the EC Emulation Program . .
A SPECIFICATIONS 165 B MODELS AND ACCESSORIES 166 C ASCII CHART 168 D LRP830 DEMONSTRATION 170 Before You Begin . . . . . . . . . . . . . . . . . . . . 170 Using DNSW32 or DNSW16 . . . . . . . . . . . . . . 171 E DEVICENET PROTOCOL EXAMPLES Header Device Type Protocol . . . . . . Header Format . . . . . . . . . . . . . . Header Device Type Command Protocol Calculating Message Size . . . . . . . . Copyright © 2000 Escort Memory Systems LRP830-Series Long-Range Passive Reader/Writer 178 . . .
NOTICE This equipment has been tested and found to comply with the limits for a Class B digital device, pursuant to Part 15 of the FCC Rules. These limits are designed to provide reasonable protection against harmful interference in a residential installation. This equipment generates, uses and can radiate radio frequency energy and, if not installed and used in accordance with the instructions, may cause harmful interference to radio communications.
1 GETTING STARTED 1.1 Introduction Escort Memory Systems' passive read/write system is a complete family of field-proven read/write Radio-Frequency Identification products. The system consists of RFID tags, reader/writers, antennas, controllers, bus interfaces, and ancillary equipment. Tags can be attached to a product or its carrier and act as an electronic identifier, job sheet, portable database, or manifest.
The LRP830 supports the industrial bus protocol DeviceNet. The LRP830 is encased in a NEMA4 enclosure and features two serial ports, 4 optoisolated inputs, 4 opto-isolated outputs. The LRP830-04 is equipped with an antenna designed for conveyor mounting and the LRP830-08 features a rectangular plate antenna. The COM1 serial port is used to receive commands from the host and to send the data back. The LRP830 COM1 can be configured either as a DeviceNet, RS232, or RS422 interface.
1.2 Unpacking and Inspection Unpack the LRP830 and documentation and retain the original shipping carton and packing material in case any items need to be returned. Inspect each item carefully for evidence of damage. If any item appears to be damaged, notify your distributor immediately.
2 MECHANICAL SPECIFICATIONS 2.1 Dimensions Figure 1 gives the dimensions for the LRP830. Figures 2-3 show the dimensions of the 04 and 08 remote antennas.
inches mm Figure 2 — LRP-04 Conveyor-Mount Antenna Copyright © 2000 Escort Memory Systems LRP830-Series Long-Range Passive Reader/Writer 5
inches mm Figure 3 — LRP-08 Antenna Dimensions 6 Copyright © 2000 Escort Memory Systems LRP830-Series Long-Range Passive Reader/Writer
2.2 RF Range and Orientation Figure 4 shows the correct tag orientation as it passes the antenna. Figures 5-7 show the RF fields of the LRP830-04 and LRP830-08 antennas. Tables 1- 3 give the typical and guaranteed ranges of the LRP series tags.
Table 1 — Antenna to Tag Ranges, LRP-04 Antenna with Metal* Tag Typical Range (Z) inches/mm Guaranteed Range inches/mm LRP125(HT) 2.50/64 2.00/51 LRP250(HT) 6.75/171 6.00/152 LRP250HT-FLX 6.75/171 6.00/152 LRP-L5555 6.75/171 6.00/152 LRP-L2666 5.75/146 5.00/127 LRP-L4982 8.00/203 7.00/178 LRP-L90140 9.00/229 8.00/203 LRP-P125 2.50/64 2.00/51 LRP-P3858 6.00/152 5.00/127 LRP-P5050 7.00/178 6.
Figure 6 — End View of RF Field, LRP-04 Antenna, Metal Copyright © 2000 Escort Memory Systems LRP830-Series Long-Range Passive Reader/Writer 9
Table 2 — Antenna to Tag Ranges, LRP-40 Antenna, No Metal* Tag Typical Range (Z) inches/mm Guaranteed Range inches/mm LRP125(HT) 3.00/76 2.25/57 LRP250(HT) 8.50/216 7.50/191 LRP250HT-FLX 8.50/216 7.50/191 LRP-L5555 8.50/216 7.50/191 LRP-L2666 7.00/178 6.00/152 LRP-L4982 10.00/254 9.00/229 LRP-L90140 12.00/305 11.00/279 LRP-P125 3.00/76 2.25/57 LRP-P33858 7.50/190 6.50/165 LRP-P5050 8.50/216 7.50/191 *These ranges calculated with no metal near the antenna.
Figure 8 — Side View of RF Field, LRP-08 Antenna, No Metal Table 3 — Antenna to Tag Ranges, LRP-08 Antenna, No Metal Tag Typical Range (Z) inches/mm Guaranteed Range inches/mm LRP125(HT) 8.00/203 7.00/178 LRP250(HT) 17.00/432 15.00/381 LRP250HT-FLX 17.00/432 15.00/381 LRP-L5555 17.00/432 15.00/381 LRP-L2666 16.00/406 13.00/330 LRP-L4982 20.00/508 18.00/457 LRP-L90140 25.00/635 22.00/559 LRP-P125 8.00/203 7.00/178 LRP-P3858 16.00/406 14.00/355 LRP-5050 17.00/432 15.
2.3 Mounting Guidelines Electromagnetic radiation and metal affect the range of the LRP830. Mount the LRP830 and antenna to minimize the impact of these factors. The RF field of the antenna can also cause errors when antennas are spaced too closely together. Do not position adjacent antennas closer than 2 meters from each other. The remote antennas for the LRP830 have a cable length 2 meters. Surrounding the antenna with metal will greatly reduce the reading range of the antenna.
Special mounting instructions must be followed to get optimal read/write performance from the LRP830-08 antenna. Mount the antenna with a minimum 5.90" (150mm) spacing from any metal to the back or sides of the antenna, as shown in Figure 10. Figure 10 — LRP830-08 Antenna Mounting Guidelines n Isolate the LRP830 and antenna from electromagnetic radiation. n Avoid surrounding LRP830 and remote antenna with metal. n Maintain at least 2 meters minimum spacing between adjacent LRP830s or antennas.
3 POWER AND ELECTRICAL INTERFACE 3.1 Connector Panel Figure 11 shows the LRP connectors, LEDs and connector panel. Unused connectors can be sealed with optional connector caps. Please see Appendix B for ordering information.
3.2 Power Connector Figure 12 shows the power connector pin designations. Figure 12 — Power Connector 3.3 COM1/COM2 Connector Figure 13 shows the connector pin designations for the COM port connections.
Serial Communications Cabling Escort Memory Systems recommends that you use Belden cables 3082A (trunkline) or 3084A (dropline) for RS485/RS422 communications. Use Belden cable 9941 for RS232 communications. More information on Belden cables can be found on their web site at www.belden.com. 3.4 DeviceNet Connector Figure 14 shows the connections for the DeviceNet connector.
3.5 Input Connector Figure 15 shows the Input Connector pin designations. Figure 15 — Input Connector Pinouts 3.6 Output Connector Figure 16 shows the Output Connector pin designations.
3.7 Digital I/O Wiring Both the Digital Inputs and Digital Outputs are optically isolated circuits with no common path between any channel terminal and another channel, or between any channel and the LRP830 power. Because they are independent and floating, the external wiring controls their use. The inputs can be configured for sensors with a PNP or NPN output. The outputs can be configured in a Sourcing or Sinking configuration.
Figure 17 — Input from Sourcing Contact Figure 17 shows the switch on the high side with the low side grounded. As this is a "Dry" contact (the current is limited to 15 mA) a high quality sealed switch should be used. Figure 18 — Input from Sinking Contact Figure 18 shows a switch connected on the low side with the high side connected to the positive supply. This also requires a high quality sealed contact.
Figure 19 — Input from NPN Sensor Figure 19 shows an Open Collector NPN output from a photosensor switching to ground. It can be wired as a sinking or low-side contact. Figure 20 — Input from PNP Sensor Figure 20 shows an Open Collector PNP output from a photosensor switches to the positive supply. It can be wired as a sourcing or high-side contact.
Figure 21 — Sourcing Output "Contact" Figure 21 shows a relay connected as a current sourcing "Contact." The relay is grounded and the +OUT terminal goes to the positive supply. The diode across the relay coil is essential to protect the output circuit and reduce noise along the wiring. It should be connected at the relay to minimize the length of wiring that could radiate noise. A 1N4001 or similar diode may be used.
Figure 23 — Sinking Output LED Driver In Figure 23, the LED and current limiting resistor are in series between the positive supply and the +OUT terminal. The -OUT terminal is grounded. The resistor in series with the LED sets the forward current. 1.2K will provide 20 mA LED current when run from 24 Vdc. Figure 24 — Output to TTL or CMOS In Figure 24 the output acts as an Open Collector. This will provide a TTL or CMOS compatible signal when a 1K to 10K pull-up to +5 Vdc (the logic supply) is used.
3.8 Power Requirement The LRP830 power supply requirement are: n 18 to 30Vdc n 31W maximum power consumption. The maximum current consumption at 24Vdc is 1.3 A. Power Options There are three options for powering the LRP830: n Powered from the DeviceNet Bus (default) This is the default configuration for powering the LRP830. If the power available over your DeviceNet network is not sufficient to power the LRP830, use one of the following methods.
Power from the DeviceNet Bus By default, the LRP830 is configured to run with power supplied by the network. In this mode, there is no galvanic isolation between the DeviceNet wires and the LRP830, and there is no need for a separate power supply. If you choose to power the LRP830 form the DeviceNet bus, you do not need to make any internal changes to cables and jumpers. Wire power according to the pinouts given for the DeviceNet connector in Figure 14, page 16.
3. The DeviceNet cable, labeled assembly 10-3116, must then exchange places with the power cable, moving from J9 to J7. 4. Referring to Figure 26, locate jumper J1 and move the shunt from pins 4 and 3 to pins 2 and 1. 5. Close the LRP830 and connect a separate +24V power supply to the external power connector shown in Figure 12, page 15.
Power from the DeviceNet bus and from an external power supply When the LRP is powered from both sources, the LRP830 will be opto-isolated from the DeviceNet bus. The LRP830 contains components sensitive to electro-static discharge. Take proper grounding precautions before opening the LRP830. To power the LRP830 from an external supply and the DeviceNet bus: 1. Open the LPR820 by loosening the four captive screws that secure the cover. 2.
3.9 LED Indicators The LRP830 has 16 LEDs indicating status of the LRP830 Reader/Writer, interface communications, and I/O status.
Table 4 shows these LEDs and their meaning. Table 4 — LED Indicators LED Color Indicates PWR red The LRP830 is receiving power RF green RF Data Transfer ANT red Antenna on and tag in field ERROR Red Unsuccessful RF command (.5 sec. flash) Entering Download Mode via DIP switch 5 (4 flashes) CONFIG green Successful RF command - 1 .5 sec.
4 SERIAL AND BUS COMMUNICATIONS 4.1 Serial Interfaces The LRP830 has RS232 and RS422 available on the COM1 serial port. COM2 is configured for RS232 communications and is reserved for downloading programs to the LRP830 and for setting up the configuration parameters. Both RS232 and RS422 interfaces are opto-isolated. The RS422 interface is specially suitable for long cable, noisy environment links.
Digital Board DIP Switch The digital board is mounted inside the top of the LRP830 enclosure. The first 5 switches of the main board sets the COM1 baud rate, electrical interface, and the download options for COM2. Switches 6, 7 and 8 are not used and should remain OFF. When switch 1 and 2 are both set ON, the baud rate is set via the Configuration Menu.
NOTE: DIP switch 4 must be in the default ON position for the DeviceNet interface to function. Table 5 Main Board DIP Switch Settings Baud rate SW 1 Download/ Restore Defaults Interface SW 2 SW 3 SW 4 SW 5 Settings 9600 ON ON 19200 ON 38400 ON Set from Configuration Menu RS232 ON ON RS422 ON DeviceNet ON Reserved Disabled ON Enabled Download/ Restore defaults Switches 6 through 8 are reserved and must be in the OFF position.
4.2 Bus Interfaces The COM1 serial port, beside the RS232 or RS422 options, can be configured as a DeviceNet interface. The following bus parameters are set by the DIP switches found on the Interface Board.
DeviceNet Interface Board DIP Switch S1 is an eight position DIP switch. Switches 1 to 6 set the DeviceNet Node address, switches 6 and 7 are reserved and switch 8 sets the bus rate. Table 6 shows these settings.
Table 5 — DeviceNet DIP Switch Settings (cont.
5 MENU CONFIGURATION The LRP830 feature a menu-driven program designed to give convenient access to the serial parameters, restore defaults or change operating modes. 5.1 How to Enter Menu Configuration Begin by connecting the COM2 port to your PC host (see table below) and running EC that is available on the diskette or from Escort Memory Systems’ Web site at www.ems-rfid.com.
To enter the Main Board configuration menu, cycle power or press the reset switch, and then press CTRL-D within the first seven seconds of the initialization. The LRP830 will enter the Configuration Menu. As the LRP830 starts the Configuration program, both the RF and CONFIG LEDs will flash. The Main Board Configuration menu will display with the current software version number together with the DSP firmware version. ****************************************************** LRP830 Standard Program Software V1.
The following sub-menus are presented here in their entirety. Actually the menus will presented one option at time, advancing as you enter selections. Some options shown are dependent on earlier selections. Set COM1 Parameters Selecting 1 from the above menu will present the following display for the COM1 parameters. These settings are valid only if you are not using the DeviceNet Interfaces (e.g. DIP switch 4 is in the OFF position). Enter the appropriate number at each prompt.
*** Set Operating Mode *** Command Protocol? [0] ABx Standard* [1] ABx Fast [2] ABx ASCII Checksum? [0] Disabled* [1] Enabled Power up in Continuous Read Mode? [0] NO [1] Single Tag [2] Multiple Tag Start Address (0 to 47) Length (1 to 48) Delay Between Duplicate Decodes (0 to 60) Raw Read Response? [0] NO [1] CR terminate [2] CR/LF terminate Save Changes to EEPROM? [0] No [1] Yes Command Protocol? The LRP830 offers three modes for the transfer of data and commands.
Start Address (0-47) Enter the tag address where you want the read to begin. Length (1-48) Enter the length of the read you wish the LRP830 to perform. Make certain that the length value does not exceed the number of possible addresses following the starting tag address. Entering a read length of 0 will disable Continuous Read Mode. Delay Between Identical Decodes (0-60) The Delay Between Identical Decodes parameters can have a value of 0 to 60 seconds.
Return to Main Menu When you have completed your configuration, entering 5 will return you to the initial menu. Unsaved changes will be effective until the LRP830 is reset. Saved changes will be loaded automatically the next time the LRP830 is reset. 5.3 Download New Program Before attempting to download new firmware to the LRP830 main board, read the instructions provided in a readme.txt file on the update diskette.
fore downloading another version of software, display and record the current configuration settings. Then download the new software version. Set switch 5 (on the main board) on and apply power to initialize the configuration parameters to their default states. When the LEDs stop flashing, turn Switch 5 to Off and press the reset switch. Enter the Configuration Menu and re-enter any non-default configuration parameters. When you select 3 from the Main Menu, the LRP830 will prompt you to begin the download.
6 RFID INTERFACE 6.1 Introduction The LRP830 offer three possible command protocols: ABx Standard, ABx Fast and ABx ASCII. The ABx Standard format is word-based and is compatible with most existing RFID systems by Escort Memory Systems. The ABx Fast protocol is a byte-based packet structure that permits command execution with fewer total bytes transferred. The ABx ASCII protocol is also a byte-based format that permits the execution of RFID commands using a seven-bit ASCII character set.
NOTE: The delay between the characters of the command packet the LRP830 cannot be longer than 200 ms.
DeviceNet and Anticollision ABx Limitations The LRP830 does not support the following “All” commands in multiple tag-in-field mode (i.e. Anticollision Index is not 0) over a DeviceNet interface: Command Number Command 84H Fill Tag All 85H Block Read All 86H Block Write All 87H Read Tag SN All 88H Tag Search All 8DH Continuous Read All 97H SN Block Read All The entire command set is available for point-to-point serial communications.
6.2 ABx Error Codes Non-Anticollision Error Codes The LRP830 will return an error if it encounters a fault during operation. Table 7 lists the possible error codes in Hexadecimal format.
ABx Fast The format of the error response is shown below. Field Bytes Contents Header 02H Response Size 00H 02H 02H Error Flag FFH Error Code XXH Checksum XXH Terminators 03H A Block Write fail error message would appear as: 0202 0002 FF06 F803H. ABx ASCII The format of the error response is shown below.
Anticollision Status Byte When the anticollision commands encounter a fault condition they indicate the set a bit in a STATUS byte returned in the response. The format of the response is otherwise the same as a successful response.
6.3 Anticollision Commands Family Interrogation The anticollision commands always have a Family ID and an Anticollision Index as parameters. These parameters manage the read/writes when multiple tags are in the same reading field. The Family ID and Anticollision Index can be used separately or together. If the Family ID is zero, that feature is disabled, if the Anticollision Index is zero, this feature (and multiple tag-in-field) is disabled as well.
Anticollision Index The Anticollision Index controls the tag reading algorithm to achieve the fastest reading speed for the number of tags expected in the reading field at any given moment. It also can disable the multiple tag-in-field feature when set to 0. The Anticollision Index should be set in relation to the maximum number of tags possibly present in the reading field at one time. Setting the Anticollision Index higher increases the number of tags that will be expected to be read in the field.
The Anticollision Commands return a successful response whenever the operation has successfully been completed on at least 1 tag. They will return an Error Response when no tag, as permitted by the Family ID and Anticollision Index, can be found in the antenna field. Note also that all the start addresses, byte lengths and packet sizes are expressed in 2 byte words, in order to be compatible with the HMS commands and to allow future developments.
6.4 6.3 ABx Standard Protocol The ABx standard is a binary protocol, word (2-byte) oriented, so the syntax table reports the Most Significant Byte (MSB) and the Least Significant Byte (LSB). In the serial transmission, the MSB is transmitted first. ABxS Command 4 (04H): Fill Tag DESCRIPTION Fill an RFID tag with a one byte value over multiple contiguous addresses. DISCUSSION This command is commonly used to clear an RFID tag's memory.
EXAMPLE Writes 'A' (41H) to the tag starting at address 0005H for the following next consecutive 10 bytes. A timeout of 2 seconds (07D0H = 2000 x 1 msec increments) is set for the completion of the configuration.
ABxS Command 5 (05H): Block Read DESCRIPTION Read a block of data from an RFID tag. DISCUSSION This command is used to read segments of data from contiguous areas of tag memory. It is capable of handling up to 48 bytes of data transferred to the host with one command. The timeout value is given in 1 msec increments and can have a value of 1EH to FFFEH (65,534 ms). When the timeout is set to 0, the LRP830 will return a syntax error.
EXAMPLE: Reads 8 bytes of data from the tag starting at address 0001H. A timeout of 2 seconds (07D0H = 2000 x 1 msec increments) is set for the completion of the Block Read.
ABxS Command 6 (06H): Block Write DESCRIPTION Write a block of data to an RFID tag. DISCUSSION This command is used to write segments of data to contiguous areas of tag memory. It is capable of transferring up to 48 bytes of data transferred from the Host with one command. The timeout value is given in 1 msec increments and can have a value of 1EH to FFFEH (65,534 ms). When the timeout is set to 0, the LRP830 will return a syntax error.
EXAMPLE: Writes 4 bytes of data to the tag starting at address 0020H. A timeout of 2 seconds (07D0H = 2000 x 1 msec increments) is set for the completion of the Block Write.
ABxS Command 7 (07H): Read Tag Serial Number DESCRIPTION Retrieve the eight-byte tag serial number. DISCUSSION Each LRP tag has an unique (264 possible numbers) serial number. This number can not be changed and is not part of the 48 available data bytes. Tag ID will be return in the LSB only, with the MSB as 00H.
ABxS Command 8 (08H): Tag Search DESCRIPTION Check to see if there is an RFID tag in the LRP830 field. DISCUSSION This command will activate LRP830 to "look" for a tag in the RF field. If the LRP830 finds a tag it will return a command echo to the host. The timeout value is given in 1 msec increments and can have a value of 1EH to FFFEH (65,534 ms). When the timeout is set to 0, the LRP830 will return a syntax error. If no tag is present, it will return an error message. See Section 6.
ABxS Command D (0DH): Continuous Block Read DESCRIPTION When in Continuous Block Read mode, the LRP830 sends block reads continuously to any tag in range of the antenna. When a tag enters the RF field, it is read and the data passed to the host computer. The LRP830 continues to read the tag but will not send the same data to the host until the tag has been outside the RF field for a specified time period.
The command is formatted as follows. Field Remarks Command Command number in hex preceded by AAH Start Address 2 byte value for the start address in the tag Read Length 2 byte value for the block read length Delay Between Identical Decodes Time the tag must be out of the antenna range before the LRP830 will transmit data again from that tag. Value is expressed in 1 second units.
To exit Continuous Block Read mode, Send the command with the read length variable set to 0 as shown below. The value of the other variables are not considered.
ABxS Command 10 (10H): Set Output DESCRIPTION Set the levels of the output lines and output LEDs "A" through "D." DISCUSSION This command uses bit logic to set the levels of the digital output lines. The four least significant bit toggle the output levels; 1 = ON and 0 = OFF. The following chart shows the hex values for all output high combinations. To reset all output, issue the command with 00H in the second word.
EXAMPLE The following example sets Output B only and resets A, C, and D.
ABxS Command 11 (11H): Input Status DESCRIPTION Retrieves the input line levels. DISCUSSION This command uses bit logic to monitor the levels of the digital input lines. The four least significant bit display the output levels; 1 = ON and 0 = OFF. The following chart shows the hex values for all input conditions that can be returned in word 2 of the response.
EXAMPLE The following example shows only Input B is ON.
ABxS Command 84 (84H): Fill Tag All DESCRIPTION Fill all RFID tags-in-field or all tags in the same family with a one byte value over multiple contiguous addresses. DISCUSSION This command is commonly used to clear an RFID tag's memory. It writes a one byte value repetitively across a specified range of tag addresses. All tags present in the antenna field with the specified Family ID will be affected by this command. The fill function requires one data value byte, a starting address, and a fill length.
A response to a successful command will follow this form. Field Remarks Command Echo Command number in hex preceded by AAH Number of Tags filled Number of tags found in the field and filled Command Status One byte Error status Message Terminator FFFFH EXAMPLE Writes 'A' (41H) to all tags of family 01H, starting at tag address 0005H for the following next consecutive 40 bytes, with four to eight tags expected in the field.
ABxS Command 85 (85H): Block Read All DESCRIPTION Read a block of data from all RFID tags-in-field or those with the specified Family ID. DISCUSSION This command is used to read segments of data from contiguous areas of tag memory. It is capable of handling up to 48 bytes of data transferred to the host with one command. The timeout value is given in 1 msec increments and can have a value of 1EH to FFFEH (65,534 ms). When the timeout is set to 0, the LRP830 will return a syntax error 21H.
EXAMPLE: Reads 4 bytes of data from the tag starting at address 0001H. A timeout of 2 seconds (07D0H = 2000 x 1 msec increments) is set for the completion of the Block Read All. The Family ID byte is set to zero so all tags will be read. The Anticollision Index is set to 2 so 4 to 8 tags will be expected. Three tags respond with read data.
ABxS Command 86 (86H): Block Write All DESCRIPTION Write a block of data to all RFID tags or all tags with the same Family ID. DISCUSSION This command is used to write segments of data to contiguous areas of tag memory. It is capable of transferring up to 48 bytes of data transferred from the Host with one command. The timeout value is given in 1 msec increments and can have a value of 1EH to FFFEH (65,534 ms). When the timeout is set to 0, the LRP830 will return a syntax error.
EXAMPLE: Writes 4 bytes of data, starting at address 0001H. A timeout of 2 seconds (07D0H = 2000 x 1 msec increments) is set for the completion of the Block Write. The Family ID byte is set to 2, so all tags with Family ID of 2 will be written to (four tags in this example). The Anticollision Index is set to 2 so 4 to 8 tags are expected in the field.
ABxS Command 87 (87H): Read Tag SN All DESCRIPTION This command retrieves the 8-byte tag serial number from all tags or those with the specified Family ID number. DISCUSSION Each LRP tag has an unique (264 possible numbers) serial number. This number cannot be changed and is not part of the 48 available data bytes. The Tag SN is returned in the LSB only, with the MSB as 00H. The timeout value is given in 1 msec increments and can have a value of 1EH to FFFEH (65,534 ms).
EXAMPLE: This example will read the 8-byte serial number from Tag Family 2. The Anticollision Index of 2 sets the number of expected tags at 4-8. In this example the SN for the found tag is 1E6E3CD200000000H in hexadecimal. Multiple tags will return a complete response packet for each tag.
ABxS Command 88 (88H): Tag Search All DESCRIPTION Check to see if there is an RFID tag in the LRP830 field. DISCUSSION This command will activate LRP830 to "look" for a tag in the RF field. As soon as the LRP830 finds a tag it will return a command echo to the host. The timeout value is given in 1 msec increments and can have a value of 1EH to FFFEH (65,534 ms). When the timeout is set to 0, the LRP830 will return a syntax error. If no tag is present, it will return an error message. See Section 6.
ABxS Command 89 (89H): EAS Set/Reset All DESCRIPTION Sets or resets the EAS feature in tag memory for all tags in range, and of the specified Family, when the command is issued. DESCRIPTION The commands contains a 1 byte parameter that enables or disables the EAS feature in tags that receive the command. When the EAS Set/Reset All command is issued, the LRP830 responds with the number of tags affected (Ntag). If the LRP830 returns a 0 for Ntag it means that no tags were set or reset by the command.
ABxS Command 8A (8AH): EAS Start/Stop DESCRIPTION If are using the EAS feature in your application, the EAS Start/Stop command enters and exits the LRP830 from EAS mode. DISCUSSION When EAS mode has been started, the LRP830 will return a response when one or more EAS-enabled tags have entered the antenna field. It will send a second response when all EAS-enabled tags have exited the field. The command contains a control byte that toggles EAS: 1 = start, 0 = stop.
EXAMPLE This example starts EAS mode. Three responses follow. The first is a command acknowledgment. The LRP830 sends the second when the first EAS-enabled tag enters the field, A third response is sent when field is clear of EAS-enabled tags. Family ID is set to 0 so that any EAS-enabled tag will trigger responses.
ABxS Command 8D (8DH): Continuous Read All DESCRIPTION Starts and stops Continuous Read All mode for multiple tags. DISCUSSION Continuous Read All mode is set by the length byte. To start Continuous Read All mode, send the command with valid, non-zero value for the length of the read (1-48). Stop the mode by sending the command with a read length of 0. While in this mode, any other command can be issued and it will be handled properly.
EXAMPLE Reads 4 bytes of data from the tag starting at address 0001H. The Family ID byte is set to zero so all tags will be read. The Anticollision Index is set to 2 so 4 to 8 tags will be expected. The Tag Delay is set to 20 (14H). Three tags respond with read data.
ABxS Command 8E (8EH): Memory Lock All DESCRIPTION This command “locks” tag addresses in four byte blocks. Once bytes are locked, they can not be unlocked. DISCUSSION The memory can be locked only in 4-byte blocks. The command passes a two byte word with bits assigned to 4-byte blocks that can be locked. Remaining bits can lock the EAS feature and the lock configuration itself.
If a bit in the configuration word is set, then the corresponding block in the tag is locked when the command is issued. If a bit in the configuration word is cleared (0), then the corresponding block will not change. Once locked, a block can not be unlocked. The command is formatted as shown below.
ABxS Command 94 (94H): SN Fill DESCRIPTION Fills only the RFID tag specified by serial number with a one byte value over multiple contiguous addresses. DISCUSSION This command is commonly used to clear an RFID tag's memory. It writes a one byte value repetitively across a specified range of tag addresses. Only the tag with the specified serial number will be affected by this command. The LRP830 will return a response after the successful fill operation or when the timeout expires.
A response to a successful command will follow this form. Field Remarks Command Echo Command number in hex preceded by AAH Number of Tags filled 0 = tag not found, 1 = tag filled Command Status One byte Error status Message Terminator FFFFH EXAMPLE Writes 'A' (41H) to a single tag, starting at tag address 0005H for the following next consecutive 40 bytes. The Family ID is turned off and the Anticollision Index is set to expect 2-4 tags.
ABxS Command 95 (95H): SN Block Read DESCRIPTION Read a block of data from a specified RFID tag. DISCUSSION This command is used to read segments of data from contiguous areas of tag memory. It is capable of handling up to 48 bytes of data transferred to the host with one command if there is no tag Family ID. The timeout value is given in 1 msec increments and can have a value of 1EH to FFFEH (65,534 ms). When the timeout is set to 0, the LRP830 will return a syntax error.
EXAMPLE: Reads 4 bytes of data from the tag specified by serial number starting at address 0001H. A timeout of 2 seconds (07D0H = 2000 x 1 msec increments) is set for the completion of the SN Block Read. The Family ID byte is set to zero. The Anticollision Index is set to 2, expecting 4-8 tags in the field.
ABxS Command 96 (96H): SN Block Write DESCRIPTION Write a block of data to a single RFID tag specified by its serial number. DISCUSSION This command is used to write segments of data to contiguous areas of tag memory. It is capable of transferring up to 48 bytes of data transferred from the Host with one command. The timeout value is given in 1 msec increments and can have a value of 1EH to FFFEH (65,534 ms). When the timeout is set to 0, the LRP830 will return a syntax error.
EXAMPLE: Writes 4 bytes of data, starting at address 0001H. A timeout of 2 seconds (07D0H = 2000 x 1 msec increments) is set for the completion of the Block Write. The Family ID byte is set to 0 and the Anticollision Index is set to 2 for this example.
ABxS Command 97 (97H): SN Block Read All DESCRIPTION Read a block of data from all RFID tags-in-field or those with the specified Family ID. Return the serial number of the tags read, along with tag data. DISCUSSION This command is used to read segments of data from contiguous areas of tag memory. It is capable of handling up to 48 bytes of data transferred to the host with one command if there is no tag family ID.
EXAMPLE: Reads 2 bytes of data from the tag starting at address 0001H. A timeout of 2 seconds (07D0H = 2000 x 1 msec increments) is set for the completion of the SN Block Read All. The Family ID byte is set to zero so all tags will be read. The Anticollision Index is set to 2 so 4-8 tags are expected. Two tags respond with read data.
6.5 ABx Fast Fast Protocol Protocol 6.4 ABx The difference from the standard ABx are: n The command/response packet contains the packet size n You can include a checksum in the command n The headers and terminator are ASCII characters n Since ABx Fast is a binary protocol, the Xon/Xoff handshake cannot be used. ABx Command Packet Structure: The command protocol is based on the following minimal packet structure.
If the LRP830 Reader/Writer encounters a fault it will respond with the following: Field Number of Bytes Content Header 2 (02H, 02H) Response Size 2 Packet length in bytes excluding the header, packet size, checksum and terminator bytes. (02H in this case) Error Flag 1 FFH Error Code 1 Hex error code, see Table 7 for details (Checksum) 1 Optional Checksum Terminator 1 (03H) n The Header and Terminator are always STX-STX and ETX respectively.
Checksum Since the DeviceNet protocol has its own data validation, it is not necessary to use the checksum option when sending ABxF commands over the DeviceNet bus. The optional checksum must be enabled from the operating mode menu to be available. The checksum is calculated by adding all the byte values in the packet (less the values in the header, checksum if present, and terminator), discarding byte overflow and subtracting the byte sum from FFH.
ABxF Command 4 (04H): Fill Tag DESCRIPTION Fill an RFID tag with a one byte value over multiple contiguous addresses. DISCUSSION This command is commonly used to clear an RFID tag's memory. It writes a one byte value repetitively across a specified range of tag addresses. The fill function requires one data value byte, a starting address, and a fill length. It will fill the tag with the data value byte, starting at the specified start address for the specified number of consecutive bytes.
EXAMPLE Writes 'A' (41H) to the tag starting at address 0005H for the following next consecutive 40 bytes. A timeout of 2 seconds (07D0H = 2000 x 1 msec increments) is set for the completion of the configuration.
ABxF Command 5 (05H): Block Read DESCRIPTION Read a block of data from an RFID tag. DISCUSSION This command is used to read segments of data from contiguous areas of tag memory. It is capable of handling up to 48 bytes of data transferred to the host. The timeout value is given in 1 msec increments and can have a value of 1EH to FFFEH (65,534 ms). When the timeout is set to 0, the LRP830 will return a syntax error.
EXAMPLE: Reads 4 bytes of data from the tag starting at address 0001H. A timeout of 2 seconds (07D0H = 2000 x 1 msec increments) is set for the completion of the Block Read.
ABxF Command 6 (06H): Block Write DESCRIPTION Write a block of data to an RFID tag. DISCUSSION The Block Write command is used to write segments of data to contiguous areas of tag memory. It is capable of handling up to 48 bytes of data transferred to the host. The timeout value is given in 1 msec increments and can have a value of 1EH to FFFEH (65,534 ms). When the timeout is set to 0, the LRP830 will return a syntax error.
EXAMPLE: Writes 4 bytes of data to the tag starting at address 0000H. A timeout of 2 seconds (07D0H = 2000 x 1 msec increments) is set for the completion of the Block Write.
ABxF Command 7 (07H): Read Tag Serial Number DESCRIPTION This command retrieves the 8-byte tag serial number. DISCUSSION Each LRP tag has an unique (264 possible numbers) serial number. This number can not be changed and is not part of the 48 available data bytes. Field Content Header Command Size Packet length in bytes excluding the header, command size, checksum and terminator bytes.
EXAMPLE: This example will wait until a tag is in range and then reads the 8-byte identification number. In this example the SN is 1E6E3DC200000000 in hexadecimal.
ABxF Command 8 (08H): Tag Search DESCRIPTION Check to see if there is an RFID tag in the LRP830 field. DISCUSSION This command will activate the reader/write to "look" for a tag in the RF field. If the LRP830 finds a tag it will return a command echo to the host. The timeout value is given in 1 msec increments and can have a value of 1EH to FFFEH (65,534 ms). When the timeout is set to 0, the LRP830 will return a syntax error. If no tag is present it will return an error message. See Section 6.
ABxF Command D (0DH): Continuous Block Read DESCRIPTION Send block reads continuously to any tag in range of the antenna. When a tag enters the RF field, it is read and the data passed to the host computer. The LRP830 continues to read the tag but will not send the same data to the host until the tag has been outside the RF field for a specified time period. This Delay Between Identical Decodes feature prevents redundant data transmissions when the LRP830 is in Continuous Block Read mode.
The command is formatted as follows. Field Content Header Command Size Command length in bytes excluding the header, command size, checksum and terminator bytes.
The LRP830 will first return an acknowledgment of the command followed by a response containing read data when a tag enters the antenna field.
ABxF Command 10 (10H): Set Output DESCRIPTION Set the levels of the output lines and output LEDs "A" through "D." DISCUSSION This command is used to set the levels of the digital output lines using bit logic. The four least significant bit toggle the output levels; 1 = ON and 0 = OFF. The following chart shows the hex values for all output high combinations. To reset all output, issue the command with 0000H for the Output Pattern byte.
EXAMPLE The following example sets Output B only and resets A, C, and D.
ABxF Command 11 (11H): Input Status DESCRIPTION Retrieves the input line levels. DISCUSSION This command is used to monitor the levels of the digital input lines using bit logic. The four least significant bit display the input levels; 1 = ON and 0 = OFF. The following chart shows all possible conditions that can be returned in the response.
EXAMPLE The following example shows only Input B is ON and A, C, and D are OFF.
ABxF Command 84 (84H): Fill All DESCRIPTION Fill all RFID tags-in-field or all tags in the same family, with a one byte value over multiple contiguous addresses. DISCUSSION This command is commonly used to clear an RFID tag's memory. It writes a one byte value repetitively across a specified range of tag addresses. All tags present in the antenna field with the specified Family ID will be affected by this command. The LRP830 will return a response after the timeout expires.
EXAMPLE Writes 'A' (41H) to all tags with Family ID 03H, starting at address 0005H for the following next consecutive 40 bytes. A timeout of 2 seconds (07D0H = 2000 x 1 msec increments) is set for the completion of the configuration. Four tags are found and filled successfully.
ABxF Command 85 (85H): Block Read All DESCRIPTION Read a block of data from all RFID tags-in-field or all those with the specified Family ID. DISCUSSION This command is used to read segments of data from contiguous areas of tag memory. The timeout value is given in 1 msec increments and can have a value of 1EH to FFFEH (65,534 ms). When the timeout is set to 0, the LRP830 will return a syntax error.
EXAMPLE: Reads 4 bytes of data from tags with Family ID AAH, starting at address 0001H. A timeout of 2 seconds (07D0H = 2000 x 1 msec increments) is set for the completion of the Block Read All. The Tag Family byte is set to zero so all tags will be read. The Anticollision Index is set to 2, expecting 4-8 tags. Two tags respond with data.
ABxF Command 86 (86H): Block Write All DESCRIPTION Write a block of data to an RFID tag. DISCUSSION The Block Write All command is used to write segments of data to contiguous areas of tag memory. The timeout value is given in 1 msec increments and can have a value of 1EH to FFFEH (65,534 ms). When the timeout is set to 0, the LRP830 will return a syntax error. The Block Write All consists of a Family ID, Anticollision Index, a start address followed by the data stream to be written to the RFID tag.
EXAMPLE: Writes 4 bytes of data to the tag starting at address 0000H. A timeout of 2 seconds (07D0H = 2000 x 1 msec increments) is set for the completion of the Block Write All. Family ID is set to 00H so all tags-in-field will be written to. The Anticollision Index is 5, expecting 32-64 tags. Five tags are written to.
ABxF Command 87 (87H): Read Tag SN All DESCRIPTION This command retrieves the 8-byte tag serial number from all tags-in-field or those with the specified Family ID. DISCUSSION Each LRP tag has an unique (264 possible numbers) serial number. This number can not be changed and is not part of the 48 available data bytes. The timeout value is given in 1 msec increments and can have a value of 1EH to FFFEH (65,534 ms). When the timeout is set to 0, the LRP830 will return a syntax error.
EXAMPLE: This example will read the 8-byte serial number from all tags permitted by the Family ID and Anticollision Index. In this example, one tag responds and the serial number is 1E6E3DC200000000 in hexadecimal.
ABxF Command 88 (88H): Tag Search All DESCRIPTION Check to see if there is any RFID tags in the LRP830 antenna field. DISCUSSION This command will activate the LRP830 to "look" for a tag in the RF field. As soon as the LRP830 finds a tag it will return a command echo to the host. The timeout value is given in 1 msec increments and can have a value of 1EH to FFFEH (65,534 ms). When the timeout is set to 0, the LRP830 will return a syntax error. If no tag is present it will return an error message.
EXAMPLE Checks for an RFID tag in the RF field. A timeout of 2 seconds (07D0H = 2000 x 1 msec increments) is set for the completion of the Tag Search All. A tag is found.
ABxF Command 89 (89H): EAS Set/Reset All DESCRIPTION Sets or resets the EAS feature in tag memory for all tags in range when the command is issued. DESCRIPTION The commands contains a 1 byte parameter that enables or disables the EAS feature in tags that receive the command. When the EAS Set/Reset All command is issued, the LRP830 will respond with the number of tags affected. If the LRP830 return a 0 for Ntag it means that no tags were set or reset by the command.
EXAMPLE This example assumes that the tags-in-field are not enabled for the EAS feature. It will enabled the EAS feature for tags with Family ID 09H. The Anticollision Index is 2, so 4-8 tags are expected in the field. When the command is issued, 5 tags with Family ID 09H are found and enabled for EAS.
ABxF Command 8A (8AH): EAS Start/Stop DESCRIPTION If are using the EAS feature in your application, the EAS Start/Stop command enters and exits the LRP830 from EAS mode. DISCUSSION When EAS mode has been started, the LRP830 will return a response when one or more EAS-enabled tags have entered the antenna field. It will send a second response when all EAS-enabled tags have exited the field. The command contains a control byte that toggles EAS: 1 = start, 0 = stop.
EXAMPLE This example starts EAS mode. Three responses follow. The first is a command acknowledgment. The LRP830 sends the second when the first EAS-enabled tag enters the field, A third response is sent when field is clear of EAS-enabled tags. Family ID is set to 0 so that any EAS-enabled tag will trigger responses.
When all EAS-enabled tags have left the field, the LRP830 will send the following response.
ABxF Command 8D (8DH): Continuous Read All DESCRIPTION Starts and stops Continuous Read All mode for multiple tags. DISCUSSION Continuous Read All mode is set by the length byte. To start Continuous Read All mode send the command with valid, non-zero value for the length of the read (1-48). Stop the mode by sending the command with a read length of 0. While in this mode, any other command can be issued and it will be handled properly.
EXAMPLE Reads 4 bytes of data from the tag starting at address 0001H. The Family ID byte is set to zero so all tags will be read. The Anticollision Index is set to 1 so 2 to 4 tags will be expected. The Tag Delay is set to 20 (14H). Two tags respond with read data.
After the LRP830 sends the acknowledgment, it will send the read data from the 2 tags.
ABxF Command 8E (8EH): Memory Lock All DESCRIPTION This command “locks” tag addresses in four byte blocks. Once bytes are locked, they can not be unlocked. DISCUSSION The memory can be locked only in 4-byte blocks. The command passes a two byte word with bits assigned to 4-byte blocks that can be locked. Remaining bits can lock the EAS feature and the lock configuration itself.
If a bit in the configuration word is set, then the corresponding block in the tag is locked when the command is issued. If a bit in the configuration word is cleared (0), then the corresponding block will not change. Once locked, a block can not be unlocked. The timeout value is given in 1 msec increments and can have a value of 1EH to FFFEH (65,534 ms). When the timeout is set to 0, the LRP830 will return a syntax error. The command is formatted as shown below.
EXAMPLE This example will lock bytes 0-3 on all tags-in-field with the Family ID of 02H. Two tags are found and locked.
ABxF Command 94 (94H): SN Fill DESCRIPTION Fill an RFID tag, identified by serial number, with a one byte value over multiple contiguous addresses. DISCUSSION This command is commonly used to clear an RFID tag's memory. It writes a one byte value repetitively across a specified range of tag addresses. The SN Fill command requires a specific serial number of the tag to be filled.
EXAMPLE Writes 'A' (41H) to the tag specified by serial number starting at address 0005H for the following next consecutive 4 bytes. A timeout of 2 seconds (07D0H = 2000 x 1 msec increments) is set for the completion of the configuration.
ABxF Command 95 (95H): SN Block Read DESCRIPTION Read a block of data from an RFID tag. DISCUSSION This command is used to read segments of data from contiguous areas of tag memory. The timeout value is given in 1 msec increments and can have a value of 1EH to FFFEH (65,534 ms). When the timeout is set to 0, the LRP830 will return a syntax error. A special error packet is sent if the timeout expires.
EXAMPLE: Reads 2 bytes of data from the tag starting at address 0001H. A timeout of 2 seconds (07D0H = 2000 x 1 msec increments) is set for the completion of the SN Block Read. If the timeout expires before reading a tag the response packet is: 02H 02H 00 03 FF 00 Status 03H.
ABxF Command 96 (96H): SN Block Write DESCRIPTION Write a block of data to an RFID tag identified by its serial number. DISCUSSION The SN Block Write command is used to write segments of data to contiguous areas of tag memory. The timeout value is given in 1 msec increments and can have a value of 1EH to FFFEH (65,534 ms). When the timeout is set to 0, the LRP830 will return a syntax error.
EXAMPLE: Writes 4 bytes of data to the tag starting at address 0000H. A timeout of 2 seconds (07D0H = 2000 x 1 msec increments) is set for the completion of the SN Block Write.
ABxF Command 97 (97H): SN Block Read All DESCRIPTION Read a block of data from all RFID tags-in-field or all those with the specified Family ID. Data will be returned with the serial number of the corresponding tag. DISCUSSION This command is used to read segments of data from contiguous areas of tag memory. It is capable of handling up to 48 bytes of data transferred to the host with one command if there is no tag family ID.
The command is formatted as follows. Field Content Header Command Size Packet length in bytes excluding the header, command size, checksum and terminator bytes. Command 97H Family ID Tag Family ID - 00H = all tags Anticollision Index Number of tags expected Start Address 2-byte value for the starting tag address Block Size 2-byte value for the length of the read in number of bytes Timeout 2-byte timeout value in 1 ms increments (1EH - FFFEH).
EXAMPLE: Reads 4 bytes of data from the tag starting at address 0001H. A timeout of 2 seconds (07D0H = 2000 x 1 msec increments) is set for the completion of the SN Block Read All. The Tag Family byte is set to zero so all tags will be read. Three tags respond with data.
Header/tag 2 02H Response Size 02H 02H Header/End Packet 00H Response Size 00H 0DH 02H 03H Command Code 97H Command Echo FFH SN byte 1/tag 2 ADH Number of tags 03H SN byte 2/tag 2 23H Status byte 08H SN byte 3/tag 2 81H Terminators 03H SN byte 4/tag 2 1DH SN byte 5/tag 2 C3H SN byte 6/tag 2 66H SN byte 7/tag 2 78H SN byte 8/tag 2 21H Data byte 1/ tag 2 52H Data byte 2/tag 2 46H Data byte 3/tag 2 49H Data byte 4/tag 2 44H Terminators
6.6 ABx ASCII ASCII Protocol Protocol 6.5 ABx The ABx ASCII Protocol is based on the ABx Fast protocol. It uses the same headers and terminator (already ASCII characters) and converts the hex value of command and data bytes to printable ASCII (2 digit Hexadecimal notation). In another words, the hex values given in an ABx Fast command are transmitted as separate ASCII characters. Since it is an ASCII protocol, the Xon/Xoff handshake can be used.
If the LRP830 encounters a fault it will respond with the following: Field Number of ASCII Characters Content Header 2 (02H, 02H) Response Size 4 Packet length in bytes excluding the header, response size, checksum and terminator bytes.
Checksum The optional checksum must be enabled from the operating mode menu to be available. The checksum is calculated by adding all the byte values (not the ASCII translation values) in the packet (less the values in the header, checksum if present, and terminator), discarding byte overflow and subtracting the byte sum from FFH. Example ASCII Command Fill Tag This command fills the specified number of cells from the specified start address with the specified value.
The ASCII character string for a fill of 32 bytes, from address 0 with 55H value, timeout 5 sec., follows.
7 LRP830 DEVICENET INTERFACE 7.1 Introduction The LRP830 is compatible with any DeviceNet scanner host that conforms to DeviceNet standards and can process standard DeviceNet fragmentation protocol as defined by the Open DeviceNet Vendor Association (ODVA) in the ODVA DeviceNet specification (see www.odva.org for details.) You may address DeviceNet protocol and scanner questions to "Dr. DeviceNet" at the ODVA Web site.
COM1 LED Indicator The COM1 LED indicates DeviceNet traffic activity. The LED does not indicate network status as defined by ODVA. DeviceNet Interface To use the DeviceNet interface: 1. Set DIP switch 4 on the main board to "1" (ON) to enable DeviceNet communications. 2. Verified default settings of serial port COM2: 9600, N, 8, 1, no flow control for configuration purposes. 7.2 Interface Board Monitor Mode The following Section describes steps required to enter the DeviceNet Interface Board Monitor mode.
4. You must press CTRL-E within 7 seconds to enter the Interface Board Monitor mode from a terminal emulator (EC) connected to COM port 2 (9600, N, 8, 1). If the LRP830 does not receive CTRL-E in the seven second period, it will automatically enter "RUN MODE". 5. Upon entering CTRL-E, wait for the following menu to appear. ———————————————————————————— | HMS/LRP Rd/Wrt Controller with DeviceNet & Serial I/O. | | (c) 2000 Escort Memory Systems, a Datalogic Co.
7.2.1 Downloading Firmware to the Interface Board To download new software to the interface board, select "X" from the Monitor Menu shown above to retain existing configuration settings or "Z" if you wish to overwrite configuration settings with factory defaults. In most cases you will want to retain existing configuration settings and should use the X command to download new firmware.
7.2.2 Downloading with the EC Emulation Program If you are using the terminal emulator "EC" provided by Escort Memory Systems (EMS), do the following from EC to download the new software: 1. Perform ALT-F to enter the file menu. 2. Select "download" from the menu. 3. Select "ASCII" from the pop-up window. 4. Specify the path/name of the hex file provided by Escort Memory Systems. When the download is complete, you will be prompted to reset the LRP830 with the following message: <:-> RESET NOW... 5.
Display Configuration Info To review the current settings enter "I" from the Monitor Menu and you will see a display similar to the following: ————————————————————————————————— | HMS/LRP Rd/Wrt Controller with DeviceNet & Serial I/O. | | (c) 2000 Escort Memory Systems, a Datalogic Co.
7.2.4 Interface Board Configuration Editor Note: the following menu can be attained via "Y" (above) or selecting "E" from the Monitor Menu (above). These are the recommended parameters, however, it is likely that A and/or B (below) may require modification according to customer requirements. <= LRP830 INTERFACE-BOARD CONFIGURATION MENU => Enter Parameter # to Change: ===== Std DeviceNet ===== 90 A. 830 Tx Msg Size (0-254) 90 B. 830 Rx Msg Size (0-254) 0 C. DevNet Protocol (Poll=0,Strobe=1) D.
7.2.5 Edit Configuration Command. To change the LRP830 configuration parameters, enter the "E" command from the Monitor Menu. The Interface Board will display the current values for user-configureable variables. In the following configuration menu, range checking and validation is performed on every input provided by the user. The current value of the item is displayed with each prompt for change. ESC exits to a previous level. The backspace key is supported.
Example The following example shows how the Tx and Rx message sizes are modified from 90 to 48 bytes in length. SELECTION 1-C? (Ctrl-C Exits) a 90 A. 830 Tx Msg Size (0-254). ?>48 Enter Parameter # to Change: ===== Std DeviceNet ===== 48 A. 830 Tx Msg Size (0-254) 90 B. 830 Rx Msg Size (0-254) 0 C. DevNet Protocol (Poll=0,Strobe=1) D. DeviceNet Serial# 04 99 12 34 (hex) ===== LRP830 Specific ===== 2 1. Device Type (GENeric: 0=norm, 1=rev; HDR: 2=n, 3=r) Y 2. ABx separation (Y/N) N 3.
7.2.6 Configuration Parameter Validation <= LRP830 INTERFACE-BOARD CONFIGURATION MENU => Enter Parameter # to Change: ===== Std DeviceNet ===== 90 A. 830 Tx Msg Size (0-254) 90 B. 830 Rx Msg Size (0-254) 0 C. DevNet Protocol (Poll=0,Strobe=1) D. DeviceNet Serial# 04 99 12 34 (hex) ===== LRP830 Specific ===== 2 1. Device Type (GENeric: 0=norm, 1=rev; HDR: 2=n, 3=r) Y 2. ABx separation (Y/N) N 3. Buf Flush Enable (Y/N) 200 4.
7.2.7 Standard DeviceNet Parameters Produce and Consume Sizes Before setting the first two parameters (TxMsgSize and RxMsgSize) you should calculate the optimum consume and produce sizes. The default size is 90 for both TxMsg and RxMsg. The default setting will create a byte offset for the command code byte when using ABx Fast and a word oriented PLC.
Produce size — ABx Fast, 8 Byte Read Generic Description HDR # of bytes Description ABX Non-separated # of bytes Description # of bytes Protocol Header, STX STX 2 Handshake word 2 Handshake word 2 Terminator, 03 1 Protocol Header, STX STX 2 Command Echo 1 Response Size 2 Terminator 03 1 Number of read bytes 8 Command Echo 1 Response Size 2 Optional Checksum 1 Number of read bytes 8 Command Echo 1 Optional Checksum 1 Number of read bytes 8 Optional Checksum 1 Total bytes
Consume size — ABx Fast, 8 Byte Read Generic Description HDR # of bytes Description ABX Non-separated # of bytes Description # of bytes Protocol Header, STX STX 2 Handshake word 2 Handshake word 2 Terminator, 03 1 Protocol Header, STX STX 2 Command Echo 2 Command Size 2 Terminator 03 1 Terminator 03 1 Command 1 Command Size 2 Command Size 2 Start Address 2 Command 1 Command 1 Length 2 Start Address Start Address 2 Timeout 2 Length 8 Length 2 Optional Checksum 1
LRP830 Receive Message Size 90 B. 830 Rx Msg Size (0-254) Size of the DeviceNet poll message command to the LRP830 from the DeviceNet Scanner Host. When "B" is entered from the Configuration Edit menu, the monitor prompts for the LRP830 Transmit Message Size (i.e., DeviceNet I/O consume size). Selection (CTRL-C to exit) ...b 48 B. 830 Rx Msg Size (0-254) ). ?>30 Important Determine the field size in commands and responses before programming this value. Field sizes are protocol dependent.
7.2.8 LRP830 Specific Parameters Device Type 2 1. Device Type (GENeric: 0=norm, 1=rev; HDR: 2=n, 3=r) Device Type specifies whether a handshaking protocol should be used between the DeviceNet Scanner Host and the LRP830. Generic indicates no handshaking protocol (due to asynchronous communication). Messages and responses are repeated in each poll, until the DeviceNet Scanner Host or LRP830 clears its output buffer.
Because ABx Non-separation removes the termination bytes that indicate the end of the message, the programmer must remember how many bytes the command asked for. In the ABx Fast response there is always a checksum byte included in the data array (00H if checksum option is disabled). The ABx Non-separated selection works across all device types (generic & polled) types. A handshake word (2 bytes) is required in the beginning of the command and response of every single device type (generic and polled).
To clear the error bit simply execute a new command. This same bit is used inside the generic mode. All error response codes are the same exact error responses that are given from ABx separated mode. No change in the protocol header or terminator has been made with error responses. Calculations must accommodate the fact that an error could occur, especially if only one byte is being read. All error responses will have a single word still as part of the header.
When the PLC sends the header word with a new number in PLC Word 0 (low byte) will a command be performed. The actual command given in an array must be valid regardless of the protocol (ABx S/ABx F). Generic repeats a command many times faster than the reader can keep up with responses due to the fact that a read request requires more time than the DeviceNet scan rate. See Section 7.2.9 for more information on Generic protocol.
7.2.9 Device Type Protocols. There are two protocols that can be used to transport the ABx RF-ID antenna commands: Generic Device Type and Header Device Type. The Generic Device Type does not contain an extra header for handshaking, and is strictly asynchronous. The DeviceNet Scanner Host repeats a command at each poll until a response is received. The LRP830 repeats each poll response until the LRP830 provides a new command response (or buffer flush occurs, when enabled).
Header Device Type Protocol When "HDR" device type is selected in the LRP830 configuration, the following features are available. A special message header is required, which precedes each ABx command and response. The HDR device type should always be the choice for operational (i.e., non-test) use. The DeviceNet Scanner Host must process every message header word coming from the LRP830. It must also correctly setup a handshake header for every message going out to the LRP830.
the REQ bit set on in the header. In this manner, the LRP830 DeviceNet board only forwards intended commands to the antenna for processing. Generic protocol repeats the same command over and over again until the scanner clears the poll message buffer or places a new command in the buffer. As a result the antenna receives many unintended commands and not every command can be processed.
A SPECIFICATIONS Table 8 — LRP830 Specifications Electrical Supply Voltage Power Consumption 18-30 Vdc 31W (1.3 A @ 24Vdc) Communication RFID Interface Bus Interface COM1 COM2 Inputs Output LRP-Series Passive RFID System DeviceNet RS232/RS422/DeviceNet RS232 Four industrial-level inputs, 4.
B MODELS AND ACCESSORIES Table 9 — Models and Accessories Available Models Part Number Description LRP830-10 Long range, passive controller, RS232, RS422 and DeviceNet/RS485 communications, 4 digital inputs and 4 digital outputs, tunnel antenna LRP830-04 Long range, passive controller, RS232, RS422 and DeviceNet/RS485 communications, 4 digital inputs and 4 digital outputs, conveyor-mount antenna LRP830-08 Long range, passive controller, RS232, RS422 and DeviceNet/RS485 communications, 4 digital inpu
Table 9 — Models and Accessories (cont) Accessories Part Number Description LRP-P125 Passive read/write tag, 25 mm round, PCB, 48 bytes memory LRP-P3858 Passive read/write tag, 38 mm x 58 mm, PCB, 48 bytes memory LRP-P5050 Passive read/write tag, 50 mm x 50 mm, PCB, 48 bytes memory Copyright © 2000 Escort Memory Systems LRP830-Series Long-Range Passive Reader/Writer 167
C ASCII CHART Decimal Hex Character Decimal Hex Character 000 00 NUL 032 20 (space) 001 01 SOH 033 21 ! 002 02 STX 034 22 '' 003 03 ETX 035 23 # 004 04 EOT 036 24 $ 005 05 ENQ 037 25 % 006 06 ACK 038 26 & 007 07 BEL 039 27 ` 008 08 BS 040 28 ( 009 09 HT 041 29 ) 010 0A LF 042 2A * 011 0B VT 043 2B ++ 012 0C FF 044 2C ' 013 0D CR 045 2D - 014 0E SO 046 2E .
Decimal Hex Character Decimal Hex Character 064 40 @ 096 60 ` 065 41 A 097 61 a 066 42 B 098 62 b 067 43 C 099 63 c 068 44 D 100 64 d 069 45 E 101 65 e 070 46 F 102 66 f 071 47 G 103 67 g 072 48 H 104 68 h 073 49 I 105 69 i 074 4A J 106 6A j 075 4B K 107 6B k 076 4C L 108 6C l 077 4D M 109 6D m 078 4E N 110 6E n 079 4F O 111 6F o 080 50 P 112 70 p 081 51 Q 113 71 q 082 52 R 114 72 r 083 5
D LRP830 DEMONSTRATION This appendix describes how to setup an LRP830 demonstration using an SS Technologies® DeviceNet scanner card connected to an LRP830 via a DeviceNet CAN bus. The following link describes available SST DeviceNet scanner products (e.g. PCMIA scanner card): http://www.sstech.on.ca/sales/cards/dn/dnpcm.htm Note: Cutler/Hammer® DeviceNet scanners use SST similar hard-ware, however, Netsolver® DNS software is typically used with Cutler Hammer scanners.
Using DNSW32 or DNSW16 The name of the recommended program is DNSW16.exe or DNSW32.exe depending upon whether you have installed the 16-bit or 32-bit version. The typical SST installation placed the program in the following PC path (for example): "C:\Program Files\SST\DeviceNet\dnscan\Dnsw32.exe" You may execute the program by entering the path given above in Window's "Run" dialog box. After installation, you can also find it from Windows 95/98/NT as shown in the following illustration.
At the Interface Setup window (not shown) just use the defaults by pressing OK. Figure 31 — Opening the LRP830 Configuration File Next, load the configuration file ( 830net.SCL), using the FILE>OPEN pull down menu as depicted in Figure 31 and 32. This file can be found on the LRP830 installation disk.
Select Scanner from the Setup menu. Setup the node 8 scan list for the scanner interface as shown in Figure 33. Figure 33 — Node 8 LRP830 Configuration Setup Note: To insure dynamic update capability in the Device I/O Data window, it is recommended that you configure the SST scanner and LRP830 for 16 byte messages instead of the 32 shown in the examples.
Prepare to go online as depicted in Figure 34. Figure 34 — Going Online Select the "Advanced" button from the pop-up window which takes you to Figure 35.
Figure 36 shows how to display the Device I/O data window. Figure 36 — Entering the Device I/O Data Window Start scanning now by clicking the PLAY icon, which looks like a black right triangle on the button bar.
Now you are ready to issue commands from the scanner demo program as shown in the Figure 32. Message offsets are shown as 00-15 as the demo only allows 16 characters to be entered. If you need to enter more than 16, DNSWxx.exe is a MS Visual Basic program (source included by SST) which you can modify any way you wish. Figure 37 shows how to enter an ABx Fast block read command (no checksum) which is output from the scanner to the antenna. The command format is defined in Section 6.4.
Figure 39 — Interface Status/LRP830 Responses Copyright © 2000 Escort Memory Systems LRP830-Series Long-Range Passive Reader/Writer 177
E DEVICENET PROTOCOL EXAMPLES For the HDR Device Type, when the DeviceNet Scanner Host has data available to send to the LRP830, it must set the "REQ" bit in the DeviceNet message header. If the message length is 30 bytes, then the message is fragmented and structured as follows from the master scanner. The header byte is underlined and italicized. DeviceNet Polled protocol is used. Examples The following are actual DeviceNet bus message captures by SS-Technologies DeviceNet Analyzer® software.
Header Device Type Protocol When selecting the “Header” device type in the LRP830 configuration, the following features are available. A special message header is required, which precedes each ABx command and response. The Allen Bradley® SLC500 PLC with DeviceNet scanner module (1747-SDN) must process every message header word coming from the LRP830. It must also correctly setup a handshake header for every message going out to the LRP830.
The length of the header is one word and should appear at the beginning of each incoming and outgoing message. When you setup your message sizes you will have 2 bytes overhead. In essence, for a 28 byte message, you will have 2 bytes of non-data overhead in each DeviceNet message. The DeviceNet message will be fragmented into four, 8 byte fragments. The first byte of every fragment is reserved for the fragment header byte. The fragment header byte count is not included in the total message size.
Header: HDR (config display notation) Command to LRP830: Standard ABx Block Read This is from the explanation of ABxS Command 5 found in Section 6.3, pages 39 and 40. It reads 8 bytes of data from the tag starting at address 0101H. A timeout of 2 seconds (07D0H = 2000 x 1 ms) is set for the completion of the Block Read. The REQ bit is set in the header word as shown in the first row below. MCID/MSGID Lgth Frg .Hdr.
Header Device Type Command Protocol The following sequence shows the handshaking that will occur between a PLC DeviceNet scanner host and the LRP830. The ladder logic in the PLC must respond with an acknowledgment for each message uploaded from the LRP830.
Polls and responses occur at the poll rate of the scanner. The recommended interscan poll delay setting is 200 milliseconds for initial testing. This setting is made in the DeviceNet Scanner Host. Other polls and responses may be occurring in between the process blocks shown in Figure 30. This example shows only polls and responses that affect the ACK and REQ bits in the header word. Multiple handshaking bits may be on in a poll or response message header.
Header Device Type For Header Device Type the fragment calculation is the same but you must include the 2 bytes of the header word before you calculate the number of fragments. For 29 bytes of I/O message (user) data then: 29 + 2 = 31 (add the two byte header) 31 / 7 = 4.43 ~ 5 fragments. For the above two examples, the user should consider using 35 byte messages to optimize fragmentation overhead.
