Instruction/ maintenance manual of the product RoadRunners Laser Baracoda
Go to page of 46
Data Capture for W orkforce in Motion The bluetooth name and Bluetooth registered trademarks are owned by Bluetooth SIG, Inc., and are used by Baracoda under license.
RoadRunners – Communication Protocol TF - Summary 2 January 20 07 SUMMAR Y SUMMARY ............................................................................................................... ................ 2 INTRODUCTION ......................
RoadRunners – Communication Protocol TF - Protocol of communication 3 January 20 07 Introduction INTRODUC TION RoadRunners is a w i reles s dat a capt ure pr oduc t .
RoadRunners – Communication Protocol TF - Protocol of communication 4 January 20 07 Protocol of communication 1. Bidirectionnal packets 1.1. Gene ric packet All frames that are described in the foll owing have to follow the follow ing format of packe t.
RoadRunners – Communication Protocol TF - Protocol of communication 5 January 20 07 1.2. Con tro l messag es 1.2.1. Specifics packets These 2 sequences w ill be recognized and pu rged for backward compatibility with other Baracod a produ cts. 1.2.2.
RoadRunners – Communication Protocol TF - Protocol of communication 6/46 January 20 07 2. Between the SCANNER and the REMOTE APPLICATION Code ID Description Payload 0x32–0x33 Barcode data Barcode .
RoadRunners – Communication Protocol TF - Protocol of communication 7/46 January 20 07 3. Between the REMOTE AP LICATION and the SCANNER 3.1. Communication messages 3.
RoadRunners – Communication Protocol TF - Protocol of communication 8/46 January 20 07 Code ID 0x4A-0x4B Description Get Supp ort Da ta Payload Response 1Byte {Battery level (%)} 2Bytes {Size of CPU.
RoadRunners – Communication Protocol TF - Protocol of communication 9/46 January 20 07 Code ID 0x56-0x57 Description n.c Paylo ad n.c Response n.c Code ID 0x5C-0x 5D Description Dock Comm ands Paylo.
RoadRunners – Communication Protocol TF - Protocol of communication 10/46 January 20 07 3.2. Scanner messages 3.2.1. Generic Code IDs Code ID 0x62-0x63 Description Get Operating Mode Payload None Re.
RoadRunners – Communication Protocol TF - Protocol of communication 11/46 January 20 07 Code ID 0x6C-0x 6D Description Set RTC Time Payload 6 bytes : {YY}{MM}{DD}{HH}{MM}{SS} Response 1 byte : {Bit .
RoadRunners – Communication Protocol TF - Protocol of communication 12/46 January 20 07 Code ID 0x7A-0 x7B Description n.c Payload n.c Response n. c Code ID 0x7C-0x 7D Description n.c Payload n.c Response n. c Code ID 0x7E-0 x7F Description n.c Payload n.
RoadRunners – Communication Protocol TF - Protocol of communication 13/46 January 20 07 3.3. User Interface messages Code ID 0x80-0x81 Description Get MMI De s cript or (Use r Interf a ce) Payload N.
RoadRunners – Communication Protocol TF - Protocol of communication 14/46 January 20 07 Code ID 0x88-0x89 Description Set MMI S ignal Payload (2 + 3n) bytes {Signal number, 0 - 3} {Number of steps, .
RoadRunners – Communication Protocol TF - Protocol of communication 15/46 January 20 07 Code ID 0x92-0x93 Description Get Beeps mode Payload Response 1 byte : {(Bit 0: Beep level 0=low , 1=high) (Bi.
RoadRunners – Communication Protocol TF - Protocol of communication 16/46 January 20 07 3.4. Miscellaneous messages (host to sc anner) Code ID 0xC0-0x C1 Description n.
RoadRunners – Communication Protocol TF - Protocol of communication 17/46 January 20 07 Code ID 0xC8-0x C9 Description Get / Set Ba rcode length Payload Get : None Set : 2 bytes {authorized barcode .
RoadRunners – Communication Protocol TF - Protocol of communication 18/46 January 20 07 3.5. Barcode messages Code ID 0xE0-0 xE1 Description Get B arcod e Vers ion Payload None Response “Barcode V.
RoadRunners – Communication Protocol TF - Protocol of communication 19/46 January 20 07 Code ID 0xEC-0 xED Description Set Prefix Payload 1-33 bytes: {Prefix length} “Prefix String” Response 1 b.
RoadRunners – Communication Protocol TF - Protocol of communication 20/46 January 20 07 Code ID 0xFA-0x FB Description Get and erase stored barcodes Payload None Response 1 byte: {(Bit 0:Success)} C.
RoadRunners – Communication Protocol TF - Protocol of communication 21/46 January 20 07 ANNEXE 1 : SMARTMODULE DEVELOPER IMPLEMENTATION GUIDE The configuration frames are as follow: Header : 1 By te Lengt h: 2 B y tes (MSB, LSB) Pa yload: 0 to 655 3 5 Byte s.
RoadRunners – Communication Protocol TF - Protocol of communication 22/46 January 20 07 Get Mode (0x04) Command He ader Le ngth Payl oad Answer Get mode 0x04 00 00 - 0x04 00 02 {Mode (1byte) | Sw it.
RoadRunners – Communication Protocol TF - Protocol of communication 23/46 January 20 07 When setting only MinSniff and MaxSniff values, the default value 0x08 will be used for Sniff attempts and Sniff timeout.
RoadRunners – Communication Protocol TF - Protocol of communication 24/46 January 20 07 mode (1 byte)] 0x41 00 01 00 if not Argument is : 0x01 to enable encryption, 0x00 to disable Get Encryption Mo.
RoadRunners – Communication Protocol TF - Protocol of communication 25/46 January 20 07 ANNEXE 2 : BARCODE DECODER 1D - FRAME CONFIGURATION FOR BRR-L DECODER SETTING VIA SERIAL CONNEXION 1/ frame fo.
RoadRunners – Communication Protocol TF - Protocol of communication 26/46 January 20 07 3/ Type The Type field defines the ty pe of command to be sent to the reader, it is 1 by te long. Type Des cription A Get config : asks the reader to give the configuration options for the selected symbology.
RoadRunners – Communication Protocol TF - Protocol of communication 27/46 January 20 07 5/ Commands This field contains the commands, its leng th must be the one specified in the Size field. There are three types of comma nds : 5.1/ Set Config (Type "B") This command is made up of 1 or 2 bytes.
RoadRunners – Communication Protocol TF - Protocol of communication 28/46 January 20 07 CODE 93 (Header "B") Bit Op tion LSB 0 FREE 1 FREE 2 FREE 3 FREE 4 FREE 5 FREE 6 FREE MSB 7 FREE COD.
RoadRunners – Communication Protocol TF - Protocol of communication 29/46 January 20 07 CODE 39 (Header "E") Bit Op tion LSB 0 Enable/Disable start-stop transmission 1 Enable/Disable Full .
RoadRunners – Communication Protocol TF - Protocol of communication 30/46 January 20 07 MATRIX 2 OF 5 (Head er "I") Bit Op tion LSB 0 FREE 1 FREE 2 FREE 3 FREE 4 FREE 5 FREE 6 FREE MSB 7 F.
RoadRunners – Communication Protocol TF - Protocol of communication 31/46 January 20 07 EAN 8 (Header "M") Bit Op tion LSB 0 FREE 1 - 2 - 3 - 4 EAN 8 transmitted as EAN 13 5 FREE 6 - MSB 7.
RoadRunners – Communication Protocol TF - Protocol of communication 32/46 January 20 07 5.2/ Usual Commands (Type "D") The method described above allows a fast a nd effective setting of a whole set of configurations for a given symbology.
RoadRunners – Communication Protocol TF - Protocol of communication 33/46 January 20 07 X UPC-A/EAN 8 transmitted as EAN 13 D, M Y UPC-A/EAN 8 transmitted as UPC-A/EAN 8 D, M Z UPC-E transmitted as UPC-A L a UPC-E transmitted as UPC -E L b - c - d Disable Max.
RoadRunners – Communication Protocol TF - Protocol of communication 34/46 January 20 07 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 th is case (defined code "E" in type field).
RoadRunners – Communication Protocol TF - Protocol of communication 35/46 January 20 07 6/ Examples Here are some examples to i llustrate each type of frame to be sent to the d ecoder and the possible answer from the decoder.. 6.1 Ge t Config Example 1.
RoadRunners – Communication Protocol TF - Protocol of communication 36/46 January 20 07 6.2 Set Config Example 2.1 – Setting a configur ation of Codabar symbology.
RoadRunners – Communication Protocol TF - Protocol of communication 37/46 January 20 07 Example 2.2 – Setting a configuration of all symbologies. Frame to be sent to th e decoder: ‘A’ ‘B’ .
RoadRunners – Communication Protocol TF - Protocol of communication 38/46 January 20 07 6.4 Special command Example 4.1 – Sending a special command to Code39 symbology.
RoadRunners – Communication Protocol TF - Protocol of communication 39/46 January 20 07 ANNEXE 3 : BARCODE DECODER 2D - FRAME CONFIGURATION FOR BRR-F DECODER SETTING VIA SERIAL CONNEXION 1/ Command syntax Tag SubTag {Da ta} [,SubTag {Data}] [;Tag SubTag {Data}] […] Storage [option] : An optional part of a co mmand.
RoadRunners – Communication Protocol TF - Protocol of communication 40/46 January 20 07 2/ symbology configuration commands Here is the list of th e configurations av ailable for each sy mbology: TA G Symbology SubTag Setting (* indicates default) Command (# indicates a numeric entry) DFT Default all C odabar settings CBRDFT.
RoadRunners – Communication Protocol TF - Protocol of communication 41/46 January 20 07 DFT Default all C ode11 set tings X25DFT. *Off X25ENA0. ENA O n X25ENA1. MIN Min length (1-80) *4 X25MIN##. X25 Matrix 2 of 5 MAX Max length (1-80) *80 X25MAX##.
RoadRunners – Communication Protocol TF - Protocol of communication 42/46 January 20 07 DFT Def ault all EAN 13 setting s E13DFT. Off E1 3ENA0. ENA *On E13ENA1. EAN 13 check digit Off E13CKX0. CKX * EAN 13 chec k digit On E13CKX1. *ISBN translate Off E13NSX0.
RoadRunners – Communication Protocol TF - Protocol of communication 43/46 January 20 07 DFT Default all 16K settings 16KDFT. *Off 16KENA0. ENA On 16KENA1. MIN Min length (0-160) *1 16KM IN##. 16K Code 16K MAX Max length (0-160) *160 16KMAX##. DFT Default all C ode49 set tings C49DFT.
RoadRunners – Communication Protocol TF - Protocol of communication 44/46 January 20 07 3/ other config uration commands TAG Su bTag Setting Command Off ALLENA0. ALL ENA On ALLENA1. AIM Symbology Identifie r transmit (all symbologies) PREBK2995C81. BK2 AIM Symbology Identifie r transmit (EAN128) PREBK2495C81.
RoadRunners – Communication Protocol TF - Protocol of communication 45/46 January 20 07 The BRR-F replies : field Code ID length Payload ASCII - - - C39DFT [ACK] ,ENA1 [ACK] ,SSX0 [ACK] ,A SC0 [ACK] ,APP0 [AC K] ,CK20 [ACK] ,B32 0 [ACK] ,MIN0 [ACK] ,MAX48 [ACK] ,DC P2 [A CK] .
RoadRunners – Communication Protocol TF - Protocol of communication 46/46 January 20 07.
An important point after buying a device Baracoda RoadRunners Laser (or even before the purchase) is to read its user manual. We should do this for several simple reasons:
If you have not bought Baracoda RoadRunners Laser yet, this is a good time to familiarize yourself with the basic data on the product. First of all view first pages of the manual, you can find above. You should find there the most important technical data Baracoda RoadRunners Laser - thus you can check whether the hardware meets your expectations. When delving into next pages of the user manual, Baracoda RoadRunners Laser you will learn all the available features of the product, as well as information on its operation. The information that you get Baracoda RoadRunners Laser will certainly help you make a decision on the purchase.
If you already are a holder of Baracoda RoadRunners Laser, but have not read the manual yet, you should do it for the reasons described above. You will learn then if you properly used the available features, and whether you have not made any mistakes, which can shorten the lifetime Baracoda RoadRunners Laser.
However, one of the most important roles played by the user manual is to help in solving problems with Baracoda RoadRunners Laser. Almost always you will find there Troubleshooting, which are the most frequently occurring failures and malfunctions of the device Baracoda RoadRunners Laser along with tips on how to solve them. Even if you fail to solve the problem, the manual will show you a further procedure – contact to the customer service center or the nearest service center
