AEG ARE i2.0x HF Stationary RFID Reader User Manual
- May 15, 2024
- AEG
Table of Contents
AEG ARE i2.0x HF Stationary RFID Reader
Product Information
Specifications
ARE i2.0x HF
- Dimensions: 37.1mm x 57.7mm x 90.2mm
- Protection Class: IP 67 (with cable or dummy cap mounted)
- Connectivity: M12, 5-Pin male A-coded plug
- Read Range for HF Applications: Achieved above the centre of AAN Xi9F HF antenna
Antenna AAN Xi9F HF
- Dimensions: 29.2mm x 50mm x 21mm
Product Usage Instructions
Mounting and Grounding
Mount ARE i2.0x HF via the top hat rail connector on the back of the unit.
Ensure proper grounding by connecting to the internal ground via the grounding
pin or top hat rail connector.
Connectivity
Connect ARE i2.0x HF using the provided M12, 5-Pin male A-coded plug. Use
specified cables for power supply and communication. The front LED symbol
indicates various states, and LED colours can be set by the user.
Read Range Optimization
For optimal read range in HF applications, ensure the transponder (40mm x 40mm
x 5mm) is perpendicular to the AAN Xi9F HF antenna.
FAQ
-
Q: How do I change the LED colors on ARE i2.0x HF?
A: LED colours can be set by the user. Refer to the product manual for detailed instructions on changing LED colours. -
Q: What is the recommended method for grounding i2.0x HF?
A: Grounding can be achieved by connecting the unit to the internal ground via the grounding pin or top hat rail connector.
AEG is a registered trademark used under license from AB Electrolux (publ).
Introduction
ARE i2.0x HF is a compact industrial reader based on an RS-232 interface. This version is compatible with ISO 15693 applications. ARE i2.0x HF uses an external antenna for communication to the transponder. There are various antenna form factors available.
Typical system structure
ARE i2.0x HF
ARE i2.0x HF works with transponders that comply with HF standard ISO 15693.
ARE i2.0x HF hardware
Dimensions ARE i2.0x HF
Protection Class
The protection Class is IP 67, assuming a cable or dummy cap is mounted.
AAN Xi9F HF dimensions
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 the internal system ground. Alternatively,
mounting straps are optionally available.
Connectivity:
ARE i2.0x HF is connected via its M12, 5-Pin male A-coded plug. Power supply
as well as communication is provided by the user. Do only use specified
cables. ARE i2.0x HF uses a 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 HF is hooked up to power, the internal LED
is switched to standby colour. LED colours 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)
The antenna AAN Xi9F HF is connected via a 2-pin connector on top of ARE i2.0x HF.
ARE i2.0x HF uses an external antenna AAN Xi9F HF. 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 the orientation of transponders relative to AAN Xi9F HF. The optimum orientation is perpendicular to the top side of the antenna for air-core coil transponders. In this orientation, the highest read range can be achieved. 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.
Read Range for HF Applications using AAN Xi9F HF
- Transponder acc. to ISO 15693 (40mm x 40mm x 5mm) transponder perpendicular (recommended)
- The highest read range is achieved right above the centre of the AAN Xi9F top side.
- Note: only one transponder in the field at a time. The above illustration only shows possible read ranges.
Firmware ARE i2.0x HF
Instruction Set
Communication with ARE i2.0x HF is based on a simple ASCII text-based
protocol. The host sends text-based telegrams to ARE i2.0x HF and receives
text-based telegrams back containing the answer to the query. Communication to
ARE i2.0x HF is always triggered by the host.
General format of instruction set
The protocol format is as follows
- Instruction
for instructions without parameter - Instruction
parameter for instructions with only 1 parameter - Instruction
parameter data for instructions with parameter and data
The space character
instruction
- Input Instruction
Answer: Parameter
BD
BD
Baudrate parameter sets the baudrate for ARE i2.0x. Please Note: Standard
parameter is 19.200 baud.
Input format: BD
Hex: | 42 | 44 | 20 | 32 | 0D |
---|---|---|---|---|---|
ASCII: | ‘B’ | ‘D’ | ‘2’ |
Output (example): Baudrate 38.400 baud
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 |
VER
- VER – Reader firmware version
- VER is used to get the actual reader firmware version.
Input format: VER
Hex: | 56 | 45 | 52 | 0D |
---|---|---|---|---|
ASCII: | ‘V’ | ‘E’ | ‘R’ |
Output (example): ARE i2.0x HF V_1.065
Hex: | 21 | 00 | 15 | … | 36. | 35 | 0D |
---|---|---|---|---|---|---|---|
ASCII: | ‘A’ | ‘R’ | ‘E’ | … | ‘6’ | ‘5’ |
TOR
TOR – Timeout Reading
After a read is triggered by GT, TOR is a time during which ARE i2.0x HF
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’ |
Parameter:
PARAMETER | FUNCTION |
---|---|
0 | limits the reading process duration to exactly one reading cycle |
1 | limits the reading process duration to a maximum of 1 time 100 |
2 | limits the reading process duration to a maximum of 2 times 100 |
… | |
255 | limits the reading process duration to a maximum of 255 times 100 |
- A TOR value of 50 equals 50 x 100ms = 5000ms = 5 sec.
- It is recommended to set the TOR value to the amount of time it takes in a dynamic situation for the transponder to travel over ARE i2.0 HF. This maximizes the number of possible reads, to compensate for EMV noise in the vicinity.
GT
GT – Get Tag
GT is used to retrieve the transponder UID. GT uses the TOR parameter to
define the time during which the reader continuously looks for a transponder
without the need for the host to get involved.
Input format: GT
Hex: | 47 | 54 | 0D |
---|---|---|---|
ASCII: | ‘G’ | ‘T’ |
Output (example in case of a successful read): E0080100002B3706
Hex: | 45 | 30 | 30 | … | 30 | 36 | 0D |
---|---|---|---|---|---|---|---|
ASCII: | ‘E’ | ‘0’ | ‘0’ | … | ‘0’ | ‘6’ |
Output (example in case of no transponder in the field): XXXXXXXX
Hex: | 58 | 58 | 58 | … | 58 | 58 | 0D |
---|---|---|---|---|---|---|---|
ASCII: | ‘X’ | ‘X’ | ‘X’ | … | ‘X’ | ‘X’ |
RD
RD – Read the transponder memory page
RD is used to read an individual memory page from a transponder in the field.
RD uses the TOR parameter during which the reader continuously looks for a
transponder without the need for the host to get involved. Please see the
datasheet of the transponder for sa pecific memory map. Page is input as a hex
number.
Input format:
- RD
page - RD
1
Hex: | 52 | 44 | 20 | 31 | 0D |
---|---|---|---|---|---|
ASCII: | ‘R’ | ‘D’ | ’1’ |
Output (example in case of a successful read): 1234567812345678
Hex: | 31 | 32 | 33 | … | … | 38 | 0D |
---|---|---|---|---|---|---|---|
ASCII: | ‘1’ | ‘2’ | ‘3’ | … | … | ‘8’ |
Output (example in case of no transponder in the field): XXXXXXXX
Hex: | 58 | 58 | 58 | … | 58 | 58 | 0D |
---|---|---|---|---|---|---|---|
ASCII: | ‘X’ | ‘X’ | ‘X’ | … | ‘X’ | ‘X’ |
WD
- WD – Write transponder memory page
- WD is used to write to individual memory pages of a transponder in the field. WD uses a TOR parameter during which the reader continuously looks for a transponder without the need for the host to get involved.
Please see the datasheet of the transponder for a specific memory map. Page is input as a hex number.
Input format:
- WD
page data - WD
5 12345678ABCDEF78
Hex: | 57 | 44 | 20 | 35 | 20 | 31 | … | 38 | 0D |
---|---|---|---|---|---|---|---|---|---|
ASCII: | ‘W’ | ‘D’ | ‘5’ | ‘1’ | … | ’8’ |
Output (example in case of a successful write): ACK
Hex: | 41 | 43 | 4B | 0D |
---|---|---|---|---|
ASCII: | ‘A’ | ‘C’ | ‘K’ |
Output (example in case of no transponder in the field): XXXXXXXX
Hex: | 58 | 58 | 58 | … | 58 | 58 | 0D |
---|---|---|---|---|---|---|---|
ASCII: | ‘X’ | ‘X’ | ‘X’ | … | ‘X’ | ‘X’ |
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
the mode is switched back to a single read
Parameters:
- 2– single read (default)
- 0 – continuous read mode
Input format:
- MD
parameterCR> - MD
0
Hex: | 4D | 44 | 20 | 30 | 0D |
---|---|---|---|---|---|
ASCII: | ‘M’ | ‘D’ | ’0’ |
Output (example): 0x1
Hex: | 30 | 0D |
---|---|---|
ASCII: | ‘0’ |
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 the 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 the same chip UID as previously read
Input format: CID
Hex: | 43 | 49 | 44 | 20 | 31 |
---|---|---|---|---|---|
ASCII: | ‘C’ | ‘I’ | ‘D’ | ‘1’ |
Output (example): 0x1
Hex: | 31 | 0D |
---|---|---|
ASCII: | ‘1’ |
CN
- CN – Filter no read from being transmitted via interface.
- CN is used in those cases, where no read information ‘xxxxxxxx’ should not 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: CN
Hex: | 43 | 4E | 20 | 31 |
---|---|---|---|---|
ASCII: | ‘C’ | ‘N’ | ‘1’ |
Output (example): 0x1
Hex: | 31 | 0D |
---|---|---|
ASCII: | ‘1’ |
VSAVE
- VSAVE – Save parameter permanently in ARE i2.0x HF flash memory
- VSAVE is used to save parameters permanently in the flash memory of ARE i2.0x HF to be available after power is 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’ |
INIT
INIT – Restore standard parameters. The command needs to be followed up by
VSAVE 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:
- 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
Error messages
- Error messages and protocol errors are acknowledged by ARE i2.0 HF using an error code. The format is described below:
-
‘#’
Example error #02 (wrong parameter)
Hex: | 15 | 23 | 30 | 32 | 0D |
---|---|---|---|---|---|
ASCII: | ‘#’ | ‘0’ | ’2’ |
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 |
LED instruction set
- Is i2.0 HF employing a multi-colour LED to signal different modes?
- Basically below colors can be created:
The user can choose any colour apart from white. This color is reserved for setup help functionality as described below.
The following modes use a distinct colour 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 colours are shown with the instructions.
LED Standby (LSTB)
The standby colour 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 the Standby LED is switched off, the LED will be active for 10 seconds after reboot in its last colour scheme and then it will be switched off.
LED Reading (LGT)
The reading colour 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 colour. At the end of the TOR parameter, it will show the no-read mode LED colour.
LED Transponder number successfully read (LRD)
Successful read colour 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.
LED No Read (LNRD)
No Read colour 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.
LED Return to standby (LRT)
Some modes require ARE i9 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
LED Error (LERR)
The 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 i9 and is active until a correct instruction is received.
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 colour and mode. This
colour and mode stay 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 the LED Process
active is switched off via its X parameter.
Activating Process active
LED colour 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 colour doesn’t care, because the parameter is switched off using the 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’ |
LED Process status
LED Process status is used to indicate the status of a process after it is
performed.
Successful Process
LED colour 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 colour 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.
LED Setup help (FLED)
- To locate the respective ARE i2.0 HF hooked up to a particular RS 232 port, the instruction FLED is used.
- This instruction flashes the LED in white for 10 seconds. The colour 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 i9 returns to standby mode.
LED (De)activate LED functionality (LED)
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’ | ‘0’ |
Output: 0
Hex: | 30 | 0D |
---|---|---|
ASCII: | ‘0’ |
- LED
0 deactivates LED functionality. - LED
1 activates LED functionality (default). - The above examples represent ARE i2.0 HF default values.
System Implementation
Power supply
- HF industry uses hdx LF RFID technology. This particular method relies on field gaps, where the RFID field is switched off. In this gap, the transponder answers with its code. This method has the advantage of a high read range in laboratory conditions. However, in an EMV-polluted environment, the read range of hdx transponders is significantly reduced as even low noise signals have a direct impact on read range.
- Therefore system integration must make sure that the power supply for ARE i2.0x HF is 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.
Grounding
- Please make sure that ARE i2.0x HF is properly grounded. This ensures proper functionality of the entire system comprising ARE i2.0x HF and AAN Xi9F. Please see Chapter 2.1.4 for details on grounding.
- Grounding can be achieved by grounding the DIN hat rail, as the clamp on the backside of ARE i2.0x HF is connected to the ground. Alternatively, the grounding pin on the front side of ARE i2.0x HF can be used to achieve this.
Mounting on metal
- ARE i2.0x HF typically mounted on a metal DIN hat rail in a metal electrical cabinet? There is no influence of metal on the performance of ARE i2.0x HF and therefore nothing to watch out for.
- It is recommended to mount AAN Xi9F HF onto a non-conductive surface. However, AAAN Xi9F HF 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.
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 HF is to be used. Noise from
frequency converters significantly reduces the read range of ARE i2.0x HF.
FCC Statement
ARE i2.0x HF
Valid for ARE i2.0x HF
Federal Communications Commission (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, under 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 by 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 the receiver.
- Connect the equipment to 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 | 08.06.2023 | Antenna connector change for ARE i2.0x HF | NK |
03 | 23.08.2023 | No read message correction | 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) >>