Eccel Technology Ltd BIORADRDR0200 Manuel D’Utilisation
41
4.2.18 Read Signature (0x12)
The Read Signature command doesn’t take any arguments. This command can be used with Mifare Ultralight EV1,
NTAG213, NTAG215 and NTAG216 tags. After successful reading, the first 32 bytes in the data buffer are filled with
the ECC signature defined by the NXP standard. Please refer to the NXP documentation for more information.
NTAG213, NTAG215 and NTAG216 tags. After successful reading, the first 32 bytes in the data buffer are filled with
the ECC signature defined by the NXP standard. Please refer to the NXP documentation for more information.
4.2.19 Configure UID (0x13)
Table 4.19
The Configure UID command takes as arguments the UID configuration byte (UID Type), the Authentication Key
Number and (optionally) the Authentication Key. This command changes the configuration of the UID on some
Mifare Classic tags. The UID Type parameter is explained in Table 4.20.
Number and (optionally) the Authentication Key. This command changes the configuration of the UID on some
Mifare Classic tags. The UID Type parameter is explained in Table 4.20.
Command Number
Command Name
Valid Tag Types
Argument Offset [bytes]
0x00
0x01
0x02
Argument Name
UID Type
Authentication Key
Number
Authentication Key
Argument Size [bytes]
0x01
0x01
0x06
Argument Description
UID Type configuration
byte.
The 6 least significant
bits define the
Authentication Key
Number from 0 to 39
that is to be used to
read the data. If the
most significant bit (bit
7) is set, then the key
will be used as Key B. If
it is zero it will be used
as Key A. If bit 6 is set,
then the key will be
taken from the
argument list (next 6
bytes).
Optional parameter
used when bit 6 in the
preceding
Authentication Key
Number argument is
set. This key will be
used as Key B if bit 7 of
the Authentication Key
Number is set, or as
Key A if it is zero. The
byte order is the least
significant byte first.
0x13
Configure UID
Some Mifare Classic