Knowledge · Code reading

Code reading: smart reader, PC or line scan?

The right reader architecture starts with the production task: code type, presentation, speed, data retention and the action the line must take after a failed read.

Marked metal part for DPM code reading

Architecture decision

Three architectures with different ownership demands

First define the code family, smallest code, reading distance, position variation, line speed and required communications. Then decide whether the same images must also support OCR, presence checks, measurement or defect inspection.

DecisionChoose this whenWatch for
Smart code readerA bounded identification station with one or a few fixed views and direct machine I/O.Check optics, embedded tools, protocols, logging and who may change recipes.
PC-based camera and softwareIdentification is combined with OCR, inspection or measurement, or results from multiple cameras must be coordinated.Greater freedom requires software ownership, an update policy, industrial PC infrastructure and diagnostic tools.
DPM with difficult opticsLaser, dot-peen or etched codes on reflective, curved or variable surfaces.Test the mark and lighting geometry first; the DPM guide covers this optical decision.
Line-scan IDContinuous webs, circumferential views of rotating parts or long products assembled line by line.Size encoder triggering, line rate, lighting, data flow and maximum image length together.

Integration and acceptance

Choose by code type, data flow and fault handling

A 1D code usually needs enough pixels across its narrow bars; a 2D code needs sufficient module sampling in both directions; DPM adds surface response and mark variation. Also define which data goes to the PLC or MES, which images are retained and how operators diagnose a no-read. Accept the station on a representative set with successful reads, no-reads and incorrect reads reported separately. Test re-reading, rejection, line stop, quarantine and manual entry wherever those recovery routes apply.

Test the architecture against your line conditions

Send representative codes or parts and describe speed, variation, communications and fault handling. Business-case inputs also include current manual scans, operator interventions, line stops, quarantine, rework and traceability risk.