The Zebra Scanner Software Developer Kit (SDK) defines an architectural framework providing a single programming interface across multiple programming languages (such as MS .NET, C++, Java) and across multiple system environments (such as Windows and Linux) for all scanners communication variants (such as IBMHID, SNAPI, HIDKB, Nixdorf Mode B, etc.).
The Zebra Scanner SDK includes a suite of components that provides a unified software development framework with a wide range of functions for interfacing Zebra scanners to user applications and solutions.
With this SDK you can read bar codes, manage scanner configurations, capture images/videos and selectively choose a list of scanners on which to work. While one application is in one programming language using a scanner or a set of scanners, another application in a different language can be used differently within the same system environment.
The SDK can build an application with complete control of its scanner's capabilities.
- Simulation HID Keyboard output
- OPOS/JPOS output
- SNAPI output
Command and Control
- LED and Beeper Control
- Aim Control
- Capture / Transfer of images
- Capture / Transfer of Video
Remote Scanner Management
- Asset Tracking
- Device Configuration (Get, Set and Store scanner attributes)
- Firmware Upgrade
- Scanner Communication Protocol Switching
- Service to Automate Configuration / Firmware Upgrade Process
NOTE For a list of a scanner's supported attribute (parameter) numbers and definitions, refer to the Product Reference Guide for that model scanner, available from the Zebra Support website at http://www.zebra.com/support. Attributes include configuration parameters, monitored data, and asset tracking information.
You can configure Zebra scanner devices to be operated in different host communication modes such as USB SNAPI, USB OPOS, USB HID Keyboard, USB IBM Table-top, SSI, and RS232 Nixdorf Mode B. Device feature support varies depending on communication mode but all modes support bar code scanning. Refer to the Product Reference Guide of a specific scanner for the bar codes to set its supported host communication modes.
Using the Zebra Scanner SDK, you can switch between supported host communication modes by calling the host variant switching command programmatically. This is useful when the device is in a less feature supportive mode and some advanced functionality is required but not supported by the current communication mode. The scanner can be switched to a feature rich mode and commands executed before switching the scanner back to the previous mode.
For example, you want to disable the UPC-A symbology but the device is in USB HID Keyboard mode. If the mode is supported by the scanner, you may switch to USB SNAPI or USB OPOS, set UPC- A to be disabled permanently and then switch the scanner back to USB HID Keyboard mode. See Table 1 below for more information.
Table 1 illustrates scanner capabilities supported by each communication mode. Refer to the specifications of a device for its ability to support of each communication mode.
Table 1 Scanner Device Communication Modes Vs. Capabilities
|Capabilities||USB SNAPI||USB OPOS||USB HID Keyboard||USB IBM Table-top||RS232 Nixdorf B||SSI|
|Host Variant Switching||Supported||Supported||Supported||Supported||Not Available||Not Available|
|Management||Supported||Supported||Not Available||Supported||Not Available||Supported|
|Image & Video||Supported||Not Available||Not Available||Not Available||Not Available||Supported (Image Only)|
|Simulated HID Keyboard Output*||Supported||Supported||Not Available||Supported||Supported*||Supported|
|*Advanced Data Formatting (ADF) is not supported when using Simulated HID Keyboard Output.|
Simulated HID Keyboard Output is a feature enabling scanners in USB SNAPI, USB IBM Table-top, USB OPOS, or SSI mode to emulate HID Keyboard keystrokes to a host system for scanned data labels. It sends the content of the scanned data label as HID Keyboard keystrokes thus emulating USB HID Keyboard scanner mode.
The Zebra Scanner SDK supports multiple scanner devices to any application that runs on top of CoreScanner APIs. Each scanner device is shown to the user application by a unique scanner identification number. The scanner ID is a numeric value assigned to each connected device so there cannot be multiple scanner devices holding the same scanner ID.
Asset tracking information like model number, serial number, current firmware version and date of manufacture are available if the scanner and its current host mode support the management feature.
For example, in some modes like USB HID Keyboard, you do not see asset tracking information but the same scanner device shows you such information when it is in USB OPOS or USB SNAPI mode.
The format of device asset tracking information can follow different naming conventions for device model, serial number or current firmware version. For example, the length of a serial number for DS6707 and DS9808 scanners can be different.
The Zebra Scanner SDK supports multiple applications accessing multiple scanner devices connected to the host at the same time.
As described previously, a scanner ID uniquely identifies a connected scanner device to all applications. A scanner ID is consistent among all applications for one SDK instance. If the CoreScanner service or the host machine is restarted, a device may be assigned a different scanner ID but it is unique and referenced by all applications.
- Three applications are connected to one scanner.
- App 1 & App 2 support bi-directional (two way) communication with the scanner.
- Legacy App 3 supported by driver converting SNAPI data into HID format.
- Three applications are connected to two scanners.
- App 1 and App 2 support bi-directional (two way) communication with the DS6878.
- Legacy App 3 receives HID keyboard emulation data from the LS2208.
- App 1 performs image capture with the DS6878.
- App 2 can remotely manage both the DS6878 and LS4208.
- App 3 receives OPOS data from both the DS6878 and LS4208.
- One application can manage multiple scanners in multiple communication interfaces.
- The application can capture data, image and video, send management commands and receive responses from multiple scanners.
- All responses from the scanners consist of the scanner device details (ScannerID, serial number, model number, etc.) identifying the device that sent the response.
For example, a bar code event for a scanned label is shown below. The scanned data label arrives with a unique ScannerID and the scanner's model number and the serial number.
<outArgs> <scannerID>1</scannerID> <arg-xml> <scandata> <modelnumber>DS6707-SR20001ZZR</modelnumber> <serialnumber>7114000503308</serialnumber> <GUID>9008A01BB72BA34BB519806B63701AAA</GUID> <datatype>11</datatype> <datalabel>0x39 0x37 0x38 0x30 0x32 0x30 0x31 0x34</datalabel> <rawdata>0x39 0x37 0x38 0x30 0x32 0x30 0x31 0x34</rawdata> </scandata> </arg-xml> </outArgs>
- DS3608-DP DS3678-DP
- DS3608-ER DS3678-ER
- DS3608-HD DS3678-HD
- DS3608-HP DS3678-HP
- DS3608-SR DS3678-SR
- DS457 Series
- DS4800 Series
Version 3.06.0018 – 04/2022
- Bug fix – ScanData property now populating in OPOS Scanner driver when compatibility mode is enabled.
- Bug fix – Barcode data now passing properly through the CoreScanner Diver when the scanners connected in serial (RS-232) Nixdorf Mode B.
Enhanced Toshiba Global Commerce Solutions (TGCS) POS system support
OPOS driver enhanced to supports System Management information calls from TGCS POS systems
- CoreScanner enhanced to support TGCS’ UPOS WMI = “UPOS_BarcodeScanner” queries
JPOS driver enhanced to support System Management Information calls from TGCS POS systems
- CoreScanner enhanced to support TGCS’ CIM Service Provider = “UPOS_BarcodeScanner” queries
- OPOS driver enhanced to supports System Management information calls from TGCS POS systems
Version 3.06.0015 – 01/2022
- Logging Agent renamed "IoT Connector".
Enhanced JPOS Driver,
- Updated Windows JPOS sample application to support smaller/lower resolutions monitors.
- Fixed rarely seen JPOS statistics retrieval issue.
Version 3.06.0013 – 10/2021
Enhanced JPOS Driver
- Added support to execute DirectIO commands without claiming the device.
- JPOS sample application enhancement to display the "Live Weight" and the logs on live weight status update events.
- Enhanced logging in JPOS driver including access to barcode data, power state, scale weight, and what API calls have been made.
Enhanced Logging Agent capabilities
- Added support for logging of operating system environment variables like "host PC name". The environmental variable check is performed real time on each logging occurrence.
- Added support for real time logging via a JSON call to cloud-based consoles like Splunk.
Version 3.06.0010 – 08/2021
- Enhanced options associated with the OPOS driver’s "ScanData" property. Option now exists to only display scanned data (without displaying the communication protocol specific details).
- Enhanced logging in JPOS driver including access to barcode data, scale weight, and what API calls have been made.
- Fixed statistics and health parameters reporting from the parent scanner device in a cascaded device setup.
Version 3.06.0006 – 04/2021
Enhanced JPOS driver
- Add support for “extended error codes” for NCRDIO_SCALE_LIVE_WEIGHT DirectIO command in JPOS.
- Add support for JPOS Scale status responses.
- Fixed JPOS Scale Open command to enable the “DeviceEnabled” property to execute.
- Fixed JPOS DirectIO RESET command.
- Fixed JPOS Scanner Not of File Direct IO Command.
- Fixed JPOS Sample application, which now shows the scale weight value when DirectIO NCR_LIVE_WEIGHT command executes.
- Fixed Scale OPOS crash issue when retrieving Check Health Text after executing Check Health command.
Version 3.06.0003 – 01/2021
OPOS and JPOS enhancements
- Added support for Scanner DirectIO RESET command.
- Added support for custom MP7000 scale result codes for ErrorOverWeight, ErrorUnderZero and ErrorSameWeight.
Enhanced Logging Agent capabilities
- Log agent can now retrieve Host/PC name and IP address.
- "Scan Avoidance" functionality renamed to "Non-Decode Event".
- The reporting interval can be customized. Set unique programming interval by attribute. Note a small interval (less than 30 seconds) may impact POS system performance.
Version 3.06.0002 – 10/2020
- Updated Visual C++ redistributable package from 2017 to 2019. Note redistributable package for 2017 is no longer included with the SDK.
- Add support for the scanner page motor action to the sample applications (C++ and C#).
- JPOS driver update. Removed Apache Xerces XML parser dependency from the Zebra JPOS Service Object (SO).
Version 3.05.0005 - 07/2020
Logging Agent bundled with Windows SDK
- The Logging Agent allows a 3rd party management console, like Microsoft’s SCCM, to track scanner information including the scanner’s health by parsing a Logging Agent generated log file.
- The Logging Agent will output a log file, one file per scanner/host.
The Logging Agent is configurable and can document one or all of the following information:
- Asset information
- Statistics for example battery charge level or UPCs scanned
- Firmware failures and or firmware success
- Parameter value(s) changed. Achieved by tracking parameter 616 (config file name changed to “Modified”)
- Scanned barcode data (all scanned items)
- Scan avoidance for MP7000
- The logging agent can have its output stored locally on its host PC or output to a network shared folder.
- Added support for Data Parsing (supports UDI, GS1 Label Parsing and Blood Bag) symbology to sample applications (C++ and C#).
- Added support for CDC switching on SDK sample applications (C++ and C#).
- OPOS Scanner/Scale CCO update from version 1.14 to version 1.14.1.
Version 3.05.0003 - 04/2020
- For NCR based retail POS customers- Added support for NCR Direct I/O command in OPOS and JPOS drivers (Scanner and Scale).
- Faster wireless firmware update for select scanners over the Bluetooth Classic communication protocol. See 123Scan’s release notes per scanner for product support details.
- OPOS driver updated to comply with all Symbologies specified in the OPOS 1.14 specification.
- JPOS driver update. JPOS driver now uses a common code base with the more mature Linux JPOS driver.
- JPOS driver operation now also validated on OpenJDK 11, in addition to existing validation on the Oracle JDK.
- Updated the version of Visual C++ redistributable package from 2012 to 2017. Note redistributable package for 2012 is no longer included with the SMS.
- Removed Windows XP support.
Version 3.05.0001 - 01/2020
- Enhanced the OPOS driver to comply with the OPOS 1.14 specification on supported Symbologies.
- Enhanced the JPOS driver to meet fully JPOS 1.14 specification compliance.
- Enhanced JPOS demo app to display barcode data in HEX format.
- Enhanced JPOS driver to support scanner configuration through a jpos.xml file.
Version 3.04.0011 - 10/2019
- Fixed WMI agent enabling filtering of scanner(s) when the configuration name contained unreadable characters.
- Fixed Windows 10 issue preventing scanner from returning barcode data in HIDKB mode after host PC logoff/logon or sleep mode event.
- Fixed a conflict when CoreScanner installed and pairing Bluetooth devices by searching the host PC.
Version 3.04.0007 - 07/2019
- Add support within OPOS driver for the following Symbologies: GS1 Data Matrix, QS1 QR and Grid Matrix.
- Enhanced the C# demo application: Added a RFID tab with Scan Scan Write functionality.
Version 3.04.0002 - 04/2019
- Added customizable logging module to CoreScanner. A user can now format the log file output to include parameters and layout from predefined options.
- Simulated HID Keyboard output, now handles German by setting “Keyboard emulation/locale” to “Default”. Other languages supported include English and French.
Version 3.03.0016 - 02/2019
- Fixed some bugs and improved stability in TWAIN driver.
- Fixed an issue in Scanner WMI provider regarding firmware download events.
- Fixed an issue with OPOS binary conversion.
Version 3.03.0013 - 11/2018
- Fixed firmware update failure (low occurrence problem).
- Updated SNAPI driver. It now includes a Microsoft signature.
- Implemented Scale OPOS driver beep on good read weight. This is a custom feature implemented to address a customer issue which can be enable through Windows registry configurations.
- Added support for NCR Direct IO command (DIO_NCR_SCAN_TONE).
- Introduced support for barcodes encoded with Windows’ code pages like Russian and Korean.
Introduced registry entries
- to control the value of the OPOS Power State property.
- to configure scale behavior.
- to configure Windows’ code pages.
- Introduced support for the NCR direct I/O command to get the “Scale live weight” data.
- Fixed a security vulnerability – Exe execution can no longer introduce a shell command injection via filename.
- Fixed firmware update progress event missing issue with Scanner WMI provider.
- Minor bug fixes.
Version 3.02.0000 - 08/2017
- Updated JPOS sample application to demonstrate Direct I/O functionality.
Version 3.01.0000 - 09/2016
- Bluetooth support for cordless scanners without a cradle on Windows 7, 8 and 10 using Microsoft’s Bluetooth stack.
- OPOS support for “Not On File Beep” NCR capability.
- Source codes of Sample Applications updated to support Microsoft Visual Studio 2010 and above.
Version 3.00.0000 - 11/2015
- Rebranded Scanner SDK from Motorola to Zebra.
- Supports Windows 10 (32 and 64 bit).
Version 2.06.0000 - 11/2015
- Support for RFD8500 firmware update.
Version 2.05.0000 - 07/2015
- Support for new MP6000 firmware features.
- Stability enhancements.
Version 2.04.0000 - 08/2014
- OPOS Direct IO support.
- JPOS supports both 64bit and 32bit JVMs on 64bit platforms.
- Added support for 32bit OPOS drivers on 64bit platforms.
- Bug fixes.
- Security enhancements to address potential security vulnerabilities.
Version 2.03.0000 - 05/2014
- Driver ADF support.
- MP6000 Scale Live Weight Event support.
- Microsoft® Visual Studio Project Template provided for Zebra Scanner SDK.
- Bug fixes.
Version 2.02.0000 - 12/2013
- Supports Windows 8/8.1 (32 and 64 bit).
- Bug fixes.
Version 2.01.0000 - 08/2013
- Inter key delay feature in HID Keyboard emulation.
- Bug fixes.
Version 2.00.0000 - 06/2013
- Optimized log file operation.
- IBM Table Top host interface support.
- MP6000 scale commands added.
- MP6000 scale support for OPOS and JPOS.
- DWORD attribute support.
- Unsolicited scanner events (Topology changes and Decode data) support (Scanner firmware support required).
- Statistics support (Scanner firmware support required).
Version 1.02.0000 - 08/2012
- Codeless scanner plug-n-play events added (Require Firmware update, check scanner PRGs for firmware support availability).
- Simple Data Formatting feature added for emulated keyboard data.
- TWAIN Custom capabilities added.
- SNAPI scanner support added to Scanner WMI Provider.
- Enhanced InstallShield with more custom installation options.
- OPOS driver modified to support Multi-threaded apartment (in-proc/out-proc) POS applications (clients).
- Host variant switching support added for scanners with NULL synapse buffer.
Version 1.01.0000 - 03/2012
- 64-bit Windows 7 support added.
- TWAIN imaging interface supported.
- USB-CDC Serial Emulation mode supported. Com protocol switching partially supported – able to programmatically switch into USB-CDC host mode but not exist.
Version 1.00.0000 - 07/2011
- Supports Windows XP SP3 (32-bit) and Windows 7 (32-bit).
- RSM 2.0 Scanner Support.
- SNAPI faster firmware download support.
- Programmatic Host Variant Switching support.
- HID Keyboard Emulation support for English and French language keyboards.