Skip to content
Technical guide

The barcode reader has stopped reading, or reads badly

Symptom: The reader no longer beeps, or nothing appears on screen

Start with a known test code. If the reader beeps but nothing appears, the problem is the interface or the input field. If it does not beep, look at the window, the reading distance and the symbology: a code not enabled in the configuration is never decoded.

Level: field setup

Have ready: A reference barcode whose content you know, a text editor, and the model’s programming manual.

Procedure

  1. Scan a reference code

    Use a code whose exact content you know, for instance one printed in the reader’s own manual. That immediately separates a device fault from a problem specific to the client’s labels.

  2. Listen for the beep

    The beep signals a successful decode. If the reader beeps but nothing appears on screen, the problem is the interface, the driver or the input field. If it does not beep, it is not decoding: check the optics and the configuration.

  3. Clean the window and vary the distance

    A scratched, greasy or film-covered window is enough to break decoding. Every reader has a useful distance range: move the reader slowly closer to and further from the code to find it.

  4. Check the input field

    In keyboard mode the data goes to the active window. Click into the target field before scanning, and test in a text editor: if the text appears there and not in the software, the reader is not at fault.

  5. Return to the default settings

    A reader that has been handled may have lost a symbology or gained a prefix. A reset to the default settings, using the barcode from the manual, restores a known state. Then reprogram the terminator and test again.

Check these before calling support

  • A reference code has been tried, different from the client’s own labels.
  • The test was run in a text editor, outside the till software.

Useful terms

  • Symbology

    A symbology is the grammar of a barcode: which characters it accepts, how they are drawn and how they are checked.

  • Keyboard wedge (HID)

    Keyboard wedge (HID) is the mode in which a reader presents itself as a keyboard: scanned characters are typed into the active field with no driver, but the application cannot tell where the input came from..

  • Imager or laser reader

    An imager-based reader is a reader that photographs the target and decodes both 1D and 2D codes, including on a phone screen.

  • Prefix, suffix and terminator

    Prefix and suffix are characters a reader adds before and after the scanned data.

Hardware involved

Related guides

Guide revised on

Reseller program

Open a reseller account

The account is free and reserved for businesses. It gives you access to our wholesale prices, training and technical support.