Français dropdown-ico

Baracoda RoadRunners Laser manuel d'utilisation

1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46

Aller à la page of

Les manuels d’utilisation similaires

Un bon manuel d’utilisation

Les règles imposent au revendeur l'obligation de fournir à l'acheteur, avec des marchandises, le manuel d’utilisation Baracoda RoadRunners Laser. Le manque du manuel d’utilisation ou les informations incorrectes fournies au consommateur sont à la base d'une plainte pour non-conformité du dispositif avec le contrat. Conformément à la loi, l’inclusion du manuel d’utilisation sous une forme autre que le papier est autorisée, ce qui est souvent utilisé récemment, en incluant la forme graphique ou électronique du manuel Baracoda RoadRunners Laser ou les vidéos d'instruction pour les utilisateurs. La condition est son caractère lisible et compréhensible.

Qu'est ce que le manuel d’utilisation?

Le mot vient du latin "Instructio", à savoir organiser. Ainsi, le manuel d’utilisation Baracoda RoadRunners Laser décrit les étapes de la procédure. Le but du manuel d’utilisation est d’instruire, de faciliter le démarrage, l'utilisation de l'équipement ou l'exécution des actions spécifiques. Le manuel d’utilisation est une collection d'informations sur l'objet/service, une indice.

Malheureusement, peu d'utilisateurs prennent le temps de lire le manuel d’utilisation, et un bon manuel permet non seulement d’apprendre à connaître un certain nombre de fonctionnalités supplémentaires du dispositif acheté, mais aussi éviter la majorité des défaillances.

Donc, ce qui devrait contenir le manuel parfait?

Tout d'abord, le manuel d’utilisation Baracoda RoadRunners Laser devrait contenir:
- informations sur les caractéristiques techniques du dispositif Baracoda RoadRunners Laser
- nom du fabricant et année de fabrication Baracoda RoadRunners Laser
- instructions d'utilisation, de réglage et d’entretien de l'équipement Baracoda RoadRunners Laser
- signes de sécurité et attestations confirmant la conformité avec les normes pertinentes

Pourquoi nous ne lisons pas les manuels d’utilisation?

Habituellement, cela est dû au manque de temps et de certitude quant à la fonctionnalité spécifique de l'équipement acheté. Malheureusement, la connexion et le démarrage Baracoda RoadRunners Laser ne suffisent pas. Le manuel d’utilisation contient un certain nombre de lignes directrices concernant les fonctionnalités spécifiques, la sécurité, les méthodes d'entretien (même les moyens qui doivent être utilisés), les défauts possibles Baracoda RoadRunners Laser et les moyens de résoudre des problèmes communs lors de l'utilisation. Enfin, le manuel contient les coordonnées du service Baracoda en l'absence de l'efficacité des solutions proposées. Actuellement, les manuels d’utilisation sous la forme d'animations intéressantes et de vidéos pédagogiques qui sont meilleurs que la brochure, sont très populaires. Ce type de manuel permet à l'utilisateur de voir toute la vidéo d'instruction sans sauter les spécifications et les descriptions techniques compliquées Baracoda RoadRunners Laser, comme c’est le cas pour la version papier.

Pourquoi lire le manuel d’utilisation?

Tout d'abord, il contient la réponse sur la structure, les possibilités du dispositif Baracoda RoadRunners Laser, l'utilisation de divers accessoires et une gamme d'informations pour profiter pleinement de toutes les fonctionnalités et commodités.

Après un achat réussi de l’équipement/dispositif, prenez un moment pour vous familiariser avec toutes les parties du manuel d'utilisation Baracoda RoadRunners Laser. À l'heure actuelle, ils sont soigneusement préparés et traduits pour qu'ils soient non seulement compréhensibles pour les utilisateurs, mais pour qu’ils remplissent leur fonction de base de l'information et d’aide.

Table des matières du manuel d’utilisation

  • Page 1

    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. 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 B[...]

  • Page 2

    RoadRunners – Communication Protocol TF - Summary 2 January 20 07 SUMMAR Y SUMMARY ............................................................................................................... ................ 2 INTRODUCTION .................................................................................................... ................. 3 [...]

  • Page 3

    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 . - 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 [...]

  • Page 4

    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. That is available for communication from the scanner to the host and from the h ost to the sca[...]

  • Page 5

    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. Acknowledgment packets These messages acknowledge the reception of a valid message with the expect[...]

  • Page 6

    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 string[...]

  • Page 7

    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.1.1. Generic Code IDs Code ID 0x40-0x41 Description Get Commu nication D escriptor Payload None Response 2 bytes: {Wir e less link : (Bit 0: CSR B C02)} {Wired link: (Bit 0: Serial [...]

  • Page 8

    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 Version string} xBytes {CPU Version} 2Byt es {S ize of BT V ersion } xBytes {BT Ve rsion} 6Bytes {BDAdress} 1Byte {BT Secure Mode} 1Byte {Scanner Ope[...]

  • Page 9

    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 Payload {Code ID} “Parameters” Response If the device responds: {Code ID} “Response” Else: {0} Code ID 0x5E-0x 5F Description Bluetooth Commands Pa[...]

  • Page 10

    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 Response 1 byte : {Bit 0 = 1:real time, Bit 0 = 1: batch} {(Bit 7: li mit ed – ie : no data loss mo de)} Code ID 0x64-0x65 Description Set Operating M[...]

  • Page 11

    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 0: Success} Code ID 0x6E-0 x6F Description Get Sending delay ( delay between beam ON and decoding process - only available for BRR-L product) Payload [...]

  • Page 12

    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.c Response n. c[...]

  • Page 13

    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 None Response 2 byte s : {(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 – right one) (B[...]

  • Page 14

    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, 0 - 4} For each ste p: {(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 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) (Bit 1: Read beep) (Bit 2 : ACK bee p)} Code ID 0x94-0x95 Description Set Beeps mode Payload 1 byte: {(Bit 0: Be ep lev el; 0= low, 1= hig h) (Bit 1: Rea[...]

  • Page 16

    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.c Payload n.c Response n. c Code ID 0xC2-0x C3 Description Get / Set PostPrefix Payload Get : None Set : 1-33 bytes {PostPrefix length} “PostPref ix string” Response Get : 1-33[...]

  • Page 17

    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 length} Response Get : 2 bytes {au thorized barcode length} Set : 1 byte {(Bit 0:Success)} Code ID 0xCA-0 xCB Description Get & erase stored barco[...]

  • Page 18

    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 Version String” or {0} if not applicable Code ID 0xE2-0 xE3 Description Get Mode Payload None Response 1 byte : {0 = trigger, 1 = autoscan, 2 = disab[...]

  • Page 19

    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 byte : {(Bit 0:Success)} Code ID 0xEE-0x EF Description Get Suffix Payload None Response 1-33 bytes: {Suffix length} “Suffix String” Code ID 0xF0- [...]

  • Page 20

    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)} Code ID 0xFC-0 xFD Description Erase stored barcodes Payload None Response 1 byte: {(Bit 0:Success)} Code ID 0xFE-0xFF Description Barcod e decod er Co[...]

  • Page 21

    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. Set PinCode (0x01) (flash only) Command Head er Length Payl oad Answ er Set PinCode 0x01[...]

  • Page 22

    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 itch role (1byte)} 0 x01 if MA STER, 0 x0 0 if S LAV E 0x01 if want automatic switch role, 0x00 otherwise Set Remote BDA (0x05) (Used by Master Mode of [...]

  • Page 23

    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. Typically va lues: Full speed (full power) MinS ni f f = 0 MaxSniff = 0 Low P o wer: (snif f of 50 0ms O nly) (l ow spe ed) MinS ni f f = [...]

  • Page 24

    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 Mode (0x40) Command Header Length Payload Answer Get Encryption mode 0x40 00 00 - 0x40 00 01 [encryption] Get Local Bluetooth Address (0x43) Command Hea[...]

  • Page 25

    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 format Header Type Size (Bytes) Command 1B yte 1B yte 1B yte 2/ Header The Header field defines the type of sy mbology to select; it is 1 byte long (ACS[...]

  • Page 26

    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. (1) (*) B Set config : sets an optio ns configurati[...]

  • Page 27

    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. The first one contains information for con[...]

  • Page 28

    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 CODE 128 / EAN 128 (Header "C") Bit Op tion LSB 0 GS transmit (EAN128) 1 AIM Symb ID transmit (EAN128) 2 FREE 3 FREE 4 FREE 5 FREE 6 FREE MSB 7[...]

  • Page 29

    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 ACSII Mode 2 Enable/Dis able "*" as start-stop char acter 3 Enable/Dis able "$" as start-stop char acter 4 FREE 5 FREE 6 FREE MSB [...]

  • Page 30

    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 FREE CODE 11 (Header "J") Bit Op tion LSB 0 FREE 1 FREE 2 FREE 3 FREE 4 FREE 5 FREE 6 FREE MSB 7 FREE MSI (Head er "K ") Bit Op tio[...]

  • Page 31

    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 FREE RSS 14 (Header "N") Bit Op tion LSB 0 LINKAGE FLAG PRINT 1 APPLICATION ID PRINT 2 FREE 3 FREE 4 FREE 5 FREE 6 FREE MSB 7 FREE RS S Lim[...]

  • Page 32

    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. It excl usively allows a simultaneous configuration of all the options available for a given sy mbo[...]

  • Page 33

    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. length A, B, C, E, F, G, H, J, K e Enable Max. length (3) A, B, C, E, F, G, H, J, K f E[...]

  • Page 34

    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). It is ma de of one byte corresponding to th e [...]

  • Page 35

    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.1 – Getting configuration of Code 39 symbology. Frame to be sent to th e decoder: ‘E’ ‘[...]

  • Page 36

    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. Frame to be sent to th e decoder: ‘F’ ‘B’ 2 $03 , $01 Head er Typ e Siz e Co mman d Readin g this fram e, the dec ode r understa nds: The user wants to set a configuration (T[...]

  • Page 37

    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’ 1 $13 Head er Typ e Siz e Co mman d Readin g this fram e, the dec ode r understa nds: The user wants to set a configuration (Type "B ") for [...]

  • Page 38

    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. We now want set a larger frame of Min-Max length for Code39 symbology. Frame to be sent to th e decoder: ‘E’ ‘E’ 3 ‘C’ , 2 , 40 Head er Typ e Siz e Co mman d Readin [...]

  • Page 39

    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. {Data} : Alternat ives in a c[...]

  • Page 40

    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. Off CBRE NA0. ENA *O[...]

  • Page 41

    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##. DFT Default all Matrix 2 of 5 settings C11DFT. *Off C11ENA0. ENA O n C11ENA1. 1 check digit C11CK2[...]

  • Page 42

    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. ISB I SBN trans late On E13NSX1 . * EAN 13 2 Digit Addenda Off E13AD20. AD2 EAN 13 2 Dig[...]

  • Page 43

    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. Off C49ENA0. ENA *On C49ENA1. MIN Min length (1-81) *1 C49MIN##[...]

  • Page 44

    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. PRE CA2 Do not tra nsm it AIM ID PREC[...]

  • Page 45

    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] . [ACK] is the ACK ascii character (0x06) Hex FE 00 3F 43 33 39 44 46 54[...]

  • Page 46

    RoadRunners – Communication Protocol TF - Protocol of communication 46/46 January 20 07[...]