Baracoda RoadRunners Laser Supplementary Manual
  1. Manuals
  2. Brands
  3. Baracoda Manuals
  4. Scanner
  5. RoadRunners Laser
  6. Supplementary manual

Baracoda RoadRunners Laser Supplementary Manual

Communication-protocol
Hide thumbs Also See for RoadRunners Laser:
Table of Contents

Advertisement

Quick Links

Download this manual See also: Programming Manual, User Manual
RoadRunners-Communication-Protocol
Baracoda, Inc. (US Office)
45 Main street - Suite 616 - Brooklyn, NY 11201
Ph: 718 488 9600 - Fx: 718 488 9601
The bluetooth name and Bluetooth registered trademarks are owned by Bluetooth SIG, Inc., and are used by Baracoda under license. The Baracoda names and
Baracoda trademarks are own by Baracoda. All specifications are subject to change without notice - Non contractual pictures © Baracoda - All rights reserved
Data Capture for
Workforce in Motion
Baracoda SA (Europe Office: France)
30 Avenue de l'Amiral Lemonnier - 78160 Marly-Le-Roi
Ph: +33 1 30 08 89 00 - Fx: +33 1 30 08 89 98

Advertisement

Table of Contents
loading

Related Manuals for Baracoda RoadRunners Laser

Summary of Contents for Baracoda RoadRunners Laser

  • Page 1 Ph: 718 488 9600 - Fx: 718 488 9601 The bluetooth name and Bluetooth registered trademarks are owned by Bluetooth SIG, Inc., and are used by Baracoda under license. The Baracoda names and Baracoda trademarks are own by Baracoda. All specifications are subject to change without notice - Non contractual pictures © Baracoda - All rights reserved...

  • Page 2: Table Of Contents

    RoadRunners – Communication Protocol SUMMARY ... 2 INTRODUCTION ... 3 Protocol of communication... 4 Bidirectionnal packets ... 4 1.1. Generic packet ... 4 1.1.1. Format of that packet ... 4 1.1.2. Explanations ... 4 1.2. Control messages... 5 1.2.1. Specifics packets ... 5 1.2.2.

  • Page 3: Introduction

    Wireless communication based on the Bluetooth protocol Barcode reader thanks to a CMOS technology (1D & 2D) This document is detailing the protocol of communication between the Baracoda scanner RoadRunners with its foreign environment through : Radio Frequency link (ie : Bluetooth) Wired link (ie : RS232 cable) The protocol of communication does not depend on the type of link.

  • Page 4: Protocol Of Communication

    RoadRunners – Communication Protocol Protocol of communication 1. Bidirectionnal packets 1.1. Generic packet All frames that are described in the following have to follow the following format of packet. That is available for communication from the scanner to the host and from the host to the scanner. 1.1.1.

  • Page 5: Control Messages

    1.2. Control messages 1.2.1. Specifics packets Code ID 0x01 These 2 sequences will be recognized and purged for backward compatibility with other Baracoda products. 1.2.2. Acknowledgment packets Code ID 0x06 0x15 These messages acknowledge the reception of a valid message with the expected sequence number 0xYY, before processing it.

  • Page 6: Between The Scanner And The Remote Application

    RoadRunners – Communication Protocol 2. Between the SCANNER and the REMOTE APPLICATION Code ID Description Payload 0x32–0x33 Barcode data Barcode string TF - Protocol of communication 6/46 January 2007...

  • Page 7: Between The Remote Aplication And The Scanner

    Code ID 0x46-0x47 Description Get Capture Frame Format Payload None Response 1 byte {0 = Baracoda’s frames, 1 = Baracoda’s frames + ACK, 2 = Raw} Code ID 0x48-0x49 Description Set Capture Frame Format Payload 1 byte {0 = Baracoda’s frames, 1 = Baracoda’s frames + ACK,...
  • Page 8 RoadRunners – Communication Protocol Code ID 0x4A-0x4B Description Get Support Data Payload Response 1Byte {Battery level (%)} 2Bytes {Size of CPU Version string} xBytes {CPU Version} 2Bytes {Size of BT Version} xBytes {BT Version} 6Bytes {BDAdress} 1Byte {BT Secure Mode} 1Byte {Scanner Operating Mode (Real Time/Batch)} 1Byte {Limited Mode} –...

  • Page 9: Dock Code Ids

    RoadRunners – Communication Protocol Code ID 0x56-0x57 Description Payload Response Code ID 0x5C-0x5D Description Dock Commands Payload {Code ID} “Parameters” Response If the device responds: {Code ID} “Response” Else: {0} Code ID 0x5E-0x5F Description Bluetooth Commands Payload {Code ID} “Parameters” Response If the device responds: {Code ID} “Response”...

  • Page 10: Scanner Messages

    {(Bit 7: limited – ie : no data loss mode)(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:...
  • Page 11 NOTE : Flash memory is also erased Code ID 0x76-0x77 Description Get Product Version Payload None Response 16 bytes : «Baracoda Abeille» Code ID 0x78-0x79 Description Get Switching On Delay Payload None Response 1 byte : {1 = 0 second, 2 = 1 second, 3 = 2 seconds}...
  • Page 12 RoadRunners – Communication Protocol Code ID 0x7A-0x7B Description Payload Response Code ID 0x7C-0x7D Description Payload Response Code ID 0x7E-0x7F Description Payload Response TF - Protocol of communication January 2007 12/46...

  • Page 13: User Interface Messages

    RoadRunners – Communication Protocol 3.3. User Interface messages Code ID 0x80-0x81 Description Get MMI Descriptor (User Interface) Payload None Response 2 bytes: {(Bit 6: NA) (Bit 5: Red LED 1 – left one) (Bit 4: Green LED 1 – left one) (Bit 2: NA) (Bit 1: Red LED 0 –...
  • Page 14 RoadRunners – Communication Protocol 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: NA) (Bit 5: Red LED 1) (Bit 4: Green LED 1) (Bit 2: NA) (Bit 1: Red LED 0) (Bit 0: Green LED 0)} {Buzzer frequency, 0 –...
  • Page 15 RoadRunners – Communication Protocol 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 7 = 0: ACK beep config select, =1: ACK beep config...

  • Page 16: Miscellaneous Messages (Host To Scanner)

    RoadRunners – Communication Protocol 3.4. Miscellaneous messages (host to scanner) Code ID 0xC0-0xC1 Description Payload Response Code ID 0xC2-0xC3 Description Get / Set PostPrefix Payload Get : None Set : 1-33 bytes Response Get : 1-33 bytes Set : 1 byte Code ID 0xC4-0xC5 Description...
  • Page 17 RoadRunners – Communication Protocol Code ID 0xC8-0xC9 Description Get / Set Barcode length Payload Get : None Set : 2 bytes {authorized barcode length} Response Get : 2 bytes Set : 1 byte Code ID 0xCA-0xCB Description Get & erase stored barcodes with ‘no data loss mode’ Payload None Response...

  • Page 18: Barcode Messages

    RoadRunners – Communication Protocol 3.5. Barcode messages Code ID 0xE0-0xE1 Description Get Barcode Version Payload None Response “Barcode Version String” or {0} if not applicable Code ID 0xE2-0xE3 Description Get Mode Payload None Response 1 byte: {0 = trigger, 1 = autoscan, 2 = disabled, 3 = true autoscan, 4 = aiming trigger scan} Code ID 0xE4-0xE5...
  • Page 19 Get and erase stored barcodes and Reset USB Plug and Scan Dongle Payload None Response 1 byte: {(Bit 0:Success)} Note : This command is only available using an USB Plug & Scan Dongle (Baracoda’s product) Code ID 0xF4-0xF5 Description Set Timestamp Payload 6 bytes:...

  • Page 20: Barcode Decoder Commands

    RoadRunners – Communication Protocol Code ID 0xFA-0xFB Description Get and erase stored barcodes Payload None Response 1 byte: {(Bit 0:Success)} Code ID 0xFC-0xFD Description Erase stored barcodes Payload None Response 1 byte: {(Bit 0:Success)} Code ID 0xFE-0xFF Description Barcode decoder Commands Payload BRR-L : BRR-F :...

  • Page 21: Annexe 1 : Smartmodule Developer Implementation Guide

    RoadRunners – Communication Protocol ANNEXE 1 : SMARTMODULE DEVELOPER IMPLEMENTATION GUIDE The configuration frames are as follow: Header: 1 Byte Length: 2 Bytes (MSB, LSB) Set PinCode (0x01) (flash only) Command Header Length Set PinCode 0x01 00 00 Max Pin length=16 Get PinCode (0x07) Command...
  • Page 22 RoadRunners – Communication Protocol Get Mode (0x04) Command Header Length Get mode 0x04 00 00 Set Remote BDA (0x05) (Used by Master Mode of the SM) Command Header Length Set Remote BDA 0x05 00 06 If The SM is set to Master (using Set MODE command), the SM use this Address to connect to. Get Remote BDA (0x06) Command...
  • Page 23 RoadRunners – Communication Protocol When setting only MinSniff and MaxSniff values, the default value 0x08 will be used for Sniff attempts and Sniff timeout. Typically values: Full speed (full power) MinSniff = 0 MaxSniff = 0 Low Power: (sniff of 500ms Only) (low speed) MinSniff = 0x0320 MaxSniff = 0x0320 Low Power: (sniff between 250ms to 500ms are acepted) (low speed)
  • Page 24 RoadRunners – Communication Protocol mode Argument is : 0x01 to enable encryption, 0x00 to disable Get Encryption Mode (0x40) Command Header Length Encryption 0x40 00 00 mode Get Local Bluetooth Address (0x43) Command Header Get local BT address 0x43 Get Maximum transmit power (0x3a) Command Header Get Transmit power...

  • Page 25: Annexe 2 : Barcode Decoder 1D - Frame Configuration For Brr-L Decoder Setting Via Serial Connexion

    RoadRunners – Communication Protocol ANNEXE 2 : BARCODE DECODER 1D - FRAME CONFIGURATION FOR BRR-L DECODER SETTING VIA SERIAL CONNEXION 1/ frame format Header Type 1Byte 1Byte 2/ Header The Header field defines the type of symbology to select; it is 1 byte long (ACSII code): Header Note: The "A"...
  • Page 26 RoadRunners – Communication Protocol 3/ Type The Type field defines the type of command to be sent to the reader, it is 1 byte long. Type Get config: asks the reader to give the configuration options for the selected Set config : sets an options configuration for the selected symbology. (1) Set Default: sets the default options configuration for the selected (*): This Type of command is not available with "A"...
  • Page 27 RoadRunners – Communication Protocol 5/ Commands This field contains the commands, its length must be the one specified in the Size field. There are three types of commands: 5.1/ Set Config (Type "B") This command is made up of 1 or 2 bytes. The first one contains information for configuration of general options (common to all the symbologies).
  • Page 28 RoadRunners – Communication Protocol CODE 128 / EAN 128 (Header "C") TF - Protocol of communication January 2007 CODE 93 (Header "B") Option FREE FREE FREE FREE FREE FREE FREE FREE Option GS transmit (EAN128) AIM Symb ID transmit (EAN128) FREE FREE FREE...
  • Page 29 RoadRunners – Communication Protocol INTERLEAVED 2 OF 5 (Header "G") STANDARD 2 OF 5 (Header "H") TF - Protocol of communication January 2007 CODE 39 (Header "E") Option Enable/Disable start-stop transmission Enable/Disable Full ACSII Mode Enable/Disable "*" as start-stop character Enable/Disable "$"...
  • Page 30 RoadRunners – Communication Protocol TF - Protocol of communication January 2007 MATRIX 2 OF 5 (Header "I") Option FREE FREE FREE FREE FREE FREE FREE FREE CODE 11 (Header "J") Option FREE FREE FREE FREE FREE FREE FREE FREE MSI (Header "K") Option FREE FREE...
  • Page 31 RoadRunners – Communication Protocol TF - Protocol of communication January 2007 EAN 8 (Header "M") Option FREE EAN 8 transmitted as EAN 13 FREE FREE RSS 14 (Header "N") Option LINKAGE FLAG PRINT APPLICATION ID PRINT FREE FREE FREE FREE FREE FREE RSS Limited (Header "O")
  • Page 32 RoadRunners – Communication Protocol 5.2/ Usual Commands (Type "D") The method described above allows a fast and effective setting of a whole set of configurations for a given symbology. It exclusively allows a simultaneous configuration of all the options available for a given symbology. The usual commands are designed to palliate this effect.
  • Page 33 RoadRunners – Communication Protocol UPC-A/EAN 8 transmitted as EAN 13 UPC-A/EAN 8 transmitted as UPC-A/EAN 8 UPC-E transmitted as UPC-A UPC-E transmitted as UPC-E Disable Max. length Enable Max. length (3) Enable all EAN/UPC symbologies Disable all EAN/UPC symbologies Enable linkage flag transmission Dissable linkage flag transmission Enable application identifier transmission Dissable application identifier transmission...
  • Page 34 RoadRunners – Communication Protocol 5.3/ Special Commands (Type "E") Some commands require more than a Boolean digit and require one or more arguments. Special commands will be used in this case (defined code "E" in type field). It is made of one byte corresponding to the type of command.

  • Page 35: Annexe 3 : Barcode Decoder 2D - Frame Configuration For Brr-F Decoder Setting Via Serial Connexion

    RoadRunners – Communication Protocol 6/ Examples Here are some examples to illustrate each type of frame to be sent to the decoder and the possible answer from the decoder.. 6.1 Get Config Example 1.1 – Getting configuration of Code 39 symbology. Frame to be sent to the decoder: ‘E’...
  • Page 36 RoadRunners – Communication Protocol 6.2 Set Config Example 2.1 – Setting a configuration of Codabar symbology. Frame to be sent to the decoder: ‘F’ ‘B’ Header Type Reading this frame, the decoder understands: The user wants to set a configuration (Type "B") for Codabar (Header "F"). the configuration will contain general options and others specific to cadabar (Size = 2).
  • Page 37 RoadRunners – Communication Protocol Example 2.2 – Setting a configuration of all symbologies. Frame to be sent to the decoder: ‘A’ ‘B’ Header Type Reading this frame, the decoder understands: The user wants to set a configuration (Type "B") for all the symbologies (Header "A"). The configuration can only contain general options and the Size field must be equal to 1.
  • Page 38 RoadRunners – Communication Protocol 6.4 Special command Example 4.1 – Sending a special command to Code39 symbology. We now want set a larger frame of Min-Max length for Code39 symbology. Frame to be sent to the decoder: ‘E’ ‘E’ ‘C’ , 2 , 40 Header Type Size...
  • Page 39 RoadRunners – Communication Protocol ANNEXE 3 : BARCODE DECODER 2D - FRAME CONFIGURATION FOR BRR-F DECODER SETTING VIA SERIAL CONNEXION 1/ Command syntax SubTag {Data} [,SubTag {Data}] [option] : An optional part of a command. {Data} : Alternatives in a command. Tag : A 3 character case-insensitive field that identifies the desired menu command group.
  • Page 40 RoadRunners – Communication Protocol 2/ symbology configuration commands Here is the list of the configurations available for each symbology: Symbology SubTag Codabar Code39 Interleaved 2 of 5 Code 93 Code 2 of 5 IATA Code 2 of 5 TF - Protocol of communication January 2007 Setting (* indicates default)
  • Page 41 RoadRunners – Communication Protocol Matrix 2 of 5 Code 11 Code 128 Telepen UPC-A UPC-E TF - Protocol of communication January 2007 Default all Code11 settings *Off Min length (1-80) *4 Max length (1-80) *80 Default all Matrix 2 of 5 settings *Off 1 check digit *2 check digits...
  • Page 42 RoadRunners – Communication Protocol EAN 13 EAN 8 Plessey Code RSS 14 RSS Limited RSS Expanded PosiCode Codablock F TF - Protocol of communication January 2007 Default all EAN 13 settings EAN 13 check digit Off * EAN 13 check digit On *ISBN translate Off ISBN translate On * EAN 13 2 Digit Addenda Off...
  • Page 43 RoadRunners – Communication Protocol Code 16K Code 49 PDF 417 MicroPDF417 Postnet Planet Code British Post Canadian Post Kiw (Netherlands) Post Australian Post Japanese Post China Post Korea Post QR Code Data Matrix MaxiCode Aztec Code TF - Protocol of communication January 2007 Default all 16K settings *Off...
  • Page 44 RoadRunners – Communication Protocol 3/ other configuration commands TAG SubTag Setting AIM Symbology Identifier transmit (all symbologies) AIM Symbology Identifier transmit (EAN128) Do not transmit AIM ID 4/ query commands A special character can be used to query the device about its settings : ‘?’...
  • Page 45 RoadRunners – Communication Protocol The BRR-F replies : field Code ID length ASCII 00 3F This means : Code39 is enabled (ENA1), - Start/stop characters are not transmitted () - Full ASCII mode is disabled () - Code39 append is off - Checksum is not calculated - Code32 is off - Code page is ISO2022...
  • Page 46 RoadRunners – Communication Protocol TF - Protocol of communication 46/46 January 2007...

Table of Contents