BaracodaメーカーAll in One Printerの使用説明書/サービス説明書
ページ先へ移動 of 42
Data Capture for W orkforce in Motion ToughRunn ers / Sc anWear Communic ation Prot ocol ©Baracoda TM – May 2009.
ToughRunners / Scan Wear – Communication Protocol v1.2 - 2 - Data Capture for W orkforce in Motion SUMM A R Y SUMMARY ................................................................... 2 REVISION HISTORY ............................................
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.
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 a.
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 con.
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.
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 .
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 payloa.
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.
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.
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.
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) p.
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 C.
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 = .
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.
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 i.
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 = .
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.
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.
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.
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 Def.
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 :.
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.
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.
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.
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.
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.
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.
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.
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.
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 stri.
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 .
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 MinSni.
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.
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.
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, .
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.
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.
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.
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 b.
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 .
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 Expa.
デバイスBaracoda All in One Printerの購入後に(又は購入する前であっても)重要なポイントは、説明書をよく読むことです。その単純な理由はいくつかあります:
Baracoda All in One Printerをまだ購入していないなら、この製品の基本情報を理解する良い機会です。まずは上にある説明書の最初のページをご覧ください。そこにはBaracoda All in One Printerの技術情報の概要が記載されているはずです。デバイスがあなたのニーズを満たすかどうかは、ここで確認しましょう。Baracoda All in One Printerの取扱説明書の次のページをよく読むことにより、製品の全機能やその取り扱いに関する情報を知ることができます。Baracoda All in One Printerで得られた情報は、きっとあなたの購入の決断を手助けしてくれることでしょう。
Baracoda All in One Printerを既にお持ちだが、まだ読んでいない場合は、上記の理由によりそれを行うべきです。そうすることにより機能を適切に使用しているか、又はBaracoda All in One Printerの不適切な取り扱いによりその寿命を短くする危険を犯していないかどうかを知ることができます。
ですが、ユーザガイドが果たす重要な役割の一つは、Baracoda All in One Printerに関する問題の解決を支援することです。そこにはほとんどの場合、トラブルシューティング、すなわちBaracoda All in One Printerデバイスで最もよく起こりうる故障・不良とそれらの対処法についてのアドバイスを見つけることができるはずです。たとえ問題を解決できなかった場合でも、説明書にはカスタマー・サービスセンター又は最寄りのサービスセンターへの問い合わせ先等、次の対処法についての指示があるはずです。