When you choose a barcode reader for an automation line, check four things: whether it reads your label at your distance and speed, which symbologies it decodes, how lighting and reflection affect the read, and how it triggers and sends data. Then test it with your real labels before you commit.
Key takeaways
- A barcode reader on an automation line is a fixed-mount scanner or camera that decodes 1D barcodes or 2D codes such as QR and Data Matrix as products pass.
- Read range depends on the code’s module size (the width of its narrowest bar or cell), so small codes need close or high-resolution readers.
- Shiny labels and plastic wrap cause glare; mounting angle and lighting often matter more than the reader price.
- A short trial with your actual labels at line speed is the only dependable check.
Barcode Reader Read Distance and Field of View
Read distance is how far the reader sits from the label, and field of view is the width of the area it can see at that distance. Both are stated in the datasheet, usually for a given code size.
The key input is the module size, also called X-dimension. A small module needs a closer reader or a higher-resolution sensor. Datasheets often give a table of read distance against module size, and a depth of field, which is the range of distances where the code stays readable. Check that your label position varies less than the depth of field, for example when boxes of different heights pass.
- Measure the smallest module on your printed label with a ruler or magnifier.
- Find the matching row in the datasheet table and note the distance range.
- Check the field of view covers the full width over which the label can wander on the belt.
- Keep a margin, since a datasheet range assumes ideal conditions, not worn labels for worn labels.
For the imaging basics behind these numbers, see the machine vision OCR and code reading guide.
Symbology Support
A symbology is a barcode format. Common 1D ones are Code 128, Code 39 and EAN or UPC; common 2D ones are QR Code and Data Matrix. The reader must list every format you use in its datasheet.
Check the symbologies on your own packaging and on your customers’ labels, because a supplier may use a different one from yours. Ask whether the reader decodes damaged or low-contrast codes, direct part marking (dots or laser marks on metal) if you need it, and stacked or GS1 formats if you handle those. Check whether the reader can enable only the codes you need, which cuts false reads.
| Item to confirm | Why it matters |
|---|---|
| 1D formats listed | Your labels may use Code 128, Code 39 or EAN |
| 2D formats listed | QR and Data Matrix are common on parts and cartons |
| Direct part marking | Needs a different imager and lighting |
| Selectable symbologies | Reduces false decodes |
Lighting and Reflection
Lighting is the illumination that gives the reader enough contrast between bars and background. Reflection is glare from a shiny label, film or metal that washes out the code.
- Many readers have built-in LED lighting, but strong ambient light or sunlight through a door can still upset them.
- If the label sits under shrink wrap or a glossy film, tilt the reader a little so the mirror-like glare bounces away from the lens. Vendor guides commonly suggest a small tilt; check yours.
- Dark or curved surfaces may need a different light colour or a diffuse light. Red light is common, but other colours can help on some backgrounds.
- Shield the read zone from direct sun, especially near open dock doors.
Light choice is a deep topic, covered in the machine vision lighting guide. Many of the same ideas apply to a simple code reader.
Trigger and Output
The trigger tells the reader when to read, and the output is how it sends the result. Both must suit your controller.
- Triggers: an external sensor input, a software command or continuous reading. A photo-sensor trigger gives a clean read per item.
- Outputs: serial (RS-232 or RS-485), Ethernet (TCP or industrial protocols), USB or discrete I/O for good or bad read.
- Check the reader’s supply voltage and whether it fits the 24 V DC your panel provides.
- Check the read rate against the line speed. Fast belts need fast decoding and short exposure.
- Decide what happens on a failed read: stop, divert or log. Make sure the reader can report a no-read.
Camera-based readers behave like small vision systems. The vision-guided robotics in India overview shows how cameras tie into a robot cell.
Mounting Angles
Mounting angle is how the reader faces the label. Small changes can turn a failing read into a stable one.
- Mount the reader so its field of view is square to the label on a flat surface, then tilt slightly if glare appears.
- Keep the label orientation consistent. Some readers read in any direction; others have limits on skew and rotation, so check the datasheet.
- Use a rigid bracket so vibration does not change the angle over time.
- For top-down reads on boxes of varied heights, check the depth of field again, since the distance changes.
Test with Real Labels
A real-label test means running the reader on your own labels, at line speed, in your own lighting. It is the most reliable check because print quality varies.
Collect labels from the worst printers, older stock and a few damaged ones. Run a trial and log each read: good, no-read or wrong data. Many vendors lend demo units or offer a read-rate trial, so ask. The numbers you need to compare are the read rate and the false read rate.
How to check this yourself
- Measure the smallest bar width (module size) on your label and the range of distances the label will sit at on the line.
- Compare both with the datasheet table for read distance, depth of field and field of view.
- List every symbology you must read and confirm each is in the datasheet.
- Run at least a few hundred labels past the reader at line speed, including damaged ones, and log good, no-read and wrong reads.
- Repeat with the line lights on, off and with daylight present, and note any change.
Common mistakes
- Choosing from the maximum read distance without checking module size.
- Testing only with perfect printed samples.
- Mounting square to a glossy label, so glare blocks the code.
- Forgetting to enable only the needed symbologies.
- Not deciding what the line does when a read fails.
Quick checklist
- Module size measured and compared with the read table.
- Every symbology you use is listed for the reader.
- Lighting and glare tested with your film and surfaces.
- Trigger and output match your controller and supply.
- Trial run on your real labels at line speed.
Frequently asked questions
What is the difference between a barcode scanner and a barcode reader?
The terms are used interchangeably. In automation, a fixed-mount barcode reader reads labels automatically as products pass, usually triggered by a sensor. A handheld scanner is operated by a person. Camera-based readers can decode both 1D and 2D codes, so check which formats your labels use.
Why does my barcode reader fail on shiny labels?
Glossy film or metal reflects the reader’s light straight back, which washes out the bars. Tilting the reader a little, using diffuse lighting or a different light colour often helps. Check the reader’s guide for its recommended mounting angle, then test on your own labels.
Can a barcode reader read QR codes and Data Matrix?
Only if its datasheet lists those 2D symbologies. Many camera-based readers do, while simple laser scanners read only 1D codes. Check that the reader decodes the code type on your parts, and test the smallest and most worn codes you expect.
Related reading
- Raspberry Pi colour tracking pan-tilt with OpenCV, a build to see how a camera finds a target.
- ESP32-CAM robot car, a learning build using a small camera module.
- ESP32-CAM module, a low-cost camera board for experiments, not an industrial reader.
- Industrial robotics hub, for related cell topics.
- Conveyor Robot Cell Integration in India
- LiPo Charger Module: What to Check Before Buying
- Desktop Robot Arm Kits: What to Check Before Buying
About the author and how this is kept accurate
Written, checked and maintained by Jignesh Panchal of Jaadu Digital. Figures in worked examples come from the stated assumptions, not from a bench test of our own. Read the editorial standard, follow the author on LinkedIn, or send a correction. Last reviewed: November 2026.



