ETTING CONFIGURATION OF CODE 39 SYMBOLOGY
ETTING A CONFIGURATION OF CODABAR SYMBOLOGY
ETTING A CONFIGURATION OF ALL SYMBOLOGIES
ODIFYING A CONFIGURATION OF ALL SYMBOLOGIES
ENDING A SPECIAL COMMAND TO CODE39 SYMBOLOGY
. ................. 30
. ................ 31
. .................. 32
. ................ 32
. ............... 33
APPENDIX 1: BLUETOOTH PROTOCOL ........................................... 34
BaracodaPencil 2 – Communication Protocol v1.3 - 2 -
Revision History
Revision History
Revision HistoryRevision History
Changes to the original manual are listed below.
Document Date Description
Data Capture
for Workforce
in Motion
1.1 26 Jan. 07
1.2 29 Sept. 08
1.3 02 Jan. 09
Initial release
Added new commands : 0x5A-0x5B : Get/Set master mode
Changed "barcode prefix/suffix" into "capture prefix/suffix"
Changed §2.3.5 "barcode messages" into "capture messages"
Changed command 0xE0-0xE1 name to "get capture version"
Add “Decoder Communication Protocol” section
Add “Appendix 1 – Bluetooth Protocol” section
BaracodaPencil 2 – Communication Protocol v1.3 - 3 -
Data Capture
Code ID
Length
Payload
1 Byte
2 Bytes
N Bytes
for Workforce
1.
1.
Introduction
Introduction
1.1.
IntroductionIntroduction
1.1.
1.1. Generalities
1.1.1.1.
BaracodaPencil 2 is a wireless data capture product.
This document is detailing the protocol of communication between the Baracoda scanner Pencil2
and its foreign environment through Radio Frequency link (ie: Bluetooth).
The protocol of communication does not depend on the type of link.
Wireless communication is based on the Bluetooth protocol, thanks to the embedded Baracoda
Equinox Bluetooth Stack.
The messages described in this document can be:
Host to scanner messages: the packet is sent only by the host to the scanner
Scanner to host messages: the packet is sent only by the scanner to the host
Bidirectional messages: the packet format is the same whether it is sent by the host or the scanner
Generalities
GeneralitiesGeneralities
in Motion
http://www.baracoda.com
1.2.
1.2. Generic packet
1.2.1.2.
All the frames described in this document are formatted as shown:
- 1 byte for code ID
• Bits 7:5 is the logical device
• Bits 4:1 is the command
• Bit 0: when set, the message must be acknowledged
- 2 bytes for the size of the payload (big-endian), including the sequence number byte which is
considered as part of the payload
- Payload (including 1 byte for sequence number when applicable).
The response will have the same code ID as the command.
Generic packet
Generic packetGeneric packet
BaracodaPencil 2 – Communication Protocol v1.3 - 4 -
Data Capture
Code ID
Description
Frame
0x01
Legacy
0x01 0x01 0
x01
Code ID
Description
Frame
0x06
ACK 0x06 0x01 0xYY
0x15
NACK
0x15 0x01 0xYY
Code ID
Description
Frame
0x16
SYN 0x16 0x01 0xYY
for Workforce
2.
2.
Communication protocol
Communication protocol
2.2.
Communication protocolCommunication protocol
2.1.
2.1. Bidirectional packets
2.1.2.1.
2.1.1.
2.1.1. Control messages
2.1.1.2.1.1.
Bidirectional packets
Bidirectional packetsBidirectional packets
Control messages
Control messagesControl messages
2.1.1.1. Specific packets
Or
0x01 0x02 0x01
These two (2) sequences will be recognized and purged for backward compatibility with older
Baracoda products.
2.1.1.2. Acknowledgment packets
in Motion
These messages acknowledge the reception of a valid message with the expected sequence number
0xYY, before processing it.
For captured data from the scanner, ACK and NAK have the same meaning but will trigger a different
event on the scanner.
2.1.1.3. Synchronization packet
This message acknowledges the reception of a message to acknowledge with an unexpected
sequence number. 0xYY is the expected sequence number.
The device will resynchronize its remote sequence number when receiving this message.
BaracodaPencil 2 – Communication Protocol v1.3 - 5 -
Data Capture
Code ID
Description
Payload
0x32
–
0x33
Barcode data
DATA
string
Data
0-32
0-32
0-32
for Workforce
2.2.
2.2. Scanner to host
2.2.2.2.
2.2.1.
2.2.1. Encapsulation scheme
2.2.1.2.2.1.
Scanner to host messages
Scanner to hostScanner to host
Encapsulation scheme
Encapsulation schemeEncapsulation scheme
messages
messagesmessages
2.2.2.
2.2.2. Data
2.2.2.2.2.2.
Data string format
DataData
string format
string formatstring format
in Motion
Timestamp
12 bytes
Data
Prefix
bytes
Capture
Prefix
0-32 bytes 0-4 bytes 0, 2 or 3 bytes - 0-4 bytes
Symbology
Prefix
AIM Identifier
Barcode / RFID
data
Symbology
suffix
Capture
suffix
bytes
suffix
bytes
BaracodaPencil 2 – Communication Protocol v1.3 - 6 -