English dropdown-ico

Baracoda L manual

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
47
48

Go to page of

Similar user manuals

A good user manual

The rules should oblige the seller to give the purchaser an operating instrucion of Baracoda L, along with an item. The lack of an instruction or false information given to customer shall constitute grounds to apply for a complaint because of nonconformity of goods with the contract. In accordance with the law, a customer can receive an instruction in non-paper form; lately graphic and electronic forms of the manuals, as well as instructional videos have been majorly used. A necessary precondition for this is the unmistakable, legible character of an instruction.

What is an instruction?

The term originates from the Latin word „instructio”, which means organizing. Therefore, in an instruction of Baracoda L one could find a process description. An instruction's purpose is to teach, to ease the start-up and an item's use or performance of certain activities. An instruction is a compilation of information about an item/a service, it is a clue.

Unfortunately, only a few customers devote their time to read an instruction of Baracoda L. A good user manual introduces us to a number of additional functionalities of the purchased item, and also helps us to avoid the formation of most of the defects.

What should a perfect user manual contain?

First and foremost, an user manual of Baracoda L should contain:
- informations concerning technical data of Baracoda L
- name of the manufacturer and a year of construction of the Baracoda L item
- rules of operation, control and maintenance of the Baracoda L item
- safety signs and mark certificates which confirm compatibility with appropriate standards

Why don't we read the manuals?

Usually it results from the lack of time and certainty about functionalities of purchased items. Unfortunately, networking and start-up of Baracoda L alone are not enough. An instruction contains a number of clues concerning respective functionalities, safety rules, maintenance methods (what means should be used), eventual defects of Baracoda L, and methods of problem resolution. Eventually, when one still can't find the answer to his problems, he will be directed to the Baracoda service. Lately animated manuals and instructional videos are quite popular among customers. These kinds of user manuals are effective; they assure that a customer will familiarize himself with the whole material, and won't skip complicated, technical information of Baracoda L.

Why one should read the manuals?

It is mostly in the manuals where we will find the details concerning construction and possibility of the Baracoda L item, and its use of respective accessory, as well as information concerning all the functions and facilities.

After a successful purchase of an item one should find a moment and get to know with every part of an instruction. Currently the manuals are carefully prearranged and translated, so they could be fully understood by its users. The manuals will serve as an informational aid.

Table of contents for the manual

  • Page 1

    RoadRunne rs Evolutio n Programmin g Guide © Baracoda TM – July 2009 RoadRunne rs Evolutio n –L (1D) & - LA (La ser) Programmin g Guide Data Capture for W ork force in Motion LA (La ser)[...]

  • Page 2

    RoadRunners Evoluti on –L (1D) & -LA (Laser) – Programming Guide v1.3 - 2 - Data Capture for W ork force in Motion SUMMARY SUMMARY ................................................................... 2 REVISION HISTORY .......................................................... 4 INTRODUCTION ..................................................[...]

  • Page 3

    RoadRunners Evoluti on –L (1D) & -LA (Laser) – Programming Guide v1.3 - 3 - Data Capture for W ork force in Motion 2.8.6. S ET LENGTHS FOR C ODE 39 ....................................................... 30 2.8.7. I TALIAN P HARMA C ODE SETTINGS .................................................... 31 2.9. C ODE 93 S ETTINGS ................[...]

  • Page 4

    RoadRunners Evoluti on –L (1D) & -LA (Laser) – Programming Guide v1.3 - 4 - Data Capture for W ork force in Motion Revision History Changes to the original manual are listed below. Document Date Description 1.0 11 July 08 Initial release 1.1 26 Au g. 08 Update “Batch” section & add “ The different connection method” section 1.2 [...]

  • Page 5

    RoadRunners Evoluti on –L (1D) & -LA (Laser) – Programming Guide v1.3 - 5 - Data Capture for W ork force in Motion Introduction The RoadRunn ers Evolution sca nner can be progra mmed by scanning b arcode labels whic h contain command s for the decoder. Programming la bels must be Code128, with specific sta rting and endin g characters. Thes[...]

  • Page 6

    RoadRunners Evoluti on –L (1D) & -LA (Laser) – Programming Guide v1.3 - 6 - Data Capture for W ork force in Motion 1. General Configuration 1.1. General d efault settings The reading of the "Reset to factor y settings” label turns all the parameters o f the scanner back to default settings and switches it off Reset to factory setting[...]

  • Page 7

    RoadRunners Evoluti on –L (1D) & -LA (Laser) – Programming Guide v1.3 - 7 - Data Capture for W ork force in Motion 1.2. Baracoda advanced features 1.2.1. Switch on delay In order to switch on the scann er in its standard mo de, you should just press the trigger. You can set up t he scanner to be s witched on only after keeping the trigger p[...]

  • Page 8

    RoadRunners Evoluti on –L (1D) & -LA (Laser) – Programming Guide v1.3 - 8 - Data Capture for W ork force in Motion 1.2.4. No data loss mode and Baracoda Header Baracod a header: It is a propr ietary data encap sulation. It is necessary to activate it to use the Baracoda keyb oard emulation (Kemul) and Ter minal. The Baracoda head er is enab[...]

  • Page 9

    RoadRunners Evoluti on –L (1D) & -LA (Laser) – Programming Guide v1.3 - 9 - Data Capture for W ork force in Motion In Autoscan mode , the scan beam i s continuously on. This mode enabl es to scan contin uously. Autoscan In Smart Autoscan m ode , for a ba ttery power co nsumption o ptimisation issu e, the scann er will be continuou sly flash[...]

  • Page 10

    RoadRunners Evoluti on –L (1D) & -LA (Laser) – Programming Guide v1.3 - 10 - Data Capture for W ork force in Motion 1.4. Operating Mode Real Time mode In real time mode, the bar code is decoded and trans mitted t o the remote host with out an y delay. If th e scanner is not con nected, the d ata is lost. Real Time mode with No Data Loss opt[...]

  • Page 11

    RoadRunners Evoluti on –L (1D) & -LA (Laser) – Programming Guide v1.3 - 11 - Data Capture for W ork force in Motion 1.4.1. Real Time mode Erases all cap tured data s tored in memory a nd force s t he scann er in Real ti me mode. No other s etting is changed. Importa nt r eminder : if an ACK beep o r buffer is need ed, the scanner must b e s[...]

  • Page 12

    RoadRunners Evoluti on –L (1D) & -LA (Laser) – Programming Guide v1.3 - 12 - Data Capture for W ork force in Motion 1.4.5. Batch mode BATCH MODE Forces the Road Runners Evo lution in Batch mode. Erases all codes in memor y When in bat ch mode, the scann er will wait for the app ropriate com mand in order to start uploading the barcodes: thi[...]

  • Page 13

    RoadRunners Evoluti on –L (1D) & -LA (Laser) – Programming Guide v1.3 - 13 - Data Capture for W ork force in Motion 1.5. The diffe rent connection m ethods There are two (2 ) different way to create a connection from a Host and a scanner: - Slave mode (b y default) The Host (PC, Bar acodaManager, …) i s creating the conne ction ont o the [...]

  • Page 14

    RoadRunners Evoluti on –L (1D) & -LA (Laser) – Programming Guide v1.3 - 14 - Data Capture for W ork force in Motion 1.6. Buzzer an d Led Settings You can use thes e options to enable o r disable the buz zer and / o r the Led. LED ON (*) LED OFF Good read beep on (*) Good read beep off ACK beep on (*) ACK beep off Beep level volume = H IGH ([...]

  • Page 15

    RoadRunners Evoluti on –L (1D) & -LA (Laser) – Programming Guide v1.3 - 15 - Data Capture for W ork force in Motion 1.7. Bluetooth settings 1.7.1. Bluetooth name You can chan ge the scanner Bluetoo th name; name that you see during a sear ch of Bluetooth peripheral. Programming proced ure for “Set Bluetoo th Name” Set BT Name End of con[...]

  • Page 16

    RoadRunners Evoluti on –L (1D) & -LA (Laser) – Programming Guide v1.3 - 16 - Data Capture for W ork force in Motion 1.7.2. Sniff period settings Change the Snif f period. If the h igher is the latency an d the smaller is the po wer consump tion. Default value is 1 50ms. Sniff period = 150ms ( *) Sniff period = 100ms Sniff period = 200ms Sni[...]

  • Page 17

    RoadRunners Evoluti on –L (1D) & -LA (Laser) – Programming Guide v1.3 - 17 - Data Capture for W ork force in Motion 1.7.3. Security (code PIN) settings Some Bluetooth device will not a ccept connections with d evices that do not have a security code. Disable BT security code Enable BT security code (*) 1.7.4. RF Power emission settings For [...]

  • Page 18

    RoadRunners Evoluti on –L (1D) & -LA (Laser) – Programming Guide v1.3 - 18 - Data Capture for W ork force in Motion 1.8. Data form at The barcode string can be added a timestamp, prefix es and/or suffixes. The symbology p refix/suffix can b e added by BaracodaManager only. These can come a s described below: Timestamp Data prefix Data (whic[...]

  • Page 19

    RoadRunners Evoluti on –L (1D) & -LA (Laser) – Programming Guide v1.3 - 19 - Data Capture for W ork force in Motion Set Timestamp END of configuration Noted tha t the timestamp must fit th e specific followin g format: {YY} {MM} {DD} {HH} {MM} {SS} The setting is made by scanning the 0-9 labels (App endix 1) as on a calculat or; following t[...]

  • Page 20

    RoadRunners Evoluti on –L (1D) & -LA (Laser) – Programming Guide v1.3 - 20 - Data Capture for W ork force in Motion 1.8.2. Data Prefix/Suffix You can add a data prefix a nd/or suffix (strings of mor e than 32 characters will not be accepted) to every barcode sent to the host device. There is no data prefi x or suffix in default settings. En[...]

  • Page 21

    RoadRunners Evoluti on –L (1D) & -LA (Laser) – Programming Guide v1.3 - 21 - Data Capture for W ork force in Motion Set Data prefix Set Data suffix End of configuration 1.8.3. Barcode Prefix/Suffix You can add a barcod e prefix and/or suffix (strings of mor e than 32 characters will not be a ccepted) to e very barcode sent to the host devic[...]

  • Page 22

    RoadRunners Evoluti on –L (1D) & -LA (Laser) – Programming Guide v1.3 - 22 - Data Capture for W ork force in Motion 1.8.4. AIM Symbology Identifier AIM Identifier will b e transmitted at the beginning of the barcode. More in formation abo ut the AIM Ident ifier is available in App endix2. AIM Symbology ident ifier - not transmitted (* ) AIM[...]

  • Page 23

    RoadRunners Evoluti on –L (1D) & -LA (Laser) – Programming Guide v1.3 - 23 - Data Capture for W ork force in Motion 2. Decoder Parameters 2.1. Decoder defau lt settings Sets the defaults d ecoder settings for all t he symbologie s Set Decoder Default Sett ings 2.2. Enable/Di sable All Symbolo gies Even if all symbo logies are disa bled, the[...]

  • Page 24

    RoadRunners Evoluti on –L (1D) & -LA (Laser) – Programming Guide v1.3 - 24 - Data Capture for W ork force in Motion Set barcode length END of config 2.4. Voting Standard voting set is two (2). This m eans that a ba rcode is considered r ead by the d ecoder if the same data is decoded twice. Ch anging this p arameter will enable a stronger s[...]

  • Page 25

    RoadRunners Evoluti on –L (1D) & -LA (Laser) – Programming Guide v1.3 - 25 - Data Capture for W ork force in Motion 2.5. Min/Max l ength per symbolo gy The following i s a procedure t o follow for every b arcode symbology . The decoder offers t he possibility to limit the reading of a barcode to a minimu m and a maximu m length, if it is fo[...]

  • Page 26

    RoadRunners Evoluti on –L (1D) & -LA (Laser) – Programming Guide v1.3 - 26 - Data Capture for W ork force in Motion 2.5.1. Symbology table Header Selected Symbology SELECT ALL Code 93 Code 128 / EAN 128 Code 39 Codabar Interleaved 2 of 5 Standard 2 of 5 (industrial 2 of 5) Code 11 MSI  Only the variable length s ymbologies appear. 2.6. C[...]

  • Page 27

    RoadRunners Evoluti on –L (1D) & -LA (Laser) – Programming Guide v1.3 - 27 - Data Capture for W ork force in Motion 2.6.2. Codabar Start/Stop characters Not transmitted (*) Transmitted 2.6.3. Codabar Check Digit Verification (AIM recommendation) Not used (*) Checked and transmitted Checked but not transmi tted 2.6.4. Set Lengths for Codabar[...]

  • Page 28

    RoadRunners Evoluti on –L (1D) & -LA (Laser) – Programming Guide v1.3 - 28 - Data Capture for W ork force in Motion 2.7. Code 11 S ettings 2.7.1. Enable/Disable Code 11 To enable or disable Code 11, scan the appropriat e barcode below. Code 11 - not active (*) Code 11 - active 2.7.2. Code 11 check digit(s) verification 1 digit (*) 2 digits [...]

  • Page 29

    RoadRunners Evoluti on –L (1D) & -LA (Laser) – Programming Guide v1.3 - 29 - Data Capture for W ork force in Motion 2.8. Code 39 s ettings 2.8.1. Enable/Disable Code 39 To enable or disable Code 39, scan the appropriat e barcode below. Enable (*) Disable 2.8.2. Enable/Disable Code 39 Full ASCII Code 39 - format - standard 43 chara cters (*)[...]

  • Page 30

    RoadRunners Evoluti on –L (1D) & -LA (Laser) – Programming Guide v1.3 - 30 - Data Capture for W ork force in Motion 2.8.4. Accepted Code 39 characters Code 39 - start/stop - accepte d characters - * only (stan dard Code 39) (*) Code 39 - start/stop - ac cepted characters - $ only (Trioptic Code 39) Code 39 - start/stop - ac cepted character[...]

  • Page 31

    RoadRunners Evoluti on –L (1D) & -LA (Laser) – Programming Guide v1.3 - 31 - Data Capture for W ork force in Motion 2.8.7. Italian PharmaCode settings Italian PharmaCode is based on Code39 encoding sch eme, thus its setting s are Code39 settings. Code 39 – Italian Pharmacod e – not a ctive (*) Code 39 – Italian Pha rmacode – active [...]

  • Page 32

    RoadRunners Evoluti on –L (1D) & -LA (Laser) – Programming Guide v1.3 - 32 - Data Capture for W ork force in Motion 2.10. Code 128 Settings 2.10.1. Enable/Disable Code 128/EAN 128 To enable or disable Code 128/EAN 128, scan the app ropriate barcode below. Disable Enable (*) 2.10.2. Set lengths for Code 128/EAN 128 Code 128/EAN 128 - barcode[...]

  • Page 33

    RoadRunners Evoluti on –L (1D) & -LA (Laser) – Programming Guide v1.3 - 33 - Data Capture for W ork force in Motion 2.10.3. EAN 128: Group Separator ‘FNC1’ included in an EAN128 co de is transmitted by default as ‘GS’ (Grou p Separator – 0x1D). Enable GS transmiss ion (*) Disable GS Transmis sion There is also the possibilit y to [...]

  • Page 34

    RoadRunners Evoluti on –L (1D) & -LA (Laser) – Programming Guide v1.3 - 34 - Data Capture for W ork force in Motion 2.10.4. Enable/Disable AIM ID Transmission Even if the “AIM ID t ransmit” is d isabled, it is possibl e to enable the AIM ID transmission f or EAN128. Enable AIM ID transmissio n for EAN128 Disable AIM ID trans mission for[...]

  • Page 35

    RoadRunners Evoluti on –L (1D) & -LA (Laser) – Programming Guide v1.3 - 35 - Data Capture for W ork force in Motion 2.11.3. Set lengths for Interleaved 2 of 5 Interleaved 2 of 5 - barcode length - minimum length = 6 (* ) Interleaved 2 of 5 – ba rcode length- any leng th 2.12. MSI Code Settings 2.12.1. Enable/Disable MSI To enable or disab[...]

  • Page 36

    RoadRunners Evoluti on –L (1D) & -LA (Laser) – Programming Guide v1.3 - 36 - Data Capture for W ork force in Motion 2.12.3. Set lengths for MSI MSI Code - barcode length - any length MSI Code - barcode length - minimum length = 6 (*) 2.13. Standard 2 of 5 Settings 2.13.1. Enable/Disable Standard 2 of 5 To enable or disable Standard 2 of 5 c[...]

  • Page 37

    RoadRunners Evoluti on –L (1D) & -LA (Laser) – Programming Guide v1.3 - 37 - Data Capture for W ork force in Motion 2.13.3. Set lengths for Standard 2 of 5 Standard 2 of 5 - barcode l ength - any length Standard 2 of 5 - barcode l ength - minimum len gth = 6 (*) 2.14. UPC/ EAN Settings 2.14.1. Enable/Disable UPC/EAN UPC / EAN - active (*) U[...]

  • Page 38

    RoadRunners Evoluti on –L (1D) & -LA (Laser) – Programming Guide v1.3 - 38 - Data Capture for W ork force in Motion 2.14.2. Transmit EAN13 Check Digit UPC / EAN - check digit - UPC - A and EAN13 - transmit ted (*) UPC / EAN - check digi t - UPC-A/EAN 13 - not t ransmitted 2.14.3. Transmit UPC-E Check Digit UPC / EAN - check digit - UPC - E [...]

  • Page 39

    RoadRunners Evoluti on –L (1D) & -LA (Laser) – Programming Guide v1.3 - 39 - Data Capture for W ork force in Motion 2.14.6. Transmit UPC number system for UPC-E UPC / EAN - UPC number s ystem - UPC - E - transmitted (*) UPC / EAN - UPC number system - UPC-E - n ot transmitted 2.14.7. UPC-A, UPC-E, EAN conversions UPC / EAN - re - encoding U[...]

  • Page 40

    RoadRunners Evoluti on –L (1D) & -LA (Laser) – Programming Guide v1.3 - 40 - Data Capture for W ork force in Motion 2.14.8. ISSN/ISBN settings UPC / EAN – ISSN/ISBN – Active (*) UPC / EAN – ISSN/ISB N – Not active UPC / EAN – ISSN/ISB N – ISSN hyphen not transm itted (*) UPC / EAN – ISSN/ISB N – ISSN hyphen transmitted UPC /[...]

  • Page 41

    RoadRunners Evoluti on –L (1D) & -LA (Laser) – Programming Guide v1.3 - 41 - Data Capture for W ork force in Motion 2.15. GS1 Data Bar (RSS) 14 Sett ings 2.15.1. Enable/Disable GS1 DataBar 14 GS1 DataBar 14 - active (*) GS1 DataBar 14 – not ac tive 2.15.2. GS1 DataBar 14 Check Digit Transmission GS1 DataBar 14 - check digit - transmitted [...]

  • Page 42

    RoadRunners Evoluti on –L (1D) & -LA (Laser) – Programming Guide v1.3 - 42 - Data Capture for W ork force in Motion 2.16. GS1 Data Bar (RSS) Limited Settings 2.16.1. Enable/Disable GS1 DataBar Limited GS1 DataBar Limited - active (*) GS1 DataBar Limited – not active 2.16.2. GS1 DataBar Limited Check Digit Transmission GS1 DataBar Limited [...]

  • Page 43

    RoadRunners Evoluti on –L (1D) & -LA (Laser) – Programming Guide v1.3 - 43 - Data Capture for W ork force in Motion 3. APPENDIX 1: ASCII Table (A-Z, a-z, 0- 9, punctuation, Control characters) Capital lette rs (A-Z): Name Programming label Name Programming label A N B O C P D Q E R F S G T H U I V J W K X L Y M Z[...]

  • Page 44

    RoadRunners Evoluti on –L (1D) & -LA (Laser) – Programming Guide v1.3 - 44 - Data Capture for W ork force in Motion Small letters (a-z): Name Programming label Name Programming label a n b o c p d q e r f s g t h u i v j w k x l Y m z[...]

  • Page 45

    RoadRunners Evoluti on –L (1D) & -LA (Laser) – Programming Guide v1.3 - 45 - Data Capture for W ork force in Motion Ponctuation: Name Programmin g label Name Programming label Space < ! = " > # ? $ @ % [ & ] ' ^ ( _ ) { * | + } , ~ - : . ; / LFLF$LF LF $[...]

  • Page 46

    RoadRunners Evoluti on –L (1D) & -LA (Laser) – Programming Guide v1.3 - 46 - Data Capture for W ork force in Motion Decimal numbe rs (0-9): Name Programming label 0 1 2 3 4 5 6 7 8 9[...]

  • Page 47

    RoadRunners Evoluti on –L (1D) & -LA (Laser) – Programming Guide v1.3 - 47 - Data Capture for W ork force in Motion Control Chara cters: Name Programming label CR EOT ETX LF NUL SOH STX TAB[...]

  • Page 48

    RoadRunners Evoluti on –L (1D) & -LA (Laser) – Programming Guide v1.3 - 48 - Data Capture for W ork force in Motion 4. APPENDIX 2 – AIM symbology identifiers structure The SI prefix is a two (2) or three (3) ch aracter string: ] c m where ] : SI indicator c : Symbology Id entification m : Modifier char acters (option al) Symbology Charact[...]