Hello all,
Please could someone help me understand how to correctly configure the output order of UDI barcodes?
CONTEXT:
We're working with a customer who wants to capture multiple UDI barcodes in one scan using Orca Scan running on the Zebra TC52-HC (Android 8.1.0). We have configured the DataWedge (version 8.0.37) application with the following settings:
BARCODE INPUT
* Enabled = true
* Hardware Trigger = true
* Configure NG SimulScan settings - Scanning Modes = UDI
KEYSTROKE OUTPUT
Enabled = true
Action key character = none
Inter character delay = 10ms
Data formatting and ordering - Send tokens:
* Barcodes and tokens = enabled
Data formatting and ordering - Token separator:
* None = enabled
Data formatting and ordering - Token order:
* Product or catalog number = enabled
* Device identifier = enabled
* Lot number = enabled
* Expiration date = enabled
* Serial number = enabled
Basic data formatting:
* Enabled = true
* Send data = true
* Send ENTER key = true
If we scan two HIBC barcodes in one scan (primary on top of secondary):
Primary = +E1813L925001K
Secondary = +$$31610015111307K
The DataWedge sends Secondary/Primary to the Orca Scan application +$$31610015111307K/+E1813L925001K
Modifying the Data formatting and ordering, token order appears to have no impact.
How do we configure the DataWedge to send the data Primary/Secondary? Or better still, a concatenated HIBC?
Many thanks!
1 Replies
Sorry if this is a silly question but I don't think this is possible:
* Configure NG SimulScan settings - Scanning Modes = UDI
Under "Configure NG SimulScan settings" the options are "MultiBarcode" or "Document Capture"
The UDI setting is under "Barcode Input", "Configure Scanning Settings", "Scanning Modes", then you can select UDI.
I checked the documentation in case this changed between DW versions, according to https://techdocs.zebra.com/datawedge/8-2/guide/input/barcode/#scanningm…
Scanning Modes exists within both Scanner Configuration and NG SimulScan Configuration sections. The availability of Scanning Modes options is interdependent on the option selected within each section:
Which means unfortunately that scanning and parsing multiple UDI barcodes with a single trigger pull is not supported. Hope that helps?