Elatec TWN3 Mini Reader Mifare NFC User manual

Transponder Reader
Mifare®NFC
Technical Manual
Doc.-Rev. 1.00

Elatec GmbH
Page 2 of 61
Content
1. INTRODUCTION......................................................................................................................................... 5
2. INSTALLATION OF MINI READER MIFARE®NFC........................................................................... 6
2.1 MECHANICAL OUTLINE............................................................................................................................ 6
2.2 PINNING................................................................................................................................................... 6
2.3 ELECTRICAL CHARACTERISTICS .............................................................................................................. 7
2.4 ASYNCHRONOUS SERIAL CONNECTION (UART) ..................................................................................... 7
2.5 SYNCHRONOUS SERIAL CONNECTION (SPI)............................................................................................. 8
2.5.1 SPI Timing..................................................................................................................................... 10
2.5.2 SPI Software Implementation........................................................................................................ 11
2.6 USAGE OF GPIOS................................................................................................................................... 12
2.7 ASYNCHRONOUS RESET......................................................................................................................... 12
2.8 POWER SUPPLY...................................................................................................................................... 12
2.9 HARD POWER DOWN ............................................................................................................................. 12
2.10 SAM...................................................................................................................................................... 12
3. SUPPORTED TRANSPONDERS............................................................................................................. 13
4. SETTING UP A TERMINAL PROGRAM.............................................................................................. 13
5. REGISTER SET ......................................................................................................................................... 14
5.1 EEPROM MEMORY ORGANIZATION ..................................................................................................... 14
5.2 STATION ID (0AH)................................................................................................................................. 15
5.3 PROTOCOL CONFIGURATION REGISTER 1(0BH) .................................................................................... 15
5.3.1 AutoStart ....................................................................................................................................... 15
5.3.2 Binary............................................................................................................................................ 15
5.3.3 MultiTag........................................................................................................................................ 15
5.3.4 NewSerialMode............................................................................................................................. 15
5.3.5 ExtendID ....................................................................................................................................... 16
5.4 BAUDRATE CONTROL REGISTER (0CH).................................................................................................. 16
5.4.1 Resetting the baudrate to default................................................................................................... 16
5.5 OPERATION MODE REGISTER 1(0EH).................................................................................................... 17
5.6 PROTOCOL CONFIGURATION REGISTER 2(13H)..................................................................................... 17
5.6.1 Disable Startup Message............................................................................................................... 17
5.6.2 Noisy Environment........................................................................................................................ 17
5.7 RESET OFF TIME (14H) .......................................................................................................................... 18
5.8 RESET RECOVERY TIME (15H)............................................................................................................... 19
5.9 PROTOCOL CONFIGURATION REGISTER 3(1BH) .................................................................................... 19
5.9.1 ReqA Extended ID......................................................................................................................... 19
5.9.2 TagInfo.......................................................................................................................................... 20
5.10 INSTALLATION IDENTIFIER (E0H …EFH).............................................................................................. 20
5.11 OPERATION MODE REGISTER 2(F0H).................................................................................................... 20
5.12 STARTUP DELAY REGISTER (F2H) ......................................................................................................... 20
6. COMMUNICATION PROTOCOL.......................................................................................................... 21
6.1 ASCII PROTOCOL .................................................................................................................................. 21
6.2 BINARY PROTOCOL................................................................................................................................ 21
6.2.1 STX................................................................................................................................................ 21
6.2.2 Station ID...................................................................................................................................... 21
6.2.3 Length............................................................................................................................................ 21
6.2.4 Data............................................................................................................................................... 21
6.2.5 Block Check Character (BCC)...................................................................................................... 21
6.2.6 ETX................................................................................................................................................ 21
6.2.7 Example......................................................................................................................................... 22
6.2.8 Remarks......................................................................................................................................... 22
7. INSTRUCTION SET.................................................................................................................................. 23
7.1 COMMAND OVERVIEW........................................................................................................................... 23
7.1.1 Common Commands ..................................................................................................................... 23
7.1.2 Mifare® Classic Specific Commands............................................................................................ 24

Elatec GmbH
Page 3 of 61
7.1.3 Mifare® PLUS Specific Commands.............................................................................................. 24
7.2 ERROR CODES........................................................................................................................................ 24
7.3 TRANSPONDER SERIAL NUMBER RELATED COMMANDS........................................................................ 25
7.3.1 Continuous read mode ‘c’ ............................................................................................................. 25
7.3.2 Select Single Tag ‘s’...................................................................................................................... 25
7.3.3 MultiTag Selection / Tag List ‘m’.................................................................................................. 26
7.3.4 Mifare® PLUS Virtual Card Select ‘nvcs’.................................................................................... 27
7.4 DATA-TRANSACTION RELATED COMMANDS ......................................................................................... 28
7.4.1 Authenticate Tag ........................................................................................................................... 28
7.4.1.1 Mifare® Classic Login ‘l’ ......................................................................................................................... 28
7.4.1.2 Mifare® Ultralight C Login ‘l’.................................................................................................................. 29
7.4.1.3 Mifare® PLUS Login ‘nl’ ......................................................................................................................... 30
7.4.1.4 Login in multiple Tag Surroundings.......................................................................................................... 31
7.4.2 Read Data Block ‘r’ / ‘rb’ ............................................................................................................. 32
7.4.2.1 Mifare® Ultralight / Ultralight C............................................................................................................... 32
7.4.3 Write Data Block ‘w’ / ‘wb’ .......................................................................................................... 33
7.4.3.1 Mifare® Ultralight / Ultralight C............................................................................................................... 33
7.4.4 Mifare® Value Block Related commands ..................................................................................... 34
7.4.4.1 Create Value Block ‘wv’ ........................................................................................................................... 35
7.4.4.2 Read Value Block ‘rv’............................................................................................................................... 35
7.4.4.3 Increment Value Block ‘+’ ........................................................................................................................ 36
7.4.4.4 Decrement Value Block ‘-‘........................................................................................................................ 36
7.4.4.5 Copy Value Block ‘=’................................................................................................................................ 37
7.4.5 Mifare® PLUS Related Commands .............................................................................................. 38
7.4.5.1 Write Personalization Data ‘nwp’.............................................................................................................. 38
7.4.5.2 Commit Personalization ‘ncp’ ................................................................................................................... 39
7.4.5.3 Write AES Sector Key / Special Block ‘nw’ ............................................................................................. 39
7.4.6 Transparent ISO14443-4 Transponder Access ‘t’......................................................................... 40
7.5 SETUP RELATED COMMANDS OF THE READER....................................................................................... 41
7.5.1 Read Byte from EEPROM ‘rp’...................................................................................................... 41
7.5.2 Write Byte to EEPROM ‘wp’......................................................................................................... 41
7.5.2.1 Factory Reset............................................................................................................................................. 41
7.5.3 Set Configuration Flags ‘of’ ......................................................................................................... 42
7.5.4 Set Configuration Registers ‘og’ ................................................................................................... 42
7.5.5 Set Tag Type ‘oa’ / ‘ob’ / ‘oj’ / ‘op’ / ‘os’ / ‘ot’ ............................................................................ 43
7.5.6 Include Tag Type ‘o+a’ / ‘o+b’ / ‘o+j’ / ‘o+p’ / ‘o+s’ ................................................................ 43
7.5.7 Exclude Tag Type ‘o-a’ / ‘o-b’ / ‘o-j’ / ‘o-p’ / ‘o-s’ ...................................................................... 43
7.5.8 Key Management........................................................................................................................... 44
7.5.8.1 Write Mifare® Classic Key ‘wm’.............................................................................................................. 44
7.5.8.2 Write AES / Triple DES Key ‘wd’ ............................................................................................................ 44
7.5.9 SAM related Commands................................................................................................................ 45
7.5.9.1 Init SAM ‘ei’ ............................................................................................................................................. 45
7.5.9.2 SAM Transmit Data ‘et’ ............................................................................................................................ 45
7.6 MISCELLANEOUS COMMANDS ............................................................................................................... 46
7.6.1 Get Station ID ‘g’.......................................................................................................................... 46
7.6.2 Antenna Power Off ‘poff’ .............................................................................................................. 46
7.6.3 Antenna Power On ‘pon’............................................................................................................... 46
7.6.4 Get Version ‘v’ .............................................................................................................................. 46
7.6.5 Reset ‘x’......................................................................................................................................... 46
7.6.6 Break............................................................................................................................................. 46
7.6.7 Read GPIO ‘ir’.............................................................................................................................. 47
7.6.8 Write GPIO ‘iw’ ............................................................................................................................ 47
7.6.9 Read GPIO1 ‘pr’........................................................................................................................... 47
7.6.10 Write GPIO1 ‘pw’ ......................................................................................................................... 47
8. TYPICAL DATA TRANSACTION PROCEDURES.............................................................................. 48
8.1 MIFARE®CLASSIC /MIFARE®PLUS.................................................................................................... 48
8.2 MIFARE®ULTRALIGHT ......................................................................................................................... 49
8.3 MIFARE®ULTRALIGHT C...................................................................................................................... 50
9. MEMORY ORGANIZATION OF MIFARE® TRANSPONDERS....................................................... 51
9.1 MIFARE®CLASSIC 1K........................................................................................................................... 51
9.2 MIFARE®CLASSIC 4K........................................................................................................................... 52

Elatec GmbH
Page 4 of 61
9.3 MIFARE®PLUS .................................................................................................................................... 53
9.4 MIFARE®ULTRALIGHT ......................................................................................................................... 54
9.5 MIFARE®ULTRALIGHT C...................................................................................................................... 55
9.5.1 Example: Writing the Triple-DES Key.......................................................................................... 56
10. MIFARE® PLUS .................................................................................................................................... 57
10.1 SECURITY LEVELS ................................................................................................................................. 57
10.2 APPLICATION HINTS .............................................................................................................................. 58
11. FIRMWARE UPDATE .......................................................................................................................... 59
12. FIRMWARE HISTORY ........................................................................................................................ 60
13. TRADEMARKS...................................................................................................................................... 61

Elatec GmbH
Page 5 of 61
1. Introduction
This document is the reference guide for the transponder reader family TWN3 Mifare®NFC and Mini
Reader Mifare®NFC. The readers are using the same reading technology, so this document is
applicable for both devices.
Note:
In order to use the functionality, which is described in this document, your Mifare®NFC reader
needs a firmware version V1.02 or above. In order to update the firmware from an elder version,
please refer to chapter 11 “Firmware Update”.

Elatec GmbH
Page 6 of 61
2. Installation of Mini Reader Mifare®NFC
This chapter covers the installation of Mini Reader Mifare®NFC in an embedded environment.
2.1 Mechanical Outline
All dimensions are in mm.
Component side shown, Pin spacing: 2.54mm
2.2 Pinning
Pin
Name
Description
Pin
char.
Pin
Name
Description
Pin
char.
1
RESET¯¯¯¯¯
Asynchronous reset
I / PU
9
VSAM
3.0V regulated supply for
SAM
S
2
PWRDWN¯¯¯¯¯¯¯
Hard power down
I / PU
10
SAM_IO
Bidirectional SAM I/O line
IO / PU
3
GND
Ground
S
11
GPIO3
General purpose
input/output 3
IO
4
VCC
3.3V –5V
S
12
GPIO2
General purpose
input/output 2
IO
5
RXD/MOSI
UART/SPI receiver input
I / PU
13
GPIO1
General purpose
input/output 1
IO
6
TXD/MISO
UART/SPI transmitter
output
O
14
GPIO0
General purpose
input/output 0
IO
7
SCK
SPI serial clock
I
15
SAM_CLK
SAM clock
O
8
SS¯¯
SPI slave select
I / PU
16
SAM_RST
SAM reset
O
I: Input
O: Output
IO: Input / Output
S: Supply
PU: Integrated Pull-up resistor

Elatec GmbH
Page 7 of 61
2.3 Electrical Characteristics
Frequency
13.56 MHz
Power supply
3.15V - 5.5V DC
Current consumption
RF field off:
RF field on:
Power Down:
10mA
Typically 80mA
< 2µA
2.4 Asynchronous Serial Connection (UART)
Because Mini Reader Mifare®NFC is transmitting and receiving TTL levels, it can be directly
connected to a microcontroller. If you plan to run the reader at a PC, an appropriate interface
converter circuit must be connected.
By default, the reader starts communication at 9600 baud, 8 databits, 1 stopbit, no parity. The
baudrate can be increased up to 115200 baud in order to achieve a higher communication speed.
Asynchronous Serial Connection is also the first offered communication interface after power-up or
reset of the reader. This means, the reader starts operation in asynchronous mode, as soon as SS¯¯ is
tied to low, synchronous mode is selected. The pin SS¯¯ can be left floating if synchronous mode is not
required.

Elatec GmbH
Page 8 of 61
2.5 Synchronous Serial Connection (SPI)
Mini Reader Mifare®NFC also offers synchronous data transfer via a 4-line SPI. In this case, the
reader is always slave, it cannot initiate any data transfer by itself. All data transfer is initiated by the
master by pulling the pin SS¯¯ to low. Data is transmitted from the master to the reader on signal MOSI,
the reader transmits its response data on signal MISO. The serial clock is issued on signal SCK. All
data bytes are transferred MSB first. A data bit is sampled at the rising edge of SCK. A SPI data
transfer is completed by releasing the pin SS¯¯ to inactive state.
After activation of SS¯¯ the SPI unit needs a setup time (see 1.5.1, marking 1) before the serial clock is
issued in order to handle any incoming or outgoing data transfer. When SS¯¯ is active, the master may
send an arbitrary count of data bytes to the reader. It is recommended to deactivate SS¯¯ when a data
frame has been transmitted completely.
A data byte takes 8 SCK pulses. If SS¯¯ is deactivated before 8 SCK pulses have been issued, the
receiver circuit is reset and the partial received data byte is dropped.
SPI communication works data frame oriented, this means that the first byte received by the reader is
always interpreted as a “length-byte”; it represents the count of data bytes which will follow. On the
same way, the reader transmits its “length-byte” first and tells the master, how many bytes will follow.
If one of the communication entities sets the length-byte to zero, it signals that it has no data to send.
The following images show an exemplary SPI transfer. Hereby, the command „Get Version‟ („v‟) is sent
to the reader. The master transmits the length-byte 0x01 followed by the command-code 0x76 (ASCII
„v‟) to the reader:

Elatec GmbH
Page 9 of 61
After sending the command frame, the master polls the reader for the response. This is done by
cyclically sending 0x00 frames:
Every command requires its individual processing time until a response is available. This response
time also depends on the response polling frequency of the master, so it might be useful to slow down
polling in order to increase processing speed of the reader. As soon as there is a response available,
the reader sends its response to the master, when polled:

Elatec GmbH
Page 10 of 61
The previous image shows the response of the reader, in this case it is the ASCII-representation of the
version string “MifareNFC 1.02<CR><LF>” (with leading length-byte 0x10).
2.5.1 SPI Timing
SPI Interface: Timing requirements. Drawing is not for scale!
MSB LSB
MSB LSB X
2
3 4
5
9
67
10
SCK
MOSI
MISO
SS
1
X
11
12
8
Marking
Description
Min
Typ
Max
1
SS¯¯ low to start of clocking
5µs
2
SS¯¯ low to data output
15ns
3
Data input setup time
10ns
4
Data input hold time
90ns
5
SCK to data output
15ns
6
SCK low
182ns
7
SCK high
182ns
8
SCK rise/fall time
1600ns
9
SCK period
364ns
10
SCK to SS¯¯ high
4µs
11
SS¯¯ inactive time
8µs
12
SS¯¯ high to tri-state
10ns
Please note: The reader requires a boot time of at least 5ms until full SPI functionality is provided. The
boot time is adjustable by the EEPROM to higher values. It is good practice for the master, to issue a
hard reset after power-up while SS¯¯ remains inactive and SCK / MOSI have a logic low level. After the
boot time has elapsed, SS¯¯ may be tied to low for the first time in order to read the version string.

Elatec GmbH
Page 11 of 61
2.5.2 SPI Software Implementation
The following code demonstrates how to implement SPI communication in software for the host
system, e.g. for a microcontroller:
byte SPI_ReadWrite(byte Data)
{
byte i;
for (i=0; i<8; i++)
{
if (Data & 0x80)
MOSI_HIGH;
else
MOSI_LOW;
SCK_HIGH;
Data <<= 1;
if (READ_MISO)
Data |= 0x01;
SCK_LOW;
}
return Data;
}
int main(void)
{
byte k;
byte q;
byte LengthByteRead;
byte LengthByteWrite;
// ...
while(1)
{
LengthByteWrite = GetNumBytesInSendBuffer();
SS_LOW;
LengthByteRead = SPI_ReadWrite(LengthByteWrite);
while ((LengthByteRead > 0) || (LengthByteWrite > 0))
{
if (LengthByteWrite > 0)
{
q = GetByteFromSendBuffer();
LengthByteWrite--;
}
else
q = 0x00;
k = SPI_ReadWrite(q);
if (LengthByteRead > 0)
{
LengthByteRead--;
PushByteToReceiveBuffer(k);
}
else
LengthByteRead = k;
}
SS_HIGH;
}
// ...
}

Elatec GmbH
Page 12 of 61
2.6 Usage of GPIOs
The reader provides four general purpose I/Os that can be configured individually. These I/Os can be
read and written by commands.
Please consider, that the GPIOs have limited current source and sink capability of max. 25mA. An
overcharge of GPIO-pins can damage the module!
2.7 Asynchronous Reset
In usual operating environments, the reset pin can be left floating. For an asynchronous hardware
reset pull the reset pin to a logic low level. The reader continues operation as soon as the reset pin is
released.
2.8 Power Supply
A power supply of 3.3V –5V must be applied between the VCC and GND pins. Please make sure that
the power supply provides a current capability of at least 100mA.
Please note: The current consumption can be significantly increased if GPIOs and/or SAM module are
used. The total current consumption may not exceed 150mA.
2.9 Hard Power Down
The reader supports a hardware power down feature which enables the user to turn off the entire
reader. Hard power down mode is entered by pulling the PWRDWN¯¯¯¯¯¯¯ pin to low; this results in turning
off the internal voltage regulator.
Please note: Maximum power saving can be achieved by entering this mode, but this also means that
the reader needs the boot time until it is available again.
2.10 SAM
The reader supports connection of ISO7816 compatible SAM cards. The lines SAM_IO, SAM_CLK,
SAM_RST, VSAM and GND have to be connected as follows:
SAM card
Pad
Line
C1
C2
C3
C4 C8
C7
C6
C5
C1
VSAM
C2
SAM_RST
C3
SAM_CLK
C4
Leave open
C5
GND
C6
Leave open
C7
SAM_IO
C8
Leave open

Elatec GmbH
Page 13 of 61
3. Supported Transponders
ISO14443A
ISO14443B
ISO18092
Mifare
- Classic 1k, 4k
- DESFire EV1
- Mini
- Plus S, X
- Pro X
- SmartMX
- Ultralight
- Ultralight C
Legic Advant1
SLE44R35
SLE66Rxx
Calypso
CEPAS
Moneo
SRI512, SRT512, SRI4K, SRIX4K
Inside Contactless PicoPass1
HID ICLASS1
FeliCa1
NFC
1UID only
4. Setting up a Terminal Program
In order to establish a connection between the reader and a terminal program, the following steps
have to be done:
Connect your reader to a PC
Start your preferred terminal program (for Windows e.g. HyperTerminal)
Select the serial port (e.g. COM1), where you connected the reader.
Set up the connection speed and format: 9600 baud (default), 8 data bits, no parity, 1 stop bit
Select no software handshake and no hardware handshake

Elatec GmbH
Page 14 of 61
5. Register Set
The reader has several system flags customizing its behavior. The flags are stored non-volatile in its
EEPROM. It is recommended to keep all bits and bytes labeled RFU at their default state to guarantee
further compatibility.
Please consider that if any register is written, the reader needs a reset so that the changes may take
effect.
5.1 EEPROM Memory Organization
Register
Access
Default value
Description
00h … 09h
RO
XXh
Internal use
0Ah
R/W
01h
Station ID
0Bh
R/W
41h
Protocol Configuration Register 1
0Ch
R/W
00h
Baudrate Control Register
0Dh
R/W
20h
RFU, never change this register
0Eh
R/W
7Fh
Operation Mode Register 1
0Fh
R/W
0Ah
RFU, never change this register
10h
R/W
00h
Internal use
11h
R/W
00h
Internal use
12h
R/W
00h
Internal use
13h
R/W
00h
Protocol Configuration Register 2
14h
R/W
0Ah
Reset Off Time
15h
R/W
25h
Reset Recovery Time
16h
R/W
00h
RFU, never change this register
17h
R/W
10h
Internal use
18h
R/W
50h
Internal use
19h
R/W
10h
Internal use
1Ah
R/W
20h
Internal use
1Bh
R/W
00h
Protocol Configuration Register 3
1Ch … 1Fh
R/W
00h
Internal use
20h … DFh
R/W
FFh
RFU, never change this register
E0h … EFh
R/W
00h
Installation Identifier
F0h
R/W
03h
Operation Mode Register 2
F1h
R/W
22h
RFU, never change this register
F2h
R/W
B4h
Startup Delay Register

Elatec GmbH
Page 15 of 61
5.2 Station ID (0Ah)
In ASCII mode, the Station ID has principally no influence on the functional behavior of the reader.
Nevertheless it can be used to identify a reader in a multi-reader environment.
In Binary mode, the Station ID is used to address the reader in protocol header. The Station ID has
the range 01h to FEh and can be set freely. The value 00h is reserved for the bus-master, all readers
send their response to this device. The broadcast message (FFh) forces all readers to response to the
command.
Default value: 01h
5.3 Protocol Configuration Register 1 (0Bh)
The Protocol configuration register 1 specifies the general behavior of the reader.
Protocol Configuration Register 1
Bit 7
Bit 6
Bit 5
Bit 4
Bit 3
Bit 2
Bit 1
Bit 0
ExtendID
RFU
RFU
RFU
NewSerial
Mode
MultiTag
Binary
AutoStart
5.3.1 AutoStart
If set the reader will start up in continuous read mode.
Default value: 1
5.3.2 Binary
If set the reader uses binary protocol. Refer to binary protocol description for further information.
Default value: 0
5.3.3 MultiTag
The MultiTag flag will enable multi tag recognition in continuous read mode. All tags are detected and
displayed. Due to the more complex search algorithm detection speed is decreased in continuous
read mode.
Default value: 0
5.3.4 NewSerialMode
The NewSerialMode flag controls the addition of a leading character to the serial number of
transponders. This eases the recognition of transponder types.
This setting affects the commands continuous reading („c‟), single tag select („s‟) and multi tag select
(„m‟).
Default value: 0
Character
Transponder type
M
ISO14443A, e.g. Mifare®
P
PicoPass
S
ISO14443B, e.g. SRIX4K

Elatec GmbH
Page 16 of 61
5.3.5 ExtendID
If set, the unique serial number (UID) of the transponder is extended by a single prefix byte. This bit
has only effect for ISO14443A transponders.
This setting affects the commands continuous reading („c‟), single tag select („s‟) and multi tag select
(„m‟).
Default value: 0
Possible values for the prefix byte are:
Prefix
Description
01h
Cascade Level 1 transponder, e.g. Mifare® Classic
02h
Cascade Level 2 transponder, e.g. Mifare® Ultralight
03h
Cascade Level 3 transponder
5.4 Baudrate Control Register (0Ch)
The Baudrate control register defines the start-up baudrate of the reader. For baudrate values, refer to
the tables below:
Baudrate Control Register
Bit 7
Bit 6
Bit 5
Bit 4
Bit 3
Bit 2
Bit 1
Bit 0
RFU
RFU
RFU
RFU
RFU
BS2
BS1
BS0
BS2
BS1
BS0
Resulting Baudrate
0
0
0
9600 bps (default)
0
0
1
19200 bps
0
1
0
38400 bps
0
1
1
57600 bps
1
0
0
115200 bps
1
0
1
reserved
1
1
0
reserved
1
1
1
reserved
5.4.1 Resetting the baudrate to default
The reader has a built-in mechanism to reset the baudrate to the default value of 9600 bps. This is
useful, if no communication is possible any more due to an errant setting of the Baudrate control
register. The reset can be done by sending a byte sequence at 9600 bps to the reader. If the
sequence matches, the reader turns its baudrate setting to 9600 bps. This configuration remains valid
until a subsequent reset or power-down event occurs. The user may now write the desired baudrate
setting to the Baudrate Control Register. After that, a reset must be executed, so that the new settings
may take effect.
In order to reset the baudrate, the host has to send the value FFh at 9600 bps three times to the
reader. The bytes must have a temporal distance of at least 100ms. If a valid sequence is recognized,
the reader switches to 9600 bps and sends an acknowledge to the host („B<CR><LF>‟) using the
ASCII protocol.

Elatec GmbH
Page 17 of 61
5.5 Operation Mode Register 1 (0Eh)
The Operation Mode Register 1 defines which tag types the reader shall support. Including or
excluding transponder types has direct influence in the transponder detection speed of the reader.
Operation Mode Register 1
Bit 7
Bit 6
Bit 5
Bit 4
Bit 3
Bit 2
Bit 1
Bit 0
RFU
RFU
RFU
RFU
RFU
SRX
ISO14443B
ISO14443A
5.6 Protocol Configuration Register 2 (13h)
The Protocol Configuration Register 2 specifies the further general behavior of the reader.
Protocol Configuration Register 2
Bit 7
Bit 6
Bit 5
Bit 4
Bit 3
Bit 2
Bit 1
Bit 0
RFU
RFU
RFU
RFU
Noisy
Environment
RFU
Disable
Startup
Message
RFU
5.6.1 Disable Startup Message
If set, the reader will not print the startup message (MifareNFC 1.02) when powered or if a reset
occurs.
Default value: 0
5.6.2 Noisy Environment
If set, the reader will only quit continuous read mode if the „.‟ character is received.
Default value: 0

Elatec GmbH
Page 18 of 61
5.7 Reset Off Time (14h)
The Reset Off Time register represents the time in milliseconds, the RF-field is switched off before and
after a reading attempt. This register is used for the continuous read mode („c‟).
The higher the value of the register, the more energy can be saved. Keep in mind that increased
saving of energy results in decreased detection speeds.
Default value: 0Ah
The image below shows the activity of the RF-field. The Reset Off Time register has been set to 64h,
this results in a pause of 200ms:

Elatec GmbH
Page 19 of 61
5.8 Reset Recovery Time (15h)
The Reset Recovery Time register represents the recovery time in milliseconds after the RF-field is
turned on. This register is used for the continuous read mode („c‟), single tag select („s‟) and multi tag
select („m‟) commands.
The value of the register determines the time the reader waits before any reading attempt. Keep in
mind that a higher value results in increased energy consumption.
Default value: 25h
The image below shows the activity of the RF-field. The Reset Recovery Time register has been set to
40h (64ms):
5.9 Protocol Configuration Register 3 (1Bh)
The Protocol Configuration register 3 specifies the further general behavior of the reader.
Protocol Configuration Register 3
Bit 7
Bit 6
Bit 5
Bit 4
Bit 3
Bit 2
Bit 1
Bit 0
TagInfo
ReqA
Extended ID
Internal use / do not change
RFU
RFU
RFU
5.9.1 ReqA Extended ID
If set, the reader will replace the cascade level information (1 byte) by the ReqA response (2 bytes).
This bit has only effect in combination with ISO14443A transponders.
Default value: 0

Elatec GmbH
Page 20 of 61
5.9.2 TagInfo
If set, the reader extends the UID by a single byte. The value of the byte gives information about the
tag type.
Default value: 0
Refer to the table below for tag types:
Byte value
Corresponding transponder type
00
Mifare® Mini
01
Mifare® Classic 1K
02
Mifare® Classic 4K
03
Mifare® Plus S
04
Mifare® Plus X
05
Mifare® Ultralight / Ultralight C
06
Mifare® DESFire
0F
Unknown ISO14443A transponder
30
PicoPass / ICLASS transponder
40
SRX transponder
60
FeliCa transponder
80
ISO14443B transponder
FF
Unknown transponder
5.10 Installation Identifier (E0h … EFh)
The Installation Identifier is used for Mifare® PLUS in virtual card environment. The Installation
Identifier must match with the one stored in the Mifare® PLUS transponder that shall be identified
using the Virtual Card Select command.
5.11 Operation Mode Register 2 (F0h)
The Operation Mode Register 2 defines which tag types the reader shall support. Including or
excluding transponder types has direct influence in the transponder detection speed of the reader.
Operation Mode Register 2
Bit 7
Bit 6
Bit 5
Bit 4
Bit 3
Bit 2
Bit 1
Bit 0
RFU
RFU
RFU
RFU
RFU
RFU
FeliCa
PicoPass /
ICLASS
5.12 Startup Delay Register (F2h)
The Startup Delay Register influences the boot time of the reader. The minimum required boot time
after power up or a hardware reset is approximately 5ms. By storing a non-zero value in the Startup
Delay Register, the user can influence e.g. the moment of sending the version string at startup. The
resulting boot time is 5ms plus the value stored in the register in milliseconds.
Default value: B4h