The 13,56 MHz Multitag Reader Module is a proximity reading device supporting a
wide range of 13,56 MHz tag. It supports ISO15693, Icode®, Tagit®, Mifare®
Standard, Mifare® Ultralight, SR176 and ISO14443 Type B cards. Using an external
antenna and a serial interface it can be easily connected to a PC. The Plug and Play
version has an integrated antenna and serial interface.
The first part of the documentation described general functions and memory
management of different tags. A listing of the memory map is given in detail if
necessary.
The second part lists the OEM module and describes the pin out.
The next chapter lists all commands and introduce to them. Each command is
explained and an example illustrates the usage. FAQs highlight general issues of the
handling of the 13,56 MHz Multitag Reader Module.
The appendices describes the Plug and Play Module, the custom coil design,
matching circuit and all steps to upgrade the Plug and Play board to +12V supply
voltage.
Additionally the use of the TempeSense® label is high lightened.
WARRANTY
THIS WARRANTY ONLY APPLIES TO THE H6160 DEVICE.
THIS DEVICE COMPLIES WITH PART 15 OF THE FCC RULES. OPERATION IS
SUBJECT TO THE FOLLOWING TWO CONDITIONS: (1) THIS DEVICE MAY NOT
CAUSE HARMFUL INTERFE RENCE, AND (2) THIS DEVICE MUST ACCEPT ANY
INTERFERENCE RECEIVED, INCLUDING INTERFERENCE THAT MAY CAUSE
UNDESIRED OPERATION.
CAUTION:
ANY CHANGES OR MODIFICATIONS NOT EXPRESSLY APPROVED BY THE
PARTY RESPONSIBLE FOR COMPLIANCE COULD VOID THE USER’S
AUTHORITY TO OPERATE THE EQUIPMENT.
ACG Identification Technologies AT Page 3
13,56 MHz Multitag Reader Module, Version 0.9v
2 Definitions and abbreviations
2.1 Definitions:
2.1.1 Anticollision loop
Algorithm processed to identify and handle a dialogue between VCD and one or
more VICCs in its antenna field.
2.1.2 Hex notation
A hexadecimal value is noted with a following h. i.e. A1h has the value A1
hexadecimal.
2.1.3 ASCII notation
ASCII characters are listed within apostrophes, i.e. ‘x’ means a single x.
LSB Least significant bit
MFR Manufacturer
MSB Most significant bit
RFU Reserved for future use
OTP One time programming
STATID Station ID
STX Start of transmission frame
UID Unique identifier
VCD Vicinity coupling device
VICC Vicinity integrated circuit card
Figure 2-1: Abbreviations
ACG Identification Technologies AT Page 4
3 Tag organization
A
y
3.1 State diagram
Anticollision Loop,
Inventor
Application
13,56 MHz Multitag Reader Module, Version 0.9v
Power off
HALT
WAKE-UP
Ready
Select
CTIVE
Figure 3-1: State Diagram
The state diagram shows the different states of a tag. First the tag must be power up.
Next command initialize a tag using the anticollision or inventory command.
A selection of a tag is necessary to interact with a tag of interest especially if more
than one tag is present at the same time. Only selected tags are capable to response
to higher commands such as read or write page data.
READY state A tag enters the READY state after it receives a
valid inventory or anticollision command. At this
state the tag all serial numbers are known and
the tag is ready to select.
ACTIVE state After a selection the tag is in the ACTIVE state.
Only an activated tag can respond to a read or
write command.
HALT state The HALT command disables a tag for further
communication. The tag is still in the field but
dies not respond to any command. To activate a
tag and to put it back to the Ready state a
WAKE-UP command has to be used.
ACG Identification Technologies AT Page 5
ACG Identification Technologies AT Page 6
(
1
) Only commands within 320µs after the EOF are recognized
The reader can communicate with ISO15693 tags. An anticollision 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
3.3.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 anticollision 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 3-3: Coding of ISO 15693 UID
Figure 3-4: Manufacturer codes
3.3.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
ACG Identification Technologies AT Page 7
Byte
0 1 2 3
Administrative block
Figure 3-5: Memory organization of ISO 15693
13,56 MHz Multitag Reader Module, Version 0.9v
3.3.3 My-D Label (SRF55VxxP)
My-D labels are specific labels of Infineon. These labels show a different memory
organization. Two different modes of tags are supported: plain and secure mode. At
the moment only plain mode tags are supported in full functionality. Only serial
numbers are supported in 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
Page
0 1 2 3 4 5 6 7
7Fh User data
… …
3Fh User data
… …
03h User data
02h
01h
00h Serial number (UID)
Figure 3-6: SRF55VxxP memory organization
3.3.3.1 UID
The UID of SRF55Vxx labels starts with 60h or E0h.
3.3.3.2 Security Bit
Bit 45 of the UID defines the secure mode of the SRF55Vxx. If set the tag supports
security algorithm and is not accessible with the reader device
SRF55V02P
SRF55V10P
Bit 45 Description
1 Tag supports crypto security mechanism
0 Chip supports plain mode only
Figure 3-7: Security bit
ACG Identification Technologies AT Page 8
13,56 MHz Multitag Reader Module, Version 0.9v
3.3.4 EM 4135
The EM4135 is an ISO15693 compliant label of EM Microelectronic-Marin SA. It has
eight bytes per page as the same as the My-D label. It only supports 35 pages. The
administrative area holds the information of the access condition and the UID.
Address
0 1 2 3 4 5 6 7
24h User data
… …
00h User data
Administrative area
Figure 3-8: Memory organization of EM 4135
Page
3.4 Icode®
Icode® labels stores data is stored in a non-volatile EEPROM. Its capacity is 512 bits
organized in 16 blocks consisting 4 bytes each (1 block = 32 bits). First 3 blocks
contain administrative data.
3.4.1 Memory organization
Page
address
Byte
0 1 2 3
0Fh User data
… …
05h User data
04h Family code identifier / User data
03h Special function (EAS) / User data
02h Write access condition
01h Serial number
00h Serial number
Figure 3-9: Icode® memory organization
3.4.2 Serial number
The serial number of a label is defined at the manufacturer process. It is stored on
page 00h and page 01h. LSB is stored first.
ACG Identification Technologies AT Page 9
13,56 MHz Multitag Reader Module, Version 0.9v
r
r
3.4.3 Write access condition
Page 02h contains the write access condition for each page. Each page can be set to
read only (bits are set to 0). This procedure is irreversible. Locking page 2 no further
changed of the access condition can be done. Always two bits must be change at the
same time. This register is implemented as OTP.
Byte 0 Byte 1 Byte 2 Byte 3
MSB LSB MSB LSB MSB LSB MSB LSB
1 1 1 1 0 0 0 0 1 1 1 1 11111111111111 1 1 1 1 11
3 2 1 0 7 6 5 4 B A 9 8 F E D C
…
…
…
…
…
…
…
…
…
data
Write
Serial
function
access
numbe
Special
User
Serial
numbe
Figure 3-10: Write access condition bytes
…
User
data
3.4.4 Special function (EAS), AFI
Special Functions (EAS) and Family Code/Application Identifier are additional
features. For more information refer to the Icode® manual.
3.4.5 User data
All other blocks are free for use and can be changed according the state of the write
access conditions.
3.5 TAGIT®
TAGIT® labels are organized in a wide range of different page size and number of
pages. Automatically the reader detects the correct memory organization.
Switching on the Extended ID mode (see chapter instruction set) the reader appends
two bytes to the UID containing the page size and the number of pages of a label.
ACG Identification Technologies AT Page 10
13,56 MHz Multitag Reader Module, Version 0.9v
3.6 SR176
The SR176 label contains only 64 bytes of data organized in two bytes per page.
3.6.1 Memory organization
Page
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
Figure 3-11: SR176 memory organization
Byte 1 Byte 0
3.6.2 Serial number UID
The UID is stored at 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 OTP.
Bit 7 Bit 6 Bit 5 Bit 4 Bit 3 Bit 2 Bit 1 Bit 0
Page 08h
Page 0Eh
Page 0Fh
Page 0Ch
Page 0Dh
Page 0Ah
Page 0Bh
Figure 3-13: Lock byte
Page 09h
Page 06h
Page 07h
Page 04h
Page 05h
Page 02h
Page 03h
Page 00h
Page 01h
3.6.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.
ACG Identification Technologies AT Page 11
13,56 MHz Multitag Reader Module, Version 0.9v
3.7 ISO 14443
The reader can only handle single tags according ISO 14443 type A or B. The reader
only identifies single tags and returns its serial number.
All other command such as read, write, select are not supported.
The Mifare® transponder family consists of various 13.56 MHZ transponders
according to ISO14443. For more details refer to ISO14443 part 1-4.
3.8 Mifare® Ultralight
Mifare® Ultralight tags have no crypto algorithm included. They are designed for a
small data volume.
3.8.1 Memory organization
Page
address
0Fh User data
…
04h User data
03h OTP
02h Lock bytes reserved
01h Serial number
00h Serial number
Byte
3 2 1 0
Figure 3-14: Memory organization of Mifare® Ultralight
3.8.2 Serial number
The UID consists of 7 bytes. The first part of the UID is stored on page 00h the
second on page 01h. The storage format on page 00h fulfills ISO14443 Type A. The
UID is factory programmed and cannot be changed.
ACG Identification Technologies AT Page 12
13,56 MHz Multitag Reader Module, Version 0.9v
3.8.3 Lock bytes
On page 2 the lock bytes are stored. Each bit specifies a page or block. Once a bit is
set it cannot be changed anymore. This process is irreversible. If a block lock bit is
set all pages within this block are read only regardless the single lock states. This
register is implemented as OTP
Byte 1 Byte 0
MSB LSB MSB LSB
7 6 5 4 3 2 1 0 7 6 5 4 3 2 1 0
Page 9
Page 8
Page 7
Page 6
Page F
Page E
Page D
Page C
Page B
Page A
Page 5
Page 4
OTP
Block A-F
OTP
Block 4-9
Figure 3-15: Lock bytes of Mifare® Ultralight
3.8.4 OTP bytes
Page 3 is implemented as OTP register. All bits are factory programmed to 0. Once a
bit is set it cannot be changed furthermore. It can be used as a 32 bit one-time
counter.
3.8.5 User data
User data is free for use. It can be changed according the write access condition.
ACG Identification Technologies AT Page 13
13,56 MHz Multitag Reader Module, Version 0.9v
4 Hardware
4.1 Pin out of OEM Module
25,5
J1
J2
2,54
1,27
30,5
4.1.1 Pin out of J1
PIN PIN Nr Description
ARX 1 Antenna RX
ATX1 2 Antenna TX1
VDD 3 +5 V DC
GND 4 Ground
RFU 5 Reserved for future us e
TGND 6 Antenna Ground
As a default data is transmitted at 9600,n,8,1. Two protocol modes are supported.
The protocol mode is configured in the reader EEPROM. As factory default, the
ASCII protocol is used.
5.1 ASCII Protocol
This protocol was designed for easy handling. The commands can be issued using a
terminal program. Data is transmitted as ASCII hexadecimal that can be displayed on
any terminal program (e.g. HyperTerminal).
Command Data
Various length Various length
Figure 5-1: ASCII protocol frame
5.2 Binary Protocol
This protocol was designed for industrial applications with synchronization and frame
checking. Also an addressing byte for party lines (master slave, multi drop) is
included.
The protocol usually requires a device driver. Data is transmitted binary.
STX Station ID Length Data BCC ETX
1 byte 1 byte 1 byte Various length 1 byte 1 byte
Figure 5-2: Binary protocol frame
5.2.1 STX
Start of transmission (02h)
5.2.2 Station ID
Unique ID of the station
00h: reserved for the bus master. Readers send response to this device ID
FFh: Broadcast message. All devices will execute the command.
5.2.3 Length
Length of the data block
5.2.4 Data
This part contains the command and data. The command values are the same as in
ASCII protocol mode (‘x’, ‘s’, …). Data is transmitted binary.
The length of the command block depends on the instruction.
5.2.5 Block Check Character (BCC)
The BCC is used to detect transmission errors. The BCC is calculated XORing each
byte of the transmission frame excluding the STX/BCC and ETX character.