Barcode Scanner Configuration: Symbologies, Prefixes, and Firmware
A scanner that beeps but outputs nothing — or reads the wrong symbology — is usually misconfigured, not broken.
Out of the box, most scanners enable a subset of symbologies: often Code 128, EAN-13, UPC-A and QR, but not Code 39, ITF-14, Data Matrix or GS1 DataBar. If a valid barcode produces no output, check the scanner’s configuration sheet before reprinting anything. Enabling the symbology is usually a single configuration barcode scan.
Prefixes and suffixes are the next suspect. A scanner configured to append Enter may submit a form prematurely; one with a prefix may prepend characters that break a numeric field. If the decoded value looks correct on screen but the application rejects it, scan into a text editor and inspect the raw characters, including invisible ones.
Some scanners are set to «symbology identifier» mode, which prepends a short code such as ]C1 to identify the format. That is useful for applications that need to distinguish GS1-128 from plain Code 128, but it breaks systems that expect only the payload. Decide which mode your application needs and configure consistently across all devices.
Finally, check firmware and the keyboard layout. An older scanner may not support newer symbologies such as GS1 DataBar Expanded; a scanner set to a different keyboard layout can swap characters like Y and Z. Keep a configuration sheet per site, record the firmware version, and re-test after any replacement or update.
Jetzt Barcode erstellen
Barcode-Generator