AEG ID i2.0x LF Compact Industrial Reader Instruction Manual
- September 27, 2024
- AEG ID
Table of Contents
Manual
ARE i2.0x LF
AEG is a registered trademark used
under license from AB Electrolux (publ)
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
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
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 – +12V…24V DC
PIN 2 – GND
PIN 3 – RX
PIN 4 – TX
PIN 5 – n/c
LED: Status indication cable: M12, 5-Pin A-coded, socket to power 2 cables)
and serial interface 3 cables)
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 Transponder orientation relative to AAN Xi9F
Disk 90° (recommended) Glass trans ponder parallel (recommended)
The highest read range is achieved right above the
center of AAN Xi9F front side.
In this orientation both transponder types are read best just outside the
perimeter of AAN Xi9F. There is a significantly reduced read range in the
center of AAN Xi9F. This is no problem in a dynamic situation. Please ensure
to start reading before the transponder is above AAN Xi9F and keep reading
until the transponder is beyond AAN Xi9F. 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 is the guiding principles to
achieve the best possible read range.
2.1.7 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.
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.
2.2 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.2.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.2.2 General format of instruction set
The protocol format is as follows
Instruction
Instruction
Instruction
The space character
| Hex: | 42 | 44 | 20 | 32 | 0D |
|---|---|---|---|---|---|
| ASCII: | ‘B’ | ‘D’ | ‘2’ |
Output (example): Baudrate 38.400 baud
Hex: ASCII:
| Hex: | 32 | 0D |
|---|---|---|
| ASCII: | ‘2’ |
Parameter:
| PARAMETER | BAUDRATE |
|---|---|
| 0 | 4.800 |
| 1 | 9.600 |
| 2 | 19.200 |
| 3 | 38.400 |
| 4 | 57.600 |
| 5 | 115.200 |
2.2.4 VER
VER – Reader firmware version
VER is used to get the actual reader firmware version. .
Input format: VER
Hex:
ASCII:
| Hex: | 56 | 45 | 52 | 0D |
|---|---|---|---|---|
| ASCII: | ‘V’ | ‘E’ | ‘R’ |
Output (example): ARE i2.0x V_1.011
| Hex: | 21 | 00 | 15 | … | … | 31 | 0D |
|---|---|---|---|---|---|---|---|
| ASCII: | ‘A’ | ‘R’ | ‘E’ | … | … | ‘1’ |
2.2.5 GT
GT – Get Tag
GT is used to retrieve the transponder UID.
Input format: GT
| Hex: | 47 | 54 | 0D |
|---|---|---|---|
| ASCII: | ‘G’ | ‘T’ |
Output (example): 12345678
| Hex: | 31 | 32 | 33 | … | … | 38 | 0D |
|---|---|---|---|---|---|---|---|
| ASCII: | ‘1’ | ‘2’ | ‘3’ | … | … | ‘8’ |
2.2.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
| Hex: | 54 | 4F | 52 | 20 | 35 | 30 | 0D |
|---|---|---|---|---|---|---|---|
| ASCII: | ‘T’ | ‘O’ | ‘R’ | ‘5’ | ‘0’ |
Output (example): 50
| Hex: | 35 | 30 | 0D |
|---|---|---|---|
| ASCII: | ‘5’ | ‘0’ |
Perametar
| 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.2.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
| Hex: | 4E | 49 | 44 | 20 | 31 |
|---|---|---|---|---|---|
| ASCII: | ‘N’ | ‘I’ | ‘D’ | ‘1’ |
Output (example): 1
| Hex: | 31 | 0D |
|---|---|---|
| ASCII: | ‘1’ |
2.2.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
| Hex: | 43 | 49 | 44 | 20 | 31 |
|---|---|---|---|---|---|
| ASCII: | ‘C’ | ‘I’ | ‘D’ | ‘1’ |
Output (example): 1
| Hex: | 31 | 0D |
|---|---|---|
| ASCII: | ‘1’ |
2.2.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
| Hex: | 43 | 4E | 20 | 31 |
|---|---|---|---|---|
| ASCII: | ‘C’ | ‘N’ | ‘1’ |
Output (example): 1
| Hex: | 31 | 0D |
|---|---|---|
| ASCII: | ‘1’ |
2.2.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
| Hex: | 52 | 44 | 20 | 31 | 0D |
|---|---|---|---|---|---|
| ASCII: | ‘R’ | ‘D’ | ’1’ |
Output (example): 12345678
| Hex: | 31 | 32 | 33 | … | … | 38 | 0D |
|---|---|---|---|---|---|---|---|
| ASCII: | ‘1’ | ‘2’ | ‘3’ | … | … | ‘8’ |
2.2.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
| Hex: | 57 | 44 | 20 | 35 | 20 | 31 | … | 38 | 0D |
|---|---|---|---|---|---|---|---|---|---|
| ASCII: | ‘W’ | ‘D’ | ‘5’ | ‘1’ | … | ’8’ |
Output (example): 12345678
| Hex: | 31 | 32 | 33 | … | … | 38 | 0D |
|---|---|---|---|---|---|---|---|
| ASCII: | ‘1’ | ‘2’ | ‘3’ | … | … | ‘8’ |
2.2.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
| Hex: | 56 | 53 | 41 | 56 | 45 | 0D |
|---|---|---|---|---|---|---|
| ASCII: | ‘V’ | ‘S’ | ‘A’ | ’V’ | ‘E’ |
Output (example): ACK
| Hex: | 41 | 43 | 4B | 0D |
|---|---|---|---|---|
| ASCII: | ‘A’ | ‘C’ | ‘K’ |
2.2.13 INIT
INIT – Restore standard parameters. Command needs to be followed up by
VSAVE in order to permanently store the parameters.
Input format: INIT
| Hex: | 49 | 4E | 49 | 54 | 0D |
|---|---|---|---|---|---|
| ASCII: | ‘I’ | ‘N’ | ‘I’ | ’T’ |
Output (example): ACK
| Hex: | 41 | 43 | 4B | 0D |
|---|---|---|---|---|
| ASCII: | ‘A’ | ‘C’ | ‘K’ |
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 |
2.2.14 Error messages
Error messages and protocol errors are acknowledged by ARE i2.0x using an
error code. The format is described below:
| Hex: | 15 | 23 | 30 | 32 | 0D |
|---|---|---|---|---|---|
| ASCII: | ‘#’ | ‘0’ | ’2’ |
The error code is comprised of a two digit ASCII coded number. Please note
that for communication through ACM 9, the appropriate reader number is
preceding the error message.
The following table displays possible error messages:
| Error code | Meaning |
|---|---|
| “00” | Unknown instruction |
| “02” | Wrong parameter |
2.2.15 ALGO
ALGO is used to activate one particular LF algorithm to be used in a
particular installation.
Input format: ALGO
Example: ALGO
| Hex: | 41 | 4C | 47 | 4F | 20 | 31 | 0D |
|---|---|---|---|---|---|---|---|
| ASCII: | ‘A’ | ‘L’ | ‘G’ | ‘O’ | ‘1’ |
Output (example): 1
| Hex: | 31 | 0D |
|---|---|---|
| ASCII: | ‘1’ |
Above example activates algorithms 1
Implemented LF algorithms:
1 – PSK1, Trovan
4 – ASK 64 Bit Manchester
5 – ISO 11784/85
6 – Hitag1/HitagS
8 – Hitag2
14 – EM4305
23 – HDX (TI)
29- HDX (AEG ID)
32- PSK1 and HDX in mixed population based on a ‘gt’ request
2.2.16 LOG (EM4305 chip specific)
EM 4305
EM 4305 is a multi purpose chip from EM microelectronic Marin.
It features 512 bit memory and can be configured to transmit in ASK 64-bit
Manchester, PSK1, Trovan, ISO 11784/85 fdx-b, pigeon mode among others or work
as a simple memory chip.
In addition to above commands the chip uses the following chip specific
commands.
LOG is used to log into a password protected chip. (see chip data sheet for
details). Standard password is 0x00000000.
Input format: LOG
Example: LOG
| Hex: | 4C | 4F | 47 | 20 | 30 | 30 | … | 30 | 0D |
|---|---|---|---|---|---|---|---|---|---|
| ASCII: | ‘L’ | ‘O’ | ‘G’ | ‘0’ | ‘0’ | … | ‘0’ |
Output (example): ACK
| Hex: | 41 | 43 | 4B | 0D |
|---|---|---|---|---|
| ASCII: | ‘A’ | ‘C’ | ‘K’ |
This answer is sent if everything went ok.
Output (example): NAK
| Hex: | 4E | 41 | 4B | 0D |
|---|---|---|---|---|
| ASCII: | ‘N’ | ‘A’ | ‘K’ |
This answer is sent if login failed.
2.2.17 PWD (EM4305 chip specific)
PWD is used to change the password for the chip. Please make sure to log
into the transponder first using the LOG command and the current password.
Only then can the password be changed. Standard password is 0x00000000.
Input format: PWD
Example: PWD
| Hex: | 50 | 57 | 44 | 20 | 30 | 31 | … | 37 | 0D |
|---|---|---|---|---|---|---|---|---|---|
| ASCII: | ‘P’ | ‘W’ | ‘D’ | ‘0’ | ‘1’ | … | ‘7’ |
Output (example): ACK
| Hex: | 41 | 43 | 4B | 0D |
|---|---|---|---|---|
| ASCII: | ‘A’ | ‘C’ | ‘K’ |
This answer is sent if everything went ok.
Output (example): NAK
| Hex: | 4E | 41 | 4B | 0D |
|---|---|---|---|---|
| ASCII: | ‘N’ | ‘A’ | ‘K’ |
This answer is sent if password change failed.
2.2.18 LD (EM4305 chip specific)
After the chip is configured correctly, it may be necessary to lock
specific memory blocks of EM 4305. Memory blocks from 0 to 13 can be locked.
Memory pages 14 and 15 serve as lock data (see chip data sheet for details).
Protection word 1 is factory set, as it contains the chip UID. Memory pages 0,
2-13 can be locked by the user. This is OTP, so once locked, it can not be
undone.
Input format: LD
| Hex: | 4C | 44 | 20 | 30 | … | 30 | 37 | 32 | 0D |
|---|---|---|---|---|---|---|---|---|---|
| ASCII: | ‘L’ | ‘D’ | ‘0’ | … | ‘0’ | ‘7’ | ‘2’ |
Output (example): ACK
| Hex: | 41 | 43 | 4B | 0D |
|---|---|---|---|---|
| ASCII: | ‘A’ | ‘C’ | ‘K’ |
This answer is sent if lock data went ok.
Output (example): NAK
| Hex: | 4E | 41 | 4B | 0D |
|---|---|---|---|---|
| ASCII: | ‘N’ | ‘A’ | ‘K’ |
This answer is sent if something went wrong during lock data.
Above example locks memory pages 4, 5 and 6. Memory page 1 is factory set, as
is the protection status bit.
2.3 LED instruction set
ARE i2.0x LF employs a multi-color LED to signal different modes.
Basically below colors can be created:
The user can choose any color apart from white. This color is reserved for
setup help functionality as described below.
The following modes use a distinct color each.
– Standby (LSTB)
– Reading (LGT)
– Transponder number successfully read (LRD)
– No Read (LNRD)
– Error (LERR)
– Process active (LPA)
– Process status (LPS)
In addition, the user can choose to switch on the LED permanently or flashing.
The following instruction set is used:
Mode
R – Red
G – Green
B – Blue
F – Flash
X – LED functionality ON or OFF for this mode
Allowed parameters are 1 (on) or 0 (off)
Default colors are shown with the instructions.
2.3.1 LED Standby (LSTB)
Standby color is Cyan, no flash.
Input format: LSTB
| Hex: | 4C | 53 | 54 | 42 | 20 | 30 | … | 31 | 0D |
|---|---|---|---|---|---|---|---|---|---|
| ASCII: | ‘L’ | ‘S’ | ‘T’ | ‘B’ | ‘0’ | … | ’1’ |
Output: 01101
| Hex: | 30 | 31 | 31 | 30 | 31 | 0D |
|---|---|---|---|---|---|---|
| ASCII: | ‘0’ | ‘1’ | ‘1’ | ‘0’ | ‘1’ |
Standby mode is active if no other instructions are carried out.
If Standby LED is switched off, the LED will be active for 10 seconds after
reboot in its last color scheme and then it will be switched off.
2.3.2 LED Reading (LGT)
Reading color is Cyan, flashing
Input format: LGT
| Hex: | 4C | 47 | 54 | 20 | 30 | 31 | … | 31 | 0D |
|---|---|---|---|---|---|---|---|---|---|
| ASCII: | ‘L’ | ‘G’ | ‘T’ | ‘0’ | ‘1’ | … | ’1’ |
Output: 01111
| Hex: | 30 | 31 | 31 | 31 | 31 | 0D |
|---|---|---|---|---|---|---|
| ASCII: | ‘0’ | ‘1’ | ‘1’ | ‘1’ | ‘1’ |
Reading mode is active for the duration of the TOR parameter. It will stop
prematurely only to show a successful read using the respective color. At the
end of the TOR parameter it will show the no read mode LED color.
2.3.3 LED Transponder number successfully read (LRD)
Successful read color is green, no flash
Input format: LRD
| Hex: | 4C | 52 | 44 | 20 | 30 | 31 | … | 31 | 0D |
|---|---|---|---|---|---|---|---|---|---|
| ASCII: | ‘L’ | ‘R’ | ‘D’ | ‘0’ | ‘1’ | … | ’1’ |
Output: 01001
| Hex: | 30 | 31 | 30 | 30 | 31 | 0D |
|---|---|---|---|---|---|---|
| ASCII: | ‘0’ | ‘1’ | ‘0’ | ‘0’ | ‘1’ |
Successful read mode is active for LRT seconds, after which the standby mode
will be active again.
2.3.4 LED No Read (LNRD)
No Read color is red, no flash
Input format: LNRD
| Hex: | 4C | 4E | 52 | 44 | 20 | 31 | … | 31 | 0D |
|---|---|---|---|---|---|---|---|---|---|
| ASCII: | ‘L’ | ‘N’ | ‘R’ | ‘D’ | ‘1’ | … | ’1’ |
Output: 10001
| Hex: | 31 | 30 | 30 | 30 | 31 | 0D |
|---|---|---|---|---|---|---|
| ASCII: | ‘1’ | ‘0’ | ‘0’ | ‘0’ | ‘1’ |
No Read mode is active after TOR seconds for LRT seconds, after which the
standby mode will be active again.
2.3.5 LED Return to standby (LRT)
Some modes require ARE i2.0x LF to go back to standby. The time until this
happens is set by using the LRT command.
Input format: LRT
Hex:| 4C| 52| 54| 20| 33| 30| 0D| |
---|---|---|---|---|---|---|---|---|---
ASCII:| ‘L’| ‘R’| ‘T’|
Output: 30
| Hex: | 33 | 30 | 0D |
|---|---|---|---|
| ASCII: | ‘3’ | ‘0’ |
LRT
2.3.6 LED Error (LERR)
Error color is red, flashing
Input format: LERR
| Hex: | 4C | 45 | 52 | 52 | 20 | 31 | … | 31 | 0D |
|---|---|---|---|---|---|---|---|---|---|
| ASCII: | ‘L’ | ‘E’ | ‘R’ | ‘R’ | ‘1’ | … | ’1’ |
Output: 10011
| Hex: | 31 | 30 | 30 | 31 | 31 | 0D |
|---|---|---|---|---|---|---|
| ASCII: | ‘1’ | ‘0’ | ‘0’ | ‘1’ | ‘1’ |
Error mode is triggered by an error of ARE i2.0x LF and is active until a
correct instruction is received.
2.3.7 LED Process active
In case of multiple commands being sent to the chip (e.g. rd and wd
instructions), it may be necessary to control LED functionality manually. The
LED Process active instruction sets the LED to a defined color and mode. This
color and mode stays on as long as the LED Process active parameter is
switched on. Normal LED functionality is discontinued during the activity of
this parameter. LED functionality returns to normal only when LED Process
active is switched off via its X parameter.
Activating Process active
LED color is yellow, flashing
Input format: LPA
| Hex: | 4C | 50 | 41 | 20 | 31 | … | … | 31 | 0D |
|---|---|---|---|---|---|---|---|---|---|
| ASCII: | ‘L’ | ‘P’ | ‘A’ | ‘1’ | … | … | ’1’ |
Output: 11011
| Hex: | 31 | 31 | 30 | 31 | 31 | 0D |
|---|---|---|---|---|---|---|
| ASCII: | ‘1’ | ‘1’ | ‘0’ | ‘1’ | ‘1’ |
Deactivating Process active
LED color doesn’t care, because parameter is switched off using X parameter
Input format: LPA
| Hex: | 4C | 50 | 41 | 20 | 31 | … | … | 30 | 0D |
|---|---|---|---|---|---|---|---|---|---|
| ASCII: | ‘L’ | ‘P’ | ‘A’ | ‘1’ | … | … | ’0’ |
Output: 11010
| Hex: | 31 | 31 | 30 | 31 | 30 | 0D |
|---|---|---|---|---|---|---|
| ASCII: | ‘1’ | ‘1’ | ‘0’ | ‘1’ | ‘0’ |
2.3.8 LED Process status
LED Process status is used to indicate the status of a process, after it is
performed.
Successful Process
LED color is green, not flashing
Input format: LPS
| Hex: | 4C | 53 | 54 | 20 | 30 | 31 | … | 31 | 0D |
|---|---|---|---|---|---|---|---|---|---|
| ASCII: | ‘L’ | ‘P’ | ‘S’ | ‘0’ | ’1’ | … | ’1’ |
Output: 01001
| Hex: | 30 | 31 | 30 | 30 | 31 | 0D |
|---|---|---|---|---|---|---|
| ASCII: | ‘0’ | ‘1’ | ‘0’ | ‘0’ | ‘1’ |
Not Successful Process
LED color is red, not flashing
Input format: LPS
| Hex: | 4C | 53 | 54 | 20 | 31 | 30 | … | 31 | 0D |
|---|---|---|---|---|---|---|---|---|---|
| ASCII: | ‘L’ | ‘P’ | ‘S’ | ‘1’ | ’0’ | … | ’1’ |
Output: 10001
| Hex: | 31 | 30 | 30 | 30 | 31 | 0D |
|---|---|---|---|---|---|---|
| ASCII: | ‘1’ | ‘0’ | ‘0’ | ‘0’ | ‘1’ |
LPS stays on for LRT seconds and then returns to standby.
2.3.9 LED Setup help (FLED)
In order to locate the respective ARE i2.0 LF hooked up to a particular RS 232
port, the instruction FLED is used.
This instruction flashes the LED in white for 10 seconds. The color can not be
changed.
Input format: FLED
| Hex: | 4C | 53 | 54 | 42 | 0D |
|---|---|---|---|---|---|
| ASCII: | ‘F’ | ‘L’ | ‘E’ | ‘D’ |
Output: FLED
| Hex: | 4C | 53 | 54 | 42 | 0D |
|---|---|---|---|---|---|
| ASCII: | ‘F’ | ‘L’ | ‘E’ | ‘D’ |
After flashing for 10 seconds ARE i2.0x LF returns to standby mode.
2.3.10 LED (De)activate LED functionality (LED)
In order to deactivate (or activate) the LED functionality, LED instruction is
used.
Input format: LED
Hex:| 53| 54| 42| 20| 30| OD| | |
---|---|---|---|---|---|---|---|---|---
ASCII:| ‘L’| ‘E’| ‘D’|
Output: 0
| Hex: | 30 | 0D |
|---|---|---|
| ASCII: | ‘0’ |
LED
LED
Above examples represent ARE i2.0 LF default values.
System implementation
3.1 Power supply
It is important for system integration to make sure that power supply for
ARE i2.0x LF is absolutely stable and clean with no noise. It is recommended
to use linear power supplies rather than switching power supplies. All other
applications benefit from this as well.
3.2 Grounding
Please make absolutely sure that ARE i2.0x LF is properly grounded. This
ensures proper functionality of the entire system comprising of ARE i2.0x LF
and AAN Xi9F. Please see chapter 2.1.4 for details on grounding.
Grounding can be achieved by grounding DIN hat rail, as clamp on backside of
ARE i2.0x LF is connected to ground. Alternatively, the grounding pin on the
frontside of ARE i2.0x LF can be used to achieve this.
3.3 Mounting on metal
ARE i2.0x LF is typically mounted on a metal DIN hat rail in a metal
electrical cabinet. There is no influence of metal on performance of ARE i2.0x
LF and therefore nothing to watch out for.
It is recommended to mount AAN Xi9F onto a non-conductive surface. However,
AAAN Xi9F is designed to work when mounted on metal as well. There is a slight
decrease in read/write range when compared to mounting on non-conductive
surfaces, but in most cases the read/write range will still be plenty for the
application.
3.4 Frequency converters
Frequency converters used in electronic motors are a source of significant
EMV noise. Make sure to stay away as far as possible from those frequency
converters when designing spots where ARE i2.0x LF to be used. Noise from
frequency
converters significantly reduce read range of ARE i2.0x LF.
FCC Statement
4.1 ARE i2.0x LF
Valid for ARE i2.0x LF
Federal Communications Commissions (FCC) Statement §15.21
You are cautioned that changes or modifications not expressly approved by the
part responsible for compliance could void the user’s authority to operate the
equipment.
§15.105 Information to the user.
Note: This equipment has been tested and found to comply with the limits
for a Class B digital device, pursuant to part 15 of the FCC Rules. These
limits are designed to provide reasonable protection against harmful
interference in a residential installation. This equipment generates, uses and
can radiate radio frequency energy and, if not installed and used in
accordance with the instructions, may cause harmful interference to radio
communications. 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 to correct the
interference by one or more of the following measures:
—Reorient or relocate the receiving antenna.
—Increase the separation between the equipment and receiver.
—Connect the equipment into an outlet on a circuit different from that to
which the receiver is connected.
—Consult the dealer or an experienced radio/TV technician for help.
Release, Change Protocol
| Revision: | Date: | Changes: | Author: |
|---|---|---|---|
| 01 | 28.05.2023 | Release first edition | NK |
| 02 | 09.06.2023 | Details added | NK |
| 03 | 21.09.2023 | Details added | NK |
| 04 | 01.02.2024 | Corrections | NK |
| 05 | 08.5.2024 | Details added | NK |
AEG Identifikationssysteme GmbH
Hörvelsinger Weg 47
89081 Ulm
Tel.: +49 731 14 00 88 – 0
Email: sales@aegid.de
Web: www.aegid.de
AEG is a registered trademark used under license from AB Electrolux (publ)
References
Read User Manual Online (PDF format)
Read User Manual Online (PDF format) >>