CipherLab 8000 Operation & User’s Manual

For 8 Series Mobile Computers: 8000 / 8200 / 8300 / 8400 / 8500 / 8600 / 8700 Version 4.03

All rights reserved The software contains proprietary information of CIPHERLAB CO., LTD.; it is provided under a license agreement containing restrictions on use and disclosure and is also protected by copyright law. Reverse engineering of the software is prohibited. Due to continued product development this information may change without notice. The information and intellectual property contained herein is confidential between CIPHERLAB and the client and remains the exclusive property of CIPHERLAB CO., LTD. If you find any problems in the documentation, please report them to us in writing. CIPHERLAB does not warrant that this document is error-free. No part of this publication may be reproduced, stored in a retrieval system, or transmitted in any form or by any means, electronic, mechanical, photocopying, recording or otherwise without the prior written permission of CIPHERLAB CO., LTD. For product consultancy and technical support, please contact your local sales representative. Also, you may visit our web site for more information. The CipherLab logo is a registered trademark of CIPHERLAB CO., LTD. Microsoft, Windows, and the Windows logo are registered trademarks of Microsoft Corporation in the United States and/or other countries. Bluetooth is a trademark of Bluetooth SIG, Inc., U.S.A. Other product names mentioned in this manual may be trademarks or registered trademarks of their respective companies and are hereby acknowledged. The editorial use of these names is for identification as well as to the benefit of the owners, with no intention of infringement. CIPHERLAB CO., LTD. Website: http://www.cipherlab.com

and 8600 added  Modified: 5.1.4 – Mifare login key settings added  Modified: 5.1.5 – Upload method settings added with FastVPort for 8600 series  Modified: 5.1.6 – Download method settings added with FastVPort for 8600 series 4.02 Jun. 25, 2014  Modified: 1.15.2 – Trim leading specified character function added  Modified: 6.2 – LATIN (Multilingual Latin I), SLAVIC (Latin II), POLISH (Central European, Latin II), Latin I (CP_1252) languages added  Modified: 6.2 – Latin(Slovak) & Windows 1250 fonts are not supported for 8600 series 4.01 Jun. 10, 2014  Modified: 1.13 – Max Length complying with Lookup when the form refers to a lookup file  Modified: 1.15.1 Field Data – further details for Comparison Operators  Modified: 1.15.2 – ENTER option added for Auto ENTER  Modified: 3.3.1 – checkbox for updating lookup once added  Modified: 5.1.4 – RFID reader option (data in Hex / length in bytes)  Modified: 6.2 – Turkish (Windows-1254) added  Modified: 7.2.1 Data_Read – notes for 8600 not supported  Modified: Appendix II – add ‘Code 39 Security Level’, ‘EAN8 GTIN-13 format (5 zeros padded)’, GS1 Formatting in Symbology Settings Table  Modified: Appendix III – add GS1 Formatting (Symbology Settings Table (8300/8500) & (8700)); add ‘Code 39 Security Level’, ‘EAN8 GTIN-13 format (5 zeros padded)’ (Symbology Settings Table (8700))  Modified: Appendix IV – add ‘Read Redundancy’, ‘Mobile Display Mode’ in the Reader Settings Table  Modified: Appendix IV – > TLC-39 default changed to ‘Disable’ > GS1 Formatting/Field Separator/Application ID mark added for GS1 DataBar and Composite CC-A/B/C in the Symbology Settings Table 4.00 Jan. 15, 2014  New: 8600 support  Modified: FTP File Setting – refer to Appendix VI Creating a Script File  New: 1.4 Color Properties (8600 only)  New: 2.4 Color Properties (8600 only)  Modified: 6.2 Font Properties – table and pictures added RELEASE NOTES

 Modified: 7.3 MobileLink removed  Modified: Appendix I Scan Engine and RFID Tag Supported tables updated  Modified: Appendix V Command Line Syntax – AG_Load added  Modified: Appendix IV Creating a Script File added 3.23 Jun. 13, 2013  Modified: 3.3.1 – Description for “Show message when data is matched” added  Modified: 7.3.7 – screenshot & related descriptions for “Add Delimiter” and “Date Style” UI items updated 3.22 Mar. 13, 2013  Modified: Appendix V Command Line Syntax – Data_Read arguments appended 3.21 Feb. 05, 2013  Modified: Chapter 1 - Form1 screenshot updated  Modified: 1.2.4 Enable MSQL - screenshots updated  Modified: 1.3 Font Size – Font Size table updated  Modified: 1.8 Data Type – screenshot updated  Modified: 1.8.6 Real – screenshot updated  Modified: Chapter 2 – Menu1 screenshot updated  Modified: Chapter 6 – screenshot updated  Modified: 6.2 Font Properties – descriptions revised  Modified: 7.2.1 Data_Read – screenshot updated  New: “Appendix III LR/ELR LASER SCAN ENGINE” – Symbology Settings Table (8700) added  Modified: “Appendix IV 2D Scan Engine” – “Convert UPC-A to EAN-13” included in “1D Symbologies Table” 3.20 Oct. 18, 2012  New: 1.8.20 Serial – “Data Type” added with “Serial” option  New: 1.14.1 Field Data – “Compare” checkbox added  New: 1.14 More – “Decimal symbol” pull-down menu added  New: 7.2.1 Data Read – pull-down menus for file selection added  Modified: 7.3 MobileLink – launching MobileLink as a Windows service  Modified: FTP File Settings – Lookup file settings 3.11 25th May 2012  New: Introduction | Using FTP Server to Transfer Files | WLAN Security Settings – WPA/WPA2: If entered passphrase falls shorter than 8 characters, a warning dialog pops up when OK button is hit to submit changes.  New: 1.2.4. Enable MSQI – “TRACK” input screen can be removed by adjusting key field properties.  New: 7.3.7. Change Data File Settings – File-naming rule with new “separator” feature and file extension customization 3.10 Apr. 24, 2012 MobileLink supports more communicative interfaces. Updates involved are:  Modified: Introduction | MobileLink Data Connection.  Modified: 7.3. MobileLink. 3.01 Feb. 07, 2012  Modified: Section 2.5: The option “Save the collected data for each form to separate data files” renamed to “Separate Each Data File and Edit Form Name” on Menu property page.

 Modified: Section 5.2 “Function Key Setting”: Data collecting forms aren’t supported by keypad shortcuts. 3.00 Dec. 16, 2011  New: 8700 support  New: Introduction | Getting Started | Localization: Bundled font files  New: Introduction | “Title Bar”  New: “Data Type” supports date/time info. Updates involved are:  1.5 “Date & Time Stamp” updated  1.8.18 “Date” newly inserted.  1.8.19 “Time” newly inserted.  Modified: 5.1.5 “Upload Method”  8000, 8200, 8300 & 8400: The interface “Bluetooth SPP” is deleted and replaced by “Bluetooth SPP_Master” and “Bluetooth SPP_Slave”.  Modified: 5.1.6 “Download Method”  8000, 8200, 8300 & 8400: The interface “Bluetooth SPP” is deleted and replaced by “Bluetooth SPP_Master” and “Bluetooth SPP_Slave”.  Modified: 7.2.1 Data_Read.exe screenshot updated.  Modified: 7.2.1 [Options] updated.  Modified: 7.2.1 [Auto upload and delete Data and Lookup files] updated. 2.28 Jul. 19, 2011  Modified: 7.2.1 Data_Read — update screenshot and settings 2.27 Jun. 03, 2011  Modified: add “Convert to 8200” feature for AG8300  Modified: 5.1.5 Upload Method — add “USB VCOM_CDC” for AG8200  Modified: 5.1.6 Download Method — add “USB VCOM_CDC” for AG8200 2.26 May 17, 2011  Modified: Appendix IV — change Code 11 and MSI to “Disable” by default 2.25 Mar. 21, 2011  New: support 8200  Modified: Using FTP Server to Transfer Files — update screenshots  Modified: 7.3.7 Change Data File Settings — add log file settings  Modified: 7.3.8 Manage Devices & 7.3.9 Manage Your Rules — update screenshots  Modified: Appendix I~II — support UPC-E1 for CCD/Laser  Modified: Appendix I~II — support Coop 25 for CCD/Laser (8000/ 8200/8300/8400)  Modified: Appendix II — add Aiming Duration (8000/8200/8300/ 8400)  Modified: Appendix III — add Scan Mode options (8300 Only) and Time-out  Modified: Appendix II~IV — change Time-out range to 0~255 sec.  Modified: Appendix III~IV — change Aiming Duration range to 1~255 sec.  Modified: Appendix IV — change Codabar, Code 93 and MSI to “Enable” by default 2.24 Jan. 04, 2011  Modified: 1.8.16 Large Data — for collecting data via 2D scan engine  Modified: 1.8.17 Read from 2D

 New: Appendix V Command Line Syntax (for utilities) 2.23 Dec. 15, 2010  New: Introduction — add System Requirements  Modified: Introduction — Getting Started, add “Using MobileLink to Transfer Files over Network”  Modified: 5.3 Security Setting  New: 7.3.8 Manage Devices  New: 7.3.9 Manage Rules 2.22 Nov. 01, 2010  Modified: Introduction — Getting Started, add “Using FTP Server to Transfer Files”  Modified: Introduction — Menu Bar, add “FTP Communication Settings”, “WLAN Communication Settings” and “FTP File Settings”  Modified: 1.8.15 Counter  Modified: 7.3 Mobile Link — update screenshots  Modified: 7.3.3 View Link Status — 8000/8300 supports Auto Upload  Modified: 7.3.7 Change Data File Settings — update Auto File Name  Modified: Appendix II — change Negative Barcode to “Enable” by default 2.21 Sep. 13, 2010  Modified: Getting Started, Upload Data — describe icons indicating support of auto upload  Modified: 3.2.4 DBF File Location (8400 Only)  Modified: 3.8 Action When the Format of Record Is Wrong  New: 7 Utilities  Modified: 7.4 SD DBF Converter (8400 Only)  Modified: Appendix I~IV — add more GS1 DataBar symbologies 2.20 Apr. 02, 2010  Modified: Introduction — Getting Started, Menu Bar, Toolbar and Menu Tree  Modified: Installing FORGE Application Generator — DATA_READ utility also synchronizes date/time on every host connection.  Modified: Getting Started — (1) add Upload Application Template (2) Download Lookup Files (file path changed to “\AG\DBF” for lookup files)  Modified: Menu Bar — (1) DBF Converter (file path changed to “\AG\DBF” for lookup files) (2) DATA_READ utility also synchronizes date/time on every host connection.  Modified: 1.14.1 Field Data — Decimal Places  Modified: 1.2.4 Enable MSQI  Modified: 3.3.3 Trim Space When Lookup Data Can Be Uploaded  Modified: 5.1.6 Download Method — AG8400 (file path changed to “\AG\DBF” for lookup files)  Modified: 5.2 Function Key Setting — update screenshot, etc.  Modified: 5.3.1 Upload .AGX — change 6-digit password to 5-digit  Modified: Appendix IV 2D Scan Engine — update 2.19 Nov. 19, 2009  New: support 8400-2D  Modified: 5.1.5 Upload & Download Settings — Buzzer Volume changed to LARGE_VOL  Modified: Appendix IV — Chinese 25, Matrix 25, Picklist Mode, 1D

Intelligent Mail 2.18 June. 25, 2009  Modified: 3.2.4 “DBF File Location” and section 6.3.3 “DAT File Location” features are added.  Modified: 5.1.5 — add DBF Converter, download and upload information 2.17 May. 07, 2009  Modified: “Convert to 8300” and other 8400 supported features are added. 2.16 Jan. 19, 2009  Modified: 8400 supported features are added. 2.15 Nov. 26, 2008  Applied new GUI screen shots and modified the relative contents. 2.14 July 30, 2008  Modified: 6.3 — add “Use Large Font for Data Browsing” for AG8000 and AG8300  Modified: Appendix II~III support replacement of EAN-128 field separator for all scan engines 2.13 Jun. 26, 2008  Modified: 1.6 Record — add “remove from lookup” and “save & remove” options  Modified: 3.11 Action When the Input Data Has No Match — add “remove from lookup” and “save & remove” options  Modified: 4.1.2 RFID Reader — Automatically enabled after initialization (checkbox removed from UI)  New: Long Range Laser option available for 8300 2.12 Nov. 06, 2007  Modified: 4.1.2 RFID Reader — RFID tags in proximity will be read automatically by 8300/8500 when RFID reader is enabled 2.11 Oct. 18, 2007  Modified: Features 2.10 Sep. 19, 2007 New Word template applied 2.07 June 20, 2006  Company name changed to CIPHERLAB CO., LTD. since April 2006  Modified: 5.3 Barcode & Parameters 2.06 Apr. 14, 2006  Modified: 1.2.2 — Font_12x12 not supported  Modified: 5.1 & 5.2.6  Modified: 6.2, 6.4 & 6.5 2.05 Apr. 10, 2006 AG for CPT-8500 is included

INTRODUCTION.................................................................................................................................... 1 System Requirements....................................................................................................................... 2 Intended Purpose.............................................................................................................................. 2 Features............................................................................................................................................. 2 Installing FORGE Batch AG ............................................................................................................... 3 Getting Started .................................................................................................................................. 4 Download AG Runtime................................................................................................................. 4 Download Application Templates................................................................................................ 5 Download Lookup Files................................................................................................................ 7 Collect & Edit Data....................................................................................................................... 7 Upload Data.................................................................................................................................. 8 Upload Application Templates..................................................................................................... 8 Localization................................................................................................................................... 9 Using FTP Server to Transfer Files .................................................................................................11 FTP Communication Settings ....................................................................................................11 FTP File Settings.........................................................................................................................13 WLAN Communication Settings ................................................................................................15 WLAN Security Settings .............................................................................................................16 Remote Console Data Transfer ......................................................................................................18 Remote Console Settings ..........................................................................................................18 Title Bar............................................................................................................................................19 Software Version Info.................................................................................................................19 Application Template’s Version Info .........................................................................................19 Menu Bar .........................................................................................................................................21 File Menu .........................................................................................................................................23 Preference ..................................................................................................................................23 AGX Template Conversion .........................................................................................................24 Recent File List...........................................................................................................................28 Language .........................................................................................................................................28 Toolbar .............................................................................................................................................29 Tree Menu........................................................................................................................................29 FORM .................................................................................................................................................31 1.1 Select a Form............................................................................................................................33 1.2 Properties..................................................................................................................................33 1.2.1 Esc.....................................................................................................................................33 1.2.2 Next...................................................................................................................................33 1.2.3 Record...............................................................................................................................34 1.2.4 Enable MSQI.....................................................................................................................36 1.3 Font Properties .........................................................................................................................40 1.4 Color Properties (8600 only)....................................................................................................40

1.5 Lookup (File) .............................................................................................................................41 1.6 Date & Time Stamp ..................................................................................................................42 1.7 Branch.......................................................................................................................................43 1.8 Reset Current Form ..................................................................................................................43 1.9 Data Type ..................................................................................................................................44 1.9.1 Nil ......................................................................................................................................45 1.9.2 Text....................................................................................................................................46 1.9.3 Integer...............................................................................................................................46 1.9.4 Real...................................................................................................................................46 1.9.5 Letter.................................................................................................................................48 1.9.6 Auto (+/-) ..........................................................................................................................48 1.9.7 Boolean.............................................................................................................................49 1.9.8 Lookup ..............................................................................................................................49 1.9.9 Fixed Data.........................................................................................................................50 1.9.10 Prompt............................................................................................................................50 1.9.11 Counter...........................................................................................................................50 1.9.12 Passdown .......................................................................................................................53 1.9.13 Extension........................................................................................................................53 1.9.14 Pause..............................................................................................................................54 1.9.15 Alphameric .....................................................................................................................54 1.9.16 Date ................................................................................................................................54 1.9.17 Time................................................................................................................................54 1.9.18 Serial...............................................................................................................................55 1.9.19 Large Data......................................................................................................................55 1.9.20 Read from 2D.................................................................................................................56 1.9.21 GPS Latitude (8600 only)..............................................................................................56 1.9.22 GPS Longitude (8600 only)...........................................................................................56 1.10 Prompt ....................................................................................................................................56 1.11 Input Type ...............................................................................................................................57 1.12 Minimum Length ....................................................................................................................57 1.13 Maximum Length....................................................................................................................57 1.13.1 Input via Barcode/RFID Reader....................................................................................58 1.13.2 Input via Keypad ............................................................................................................58 1.14 Variables/Field .......................................................................................................................59 1.14.1 Field ................................................................................................................................60 1.14.2 Variables.........................................................................................................................61 1.15 More........................................................................................................................................62 1.15.1 Field Data .......................................................................................................................63 1.15.2 Barcode Input.................................................................................................................65 MENU .................................................................................................................................................67 2.1 Select a Menu...........................................................................................................................68 2.2 Properties..................................................................................................................................68 2.2.1 Menu Caption...................................................................................................................68 2.2.2 ESC....................................................................................................................................68 2.3 Font Properties .........................................................................................................................68 2.4 Color Properties (8600 only)....................................................................................................69 2.5 Data...........................................................................................................................................69 2.5.1 Save Caption ....................................................................................................................69

2.5.2 Save Selected Item ..........................................................................................................69 2.5.3 Pass Down........................................................................................................................69 2.6 Separate Each Data File and Edit Form Name.......................................................................69 2.7 Item Name ................................................................................................................................70 2.8 Next ...........................................................................................................................................70 2.9 Reset Current Menu .................................................................................................................70 LOOKUP..............................................................................................................................................71 3.1 Select a Lookup File .................................................................................................................73 3.2 Field Property............................................................................................................................73 3.2.1 Number of Fields..............................................................................................................73 3.2.2 Fixed Length .....................................................................................................................73 3.2.3 Delimiter ...........................................................................................................................73 3.2.4 DBF File Location (8200/8400/8600/8700 Only).......................................................74 3.3 Lookup Data..............................................................................................................................76 3.3.1 Only Read Data Once.......................................................................................................76 3.3.2 Lookup Data Can Be Uploaded .......................................................................................76 3.3.3 Trim Space When Lookup Data Can Be Uploaded.........................................................76 3.4 Action When the Input Data Has No Match............................................................................77 3.4.1 Continue ...........................................................................................................................77 3.4.2 Show Warning Message ..................................................................................................77 3.4.3 Insert to Lookup File ........................................................................................................77 3.4.4 Show Warning Message & Insert ....................................................................................78 3.4.5 Clear the Screen...............................................................................................................78 3.4.6 Show Warning & Clear Screen ........................................................................................78 3.5 Offset.........................................................................................................................................79 3.6 Length .......................................................................................................................................79 3.7 Key Field....................................................................................................................................79 3.8 Action When Record Format Is Wrong.....................................................................................80 3.8.1 Stop the Download Process ............................................................................................80 3.8.2 Truncate / Reformat the Record.....................................................................................81 3.8.3 Skip the Record................................................................................................................82 3.9 Reset Current Lookup File .......................................................................................................82 SYMBOLOGY ......................................................................................................................................83 4.1 Reader Settings ........................................................................................................................84 4.1.1 Code ID .............................................................................................................................84 4.1.2 Reset.................................................................................................................................84 4.2 Barcode & Parameters.............................................................................................................84 SETTINGS...........................................................................................................................................85 5.1 Initial Settings ...........................................................................................................................86 5.1.1 Data Manipulation ...........................................................................................................86 5.1.2 Keypad & LCD ..................................................................................................................87 5.1.3 Notification .......................................................................................................................87 5.1.4 Reader Option ..................................................................................................................88 5.1.5 Upload Method.................................................................................................................89 5.1.6 Download Method............................................................................................................92 5.1.7 Baud Rate & Modem Speed............................................................................................94

5.1.8 Reset Settings ..................................................................................................................94 5.2 Function Key Setting ................................................................................................................95 5.3 Security Setting.........................................................................................................................96 5.3.1 Security Checking.............................................................................................................96 5.3.2 Upload .AGX......................................................................................................................98 STARTUP ............................................................................................................................................99 6.1 Application Start From............................................................................................................100 6.2 Font Properties .......................................................................................................................101 6.3 Color Properties (8600 only)..................................................................................................102 6.4 Data Field Properties..............................................................................................................103 6.4.1 Number of Delimiter ......................................................................................................103 6.4.2 Browse data font size ....................................................................................................103 6.4.3 DAT File Location............................................................................................................103 6.5 Redefine Prompts & Messages .............................................................................................103 6.6 Import Prompts & Messages .................................................................................................103 6.7 Reset Prompts & Messages to Default.................................................................................103 UTILITIES..........................................................................................................................................105 7.1 Download Utilities...................................................................................................................106 7.1.1 AG Load...........................................................................................................................106 7.1.2 DLookup..........................................................................................................................109 7.1.3 ProgLoad.........................................................................................................................112 7.2 Upload Utilities........................................................................................................................114 7.2.1 Data_Read......................................................................................................................114 7.2.2 AGX_Read.......................................................................................................................118 7.3 SD DBF Converter (8200/8400/8600/8700 Only) ............................................................120 7.4 Program Simulation................................................................................................................122 SCAN ENGINE SETTINGS.................................................................................................................125 Symbologies Supported................................................................................................................126 RFID Tags Supported ....................................................................................................................128 CCD/LASER SCAN ENGINE..............................................................................................................131 Reader Settings Table...................................................................................................................131 Symbology Settings Table.............................................................................................................133 LR/ELR LASER SCAN ENGINE.........................................................................................................139 Reader Settings Table...................................................................................................................139 Symbology Settings Table (8300/8500).....................................................................................140 Symbology Settings Table (8700) ................................................................................................144 2D SCAN ENGINE.............................................................................................................................149 Reader Settings Table...................................................................................................................149 Symbology Settings Table.............................................................................................................151 1D Symbologies .......................................................................................................................151 2D Symbologies .......................................................................................................................157

COMMAND LINE SYNTAX.................................................................................................................161 Download Utilities..........................................................................................................................162 DLookup....................................................................................................................................162 ProgLoad...................................................................................................................................163 AG_Load....................................................................................................................................164 Upload Utilities ..............................................................................................................................166 Data_Read................................................................................................................................166 CREATING A SCRIPT FILE.................................................................................................................171 Remote File Information..........................................................................................................174 Local File Information ..............................................................................................................174 Version Control.........................................................................................................................175 Mandatory Flag.........................................................................................................................175 Update Script File.....................................................................................................................176 Update User Program...............................................................................................................177 Switch to a Different Server ....................................................................................................177 Wildcards for Remote File Name ............................................................................................178

CipherLab 8-Series Mobile Computers (8000/8200/8300/8400/8500/8600/8700) enables users to develop the custom templates that work with the AG runtime preloaded on the mobile computers. Users are in the position to define their own application templates on any desktop computer without writing any program code. FORGE Batch Application Generator develops the templates for various applications such as the following:  Receiving in Retail  Price Check  Product labeling & Tracking  Shelf Product Replenishment  Mobile Point of Sale (POS)  Mobile Inventory Management  Order Picking & Staging  Work-In-Process Tracking  Material Flow Control  Transportation & Distribution  Warehousing  Asset Management FORGE Batch Application Generator simulates the program’s running sequences on the actual mobile computer and allows you to design a new application template on your personal computer in minutes. Offload the application template you have designed and your lookup file(s) to the mobile computer so the data collection can commence immediately. This manual provides users with a comprehensive guide to FORGE Batch AG for 8-Series Mobile Computers by relating the approaches while interspersing the examples for various applications. We recommend that you read the document thoroughly before use and keep it at hand for quick reference. Thank you for choosing CipherLab products! INTRODUCTION

SYSTEM REQUIREMENTS To run the program, one of the Windows operating systems is required:  Windows 2000  Windows XP  Windows Vista  Windows 7 INTENDED PURPOSE Data collection mainly consists of three elements: input (scanning or key-in), data processing, and output (or updating database). FORGE Batch Application Generator for 8000/8200/8300/8400/8500/8600/8700 Series Mobile Computers is specifically designed to deal with the sequences of data processing inside the mobile computers. The Batch AG program and runtime package can be working with a wireless mobile computer even if you don’t want to use its wireless connectivity. In particular, when you use a Bluetooth mobile computer, say 8062 or 8330, you will be able to use Bluetooth SPP for download and upload by selecting “RS-232/IrDA/USB VCOM”. FEATURES  Definition of program flow  Editing of screens and data  Managing barcode reader and RFID reader  Font size options and program localization  Simple program simulation for debugging  Password-protected user settings to prevent unauthorized user intervention  Hot key selection for tasks or user settings’ menus  Definition of system initial settings for a quick start  Easy cloning by downloading the template file  Integrated interface for downloading lookup files and uploading data  FTP client configuration for wireless mobile computers, as well as for 8200/8400 used with Ethernet Cradle

Install FORGE Batch AG for 8000/8200/8300/8400/8500/8600/8700 Series Mobile Computers from the Product CD. The Batch AG will be installed to the prompted “C:\CipherLab\Forge\Batch\” directory if you don’t change the path to somewhere else.  Shortcuts to the AG program is created and placed in Start | All Programs | CipherLab | Forge | Batch | Application Generator.  Shortcuts to the Remote Console utility is created and placed in Start | All Programs | CipherLab | Forge | Batch | Remote Console. Refer to the Remote Console user guide.  Shortcuts to the utilities are created and placed in Start | All Programs | CipherLab | Forge | Batch | Utilities. Refer to Utilities. Shortcut Name of Utility Program Name Usage Remote Console RemoteConsole.exe To receive data from the mobile computer via Remote Console utility. AG_Load AG_Load.exe To download the current application template to the mobile computer. AGX_Read AGX_Read.exe To upload the current application template from the mobile computer. Data_Read Data_Read.exe To receive data via Data_Read utility. It also synchronizes date/time on every host connection. DLookup DLookup.exe To download associated lookup file(s) to the mobile computer Prog_Load ProgLoad.exe To download the AG runtime or font file (.SHX) to the mobile computer. Simulator Simulator.exe To launch the simulator. DBF_Converter DBF_Converter.exe To convert text file into DBF file.

GETTING STARTED The 8 series mobile computer have to be preloaded with files as follows to commence data collection:  an AG runtime (U8*.SHX)  an application template (*.AGX)  some other files such as lookup files The 8 Series Batch Application Generator enables the data exchange between a mobile computer and a host computer such as your PC. The aforesaid files the mobile computer required are deliverable through such Batch AG. Please follow the instructions below to proceed. 1) Run the 8 Series Batch AG program on your PC. The work area appears as the picture shown below: DOWNLOAD AG RUNTIME 2) On the mobile computer, press [7] + [9] + [Power] simultaneously to enter System Menu. Select Load Program and then select the transmission interface to receive the AG runtime program from your computer. 3) On your PC, click Transfer | Send Program on the Batch AG menu bar to bring up the [Program download] dialog box. Configure the communication settings that are consistent with the settings on the mobile computer. Select the AG runtime program (U8*.SHX) corresponding to the specific model to send. Tree Menu Toolbar Menu Bar

installation wizard, the AG runtime programs for 8 series models can be accessed in the “C:\CipherLab\Forge\Batch\8 Series\RunTime\” directory. If not, browse to where you have installed the Batch AG. 4) Click the OK button and then your PC starts sending the selected U8*.SHX file. Note: To send a font file to the mobile computer, see Localization. DOWNLOAD APPLICATION TEMPLATES After the downloaded runtime (U8*.SHX) is set up in the mobile computer, a user’s application template (*.AGX) is further needed to enable the mobile computer to collect data. Such template carrying application menus and data collecting forms makes it possible for users to collect data and edit/manage data. In order to have an “application template” for the mobile computer, you need to customize/design one by the Batch AG on your PC. DESIGN APPLICATION TEMPLATES 5) From the menu bar of the Batch AG, click File | New or File | Open to open a new or an existing application template. An application template is composed of six groups of properties. 6) In the left pane of the Batch AG, click on the plus sign of the “Application Template” to see the drop-downs. From the drop-downs, click to start your customization of a new or a lately edited application template. Warning: The reader type information is essential for sending the template file to the mobile computer. Select Settings -> Initial -> Reader Option, and then click the Reader Type drop-down menu to specify the barcode reader type that is consistent with the reader actually integrated with the mobile computer; otherwise you will be alerted with the "wrong reader type" message.

Property Groups Descriptions Startup Configures the program sequences and customizes the user interface that are to be presented on the mobile computer. Settings Configures system settings so that they work when the mobile computer is initializing. Symbology Configures reader settings, symbologies and barcode parameters. Menu Customizes the hierarchical menus to be accessed under the main menu of the user’s application, e.g. 1. Collect Data | Menu 1 | (Menu 2) | Form 1. Lookup Configures the data structures for the lookup files to be referred to by user’s applications. Up to 3 lookup files are supported. Form A data collecting form covers multiple input fields that accept the data input by the user. It may be arranged following up a menu. For example: 1. Collect Data | (Menu 1) | Form 1. 7) When completing template customization, click File | Save or File | Save As to save the currently edited template to an .AGX file. You may run program simulation by selecting Tools | Simulator from the menu bar to verify if the program sequences meet your requirements. Refer to 7.4 Program Simulation. PROCEED TO DOWNLOAD With the application template file created, follow steps below to send it to the mobile computer: 8) Establish a proper connection between the mobile computer and the host computer such as your PC. 9) Power on the mobile computer to have the AG runtime main menu show up. 10) On the mobile computer, select the appropriate download interface by 3. Utilities | 1. Program Settings | 2. Download Program Interface. Press the Enter key to confirm. 11) Go back to the previous menu, and then select 3. Utilities | 6. Load Application. The mobile computer will enter connecting mode. 12) On your PC, run Batch AG. Select Transfer | Send Application from the menu bar. A [Download AG] dialogue box displays. Configure the transmission interface that is consistent with the download interface set on the mobile computer. Click the OK button and then the Batch AG will proceed to send the template file (*.AGX) to the mobile computer. 13) When the mobile computer finishes the download, the main menu of the new user application will display on the screen of the mobile computer.

upload/download interface, those on the mobile computer will be overwritten after the template file is sent to the mobile computer. (2) SD Card option is provided from which the 8200/8400/8600/8700 mobile computers can download template files (.AGX). The default import directory automatically created on SD card is “\AG\IMPORT”. (3) When your Batch AG is a version of 1.00.0005 or later, you are able to retrieve the template file from the mobile computer. Refer to Upload Application Template and 5.3.2 Upload .AGX. DOWNLOAD LOOKUP FILES If you have assigned a lookup file to which the application template will refer, the mobile computer needs to have that lookup file (Refer to 1.5 Lookup (File) and Chapter 3. Lookup). Follow steps below for the mobile computer to download lookup files from your PC: 14) On the mobile computer, select 3. Utilities | 8. Load Lookup File. The mobile computer enters download lookup mode. Note: If an application template doesn’t refer to any lookup file, the command 8. Load Lookup File is absent from the 3. Utilities submenu. 15) Run Batch AG on your PC, click Transfer | Send Lookup (or run the “DLookup.exe” utility). You can send up to three lookup files to the mobile computer. 16) Upon the completion of download, the main menu displays. Note: (1) Users need to resend their lookup files every time they renew the application templates even if the lookup files are the same. (2) Lookup files can be stored on the SD Card of 8200/8400/8600/8700 mobile computers. The default directory is “\AG\DBF”, which is automatically created on the SD card. Refer to 7.3 SD DBF Converter (8200/8400/8600/8700 Only). (3) Use the DBF Converter tool to convert lookup files to DBF format (.DB0) before sending them to the mobile computer. Run DBF converter by selecting Tools | DBF Converter from the menu bar of the Batch AG. In the DBF converter tool window, you can select to copy the converted lookup files either to the SRAM of the mobile computer or the directory “\AG\DBF” on the SD card inserted in the mobile computer. COLLECT & EDIT DATA 17) To collect data with the mobile computer, select 1. Collect Data from user’s application main menu on the mobile computer. 18) To edit the collected data, select the following submenus from user’s application main menu on the mobile computer – 3. Utilities | 2. Browse Data 3. Utilities | 3. Delete Data (Refer to 5.1.1 Data Manipulation.)

UPLOAD DATA To upload the data collected by the mobile computer to your PC: 19) On the mobile computer, select 2. Upload Data. The following options will be presented when lookup files are used. 　 Data file(s) 　 Lookup file(s), if any in use 　 All (one by one) 　 All (append), that is, all-in-one 20) On your PC, from the menu bar of the Batch AG, select Transfer | Direct-Link Data Transfer or Transfer | Remote Console Data Transfer. See 7.2.1 Data_Read for Direct-Link Data Transfer. Refer to the Remote Console user guide for Remote Console Data Transfer. Note: (1) Batch AG supports automatically uploading data to a host computer when the upload interface is properly configured. Once the mobile computer is seated in the cradle or connected via the RS-232 or USB Virtual COM cable, a running dot or a hourglass icon displays on the upper-right corner of the screen indicating the mobile computer is ready for auto upload. Refer to 7.2.1 Data_Read. (2) SD Card option is provided for 8200/8400/8600/8700 to store DAT files and DBF files in the SD card. The files will be saved to the default directory “\AG\EXPORT” on the SD card that is created automatically. UPLOAD APPLICATION TEMPLATES To output the mobile computer’s application template to a host computer such as your PC: 1) Establish a connection between your mobile computer and your PC. 2) For the transmission interface, make consistent settings on both your PC and the mobile computer. On the mobile computer, go by 3. Utilities | 1. Program Settings | 1. Upload Interface to configure the interface. 3) On your PC, run Batch AG. Select Transfer | Receive Application from the menu bar. The [AGX_Read] dialog box displays. Make related settings in this dialog box and fetch the application template from the mobile computer. Note: In the [AGX_Read] dialogue box, type in the password that is previously set up when the template file is created by Batch AG (version 1.00.0005 or later) on a host computer. Refer to 5.3.2 Upload .AGX 4) Once the OK button is clicked, your PC will start to receive the template file (*.AGX) from the mobile computer. 5) If your Batch AG is a version of 1.00.0005 or later, you are able to retrieve the template file from the mobile computer. Refer to 5.3.2 Upload .AGX.

translate the text on the UI of Batch AG, 2) translate the menu prompts/messages of the application template, 3) Send a font file (*.SHX) to the mobile computer. 1) to localize the user’s interface of the Batch AG 1. Go to the directory where the Batch AG is installed on your PC. Find the language folder. 2. If you haven’t selected an alternative directory when installing the Batch AG, the language folder can be found inside C:\CipherLab\Forge\Batch\8 Series. 3. In [Language] folder, save the original language file (.lng) as a new file. Open the newly saved language file with a text editor, and translate the text (the text of Batch AG’s user interface) from English into another language. 4. Run Batch AG on your PC. From the menu bar of the Batch AG, select Language to drop down the commands that present the available languages. You will see the newly saved language included in the submenu. 5. Select the new language. The user’s interface of the Batch AG shifts to the new language. 2) to re-define/translate the menu (prompts and messages) of the template file 1. The template can only be re-defined / translated in the Bath AG. 2. Run the Batch AG on your PC. In the left pane, unfold [Application Template]. Find Startup property page among the drop-downs. 3. On Startup property page, re-define or translate the menu prompts/messages of the template file. 4. Send the re-defined / translated template file (*.AGX) to the mobile computer. See Download Application Templates > Proceed to Download to send the template file to your mobile computer. 5. Restart the mobile computer to apply the new application template. Note: For 8000/8300, to apply double-byte characters such as Japanese, Chinese, etc., the menu prompts/messages of template file need to be re-defined / translated in the Form and Menu property pages by Batch AG, so that characters can display properly on the screen of the mobile computers. And note, for an input field, the elements other than menu prompts and messages can only display in alphanumeric characters. 3) Send a font file (*.SHX) to the mobile computer. A set of font files are bundled with the Batch AG to support a few languages on 8000, 8200, 8300, 8400, 8500, 8600 and 8700 models. If you haven’t selected an alternative directory when installing the Batch AG, these font files are accessible in the “C:\CipherLab\Forge\Batch\8 Series\Font Files” directory. To send a copy of the desired font file to the mobile computer:

1. On the mobile computer, press [7], [9] and [Power] simultaneously to boot the mobile computer into System Menu. Select 6. Load Program. And select a download interface. 2. Run Batch AG on your PC. From the menu bar, select Transfer | Send Program to send a desired font file (.SHX) to the mobile computer. Note: Be sure to make consistent settings for the transmission interface on both your PC and the mobile computer.

Creating template files by the Batch AG version 1.00.0008 or newer, a remote FTP server is readily available to which the mobile computer is allowed to log in and transfer files whether wirelessly through Wi-Fi or wired by Ethernet Cradle. FTP stands for File Transfer Protocol and is built on a client-server architecture. The mobile computer accesses an FTP server to carry out the following:  Update the script file  Upload or download lookup files (featuring version control)  Upload data files Note: If you don’t make FTP communication settings in the template file, you can still do it later on the mobile computer’s user application main menu. Select 3. Utilities | 1. Program Settings | 10. FTP Settings. FTP COMMUNICATION SETTINGS Run Batch AG on your PC. Select Transfer | FTP Communication Setting from the menu bar to have the [FTP Communication Setting] dialogue box: In this dialog box, make the settings one by one as detailed below: Server IP or Name Specify the IP address or the name of the FTP server. Port Specify the port number of the remote FTP server.  By default, TCP port 21 is used on the server for the control connection.

User Name Specify the user name for logging onto the remote FTP server. (64 characters maximum) Password Specify the password for logging onto the FTP server. (64 characters maximum) FTP Communication Interface Among 8-Series mobile computers, their communication with FTP servers are supported through the following interfaces: Options 8071 8200 8230 8330 8370 8400 8470 8630 8770 8790 WLAN 9 8 9 9 9 8 9 9 9 9 Ethernet Cradle 8 9 9 8 8 9 9 8 8 8

After completing the configuration of an FTP server, you need to configure which files should be copied to and from the mobile computer. From the menu bar of the Batch AG, select Transfer | FTP File Setting to bring up the [FTP File Setting] dialogue box. This dialogue box features the following settings: Download Script File Tick this checkbox to enable the mobile computer to download, from the FTP server, any update to the script file “FTP.dat”. Create a Script File (FTP.dat) Tick this checkbox to create a script file “FTP.dat” on your PC and save the other FTP-related settings into this file.  The file name “FTP.dat” is reserved for the script file. The file name must be uppercase while the file extension is lowercase. Please refer to Appendix VI Creating a Script File on how to create a script file for further details.

Data File Settings In this group box, select which data files will be uploaded to the FTP server. Instead of using the default file name “DATAF1~DATAF10”, you may change it if necessary.  The length of the file name plus the full directory path on the FTP server is maximum 255 characters.  When no directory path is specified, the data file will be uploaded to the root directory of the FTP server. Lookup File Settings Select if to download or upload any lookup files.  When a “Download” checkbox is ticked for a particular lookup file, the “Upload” checkbox is then ticked automatically. You can remove the tick if necessary. Note that there is only one set of Download and Version Control boxes for SRAM lookup file settings.  When the “Download” checkbox is selected for a particular lookup file, you may apply version control by ticking the “Version Control” checkbox if necessary. The system will show a message dialog box to prompt you whether to check the lookup file only when the lookup file is downloaded to the terminal for the first time.  The uploads will be saved in the root directory of the FTP server with file names of “DBF1.txt~DBF3.txt” respectively.  The downloads will be saved to the SRAM or SD Card in DBF format, depending on the Lookup settings.

Some of CipherLab’s 8-Series models support Wi-Fi networking. The configuration of Wi-Fi connection is necessary for the mobile computer to log in to a WLAN network. Run Batch AG on your PC. Select Transfer | WLAN Communication Setting from the menu bar. A [WLAN Communication Setting] dialogue box displays: In this dialogue box, make the following settings: Enable DHCP DHCP server is enabled by default and all settings can be obtained from it. If DHCP server is disabled, you must provide the following information —  Subnet Mask  Gateway  DNS Server  Terminal IP SSID “SSID” refers to “Service Set Identifier”, which is the name of a wireless local network (WLAN) to uniquely identify a group of wireless network devices used in a given “Service Set”. For example, you need to specify the SSID being used by the access points so that the mobile computer can associate to the access points.  SSID can be made up of 32 characters maximum. Security Authentication and encryption help provide data protection on the 802.11b/g network (802.11b/g/n for 8600). Refer to WLAN Security Settings.

WLAN SECURITY SETTINGS In order to prevent information theft, IEEE 802.11 standard has defined two authentication processes to provide Wi-Fi security. They are “Open System Authentication” (OSA) and “Shared Key Authentication (SKA)”. Make valid security settings here to enable the mobile computer to access a WLAN network. Click the Security button in the [WLAN Communication Setting] dialogue box. The [WLAN Security Setting] dialogue box displays. Make the following settings: Authentication Selects between Open System and Shared Key. Setting Remark Open System By “Open System Authentication”, any wireless device can access any WEP network and receive files that are not encrypted. When a client computer attempts to connect to a WLAN AP, it sends out an authentication request to that AP. The AP authenticates the request and the client gets to connect to the network.  “Open System Authentication” allows any device network access. If no encryption is enabled on the network, any device that has the SSID of the access point can gain access to the network. Shared Key By “Shared Key Authentication”, when a client computer attempts to connect to a WLAN AP, it sends out an authentication request to that AP. Then a

the pre-configured WEP keys takes place between the client computer and the AP. If the AP finally justifies the challenge text it decrypts, it will send back a positive response to the client computer. Then the client gets to connect to the network.  “Shared Key Authentication” requires a static WEP key configured in the mobile computer. The mobile computer’s access request can only be granted when it passed the challenge based authentication of the access point. Note: For “Shared Key Authentication”, the active WEP key is used for authentication. EAP Select it to activate the authentication of Extensible Authentication Protocol (EAP). It requires user name and password so that the mobile computer can be identified when connecting Cisco® access points. Setting Remark Identity Specify a user name. (32 characters maximum) Password Specify a password. (32 characters maximum) WEP Key Select it to apply Wired Equivalent Privacy or Wireless Encryption Protocol (WEP) for the mobile computer’s data encryption. Setting Remark Key Length Encryption type can be 64 bits (5 bytes) or 128 bits (13 bytes).  Using 64-bit encryption, the password phrase can be 5 characters long.  For 128-bit encryption, the password phrase can be 13 characters long. Key 1 ~ 4 Up to four WEP keys can be configured. Up to 5/13 characters (ASCII codes) for the WEP key can be specified in a particular key field depending on the key length you selected. Active Only one key (the active one) can be used at a time. Note: Make sure the settings are consistent with those of the devices of the wireless network to which the mobile computer is connecting, e.g. the access points.. WPA-PSK/WPA2-PSK Passphrase WPA-PSK supports to enhance security over wireless networks. It is a Pre-Shared key for authentication that requires a passphrase to access the network. The passphrase must be 8 to 63 characters (ASCII codes) to auto-generate a WEP key. If the entered passphrase falls shorter than 8 characters, a warning dialog pops up when OK button is clicked to submit changes.  For 8200/8400/8600/8700, WPA2-PSK is also supported.

REMOTE CONSOLE DATA TRANSFER Remote Console harnesses a Windows-based PC (host) to one or more mobile computers (clients) so the host is able to retrieve data files from the client(s) and exchange lookup files with them. Please see the Remote Console user guide for more details. Remote Console is capable of data connection through various interfaces, especially Local Area Network (TCP/IP). REMOTE CONSOLE SETTINGS To be able to launch Remote Console, make the following settings in Batch AG: 1) From Batch AG menu bar, select Transfer | Remote Console Setting. A Remote Console Settings dialog opens. 2) Make suitable settings by referencing the following: Setting Description Enable Remote Console Data Transfer Tick to make Remote Console available. Enable Auto Update Tick to make client mobile computer(s) auto-start outputting data to host computer once connection is up.  This item is selected by default.  To offload a lookup file to the client(s), assign the lookup file by selecting System | Rule Maintenance in the menu bar of the RemoteConsole utility. Refer to the Remote Console user guide. Server IP or Name Specify the destination Server IP or Name (8630 only) Port Specify the port number (8630 only)

1) the version info of the software, and 2) the version info of the application template file the Batch AG opens. Update the Batch AG to the latest available version on your PC to have this new support. SOFTWARE VERSION INFO When Batch AG is launched without opening any application template file, Title Bar shows information with Batch AG’s name and the software version. Without any application template opened, the software version delivered on the Title Bar agrees with the info given by clicking Help from menu bar. See also Menu Bar. APPLICATION TEMPLATE’S VERSION INFO After the Batch AG opens an application template file (*.AGX), the Title Bar shows the version info about the Batch AG that created the application template file. The screenshot below displaying an 8000 application template file created by a previous version of Batch AG software is now opened by the Batch AG. Delivers the software’s version info. The software’s version info delivered by the Help Menu.

Note when the opened application template file is too dated to carry the creator’s version info, the Title Bar shows the software’s version info. Delivers the version of the Batch AG that created the currently opened application template file.

to perform. Each menu contains a list of commands and sometimes sub-menus. For the provided tools, refer to Utilities. Menu Command Action… New Creates a new application template by selecting model name. Open Opens an existing template file. Browse where the file locates on the local disk. Save Saves the currently edited template file. Save As Saves the currently edited template file to a new one. Preference Configures how the Batch AG will act whenever it is used. Refer to Preference. Convert to 8xxx Converts the currently edited template file to another 8-series model. Refer to AGX Template Conversion. Recent File List Opens the recently opened template files. Refer to Recent File List. File Exit Quits the Batch AG. Send Program Sends an AG runtime or font file (.SHX) to the mobile computer. Send Application Sends the currently opened template file to the mobile computer. Receive Application Fetches the application template flies from the mobile computer. A password needs to be provided. Refer to Upload Application Templates and 5.3.2 Upload .AGX. Send Lookup Sends associated lookup file(s) to the mobile computer. Transfer Direct-Link Data Transfer Fetches data via Data_Read utility. It also synchronizes date/time on every host connection.

Remote Console Data Transfer Fetches data from the mobile computer via the Remote Console utility. FTP Communication Settings Assigns the IP and port number of a remote FTP server as well as the username and password for the mobile computer to log in. Refer to FTP Communication Settings. WLAN Communications Settings Specifies the wireless networking settings for 8071, 8230, 8330/8370, 8470, 8630 or 8770/8790. Refer to WLAN Communication Settings. Remote Console Settings Specifies if to enable Remote Console Data Transfer and if to enable Auto Update. FTP File Settings Specifies the files to be copied to and from the mobile computer. Refer to FTP File Settings. Simulator Launches the simulator of the mobile computer. Tools DBF Converter Converts text file to DBF format that is used on the SD card on 8200/8400/8600/8700. Language Selects a preferred language for the Batch AG’s user’s interface. Refer to Language. Help About Forge Batch AG Shows the information about the Batch AG.

open, save, save as, etc. It also includes a list of recently opened files and the Exit command to quit the Batch AG. The File menu and its commands are detailed in the following content of this section. PREFERENCE Select File | Preference from the menu bar to pop up the [Preference] dialog box, which configures how the Batch AG acts each time it is launched. The featured selections are detailed as follows. Make the settings that meet your needs. Auto pre-load the last editing file Select this item to load the last edited template file as soon as the Batch AG is run. Always on top Select this item to have the Batch AG (ForgeAG.exe) and the utilities remain on the top of any other windows opened.

AGX TEMPLATE CONVERSION This command converts the currently edited template file to a template for another 8-series model. Select File | Convert to 8xxx from the menu bar of the Batch AG to achieve the conversion. The template conversion involves the change of these 2 elements of a template:  The changes of upload/download interface.  The changes of the prompts & messages. The following table gives an account of the upload/download interface conversion between 8-series models. The table only lists models when the target device doesn’t have the same upload/download interface as the original one.

Upload Interface Download Interface Original Target Original Target Original Target Modem 8600 Ethernet Cradle RS232 Modem RS232 Modem 8200 8700 Ethernet Cradle RS232 Modem RS232 Direct-RS232 8000 Keyboard Wedge Cradle IR Direct-RS232 Cradle IR Direct-RS232 Direct-RS232 Cradle IR Cradle IR IrDA RS232 8400 Keyboard Wedge USB HID IrDA RS232 Direct-RS232 Direct-RS232 Cradle IR Cradle IR IrDA RS232 8200 Keyboard Wedge USB HID IrDA RS232 Direct-RS232 Direct-RS232 Cradle IR Cradle IR IrDA RS232 8300 8600 Keyboard Wedge USB HID IrDA RS232 Direct-RS232 8071 Keyboard Wedge Cradle IR Direct-RS232 Cradle IR Direct-RS232 Direct-RS232 Cradle IR Cradle IR IrDA RS232 8470 Keyboard Wedge USB HID IrDA RS232 Direct-RS232 Direct-RS232 Cradle IR Cradle IR IrDA RS232 8330/8370 8630 Keyboard Wedge USB HID IrDA RS232 Modem 8400 8700 Ethernet Cradle RS232 Modem RS232

Conversion between Devices Upload Interface Download Interface Original Target Original Target Original Target Modem 8400 8600 Ethernet Cradle RS232 Modem RS232 Cradle IR Cradle IR 8200 IrDA RS232 IrDA RS232 Cradle IR Cradle IR 8400 IrDA RS232 IrDA RS232 Cradle-IR Cradle-IR IrDA IrDA Modem 8500 8700 Ethernet Cradle RS232 Modem RS232 8700 8400 USB VCOM_CDC RS232 USB VCOM_CDC RS232

Prompts/Messages Conversion  The prompts of upload/download ports are reset to the defaults of the target device. Check it up on the Startup property page.  For 8500 series, after you select “Convert to 8400”, the prompt “F8:Edit F9:Del” will change over to 8400’s “F8:Edit Del:Del”.  If you convert an 8300 template file to an 8000 template file, the prompts which are considered too long will be truncated automatically. Note: For the prompts on Form property page and Menu Caption/Item Name on Menu property page, long strings will be truncated when the template file is converted from 8300 to 8000.

RECENT FILE LIST The File menu shows the recently opened templates when it is dropped down. Up to 4 recently opened template files are displayed for your quick access. The most recently opened one is placed on the top. Click File from the menu bar to see them. LANGUAGE When there is any language file (*.lng) saved into the directory where the Batch AG is installed, it will be added to the commands in the Language menu and becomes available. In the menu bar of the Batch AG, select Language and then select the language you prefer for the Batch AG’s user interface. Refer to Localization.

clicked to trigger Batch AG to take an action. Icons Command Description New Creates a new application template. Open Opens an existing application template. File path needs to be specified. Save Saves the current editing template. Send Application Sends the currently edited template file to the mobile computer. Send Lookup Sends associated lookup file(s) to the mobile computer. Get File via Direct-Link Fetches data from the mobile computer. About Shows the information about the Batch AG program. Exit Quits the Batch AG. TREE MENU In the work area of the Batch AG, a tree menu is featured in the left pane for user’s navigation through various theme-grouped property pages that enable user’s configuration for an application template.  Click on the "+" sign to expand the tree menu or the "-" sign to collapse it.  Click on an expanded item from the tree menu. The configuration it features will display on the right pane.

the data. One or more data collecting forms can be arranged in a menu, and multiple menus are definable for an application template. Forms and menus can be set to connect to each other for user’s data collecting needs. Each input field in a data collecting form will occupy one line on the screen of the mobile computer when the data collecting form is run on the mobile computer. Once all the input fields on a data collecting form are completed, the input data will be kept as a transaction record and saved into a “data file” on the mobile computer. The transaction record can be added to the lookup database that the form refers to, or directly output to a printer, etc. The Batch AG enables users to customize their own data collecting forms. To customize one of your own: Run the Batch AG on your PC. In the left pane, expand the [Application Template] tree menu. From the expanded items, select Form. You will see:  Up to 10 forms definable.  Maximum eight input fields supported by each form (12 input fields for 8600 due to the screen size). In the following content of this chapter, you will be guided to how data collecting forms are customized by the Form property pages. Chapter 1 FORM

IN THIS CHAPTER 1.1 Select a Form............................................................ 33 1.2 Properties................................................................. 33 1.3 Font ....................................................................... 40 1.4 Color Properties (8600 only)........................................ 40 1.6 Date & Time Stamp.................................................... 42 1.7 Branch ..................................................................... 43 1.8 Reset Current Form.................................................... 43 1.9 Data Type................................................................. 44 1.10 Prompt ................................................................... 56 1.11 Input Type .............................................................. 57 1.12 Minimum Length ...................................................... 57 1.13 Maximum Length ..................................................... 57 1.14 Variables/Field......................................................... 59 1.15 More ...................................................................... 62 1 2 3 5 6 7 11 12 13 8 9 14 15 4 10

1.1 SELECT A FORM  Ten forms are definable, Form 1 ~ 10. Select one to start with, usually "Form 1".  Each Form property page carries a certain amount of group boxes in the upper half for configuring attributes of a particular data collecting form, including [Properties], [Font Properties], [Lookup], [Date & Time stamp], [Branch], [Color Properties] (8600 series only), and a Reset Current Form button.  In the bottom half of the Form property page, an eight-row table (12 for 8600 series) presents. Such table is designed for users to configure settings of the eight input fields of a data collecting form respectively. 1.2 PROPERTIES [Property] group box covers the configurations labeled with Esc, Next, Record and Enable MSQI. Together they specify how a data collecting form behaves when it is run on the mobile computer. The following contents of this section will walk you through these configurations one by one. 1.2.1 ESC Click the ESC drop-down item to determine a form/menu to display when the [ESC] key is pressed to the form running on the mobile computer. Options available are:  Main Menu  Form 1 ~ 10  Menu 1 ~ 10 For the “Menu” options, refer to the Menu property page. Note: Normally, the [ESC] key is used to return to a previous form or menu. 1.2.2 NEXT Click the Next drop-down item to determine a form/menu to display when the last input field of the data collecting form is completed. Options available are:  Main Menu  Form 1 ~ 10  Menu 1 ~ 10 For the menu options, refer to the Menu property page. The mobile computer takes the action of “Next” as soon as the key value of [Enter] is sent to report the completion of the last input field. However, how [Enter] key value is produced depends on the input device that does the last data entry. See 1.11 Input Type for details. The following table summarizes how the completion of the last input field is reported to the system when the input devices are different:

Last Field Input Device Last Input Field Completion Report Reader The [Auto Enter] item in the More properties of the input field must be set to "Scan + ENTER". Refer to 1.15 More. Keypad The [Enter] key on 8000/8200/8300/8400/8500/8600/8700 models needs to be pressed. Both of the above See the two above. RFID The [Enter] key on 8300/8500/8600/8700 models needs to be pressed. All See all of the above mentioned. 1.2.3 RECORD Record configures which action to take when all the input fields of a form is completed. Options Action... Save Saves the record to a sequential data file. Update lookup Updates the lookup file associated with the form. Save & update Saves the record to a sequential data file, and updates the lookup file. Pass down Combine the data with the one of the next form or menu as a single record of data without saving. Output record Outputs the record directly to a printer through COM port instead of saving it to a file. Output screen Similar to "output record". This option outputs what is displayed on the screen such as the prompts and data collected. Save & output record Saves the record to a sequential data file and outputs it directly to a printer through COM port. Save & output screen Saves the record to a sequential data file and outputs what is displayed on the screen. Remove from lookup Removes the record from the lookup file. Save & remove Saves the record to a sequential data file and removes it from the lookup file. Note: Instead of saving all the collected data to a single data file, you may select to save the collected data for each form to separate data files on the Menu property page. By the Record item on Form property page and the Lookup data can be uploaded checkbox on Lookup property page, you can select if to upload the data file(s) or lookup file(s), or both files ("All, one by one") to a host computer. You can also select to merge them to a new file ("All, append") for the upload. See also 3.3.2 Lookup Data Can Be Uploaded.

Note: The uploaded file is a sequential file. The files retrievable from the mobile computer are:  Data file: Such “data file” is generated on the mobile computer only when you have selected "Save", "Save & update", "Save & output record", "Save & output screen", or “Save & remove” options from the Record drop-down menu.  Lookup file: A lookup file would be available on the mobile computer when you have chosen to use a lookup file for your data collection and have allowed it to be uploaded. When there is collected data on the mobile computer to be uploaded to a host computer, select 2. Upload Data from the user application main menu on the mobile computer after a connection is established between the mobile computer and your PC to follow through the uploading. Warning: If you select "output record" or "output screen" for the Record mode, 2. Upload Data on the mobile computer will become unavailable.

1.2.4 ENABLE MSQI Multiple Scan Quantity Incrementing (MSQI) enables a form to be performed repeatedly, whereupon the data collected is saved to a data file until the [ESC] key is pressed. With MSQI selected in a Form property page, the first 2 input fields of the data collecting form are set to the following status:  The 1st input field data type is set to “Text”. In the Lookup group box, the available lookup options rely on how many lookup files you have configured in the Lookup property page.  The 2nd input field data type is set to “MSQI” by which the input value increases to the next higher value (normally increases by 1) when the same barcode is continuously scanned. The initial value/text of a MSQI field is set to “0” by default. Users can click the More button to bring up the dialog box and then specify a value instead. And if the MSQI field is set to fetch any lookup value, the lookup value applies. With MSQI enabled, if you choose to use a lookup file, the input fields of the 3rd and up will become available for you to import more information from the lookup file.

By the example of the screenshot above, the data collecting process will repeat as long as you shall go on scanning barcodes. Such Form 1 also features the following:  When a barcode is repeatedly scanned, the value in the “Qty” field whose data type is set to MSQI will increase to the next higher value each time the barcode is scanned.  When you change over to scanning another barcode, the quantity starts over to accumulate for the new barcode scanned. Data for the previous barcode scanned will be saved as a transaction record. How MSQI works: 1) The input field that is set to “key field” admits a piece of data (line #1 on the screen of the mobile computer).

2) The succeeding MSQI input field fetches the corresponding lookup value as the initial quantity value (line #2 on the screen of the mobile computer). If no lookup file is assigned, the pre-defined initial value will be applied. 3) The input field set to “key field” admits the same barcode again. The value in the MSQI input field increases to the next higher value; say increasing by “1”. 4) The input field set to key field admits a different data. Repeating step 2 and step 3. Data for the previous item will be saved automatically. Take step 3 for example, data for the quantity field saved with this transaction record is the value displayed on the screen, say “3” for this case. 5) Press [ESC] to quit scanning and exit the MSQI-enabled data collecting form. Right before exit, a screen shows up to present a “TRACK” input field for your better documentation of track number. If you don’t feel the need for such “TRACK” input screen, disable it by deselecting Save Track from the key field’s Properties dialog. Click the More button of the key field to open its Properties dialog. See the screenshots below:

Properties dialog opens. Note: If there are a large number of barcodes of the same item, you may manually input the quantity to override the previous scanned quantity. Key field Click the More button to bring up the Properties dialog box. Deselect to disable “TRACK” input screen

1.3 FONT PROPERTIES In [Font Properties] group box, select between the small and large font sizes for the data colleting form. Large font is only applicable to the double-byte languages such as Chinese, Japanese, etc. For a data collecting form, configure the font size for various models as tabulated below. And see also Localization and 2.3 Font . Mobile Computer Small Font (6x8) Large Font (8x16) 8000 Series 16 characters by 8 lines (default) 12 characters by 8 lines 8300 Series 20 characters by 8 lines (default) 15 characters by 8 lines 8500 Series N/A 20 characters by 8 lines Mobile Computer Small Font (10x20) Large Font (12x24) 8600 Series 24 characters by 12 lines (default) 20 characters by 12 lines Mobile Computer Small Font (8x16) Large Font (12x16) 8200/8400/8700 Series Single-byte 20 characters by 8 lines (8x16) 13 characters by 8 lines (12x16) Mobile Computer Character Type Small Font (8x16, 16x16) Large Font (10x20, 20x20) Alphanumeric 20 characters by 8 lines (8x16) 16 characters by 7 lines (10x20) 8200/8400/8700 Series Double-byte Double-byte Language Characters 10 characters by 8 lines (16x16) 8 characters by 7 lines (20x20) Note: The [Font Properties] group box isn’t available on the Form/Menu property pages for 8500 templates which can only display information in small font size. 1.4 COLOR PROPERTIES (8600 ONLY) This group box is available only for 8600 series. Click the drop-down menus to determine background & foreground colors of the form for 8600 mobile computer.

1.5 LOOKUP (FILE) In [Lookup] group box of a form, select if the data collecting form should refer to a lookup file, i.e. a database array, so that when that form runs on the mobile computer, it is able to fetch values from that lookup file. To refer to one or more lookup files listed in the [Lookup] group box, you need to provide further details about the data structure of the lookup file(s) in the Lookup property page. See Chapter 3. Lookup for details. A lookup file is a database. Select whether or not a lookup file is associated with the form. If a lookup file is used, its data format must be defined on the Lookup property page. Note: The associated lookup file(s) must be duplicated to the mobile computer as well. For a data collecting form, as long as a lookup file is assigned in the [Lookup] group box, the “Lookup” option of Data Type and the Field item will be activated for the input fields. See 1.9.8 Lookup and 1.14.1 Field for more details.

1.6 DATE & TIME STAMP The [Date & Time Stamp] group box encloses a set of options that control affixing date/time info to a form’s transaction entry. By and large, the date/time info helps you with better analysis of the collected data. Options provided are [No Time Stamp], [Add to front of record], and [Append to end of record]. [No Time Stamp] is selected by default, which means the software disables the date/time info if users don’t select an alternative. Writing date/time info to lookup files relies on the data types [Date] and [Time]. Update your Batch AG (for the host) and the AG Runtime (for the mobile computer) to the latest version available to get your hands on the support (except 8500). See 1.9.16 Date and 1.9.17 Time for more details.  Stamp Position [Add to front of record] and [Append to end of record] set whether the date/time info appear to the left or right of a transaction entry. The comma “,” is the default character that separates the date info and time info.  Date & Time Format When the Date/Time stamp is enabled, the [Date & Time Format] button becomes available. Click it to pop up the [Date & Time Stamp settings] window to define the appearance you want for the date/time info in the data file. All options on the [Date & Time Stamp settings] window are selected by default. Deselect one to disable a piece of date/time info element.

1.7 BRANCH On 8-series mobile computers, a data collecting form is usually followed by either another form or menu. The [Branch] group box features the options required for a data collecting form that is designed to lead to more than one other form. It also configures the keypad shortcut for the mobile computer to switch between the forms and menus. Up to four shortcuts can be configured. Take the following illustration for example. Note: Data cannot be passed down through branches. 1.8 RESET CURRENT FORM The “Resent Current Form” button brings the current form back to default state when it is clicked.

1.9 DATA TYPE A datagrid at the bottom half of a form page configures the elements of the input fields in a data collecting form. Every row constitutes an input field while each column represents an element of an input field that needs to be configured. The available selections for input data type: Data Type Prompt Input Source Length Lookup Properties on-screen saved in record Min / Max Field More... Nil Text 9 9 9 9 9

Integer 9 9 9 9 9 Real 9 9 9 9 9 Letter 9 9 9 9 9 Auto (+/-) 9 9 9 9 9 Boolean 9 9 9 9 Lookup 9 User-definable 9 9 Fixed data 9 9 9 Prompt 9 Counter 9 Pass down 9 Extension Pause 9 Alphameric 9 9 9 9 9 Read from 2D 9 9 9 Date 9 9 Time 9 9 Serial 9 Large data 9 9 9 9 GPS Latitude 9 9 GPS Longitude 9 9 The following contents of this section will walk you through all the data types supported for an input field in a data collecting form. 1.9.1 NIL When “Nil” is set to the data type of an input field, the input field doesn’t accept any data whatever the format is.  “Nil” is the default setting. An input field set to “Nil” in a data collecting form would present a totally blank area (line) on the screen of the mobile computer.

1.9.2 TEXT When “Text” is set to the data type of an input field, the input field accepts any ASCII character. For example, $1a2b3c=-*/… 1.9.3 INTEGER When “Integer” is set to the data type of an input field, the input field accepts the whole numbers such as … -2, -1, 0, 1, 2 … but not 3.5. 1.9.4 REAL When “Real” is set to the data type of an input field, the input field accepts any number that features a decimal whether it is rational or irrational. For example, 4.56. The following contents of this section will describe how a data collecting form interacts with the specified lookup file when either “Real” or “Integer” is selected as the “Data Type” for an input field.

 In a data collecting form that refers to a lookup file, when an input field is set to integer/real and associated with a certain lookup field (by the “Field” element), it will first fetch the value in the associated lookup file when the data collecting form runs on the mobile computer. However, you can choose to ignore such fetched value and input your data into the input field.  In the case you choose to input your own data, if the Record mode of the data collecting form is set to “Save & Update”, the value you input will trigger different arithmetic performed to the lookup values depending on the “Field” element setting. The following table summarizes the arithmetic performed: Field Setting (Lookup File) Arithmetic Performed Field 1 ~ 8 The input value will overwrite the associated lookup value. No arithmetic would be performed. +Field 1 ~ 8 The value you input will be added to the value in the associated lookup field automatically. - Field 1 ~ 8 The value you input will be deducted from the value in the associated lookup field automatically. Hereunder is an example: The input field first fetches the associated lookup value, say “4000”. You can proceed to input your own data, say “5”. By this example, when different “Field” element is set, the arithmetic performed would be: “Field” Setting Arithmetic performed field (no arithmetic sign) If you input “5”, the value “5” will be saved in the transaction record on the mobile computer and overwrite the value in the associated field of the specified lookup file. The value saved in the lookup file will be “5”. You can check the updated lookup file by selecting 3. Utilities | 2. Browse Data from the user application main menu. +field (with a plus sign) If you input “5”, the value “5” will be saved in the transaction record on the mobile computer, and 5 will be added to the associated lookup value. The value saved into the lookup file will be 4005. You can check the updated lookup file by selecting 3. Utilities | 2. Browse Data from the user application main menu. -field (with a minus sign) If you input 5, the value “-5” will be saved in the transaction record on the mobile computer, and 5 will be deducted from the value in the associated field of the specified lookup file. The value saved into the lookup file will be 3995. You can check the updated lookup file by selecting 3. Utilities | 2. Browse Data from the user application main menu.

1.9.5 LETTER When “Letter” is set to the data type of an input field, the input field accepts any letter, either upper or lower case (from Aa to Zz). 1.9.6 AUTO (+/-) When “Auto (+/-)” is set as the data type of an input field, it produces similar arithmetic as the “Integer” or “Real” does when a lookup file is specified. However, “Auto (+/-)” distinguishes from “Integer” and “Real” by showing the lookup value ahead of the input field. Depending on the “Field” element setting, a plus sign (+) or a minus sign (-) will display ahead of the input field. Similar to “Integer” and “Real”, for an input field set to “Auto (+/-)”, when you input your data, the arithmetic performed differs by the “Field” setting. The following example shows the arithmetic performed when different “Field” element is set: “Field” Setting Arithmetic Performed field (no sign) If input value is 5, the value saved in transaction record is 5, and the value saved to the lookup file is 5 too. +field If input value is 5, the value saved in transaction record is 5, and the value saved to the lookup file is 1005. -field If input value is 5, the value saved in transaction record is -5, and the value saved to the lookup file is 995.

1.9.7 BOOLEAN When “Boolean” is set to the data type of an input field, the input field accepts only one of the following sets: "0 or 1", "Y or N" and "T or F". If you input any value other than the above, a message will display on the mobile computer indicating "Data type is wrong!" 1.9.8 LOOKUP When “Lookup” is set to the data type of an input field, the input field doesn’t accept data input but fetches the associated lookup value. “Lookup” data type is particularly applicable to the case as exemplified below: An input field #2 is preceded by an input field #1 that contains the data matching the "key field", i.e. the “indexed” field, of the associated lookup file. Then the input field #2 will fetch the value in the corresponding field in that lookup file. Note: By default the fetched lookup value won’t be saved into the transaction record unless you enable “Save field data” in the advance property page (by clicking the More button). See 1.15 More for details. Note: The lookup value is fetched for reference. No change is allowed.

1.9.9 FIXED DATA When “Fixed Data” is set to the data type of an input field, the line it occupies on the screen of the mobile computer doesn’t accept data input but shows a pre-defined data string to the data collectors and needs to be included into the data file. Define the data string in the “Prompt” element setting.  “Fixed Data” will be saved as part of the transaction record. 1.9.10 PROMPT When “Prompt” is set to the data type of an input field, the line it occupies on the screen of the mobile computer doesn’t accept data input but shows a pre-defined prompt string on the screen of the mobile computer. Define the prompt string in the “Prompt” element setting.  It distinguishes “Prompt” from “Fixed Data” that “Prompt” won’t be saved as part of the transaction record. 1.9.11 COUNTER When “Counter” is set to the data type of an input field, the line it occupies on the screen of the mobile computer doesn’t accept data input but registers the count of user’s data collecting process. It counts each time the “Counter” field is executed. Normally, the record count starts from 0000000 (7 digits for 8000, 8200, 8300, 8400, 8600, and 8700 but only 5 digits for 8500). However, when a menu is arranged before a form, and you have configured to save the menu caption, the count will start from “1” instead of “0”. To save the count record to the data file, click the “More” button of the input field for the advanced settings. You may find the record count in other places:  The record count also displays at the bottom of user’s application main menu (next to date and time).  The record count also displays upon the completion of data input. Refer to 5.1.1 Data Manipulation for “Entry Options”. 8000 For 8000, when a field (a line on the screen of the mobile computer) is set to show counter, the current count will be saved and displays in the format of seven digits starting from 0000000. However, due to the space constraint, the counter displaying in user application main menu would appear slightly different from the one in a field of a data collecting form and in the data file. The following example shows what difference it makes: Record Count Range: 0000 ~ 9999 Record Count Range: 10000 ~ 99999 Record Count Range: >0000 ~ (= 100000 ~)

8200 For 8200, when a field (a line on the screen of the mobile computer) is set to show counter, the current count will be saved and displayed in the format of seven digits starting from 0000000. The counter is displayed on the user application main menu as the picture shown below: 8300 For 8300, when a field (a line on the screen of the mobile computer) is set to show counter, the current count will be saved and displayed in the format of seven digits starting from 0000000. The counter is displayed on the user application main menu as the picture shown below: 8400 For 8400, when a field (a line on the screen of the mobile computer) is set to show counter, the current record count will be saved and displayed in the format of seven digits, starting from 0000000. The counter is displayed on the user application main menu as the picture shown below:

8500 For 8500, when a field (a line on the screen of the mobile computer) is set to show counter, the current record count will be saved and displayed in the format of five digits, starting from 00000. The counter is displayed on the user application main menu as the picture shown below: 8600 For 8600, when a field (a line on the screen of the mobile computer) is set to show counter, the record count is saved and displayed by seven digits, starting from 0000000. The counter is displayed on the user application main menu as the picture shown below: 8700 For 8700, when a field (a line on the screen of the mobile computer) is set to show counter, the record count is saved and displayed by seven digits, starting from 0000000. The counter is displayed on the user application main menu as the picture shown below:

1.9.12 PASSDOWN When “Passdown” is set to the data type of an input field, the input field doesn’t admit manual data input but imports the data collected by the previous form that is set to “Pass down” for the Record mode.  When one line isn’t enough to display the imported data, the input field needs one or more input fields succeeding it set to "Extension".  A “Pass down” input field also imports the data from a menu. See also 2.5.3 Pass Down. Note: An input field set to “Pass down” is able to combine the data collected by multiple preceding forms to one record. 1.9.13 EXTENSION When “Extension” is set to the data type of an input field, the input field doesn’t accept data input but reserves field space for an input field above it that is so extended as to require additional field space of a second input field to completely display on the screen of the mobile computer. Note: How many extension fields are required depends on the maximum length of your data and the screen size of the mobile computer. Taking a mobile computer with the screen that allows 20 small-font characters per line for example:  Now the prompt string ("Description_:" in line 2) takes up the space of 13 characters, and the data length is maximum 15 characters…  Together they make the length reaching 28 characters, which requires the field space of more than one line.  As a result, the data type of line 3 needs to be set to "Extension" if you want to fully display the input data. Description_:1234567 890ABCDE Max. 20 Characters Max. 8 Lines 13 characters 15 characters

1.9.14 PAUSE When “Pause” is set to the data type of an input field, the line it occupies on the screen of the mobile computer doesn’t accept data input but shows an alert string to call the attention of the data collectors to something. Define the alert string in the “Prompt” element setting.  The prompt string will not be saved. However, it will be highlighted and blink constantly on the mobile computer. 1.9.15 ALPHAMERIC When “Alphameric” is set to the data type of an input field, the input field accepts any alphabetic, numeric, or alphanumeric characters. For example, ABC123xyz. 1.9.16 DATE The “Data Type” starts to support date info. Update both the Batch AG on your PC and the AG Runtime on the mobile computer to the latest version available to have this new feature – the data type “Date”. Note 8500 isn’t supported presently. The data type “Date” depends on the mercy of the “Date & Time stamp” settings. Disable the “Date & Time stamp” to have the “Date” listed in the “Data Type” selections. Likewise, selecting “Date” data type leaves the “Date & Time stamp” settings unavailable. When “Date” is set to the data type of an input field, the line it occupies on the mobile computer’s screen doesn’t accept data input but imports date info. The date info is saved into a form’s transaction entry and stored in the data file. To further write the date info into lookup files, set the Record mode of a form to “Save & update”. (See also 1.2.3 Record.) Note a corresponding field must be assigned for the lookup file to admit the time info. A More button is available to set whether the date info shows on the mobile computer’s screen and how it manifests itself (the output format). 1.9.17 TIME The “Data Type” starts to support time info. Update both the Batch AG on your PC and the AG Runtime on the mobile computer to the latest version available to have this new feature – the data type “Time”. Note 8500 isn’t supported presently. The data type “Time” depends on the mercy of the “Date & Time stamp” settings. Disable the “Date & Time stamp” to have the “Time” listed in the “Data Type” selections. Likewise, selecting “Time” data type leaves the “Date & Time stamp” settings unavailable.

When “Time” is set to the data type of an input field, the line it occupies on the mobile computer’s screen doesn’t accept data input but imports time info, with time resolution configurable down to seconds granularity. The time info is saved into a form’s transaction entry and stored in the data file. To further write the time info into lookup files, set the Record mode of a form to “Save & update” (See also 1.2.3 Record.). Note a corresponding field must be assigned for the lookup file to admit the time info. A More button is available to set whether the time info shows on the mobile computer’s screen and how it manifests itself (its output format). 1.9.18 SERIAL This data type is used to keep information with the serial number of a particular terminal, indicating the data record was created by some terminal according to the serial number. 1.9.19 LARGE DATA When an input field is set to “Large Data”, it accepts data of maximum 2048 characters collected by 2D scan engines. This data type is only available when the reader type is set to 2D reader for 8200, 8400, 8500 and 8700 mobile computers by the “Initial” page under “Setting” property page. Refer to 5.1.4 Reader Option.  Each form can have one input field set to read large data.  The maximum field length is set to 160 characters by default. To extend the field length up to 2048 characters, you need to manually configure the “Max. Length” setting.  Note, for “Large Data”, the “Read partial barcode” is enabled by default whereby only a short piece of the scanned barcode will be read, from the 1st character to the 20th character by default. If you need the whole extended data to be read, be sure to disable “Read partial barcode” in the advanced setting of the input field. Click the “More” button of an input field to pop up a [Properties] dialogue box. See 1.15.2 Barcode Input. Note: The setting of “Variable” / “Field” element isn’t available when both of the conditions are met: (1) More than 160 characters are set for the maximum field length, and (2) the “Read partial barcode” is disabled.

1.9.20 READ FROM 2D “Read from 2D” data type is available only when the following conditions are met: (1) 2D scan engine is selected for 8200/8400/8700 mobile computers, and (2) one of the preceding input fields is set to “Large data”. When “Read from 2D” is set to the data type of an input field, the line it occupies on the screen of the mobile computer doesn’t accept data input but displays a short piece extracted from the preceding “Large Data” field.  For each data collecting form, after having set one input field to “Large Data”, you can set as many input fields to “Read from 2D” as you need.  “Read from 2D” supports to extract a partial piece reaching up to 160 characters from the extended data in the preceding “Large Data” field. Refer to 1.15.2 Barcode Input. 1.9.21 GPS LATITUDE (8600 ONLY) When “GPS Latitude” is set to the data type of an input field, the line it occupies on the mobile computer’s screen doesn’t accept data input but gets the latitude coordinates where the mobile computer is. The latitude info is saved into a form’s transaction entry and stored in the data file. 1.9.22 GPS LONGITUDE (8600 ONLY) When “GPS Longitude” is set to the data type of an input field, the line it occupies on the mobile computer’s screen doesn’t accept data input but gets the longitude coordinates where the mobile computer is. The longitude info is saved into a form’s transaction entry and stored in the data file. 1.10 PROMPT “Prompt” is the label or the name of an input field. Specify a prompt string for an input field, if necessary. Note: Prompt strings won’t be saved in a transaction record except for "Fixed Data".

1.11 INPUT TYPE The “Input Type” configures the source that data is collected from. Depending on the models of the mobile computer, the options available are:  Reader  Keypad  Both  RFID (only applicable to 8300, 8500, 8600, 8700 Series)  All (only applicable to 8300, 8500, 8600, 8700 Series) After the required information is entered into one input field, it takes to press the [Enter] key on the mobile computer to complete the input field. Then the cursor will move either to the next input field, or to the next form or menu. When "Reader" is selected for the “Input Type”, you need to enable "Auto Enter" in the input field property by clicking the More button. See 1.15 More. Note: When "RFID" is selected, you may still press the [ESC] or [Enter] key on the mobile computer to cancel or confirm a task. However, the other keys on the keypad won’t work. 1.12 MINIMUM LENGTH The “Min Length” specifies the minimum length of the input data.  If the input data is shorter than specified, it is considered unacceptable. A warning message will display indicating "Data is too short!" 1.13 MAXIMUM LENGTH The “Max Length” specifies the maximum length of the data input. 8000/8300 allow maximum 80 characters, 8200/8400/8500/8700 up to 160 while 8600 up to 240.  When the form refers to a lookup file, “Max Length” specified here will be compared with the length setting specified in the lookup file. If “Max Length” exceeds the length specified in lookup, it is changed to be equal to the lookup field length. You can facilitate data input by showing input marks in the input field. Click the More button to pop up the [Properties] dialog box. In [Field data] group box, tick the “Show input mark” checkbox and assign a mark or symbol. The input field will be highlighted by a succession of the assigned input mark that is equally long as the maximum length specified.  If the input data is longer than specified maximum, it is considered unacceptable.

1.13.1 INPUT VIA BARCODE/RFID READER For the data input from the barcode or RFID reader, a warning message will display when the data is too long. 1.13.2 INPUT VIA KEYPAD As long as the length falls within the scope specified, a data input by the keypad is always acceptable even if it is longer than the screen can display. Taking the scenario below for example, when:  the screen of the mobile computer displays 20 characters per line for small font, and  the prompt string configured takes up 12 characters. The transaction between the data input, the on-screen indication and the record saved would be in the relationship as tabulated below: Line Input from Keypad Screen Reading Transaction Record 12345678 12345678 12345678 1234567890 34567890 1234567890 #1 1234567890ABCDE 3456789E 123456789E #3, 4 1234567890A 123456789A 123456789A #5, 6 1234567890LEMONADE 1234567890LEMOE 1234567890LEMOE #7, 8 1234567890ORANGE_JUICE 1234567890ORANGE_JUICE 1234567890ORANGE_JUICE

1.14 VARIABLES/FIELD “Variables” / “Field” are both the elements of an input field that decides whether the input field should admit a data read or import some other data. “Variables” and “Field” are exclusive against each other. When a data collecting form refers to a lookup file, the element available is “Field” while otherwise “Variables”. Refer to 1.5 Lookup (File).

1.14.1 FIELD “Field” element is only available when the data collecting form is set to refer to a lookup file. For “Field” element, you set an input field to either admit the data read or fetch lookup value. A lookup file usually contains a list of key fields (i.e. the indexed fields) and other associated fields. Normally, the "key field" is kept as Field #1. When an input field refers to the key field and finds its data matching, the following input fields will proceed to import the data from the remaining associated fields of that lookup file. The following screenshots show you the “Field” options available when the input data type is selected as Integer/Real/Auto(+/-), or otherwise:  For the input data types other than Integer, Real, and Auto (+/-), see left below.  For the input data types of Integer, Real, and Auto (+/-), see right below. Note: For the field options with a prefixed arithmetic sign (+, -), the input data will be added or deducted from the lookup value. Lookup Field for data type: integer, real, auto (+/-) Lookup Field for data type other than integer, real, auto (+/-)

1.14.2 VARIABLES “Variables” element is only available when the data collecting form isn’t referring to any lookup file. For “Variables” element, you set an input field to either admit the data read or fetch some other data collected by the proceeding form. The following describes how “Variables” function:  When an input field is set to “set V1”, the data admitted can be fetched by an input field set to “get V1” in the succeeding form.  When an input field is set to “get V1”, it fetches the value in the input field set to “set V1” in the direct preceding form.  When an input field is set to “get&set V1”, it fetches the value from an input field set to “set V1” in the preceding form and sets the fetched value to the new variable that is to be fetched by the succeeding from. This selection is applicable when a data needs to pass over to the next form. Examples:  Select “set v1” for input field #1 of form 1, and its input data will be saved in the first character array.  Select “get v1” for input field #3 of form 2, it will fetch the data in field #1 of form 1 automatically.  Select “get&set v1” for input field #3 of form 2, it will fetch the data in field #1 of form 1 and is set to a new variable that can be fetched by the direct succeeding form.

1.15 MORE To every data collecting form, every input field features a “More” button by which the advance settings of the input field is possible. Click the “More” button of an input field to pop up a [Properties] dialogue box as below:

1.15.1 FIELD DATA The [Field Data] group box features the following configuration: Fixed Data Length Select this item and enter a value to confine the data length within the specified value.  If the input data is longer than specified, it will be truncated and saved to transaction record. When the data is browsed on the mobile computer, it would display in a truncated manner.  If the input data is shorter than specified, "space" or "0" can be selected to add ahead or after the data based on either "Left" or "Right" alignment. Below are some examples: Fixed data length Alignment Input data Transaction record 4 Left aligned / space 123456789 1234 4 Right aligned / space 123456789 6789 10 Left aligned / 0 7654321 7654321000 10 Right aligned / 0 7654321 0007654321 Initial Value or Text Select this item and enter a value or text that is up to 9 characters to have it show in the input field on the screen of the mobile computer. Such value or text will be replaced by the data input. It functions to provide the prompt of an initial value of quantity for example. Note: When an input data is set to a “variable” for the following data collecting form to fetch, the Initial Value/Text won’t be available. Add Prefix Code Select this item to prefix the input data with a code. Click the text box to pop up a [Grid Control] dialogue box. Select one or more codes from the ASCII codes presented. For example, a dollar sign ("$") can be added ahead of the data input for price. Add Suffix Code Select this item to suffix the input data with a code. Click the text box to pop up a [Grid Control] dialogue box. Select one or more codes from the ASCII codes presented. Next to delimiters (section 6.4 Data Field Properties), prefix and/or suffix codes can also function to separate each data piece. Note: You may use prefix/suffix code to enclose the input data. Show Input Mark Select this item and enter a specific mark or symbol, such as underline (_) or asterisk (*), into the text box. Such mark or symbol will show in a succession to highlight the input field. However as soon as any data is input, such mark/symbol succession will be replaced by the data. The number of input marks shown on the screen equals to the maximum length of data specified in 1.13 Maximum Length.

Decimal Places This drop-down menu is available only when the Data Type field is set to Real. “Decimal places” defines how many decimal digits after the decimal point.  The “Decimal places” is set to variable by default meaning any real numbers are acceptable. When “Decimal places” is set to ‘4’, for example, and the data input has only 2 decimal places like "8.12", the system will save the input data as "8.1200". If you try to input a number "8.12345" via the keypad, the fifth decimal digit will be discarded. Only "8.1234" is considered acceptable and saved to file. If the barcode "8.12345" is scanned via the barcode reader, a warning message “Incorrect decimal input” will display on the screen of the mobile computer, and the system will automatically clear the input data and wait for new entry. Decimal Symbol This drop-down menu is available only when the Data Type field is set to Real. “Decimal symbol” allows users to designate ‘,’ or ‘.’ as the decimal point symbol.  The “Decimal symbol” is set to ‘.’ by default. Compare This function is available only when the Data Type field is set to Integer or Real. Tick the “Compare” checkbox to enable the “Comparison Operators Settings” button and then click the button to bring up the settings window. With this comparison function enabled, the field value will be compared with the comparison condition (If the form refers to a lookup file, the field value comes from the lookup file). You can determine the behaviour in reaction to results not matched, by selecting the radio buttons as follows:  Show warning message: Show message for notification. The scanned data will be discarded.  Insert data: The scanned data will be inserted.  Show warning message & Insert data: Show message for notification and the scanned data will also be inserted.

1.15.2 BARCODE INPUT The [Barcode Input] group box features the following configuration: Trim leading specified Here you can specify one character to be removed that matches the leading character(s) of the barcode. For example, if it is specified to remove the character “0”, one or more zeros will be stripped off the barcode data “012345” and “00012345”. However, for barcode data “010333”, only the first zero will be stripped off. Note that if the specified character can’t be located in the starting position, the data will be kept unchanged. Examples: Original Data Specified character(s) to be removed Data with specified character(s) removed 012345 0 12345 0012345 0 12345 010333 0 10333 100330 0 100330 (unchanged) Read Partial Barcode To collect only a short piece of the barcode scanned, select this item and configure which character to start with and how long the data should be. Examples: Start position Max. length Barcode scanned Transaction record 2 10 9876543210 876543210 2 3 9876543210 876 Check Leading Code Select this item to enable the check against the leading characters of a barcode scanned. When the leading characters don’t match the specified code (up to 6 characters), the barcode will be rejected. Examples: Leading code Barcode scanned Transaction record 9 9876543210 9876543210 2 9876543210 (Error message: Wrong leading code!) 98765 9876543210 9876543210 978 9876543210 (Error message: Wrong leading code!) When “Read partial code” and “Check leading code” are both enabled: Start position Max. length Leading Code Barcode scanned Transaction record

2 7 8 9876543210 8765432 2 7 9 9876543210 (Error message: Wrong leading code!) Check Digit Verification The “check digit” refers to the digit at the end of a barcode derived from a simple formula to validate the barcode scanned. Select this item to enable the check against the barcode’s check digit. From the drop-down menu, select one formula for the checksum examination. Modulus 10 and 11 are available. When the check digit isn’t validated, the barcode scanned will be rejected. Auto ENTER Normally, [Enter] key needs to be pressed on the mobile computer to complete one input field, so that the on-screen cursor will proceed to the next input field, or the next form/menu configured. From the drop-down menu, select if to trigger a carriage return before or after the barcode is scanned, or simply to trigger a carriage return without scanning.  For barcode scanning, it proves to save time when Scan+ENTER is enabled.  For a typical application of continuous scanning, it is efficient by making use of ENTER+Scan.  For a specific field that users want to skip over.

computer to collect data. With Batch AG, up to ten menus are definable. Forms and menus can be set to connect to each other for user’s data collecting needs. A “Menu” property page covers the settings as the picture shown below: In the following contents of this chapter, you will be guided to how menus can be defined through the Menu property pages. IN THIS CHAPTER 2.1 Select a Menu ........................................................... 68 2.2 Properties................................................................. 68 2.3 Font ....................................................................... 68 2.4 Color Properties (8600 only)........................................ 69 2.5 Data ........................................................................ 69 2.6 Separate Each Data File and Edit Form Name................. 69 2.7 Item Name ............................................................... 70 2.8 Next ........................................................................ 70 2.9 Reset Current Menu ................................................... 70 Chapter 2 MENU 1 2 5 7 3 4 8 9 6

2.1 SELECT A MENU  Menu 1~10 are available. Select one to start with, usually "Menu 1".  Each Menu carries these group boxes: the [Properties], [Font Properties], [Color Properties] (8600 only), [Data], a command name editing table, a checkbox to enable the Edit Form Name button, and a Reset Current Menu button. 2.2 PROPERTIES [Property] group box features the settings of Menu caption and Esc. The former specifies the title of the menu while Esc configures the data collecting form or any other menu to succeed the menu. In the following content of this section, you will be walked through said settings one by one. 2.2.1 MENU CAPTION Select “Menu Caption” to be able to specify a title for the menu if necessary. 2.2.2 ESC Select a form or menu to display when the [ESC] key is pressed to the menu. Options available are:  Main Menu  Form 1 ~ 10  Menu 1 ~ 10 Note: Normally, the [ESC] key is used to return to a previous form or menu. 2.3 FONT PROPERTIES Large font is only applicable to the double-byte languages such as Chinese, Japanese, etc. For a menu, font size needs to be configured according to the font in use on the mobile computer. Refer to Localization and 1.3 Font .

2.4 COLOR PROPERTIES (8600 ONLY) Click the drop-down menus to determine background & foreground colors of the menu for 8600 mobile computer. 2.5 DATA [Data] group box features a few actions for the mobile computer to take when the menu is selected on the mobile computer 2.5.1 SAVE CAPTION Select “Save Caption” to save the menu caption to the transaction record as long as the menu is selected and run. 2.5.2 SAVE SELECTED ITEM Select “Save Selected Item” to save the name of the selected item to the transaction record. 2.5.3 PASS DOWN As long as either of the aforesaid items is selected, the option “Pass Down” would become available. Select if to pass the enabled information to the next form or to affix the enabled information to a transaction record entry. By the options in the [Data] group box, the combinations available are:  Save caption & pass down  Save selected item & pass down  Save both & pass down Note: The selected data will be passed down to an associated form or menu. 2.6 SEPARATE EACH DATA FILE AND EDIT FORM NAME When a menu leads to more than one form, select this item to save the data collected from each form to individual data files. As soon as this item is selected, the "Pass down" in [Data] group box is selected automatically, which means the menu caption and/or the selected item name will be affixed to each transaction data entry and saved into the data file of the due form.

2.7 ITEM NAME In the upper right of the Menu property page, there is a table that can configure up to ten items for a menu. Each row in this table sets up a menu item that will occupy one line on the screen of the mobile computer while each column configures an element of a menu item. For the “Item Name” setting, specify the names of the items to be featured by the menu. For example, you may specify "1. Goods In" or simply "Goods In" as the first item name (See below). Note: Whether you have included a number in an item or not, you can press [1] on the mobile computer to enter the first menu item, say the "Goods In" menu as exemplified by the screenshot above. 2.8 NEXT For the “Next” setting, sets a menu or a form for the menu item to lead to when the menu item is selected. Options available are:  Main Menu  Form 1 ~ 10  Menu 1 ~ 10 The selection of an item is executed by one of the following operations performed on the mobile computer -  Press the shortcut key (Item No.) of a menu item, e.g. press [2] to select the second menu item. The form or menu you specified here in the “Next” element column will display.  Press the navigation keys [Up/Down] to move between the menu items, and press [Enter] to select it. 2.9 RESET CURRENT MENU Click the “Reset Current Menu” button to load the default settings. Note: The settings of current menu will be cleared. Caption Item Name

supported by the mobile computer and definable with the Batch AG. If the settings on a Lookup property page are improperly made, it may go wrong when an input field of a form refers to a lookup field. The Lookup property page makes it possible for users to provide information about data structure of the lookup file(s) they are going to use and to configure the related parameters. Therefore, to collect data with the help of lookup file(s), the following settings are needed in addition to the “Lookup” property page:  The [Lookup] group box featured on the Form property page. See 1.5 Lookup (File).  The setting of “Data Type” of an input field on the Form property page. See 1.9.8 Lookup (Data Type).  The setting of the “Field” element of an input field on the Form property page. See 1.14.1 Field. Users need to apply an application template that refers to lookup files to be able to send the lookup files to the mobile computer; otherwise the command 3. Utilities | 8. Load Lookup File will be absent from the user application main menu. Chapter 3 LOOKUP 1 2 8 9 3 5 6 7 4

IN THIS CHAPTER 3.1 Select a Lookup File ................................................... 73 3.2 Field Property............................................................ 73 3.3 Lookup Data ............................................................. 76 3.4 Action When the Input Data Has No Match .................... 77 3.5 Offset ...................................................................... 79 3.6 Length ..................................................................... 79 3.7 Key Field .................................................................. 79 3.8 Action When Record Format Is Wrong........................... 80 3.9 Reset Current Lookup File ........................................... 82

3.1 SELECT A LOOKUP FILE Up to 3 lookup files are definable. Select one to start with, usually the “1st Lookup File”. Each Lookup property page carries these elements: the group boxes [Field property], [Lookup data], [Action when input data no match], [Action when record format is wrong] and a table that enables users to provide the data structure of their lookup file(s). In the following contents of this chapter, you will be walked through the said elements one by one: 3.2 FIELD PROPERTY [Field property] group box features the settings of “Number of fields”, “Fixed length”, “Delimiter” and “DBF file location”. Together with the data structure table, users are able to provide the information about the data structure of their lookup file(s) at hand. 3.2.1 NUMBER OF FIELDS In the “Number of fields” box, configure the number of fields in the lookup file you are using. Set a number up to eight (up to 12 for 8600) that is no smaller than the lookup file’s actual field amount. Refer to 1.14.1 Field. 3.2.2 FIXED LENGTH Fixed Length is the default setting. When Fixed Length is selected, users are able to define the length of the information pieces in a lookup file, so that a data collecting form is able to look up in a database that has no express matrix or grid structure. The following settings are necessary:  Number of fields  Offset  Length 3.2.3 DELIMITER “Delimiter” setting lets users to define an ASCII character to separate the data fields. Proceed to define related settings as follows:  Number of fields  Max. Length If the maximum length of each field is set improperly, you will receive a warning message when the mobile computer is downloading the lookup file. Whether the download will fail or not depends on the action you want the mobile computer to take when the data format is wrong. Refer to the settings of 3.8 Action When Record Format Is Wrong.

3.2.4 DBF FILE LOCATION (8200/8400/8600/8700 ONLY) The setting of “DBF file location” is only available for 8200, 8400, 8600 and 8700 since currently only these models support the memory extension with an SD card. By the setting of “DBF file location”, you may specify where the lookup file is located. The options are:  SRAM  SD Card Normally, the lookup files are stored in the SRAM of the mobile computer. The original lookup files (.TXT) will be automatically saved to DBF format when being sent to the mobile computer. 8200/8400/8600/8700 support to save files to the SRAM, to the SD card or to the SRAM through the SD card. Before the lookup files are sent to the SD card of the mobile computer, they need to be converted to DBF format (.DB0) by the DBF converter tool. You must save the lookup files (.TXT) to DBF format first. Refer to 7.3 SD DBF Converter (8200/8400/8600/8700 Only). The following table details how a DBF file can be sent to the mobile computer when the destined locations are different: File Location Sending Method (1) Send the lookup file to 8200/8400/8700 SRAM.  The sending is carried out by the lookup sending utility featured by the Batch AG. Click Transfer | Send Lookup on the menu bar of the Batch AG to run the utility. SRAM (2) Send the lookup file to 8200/8400/8600/8700 SRAM through the SD card.  The sending is carried out by the DBF converter featured by the Batch AG. Click Tools | DBF Converter from the menu bar of the Batch AG to run the utility. In the DBF tool window, be sure to enable Distribute.  Note the mobile computer’s application template must have the Lookup property’s DBF file location set to “SRAM”. SD Card Send the DBF file to the SD card in 8200/8400/8600/8700.  Such sending is only feasible when the mobile computer installed with the SD card runs as a removable disk. It requires the mobile computer with SD card connected to a host computer with a USB cable.  Such sending is carried out by the DBF converter featured by the Batch AG. Click Tools | DBF Converter from the menu bar of the Batch AG to run the utility. In the DBF tool window, be sure to enable Distribute.  Note the mobile computer’s application template must have the Lookup property’s DBF file location set to “SD Card”.

Note: It takes less time to send lookup files to SRAM via SD card than send to SRAM directly.

3.3 LOOKUP DATA [Lookup data] group box features the settings about how the data in the lookup file should be handled. 3.3.1 ONLY READ DATA ONCE When this checkbox is not ticked, each time the key value of an incoming data will be compared with entries read from the referenced lookup file. And the matched value will be brought up. If you tick the checkbox, the following details how a data collecting form deals with the incoming data: Lookup data found matching… An input field value will be rejected when it can be found matching an entry in the lookup file. The input field will then be cleared automatically by default.  Show message when the data is matched: For the event of rejecting an input field value, you can decide to show a warning message before the input field is cleared by ticking this checkbox. In this case, press any key on the mobile computer to clear the input field.  Allow to update lookup data once if the data is matched: Ticking this checkbox means that the lookup file is updated just once for the first time the incoming data is found in the lookup file. No lookup data found matching… As long as the Only read data once checkbox is ticked, the action for a data collecting form to take would be set to Insert to lookup file automatically (see 3.4 Action When the Input Data Has No Match). Then the incoming data will be written into the lookup file when no data in the lookup file is found matching the incoming data, i.e. new data.  Another action available for the data collecting form to take is Show Warning Message & Insert. It supports to show a warning message before the incoming data is accepted into the lookup file. 3.3.2 LOOKUP DATA CAN BE UPLOADED This is the default setting. It enables the exchange of a lookup file between the mobile computer and a host computer (such as your PC). On the mobile computer, select 2. Upload Data from the user application main menu after you have the data collected and have the connection established between your PC and the mobile computer. Refer to 1.2.3 Record. 3.3.3 TRIM SPACE WHEN LOOKUP DATA CAN BE UPLOADED This option is only available when the Delimiter option is selected in the [Field property] group box. Select this option to remove the spaces in a lookup file that has delimiters to separate the data fields when it is uploaded to your PC.

3.4 ACTION WHEN THE INPUT DATA HAS NO MATCH The [Action when input data no match] group box features a few actions for the data collecting form to take when the incoming data finds no match in the key fields of the lookup file. See 3.7 Key Field for reference. 3.4.1 CONTINUE When “Continue” is selected, the data collecting form goes on and allows the incoming data to input into its field when the incoming data finds no match in the key fields of the lookup file. No message will display.  With “Continue” selected, if the “Record” mode of the data collecting form is set to "Save", "Save & update", "Save & output record", "Save & output screen" or “Save & remove” on the Form property page, data can only be saved in a data file. See 1.2.3 Record for reference. 3.4.2 SHOW WARNING MESSAGE When Show warning message is selected, a warning message "Data not found!" would display when the incoming data finds no match in the key fields of the lookup file.  The cursor shows at the end of the data input to prompt you to input other data. (By the example below, you need to replace “9990” with other data.) 3.4.3 INSERT TO LOOKUP FILE When “Insert to lookup file” is selected, the data collecting form proceeds to accept the incoming data without showing any message even when the incoming data finds no match in the key fields of the lookup file. The incoming data will be written into the target lookup file if the Record mode of the data collecting form is set to "Update lookup", "Save & update", “Remove from lookup”, or “Save & remove”. See 1.2.3 Record for details.

3.4.4 SHOW WARNING MESSAGE & INSERT When “Showing warning message & insert” is selected, the data collecting form shows a warning message “Data not found!” before accepting the incoming data into the target lookup file even if the incoming data finds no match in the lookup file. The incoming data will be written into the target lookup file if the Record mode of the data collecting form is set to "Update lookup", "Save & update", “Remove from lookup”, or “Save & remove”. See 1.2.3 Record for reference. 3.4.5 CLEAR THE SCREEN When “Clear the screen” is selected, the data collecting form automatically clears the incoming data when it finds no match in the lookup file. The incoming data isn’t accepted into the lookup file. The input field awaits new entry. 3.4.6 SHOW WARNING & CLEAR SCREEN When “Show warning & clear screen” is selected, the data collecting form shows a warning message “Data not found!” when the incoming data finds no match in the lookup file. The incoming data will be cleared and the input field awaits new entry.

3.5 OFFSET This applies to Fixed Length. Specify the start position for each referred data field. 3.6 LENGTH  When the field property is set to Fixed Length, specify the length for each referred data field. The value can be 255 at most.  When the field property is set to Delimiter, specify the maximum length for each referred data field. The value can be 255 at most. Note: If a delimiter is used to separate data fields, any improper value would cause wrong data format. 3.7 KEY FIELD The import of data depends on the key field. Select your key field so that an index file can be created for the database (lookup file).  When a form makes reference to a lookup file, there must be one input field associated with the key field of the database (lookup file). When its input data is found matching with any key field value of the database, data of other fields linking with the key field will be imported from database into the form. If no matching, see 3.4 Action When the Input Data Has No Match. Note: If offset and length of each field are specified improperly, it may go wrong with data import.

3.8 ACTION WHEN RECORD FORMAT IS WRONG The [Action when the format of record is wrong] group box features a few actions for the application template to take when a lookup file of wrong data format is sent to the mobile computer. The crucial factors for a lookup file’s data format are usually the separation of data fields, i.e. fixed length and delimiter. 3.8.1 STOP THE DOWNLOAD PROCESS With “Stop the download process” selected, a warning message will be displayed on the mobile computer to indicate which line is found format mismatching if a lookup file with wrong format is detected. The downloading process is stopped then. You will need to correct the data format. For example, remove any empty record (line) at the end of the lookup file. And then download the lookup file again. The following table lists the actions taken by the application template when the incoming lookup file’s format is wrong: (Note: An application template is marked as “.AGX”.) Fixed Length Conditions Action Record length in source file is greater than that specified in .AGX Stop download Record length in source file is less than that specified in .AGX Stop download Delimiter Cause of Failure Action The number of fields in the source lookup file is more than that specified in .AGX Stop download The number of fields in the source lookup file is less than that specified in .AGX Stop download The field length in the source lookup file is more than that specified in .AGX Stop download The field length in the source lookup file is less than that specified in .AGX Allow downloadNote Note: If the max data length specified in the application template is more than the field length in the source lookup file, the data field in the lookup file will be padded with blank space when it is sent to the mobile computer.

3.8.2 TRUNCATE / REFORMAT THE RECORD When “Truncate/Reformat the Record” is selected, if a lookup file of wrong format is sent in, the application template first displays a message on the mobile computer to notify the mismatching part fixed, automatically truncated, or reformatted during downloading. For example, the additional fields of a record will be left out. However, you may need to reload the lookup file after the data format has been corrected. The following table lists the actions taken by the application template when the incoming lookup file’s format is wrong: (Note: An application template is marked as “.AGX”.) Fixed Length Conditions Action Record length in source file is greater than that specified in .AGX Truncate Record length in source file is less than that specified in .AGX ReformatNote Note: Each field of that specific record will be padded with additional space. Delimiter Conditions Action The number of fields in the source lookup file is more than that specified in .AGX Truncate The number of fields in the source lookup file is less than that specified in .AGX ReformatNote1 The field length in the source lookup file is more than that specified in .AGX Truncate The field length in the source lookup file is less than that specified in .AGX Allow downloadNote2 Note: (1) Additional fields will be appended with additional delimiter and space. (2) The data field concerned will be padded with additional blank space.

3.8.3 SKIP THE RECORD When “Skip the record” is selected, if a lookup file of wrong format is set in, the application template first displays a message on the mobile computer to indicate the mismatching part discarded. Then you may need to reload the lookup file after the data format has been corrected. Fixed Length Conditions Action Record length in the source lookup file is more than that specified in .AGX Skip Record length in the source lookup file is less than that specified in .AGX Skip Delimiter Conditions Action The number of fields in the source lookup file is more than that specified in .AGX Skip The number of fields in the source lookup file is less than that specified in .AGX Skip The field length in the source lookup file is more than that specified in .AGX Skip The field length in the source lookup file is less than that specified in .AGX Allow downloadNote Note: That specific field will be padded with additional blank space. 3.9 RESET CURRENT LOOKUP FILE Click the “Reset Current Lookup File” button to load the default settings. Note: The settings for the current lookup file will be cleared.

computer’s barcode support depends on the scan engine equipped. According to application requirement, users may need to enable or disable certain symbologies, and the configuration should be included in the application template on the mobile computer. The Batch AG’s Symbology property page is the access to achieve the such configuration. The Symbology property page covers the group boxes of [Reader Settings] and [Barcode & Parameters]. In the following contents of this chapter, you will be guided through these group boxes one by one. IN THIS CHAPTER 4.1 Reader Settings......................................................... 84 4.2 Barcode & Parameters ................................................ 84 Chapter 4 SYMBOLOGY 1 2

4.1 READER SETTINGS The [Reader Settings] group box features a set of options regarding how the scan engine should scan and read. Refer to the following appendices for information on barcode reader settings —  Appendix II - CCD/Laser Scan Engine for details.  Appendix III - LR/ELR Laser Scan Engine for details.  Appendix IV - 2D Scan Engine for details. 4.1.1 CODE ID The “Code ID” means the characters prefixed to a barcode scanned to identify the barcode’s symbology. Click the Code ID button to pop up a [Code ID] dialogue box that features the settings of barcode ID. When “Code ID” is enabled, a Code ID will be prefixed to the decoding result of a barcode.  Click on the text box next to a barcode name, and select one code from the pop-up [The Grid Control] (ASCII codes) dialogue box. Alternatively, you may click Set 1 ~ 5 buttons to assign code ID for all text boxes. Note: The Code ID settings for GS1 Databar-14/Expanded, GS1 Databar Limited, and GS1-128 are detailed in 4.2 Barcode & Parameters. 4.1.2 RESET Click the [Reset] button to load the default settings. The resetting applies to the following -  The settings in [Reader Settings] group box. See 4.1 Reader Settings.  The settings in [Barcode & Parameters] group box. See 4.2 Barcode & Parameters. Note: The current settings will be cleared. 4.2 BARCODE & PARAMETERS The [Barcode & Parameters] group box features the advance settings of various barcode symbologies supported. Refer to the following appendices for information on symbology settings —  Appendix II - CCD/Laser Scan Engine for details.  Appendix III - LR/ELR Laser Scan Engine for details.  Appendix IV - 2D Scan Engine for details. Note: Code ID settings for GS1 Databar-14/Expanded, GS1 Databar Limited, and GS1-128 are provided in this group box.

These basic settings are divided into three themes: “Initial”, “Function Key” and “Security”. Each is presented on a single tabbed page of the Settings. IN THIS CHAPTER 5.1 Initial Settings........................................................... 86 5.2 Function Key Setting .................................................. 95 5.3 Security Setting......................................................... 96 Chapter 5 SETTINGS 1 2 3

5.1 INITIAL SETTINGS The Initial property page features the following settings: Settings Default Value Remarks Data Deletion Manual Entry Options Show count Stay on the LCD for 600 ms Key Click Tone 2 Backlight Turn off Warning Beep Two beeps Good Read Beep One beep Vibrator Duration Off Buzzer Volume LARGE_VOL Only for 8200/8400/8600 Reader Option CCD/Laser Upload Method Cradle-IRNote Download Method Cradle-IRNote Bluetooth SPP is not available on the mobile computer unless selected for downloading to 8061, 8360. Baud Rate & Modem Speed 115200 bps Note: For 8200/8400/8600/8700, the default upload/download port is RS-232. 5.1.1 DATA MANIPULATION The [Data Manipulation] group box covers settings of “Data Deletion” and “Entry Options” which are detailed in the following: Data Deletion Configures if the data should be automatically deleted from the mobile computer after it is uploaded to a host computer. It is set to “Manual” by default, which means the application template won’t delete the data from the mobile computer after uploading but leaves it to your decision if to delete the data right after the uploading completes. When the upload completes, you will be prompted if to delete the data. If you decide not to delete the data right at the moment, you can always delete the data later by selecting 3. Utilities | 3. Delete Data from the application main menu on the mobile computer. Select “Automatic” to have the data automatically deleted from the mobile computer upon upload completion. The data on the mobile computer is no longer available as soon as it is uploaded to a host computer. You won’t see any data by using 3. Utilities | 2. Browse Data in the user application main menu of the mobile computer; however, the data won’t be deleted if the uploaded data type are lookup files. If “No” is selected, the application template will skip the data deletion prompt upon completion of upload. The data file(s) and lookup file(s) will remain on the mobile computer after they are uploaded to a host computer. However, you can always select 3. Utilities | 3. Delete Data to delete them later. Entry Options