ACG Identification Technologies GmbH (ACG) reserves the right to make changes to
its products or services or to discontinue any product or service at any time without
notice. ACG provides customer assistance in various technical areas, but does not
have full access to data concerning the use and applications of customer's products.
Therefore, ACG assumes no liability and is not responsible for customer applications
or product or software design or performance relating to systems or applications
incorporating ACG products. In addition, ACG assumes no liability and is not
responsible for infringement of patents and/or any other intellectual or industrial
property rights of third parties, which may result from assistance provided by ACG.
ACG products are not designed, intended, authorized or warranted to be suitable for
life support applications or any other life critical applications that could involve potential risk of death, personal injury or severe property or environmental damage.
With the edition of this document, all previous editions become void. Indications
made in this manual may be changed without previous notice.
Composition of the information in this manual has been done to the best of our
knowledge. ACG does not guarantee the correctness and completeness of the
details given in this manual and may not be held liable for damages ensuing from
incorrect or incomplete information. Since, despite all our efforts, errors may not be
completely avoided, we are always grateful for your useful tips.
The installation instructions given in this manual are based on advantageous
boundary conditions. ACG does not give any guarantee promise for perfect function
in cross environments.
The ACG logo is a registered trademark of ACG Identification Technologies GmbH.
The mifare
®
logo is a registered trademark of Philips Electronic N.V.
All other products mentioned in this document might be brands or brand names of
the different suppliers.
This document may be downloaded onto a computer, stored and duplicated as necessary to support the use of the related ACG products. Any other type of duplication,
circulation or storage on data carriers in any manner not authorized by ACG
represents a violation of the applicable copyright laws and shall be prosecuted.
ACG Identification Technologies GmbH 1
ACG HF Multi ISO RFID Reader V1.0
Safety Instructions / Warning - Read before start-up!
• The device may only be used for the intended purpose designed by for the
manufacturer. The operation manual should be conveniently kept available at
all times for each user.
• Unauthorized changes and the use of spare parts and additional devices that
have not been sold or recommended by the manufacturer may cause fire,
electric shocks or injuries. Such unauthorized measures shall exclude any
liability by the manufacturer.
• The liability-prescriptions of the manufacturer in the issue valid at the time of
purchase are valid for the device. The manufacturer shall not be held legally
responsible for inaccuracies, errors, or omissions in the manual or
automatically set parameters for a device or for an incorrect application of a
device.
• Repairs may be executed by the manufacturer only.
• Only qualified personnel should carry out installation, operation, and
maintenance procedures.
• Use of the device and its installation must be in accordance with national legal
requirements and local electrical codes.
• When working on devices the valid safety regulations must be observed.
ACG Identification Technologies GmbH 2
ACG HF Multi ISO RFID Reader V1.0
Preface
Read This First
About This Guide
This manual describes the ACG HF Multi ISO Reader Module. Its goal is to describe
the reader, how it works, how to integrate it and how to use it.
If You Need Assistance
Our application center is located in Europe to provide direct support. For more
information, please contact your nearest ACG Sales Center. The contact addresses
can be found on our home page:
The ACG HF Multi ISO Reader Module supports a broad range of tags compliant
with ISO 14443 type A and B standards, including SR176 tags, tags which belong to
the Philips mifare
command structure allows the device to communicate with tags that use an operating
system. The read/write unit supports ISO 14443-4 layer with automatic chaining, 256
byte buffer and frame length, extended time framing and up to 848kBaud
transmission rates over the air interface.
Additionally this unit implements a DES cipher which enables to use mifare
tags. These tags are designed for use in high security algorithms.
A SAM interface is also available.
Major applications are:
®
family, ISO 15693 tags, ISO 18000-3, EPC and UID tags. An open
®
DESFire
• Access control, identification using high security cards
• Ticketing using standard mifare
• Data storage
• Multi-applications using operating systems
®
cards
2 Extended Documentation
Please note that all confidential material is excluded from this documentation.
You can obtain the extended documentation containing the confidential information
after signing a NDA.
ACG Identification Technologies GmbH 11
ACG HF Multi ISO RFID Reader V1.0
3 Definitions and Abbreviations
3.1 Definitions
3.1.1 Anti-collision loop
An algorithm used to identify and handle a dialogue between a reader and one or
more tags in its antenna field.
3.1.2 Hex notation
A hexadecimal value is marked with the suffix ‘h’, i.e. A1h has the value A1
hexadecimal.
3.1.3 ASCII notation
ASCII characters are listed within apostrophes, i.e. ‘x’ means a single x.
ACG Identification Technologies GmbH 12
ACG HF Multi ISO RFID Reader V1.0
3.2 Abbreviations
Abbreviation Description
AID Application ID
ASCII American Standard Code for Information Interchange
ATR Answer to Reset
ATS Answer to Select
AFI Application Family Identifier
block For the mifare® Standard one block contains 16 bytes
CBC Cipher Block Chaining
CID Card Identifier (logical card address, ISO 14443-4)
CRC Cyclic Redundancy Check
DES Data Encryption Standard, for more details about DES
refer to [3].
DSFID Data storage format identifier
EDC Error Detection Code
EGT Extra Guard Time
EOF End of Frame
ETU Elementary time unit
Hex / xxh Value in Hexadecimal notation
I-block Information block
KTT Key Transfer Transponder
LSB Least Significant Bit or Byte
MSB Most Significant Bit or Byte
NAD Node Address (ISO 14443-4)
OSI Open System Interconnection
OTP One time programmable
PCB Protocol Control Byte (ISO 14443-4)
PCON Protocol Configuration byte of the reader
PPS Protocol and Parameter Selection
RATS Request for Answer to Select
R-block Receive ready block
REQA Request ISO Type A
REQB Request ISO Type B
RFU Reserved for Future Use
ACG Identification Technologies GmbH 13
ACG HF Multi ISO RFID Reader V1.0
Abbreviation Description
S-block Supervisory block
Sector For the mifare® Standard one sector contains 4 blocks
SID Station ID
SFGT Guard time after RATS
SN Serial Number of a tag (a 32 bit number)
SOF Start of frame
TDES Triple DES
Value block 32 bit data block format. Used in ticketing application
<CR> Carriage return (0Dh)
<LF> Line feed (0Ah)
Figure 3-1: Abbreviations
ACG Identification Technologies GmbH 14
ACG Identification Technologies GmbH 15
command
√
1
Performance varies
4 Supported tags
ACG HF Multi ISO RFID Reader V1.0
Transfer
√
√
√
√
√
√
√
√
√
√
√
√
√
√
√
Comments
encryption included
encryption not included
encryption included
works only with ‘t’ command
extended setup needed
ISO 14443 A
mifare
mifare
Figure 4-1: Supported labels (Part 1)
mifare
®
mifare
®
mifare
®
Standard
®
4k
Ultralight
®
ProX
DESFire
SLE66CLX320P
SLE 55R04 / 08
Smart MX
Jewel Tag
ISO 14443 B
SLE6666CL160S
SR176
SLIX 4K
ASK GTML2 ISO
ASK GTML
Sharp B
TOSMART P0032/64
Manufacturer
Philips
Philips
Philips
Philips
Philips
Infineon
Infineon
Philips
Innovision
Infineon
STM
STM
ASK
ASK
Sharp
Toshiba
Serial
number
√
√
√
√
√
√
√
√
-
√
√
√
√
√
√
√
Read
block
√
√
√
√
-
-
-
-
-
-
√
√
-
-
-
-
Write
block
√
√
√
√
-
-
-
-
-
-
√
√
-
-
-
-
Dual Interface
ISO 14443 A compliant
1
(
)
ISO 14443 B
compliant(
1
)
various
various
√
√
-
-
-
-
√
√
ACG Identification Technologies GmbH 16
√
√
√
ACG HF Multi ISO RFID Reader V1.0
Figure 4-2: Supported labels (Part 2)
ISO 15693
EM 4135
ICODE® SLI
LRI12
LRI64
LRI512
SRF55VxxP
SRF55VxxS
Tag-it™ HF-I Standard
Tag-it™ HF-I Pro
TempSense
ICODE®
ICODE® EPC
ICODE® UID
Manufacturer
EM Microelec.
Philips
STM
STM
STM
Infineon
Infineon
TI
TI
KSW
Philips
Philips
Philips
Serial
number
√
√
√
√
√
√
√
-
√
√
√
√
Read
block
√
√
√
√
√
√
-
√
-
√
√
√
√
Write
block
√
√
√
√
√
√
-
√
-
√
√
√
√
Transfer
command
√
√
√
√
√
√
√
√
√
√
√
Comments
with 10% modulation index
encryption included
only in addressed mode
temperature logging
ACG HF Multi ISO RFID Reader V1.0
5 The mifare® Transponder Family
The mifare
compliant to the ISO 14443 standard.
5.1 mifare® Standard
The mifare® Standard card consists of 16 sectors. A sector includes four blocks of 16
bytes each.
®
transponder family consists of various 13.56 MHz transponder ICs, all
mifare
Sector 0 (Block: 0...3) Block 8: Data or value (16 bytes)
Sector 1 (Block: 4...7) Block 9: Data or value (16 bytes)
Sector 2 (Block 8...11) Block 10: Data or value (16 bytes)
...
Sector 15 (Block 60...63)
®
Standard Sector 2
Block 11: Access Conditions (4
bytes), Key A, Key B (16 bytes)
Figure 5-1: mifare® Standard: sector diagram
5.1.1 Sector 0 / Block 0
Block 0 is read only.
Serial Number (4 bytes) Check byte (1 byte) Manufacturer data (11 bytes)
Figure 5-2: mifare® Standard: sector 0 / block 0
ACG Identification Technologies GmbH 17
ACG HF Multi ISO RFID Reader V1.0
5.1.2 Blocks 3, 7, 11, 15, …
Transport keys are set on delivery:
Key A (6 bytes) Access Conditions (4 bytes) Key B (6 bytes)
Key A
A0 A1 A2 A3 A4 A5 (Infineon) or FF FF FF FF FF FF (new Philips cards)
Key B
B0 B1 B2 B3 B4 B5 (Infineon) or FF FF FF FF FF FF (new Philips cards)
Access Conditions
FF 07 80 xx (key A is used to read or write; key A itself is not readable; key B is data
only). For further information refer to the mifare
®
card manual.
Remarks
Enabled keys are always read as 00 00 00 00 00 00
Using key B as a data area will cause a security gap, due to the fact that it is
necessary to rewrite key A and the access conditions at each write process. It is not
recommended to use key B as a data storage area.
ACG Identification Technologies GmbH 18
ACG HF Multi ISO RFID Reader V1.0
5.2 State Diagram
All mifare
®
cards use the following state diagram.
Power Off
Reset
Reader Instruction Set
read/write/...
Idle
Ready
Select
Active
Log In
Authenticated
REQA
Wake Up
Select
Anticollision Loop
Authenticate
ISO 14443 Commands
Halt
Halt
Tag interfacing
commands
Figure 5-4: State diagram
ACG Identification Technologies GmbH 19
ACG HF Multi ISO RFID Reader V1.0
5.3 mifare® Ultralight
mifare® Ultralight cards have no encryption included. They only support plain text
data transmission.
mifare
bytes per sector. Only the 4 least significant bytes are valid when using mifare
Ultralight.
Ensure that the other bytes match with the tag content when using the write
command; otherwise the read back will fail.
®
Ultralight only supports 4 bytes per sector, but the command set uses 16
®
5.4 mifare® 4k
mifare® 4k cards have an increased memory. Beginning from sector 32 (20h), sectors
have 16 blocks. Due to compatibility reasons, the sector indices have changed
according to the following table. The login sector has to be used to access the
corresponding sector on the card.
Sector Block Login sector
00h 00h – 03h 00h
01h 04h – 07h 01h
… … …
1Fh 7Ch – 7Fh 1Fh
20h 80h – 8Fh 20h
21h 90h – 9Fh 24h
22h A0h – AFh 28h
23h B0h – BFh 2Ch
24h C0h – CFh 30h
25h D0h – DFh 34h
26h E0h – EFh 38h
27h F0h – FFh 3Ch
Figure 5-5: mifare® 4k sector index table
5.5 mifare® ProX
mifare® ProX tags have an operating system onboard. Data organization depends on
the operating system installed on the card. These cards can include additional
functionalities such as DES or a proprietary encipher algorithm.
Before accessing the operating system, the card must be selected. Customized
commands are issued using the transfer command.
ACG Identification Technologies GmbH 20
ACG HF Multi ISO RFID Reader V1.0
5.6 mifare® DESFire
This tag supports additional security algorithms (DES, Triple-DES, MAC) for security
sensitive applications.
DESFire tags are addressed using a specific command set (see DESFire command
set).
5.6.1 Memory organization
The memory of a DESFire card can be personalized to specific requirements. The
card can be seen as data storage device like a hard disk in a PC. The memory is
divided into a maximum of 28 different applications (directories) with 16 files each. An
application has up to 14 keys. Depending on keys and access conditions a file can
be accessed in four different ways. Plain data is never secured. Data is secured
using a MAC, single DES or triple DES enciphers.
The following figure describes the memory organization of a DESFire card.
DESFire card (Application 0)
Application 1
File
ID 1
File
ID 2
...
File
ID n
Application 2
File
ID 1
File
ID 2
...
File
ID n
...
Application n
File
ID 1
Figure 5-6: DESFire memory organization
ACG Identification Technologies GmbH 21
File
ID 2
...
File
ID n
ACG HF Multi ISO RFID Reader V1.0
5.6.2 State diagram of DESFire
Activate DESFire card
Select Application
Login to Application
Select File with ID
Change File
Commit / Abort Transaction
Figure 5-7: DESFire state diagram
ACG Identification Technologies GmbH 22
ACG HF Multi ISO RFID Reader V1.0
5.6.2.1 Activate PICC
Before accessing a DESFire card, the card must be selected. A DESFire card has a
7 byte UID. After activation, the card is powered up and ready to accept a DESFire
command. Application 0 is selected automatically.
5.6.2.2 Select application
To jump into another application, the application has to be selected. An application
can be seen as a directory, which contains up to 16 files. The size of the application
depends on the stored files.
5.6.2.3 Login to application
Specific access rights can be set for each application. Login to an application allows
changing the organization of the application. Login to a file opens a secured file for
access. A file can be accessed in four different ways: without any security or secured
with MAC, single DES or triple DES.
5.6.2.4 Select file
Before accessing a file, the file must be selected
5.6.2.5 Change file
A selected file can be changed according its access rights. If a file is secured, a login
is required before changes can be made.
5.6.2.6 Commit / Abort transaction
Value files, backup files, linear record files and cyclic record files only adapt their
values after the commit transaction command is given. Several files can be changed
within an application at the same time. The abort transactions command annuls all
changes within an application. Power loss will cancel all modifications too.
For more details about application settings and access rights refer to [2].
ACG Identification Technologies GmbH 23
ACG HF Multi ISO RFID Reader V1.0
5.7 my-d™ IC (SLE 55Rxx)
my-d™ ICs are specific ICs from Infineon. These labels show a different memory
organization. Two different modes of tags are supported: plain and secure mode.
Memory Size of SLE Rxx-family
Type User Memory Administration
Memory
SLE 55R01 128 Bytes 32 Bytes 16
SLE 55R02 256 Bytes 64 Bytes 32
SLE 55R04 616 Bytes 154 Bytes 77
SLE 55R08 1024 Bytes 256 Bytes 128
SLE 55R16 2048 Bytes 512 Bytes 256
Address
Byte number within a page
0 1 2 3 4 5 6 7
FFh User data
… …
7Fh User data
… …
4Ch User data
Number of pages
… …
1Fh User data
… …
0Fh User data
… …
04h User data
03h
02h
01h
00h
Serial number (UID)
Figure 5-8: SLE 55Rxx memory organization
SLE 55R02
SLE 55R01
SLE 55R04
SLE 55R08
SLE 55R16
ACG Identification Technologies GmbH 24
ACG HF Multi ISO RFID Reader V1.0
6 ISO 14443 Type B
ISO 14443 type B cards are supported.
6.1 SR176
The SR176 label contains only 30 bytes of data organized in two bytes per page.
6.1.1 Memory organization
Block
address
0Fh Lock byte RFU Chip ID
0Eh User data
… …
04h User data
03h Serial number
02h Serial number
01h Serial number
00h Serial number
Byte 1 Byte 0
Figure 6-1: SR176 memory organization
6.1.2 Serial number UID
The UID is stored in the first 4 pages. Page 00h contains the LSB of the UID.
The lock byte defines the write access condition of a pair of pages. Each bit can only
be set once. This procedure is irreversible. This byte is implemented as an OTP.
Bit 7 Bit 6 Bit 5 Bit 4 Bit 3 Bit 2 Bit 1 Bit 0
Page 08h
Page 0Fh
Page 0Eh
Page 0Ch
Page 0Dh
Page 0Ah
Page 0Bh
Figure 6-3: Lock byte
Page 09h
Page 06h
Page 07h
Page 04h
Page 05h
Page 02h
Page 03h
Page 00h
Page 01h
6.1.4 Chip ID
The Chip ID is defined in the low nibble of page 0Fh. It is manufacturer set and is
used internally to select and separate single tags.
6.2 SRIX4K
The SRIX4K label contains 512 bytes of data organized into four-byte pages.
6.2.1 Memory organization
Block
address
FFh OTP Lock Reg ST Reserved ST Reserved Fixed Chip ID
7Fh User data
… …
07h User data
06h 32 bits binary counter
05h 32 bits binary counter
04h 32 bits Boolean Area
Byte 3 Byte 2 Byte 1 Byte 0
03h 32 bits Boolean Area
02h 32 bits Boolean Area
01h 32 bits Boolean Area
00h 32 bits Boolean Area
Figure 6-4: SRIX4K memory organization
6.2.2 Lock block
Locking of blocks is not supported with this tag.
ACG Identification Technologies GmbH 26
ACG HF Multi ISO RFID Reader V1.0
7 ISO 15693
The reader can communicate with ISO15693 tags. An anti-collision is needed if
multiple instances of tags are in the same antenna field. The reader detects each
type of ISO15693 labels and handles them individually
7.1 Coding of UID
The UID of a tag is defined in ISO/IEC 15693-3. All tags compliant to ISO15693
support the specified format. The UID is factory programmed and cannot be
changed. The UID is needed for the anti-collision sequence to separate several tags
in the same antenna field.
Byte
7 6 5 4 3 2 1 0
E0h MFR
Code
The MFR Code is listed in ISO/IEC 7816-6:1996/Amd.1: 2000(E). Following
manufacturer are tested with our reader
MFR-Code Company
02h ST Microelectronics
04h Philips Semiconductors
05h Infineon Technologies AG
07h Texas Instrument
16h EM Microelectronic-Marin SA
Serial number
Figure 7-1: Coding of ISO 15693 UID
Figure 7-2: Manufacturer codes
ACG Identification Technologies GmbH 27
ACG HF Multi ISO RFID Reader V1.0
7.2 Memory organization
An ISO15693 tag is separated into two blocks. An administrative block which
contains the UID, AFI, DSFID and the lock page state. The user block is free for
custom use. The chip manufacturer defines the amount of bytes and number of
pages of each tag. As default four bytes are used for several tags.
Page
address
3Fh User data
… …
00h User data
Byte
0 1 2 3
Administrative block
Figure 7-3: Memory organization of ISO 15693
ACG Identification Technologies GmbH 28
ACG HF Multi ISO RFID Reader V1.0
7.3 my-d™ IC (SRF55VxxP)
my-d™ ICs are specific ICs from Infineon. These labels show a different memory
organization. Two different modes of tags are supported: plain and secure mode.
Two different cards with 320 bytes or 1k bytes EEPROM memory are available. The
EEPROM memory is divided into pages.
Each tag is split into two parts: The administrative blocks (00h, 01h, 02h) and the
user area. Administrative pages are read only and cannot be changed. User data is
free for use. Additionally user data pages can be locked. This procedure is
irreversible.
The EEPROM of SRF55V10P is organized in 128 pages addressed 00h to 7Fh. The
EEPROM of SRF55V02P consists of 32 pages addressed 00h to 1Fh.
Address
0 1 2 3 4 5 6 7
7Fh User data
… …
1Fh User data
… …
03h User data
02h
01h
00h
Figure 7-4: SRF55VxxP memory organization
Byte number within a page
Serial number (UID)
7.3.1 UID
The UID of SRF55Vxx labels starts with 60h or E0h.
7.3.2 Security Bit
SRF55V10P
SRF55V02P
Bit 45 of the UID defines the secure mode of the SRF55Vxx. If set the tag supports
security algorithm.
Bit 45 Description
1 Tag supports crypto security mechanism
0 Chip supports plain mode only
Figure 7-5: Security bit
ACG Identification Technologies GmbH 29
Loading...
+ 127 hidden pages
You need points to download manuals.
1 point = 1 manual.
You can buy points or you can get point for every manual you upload.