Baracoda Pencil 2 User manual

Data Capture
for Workforce
in Motion
BaracodaPencil 2
Communication Protocol
©Baracoda
TM
– January 2009

BaracodaPencil 2 – Communication Protocol v1.3 - 2 -
Data Capture
for Workforce
in Motion
SUMMARY
SUMMARYSUMMARY
SUMMARY
SUMMARY................................................................... 2
REVISION HISTORY.......................................................... 3
1. INTRODUCTION ........................................................ 4
1.1. G ENERALITIES .......................................................... 4
1.2. G ENERIC PACKET ........................................................ 4
2. COMMUNICATION PROTOCOL .............................................. 5
2.1. B IDIRECTIONAL PACKETS ................................................... 5
2.1.1. C ONTROL MESSAGES .............................................. 5
2.2. S CANNER TO HOST MESSAGES ................................................ 6
2.2.1. E NCAPSULATION SCHEME ........................................... 6
2.2.2. D ATA STRING FORMAT ............................................ 6
2.3. H OST TO SCANNER MESSAGES ................................................ 7
2.3.1. C OMMUNICATION MESSAGES ......................................... 7
2.3.2. S CANNER MESSAGES .............................................. 9
2.3.3. U SER I NTERFACE MESSAGES ....................................... 11
2.3.4. M ISCELLANEOUS MESSAGES ........................................ 14
2.3.5. C APTURE MESSAGES ............................................. 18
2.4. D ECODER C OMMUNICATION P ROTOCOL .......................................... 21
2.4.1. FRAME FORMAT ................................................ 21
2.4.2. H EADER ..................................................... 21
2.4.3. T YPE ....................................................... 22
2.4.4. S IZE ....................................................... 22
2.4.5. C OMMAND .................................................... 22
2.4.6. E XAMPLES ................................................... 30
E XAMPLE 1.1 – G ETTING CONFIGURATION OF C ODE 39 SYMBOLOGY . ................. 30
E XAMPLE 2.1 – S ETTING A CONFIGURATION OF C ODABAR SYMBOLOGY . ................ 31
E XAMPLE 2.2 – S ETTING A CONFIGURATION OF ALL SYMBOLOGIES . .................. 32
E XAMPLE 3.1 – M ODIFYING A CONFIGURATION OF ALL SYMBOLOGIES . ................ 32
E XAMPLE 4.1 – S ENDING A SPECIAL COMMAND TO C ODE 39 SYMBOLOGY . ............... 33
APPENDIX 1: BLUETOOTH PROTOCOL...........................................34

BaracodaPencil 2 – Communication Protocol v1.3 - 3 -
Data Capture
for Workforce
in Motion
Revision History
Revision HistoryRevision History
Revision History
Changes to the original manual are listed below.
Document Date Description
1.1 26 Jan. 0 Initial release
1.2 29 Sept. 08 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"
1.3 02 Jan. 09 Add “Decoder Communication Protocol” section
Add “Appendix 1 – Bluetooth Protocol” section

BaracodaPencil 2 – Communication Protocol v1.3 - 4 -
Data Capture
for Workforce
in Motion
1.
1.1.
1. Introduction
IntroductionIntroduction
Introduction
1.1.
1.1.1.1.
1.1. Generalities
GeneralitiesGeneralities
Generalities
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
http://www.baracoda.com
1.2.
1.2.1.2.
1.2. Generic packet
Generic packetGeneric packet
Generic packet
All the frames described in this document are formatted as shown:
Code ID
Length
Payload
1 Byte
2 Bytes
N Bytes
- 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.

BaracodaPencil 2 – Communication Protocol v1.3 - 5 -
Data Capture
for Workforce
in Motion
2.
2.2.
2. Communication protocol
Communication protocolCommunication protocol
Communication protocol
2.1.
2.1.2.1.
2.1. idirectional packets
idirectional packetsidirectional packets
idirectional packets
2.1.1.
2.1.1.2.1.1.
2.1.1. Control messages
Control messagesControl messages
Control messages
2.1.1.1. Specific packets
Code ID
Description
Frame
0x01
Legacy
0x01 0x01 0
x01
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
Code ID
Description
Frame
0x06
ACK
0x06 0x01 0xYY
0x15
NACK
0x15 0x01 0xYY
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
Code ID
D
escription
Frame
0x16
SYN
0x16 0x01 0xYY
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 - 6 -
Data Capture
for Workforce
in Motion
2.2.
2.2.2.2.
2.2. Scanner to host
Scanner to hostScanner to host
Scanner to host messages
messagesmessages
messages
2.2.1.
2.2.1.2.2.1.
2.2.1. Encapsulation scheme
Encapsulation schemeEncapsulation scheme
Encapsulation scheme
Code ID
Description
Payload
0x32
–
0x33
Barcode data
DATA
string
2.2.2.
2.2.2.2.2.2.
2.2.2. Data
DataData
Data string format
string formatstring format
string format
Timestamp Data
Prefix
Capture
Prefix
Symbology
Prefix AIM Identifier Barcode / RFID data
Symbology
suffix
Capture
suffix
Data
suffix
12 bytes
0
-
32
bytes 0-32 bytes 0-4 bytes 0, 2 or 3 bytes - 0-4 bytes
0
-
32
bytes
0
-
32
bytes

BaracodaPencil 2 – Communication Protocol v1.3 - -
Data Capture
for Workforce
in Motion
2.3.
2.3.2.3.
2.3. Host to scanner
Host to scannerHost to scanner
Host to scanner messages
messagesmessages
messages
2.3.1.
2.3.1.2.3.1.
2.3.1. Communication messages
Communication messagesCommunication messages
Communication messages
Code ID
0x40
-
0x41
Description
Get Communication escriptor
Payload
None
Response
2 bytes:
{Wireless link: (Bit 0: Bluetooth)}
{Wired link: (Bit 0: Serial Dock)}
Code ID
0x42
-
0x43
Description
Get Retransmission Parameters
Payload
None
Response
2 bytes:
{Max number of retransmission, 1 to 0xFE, 0xFF = infinity}
{Delay between transmission, 1 to 0xFF, in tenth of seconds}
Code ID
0x44
-
0x45
Description
Set Retransmission Parameters
Payload
2 bytes:
{Max number of retransmissions, 1 to 0xFE, 0xFF = infinity}
{Delay between transmissions, 1 to 0xFF, in tenth of seconds}
Response
1 b
yte:
{(Bit 0: Success)}
Code ID
0x46
-
0x4
Description
Get Capture Frame Format
Payload
None
Response
1 byte
{0 = Baracoda, 1 = Baracoda + ACK, 2 = Raw}
Code ID
0x48
-
0x49
Description
Set Capture Frame Format
Payload
1 byte
{0 = Baracoda, 1 = Baracoda + ACK, 2 = Raw}
Response
1 byte:
{Bit0: Success}

BaracodaPencil 2 – Communication Protocol v1.3 - 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
0x52
-
0x53
Description
isable Barcode Programming F
unctionality
Payload
1 byte :
{1 = Disable barcode programming functionality,
0 = Enable}
Response
1 byte : {Bit 0 : Success}
Code ID
0x56
-
0x5
Description
Get/Set In charge behavior
Payload
Get : None
Set : 1 byte :
{shutdown timeout (0 = leave current timeouts (default), 255 = infinity)}
Response
Get : 1 byte :
{shutdown timeout (0 = leave current timeouts (default), 255 = infinity)}
Set : 1 byte :
{Bit 0 : Success}
Remarks
When scanner in charge, the shutdown timers can be modified
Code I
D
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}
Set : 1 byte :
{Bit 0 : Success}
Cod
e ID
0x5E
-
0x5F
Description
Bluetooth Commands
Payload
{Code ID} “Parameters”
Response
If the device responds: {Code ID} “Response”
Else: {0}
Bluetooth specific commands from the Platform2 Bluetooth communication protocol are to be
framed within the payload of this message.

BaracodaPencil 2 – Communication Protocol v1.3 - 9 -
Data Capture
for Workforce
in Motion
2.3.2.
2.3.2.2.3.2.
2.3.2. Scanner messages
Scanner messagesScanner messages
Scanner messages
Code ID
0x60
-
0x61
Description
Get Scanner Status
Payload
None
Response
2 bytes:
{(Bit : Upgrading) (Bit 1: Docked) (Bit 0: Charging)}
{Battery level, 0 to 100}
Code ID
0x62
-
0x63
Description
Get Operating Mode
Payload
None
Response
1 byte:
{Bit 0 = 0:real time, Bit 0 = 1: batch}
{(Bit : limited)}
Remarks
“limited” means barcode buffer = 0 when in real time, no data loss mode and
disconnected
Code ID
0x64
-
0x65
Description
Set Operating Mode
Payload
1 byt
e:
{Bit 0 = 0: real time, Bit 0 = 1: batch}
If real time mode is set :
{(Bit : limited)(Bit 6: ACK beep) (Bit 5: no ACK beep)}
NOTE : the ACK beep enable / disable is only effective when Capture Frame Format is
“Baracoda + ACK”
Response
1 byte:
{Bit 0: Success}
Remarks
Batch mode is not available for D
-
Fly scanner
Code ID
0x66
-
0x6
Description
Get Shutdown Timers
Payload
None
Response
2 bytes:
{Number of minutes before shutdown when connected, 1 to 0xFE,
0xFF = infinity}
{Number of minutes before shutdown when disconnected, 1 to 0xFE,
0xFF = infinity}
Code ID
0x68
-
0x69
Description
Set Shutdown Timers
Payload
2 bytes:
{Number of minutes before shutdown when connected, 1 to 0xFE,
0xFF = infinity}

BaracodaPencil 2 – Communication Protocol v1.3 - 10 -
Data Capture
for Workforce
in Motion
{Number of minutes before shutdown when disconnect
ed, 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}
Code ID
0x6C
-
0x6D
Description
Set RTC time
Payload
6 bytes:
{YY}{MM}{DD}{HH}{MM}{SS}
Response
1 byte:
{Bit 0: Success}
Code ID
0x 4
-
0x 5
Description
Restore defaults settings
Payload
None
Response
1 byte:
{Bit 0: Success}
Remarks
External Flash memory is also erased
Code ID
0x 6
-
0x
Description
Get Product Version
Payload
None
Response
x bytes :
«BaracodaPencil2…»
Code ID
0x 8
-
0x 9
Description
Get Switching On elay
Payload
None
Response
1 byte :
{1 = 0 second, 2 = 1 second, 3 = 2 seconds}
Code ID
0x A
-
0x B
Description
Set Switching On elay
Payload
1 byte :
{1 = 0 second, 2 = 1 second, 3 = 2 seconds}
Response
1 byte :
{Bit 0 :Success}

BaracodaPencil 2 – Communication Protocol v1.3 - 11 -
Data Capture
for Workforce
in Motion
2.3.3.
2.3.3.2.3.3.
2.3.3. User Interface messages
User Interface messagesUser Interface messages
User Interface messages
Code ID
0x80
-
0x81
Description
Get MMI escriptor
Payload
None
Response
2 bytes:
{(Bit 6: Blue LED 1)
(Bit 5: Red LED 1)
(Bit 4: Green LED 1)
(Bit 2: Blue LED 0)
(Bit 1: Red LED 0)
(Bit 0: Green LED 0)}
{(Bit 0: Buzzer)}
Code ID
0x82
-
0x83
Description
Get MMI Mode
Payload
None
Response
1 byte:
{(Bit 1: Buzzer Enabled) (Bit 0: LEDs enabled)}
Code ID
0x84
-
0x85
Description
Set MMI Mode
Payload
1 by
te:
{(Bit 1: Buzzer Enabled) (Bit 0: LEDs enabled)
(Bit = 0:Buzzer config select, =1: Buzzer config deselect)(Bit 6 = 0:leds config select, =1:
leds config deselect)}
Response
1 byte: {(Bit 0: Success)}
Code ID
0x86
-
0x8
Description
Get MMI Signal (U
ser interface)
Payload
1 byte:
{Signal number, 0 - 3}
Response
(1 + 3n) bytes:
{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) (Bit 1: Red
LED 0) (Bit 0: Green LED 0)}
{Buzzer frequency, 0 – 0xFF * 50Hz = 0 – 12 50Hz}
{Delay until next step, in tenth of seconds}
Code ID
0x88
-
0x89
Description
Set MMI Signal
Payload
(2 + 3n) bytes
{Signal number, 0 - 3}
{Number of steps, 0 - 4}

BaracodaPencil 2 – Communication Protocol v1.3 - 12 -
Data Capture
for Workforce
in Motion
For each step:
{(Bit 6: Blue LED 1) (Bit 5: Red LED 1) (Bit 4: Green LED 1) (Bit 2: Blue LED 0) (Bit 1: Red
LED 0) (Bit 0: Green LED 0)}
{Buzzer frequency, 0 – 0xFF * 50Hz = 0 – 12 50Hz}
{Delay until next step, in tenth of seconds}
Response
1 byte: {(Bit 0: Success)}
Code ID
0x8A
-
0x8B
Description
Play
Signal
Payload
2 bytes:
{Signal number, 0 - 3}
{Number of loops, 0 – 0xFE, 0xFF = infinity}
Response
1 byte: {(Bit 0: Success)}
Code ID
0x8C
-
0x8D
Description
Stop Signal
Payload
1 byte:
{Signal number, 0 – 3}
Response
1 byte:
{(Bit 0: Success)}
The list of MMI signals is:
IHM_SIGNAL_CAPTURE_READ : 0
IHM_SIGNAL_CAPTURE_ACK : 1
IHM_SIGNAL_CAPTURE_NAK : 2
IHM_SIGNAL_CAPTURE_LOST : 3
Code ID
0x92
-
0x93
Description
Get Beeps mode
Payload
Response
1 byte:
{(Bit 0: Beep level 0=low, 1=high)
(Bit 1: Read beep)
(Bit 2: ACK beep)}
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 = 0: ACK beep config select, =1: ACK beep config deselect)
(Bit 6 = 0: Read beep config select, =1: Read beep config deselect)
(Bit 5 = 0: Beep level config select, =1: Beep level config deselect)}}

BaracodaPencil 2 – Communication Protocol v1.3 - 13 -
Data Capture
for Workforce
in Motion
Response
1 byte:
{(Bit 0: Success)}

BaracodaPencil 2 – Communication Protocol v1.3 - 14 -
Data Capture
for Workforce
in Motion
2.3.4.
2.3.4.2.3.4.
2.3.4. Miscellaneous messages
Miscellaneous messagesMiscellaneous messages
Miscellaneous messages
Code ID
0xC2
-
0xC3
Description
Get/Set ataPrefix
Payload
Get : None
Set : 1-33 bytes:
{ DataPrefix length}
“DataPrefix String”
Response
Get : 1
-
33 bytes:
{ DataPrefix length}
“DataPrefix String”
Set : 1 byte:
{Success?}
Code ID
0xC4
-
0xC5
Description
Get/Set ataSuffix
Payload
Get : None
Set : 1-33 bytes:
{ DataSuffix length}
“DataSuffix String”
Response
Get : 1
-
33 bytes:
{ DataSuffix length}
“DataSuffix String”
Set : 1 byte:
{Success?}
Code ID
0xC6
-
0xC
Description
Get/Set ata Format 2
Payload
Get : None
Set : 1 byte:
{(Bit 5 = 0: DataPrefix config select, =1: DataPrefix config deselect)
(Bit 4 = 0: DataSuffix config select, =1: DataSuffix config deselect)
(Bit 1: DataPrefix)
(Bit 0: DataSuffix)
Response
Get : 1 byte:
{(Bit 1: DataPrefix)
(Bit 0: DataSuffix)}
Set : 1 byte:
{(Bit 0:Success)}

BaracodaPencil 2 – Communication Protocol v1.3 - 15 -
Data Capture
for Workforce
in Motion
Code ID
0xC8
-
0xC9
Description
Get / Set Barcode length
Payload
Get : None
Set : 2 bytes
{authorized barcode length. 0 = disabled}
Response
Get : 2 bytes
{authorized barcode length. 0 = disabled}
Set : 1 byte
{(Bit 0:Success)}
Code ID
0xCA
-
0xCB
Desc
ription
Get and erase stored barcodes with no data loss mode
Payload
None
Response
1 byte
{(Bit 0:Success)}
Code ID
0xCC
-
0xCD
Description
Res
et modes
Payload
None = restore defaults, keep link keys, reboot scanner
1byte :
0 = restore defaults, keep link keys, reboot scanner
1 = switch off scanner (no restoring defaults)
2 = reboot scanner (no restoring defaults)
Response
1 byte
{(Bit 0:Success)}
Code ID
0xCE
-
0xCF
Description
Batch upload commands
Payload
{Code ID} “Parameters” (cf. below)
Respo
nse
{Code ID} “Response”
The UPLOAD Code IDs are:
Code ID
0
Description
Launch upload process (typically used only for the upload barcode)
Payload
1 byte:
{0 mandatory}
Response
1 byte:
{Bit 0: Success}
Code ID
1
Description
Ready to start upload
(Scanner to host message)
Payload
3 bytes :
{0 mandatory}

BaracodaPencil 2 – Communication Protocol v1.3 - 16 -
Data Capture
for Workforce
in Motion
{ number of elements to be uploaded MSB }
{ number of elements to be uploaded LSB }
Response
None
Code ID
2
Description
Start uploading barcodes
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 process
Payload
2 bytes :
{0 mandatory}
{1 : upload successful, data can be erased from the scanner
0 : upload failed, do not erase data}
Response
1 byte:
{Bit 0: Success}
Code ID
0xD2
-
0xD3
Description
Get/Set Anti duplicate scans
Payload
Get : None
Set : 1 byte
{0 = disabled
1 = no consecutive duplicate scans + error signal
2 = no consecutive duplicate scans + no decoding}
Response
Get : 1 byte
{0 = disabled
1 = no consecutive duplicate scans + error signal
2 = no consecutive duplicate scans + no decoding }
Set : 1 byte
{(Bit 0:Success)}
Comments
The comparison will be made over the 32
first characters of the barcodes only.
Code ID
0xD4
-
0xD5
Description
Restore last batch
Payload
None
or 1 byte (optional):

BaracodaPencil 2 – Communication Protocol v1.3 - 1 -
Data Capture
for Workforce
in Motion
{1 = upload data after retrieving}
Response
1 byte:
{(Bit 0:Success)}
Comments
This is only available if no new scan has
been made.
Code ID
0xD8
-
0xD9
Description
Enable remote trigger
Payload
None : use default 5s timeout
1 byte : {timeout (s)}
Response
1 byte
{(Bit 0:Success)}

BaracodaPencil 2 – Communication Protocol v1.3 - 18 -
Data Capture
for Workforce
in Motion
2.3.5.
2.3.5.2.3.5.
2.3.5. Capture
CaptureCapture
Capture messages
messagesmessages
messages
Code ID
0xE0
-
0xE1
Description
Get
Capture
Version
Payload
None
Respon
se
“Capture Version String” or {0} if not applicable
Code ID
0xE2
-
0xE3
Description
Get Mode
Payload
None
Response
1 byte:
{0 = trigger, , 2 = disabled}
Code ID
0xE4
-
0xE5
Description
Set Mode
Payload
1 byte OR
{0 = trigger, 2 = disabled}
Response
1 byte:
{(Bit 0: Success)}
Code ID
0xE6
-
0xE
Description
Get ata Format
Payload
None
Response
1 byte:
{(Bit 2:Timestamp)
(Bit 1: Capture Prefix)
(Bit 0: Capture Suffix)}
Code ID
0xE8
-
0xE9
Description
Set ata Format
Payload
1 byte:
{(Bit = 0: Timestamp config select, =1: Timestamp config deselect)
(Bit 6 = 0: Capture Prefix config select, =1: Capture Prefix config deselect)
(Bit 5 = 0: Capture Suffix config select, =1: Capture Suffix config deselect)
(Bit 2:Timestamp)
(Bit 1: Capture Prefix)
(Bit 0: Capture Suffix) }
Response
1 byte:
{(Bit 0:Success)}
Code ID
0xEA
-
0xEB
Description
Get
Capture
Prefix
Payload
None
Response
1
-
33 bytes:
{ Capture Prefix length}

BaracodaPencil 2 – Communication Protocol v1.3 - 19 -
Data Capture
for Workforce
in Motion
“Capture Prefix String”
Code ID
0xEC
-
0xED
Description
Set
Capture
Prefix
Paylo
ad
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
Response
1
-
33 bytes:
{ Capture Suffix length}
“Capture Suffix String”
Code ID
0xF0
-
0xF1
Description
Set
Capture
Suffix
Payload
1
-
33 bytes:
{ Capture Suffix length}
“Capture Suffix String”
Response
1 byte:
{(Bit 0:Success)}
Code ID
0xF4
-
0xF5
Description
Set Timestamp
Payload
6 bytes:
{YY}{MM}{DD}{HH}{MM}{SS}
Response
1 byte:
{Bit 0: Success}
Remark
This feature is not available in the D
-
Fly Product
Code ID
0xF6
-
0xF
Description
Set AIM Symbology Identifier transmission
Payload
1 byte:
{0 : disabled, 1 : enabled}
Response
1 byte:
{Bit 0: Success}
Code ID
0xF8
-
0xF9
Description
G
et stored barcodes count
Payload
None
Response
2 bytes:

BaracodaPencil 2 – Communication Protocol v1.3 - 20 -
Data Capture
for Workforce
in Motion
{Stored barcodes count [15:8]}
{Stored barcodes count [ :0]}
Code ID
0xFA
-
0xFB
Description
Get and erase stored barcodes
Payload
None
Response
1 byte:
{(Bit 0:Success)}
Code ID
0xFC
-
0xFD
De
scription
Erase stored barcodes
Payload
None
Response
1 byte:
{(Bit 0:Success)}
Code ID
0xFE
-
0xFF
Description
Barcode decoder Commands
Payload
{header} {type} {size} “Parameters”
Response
If the device responds:
{Code ID}{length}{header}{type} {response size} “Response”
Else: {0}
Barcode decoder specific commands from the Platform2 Decoder communication protocol are to be
framed within the payload of this message.