AEG ARE i2.0x LF User manual

Manual
ARE i2.0x LF
AEG is a registered trademark used under license from AB Electrolux (publ)

Manual ARE i2.0x LF release V2
Version:
13
Page:
2 / 34
Manual ARE i2.0x LF release V2.docx
1. Introduction ............................................................................................................................................ 4
2. ARE i2.0x LF ............................................................................................................................................. 5
2.1 ARE i2.0x LF hardware.................................................................................................................... 5
2.1.1 Dimensions ARE i2.0x LF............................................................................................................. 5
2.1.2 Protection Class........................................................................................................................... 5
2.1.3 AAN Xi9F dimensions.................................................................................................................. 5
2.1.4 Mounting and grounding............................................................................................................. 6
2.1.5 Connectivity: ............................................................................................................................... 6
2.1.6 Read Range for SEMI Applications using AAN Xi9F.................................................................... 7
2.2 Firmware ARE i2.0x LF .................................................................................................................... 9
2.2.1 Instruction Set............................................................................................................................. 9
2.2.2 General format of instruction set................................................................................................ 9
2.2.3 BD ................................................................................................................................................ 9
2.2.4 VER............................................................................................................................................ 10
2.2.5 TOR ........................................................................................................................................... 10
2.2.6 GT .............................................................................................................................................. 11
2.2.7 RD .............................................................................................................................................. 11
2.2.8 WD ............................................................................................................................................. 12
2.2.9 MD ............................................................................................................................................. 12
2.2.10 NID......................................................................................................................................... 13
2.2.11 CID ......................................................................................................................................... 13
2.2.12 CN .......................................................................................................................................... 13
2.2.13 LD .......................................................................................................................................... 14
2.2.14 VSAVE ................................................................................................................................... 14
2.2.15 INIT........................................................................................................................................ 15
2.2.16 Error messages...................................................................................................................... 15
2.3 Firmware ARE i2.0x LF .................................................................................................................. 16
2.3.1 Instruction Set ........................................................................................................................... 16
2.3.2 General format of instruction set.............................................................................................. 16
2.3.3 BD .............................................................................................................................................. 16
2.3.4 VER............................................................................................................................................ 17
2.3.5 GT.............................................................................................................................................. 17

Manual ARE i2.0x LF release V2
Version:
13
Page:
3 / 34
Manual ARE i2.0x LF release V2.docx
2.3.6 TOR ........................................................................................................................................... 17
2.3.7 NID............................................................................................................................................. 18
2.3.8 CID ............................................................................................................................................. 18
2.3.9 CN .............................................................................................................................................. 19
2.3.10 RD.......................................................................................................................................... 19
2.3.11 WD ......................................................................................................................................... 19
2.3.12 VSAVE ................................................................................................................................... 20
2.3.13 INIT........................................................................................................................................ 20
2.3.14 Error messages...................................................................................................................... 21
2.3.15 ALGO ..................................................................................................................................... 21
2.3.16 LOG (EM4305 chip specific)................................................................................................... 22
2.3.17 PWD (EM4305 chip specific).................................................................................................. 22
2.3.18 LD (EM4305 chip specific) ..................................................................................................... 23
2.4 LED instruction set........................................................................................................................ 24
2.4.1 LED Standby (LSTB).................................................................................................................. 25
2.4.2 LED Reading (LGT).................................................................................................................... 25
2.4.3 LED Transponder number successfully read (LRD) .................................................................. 26
2.4.4 LED No Read (LNRD) ............................................................................................................. 26
2.4.5 LED Return to standby (LRT).................................................................................................... 27
2.4.6 LED Error (LERR)....................................................................................................................... 27
2.4.7 LED Process active .................................................................................................................... 28
2.4.8 LED Process status .................................................................................................................... 29
2.4.9 LED Setup help (FLED).............................................................................................................. 30
2.4.10 LED (De)activate LED functionality (LED) ............................................................................ 30
3. System implementation........................................................................................................................ 31
3.1 Power supply ................................................................................................................................ 31
3.2 Grounding ..................................................................................................................................... 31
3.3 Mounting on metal....................................................................................................................... 31
3.4 Frequency converters................................................................................................................... 31
4. FCC Statement....................................................................................................................................... 32
4.1 ARE i2.0x LF................................................................................................................................... 32
5. Release, Change Protocol...................................................................................................................... 33

Manual ARE i2.0x LF release V2
Version:
13
Page:
4 / 34
Manual ARE i2.0x LF release V2.docx
1. Introduction
ARE i2.0x LF is a compact industrial reader based on an RS-232 interface. This version is compatible with most LF
applications. ARE i2.0x LF uses an external antenna for communication to the transponder. There are various antenna form
factors available.
Typical system structure
host connection via
RS-232 interface
AAN Xi9F antenna
glass transponder acc. SEMI E144-0312 standard

Manual ARE i2.0x LF release V2
Version:
13
Page:
5 / 34
Manual ARE i2.0x LF release V2.docx
2. ARE i2.0x LF
ARE i2.0x LF works with most LF transponder technologies in ASK, PSK and FSK.
2.1 ARE i2.0x LF hardware
2.1.1 Dimensions ARE i2.0x LF
2.1.2 Protection Class
Protection Class is IP 67, assuming cable or dummy cap is mounted.
2.1.3 AAN Xi9F dimensions
37.1mm | 1.4631 in
114.5mm | 4.50
8 in
30mm | 1.181 in
20mm | 0.787 in
21mm | 0.827 in
12mm | 0.472 in
50mm | 1.969 in
29.2mm | 1.150 in
57.7mm | 2.272 in
90.2mm | 3.551 in

Manual ARE i2.0x LF release V2
Version:
13
Page:
6 / 34
Manual ARE i2.0x LF release V2.docx
2.1.4 Mounting and grounding
Mounting is recommended via the top hat rail connector on the back of the unit.
Note: Grounding of the unit can be achieved by grounding the top hat rail. The top hat rail connector is hooked up to
internal system ground. Alternatively mounting straps are optionally available.
2.1.5 Connectivity:
ARE i2.0x LF is connected via its M12, 5-Pin male A-coded plug. Power supply as well as communication is provided by user.
Do only use specified cables. ARE i2.0x LF uses a LED lit RFID symbol on its front side to visually communicate its various
states (standby, reading, successful read, no read, error, and so on...). When ARE i2.0x LF is hooked up to power, the internal
LED is switched to standby color. LED colors can be set by the user.
PIN 1 – +7V…24V DC
PIN 2 – GND
PIN 3 – RX
PIN 4 – TX
PIN 5 – CGND
LED: Status indication
cable: M12, 5-Pin A-coded, socket to power 2 cables)
and serial interface 3 cables)
Top hat rail
connector
Connected to
internal ground Grounding pin can be
used alternatively to
ground ARE i2.0x

Manual ARE i2.0x LF release V2
Version:
13
Page:
7 / 34
Manual ARE i2.0x LF release V2.docx
The antenna AAN Xi9F is connected via a 3-pin connector on top of ARE i2.0x LF.
ARE i2.0x LF uses an external antenna AAN Xi9F. There are air core coil transponders like disks and ferrite core coil
transponders like glass tube transponders. It is important to understand the impact of orientation of transponders relative
to AAN Xi9F. Optimum orientation is parallel to the top side of the antenna for glass tube transponders. In this orientation,
the highest read range can be achieved.
If it is not possible to ensure such orientation, glass tube transponders can be oriented perpendicular on the outside of the
antenna. This will result in some decrease of read range, but in most cases this is acceptable.
Reading distance depends a lot on the particular installation. Absolute values only make sense based on a particular
transponder. Absolute values make no sense for transponder types, because the values will vary too much. Above are the
guiding principles to achieve the best possible read range.
2.1.6 Read Range for SEMI Applications using AAN Xi9F
Glass transponder acc. to SEMI E144-0312 standard
Glass transponder parallel (recommended)
The highest read range is achieved right above the center of AAN Xi9F front side.
90mm
90mm
90mm
100mm

Manual ARE i2.0x LF release V2
Version:
13
Page:
8 / 34
Manual ARE i2.0x LF release V2.docx
Glass transponder 90° perpendicular
The highest read range is achieved right at the perimeter of the antenna housing.
*note: only one transponder in the field at a time. Above illustration only shows possible read ranges.
60mm
60mm
65mm
65mm
10mm

Manual ARE i2.0x LF release V2
Version:
13
Page:
9 / 34
Manual ARE i2.0x LF release V2.docx
2.2 Firmware ARE i2.0x LF
2.2.1 Instruction Set
Communication with ARE i2.0x LF is based on a simple ASCII text based protocol. The host sends text based telegrams to
ARE i2.0x LF and receives text based telegrams back containing the answer to the query. Communication to ARE i2.0x LF is
always triggered by the host.
2.2.2 General format of instruction set
The protocol format is as follows
Instruction <CR> for instructions without parameter
Instruction <SP> parameter <CR> for instructions with only 1 parameter
Instruction <SP> parameter <SP>data<CR> for instructions with parameter and data
The space character <SP> separates commands from parameters and data and the <CR> character acts as command line
terminator.
instruction<CR> can be used to check the current parameter value for instructions that carry a parameter.
Input Instruction <CR> Answer: Parameter<CR>
2.2.3 BD
BD – Baudrate parameter sets the baudrate for ARE i2.0x. Please Note: Standard parameter is 38.400 baud.
Input format: BD<SP>Parameter<CR>
e.g. BD<SP>3<CR>
Hex:
42
44
20
33
0D
ASCII:
‘B’
‘D’
<SP>
‘3’
<CR>
Output (example):Baudrate 38.400 baud
Hex:
33
0D
ASCII:
‘3’
<CR>
Parameter:
PARAMETER BAUDRATE
0
4.800
1
9.600
2
19.200
3
38.400
4
57.600
5
115.200

Manual ARE i2.0x LF release V2
Version:
13
Page:
10 / 34
Manual ARE i2.0x LF release V2.docx
2.2.4 VER
VER – Reader firmware version
VER is used to get the actual reader firmware version.
Input format: VER <CR>
Hex:
56
45
52
0D
ASCII:
‘V’
‘E’
‘R’
<CR>
Output (example):ARE i2.0x V_1.011 <CR>
Hex:
21
00
15
...
...
31
0D
ASCII:
‘A’
‘R’
‘E’
...
...
‘1’
<CR>
2.2.5 TOR
TOR – Timeout Reading
After a read is triggered by GT, TOR is a time during which ARE i2.0x LF continuously tries to read a transponder UID
without the need to be triggered by the host again. This limits bus traffic considerably. Once a successful read is
performed, continuous reading stops immediately regardless of time and the transponder UID is transmitted to the host.
If reading is not successful, a no read (XXXXXXXXXXXXXXXX) is sent to the host after TOR time has expired.
The chosen parameter for TOR is sent as acknowledgement.
Input format: TOR<SP>50<CR>
Hex:
54
4F
52
20
35
30
0D
ASCII:
‘T’
‘O’
‘R’
<SP>
‘5’
‘0’
<CR>
Output (example):50 <CR>
Hex:
35
30
0D
ASCII:
‘5’
‘0’
<CR>
Parameter:
PARAMETER FUNCTION
0 limits the reading process duration to exactly one reading cycle
1 limits the reading process duration to maximum 1 times 100ms
2 limits the reading process duration to maximum 2 times 100ms
...
255 limits the reading process duration to maximum 255 times 100ms
A TOR value of 50 equals 50 x 100ms = 5000ms = 5 sec.
It is recommended to set TOR value to the amount of time it takes in a dynamic situation for the transponder to travel over
ARE i2.0x LF. This maximizes the number of possible reads, in order to compensate for EMV noise in the vicinity.

Manual ARE i2.0x LF release V2
Version:
13
Page:
11 / 34
Manual ARE i2.0x LF release V2.docx
2.2.6 GT
GT – Get Tag
GT is used to retrieve the transponder UID. GT uses TOR parameter to define the time during which the reader
continuously looks for a transponder without the need for the host to get involved.
In LF application this command can be used to retrieve the carrier ID stored in memory block 1 of LF compatible
transponder.
Input format: GT<CR>
Hex:
47
54
0D
ASCII:
‘G’
‘T’
<CR>
Output (example):1234567812345678 <CR>
Hex:
31
32
33
...
...
38
0D
ASCII:
‘1’
‘2’
‘3’
...
...
‘8’
<CR>
Output (example in case of no transponder in the field): xxxxxxxxxxxxxxxx<CR>
Hex:
78
78
78
...
78
78
0D
ASCII:
‘x’
‘x’
‘x’
...
‘x’
‘x’
<CR>
2.2.7 RD
RD – Read transponder memory page
RD is used to read an individual memory page from a transponder in the field. RD uses TOR parameter during which the
reader continuously looks for a transponder without the need for the host to get involved.
Please see datasheet of transponder for specific memory map. Page is input as decimal.
Input format: RD<SP>page<CR>
RD<SP> 1<CR>
Hex:
52
44
20
31
0D
ASCII:
‘R’
‘D’
<SP>
’1’
<CR>
Output (example in case of a successful read): 1234567812345678<CR>
Hex:
31
32
33
...
...
38
0D
ASCII:
‘1’
‘2’
‘3’
...
...
‘8’
<CR>
Output (example in case of no transponder in the field): xxxxxxxxxxxxxxxx<CR>
Hex:
78
78
78
...
78
78
0D
ASCII:
‘x’
‘x’
‘x’
...
‘x’
‘x’
<CR>

Manual ARE i2.0x LF release V2
Version:
13
Page:
12 / 34
Manual ARE i2.0x LF release V2.docx
2.2.8 WD
WD – Write transponder memory page
WD is used to write to individual memory page of a transponder in the field. WD uses TOR parameter during which the
reader continuously looks for a transponder without the need for the host to get involved.
Please see datasheet of transponder for specific memory map. Page is input as decimal.
Input format: WD<SP>page<SP>data<CR>
WD<SP> 5<SP> 12345678ABCDEF78<CR>
Hex:
57
44
20
35
20
31
...
38
0D
ASCII:
‘W’
‘D’
<SP>
‘5’
<SP>
‘1’
...
’8’
<CR>
Output (example in case of a successful write): ACK<CR>
Hex:
41
43
4B
0D
ASCII:
‘A’
‘C’
‘K’
<CR>
Output (example in case of no transponder in the field): xxxxxxxxxxxxxxxx<CR>
Hex:
78
78
78
...
78
78
0D
ASCII:
‘x’
‘x’
‘x’
...
‘x’
‘x’
<CR>
2.2.9 MD
MD – Read mode
MD is used to either read the chip UID once per trigger by the host (e.g GT command) or read the chip UID continuously
after a trigger by the host until mode is switched back to single read
Parameters: 2 – single read (default) | 0 – continuous read mode
Input format: MD<SP>parameterCR>
MD<SP> 0<CR>
Hex:
4D
44
20
30
0D
ASCII:
‘M’
‘D’
<SP>
’0’
<CR>
Output (example): 0x1<CR>
Hex:
30
0D
ASCII:
‘0’
<CR>

Manual ARE i2.0x LF release V2
Version:
13
Page:
13 / 34
Manual ARE i2.0x LF release V2.docx
2.2.10 NID
NID – Double reading of UID to ensure consistency in EMV polluted environment.
NID is used to double read a transponder UID to ensure consistency in an EMV polluted environment. The transponder UID
is transmitted only after two consecutive reads of the same UID
Parameters: 0 – every UID is transmitted | 1 – UID only transmitted if read twice consecutively
Input format: NID<SP>1<CR>
Hex:
4E
49
44
20
31
ASCII:
‘N’
‘I’
‘D’
<SP>
‘1’
Output (example): 1<CR>
Hex:
31
0D
ASCII:
‘1’
<CR>
2.2.11 CID
CID – Filter same UID numbers to transmit only once via interface
CID is used to filter multiple read transponder UID to transmit only once via interface. There needs to be one different
Transponder UID read before the same number will be transmitted again.
Parameters: 0 – no filter function | 1 – filter same chip UID as previously read
Input format: CID<SP>1<CR>
Hex:
43
49
44
20
31
ASCII:
‘C’
‘I’
‘D’
<SP>
‘1’
Output (example): 0x1<CR>
Hex:
31
0D
ASCII:
‘1’
<CR>
2.2.12 CN
CN – Filter no read from being transmitted via interface.
CN is used in those cases, where no read information ‘XXXXXXXXXXXXXXXX’ is not to appear on the interface. Only valid
transponder UID will be transmitted.
Parameters: 0 – no filter function | 1 – filter no read information from being transmitted

Manual ARE i2.0x LF release V2
Version:
13
Page:
14 / 34
Manual ARE i2.0x LF release V2.docx
Input format: CID<SP>1<CR>
Hex:
43
4E
20
31
ASCII:
‘C’
‘N’
<SP>
‘1’
Output (example): 0x1<CR>
Hex:
31
0D
ASCII:
‘1’
<CR>
2.2.13 LD
LD – lock memory page
LD is used to lock a particular memory page from a transponder in the field.
Input format: LD<SP> 1<CR>
Hex:
4D
44
20
31
0D
ASCII:
‘L’
‘D’
<SP>
’1’
<CR>
Output (example): 1234567812345678<CR> (content of locked memory page)
Hex:
31
32
33
...
...
38
0D
ASCII:
‘1’
‘2’
‘3’
...
...
‘8’
<CR>
If there is an error during locking, the answer will be XXXXXXXXXXXXXXXX<CR>
2.2.14 VSAVE
VSAVE – Save parameter permanently in ARE i2.0 LF flash memory
VSAVE is used to save parameters permanently in flash memory of ARE i2.0 LF to be available after power on.
Input format: VSAVE <CR>
Hex:
56
53
41
56
45
0D
ASCII:
‘V’
‘S’
‘A’
’V’
‘E’
<CR>
Output (example):ACK<CR>
Hex:
41
43
4B
0D
ASCII:
‘A’
‘C’
‘K’
<CR>

Manual ARE i2.0x LF release V2
Version:
13
Page:
15 / 34
Manual ARE i2.0x LF release V2.docx
2.2.15 INIT
INIT – Restore standard parameters. Command needs to be followed up by VSAVE in order to permanently store the
parameters.
Input format: INIT<CR>
Hex:
49
4E
49
54
0D
ASCII:
‘I’
‘N’
‘I’
’T’
<CR>
Output (example):ACK<CR>
Hex:
41
43
4B
0D
ASCII:
‘A’
‘C’
‘K’
<CR>
The following parameters are set:
BD 3 LRD 01001
TOR 50 LNRD 10001
CID 0 LERR 10011
CN 0 LRT 30
MD 2 LPA 00000
LSTB 01101 LED 1
LGT 01111
2.2.16 Error messages
Error messages and protocol errors are acknowledged by ARE i2.0x LF using an error code. The format is described below:
<NAK> '#' <error code> <CR>
Example error #02 (wrong parameter)
Hex:
15
23
30
32
0D
ASCII:
<NAK>
‘#’
‘0’
’2’
<CR>
The error code is comprised of a two digit ASCII coded number.
The following table displays possible error messages:
Error code Meaning
"00" Unknown instruction
"02" Wrong parameter

Manual ARE i2.0x LF release V2
Version:
13
Page:
16 / 34
Manual ARE i2.0x LF release V2.docx
2.3 Firmware ARE i2.0x LF
ARE i2.0x LF works with (all) low frequency transponders in ASK, PSK and FSK modulation. Please see chapter 2.3.15 for
details on which transponder chips are implemented. Depending on the selected algorithms, not all instructions below make
sense so only those which do work accordingly (e.g. write command ‘wd’ does not work for a read only transponder).
2.3.1 Instruction Set
Communication with ARE i2.0x is based on a simple ASCII text based protocol. The host sends text based telegrams to ARE
i2.0x and receives text based telegrams back containing the answer to the query. Communication to ARE i2.0x is always
triggered by the host.
2.3.2 General format of instruction set
The protocol format is as follows
Instruction <CR> for instructions without parameter
Instruction <SP> parameter <CR> for instructions with only 1 parameter
Instruction <SP> parameter <SP>data<CR> for instructions with parameter and data
The space character <SP> separates commands from parameters and data and the <CR> character acts as command line
terminator.
instruction<CR> can be used to check the current parameter value for instructions that carry a parameter.
Input Instruction <CR> Answer: Parameter<CR>
2.3.3 BD
BD – Baudrate parameter sets the baudrate for ARE i2.0x. Please Note: Standard parameter is 38.400 baud.
Input format: BD<SP>Parameter<CR>
e.g. BD<SP>3<CR>
Hex:
42
44
20
33
0D
ASCII:
‘B’
‘D’
<SP>
‘3’
<CR>
Output (example):Baudrate 38.400 baud
Hex:
33
0D
ASCII:
‘3’
<CR>
Parameter:
PARAMETER BAUDRATE
0
4.800
1
9.600
2
19.200
3
38.400
4
57.600
5
115.200

Manual ARE i2.0x LF release V2
Version:
13
Page:
17 / 34
Manual ARE i2.0x LF release V2.docx
2.3.4 VER
VER – Reader firmware version
VER is used to get the actual reader firmware version. .
Input format: VER <CR>
Hex:
56
45
52
0D
ASCII:
‘V’
‘E’
‘R’
<CR>
Output (example):ARE i2.0x V_1.011 <CR>
Hex:
21
00
15
...
...
31
0D
ASCII:
‘A’
‘R’
‘E’
...
...
‘1’
<CR>
2.3.5 GT
GT – Get Tag
GT is used to retrieve the transponder UID.
Input format: GT<CR>
Hex:
47
54
0D
ASCII:
‘G’
‘T’
<CR>
Output (example):12345678 <CR>
Hex:
31
32
33
...
...
38
0D
ASCII:
‘1’
‘2’
‘3’
...
...
‘8’
<CR>
2.3.6 TOR
TOR – Timeout Reading
After a read is triggered by GT, TOR is a time during which ARE i2.0x continuously tries to read a transponder UID
without the need to be triggered by the host again. This limits bus traffic considerably. Once a successful read is
performed, continuous reading stops immediately regardless of time and the transponder UID is transmitted to the host.
If reading is not successful, a no read (XXXXXXXX) is sent to the host after TOR time has expired.
The chosen parameter for TOR is sent as acknowledgement.
Input format: TOR<SP>50<CR>
Hex:
54
4F
52
20
35
30
0D
ASCII:
‘T’
‘O’
‘R’
<SP>
‘5’
‘0’
<CR>
Output (example): 50<CR>
Hex:
35
30
0D
ASCII:
‘5’
‘0’
<CR>

Manual ARE i2.0x LF release V2
Version:
13
Page:
18 / 34
Manual ARE i2.0x LF release V2.docx
Parameter:
PARAMETER FUNCTION
0 limits the reading process duration to exactly one reading cycle
1 limits the reading process duration to maximum 1 times 100ms
2 limits the reading process duration to maximum 2 times 100ms
...
255 limits the reading process duration to maximum 255 times 100ms
A TOR value of 50 equals 50 x 100ms = 5000ms = 5 sec.
It is recommended to set TOR value to the amount of time it takes in a dynamic situation for the transponder to travel over
ARE i2.0x. This maximizes the number of possible reads, in order to compensate for EMV noise in the vicinity.
2.3.7 NID
NID – Double reading of UID to ensure consistency in EMV polluted environment.
NID is used to double read a transponder UID to ensure consistency in an EMV polluted environment. The transponder UID
is transmitted only after two consecutive reads of the same UID
Parameters: 0 – every UID is transmitted | 1 – UID only transmitted if read twice consecutively
Input format: NID<SP>1<CR>
Hex:
4E
49
44
20
31
ASCII:
‘N’
‘I’
‘D’
<SP>
‘1’
Output (example): 1<CR>
Hex:
31
0D
ASCII:
‘1’
<CR>
2.3.8 CID
CID – Filter same UID numbers to transmit only once via interface
CID is used to filter multiple read transponder UID to transmit only once via interface. There needs to be one different
Transponder UID read before the same number will be transmitted again.
Parameters: 0 – no filter function | 1 – filter same chip UID as previously read
Input format: CID<SP>1<CR>
Hex:
43
49
44
20
31
ASCII:
‘C’
‘I’
‘D’
<SP>
‘1’
Output (example): 1<CR>
Hex:
31
0D
ASCII:
‘1’
<CR>

Manual ARE i2.0x LF release V2
Version:
13
Page:
19 / 34
Manual ARE i2.0x LF release V2.docx
2.3.9 CN
CN – Filter no read from being transmitted via interface.
CN is used in those cases, where no read information ‘XXXXXXXX’ is not to appear on the interface. Only valid transponder
UID will be transmitted.
Parameters: 0 – no filter function | 1 – filter no read information from being transmitted
Input format: CID<SP>1<CR>
Hex:
43
4E
20
31
ASCII:
‘C’
‘N’
<SP>
‘1’
Output (example): 1<CR>
Hex:
31
0D
ASCII:
‘1’
<CR>
2.3.10 RD
RD – Read transponder memory page
RD is used to read an individual memory page from a transponder in the field.
Input format: RD<SP> 1<CR>
Hex:
52
44
20
31
0D
ASCII:
‘R’
‘D’
<SP>
’1’
<CR>
Output (example): 12345678<CR>
Hex:
31
32
33
...
...
38
0D
ASCII:
‘1’
‘2’
‘3’
...
...
‘8’
<CR>
2.3.11 WD
WD – Write transponder memory page
WD is used to write to individual memory page from a transponder in the field.
Input format: WD<SP> 5<SP> 12345678<CR>
Hex:
57
44
20
35
20
31
...
38
0D
ASCII:
‘W’
‘D’
<SP>
‘5’
<SP>
‘1’
...
’8’
<CR>
Output (example): 12345678<CR>
Hex:
31
32
33
...
...
38
0D
ASCII:
‘1’
‘2’
‘3’
...
...
‘8’
<CR>

Manual ARE i2.0x LF release V2
Version:
13
Page:
20 / 34
Manual ARE i2.0x LF release V2.docx
2.3.12 VSAVE
VSAVE – Save parameter permanently in ARE i2.0x flash memory
VSAVE is used to save parameters permanently in flash memory of ARE i2.0x to be available after power on.
Input format: VSAVE <CR>
Hex:
56
53
41
56
45
0D
ASCII:
‘V’
‘S’
‘A’
’V’
‘E’
<CR>
Output (example):ACK<CR>
Hex:
41
43
4B
0D
ASCII:
‘A’
‘C’
‘K’
<CR>
2.3.13 INIT
INIT – Restore standard parameters. Command needs to be followed up by VSAVE in order to permanently store the
parameters.
Input format: INIT<CR>
Hex:
49
4E
49
54
0D
ASCII:
‘I’
‘N’
‘I’
’T’
<CR>
Output (example):ACK<CR>
Hex:
41
43
4B
0D
ASCII:
‘A’
‘C’
‘K’
<CR>
The following parameters are set:
TOR 50 LRD 01001
MD 2 LNRD 10001
CID 0 LERR 10011
CN 0 LED 1
LSTB 01101 LRT 30
LGT 01111 LPA 00000