BLUEBOX Gen.2 HFM
Page 25 of 37
3.21
Writing a Data Block of an ISO 15693 Transponder
This command is used to write a data block of a known (UID) ISO 15693
transponder. Note that the number of bytes of a block depends on the
transponder type; for example, the ICODE2 transponder is organized in blocks
of 4 bytes, the MB89R118 transponder is organized in blocks of 8 bytes, for
more details see the specific transponder data sheet.
Byte
Value
Description
Notes
1
0x12
Command code
1+1
0x..
Transponder UID, 1 st
byte
1+i
0x..
Transponder UID, i th
byte
i < 8
1+8
0x..
Transponder UID, 8 th byte
10
0x..
Block number
Max value depends on the
specific transponder
10+1
0x..
Data to be written in the block, 1 st
byte
10+i
Data to be written in the block, i th
byte
i < n
10+n
Data to be written in the block, n th
byte n depends on the specific
transponder
If the command is not successfully executed, the answer is given in short form
through the ‘reply ack’ / ‘reply nak’ flags; otherwise, the
BLUEBOX
answers,
a) if the addressed transponder is not present:
Byte
Value
Description
Notes
1
0x12
Command code
2
0x01
Status no transponder
b) if the addressed transponder do not support the requested block or if some
error is occurred during the transaction:
Byte
Value
Description
Notes
1
0x12
Command code
2
0x02
Status block not supported or errors
c) if the addressed transponder is present and the block has been correctly
written:
Byte
Value
Description
Notes
1
0x12
Command code
2
0x00
Status ok block successfully written