Escort Memory Systems warrants that all products of its own manufacture conform to Es
cort Memory Systems specifications and arefreefromdefects in material and workmanship
when used under normal operating conditions and within the service conditions for which
they were furnished. The obligation of Escort Memory Systems hereunder shall expire one
(1) yearafter delivery, unlessotherwisespecified,andis limited to repairing, or at its option,
replacing without charge, any such product which in Escort Memory System's sole opinion
proves to be defective within the scope of this Warranty. In the event Escort Memory Sys
tems is not able to repair or replace defective products or components within a reasonable
time after receipt thereof, Buyers shall be credited for their value at the original purchase
price. Escort Memory Systems must be notified in writing of the defect or nonconformity
within the warranty period and the affected product returned to Escort Memory Systems
factory or to an authorized service center within thirty (30) days after discovery of such de
fect or nonconformity. Shipment shall not be made without prior authorization by Escort
Memory Systems.
This is Escort Memory Systems' sole warranty with respect to the products delivered here
under. No statement, representation, agreement orunderstandingoral or written, made by
an agent, distributor, representative, or employee of Escort Memory Systems which is not
contained in this warranty, will be binding upon Escort Memory Systems, unless made in
writing andexecutedby an authorized Escort Memory Systems employee. Escort Memory
Systems makes no other warranty of any kindwhatsoever,expressedorimplied, and all im
plied warranties of merchantability and fitness for a particular use which exceed the
aforestated obligation are hereby disclaimed by Escort Memory Systems and excluded
from this agreement. Under no circumstances shall Escort Memory Systems be liable to
Buyer, in contract or in tort, for any special, indirect, incidental, or consequential damages,
expenses, losses or delay however caused.
Equipment or parts which have been subject to abuse, misuse, accident, alteration, neglect, unauthorized repair or installation are not covered by warranty. Escort Memory Systems shall make the final determination as to the existence andcauseofanyalleged defect.
No liability is assumed for expendable items such as lamps andfuses. No warranty is made
with respecttocustom equipment or products produced to Buyer's specifications except as
specifically stated in writing by Escort Memory Systems in the contract for such custom
equipment.
This warranty is the only warranty made by Escort Memory Systems with respect to the
goods delivered hereunder, and may be modified or amended only by a written instrument
signed by a duly authorizedofficerofEscort Memory Systems andacceptedbythe Buyer.
Extended warranties of up to four years are available for purchase for most EMS products.
Contact EMS or your distributor for more information.
-
-
-
-
-
This document contains proprietary informationwhich is protected by copyright. All rights are re
served. The information in this manual has been carefully checked and is believed to be accu
rate; however, no responsibility is assumed for possible inaccuracies or omissions.
Specifications are subject to change without notice.
EMS®, Escort Memory Systems® and the EMS® logo are registered trademarks of Escort
Memory Systems, aDatalogic Group Company. Other brand and product names mentionedare
trademarks or registered trademarks of their respective holders.
Escort Memory Systems
A Datalogic Group Company
170 Technology Circle
Scotts Valley, CA 95066
Telephone (831) 438-7000
FAX (831) 438-5768
www.ems-rfid.com
email: info@ems-rfid.com
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 ra
dio frequency energy and, if not installed and used in accordance with the in
structions, may cause harmful interference to radio communications.
However, there is no guarantee that interference will not occur in a particular
installation. If this equipment does cause harmful interference to radio or
television reception, which can be determined by turning the equipment off
and on, the user is encouraged to try and correct the interference by one or
more of the following measures:
Reorient or relocate the receiving antenna.
n
-
Increase the separation between the equipment and the re
n
-
ceiver.
Connect the equipment into an outlet on a circuit different
n
from that to which the receiver is connected.
Consult the dealer or an experienced radio/TV technician for
n
help.
CAUTION
Changes or modifications not expressly approved by Escort Memory Systems could void the user’s authority to operate the equipment.
Escort Memory Systems' passive read/write system is a complete family of
field-proven read/write Radio-Frequency Identification products. The sys
tem consists of RFID tags, reader/writers, antennas, controllers, bus inter
faces, 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. Tags are read and updated via an Escort Memory Systems
Reader/Writer, through any nonconductive material, while moving or stand
ing still.
Escort Memory Systems' LRP-Series long-range passive RFID system is the
latest in our line of high performance, industrial RFID equipment. The passive design of the LRP read/write system uses the RF field from the antenna
to power the tag, eliminating the need for tag batteries. The LRP passive
read/write system is designed to provide cost effective RFID data collection
and control solutions to automation and material handling applications.
The LRP system uses the internationally recognized ISM frequency of 13.56
MHZ to both power the tag, and to establish a radio link to transfer the information.
-
-
-
The LRP830 is specifically designed to work with LRP-Series passive tags,
which provide 48 bytes of reprogrammable memory.
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.
COM2 is an RS232 serial port used to download new software releases and
to setup the configuration parameters.
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 dam
aged, notify your distributor immediately. The LRP830 is delivered with the
following components:
LRP830 (-04, -08) Reader/Writer
n
LRP830 to Antenna Cable
n
LRP830 Operator's Manual
n
The following components are required for configuring a complete system:
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*
TagTypical Range (Z)
inches/mm
LRP125(HT)2.50/642.00/51
LRP250(HT)6.75/1716.00/152
LRP250HT-FLX6.75/1716.00/152
LRP-L55556.75/1716.00/152
LRP-L26665.75/1465.00/127
LRP-L49828.00/2037.00/178
LRP-L901409.00/2298.00/203
LRP-P1252.50/642.00/51
LRP-P38586.00/1525.00/127
LRP-P50507.00/1786.00/152
*These ranges are determined with metal near the -04 antenna as it would be in most conveyor
mountings. The actual tuning and testing of the -04 antenna is done with the antenna mounted be
tween two metal rollers on metal rails. The metal rollers are mounted 1/4” from the antenna.
NOTE: Proximity to metal, CRT devices, and other sources of electromagnetic radiation may affect
the range of the antenna.
Guaranteed Range
inches/mm
-
Figure 5 — Side View of RF Field, LRP-04 Antenna, Metal
Table 2 — Antenna to Tag Ranges, LRP-40 Antenna, No Metal*
TagTypical Range (Z)
inches/mm
LRP125(HT)3.00/762.25/57
LRP250(HT)8.50/2167.50/191
LRP250HT-FLX8.50/2167.50/191
LRP-L55558.50/2167.50/191
LRP-L26667.00/1786.00/152
LRP-L498210.00/2549.00/229
LRP-L9014012.00/30511.00/279
LRP-P1253.00/762.25/57
LRP-P338587.50/1906.50/165
LRP-P50508.50/2167.50/191
*These ranges calculated with no metal near the antenna.
NOTE: Proximity to metal, CRT devices, and other sources of electromagnetic radiation may affect
the range of the antenna.
Guaranteed Range
inches/mm
Figure 7 — End View of RF Field, LRP-08 Antenna, No Metal
Figure 8 — Side View of RF Field, LRP-08 Antenna, No Metal
Table 3 — Antenna to Tag Ranges, LRP-08 Antenna, No Metal
TagTypical Range (Z)
inches/mm
LRP125(HT)8.00/2037.00/178
LRP250(HT)17.00/43215.00/381
LRP250HT-FLX17.00/43215.00/381
LRP-L555517.00/43215.00/381
LRP-L266616.00/40613.00/330
LRP-L498220.00/50818.00/457
LRP-L9014025.00/63522.00/559
LRP-P1258.00/2037.00/178
LRP-P385816.00/40614.00/355
LRP-505017.00/43215.00/381
*These ranges calculated with no metal near the antenna.
NOTE: Proximity to metal, CRT devices, and other sources of electromagnetic radiation may affect
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. Sur
rounding the antenna with metal will greatly reduce the reading range of the
antenna. As rule of thumb, keep any metal structure away from the antenna
at least more than the reading range along the axis, and a third of such dis
tance on the side. The mounting holes are accessed through the inside of the
LRP830 Reader/Writer. Refer to Figure 9 for locations and dimensions.
Special mounting instructions must be followed to get optimal read/write
performance from the LRP830-08 antenna. Mount the antenna with a mini
mum 5.90" (150mm) spacing from any metal to the back or sides of the an
tenna, 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.
n
Stay within the guaranteed range for the tag to be used.
n
Conform with EIA RS232, RS422 and RS485 standards.
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.
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.4DeviceNet Connector
Figure 14 shows the connections for the DeviceNet connector.
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 config
ured for sensors with a PNP or NPN output. The outputs can be configured
in a Sourcing or Sinking configuration. The examples in Figures 17 through
24 show different connections for common input and output devices.
Inputs
The +IN terminal must be at a higher positive potential than the -IN terminal
for current to be sensed correctly. The voltage range is 4.5 to 30V between
the +IN and the -IN inputs and the maximum current is 25 mA.
Outputs
The output is limited to 30Vdc when off and 500 mA. These are maximum
ratings. A device that operates at 200 mA may destroy the output due to inrush current if that current exceeds 500 mA (e.g. an incandescent light). The
inductive "kick" (back EMF from a collapsing magnetic field) when a relay
is released can impose a voltage higher than 30V and destroy the output
transistor (use a backwards diode to clamp the back EMF).
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 con
nected to the positive supply. This also requires a high quality sealed contact.
Figure 21 shows a relay connected as a current sourcing "Contact." The re
lay is grounded and the +OUT terminal goes to the positive supply. The di
ode 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 22 — Sinking Output "Contact"
Figure 22 shows a "Contact" sinking current from a relay, the -OUT terminal
is grounded and the relay goes to the positive supply. This configuration
must also have a diode across the relay coil to protect the circuit and reduce
noise.
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.
The maximum current consumption at 24Vdc is 1.3 A.
Power Options
There are three options for powering the LRP830:
Powered from the DeviceNet Bus (default)
n
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.
Powered via the external power connector
n
This is how you must power the LRP830 if you are not connecting
the LRP830 to a DeviceNet network.
n
Powered from an external supply and isolated DeviceNet bus
power (isolated mode)
When the LRP is powered from both sources, the LRP830 will be
opto-isolated from the DeviceNet bus.
The DeviceNet interface board draws 20 mA at 24 Vdc from the
DeviceNet bus when the LRP830 is powered with this method.
Power to the external power connector should conform to the spec
ifications given above.
If you choose to power the LRP830 with an external supply via the power
connector, you must open the LRP830 and changed jumper and cable loca
tions. The following sections describe how to make these changes.
By default, the LRP830 is configured to run with power supplied by the net
work. 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 ac
cording to the pinouts given for the DeviceNet connector in Figure 14, page
16.
Power via the external supply connector
The LRP830 contains components sensitive to electro-static discharge. Take
proper grounding precautions before opening the LRP830.
To change the LRP830 to run in isolated mode:
1. Open the LPR820 by loosening the four captive screws that secure the cover.
2. Refer to Figure 25 and then move the power cable, labeled assembly 10-3110, from connector J7 to J9.
Entering Download Mode via DIP switch 5 (4 flashes)
Configuration Mode initiated (CTRL-D) - Both LEDS flash 4 times
Configuration Mode initiated (CTRL-E) - Both LEDS flash 2 times
Outgoing data (TX): green
Outgoing data (TX): green
Additional LED behavior may be observed during certain commands and
conditions. This behavior will be indicated as appropriate elsewhere in this
manual.
The LRP830 has RS232 and RS422 available on the COM1 serial port.
COM2 is configured for RS232 communications and is reserved for down
loading 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.
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 inter
face, 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.
-
Figure 28 — Digital Board with DIP Switch
NOTE:
When you set switch 5 ON to enable download, the default parameters will
first be restored and saved to the non-volatile memory.
The baud rate configuration on the main board only applies to the RS232
and RS422 serial interfaces. When a Bus Interface (DeviceNet) is selected,
the baud rate is set by the Interface Board DIP switches.
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.
The LRP830 feature a menu-driven program designed to give convenient
access to the serial parameters, restore defaults or change operating modes.
5.1How 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 Sys
tems’ Web site at www.ems-rfid.com.
LRP830Standard PC Serial Port
COM2 Pin NumberSignal NameDB9 Pin NumberSignal Name
RTX2 RX
PRX3 TX
MGND5GND
Set the serial parameters to the LRP830 default settings or the last known
state of COM2.
The default settings for COM2 are as follows:
Baud9600
ParityNone
Data bits8
Stop bits1
Flow controlNone
-
If you can not establish communications with COM2, do the following to
restore the default values.
1. Place DIP switch five in the ON position and cycle power to
the LRP830 or press the reset switch. This will load the default
values.
2. Place DIP switch 5 in the OFF position and cycle power once
more.
Please refer to Chapter 4, Serial and Bus Communications for more infor
mation on the serial interface.
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 initial
ization. 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.7C, June 2000
DSP Firmware V1.7B, August 2000
*******************************************************
[1]Set-up Operating Parameters
[2]Download New Program
[3]Download DSP Firmware
[4]Exit to Operating Mode
Enter Selection:
5.2Set-up Operating Parameters
To change the operating parameters of the LRP830, enter 1 at the initial
menu. The following menu will be displayed, listing the current settings:
The exact appearance of the menu display will depend on the settings you
have made, and will be updated when you save your changes.
Serial Port COM1: RS232, 9600, N, 8, 1, No handshake (DIP switches)
Serial Port COM2: RS232, 9600, N, 8, 1, No handshake
Operating Mode: ABx Standard
RF Communication: Fast Mode
-
[1]Set COM1 Parameters
[2]Set COM2 Parameters
[3]Set Operating Mode
[4]Set RF Communications
[5]Restore Factory Defaults
[6]Return to Main Menu
Enter Selection:
Enter the number of the sub-menu you wish to enter. When you have made
your selection you will be prompted to save your changes to the non-volatile
EEPROM. For the new settings to take effect, you must save your changes
to the EEPROM and reset the LRP830. If you do not save changes to the
EEPROM, the new settings will be effective only until the LRP830 is reset.
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. The default values are indicated by an
asterisk (*).
Data size? [0] 7 bit [1] 8 bit*
Parity? [0] None* [1] Even [2] Odd
Handshake? [0] None* [1] Xon/Xoff
Save Changes to EEPROM? [0] No [1] Yes
Set COM2 Parameters
Selecting 2 from the above menu will bring to the following display for the
COM2 parameters. Enter the appropriate number at each prompt. The
default values are indicated by an asterisk.
Data size? [0] 7 bit [1] 8 bit*
Parity? [0] None* [1] Even [2] Odd
Handshake? [0] None* [1] Xon/Xoff
Save Changes to EEPROM? [0] No [1] Yes
Set Operating Mode
The Set Operating Mode menu allows you to choose the command protocol
the LRP830 will use or configure it to automatically enter Continuous Read
Mode upon start-up.
*** 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. ABx
Standard (ABxS) uses only the LSB for tag data while ABx Fast (ABxF)
will use both the MSB and the LSB for the passing of data. ABx ASCII
(ABxA) mode permits RFID operations using seven bit data packets in the
form of printable ASCII characters.
Checksum?
ABx Fast and ABx ASCII also permits you to include a checksum in the
command. To use a checksum value with the ABx commands, you must
enable the checksum option. It is recommended that you enable the
checksum option.
Power up in Continuous Read Mode?
You also have the option of setting the LRP830 to start-up in Continuous
Read Mode. When you have configured the LRP830 to function in this
manner, you do not issue commands to the LRP830. It will, upon start-up,
enter directly into a Continuous Read Mode. Since this bypasses the normal
command parameters, you must specify the Continuous Read Mode
parameters.
The LRP830 will respond to other commands and resume Continuous Read
Mode when completed.
This option will not function over a DeviceNet bus.
If you are using your LRP830 in this mode, you must choose if you want the
LRP830 to read a single tag or read multiple tags within the field.
To exit Continuous Read Mode you must either re-enter the configuration
menu and select NO from the Power up in Continuous Read Mode option,
or issue a Continuous Read command from the host with a read length of 0
as described in Chapter 6, RFID Interface.
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 fol
lowing the starting tag address. Entering a read length of 0 will disable Con
tinuous Read Mode.
Delay Between Identical Decodes (0-60)
The Delay Between Identical Decodes parameters can have a value of 0 to
60 seconds. When the Delay Between Identical Decodes is set to 0, the
LRP830 will continuously read AND transmit tag data to the host. This can
flood the buffers and cause communication errors and data loss.
Raw Read Response?
If you have selected ABx Fast or ABx ASCII, you have the option of stripping the command protocol from the data and adding a terminator to separate the data packets. You can choose a CR (0DH) or CR/LF (0DH, 0AH) to
terminate the data.
Set RF Communication
-
The LRP830 should be configured with the default (0) Fast Mode.
*** Set RF Communication ***
RF Communication? [0] Fast Mode* [1] Standard Mode 0
Save Changes to EEPROM? [0] No [1] Yes
Restore Factory Defaults
It is often helpful during troubleshooting to restore the LRP830 to known
default values. To do so, select 1from this menu.
The restored defaults will be saved to the EEPROM. The communication
defaults can also be restored by placing the main board DIP switch number 5
in the ON position and then restarting the LRP830. After you have saved
any changes, you must re-initialize the LRP830 with switch 5 in the OFF
position.
When you have completed your configuration, entering 5 will return you to
the initial menu. Unsaved changes will be effective until the LRP830 is re
set. Saved changes will be loaded automatically the next time the LRP830 is
reset.
-
5.3Download 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.
When you select 2 from the Main Menu, the LRP830 will display informa
tion on the current program and prompt you to begin the download.
*** Download New Program***
Program Size:21824 Bytes
Program Checksum:5AE0H (OK)
Free Program Memory:39600 Bytes
Flash Write Counter:2 times
Press a key to start Downloading
After you have pressed a key, the LRP830 will display:
Send the Intel Hex file. Downloading now.
Send the new program file via your terminal emulation program in ASCII
text or Hexadecimal format. Wait 10 seconds after the download is complete
before resetting the LRP830.
IMPORTANT:
It is not necessary to download firmware into the unit unless instructed to do
so by Escort Memory Systems technical support personnel.
-
5.4Downloading DSP Firmware
Before attempting to download new firmware to the LRP830 main board,
read the instructions provided in a readme.txt file on the update diskette.
When upgrading software in the controller the number and meaning of the
configuration parameters may not match between the old and new software.
The old settings may not be interpreted properly with the new software. Be
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 pa
rameters 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.
*** Download DSP Firmware***
Press a key to start Downloading
After you have pressed a key, the LRP830 will display:
Send the Intel Hex file. Downloading now.
Send the new firmware via your terminal emulation program in ASCII text
or Hexadecimal format. The firmware will be automatically transferred to
the DSP Flash Memory. Wait 10 seconds after the download is complete
before resetting the LRP830.
Record: 750
Download OK
File Transfer to DSP
Blocco 24/24
DSP Flash Programming...
New Firmware Transferred to DSP
WARNING:
Do not download INTERFACE BOARD firmware to the main board.
IMPORTANT:
It is not necessary to download firmware into the unit unless instructed to do
so by Escort Memory Systems technical support personnel.
5.5Exit to Operating Mode
This option is available if you wish to use temporary, unsaved, configuration
parameters. The unsaved options you have selected will be used until the
LRP830 is reset and the saved parameters are restored.
The LRP830 offer three possible command protocols: ABx Standard, ABx
Fast and ABx ASCII. The ABx Standard format is word-based and is com
patible 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.
The ABx Fast protocol is the most efficient and therefore recommended by
Escort Memory Systems. Table 7 lists the ABx commands available for the
LRP830.
The LRP830 command set is made of two subsets: the ‘Non-Anticollision’
commands and the ‘Anticollision’ commands. The Anticollision commands
allow you to manage the multiple-tags-in-field capability of the LRP system.
Command Timeout
-
Most commands have a timeout value that is used to limit the time the
LRP830 will attempt to complete the specified operation. This value is given
in 1 ms increments with a maximum value of 65,534 ms. A timeout value of
0 will generate a syntax error.
Between 500ms and 1000ms is recommended for a timeout value for single
tag commands. Shorter timeouts may result in diminished range. A 30ms
timeout value is the shortest allowable timeout and should only be used for
short range, single tag command applications. Multiple tag commands will
require longer timeout values. For time critical applications the timeout
value should be tested to obtain the maximum performance value. A longer
timeout value does not mean that the command will take any longer to exe
cute if the tag being addressed is in the field, it only represents the period of
time (in milliseconds) the unit will attempt to execute the command. If the
tag is present, the response time to execute the command will be the same
whether the timeout is 100ms or 10,000ms.
The LRP830 will return an error if it encounters a fault during operation.
Table 7 lists the possible error codes in Hexadecimal format.
Table 7 — Non-Anticollision Error Codes
Error CodeDescription
04HFill Operation has failed
05HBlock Read has failed
06HBlock Write has failed
08HSearch Tag Operation failed
21HInput Command does not match pre-defined format (syntax error)
Additionally there are internal DSP errors, F1H through F5H, for use by
Escort Memory Systems technical support.
ABx Standard
ABxS error codes are returned in the LSB of the second register passed to
the PLC. The format of the error response is shown below.
MSBLSBRemarks
AAHFFHCommand Error
00HXXHError Code
FFHFFHMessage Terminator
A Block Write fail error message would appear as: AAFF 0006 FFFFH.
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.
The STATUS byte is defined as follows:
76543210
Antenna
Failure
R/W Error CollisionsInternal
Error
TimeoutVerify
Error
Reserved Reserved
Some of the conditions are the same as found in the non-anticollision com
-
mands, other are new and relate only to the anticollision.
If any of the flag bits of the returned Status are set, then that condition
occurred during the command execution. Multiple conditions can occur in
the same command.
AntennaThere is an error at the antenna
Failure
R/W errorError during the tag memory access
CollisionCollisions detected: more than one tag in the field answered to
the LRP830 at the same time, meaning a higher Anticollision
Index probably needs to be set
Internal Error Internal error in low-level firmware
(contact Escort Memory Systems technical assistance)
TimeoutTimeout expired
Verify Error Set when re-read verification fails
Syntax Errors
Syntax errors (error code 21H) will be returned in the same format as
described for the non-anticollision commands.
The anticollision commands always have a Family ID and an Anticollision
Index as parameters. These parameters manage the read/writes when multi
ple 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.
If both the features are disabled, the commands operate exactly the same as
the Non-Anticollision commands.
Family ID
The Family ID is a 1 byte field in the LRP tag memory at address 0. When
the Family ID parameter is set to zero, the command is broadcast to all the
tags in the field. On the other hand, if it is not equal to zero, only the tags
with the specified Family ID in byte 1will respond to the LRP830.
This feature can help in implementing a multi-level organization of the tags,
by permitting the selective reading of tags by Family ID. This gives faster
access to the tags than by using Anticollision Index alone. As previously
noted, Family ID and the Anticollision Index can be used together for
increased efficiency.
-
When using the Family ID feature, the first byte of tag memory is reserved,
and thus only 47 bytes are allowed to be used. When the feature is disabled,
48 bytes are available for user data.
For this reason, in the read and write commands, once the parameter Family
ID is not equal to zero, the addresses can go from 1 to 47, and the size from
0 to 47. However, when the Family Code is zero, the addresses can start
from 0, and the size can be up to 48.
In order to initialize a tag with a chosen Family ID, byte 0 in the tag must be
set to that value by means of a Block Write or a Block Write All command.
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. Lowering the Index speeds up the tag read operation.
Selecting the Anticollision Index is therefore a tradeoff choice between the
number of tags in the reading field, and the time required to read/write to
them. Regardless of the index setting, ALL tags present will be read. The in
dex simply makes the process more efficient.
None of the Anticollision Index values will absolutely limit the number
of tags that can be read by the LRP830. The following table can assist you
in setting the Index value, but tests should be done to find the best value.
The allowed values are from 0 to 7.
Some commands return or have as a parameter, the Serial Number (SN).
The tag serial number is a unique read-only, 64 bit (8 bytes) code in the tag
memory. SN commands can be used to selectively write to a specific tag,
identified by the SN. A target tag can be identified with a previous SN read
command.
Note that the anticollision commands, except SN Block Write, SN Fill and
Tag Search All, will return a response packet only after the timeout is ex
pired. If the command has the Anticollision Index set to 0, then a response
will be returned after the first successful operation.
The Anticollision Commands return a successful response whenever the op
eration 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 ex
pressed in 2 byte words, in order to be compatible with the HMS commands
and to allow future developments.
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. 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 then proceed to fill the tag with the data value byte, starting at
the specified start address for the specified number of consecutive bytes.
When Fill Length is set to 0, the LRP830 will write fill data from the start
address to the end of the tag's 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.
FieldRemarks
CommandCommand number in hex preceded by AAH
Start AddressThe tag address where the fill will start
Fill LengthThe number of tag addresses to be filled in bytes
TimeoutTimeout value given in 1 ms units (1EH - FFFEH)
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.
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.
The Block Read command consists of a start address and length, followed
by the message terminator, FFFFH, as shown below. If the read range ex
ceeds the last tag address, the LRP830 will return error message 21H, in
-
-
valid format.
The data read from the tag is returned in the LSB of the register, and the
MSB is always 00H.
FieldRemarks
CommandCommand number in hex preceded by AAH
Start AddressThe tag address where the read will start
Read LengthThe number of tag addresses to be read
TimeoutTimeout value given in 1 ms units (1EH - FFFEH)
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.
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 incre
ments and can have a value of 1EH to FFFEH (65,534 ms). When the time
out is set to 0, the LRP830 will return a syntax error.
The Block Write command consists of a start address followed by the data
stream to be written to the RFID tag. If the write range exceeds the last tag
address, the LRP830 will return error message 21H, invalid format. The
LRP830 will also return an error if the write length is 0.
The data to be written to the tag is contained in the LSB of the register, and
the MSB is always 00H.
FieldRemarks
CommandCommand number in hex preceded by AAH
Start AddressThe tag address where the write will start
Write LengthThe number of tag addresses to be written to in bytes
TimeoutTimeout value given in 1 ms units (1EH - FFFEH)
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.
DESCRIPTION
Retrieve the eight-byte tag serial number.
DISCUSSION
Each LRP tag has an unique (2
64
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.
FieldRemarks
CommandCommand number in hex preceded by AAH
Timeout2-byte timeout value in 1 ms increments (1EH - FFFEH)
Message TerminatorFFFFH
EXAMPLE:
This example will wait until a tag is in range and then reads the 8-byte serial
number. In this example the SN is 1E6E3DC200000000H in hexadecimal.
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.2 for
more information on error codes.
FieldRemarks
CommandCommand number in hex preceded by AAH
Timeout2-byte timeout value in 1 ms increments (1EH - FFFEH)
Message TerminatorFFFFH
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.
DESCRIPTION
When in Continuous Block Read mode, the LRP830 sends block reads con
tinuously 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 Identi
cal Decodes feature prevents redundant data transmissions when the
LRP830 is in Continuous Block Read mode.
DISCUSSION
The initiate/cancel Continuous Block Read command contains three param
eters: read length, start address, and delay between identical decodes. The
read length parameter switches the mode. Any valid, non-zero length (1-48)
will set the LRP830 into Continuous Block Read mode. A read length value
of 00H will turn Continuous Block Mode off.
The Delay Between Identical Decodes value can have a value of 0 to 60
seconds. When the Delay Between Identical Decodes is set to 0, the LRP830
will continuously read AND transmit tag data to the host. This can flood the
buffers and cause communication errors and data loss.
-
-
If the LRP830 receives other commands from the host, it will execute them
and then resume Continuous Block Read mode. To exit Continuous Block
Read mode, issue the command with a read length of 0.
In Continuous Block Read mode, the LEDs will display as follows:
LEDBehaviorDescription
ANT LEDONAssumes the Antenna is powered and functioning
CONFIG LED BLINKTag entered the RF field
RF LEDONA tag has been read and is still in the field
RF LEDOFFA read tag has been out of range for the specified time
NOTE:
This command can not be used over a DeviceNet interface.
Start Address2 byte value for the start address in the tag
Read Length2 byte value for the block read length
Delay Between
Identical Decodes
Message TerminatorFFFFH
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.
EXAMPLE
This example places the LRP830 in Continuous Block Read mode and reads
8 bytes of data from the tag starting at address 0001H. A delay between
identical reads of 2 seconds (0002H = 2 x 1 second increments) is set.
Command from Host
MSBLSBRemarks
AAH0DHPerform Command D
00H01HStart address
00H08HRead 8 bytes
00H02H2 second delay
FFHFFHMessage Terminator
Response from LRP830
MSBLSBRemarks
AAH0DHCommand echo
FFHFFHMessage Terminator
The LRP830 will first return an acknowledgment of the command followed
by a response containing read data when a tag enters the antenna field.
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.
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=ONand0=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.
MSBLSBRemarksLSB Bit 3
Output D
00H00HReset A, B, C, D0000
00H01HSet Output A - Reset B, C, D0001
00H02HSet Output B - Reset A, C, D0010
00H03HSet Output A, B - Reset C, D0011
00H04HSet Output C - Reset A, B, D0100
00H05HSet Output A, C - Reset B, D0101
00H06HSet Output B, C - Reset A, D0110
00H07HSet Output A, B, C - Reset D0111
00H08HSet Output D - Reset A, B, C1000
00H09HSet Output A, D - Reset B, C1001
00H0AHSet Output B, D - Reset A, C1010
00H0BHSet Output A, B, D - Reset C1011
00H0CHSet Output C, D - Reset A, B1100
00H0DHSet Output A, C, D - Reset B1101
00H0EHSet Output B, C, D - Reset A1110
00H0FHSet Output A, B, C, D1111
FieldRemarks
CommandCommand number in hex preceded by AAH
Output PatternHex value for the bit output settings
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=ONand0=OFF.
The following chart shows the hex values for all input conditions that can be
returned in word 2 of the response.
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. It will then proceed to fill the tag with the data value byte, starting at
the specified start address for the specified number of consecutive bytes.
The Fill Length must be set to a non-zero value (1-48). The timeout value is
given in 1 msec increments and can have a value of 1EH to FFFEH (65,534
ms). When the Anticollision Index is not zero (multiple tag-in-field enabled), the LRP830 will return a response after the timeout expires. If the
Anticollision Index is 0, a response is returned when a successful operation
is performed on 1 tag or when the timeout has expired. When the timeout is
set to 0, the LRP830 will return a syntax error.
FieldRemarks
CommandCommand number in hex preceded by AAH
Family CodeTag Family ID - 00H = all tags
Anticollision indexNumber of tags expected
Start AddressThe tag address where the fill will start
Fill LengthThe number of tag addresses to be filled (1-48)
Timeout2-byte timeout value in 1 ms increments (1EH - FFFEH)
Data Value ByteThe byte to be used as fill
Message TerminatorFFFFH
NOTE:
This command can not be used over a DeviceNet interface.
A response to a successful command will follow this form.
FieldRemarks
Command EchoCommand number in hex preceded by AAH
Number of Tags filledNumber of tags found in the field and filled
Command StatusOne byte Error status
Message TerminatorFFFFH
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. A timeout of 2 seconds (07D0H = 2000 x 1 msec increments) is
set for the completion of the Fill All Tag. The Anticollision Index is set to 2
so 4 to 8 tags will be expected. Four tags are successfully filled within the
timeout.
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.
The Block Read All consists of Tag Family ID and an Anticollision Index,
a start address and length, followed by a timeout value and the message
terminator. If the read length exceeds the last tag address, the LRP830 will
return a syntax error message 21H.
The data read from the tag is returned in the LSB of the register, and the
MSB is always 00H.
A special termination packet (AAH FFH) is sent after the timeout expires.
When the Anticollision Index is not zero (multiple tag-in-field enabled), the
LRP830 will return a response after the timeout expires. If the Anticollision
Index is 0, the command returns after the successful operation on one tag or
when the timeout expires. No termination packet is sent after a successful
operation when the Anticollision Index set to 0.
FieldRemarks
CommandCommand number in hex preceded by AAH
Tag FamilyTag Family ID - 00H = all tags
Anticollision indexNumber of tags-in-field expected
Start AddressThe tag address where the read will start
Read LengthThe number of tag addresses to be read
Timeout2-byte timeout value in 1 ms increments (1EH - FFFEH)
Message TerminatorFFFFH
NOTE:
This command can not be used over a DeviceNet interface.
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.
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 incre
ments and can have a value of 1EH to FFFEH (65,534 ms). When the time
out is set to 0, the LRP830 will return a syntax error.
The Block Write consists of a Tag Family ID and an Anticollision Index,
start address followed by the data stream to be written to the RFID tag. If the
write range exceeds the last tag address, the LRP830 will return error mes
-
sage 21H, invalid format.
The data to be written to the tag is contained in the LSB of the register, and
the MSB is always 00H.
The LRP830 returns a response when the timeout expires. If the
Anticollision Index is 0 the command returns a response after the successful
operation on 1 tag, or when the timeout expires.
-
FieldRemarks
CommandCommand number in hex preceded by AAH
Family IDTag Family ID - 0 = all tags
Anticollision IndexNumber of tags-in-field expected
Start AddressThe tag address where the write will start
Write LengthThe number of tag addresses to be written to in bytes
Timeout2-byte timeout value in 1 ms increments (1EH - FFFEH)
Write DataThe data to be written (1-48 bytes)
Message TerminatorFFFFH
NOTE:
This command can not be used over a DeviceNet interface.
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.
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 (2
64
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). When the timeout is set to 0, the LRP830 will
return a syntax error. A special termination packet (starting with AAH FFH)
is sent when the timeout expires. If the Anticollision Index is 0, a response
is returned after successful operation to 1 tag or after the timeout has ex
pired. No termination packet is sent after a successful operation when the
Anticollision Index set to 0.
FieldRemarks
CommandCommand number in hex preceded by AAH
Family IDTag Family ID - 00H = all tags
Anticollision IndexNumber of tags-in-field expected
Timeout2-byte timeout value in 1 ms increments (1EH - FFFEH)
Message TerminatorFFFFH
NOTE:
This command can not be used over a DeviceNet interface.
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 ex
ample the SN for the found tag is 1E6E3CD200000000H in hexadecimal.
Multiple tags will return a complete response packet for each tag.
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.2 for more information on error codes.
The number of tags returned can be either 1 (tag found) or 0 (timeout ex
-
pired without having found a tag).
FieldRemarks
CommandCommand number in hex preceded by AAH
Family IDTag Family ID - 00H = all tags
Anticollision IndexNumber of tags-in-field expected
Timeout2-byte timeout value in 1 ms increments (1EH - FFFEH)
Message TerminatorFFFFH
NOTE:
This command can not be used over a DeviceNet interface.
EXAMPLE
Checks for an RFID tag in the RF field. A timeout of 1 seconds (07D0H =
2000 x 1 msec increments) is set for the completion of the Tag Search All.
The Family ID is set for any tag, and the Anticollision Index is set to expect
4-8 tags. One tag is found and the command is successful.
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 com
mand 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.
When multiple tag-in-field is enabled (Anticollision Index is not 0), the
LRP830 will return a response when the timeout period expires. When mul
tiple tag-in-field is disabled, the LRP830 will return a response when it reads
a tag or the timeout expires.
FieldRemarks
CommandCommand number in hex preceded by AAH
Family IDTag Family ID - 00H = all tags
Anticollision IndexNumber of tags expected
Timeout2-byte timeout value in 1 ms increments (1EH - FFFEH)
Set/Reset1 = Set, 0 = Reset EAS
Message TerminatorFFFFH
-
-
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 com
mand is issued, 5 tags with Family ID 09H are found and enabled for EAS.
DESCRIPTION
If are using the EAS feature in your application, the EAS Start/Stop com
-
mand 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 com
mand contains a control byte that toggles EAS: 1 = start, 0 = stop. A Family
ID can be set so that only EAS-enabled tags from the specified Family trig
ger EAS responses. The Anticollision Index is ignored and should be set to
00H for this command.
The EAS mode also controls the CONFIG, ERROR and RF LEDs. The
following table:
LED(s)BehaviorDescription
CONFIG,
ERROR,
RF LEDs
RF LEDONEAS-enabled tag entered field. LED will remain ON until all EAS tags
ERROR LED BLINKSLast EAS tag left the field.
OFFNo EAS-enabled tag in field
have left the field.
-
-
IMPORTANT:
EAS mode prevents any other commands from being acknowledged or exe
cuted until EAS has been stopped.
EXAMPLE
This example starts EAS mode. Three responses follow. The first is a com
mand 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.
-
Command from Host
MSB LSBRemarks
AAH89HPerform Command 89
00H00HFamily ID/null byte
00H01HStart/Stop
FFHFFHMessage Terminator
ACT Response from LRP830
MSB LSBRemarks
AAH89HCommand Echo
FFH00HNtag/Status
FFHFFHMessage Terminator
When an EAS-enabled tag enters the antennas’ field, the LRP830 responds
with an EAS tag-in-field response.
Tags-in-Field Response from LRP830
MSB LSBRemarks
AAH89HCommand Echo
01H00HNtag/Status
FFHFFHMessage Terminator
When all EAS-enabled tags have left the field, the LRP830 will send the fol
lowing response.
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. After processing the new command, the LRP will resume the Con
tinuous Read All mode.
The command has a parameter, tag delay, that can prevent multiple reads of
the same tag. A tag is not read a second time until a specified number of
tags have been read since it was last read. Allowed value are from 0 to 255
(FFH), where 0 means the tag can be re-read anytime. When Continuous
Read All mode is interrupted with other commands, the tag delay count is
stopped during execution of the other commands and then resumed.
The LRP830 will respond with an acknowledge packet followed by data
packets for each tag read.
-
CONFIG LED blinks after each packet transmission.
FieldRemarks
CommandCommand number in hex preceded by AAH
Family IDTag Family ID - 00H = all tags
Anticollision IndexNumber of tags expected
Start AddressTag address for the start of the read
Read Length1-48 = start, 0 = stop
Tag DelayNumber of tags that must be read before the same tag will be read again
Message TerminatorFFFFH
(0-225)
NOTE:
This command can not be used over a DeviceNet interface.
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.
Command from Host
MSBLSBRemarks
AAH8DHPerform Command 8D
00H02HTag Family 00/ Index 2
00H01HStart Address
00H04HRead Length
00H14HTag Delay
FFHFFHMessage Terminator
ACK Response from LRP830
MSB LSBRemarks
AAH8DHCommand Echo
FFHFFHMessage Terminator
After the LRP830 sends the acknowledgment, it will send the read data from
the 3 tags.
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. Re
-
maining bits can lock the EAS feature and the lock configuration itself.
When multiple tag-in-field is enabled (Anticollision Index is not 0), the
LRP830 will return a response when the timeout period expires. When mul
tiple tag-in-field is disabled, the LRP830 will return a response when it locks
bytes or the timeout expires.
Attempting to write to locked bytes will return a write error timeout in the
status byte. If you write to addresses that\ contain both locked and
non-locked bytes, the LRP830 will return a write error in the status byte.
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.
FieldRemarks
CommandCommand number in hex preceded by AAH
Family CodeTag Family ID - 00H = all tags
Anticollision indexNumber of tags-in-field expected
Timeout2-byte timeout value in 1 ms increments (1EH - FFFEH)
Lock MSBBits 8-15 of the configuration word
Lock LSBBits 0-7 of the configuration word
Message TerminatorFFFFH
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.
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.
The fill function requires a Family ID and an Anticollision Index, one data
value byte, a starting address, and a fill length. Then the command lists the
serial numbers of the tag to be filled. It fills the specified tag with the data
value byte, starting at the specified start address for the specified number of
consecutive bytes. When Fill Length is set to 0, the LRP830 will write fill
data from the start address to the end of the tags 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. It returns a response when done or when the timeout
expires.
FieldRemarks
CommandCommand number in hex preceded by AAH
Family CodeTag Family ID - 00H = all tags
Anticollision indexNumber of tags-in-field expected
Start AddressThe tag address where the fill will start
Fill LengthThe number of tag addresses to be filled
Timeout2-byte timeout value in 1 ms increments (1EH - FFFEH)
A response to a successful command will follow this form.
FieldRemarks
Command EchoCommand number in hex preceded by AAH
Number of Tags filled0 = tag not found, 1 = tag filled
Command StatusOne byte Error status
Message TerminatorFFFFH
EXAMPLE
Writes 'A' (41H) to a single tag, starting at tag address 0005H for the follow
ing next consecutive 40 bytes. The Family ID is turned off and the
Anticollision Index is set to expect 2-4 tags. A timeout of 2 seconds (07D0H
= 2000 x 1 msec increments) is set for the completion of the configuration.
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.
The SN Block Read consists of Family ID and an Anticollision Index, a start
address and length, followed by a timeout value. The 8-byte serial number of
the target tag is specified. If the read length exceeds the last tag address, the
LRP830 will return error message in the status byte. It returns a response
when done or when the timeout expires.
The data read from the tag is returned in the LSB of the register, and the
MSB is always 00H. A special error packet (AAH FFH) is sent if the timeout expires.
FieldRemarks
CommandCommand number in hex preceded by AAH
Tag FamilyTag Family ID - 00H = all tags
Anticollision indexNumber of tags expected
Start AddressThe tag address where the read will start
Read LengthThe numbers of tag addresses to be read
Timeout2-byte timeout value in 1 ms increments (1EH - FFFEH)
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 incre
ments) 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.
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 incre
ments and can have a value of 1EH to FFFEH (65,534 ms). When the time
out is set to 0, the LRP830 will return a syntax error.
The SN Block Write consists of a Family ID, Anticollision Index, and start
address followed by the data stream to be written to the RFID tag. If the
write range exceeds the last tag address, the LRP830 will return an error
message 21H, invalid format. It returns a response when done or when the
timeout expires.
The data to be written to the tag is contained in the LSB of the register, and
the MSB is always 00H.
FieldRemarks
CommandCommand number in hex preceded by AAH
Family IDTag Family ID - 00H = all tags
Anticollision IndexNumber of tags-in-field expected
Start AddressThe tag address where the write will start
Write LengthThe number of tag addresses to be written to
Timeout2-byte timeout value in 1 ms increments (1EH - FFFEH)
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.
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. 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 response to this command will contain the serial number of the respond
ing tags preceding the data from those tags. The termination packet is trans
mitted when the timeout expires. Each packet will be sent to the host as soon
as it is available. The returned serial numbers can be used to read/write to
tags-in-field via the SN Block Read/Write command.
The SN Block Read All consists of Family ID, Anticollision Index, a start
address and length, followed by a timeout value and the message terminator
FFFFH. A special termination packet is sent when the timeout expires. If the
Anticollision Index is 0, a response is returned when the operation is successfully completed on 1 tag, or when the timeout expires. A termination
packet is not sent for successful completion if the Anticollision Index is 0.
If the read length exceeds the last tag address, the LRP830 will return an
invalid format error message (error code 21H).
FieldRemarks
CommandCommand number in hex preceded by AAH
Tag FamilyTag Family ID - 00H = all tags
Anticollision indexNumber of tags expected
Start AddressThe tag address where the read will start
Read LengthThe number of tag addresses to be read
Timeout2-byte timeout value in 1 ms increments (1EH - FFFEH)
Message TerminatorFFFFH
-
-
NOTE:
This command can not be used over a DeviceNet interface.
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.
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
n
cannot be used.
ABx Command Packet Structure:
The command protocol is based on the following minimal packet structure.
The data field and the checksum may not be present depending on the com
mand type and your checksum setting.
FieldNumber of Bytes Content
Header2<STX><STX> (02H, 02H)
Command Size2Packet length in bytes excluding the header, command
Command1Command Code
(Data)variablecommand data/parameters
(Checksum)1Optional Checksum
Terminator1<ETX> (03H)
size, checksum and terminator bytes.
-
Following a successful operation, the LRP830 will respond with the follow
ing. The data field and the checksum may not be present depending on your
checksum setting.
FieldNumber of Bytes Content
Header2<STX><STX> (02H, 02H)
Response Size2Packet length in bytes excluding the header, response
If the LRP830 Reader/Writer encounters a fault it will respond with the fol
lowing:
FieldNumber of Bytes Content
Header2<STX><STX> (02H, 02H)
Response Size2Packet length in bytes excluding the header, packet
Error Flag1FFH
Error Code1Hex error code, see Table 7 for details
(Checksum)1Optional Checksum
Terminator1<ETX> (03H)
The Header and Terminator are always STX-STX and ETX
n
size, checksum and terminator bytes. (02H in this case)
respectively.
All other bytes are interpreted as binary data (0 - 255 dec).
n
Fields with two bytes are sent most significant byte (MSB)
n
first.
The sequence for each command is given with the response format in the
following section.
Command/Response Size
-
The ABx Fast requires that the length of the packet be included in the command. All parameters and data between the Command/Response Size and
the Checksum or Terminator bytes must be accounted for in the com
mand/response size word. This includes all command codes and parameters
such as field definitions for Block Read/Writes. The command/response size
will be the same with, or without, a 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. Thus,
when the packet length through the checksum are added as byte values, the
sum will be FFH.
EXAMPLE
The following is a typical command using a checksum.
Command from Host
FieldContents
Header
<STX><STX>
Command Size00H
Command Code01H
Timeout07H
Checksum24H
Terminators <ETX>03H
02H
02H
03H
D0H
Sum these values to calculate
the checksum
The summed values begin with the Command Size and end with the timeout
value. That sum, less overflow, is subtracted from FFH for the checksum
value.
Thus: 00 + 03 + 01 +07 + D0 = DBFF - DB = 24H
The optional Checksum is included in the following command explanations.