Baracoda Barcode Reader - Manual (Page 64)

DualRunners – Communication Protocol v1.3 - 64 -
Data Capture
for Workforce
in Motion
If the read operation has been successful, the reader will send the tag ID, the tag data and then 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:
00 01 04 xx xx xx xx 02 00 00 aa aa .. aa 00 01 bb bb .. bb 00 02 cc cc .. cc 01 00 dd .. 27 0E ee ee .. ee DE 00 02
81 01,
where
- 00 01: tag protocol (Mifare)
- 04: tag ID length (4 bytes)
- xx xx xx xx: tag ID (tag ID is read-only)
- 03: card type (03 means Mifare 4K)
- 00: sector id (0)
- 00: block id (block 0 of sector 0)
- aa aa .. aa: 16 bytes of block 0, sector 0
- 00: sector id (0)
- 01: block id (block 1 of sector 0)
- bb bb .. bb: 16 bytes of block 1, sector 0
- 00: sector id (0)
- 02: block id (block 2 of sector 0)
- cc cc .. cc: 16 bytes of block 2, sector 0
- 01: sector id (1)
- 00: block id (block 0 of sector 1)
- cc cc .. cc: 16 bytes of block 0, sector 1
- etc...
- 27: sector id (39)
- 0E: block id (block 14 of sector 39)
- ee ee .. ee: 16 bytes of block 14, sector 39
- DE 00 02 81 01: end of data, where 00 02 – length, 81 – command ID, 01 – success status (01 means
success)
Please note that the dump does not show all 40 sectors of the tag data. The first 32 (thirty-two) sectors all have
an identical structure: (sector id, block id followed by 16 (sixteen) bytes of data) x (3) three times per sector.
The next eight (8) sectors’ structure is: (sector id, block id followed by 16 (sixteen) bytes of data) x (15) fifteen
times per sector. The last byte of the end of data packet is equal to 1 (one), which means that the read
operation has been successful.