Baracoda Barcode Reader - Manual (Page 69)

DualRunners – Communication Protocol v1.3 - 69 -
Data Capture
for Workforce
in Motion
c) Reader’s response (successful read)
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 04 08 xx xx xx xx xx xx xx xx 0B 00 aa bb cc dd 01 ee ff gg hh 02 ... 3F ii jj kk ll DE 00 02 81 01,
where
- 00 04: tag protocol (ISO 15693 for Tag-it HF-I Plus inlay)
- 08: tag ID length (8 bytes)
- xx xx xx xx xx xx xx xx: tag ID (tag ID is read-only)
- 0B: card type (0B means Tag-it HF-I Plus inlay)
- 00: block id (0)
- aa bb cc dd: 4 bytes of block 0
- 01: block id (1)
- ee ff gg hh: 4 bytes of block 1
- etc...
- 3F: block id (63)
- ii jj kk ll: 4 bytes of block 63
- 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 64 blocks of the tag data. They all have an identical structure:
block id followed by 4 (four) bytes of data. The last byte of the end of data packet is equal to 1 (one), which
means that the read operation has been successful.
d) Reader’s response (read failure)
If the reader cannot read the tag data, the reader’s response will be the following:
[xx xx yy zz zz zz zz vv] DE 00 02 81 00,
where:
- the first part of the response is optional and will be sent only if a tag of a different protocol was read
o xx xx: tag protocol
o yy: tag ID length
o zz zz zz zz: tag ID (yy bytes)
o vv: card type
- DE 00 02 81 00: end of data, where 00 02 – length, 81 – command ID, 00 – success status (01 means
failure)