No part of this publication may be reproduced or used in any form, or by any electrical or mechanical means,
without permission in writing from Zebra. This includes electronic or mechanical means, such as photocopying,
recording, or information storage and retrieval systems. The material in this manual is subject to change
without notice.
The software is provided strictly on an “as is” basis. All software, including firmware, furnished to the user is on
a licensed basis. Zebra grants to the user a non-transferable and non-exclusive license to use each software
or firmware program delivered hereunder (licensed program). Except as noted below, such license may not be
assigned, sublicensed, or otherwise transferred by the user without prior written consent of Zebra. No right to
copy a licensed program in whole or in part is granted, except as permitted under copyright law. The user shall
not modify, merge, or incorporate any form or portion of a licensed program with other program material, create
a derivative work from a licensed program, or use a licensed program in a network without written permission
from Zebra. The user agrees to maintain Zebra’s copyright notice on the licensed programs delivered
hereunder, and to include the same on any authorized copies it makes, in whole or in part. The user agrees not
to decompile, disassemble, decode, or reverse engineer any licensed program delivered to the user or any
portion thereof.
Zebra reserves the right to make changes to any software or product to improve reliability, function, or design.
Zebra does not assume any product liability arising out of, or in connection with, the application or use of any
product, circuit, or application described herein.
No license is granted, either expressly or by implication, estoppel, or otherwise under any Zebra Technologies
Corporation, intellectual property rights. An implied license only exists for equipment, circuits, and subsystems
contained in Zebra products.
Revision History
Changes to the original guide are listed below:
ChangeDateDescription
-01 Rev A5/2011Initial release.
-02 Rev A3/2012Updates for 64-bit.
-03 Rev A4/2014Updates to include scale information.
Supported Symbology Types vs. Scanner Mode ........................................................................... 6-2
Index
ABOUT THIS GUIDE
Introduction
This guide provides information about the Zebra Scanner JPOS Driver.
Chapter Descriptions
Topics covered in this guide are as follows:
•
Chapter 1, INTRODUCTION TO THE SCANNER JPOS DRIVER provides an overview of the Zebra Scanner
JPOS Driver.
•
Chapter 2, INSTALLATION & CONFIGURATION describes specific installation instructions and settings to
configure the Zebra Scanner JPOS Driver on a host computer.
•
Chapter 3, JPOS PROPERTIES, METHODS, EVENTS provides information about JPOS properties,
methods, and events.
•
Chapter 4, SAMPLE APPLICATION (SCANNER JPOS TEST) provides information about the sample
application in the Zebra Scanner JPOS Driver suite.
•
Chapter 5, DIRECTIO describes how the DirectIO feature allows a POS application to communicate directly
with the underlying CoreScanner Service.
•
Chapter 6, SUPPORTED SYMBOLOGY TYPES VS. SCANNER MODE provides a matrix of scanner modes
and supported symbology types in each mode.
viiiSCANNER JPOS DRIVER DEVELOPER’S GUIDE
Notational Conventions
The followingconventions are used in this document:
•
Courier New font is used for code segments.
•
Italics are used to highlight:
• Chapters and sections in this and related documents
• Dialog box, window and screen names
• Drop-down list and list box names
• Screen field names
• Check box and radio button names
• File names
• Directory names.
•
Bold text is used to highlight:
• Parameter and option names
• Icons on a screen
• Key names on a keypad
• Button names on a screen.
•
bullets (•) indicate:
• Action items
• Lists of alternatives
• Lists of required steps that are not necessarily sequential
•
Sequential lists (e.g., those that describe step-by-step procedures) appear as numbered lists.
•
Notes, caution and warning statements appear as follows:
NOTE This symbol indicates something of special interest or importance to the reader. Failure to read the note
will not result in physical harm to the reader, equipment or data.
CAUTION This symbol indicates that if this information is ignored, the possibility of data or material damage may
occur.
WARN I N G ! This symbol indicates that if this information is ignored the possibility that serious personal
Service Information
injury may occur.
If you have a problem using the equipment, contact your facility's technical or systems support. If there is a
problem with the equipment, they will contact the Zebra Global Customer Support Center at:
www.zebra.com/support
.
CHAPTER 1 INTRODUCTION TO THE
SCANNER JPOS DRIVER
Overview
The POS application is either a Java application or an applet that uses one or more JavaPOS devices. An
application accesses the JavaPOS device through the JavaPOS Device Interface, which is specified by Java
interfaces.
Each JavaPOS device is a combination of these components:
•
JavaPOS Device Control is a Java class that provides the interface between the application and the
device category. It contains no graphical component and is therefore invisible at runtime and conforms to
the JavaBeans API. The Device Control was designed so that all implementations of a device category's
control are compatible. The Device Control can be developed independently of a Device Service for the
same device category. They may even be developed by different companies.
•
JavaPOS Device Service is a Java class that is called by the Device Control through the JavaPOS
Device Service Interface. The Device Service is used by the Device Control to implement
JavaPOS-prescribed functionality for a physical device. It can also call special event methods provided
by the Device Control to deliver events to the application.
•
The JPOS driver included with the Zebra Scanner SDK for Windows provides JNI (Java Native Interface)
mechanisms to scanner and scale devices (csjposscanner.dll and csjposscale.dll) for the JavaPOS
Device Service layer to interface with the Corescanner driver.
1 - 2SCANNER JPOS DRIVER DEVELOPER’S GUIDE
Zebra Scanner JPOS Driver Architecture
Figure 1-1
For more information about JavaPOS, JavaPOS architecture, terminology and programmer's guides, refer to:
•
•
Zebra Scanner JPOS Driver Architecture
JavaPOS home page at http://www.javapos.com/
UPOS home page at http://www.nrf-arts.org.
NOTE The terms JavaPOS and JPOS are used interchangeably in this document.
CHAPTER 2 INSTALLATION &
CONFIGURATION
Overview
This chapter describes installation instructions and settings to configure the Zebra Scanner JPOS Driver on a
host computer.
For custom installation instructions on installing the Zebra scanner JPOS driver, refer to the Scanner SDK
Developers Guide.
NOTE JPOS components are installed by default with the standard scanner SDK installation. If a custom scanner
SDK installation is performed, the JPOS option must be selected to install the JPOS components.
2 - 2 SCANNER JPOS DRIVER DEVELOPER’S GUIDE
Configuration
After a successful installation of the Zebra Scanner SDK with the JPOS driver, an XML file named jpos.xml is
created in the folder C:\Program Files\Zebra Technologies\Barcode Scanners\Scanner SDK\JPOS\Sample Applications\bin.
The Zebra Scanner JPOS Driver reads jpos.xml to retrieve required configurations such as the baud rate for
serial scanners and scanner filtering rules to form the logical scanner defined by the user. Each <JposEntry logicalName="LogicalScannerName"> tag defines a logical scanner. The following sample JPOSEntries
represents serial, USB IBM Hand-held and USB SNAPI logical devices.
<prop name="parity" value="O"/>
<!--Port mode, default='B', valid values are: 'B'=Nixdorf-B-->
<prop name="mode" value="B"/>
<!--UPC-A Length, default=13, indicates the number of digits generated by the scanner-->
<!--for UPC-A labels based on the scanner's preamble and check digit settings.-->
<!--The scanner service uses this value to determine when supplementals are present.-->
<!--The default value of 13 assumes preamble is set to system character-->
<!--and country code and that transmit check digit is enabled-->
<prop name="UPCALength" value="13"/>
<!--UPC-E Length, default=7, indicates the number of digits generated by the scanner-->
<!--for UPC-E labels based on the scanner's preamble and check digit settings.-->
<!--The scanner service uses this value to determine when supplementals are present.-->
<!--The default value of 7 assumes preamble is set to system character-->
<!--only and that transmit check digit is disabled-->
<prop name="UPCELength" value="7"/>
NOTE When a scale device (such as MP6200) is connected to a host PC via an RSM-supported host mode,
scale functionality is available. The scale is accessible using the JPOS Open and Claim methods.
RSM-supported host modes include SNAPI, IBM HH, IBM TT and SSI.
Scanner Configuration Bar Codes
Scan the Set All Defaults bar code below to return all parameters to the scanner's default values. Refer to the
scanner's Product Reference Guide for default values.
Scan the appropriate bar code below to configure the scanner for either USB or RS-232 communication
protocols.
USB Communication Protocol
INSTALLATION & CONFIGURATION2 - 5
Set All Defaults
RS-232 Communication Protocol
USB (IBM Hand-held)
USB (IBM Table-top)
USB SNAPI
Wincor-Nixdorf RS-232 Mode B
Loading...
+ 37 hidden pages
You need points to download manuals.
1 point = 1 manual.
You can buy points or you can get point for every manual you upload.