Baracoda All in One Printer 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

Ir a la página of

Buen manual de instrucciones

Las leyes obligan al vendedor a entregarle al comprador, junto con el producto, el manual de instrucciones Baracoda All in One Printer. La falta del manual o facilitar información incorrecta al consumidor constituyen una base de reclamación por no estar de acuerdo el producto con el contrato. Según la ley, está permitido adjuntar un manual de otra forma que no sea en papel, lo cual últimamente es bastante común y los fabricantes nos facilitan un manual gráfico, su versión electrónica Baracoda All in One Printer o vídeos de instrucciones para usuarios. La condición es que tenga una forma legible y entendible.

¿Qué es un manual de instrucciones?

El nombre proviene de la palabra latina “instructio”, es decir, ordenar. Por lo tanto, en un manual Baracoda All in One Printer se puede encontrar la descripción de las etapas de actuación. El propósito de un manual es enseñar, facilitar el encendido o el uso de un dispositivo o la realización de acciones concretas. Un manual de instrucciones también es una fuente de información acerca de un objeto o un servicio, es una pista.

Desafortunadamente pocos usuarios destinan su tiempo a leer manuales Baracoda All in One Printer, sin embargo, un buen manual nos permite, no solo conocer una cantidad de funcionalidades adicionales del dispositivo comprado, sino también evitar la mayoría de fallos.

Entonces, ¿qué debe contener el manual de instrucciones perfecto?

Sobre todo, un manual de instrucciones Baracoda All in One Printer debe contener:
- información acerca de las especificaciones técnicas del dispositivo Baracoda All in One Printer
- nombre de fabricante y año de fabricación del dispositivo Baracoda All in One Printer
- condiciones de uso, configuración y mantenimiento del dispositivo Baracoda All in One Printer
- marcas de seguridad y certificados que confirmen su concordancia con determinadas normativas

¿Por qué no leemos los manuales de instrucciones?

Normalmente es por la falta de tiempo y seguridad acerca de las funcionalidades determinadas de los dispositivos comprados. Desafortunadamente la conexión y el encendido de Baracoda All in One Printer no es suficiente. El manual de instrucciones siempre contiene una serie de indicaciones acerca de determinadas funcionalidades, normas de seguridad, consejos de mantenimiento (incluso qué productos usar), fallos eventuales de Baracoda All in One Printer y maneras de solucionar los problemas que puedan ocurrir durante su uso. Al final, en un manual se pueden encontrar los detalles de servicio técnico Baracoda en caso de que las soluciones propuestas no hayan funcionado. Actualmente gozan de éxito manuales de instrucciones en forma de animaciones interesantes o vídeo manuales que llegan al usuario mucho mejor que en forma de un folleto. Este tipo de manual ayuda a que el usuario vea el vídeo entero sin saltarse las especificaciones y las descripciones técnicas complicadas de Baracoda All in One Printer, como se suele hacer teniendo una versión en papel.

¿Por qué vale la pena leer los manuales de instrucciones?

Sobre todo es en ellos donde encontraremos las respuestas acerca de la construcción, las posibilidades del dispositivo Baracoda All in One Printer, el uso de determinados accesorios y una serie de informaciones que permiten aprovechar completamente sus funciones y comodidades.

Tras una compra exitosa de un equipo o un dispositivo, vale la pena dedicar un momento para familiarizarse con cada parte del manual Baracoda All in One Printer. Actualmente se preparan y traducen con dedicación, para que no solo sean comprensibles para los usuarios, sino que también cumplan su función básica de información y ayuda.

Índice de manuales de instrucciones

  • Página 1

    Data Capture for W orkforce in Motion ToughRunn ers / Sc anWear Communic ation Prot ocol ©Baracoda TM – May 2009[...]

  • Página 2

    ToughRunners / Scan Wear – Communication Protocol v1.2 - 2 - Data Capture for W orkforce in Motion SUMM A R Y SUMMARY ................................................................... 2 REVISION HISTORY .......................................................... 3 1. INTRODUCTION: GENERIC PACKET FORMAT ................................. 4 2. COMM[...]

  • Página 3

    ToughRunners / Scan Wear – Communication Protocol v1.2 - 3 - Data Capture for W orkforce in Motion Re vision History Changes to the original manual are listed belo w. Documen t Date Description 1.0 25th Sep. 07 Initial release 1.1 16th Dec. 08 Graphic Presenta tion upd ated 1.2 15th May 09 Updated for firm ware version 4.00.6[...]

  • Página 4

    ToughRunners / Scan Wear – Communication Protocol v1.2 - 4 - Data Capture for W orkforce in Motion 1. Introduction: gen eric packet format All the frames described in this docu ment are formatt ed as shown (*): STX Frame # Nbr of cmds Comm and 1 … Comm and x Checksum ETX 1 byte 1 byte 1 byte 3  n bytes … 3  n bytes 1 byte 1 byte B a ) 1[...]

  • Página 5

    ToughRunners / Scan Wear – Communication Protocol v1.2 - 5 - Data Capture for W orkforce in Motion 2. Command ID summary The commands are sort ed by category ( 4 MSB of Command ID): 0x0? Scanner control commands 0x01 Enter "Setting Mode" 0x02 Exit "Setting Mode" 0x03 Launch autotest // RESER VED 0x04 Endurance (AutoScan) tes t[...]

  • Página 6

    ToughRunners / Scan Wear – Communication Protocol v1.2 - 6 - Data Capture for W orkforce in Motion 0x3? RESERVED 0x4? MMI commands 0x40 Get vibrator 0x41 Set vibrator 0x42 Get beeps (since version 3.01.00) 0x43 Set beeps (since version 3.01.00) 0x5? Bluetooth commands 0x5E Bluetooth module command s 0x6? Reading and triggering c ommands 0x60 Get [...]

  • Página 7

    ToughRunners / Scan Wear – Communication Protocol v1.2 - 7 - Data Capture for W orkforce in Motion 0xA? Data format commands 0xA2 Get symbology prefix 0xA3 Set symbology prefix 0xA4 Get data suffix 0xA5 Set data suffix 0xA6 Get data pref ix 0xA7 Set data prefix 0xA8 Get AIM symbology ID tra nsmission 0xA9 Set AIM symbology ID tra nsmission 0xAA G[...]

  • Página 8

    ToughRunners / Scan Wear – Communication Protocol v1.2 - 8 - Data Capture for W orkforce in Motion 3. Command details 3.1. Setting mode Command ID 0x01 Description Enter Setting mode Length 0 payload none Response 0 (1 = ERROR) Command ID 0x02 Description Exit Setting mode Length 0 payload none Response 0 (1 = ERROR) A radio disconnection l eads [...]

  • Página 9

    ToughRunners / Scan Wear – Communication Protocol v1.2 - 9 - Data Capture for W orkforce in Motion Command ID 0x06 Description Reset operati onal statisti cs Length 10 payload 10 bytes : AAAABBBBCC where : AAAA = Number of scans don e BBBB = Operat ing time (min utes) CC = Number o f charge cycl es done (MSB first) Response 0 (1 = ERROR) 3.3. Wri[...]

  • Página 10

    ToughRunners / Scan Wear – Communication Protocol v1.2 - 10 - Data Capture for W orkforce in Motion 3.4. Restore defau lt settings Command ID 0x0F Description Restore facto ry default se ttings (reboo ts scanner) Length 1 payload A = 0 Response none 3.5. MMI settings Command ID 0x40 Description Get vibrator Length 0 payload none Response ABC wher[...]

  • Página 11

    ToughRunners / Scan Wear – Communication Protocol v1.2 - 11 - Data Capture for W orkforce in Motion B = Vibration duration on B ARCODE LOST e vent C = Vibration duration on NACK event Durations in 1/10 sec Response 0 (1 = ERROR) Command ID 0x4 2 (Since versio n 3.01.00) Description Get beeps Length 0 payload none Response 1 byte: Bit A.0 = 0  [...]

  • Página 12

    ToughRunners / Scan Wear – Communication Protocol v1.2 - 12 - Data Capture for W orkforce in Motion 3.6. Bluetooth commands Command ID 0x5E Description Bluetooth Com mands Length Variable (1-2 55) payload {Code ID} {le ngth} “Param eters” Response If the device responds: {Code ID} {length} “Response” Else: {0} Bluetooth specific com mands[...]

  • Página 13

    ToughRunners / Scan Wear – Communication Protocol v1.2 - 13 - Data Capture for W orkforce in Motion B d32 ) 0x00 : Length MSB B d33 ) 0x04 : Length LSB B d34 ) 0x30 : PIN Code 0 B d35 ) 0x30 : PIN Code 1 B d36 ) 0x30 : PIN Code 2 B d37 ) 0x30 : PIN Code 3 B e ) 0x31 : CheckSu m = ( ∑ = x b i i B ) mod 256 = 0x01+0x5E+x007+0x07+0x04+0x00 +0x30+0[...]

  • Página 14

    ToughRunners / Scan Wear – Communication Protocol v1.2 - 14 - Data Capture for W orkforce in Motion ------01 : Simple scan ------10 : Start Multi scan Session ---1---- : Stop Multis can Session D = long pres s duration x 100ms E = maximum s cans in sessi on: -0000000 : unlimited -XXXXXXX : number of s cans in the s ession 1------- : Anti-doubloo [...]

  • Página 15

    ToughRunners / Scan Wear – Communication Protocol v1.2 - 15 - Data Capture for W orkforce in Motion Command ID 0x61 Description Set reading m ode Length 9 payload ABCDEFGHI where : A = long pres s action (1 s ec.): ------00 : Disabled ------01 : Hold laser beam ------10 : Shut down sc anner ------11 : Start Multis can Session B = simple pr ess ac[...]

  • Página 16

    ToughRunners / Scan Wear – Communication Protocol v1.2 - 16 - Data Capture for W orkforce in Motion G = 0 H = 0 I = 0 Response 0 (1 = ERROR) Command ID 0x62 Description Get remote tr iggering sett ings Length 0 payload none Response ABCDEFG where : A = character to trigger a Good Read si gnal B = character to trigger a Good Read si gnal C = chara[...]

  • Página 17

    ToughRunners / Scan Wear – Communication Protocol v1.2 - 17 - Data Capture for W orkforce in Motion Command ID 0x63 Description Set remote tr iggering sett ings Length 7 payload ABCDEFG where : A = character to trigger a Good Read si gnal B = character to trigger a Good Read si gnal C = character to trigger a Simple Scan D = character to start an[...]

  • Página 18

    ToughRunners / Scan Wear – Communication Protocol v1.2 - 18 - Data Capture for W orkforce in Motion Command ID 0x81 Description Set symbology settings Length 20 (since ver sion 3.02.03) payload cf. Appendix B for detail s Response 0 (1 = ERROR) Command ID 0x82 Description Get voting va lue Length 0 payload none Response V = number of decodes to v[...]

  • Página 19

    ToughRunners / Scan Wear – Communication Protocol v1.2 - 19 - Data Capture for W orkforce in Motion Length 1 payload T = timeout in seconds (255 = Autoscan m ode) Response 0 (1 = ERROR) 3.9. Data format com mands Command ID 0xA2 Description Get symbology prefix Length 0 or 1 payload None Response 22 or 28 bytes (s ince version 3.02.03) (if length[...]

  • Página 20

    ToughRunners / Scan Wear – Communication Protocol v1.2 - 20 - Data Capture for W orkforce in Motion Default settings : 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x0 0 0x00 0x00 0x00 Command ID 0xA3 Description Set symbology prefix Length 28 (since ver sion 3.02.03) payload AABBCCDDEEFFG GHHIIJJKK LL[...]

  • Página 21

    ToughRunners / Scan Wear – Communication Protocol v1.2 - 21 - Data Capture for W orkforce in Motion Command ID 0xA4 Description Get data suff ix Length 0 payload None Response 0-32 bytes: suffix Default settings : No suffix Command ID 0xA5 Description Set data suff ix Length 0-32 payload suffix Response 0 (1 = ERROR) Command ID 0xA6 Description G[...]

  • Página 22

    ToughRunners / Scan Wear – Communication Protocol v1.2 - 22 - Data Capture for W orkforce in Motion Command ID 0xA8 Description Get AIM symbo logy ID trans mission Length 0 payload None Response A : 0 = disabled 1 = enabled Default settings : A = 0 Command ID 0xA9 Description Set AIM symbo logy ID trans mission Length 1 payload A : 0 = disabled 1[...]

  • Página 23

    ToughRunners / Scan Wear – Communication Protocol v1.2 - 23 - Data Capture for W orkforce in Motion CC = Standard 2 of 5 DD = Codabar EE = EAN/UPC FF = Code128 GG = MSI HH = PLESSEY II = Code93 JJ = EAN128 KK = Codabloc k F LL = RSS 14 ( GS1 Databar) MM = RSS Ltd (GS1 Databar Ltd) NN = RSS Expa nded (GS1 Dat abar Expanded ) 0x00 means di sabled. [...]

  • Página 24

    ToughRunners / Scan Wear – Communication Protocol v1.2 - 24 - Data Capture for W orkforce in Motion EE = EAN/UPC FF = Code128 GG = MSI HH = PLESSEY II = Code93 JJ = EAN128 KK = Codabloc F LL = RSS 14 ( GS1 Databar) MM = RSS Ltd (GS1 Databar Ltd) NN = RSS Expa nded (GS1 Dat abar Ltd) 0x00 means di sabled. Response 0 (1 = ERROR) 3.10. Communication[...]

  • Página 25

    ToughRunners / Scan Wear – Communication Protocol v1.2 - 25 - Data Capture for W orkforce in Motion Length 1 payload Bit A.0 = 1 if switc h to slave wh en charging Bit A.1 = 1 i f switch radi o off when ch arging Response 0 (1 = ERROR) 3.11. Power saving comman ds Command ID 0xF0 Description Get shutdown timers Length 0 payload None Response 7 by[...]

  • Página 26

    ToughRunners / Scan Wear – Communication Protocol v1.2 - 26 - Data Capture for W orkforce in Motion CC = radio shut down timer wh en in Slave m ode (sec.) U = 0 (unused ) Response 0 (1 = ERROR) Command ID 0xF2 Description Get battery s tatus Length 0 payload None Response 1 byte: Bits A.0-6 = battery level (RFU) Bit A.7 = 1  low battery[...]

  • Página 27

    ToughRunners / Scan Wear – Communication Protocol v1.2 - 27 - Data Capture for W orkforce in Motion 4. Special packets These packets do not foll ow the above fram e format. 4.1. Deprecated packe ts Code ID Description frame 0x01 Legacy 1 1 1 o r 1 2 1 These 2 sequences will be recognized and pu rged for backward compatibility with older Baracoda [...]

  • Página 28

    ToughRunners / Scan Wear – Communication Protocol v1.2 - 28 - Data Capture for W orkforce in Motion 4.3. Special scanner t o host messages Code ID Description Payload 0x32–0x33 Barcode data Barcode strin g 4.4. Special host to scanner messag es Code ID 0x46-0x47 Description Get Capture F rame Format Payload None Response 1 byte {0 = Baracoda , [...]

  • Página 29

    ToughRunners / Scan Wear – Communication Protocol v1.2 - 29 - Data Capture for W orkforce in Motion 5. Append ix A: Bluetooth Protocol. 5.1. The configu ration frames are as fo llows: Header Length Payload 1 byte 2 bytes(MSB, LS B) 0 to 65535 bytes 5.2. Command s: Command Header Length Payload Answer Set PinCode 0x01 xx xx (new pin size) N digits[...]

  • Página 30

    ToughRunners / Scan Wear – Communication Protocol v1.2 - 30 - Data Capture for W orkforce in Motion Command Header Length Payload Answer Set mode 0x03 00 0 2 [0 x01 if MASTER, 0x00 if SLAVE], [BT Clock Role switch] (def ault SLAVE) 0x03 00 01 01 if done 0x03 00 01 00 if not You can set the size to 2. In this case, th e second argument tells the m[...]

  • Página 31

    ToughRunners / Scan Wear – Communication Protocol v1.2 - 31 - Data Capture for W orkforce in Motion Command Header Length Payload Answer Get Bluetooth Version 0x76 00 00 - 0x76, x , x, {version string } Command frame Answ er Restore Factory Settings 'R', 's', 't' - Restore default settings: Pin code “0000” Mode :[...]

  • Página 32

    ToughRunners / Scan Wear – Communication Protocol v1.2 - 32 - Data Capture for W orkforce in Motion Command Header Length Payload Answer Get page scan timeout 0x25 00 00 - 0x25 00 04 [Page Interval (MSB) | Page Int erval (LSB) | Page Window ( MSB) | Page Wind ow (LSB)] Page Scan Interval and Page Scan Wind ow are in num ber of Bluetooth sl ots) ([...]

  • Página 33

    ToughRunners / Scan Wear – Communication Protocol v1.2 - 33 - Data Capture for W orkforce in Motion Command Header Length Payload Answer Set sniff 0x09 00 04 [MSB of MinSniff interval, LSB of MinSniff interval, MSB of MaxSniff i nterval, LSB of MaxSnif interval] 0x09 00 01 01 if done 0x09 00 01 00 if not Command Header Length Payload Answer Set s[...]

  • Página 34

    ToughRunners / Scan Wear – Communication Protocol v1.2 - 34 - Data Capture for W orkforce in Motion MinSniff = 0x0050 MaxSniff = 0x00F0 Attempt = 0x0008 Timeout = 0x0030 MaxSniff and MinSni ff are only used for sniff neg ociation between the S martodule and the other BT device. If both sides all ow sniff value MaxSniff, then MaxSni ff will be use[...]

  • Página 35

    ToughRunners / Scan Wear – Communication Protocol v1.2 - 35 - Data Capture for W orkforce in Motion Command Header Length Payload Answer Set security mode 0x21 00 {size} {00 non secured, 01 se cured} {PIN CODE (default 01) 0x21 0 0 01 01 if done, 0x21 00 01 00 if not Size=PINCODE size + 1 For example : 0x21 00 05 00 30 30 30 30 to disabl e securi[...]

  • Página 36

    ToughRunners / Scan Wear – Communication Protocol v1.2 - 36 - Data Capture for W orkforce in Motion Command Header Length Payload Answer Get local BT address 0x 4 3 00 00 - 0x43 00 06 {6 Bytes (B D_address MSB, ... , LSB)} Command Header Length Payload Answer Set Target Service UUID 0x38 00 02 [UUID (2 Bytes)] (default 0x1101) 0x38 00 01 01 if do[...]

  • Página 37

    ToughRunners / Scan Wear – Communication Protocol v1.2 - 37 - Data Capture for W orkforce in Motion Command Header Length Payload Answer Set Remote rfco mm channel 0x36 00 01 [channel (1 Byte)] 0x36 00 01 01 if done 0x36 00 01 00 if not Command Header Length Payload Answer Get Remote rfco mm channel 0x37 00 00 - 0x37 0 0 01 [ channel ] If “chan[...]

  • Página 38

    ToughRunners / Scan Wear – Communication Protocol v1.2 - 38 - Data Capture for W orkforce in Motion 6. Append ix B: Decoder Protocol. This section describes in detail the 20 byt es of the response/payl oad of the 0x80/0x81. Byte # Byte name Default v alue 1 COD1 0xB4 2 COD2 0 x90 3 OPC39 0xEF 4 OPMUL 0x20 5 OP25I 0x36 6 LEI1 0x00 7 LEI2 0x00 8 LE[...]

  • Página 39

    ToughRunners / Scan Wear – Communication Protocol v1.2 - 39 - Data Capture for W orkforce in Motion When both code128 an d EAN128 are ena bled, both are decoded but have a different symbology ID . When only EA N128 is e nabl ed, only EAN128 co des are decoded. Code39 param eters: OPC39 Descripti on Default b0 Standard 43 chara cters ( 1) / FULL A[...]

  • Página 40

    ToughRunners / Scan Wear – Communication Protocol v1.2 - 40 - Data Capture for W orkforce in Motion Standard 2 of 5 and MSI param eters: OP25S Descri ption Defaul t b0 Reserved (d o not modi fy) 1 b1 (0,0) : 1 fi xed all owed length (specifi ed in LES1) (1,0) : 2 fi xed all owed lengths (speci fied in LES 1 and LES2) (0,1) : 3 fi xed all owed len[...]

  • Página 41

    ToughRunners / Scan Wear – Communication Protocol v1.2 - 41 - Data Capture for W orkforce in Motion OPEAN2 Descripti on Default b0 U PCE check di git not transmit ted 0 b1 UPCE conversi on enable d 0 b2 0: transmit UPCE as UP CA 1: transmi t UPCE as EA N13 0 b3 0: transmit UPCA as E AN13 1: transmi t UPCA as U PCA 1 b4 Reserved (d o not modi fy) [...]

  • Página 42

    ToughRunners / Scan Wear – Communication Protocol v1.2 - 42 - Data Capture for W orkforce in Motion RSS Expand ed (GS1 D atabar Exp anded) par ameters : RSS Expanded Descripti on Default b0 RSS Expanded val idati on 1 b1 AIM Prefix « ]e0 » vali dation 1 b2 AI M Prefix « ] C1 » vali dation ( prioritary over b1) 0 b3 Appli cation indenti fier A[...]