Elatec TWN3 Multi ISO User manual

Transponder Reader
Multi ISO
Technical Manual
Doc.-Rev. 1.05

Elatec GmbH
Page 2 of 65
Content
1. Introduction.....................................................................................................................5
2. Installation of Nano Module Multi ISO.........................................................................6
2.1 Mechanical Outline................................................................................................................. 6
2.2 Pinning..................................................................................................................................... 6
2.3 Electrical Characteristics....................................................................................................... 7
2.4 External Connections ............................................................................................................. 7
2.4.1 Antenna........................................................................................................................................... 7
2.4.2 Asynchronous Serial Connection (UART)...................................................................................... 8
2.4.3 Usage of GPIOs............................................................................................................................... 8
2.4.4 Asynchronous Reset........................................................................................................................ 8
2.4.5 Power supply................................................................................................................................... 8
2.4.6 SAM................................................................................................................................................ 8
3. Supported transponders ..................................................................................................9
4. Setting up a Terminal Program......................................................................................9
5. Register Set....................................................................................................................10
5.1 EEPROM Memory Organization........................................................................................ 10
5.2 Unique Device ID (00h … 04h) ............................................................................................ 11
5.3 Station ID (0Ah).................................................................................................................... 11
5.4 Protocol Configuration Register 1 (0Bh)............................................................................ 11
5.4.1 AutoStart ....................................................................................................................................... 11
5.4.2 Binary............................................................................................................................................ 11
5.4.3 MultiTag........................................................................................................................................ 11
5.4.4 NewSerialMode............................................................................................................................. 11
5.4.5 ExtendID ....................................................................................................................................... 12
5.5 Baudrate Control Register (0Ch)........................................................................................ 12
5.5.1 Resetting the Baudrate to Default ................................................................................................. 13
5.6 Operation Mode Register 1(0Eh) ........................................................................................ 14
5.7 Protocol Configuration Register 2 (13h)............................................................................. 14
5.7.1 Disable Startup Message............................................................................................................... 14
5.7.2 Noisy Environment ....................................................................................................................... 14
5.7.3 Reset Recovery Time Multiplier................................................................................................... 14
5.8 Reset Off Time (14h)............................................................................................................. 15
5.9 Reset Recovery Time (15h) .................................................................................................. 15
5.10 Application Family Identifier AFI (16h)......................................................................... 16
5.11 Protocol Configuration Register 3 (1Bh)......................................................................... 16
5.11.1 ReqA Extended ID ........................................................................................................................ 16
5.11.2 TagInfo.......................................................................................................................................... 16
5.12 Installation Identifier (E0h … EFh) ................................................................................ 17
5.13 Operation Mode Register 2 (FEh) ................................................................................... 17
5.14 Beep Tone and Length (FFh) ........................................................................................... 18
6. Communication Protocol..............................................................................................19
6.1 ASCII Protocol...................................................................................................................... 19
6.2 Binary Protocol..................................................................................................................... 19

Elatec GmbH
Page 3 of 65
6.2.1 STX............................................................................................................................................... 19
6.2.2 Station ID ...................................................................................................................................... 19
6.2.3 Length ........................................................................................................................................... 19
6.2.4 Data............................................................................................................................................... 19
6.2.5 Block Check Character (BCC)...................................................................................................... 19
6.2.6 ETX............................................................................................................................................... 19
6.2.7 Example ........................................................................................................................................ 20
6.2.8 Remarks ........................................................................................................................................ 20
7. Instruction Set ...............................................................................................................21
7.1 Command Overview............................................................................................................. 21
7.1.1 Common Commands..................................................................................................................... 21
7.1.2 Mifare® Classic Specific Commands ........................................................................................... 22
7.1.2.1 Mifare® PLUS Specific Commands......................................................................................... 22
7.1.3 ISO15693 specific commands....................................................................................................... 22
7.2 Error Codes........................................................................................................................... 22
7.3 Transponder Serial Number Related Commands............................................................. 23
7.3.1 Continuous read mode ‘c’ ............................................................................................................. 23
7.3.2 Select Single Tag ‘s’ ..................................................................................................................... 23
7.3.3 MultiTag Selection / Tag List ‘m’................................................................................................. 24
7.3.4 Mifare® PLUS Virtual Card Select ‘nvcs’.................................................................................... 25
7.4 Data Transaction Related Commands................................................................................ 26
7.4.1 Authenticate Tag........................................................................................................................... 26
7.4.1.1 Mifare® Classic Login ‘l’ ......................................................................................................... 26
7.4.1.2 Mifare® Ultralight C Login ‘l’.................................................................................................. 27
7.4.1.3 Mifare® PLUS Login ‘nl’ ......................................................................................................... 28
7.4.1.4 Login in multiple Tag Surroundings ......................................................................................... 29
7.4.2 Read Data Block ‘r’ / ‘rb’ ............................................................................................................. 30
7.4.2.1 Mifare® Ultralight / Ultralight C .............................................................................................. 30
7.4.3 Write Data Block ‘w’ / ‘wb’.......................................................................................................... 31
7.4.3.1 Mifare® Ultralight / Ultralight C .............................................................................................. 31
7.4.4 Mifare® Value Block Related Commands.................................................................................... 32
7.4.4.1 Create Value Block ‘wv’........................................................................................................... 33
7.4.4.2 Read Value Block ‘rv’............................................................................................................... 33
7.4.4.3 Increment Value Block ‘+’........................................................................................................ 34
7.4.4.4 Decrement Value Block ‘-’....................................................................................................... 34
7.4.4.5 Copy Value Block ‘=’ ............................................................................................................... 35
7.4.5 Mifare® PLUS Related Commands.............................................................................................. 36
7.4.5.1 Write Personalization Data ‘nwp’ ............................................................................................. 36
7.4.5.2 Commit Personalization ‘ncp’................................................................................................... 37
7.4.5.3 Write AES Sector Key / Special Block ‘nw’............................................................................. 37
7.4.5.4 Proximity Check ‘npc’ .............................................................................................................. 38
7.4.6 Transparent ISO14443-4 Transponder Access ‘t’ ......................................................................... 39
7.5 Setup Related Commands of the Reader............................................................................ 40
7.5.1 Read Byte from EEPROM ‘rp’ ..................................................................................................... 40
7.5.2 Write Byte to EEPROM ‘wp’ ....................................................................................................... 40
7.5.3 Set Configuration Flags ‘of’.......................................................................................................... 41
7.5.4 Set Configuration Register ‘og’ .................................................................................................... 42
7.5.5 Set Tag Type ‘oa’ / ‘ob’ / ‘op’ / ‘os’ / ‘ot’ / ‘ov’........................................................................... 42
7.5.6 Include Tag Type ‘o+a’ / ‘o+b’ / ‘o+p’ / ‘o+s’ / ‘o+v’ ................................................................. 43
7.5.7 Exclude Tag Type ‘o-a’ / ‘o-b’ / ‘o-p’ / ‘o-s’ / ‘o-v’..................................................................... 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

Elatec GmbH
Page 4 of 65
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
7.6.11 Beep ‘b’......................................................................................................................................... 48
7.6.12 Resend Last Answer ‘ra’ ............................................................................................................... 48
7.6.13 Field Reset ‘y’ ............................................................................................................................... 48
7.6.14 Lock Block (ISO15693 only) ‘k’ .................................................................................................. 48
7.6.15 AES Data Encryption/Decryption ‘as’ .......................................................................................... 49
7.6.16 DES / Triple-DES Data Encryption/Decryption ‘ds’ .................................................................... 50
8. Typical Data Transaction Procedures..........................................................................51
8.1 Mifare® Classic / Mifare® PLUS........................................................................................ 51
8.2 Mifare® Ultralight................................................................................................................ 52
8.3 Mifare® Ultralight C............................................................................................................ 53
8.4 I•Code SLI / SRX.................................................................................................................. 54
9. Memory Organization of Mifare® Transponders........................................................55
9.1 Mifare® Classic 1k ............................................................................................................... 55
9.2 Mifare® Classic 4k ............................................................................................................... 56
9.3 Mifare® PLUS ...................................................................................................................... 57
9.4 Mifare® Ultralight................................................................................................................ 58
9.5 Mifare® Ultralight C............................................................................................................ 59
9.5.1 Example: Writing the Triple-DES Key......................................................................................... 60
10. Mifare® PLUS...............................................................................................................61
10.1 Security Levels................................................................................................................... 61
10.2 Application Hints .............................................................................................................. 62
11. Firmware Update...........................................................................................................63
12. Firmware History..........................................................................................................64
13. Trademarks....................................................................................................................65

Elatec GmbH
Page 5 of 65
1. Introduction
This document is the reference guide for the transponder reader family TWN3 Multi ISO and Nano
Module Multi ISO. 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 Multi ISO reader
needs a firmware version V1.15 or above. In order to update the firmware from an elder version,
please refer to chapter 8 “Firmware update”.

Elatec GmbH
Page 6 of 65
2. Installation of Nano Module Multi ISO
This chapter covers the installation of Nano Module Multi ISO in an embedded environment.
2.1 Mechanical Outline
Dimensions: 30.48mm x 25.40mm x 3.7mm (1.2” x 1” x 0.15”)
Connectors are in 2.54mm (0.1”) grid.
Component side shown
2.2 Pinning
Pin
Name
Description
1
AntRX
Antenna receiver input
2
AntTX1
Antenna transmitter output 1
3, 20
VCC
5V
4, 6, 19
GND
Ground
5
AntTX2
Antenna transmitter output 2
7
SAM_CLK
SAM clock
8
SAM_IO
Bidirectional SAM I/O line
9
SAM_RESET
SAM reset
10
NC
Not connected
11
RXD
RS-232 receiver input
12
TXD
RS-232 transmitter output
13
GPIO0
General purpose input / output 0
14
GPIO1 / Beeper
General purpose input / output 1, connection port for beeper
15
RESET¯¯¯¯¯
Asynchronous reset
16
NC
Not connected
17
GPIO2
General purpose input / output 2
18
GPIO3
General purpose input / output 3

Elatec GmbH
Page 7 of 65
2.3 Electrical Characteristics
Frequency
13.56MHz
Power supply
4.5V - 5.5V DC
Current consumption
RF field off:
RF field on:
20mA
Typically 120mA, depending on antenna
2.4 External Connections
The schematic below shows a typical application circuit for operating the reader module.
2.4.1 Antenna
Nano Module Multi ISO requires an external antenna circuit for reading transponders. The part values
of C1 –C5 and R1 are strongly depending on the used antenna inductor. Take the guide below as a
reference for creating your own PCB antenna.
Little PCB Antenna Design Guide:
- Antenna inductance value is usually in the range of 1µH.
- For antenna loop up to 40mm diameter use 5 turns.
- For antenna loop larger than 40mm diameter use 3 turns.
- Use between 1mm to 2mm track width.
- Middle tap improves EMC compliance, but can be omitted for simple designs.
- All capacitors have to be chosen to create maximum field strength (measure antenna field with
an oscilloscope and the voltage induced in some auxiliary loop; alternatively measure the
module power consumption which is maximum at optimum tuning).
- C1 is used for fine tuning. Some extra capacitors may be connected in parallel to achieve best
performance.
- Typical capacitor values: 10pF … 470pF. Prefer NP0/C0G ceramic capacitors.
- Value of R1 is usually 4.7kΩ, but this value may differ from design to design.
For further information regarding antenna design please contact NXP in order to receive the
appropriate Application notes (Application Note Micore Reader IC Family; Directly Matched Antenna
Design)

Elatec GmbH
Page 8 of 65
2.4.2 Asynchronous Serial Connection (UART)
Because Nano Module Multi ISO is transmitting and receiving TTL levels, it can be directly connected
to a microcontroller. If you plan to run Nano Module Multi ISO 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.
2.4.3 Usage of GPIOs
Nano Module Multi ISO provides four general purpose I/Os that can be configured individually. These
I/Os can be read and written via 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!
A non self-oscillating beeper can also be connected to GPIO1. The tone length and frequency can be
controlled by commands.
2.4.4 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. Nano Module Multi ISO continues operation as soon as the
reset pin is released.
2.4.5 Power supply
A power supply of 4.5V –5.5V must be applied between the VCC and GND pins. Please make sure
that the power supply provides a current capability of at least 120mA.
2.4.6 SAM
The reader supports connection of ISO7816 compatible SAM cards. The lines SAM_IO, SAM_CLK,
SAM_RST, VCC and GND have to be connected as follows:
SAM card
Pad
Line
C1
C2
C3
C4 C8
C7
C6
C5
C1
VCC
C2
SAM_RST
C3
SAM_CLK
C4
Leave open
C5
GND
C6
Leave open
C7
SAM_IO
C8
Leave open

Elatec GmbH
Page 9 of 65
3. Supported transponders
ISO14443A
ISO14443B
ISO15693
Mifare
- Classic 1k, 4k
- DESFire EV1
- Light
- Mini
- Plus S, X
- Pro X
- SmartMX
- Ultralight
- Ultralight C
Legic Advant1
SLE44R35
SLE66Rxx
my-d move
Calypso
CEPAS
Moneo
SRI512, SRT512, SRI4K, SRIX4K
Inside Contactless PicoPass1
HID ICLASS1
ICODE SLI
Tag-it
Legic Advant1
Inside Contactless PicoPass1
HID ICLASS1
my-d
EM4033
EM4233
EM4135
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 10 of 65
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 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 … 04h
RO
XXh
Unique device ID
05h … 09h
RO
00h
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
Application Family Identifier AFI
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 … FDh
R/W
FFh
RFU, never change this register
FEh
R/W
01h
Operation Mode Register 2
FFh
R/W
22h
Beep tone and length (Nano Module Multi ISO only)

Elatec GmbH
Page 11 of 65
5.2 Unique Device ID (00h … 04h)
The Unique Device ID is factory programmed and cannot be changed. It forms a unique 40 bit ID of
the reader.
5.3 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.4 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.4.1 AutoStart
If set the reader will start up in continuous read mode.
Default value: 1
5.4.2 Binary
If set the reader uses binary protocol. Refer to binary protocol description for further information.
Default value: 0
5.4.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.4.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

Elatec GmbH
Page 12 of 65
Character
Transponder type
M
ISO14443A, e.g. Mifare®
P
PicoPass / ICLASS
S
ISO14443B, e.g. SRIX4K
V
ISO15693, e.g. I•Code SLI
5.4.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.5 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

Elatec GmbH
Page 13 of 65
5.5.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 14 of 65
5.6 Operation Mode Register 1(0Eh)
The Operation Mode Register 1 defines which tag types the reader shall support. Including or
excluding of 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
ISO15693
RFU
SRX
RFU
ISO14443A
5.7 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
Reset Recovery Time
Multiplier
Noisy
Environment
RFU
Disable
Startup
Message
RFU
5.7.1 Disable Startup Message
If set, the reader will not print the start-up message (MultiISO 1.15) when powered or if a reset
occurs.
Default value: 0
5.7.2 Noisy Environment
If set, the reader will only quit continuous read mode if the „.‟ character is received.
Default value: 0
5.7.3 Reset Recovery Time Multiplier
Multiplies the value of the Reset Recovery Time:
Default value: 00
Reset Recovery Time Multiplier[1:0]
Reset Recovery Time
00
1x
01
2x
10
3x
11
4x

Elatec GmbH
Page 15 of 65
5.8 Reset Off Time (14h)
The Reset Off Time register represents the time in milliseconds, the RF-field is switched off, after a
reading attempt has finished. This register is used for the continuous read mode („c‟).
The higher the value of the register, the more energy can be saved. As soon as there is a transponder
in range, the field turned on permanently. 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 80h,
this results in a pause of 128ms:
5.9 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 (64 ms):

Elatec GmbH
Page 16 of 65
5.10 Application Family Identifier AFI (16h)
The Application Family Identifier (AFI) is only supported by ISO15693 transponders. If the value of this
register is different from 00h, the AFI is used. This means, that only transponders containing an
identical AFI will answer to the reader.
Default value: 00h
5.11 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.11.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
5.11.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:

Elatec GmbH
Page 17 of 65
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
10
I•Code SL2
11
I•Code SL2-S
12
Tag-it™HF-I Plus Inlay
13
Tag-it™HF-I Plus Chip
14
Tag-it™HF-I Standard
15
Tag-it™HF-I Pro
1F
Unknown ISO15693 transponder
30
Picopass / ICLASS transponder
40
SRX transponder
80
ISO14443B transponder
FF
Unknown transponder
5.12 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 Virtual Card Select command.
5.13 Operation Mode Register 2 (FEh)
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
RFU
PicoPass /
ICLASS

Elatec GmbH
Page 18 of 65
5.14 Beep Tone and Length (FFh)
This register defines the beep tone (frequency) and beep length. It is only implemented on Nano
Module Multi ISO.
Beep Tone and Length Register
Bit 7
Bit 6
Bit 5
Bit 4
Bit 3
Bit 2
Bit 1
Bit 0
Length
Tone
The beep tone code selects a predefined frequency from the table below:
Tone[3:0]
Frequency
Standard pitch (Vienna scale)
0000
523Hz
C
0001
554Hz
Cis
0010
587Hz
D
0011
622Hz
Dis
0100
659Hz
E
0101
699Hz
F
0110
739Hz
Fis
0111
784Hz
G
1000
831Hz
Gis
1001
880Hz
A
1010
932Hz
Ais
1011
988Hz
H
1100
Reserved
1101
Reserved
1110
Reserved
1111
Reserved
The following formula defines the beep length:
BeepLength = (Length[3:0] + 1) x 62.5ms
Examples:
Length[3:0]
BeepLength
0000
62.5ms
0001
125ms
0111
500ms
1111
1000ms

Elatec GmbH
Page 19 of 65
6. Communication Protocol
6.1 ASCII Protocol
The ASCII protocol has been designed for easy handling. Data is always transmitted in hexadecimal
notation, i.e. 5E.
Every time the reader is powered up, a startup message is displayed. On the terminal screen this
should look like this:
MultiISO 1.15<CR><LF>
The reader is now ready for reception of commands. By default, the reader starts in continuous
reading mode, this means the reader is scanning for transponders and prints the present UIDs.
Please note that pseudo-tetrade values always must be submitted in capital letters, e.g. 1234ABCD
Commands must be submitted in lower-case letters, e.g. wp0C03
6.2 Binary Protocol
The binary protocol has been designed for industrial applications with synchronization and frame
checking. The reader uses a watchdog timer internally to ensure correct framing. A binary frame is
built up as follows:
STX
Station ID
Length
Data
BCC
ETX
1 byte
1 byte
1 byte
Various length
1 byte
1 byte
In binary mode, the reader only gives a response if a command is issued. This means, the reader
does not show the start-up string and also continuous read does not work.
6.2.1 STX
Start of transmission (02h)
6.2.2 Station ID
00h: Reserved for the bus master. Responses are sent with Station ID set to 00h.
FFh: Broadcast message. All devices will execute the command and send their response.
6.2.3 Length
Denotes the length of the data block in bytes.
6.2.4 Data
The data block contains the command including its arguments. The command values are the same as
in ASCII protocol mode whereas the arguments are transmitted in binary. If a command requires a
subsequent carriage return (0Dh) it also must be submitted.
6.2.5 Block Check Character (BCC)
The BCC is used to detect transmission errors. The BCC is calculated by XOR-ing each byte of the
transmission frame except the STX/ETX characters.
6.2.6 ETX
End of Transmission (03h)

Elatec GmbH
Page 20 of 65
6.2.7 Example
This example shows how to log into sector 0 of a Mifare®card, using transport key FFh:
STX
Station ID
Length
Data
BCC
ETX
02
01
04
6C 00 FF 0D
9B
03
6.2.8 Remarks
If an invalid instruction frame is received (e.g. BCC is wrong) or if the requested Station ID does not
match the internal ID of the reader, the command is not executed.