1. DL manuals
  2. Baracoda
  3. Scanner
  4. TagRunners
  5. Supplementary Manual

Baracoda TagRunners Supplementary Manual

Manual is about: Baracoda TagRunners: User Guide

Summary of TagRunners

  • Page 1

    Data capture for workforce in motion tagrunners communication protocol ©baracoda tm – december 2008.

  • Page 2

    Tagrunners – communication protocol v1.4 - 2 - data capture for workforce in motion summary summary summary summary summary ................................................................... 2 revision history .......................................................... 3 1. 1. 1. 1. Introduction ......

  • Page 3

    Tagrunners – communication protocol v1.4 - 3 - data capture for workforce in motion revision history revision history revision history revision history changes to the original manual are listed below. Document date description 1.0 23 dec. 08 initial release 1.2 23 dec. 08 modified §2.2.1, 2.2.2. Upd...

  • Page 4

    Tagrunners – communication protocol v1.4 - 4 - data capture for workforce in motion 1. 1. 1. 1. Introduction 1.1. 1.1. 1.1. 1.1. Generalities generalities generalities generalities tagrunners is a wireless rfid data capture product (13.56mhz). This document is detailing the protocol of communication...

  • Page 5

    Tagrunners – communication protocol v1.4 - 5 - data capture for workforce in motion 2. 2. 2. 2. Communication protocol 2.1. 2.1. 2.1. 2.1. Bidirectional bidirectional bidirectional bidirectional packets packets packets packets 2.1.1. Control messages 2.1.1.1. Specific packets code id description fra...

  • Page 6

    Tagrunners – communication protocol v1.4 - 6 - data capture for workforce in motion 2.2. 2.2. 2.2. 2.2. Scanner to hos scanner to hos scanner to hos scanner to host t t t messages messages messages messages 2.2.1. Encapsulation scheme code id description payload 0x34–0x35 rfid data (tagid) data stri...

  • Page 7

    Tagrunners – communication protocol v1.4 - 7 - data capture for workforce in motion 2.3. 2.3. 2.3. 2.3. Host to host to host to host to scanner scanner scanner scanner messages messages messages messages 2.3.1. Communication messages code id 0x40-0x41 description get communication descriptor payload...

  • Page 8

    Tagrunners – communication protocol v1.4 - 8 - data capture for workforce in motion code id 0x50-0x51 description lock/unlock scan engine payload 1 byte : {0 = unlock, 1 = lock} response 1 byte : {bit 0 : success} code id 0x54-0x55 description get/set dock use payload get : none set : 1 byte : {0 = ...

  • Page 9

    Tagrunners – communication protocol v1.4 - 9 - data capture for workforce in motion code id 0x5a-0x5b description get/set master mode payload get : none set : 1-2 byte(s) : {1 : enable, 0 : disable} [optional]{1 : disconnect the scanner if connected} response get : 1 byte : {1 : enabled 0 : disabled...

  • Page 10

    Tagrunners – communication protocol v1.4 - 10 - data capture for workforce in motion 2.3.2. Scanner messages code id 0x60-0x61 description get scanner status payload none response 2 bytes: {(bit 7: upgrading) (bit 1: docked) (bit 0: charging)} {battery level, 0 to 100} code id 0x62-0x63 description ...

  • Page 11

    Tagrunners – communication protocol v1.4 - 11 - data capture for workforce in motion {number of minutes before shutdown when disconnected, 1 to 0xfe, 0xff = infinity} response 1 byte: {bit 0: success} code id 0x6a-0x6b description get rtc time payload none response 6 bytes: {yy}{mm}{dd}{hh}{mm}{ss} ...

  • Page 12

    Tagrunners – communication protocol v1.4 - 12 - data capture for workforce in motion 2.3.3. User interface messages led 1 : left led led 0 : right led code id 0x80-0x81 description get mmi descriptor payload none response 2 bytes: {(bit 6: blue led 1) (bit 5: red led 1) (bit 4: green led 1) (bit 2: ...

  • Page 13

    Tagrunners – communication protocol v1.4 - 13 - data capture for workforce in motion code id 0x88-0x89 description set mmi signal payload (2 + 3n) bytes {signal number, 0 - 3} {number of steps, 0 - 4} for each step: {(bit 6: blue led 1) (bit 5: red led 1) (bit 4: green led 1) (bit 2: blue led 0) (bi...

  • Page 14

    Tagrunners – communication protocol v1.4 - 14 - data capture for workforce in motion code id 0x94-0x95 description set beeps mode payload 1 byte: {(bit 0: beep level; 0=low, 1=high) (bit 1: read beep) (bit 2: ack beep) (bit 7 = 0: ack beep config select, =1: ack beep config deselect) (bit 6 = 0: rea...

  • Page 15

    Tagrunners – communication protocol v1.4 - 15 - data capture for workforce in motion 2.3.4. Miscellaneous messages code id 0xc2-0xc3 description get/set dataprefix payload get : none set : 1-33 bytes: { dataprefix length} “dataprefix string” response get : 1-33 bytes: { dataprefix length} “dataprefi...

  • Page 16

    Tagrunners – communication protocol v1.4 - 16 - data capture for workforce in motion set : 2 bytes {authorized rfid data length. 0 = disabled} response get : 2 bytes {authorized rfid data length. 0 = disabled} set : 1 byte {(bit 0:success)} code id 0xca-0xcb description get and erase stored data wit...

  • Page 17

    Tagrunners – communication protocol v1.4 - 17 - data capture for workforce in motion code id 2 description start uploading data payload 1 byte: {0 mandatory} response 1 byte: {bit 0: success} code id 3 description reserved payload n/a response n/a code id 4 description set upload status and end proc...

  • Page 18

    Tagrunners – communication protocol v1.4 - 18 - data capture for workforce in motion code id 0xd8-0xd9 description enable remote trigger payload none : use default 5s timeout 1 byte : {timeout (s)} response 1 byte {(bit 0:success)} code id 0xde-0xdf description rfid commands payload {code id} “param...

  • Page 19

    Tagrunners – communication protocol v1.4 - 19 - data capture for workforce in motion 2.3.5. Capture messages code id 0xe2-0xe3 description get mode payload none response 1 byte: {0 = trigger, 1 = smart autoscan, 2 = disabled, 3= autoscan } code id 0xe4-0xe5 description set mode payload 1 byte or 2 b...

  • Page 20

    Tagrunners – communication protocol v1.4 - 20 - data capture for workforce in motion code id 0xec-0xed description set capture prefix payload 1-33 bytes: { capture prefix length} “capture prefix string” response 1 byte: {(bit 0:success)} code id 0xee-0xef description get capture suffix payload none ...

  • Page 21

    Tagrunners – communication protocol v1.4 - 21 - data capture for workforce in motion appendix 1 appendix 1 appendix 1 appendix 1: bluetooth protocol : bluetooth protocol : bluetooth protocol : bluetooth protocol the configuration frames are as follows: the configuration frames are as follows: the co...

  • Page 22

    Tagrunners – communication protocol v1.4 - 22 - data capture for workforce in motion command set mode header 0x03 (flash only) length 00 02 payload 0x01 if master, 0x00 if slave, [role switch] response 0x03 00 01 01 if done 0x03 00 01 00 if not when in master, the module connects to the address spec...

  • Page 23

    Tagrunners – communication protocol v1.4 - 23 - data capture for workforce in motion command get bluetooth version header 0x76 length 00 00 payload response 0x76, x, x, {version string } command restore factory settings header length payload ('r', 's', 't') response command get inquiry scan timeout ...

  • Page 25

    Tagrunners – communication protocol v1.4 - 25 - data capture for workforce in motion command set sniff header 0x09 length 00 04 payload [msb of minsniff interval, lsb of minsniff interval, msb of maxsniff interval, lsb of maxsnif interval] response 0x09 00 01 01 if done 0x09 00 01 00 if not remark c...

  • Page 26

    Tagrunners – communication protocol v1.4 - 26 - data capture for workforce in motion low power (medium speed): minsniff = 0x0050 maxsniff = 0x00f0 attempt = 0x0008 timeout = 0x0030 maxsniff and minsniff are only used for sniff negotiation between the smart module and the other bt device. If both sid...

  • Page 27

    Tagrunners – communication protocol v1.4 - 27 - data capture for workforce in motion command get security mode header 0x20 length 00 00 payload response 0x20 00 01 01 if secured 0x20 00 01 00 if non secured remark command set security mode header 0x21 length 00 {size} payload {00 non secured, 01 sec...

  • Page 28

    Tagrunners – communication protocol v1.4 - 28 - data capture for workforce in motion typical bluetooth class of device: peripheral 0x000500 (default) undefined 0x001f00 phone 0x502204 computer 0x120104 pda 0x100114 access point 0x120320 command set remote rfcomm channel header 0x36 length 00 01 payl...

  • Page 29

    Tagrunners – communication protocol v1.4 - 29 - data capture for workforce in motion payload response 0x39 00 02 [uuid] remark try to connect to this remote service. Here are some service uuid: spp 0x1101 dun 0x1103 fax 0x1102 you can get more uuids by reading the bluetooth spec. Command get encrypt...

  • Page 30

    Tagrunners – communication protocol v1.4 - 30 - data capture for workforce in motion appendix 2 appendix 2 appendix 2 appendix 2: : : : rfid communication protocol rfid communication protocol rfid communication protocol rfid communication protocol introduction introduction introduction introduction ...

  • Page 31

    Tagrunners – communication protocol v1.4 - 31 - data capture for workforce in motion bit 10 : rfu bit 11 : rfu bit 12 : rfu bit 13 : rfu bit 14 : rfu bit 15 : rfu bit 16 : rfu for the deselect mask, a set bit masks its configuration. Example : the current active protocols mask value is 0xffff (all p...

  • Page 32

    Tagrunners – communication protocol v1.4 - 32 - data capture for workforce in motion a set bit means that a key has been loaded at this emplacement. Remarks for mifare cards, a 6-byte security key is needed to access the data. The scanner is able to handle 16 keys for each of the 2 key sets (a and b...

  • Page 33

    Tagrunners – communication protocol v1.4 - 33 - data capture for workforce in motion communication messages code id 0x80 description find tag and get id (tagrunners only) payload 0-3bytes: [optional 2 bytes] : {protocol mask} [optional 1 byte] : {timeout (s)} response none if no tag detected else x ...

  • Page 34

    Tagrunners – communication protocol v1.4 - 34 - data capture for workforce in motion 01 : mifare ultralight card 02 : mifare 1k card 03 : mifare 4k card etc. The complete list of card types codes is shown below } for each read sector/page: if mifare ultralight : {1b : page number 4b : data} if mifar...

  • Page 35

    Tagrunners – communication protocol v1.4 - 35 - data capture for workforce in motion for the two above commands, the complete list of card types codes for read/write compatibility: code protocol manufacturer card type compatibility 0x01 iso 14443-a nxp mifare ultralight yes 0x02 iso 14443-a nxp mifa...

  • Page 36

    Tagrunners – communication protocol v1.4 - 36 - data capture for workforce in motion (blocks 8-9 uid, block 10 afi) tag-it hf-i pro chip/inlay 48 bytes: 12 4-byte blocks (blocks 8-9 uid, block 10 afi, block 11 password) lri64 14 bytes: 14 1-byte blocks (blocks 0-7 uid, block 8 afi, block 9 dsfid).