User Manual
Table Of Contents
- Voyager 1250g User's Guide
- Table of Contents
- Getting Started
- Programming the Interface
- Introduction
- Programming the Interface - Plug and Play
- USB Serial Commands
- Verifone® Ruby Terminal Default Settings
- Gilbarco® Terminal Default Settings
- Honeywell Bioptic Aux Port Configuration
- Datalogic™ Magellan© Bioptic Aux Port Configuration
- NCR Bioptic Aux Port Configuration
- Wincor Nixdorf Terminal Default Settings
- Wincor Nixdorf Beetle™ Terminal Default Settings
- Wincor Nixdorf RS232 Mode A
- Keyboard Country Layout
- Keyboard Wedge Modifiers
- RS232 Modifiers
- NCR Modifiers
- Scanner to Bioptic Communication
- Input/Output Settings
- Data Editing
- Data Formatting
- Symbologies
- All Symbologies
- Message Length Description
- Codabar
- Code 39
- Interleaved 2 of 5
- NEC 2 of 5
- Code 93
- Straight 2 of 5 Industrial (three-bar start/stop)
- Straight 2 of 5 IATA (two-bar start/stop)
- Matrix 2 of 5
- Code 11
- Code 128
- ISBT 128
- GS1-128
- Telepen
- UPC-A
- UPC-A/EAN-13 with Extended Coupon Code
- UPC-E0
- EAN/JAN-13
- EAN-13 Beginning with 2 Addenda Required
- EAN-13 Beginning with 290 Addenda Required
- EAN-13 Beginning with 378/379 Addenda Required
- EAN-13 Beginning with 414/419 Addenda Required
- EAN-13 Beginning with 434/439 Addenda Required
- EAN-13 Beginning with 977 Addenda Required
- EAN-13 Beginning with 978 Addenda Required
- EAN-13 Beginning with 979 Addenda Required
- ISBN Translate
- ISSN Translate
- EAN/JAN-8
- MSI
- Plessey Code
- GS1 DataBar Omnidirectional
- GS1 DataBar Limited
- GS1 DataBar Expanded
- Trioptic Code
- GS1 Emulation
- Postal Codes
- Interface Keys
- Utilities
- Serial Programming Commands
- Product Specifications
- Maintenance
- Customer Support
- Reference Charts
- Sample Symbols
- Programming Chart
3 - 18
Output Sequence Example
In this example, you are scanning Code 93, Code 128, and Code 39 bar
codes, but you want the scanner to output Code 39 1st, Code 128 2nd, and
Code 93 3rd, as shown below.
Note: Code 93 must be enabled to use this example.
You would set up the sequence editor with the following command line:
SEQBLK62999941FF6A999942FF69999943FF
The breakdown of the command line is shown below:
SEQBLKsequence editor start command
62 code identifier for Code 39
9999 code length that must match for Code 39, 9999 = all lengths
41 start character match for Code 39, 41h = “A”
FF termination string for first code
6A code identifier for Code 128
9999 code length that must match for Code 128, 9999 = all lengths
42 start character match for Code 128, 42h = “B”
FF termination string for second code
69 code identifier for Code 93
9999 code length that must match for Code 93, 9999 = all lengths
43 start character match for Code 93, 43h = “C”
FF termination string for third code
To program the previous example using specific lengths, you would have to
count any programmed prefixes, suffixes, or formatted characters as part of
the length. If you use the example on page 3-18, but assume a <CR> suf-
fix and specific code lengths, you would use the following command line:
SEQBLK62001241FF6A001342FF69001243FF
The breakdown of the command line is shown below:
A - Code 39
B - Code 128
C - Code 93