Baracoda Barcode Reader - Manual (Page 67)

DualRunners – Communication Protocol v1.3 - 67 -
Data Capture
for Workforce
in Motion
DE 00 F8 82 00 00 00 03 27 00 F0 yy .. yy
where:
- DE: prefix
- 00 F8: data length (248 bytes will follow)
- 82: command ID (write tag data)
- 00 00: protocol mask (it’s best to specify 00 00 for Mifare cards)
- 00: timeout for the response (0 means use default = 5s)
- 03: card type (Mifare 4K)
- 27: start sector (39)
- 00 F0: data length (240 bytes)
- yy .. yy: 240 bytes of data to be written in sector 39
To sum up, the developer should remember that the first 32 (thirty-two sectors) are 48-bytes long and the last
8 (eight) have a length of 240 (two hundred and forty) bytes.
c) Reader’s response (successful write)
If the write operation has been successful, the reader will send an end of data packet with the success byte set
to 1 (one). On the other hand, if the operation has failed, the reader may send the tag ID and an end of data
packet with the success byte set to 0 (zero).
The following is an example of the reader’s response:
DE 00 02 81 01,
where
- DE 00 02 81 01: end of data, where 00 02 – length, 81 – command ID, 01 – success status (01 means
success)
d) Reader’s response (write failure)
If the reader cannot write the tag data, the reader’s response will be the following:
DE 00 02 81 00,
where:
- DE 00 02 81 00: end of data, where 00 02 – length, 81 – command ID, 00 – success status (01 means
failure)
Please note that most Mifare 4K cards have pages that are read-only. The developer should not try to modify
those fields as the results are unpredictable (e.g. the reader may report a success even though the write
operation failed). Please refer to the used RFID tag manufacturer specification for more details.