Knowledge · Identification
A production line needs to know which part or package is present before it records a process step or allows the next action. A smart code reader captures and decodes a symbol, then reports its data and status. This guide follows that process from the image to the machine decision.
Distinguish successful decoding, correct product identity and formal code-quality verification before defining acceptance.

A smart code readeris an imaging device with onboard code-location and decoding software. It returns decoded text and a read status. Supported code types, integrated optics, lighting and machine interfaces vary by model and licence.
This differs from sending images from an area scan camerato separate decoding software. Both approaches can perform identification. Compare the complete required task, including data checks, timing, image retention and maintenance, before choosing the architecture.
The reader must meet the optical and timing requirements as well as the data-interface requirements. Use this page to understand its operation. Related imaging hardware is listed under Cameras . Use the specialist selection pages for model and architecture comparisons.
In one sentence
A valid decode is one step. The controller must still determine whether the value belongs to the expected product and to the current trigger.
Think of the path as five linked steps: present the part → illuminate → capture → locate & decode → communicate.

Present the code within the validated field and distance range. A supported sensor or controller trigger starts acquisition; some applications use continuous acquisition. Include code rotation, tilt and the required clear margin around the symbol in the visibility check. An obscured code may need another view or a change to part presentation.
The light must make bars or cells distinguishable from their background without saturating important regions. Test integrated illumination on the actual surfaces and distances; it may need an external light. For geometry and timing options, see the lighting hub.
A global shutter exposes the image at the same time across the sensor. Short exposure or a correctly timed light pulse limits motion blur. Check that the narrowest bar or code cell occupies enough pixels at the largest required field of view. Test focus over the permitted reading distance; autofocus is useful only within the selected model’s range and response time.
The decoder locates candidate code patterns, determines their orientation and interprets the bars or cells. Depending on the code format, error correction can recover some damaged elements and checksums can detect certain errors. Confirm the decoded content against a reference during testing; a successful decode alone does not establish that the correct part was identified.
Decoded text normally travels over a supported data connection such as Ethernet or serial communication. Digital I/O commonly carries status signals such as ready, good-read or no-read; it is not a general text channel. Define how text, status and trigger identity are associated, and verify the exact protocol and electrical interface.
| Stage | What happens | What this means |
|---|---|---|
| Trigger | External or free-run start | Match PLC / sensor timing |
| Light | Integrated or external LEDs | Critical for DPM & shiny parts |
| Decode | Locate symbol, read modules | Symbology set & grade matter |
| Output | String + status to controls | Protocol & no-read handling |
Code structure and marking method are different properties. Record both before testing the reader.
Linear codes encode data in bars and spaces along one axis. Confirm the required symbology, narrowest bar and clear margins. An imaging reader can examine several regions of the symbol; suitability still depends on the tested damage, contrast and orientation. Do not assume a universal performance advantage over another reading method.
Matrix codes such as Data Matrix and QR use a two-dimensional cell pattern. Stacked formats such as PDF417 use a different structure. Error-correction capacity depends on the format and encoding and does not guarantee recovery of a particular damaged mark. Match the reader’s supported symbologies and data formatting to the application.
Direct Part Marking (DPM) describes applying a mark directly to the part, for example by laser or dot peen. It is not a separate code symbology: a Data Matrix may be printed on a label or marked directly on metal. Surface and marking variation determine the lighting trial; the specialist DPM guide covers that selection.
This is the decision project teams ask most often. Both paths can read codes. They differ in ownership cost, flexibility and how you staff the project.

| Approach | Best when | Watch-outs |
|---|---|---|
| Smart code reader | ID is the job; high read-rate KPI; standard symbologies | Less flexible for multi-tool inspection |
| Smart camera | Codes plus presence, OCR, simple gauging on one device | Tool limits vs full PC libraries |
| Area scan + PC software | Multi-feature inspection; custom algorithms; shared PC | You own lighting, lens, decode tuning & IT |
Choose a dedicated smart code reader when identification is the main task and the selected model supports the required codes, lighting, configuration and machine interface. Validate the read result and processing time with representative parts. Integrated lighting or autofocus may simplify installation, but their suitability must be demonstrated at the required distance and speed.
Choose an area scan camera with decode software when the same image also needs supported measurement or inspection functions and external processing fits the project. Check that all tasks share compatible imaging conditions. Include lensand lighting selection and assign ownership of the software configuration. Compare architectures in smart camera vs PC-based vision.
Hybrid stations are common: a smart reader for the serialized mark, a separate camera for cosmetic QC. Do not force one device to be both if takt or lighting geometries conflict.
Inspect the original image when a code fails. Establish whether the failure is caused by missing contrast, focus, movement, symbol damage or data handling before changing the decoder settings.
For printed labels, compare front-light angles and include any glossy laminate. Verify the required clear margins around the symbol. Test changes in ambient light with the planned shielding installed.
On glossy surfaces, a direct reflection may saturate code cells. Compare diffuse and directional illumination using the same sample positions. Polarization may help some surfaces, but its effect and light loss must be tested on the actual material.
For direct marks, retain examples of permitted marking and surface variation. Compare lighting using those parts and record both images and decoded results. Use a feasibilitytrial to qualify the complete combination.
On a conveyor, compare travel during exposure with the allowed blur at the code. Synchronise a pulsed light with the reader’s exposure and stay within the light and controller ratings. Increasing electronic gain also amplifies image noise. Assess reading performance in this setup separately from formal code verification.
For light geometry and continuous or pulsed operation, use the Computer Vision lightingguide.

Identification can support the following process tasks when code visibility and data handling are validated:
Define whether the task is reading a value, checking it against an order, or verifying formal marking quality. A successful decode alone does not cover the other two requirements.
Compare the reader against your actual code formats, cell sizes, reading distance, speed and machine interface. Confirm these capabilities for the exact model and software licence. A larger pixel count cannot compensate for missing contrast, poor focus or incorrect result handling.
List the required code formats and expected data structure, including separators or application identifiers. Confirm model and licence support. Test the string received by the PLC or production system, not only the text shown in the reader’s setup screen.
Illustrative sampling: a 0.2 mm module across a 100 mm field with 1,280 horizontal pixels occupies 0.2 × 1,280 ÷ 100 = 2.56 pixels. At a 160 mm field this falls to 1.6 pixels. Compare these values with the exact reader’s requirements and test the code; they are not universal decode thresholds.
Test integrated and external lighting where relevant. Include mounts, filters and any controller in the comparison. Confirm that the selected light preserves contrast across the required position and surface range.
Measure the complete trigger-to-result time, including any focusing, multiple exposures or retries. Compare it with the actual result deadline and shortest trigger interval. In multi-code mode, define the expected code count and ordering and test missing or additional symbols.
Agree the status and data sequence with the PLC engineer. Include no-read, unexpected content, late data and lost connection. If diagnostic images are stored, define retention and behaviour when storage is unavailable.
Check operating temperature, protection rating and compatibility with cleaning or cutting fluids. Support cables so they do not move the reader. Verify that cleaning access does not disturb the accepted position and focus.
A reliable ID station is a system:
Validate independent good, defective and borderline marks. Report attempts, correct expected values, no-reads, unexpected values and late results separately. Identify repeated reads of one part separately from distinct parts. Agree limits in advance and test the operator’s recovery procedure without losing product identity.
On packaging lines, check the smallest permitted code and every format’s position range. Validate continuous or pulsed illumination at production speed and verify that a format change loads the intended settings.
For marked metal, include dry and oily surfaces and normal marking variation. Retain the images and expected values used to qualify the lighting and decoding combination.
For small electronic parts, verify pixels per module and focus at the nearest and farthest positions. If the same station also inspects assembly, test whether the required views and lighting are compatible.
For serialization, test the link between the decoded identifier and the active production record. Define duplicate handling, rejected-part handling and the evidence needed for the applicable validation process.
The station acquires an image, decodes it and sends the result with its status to machine control. Associate each result with the corresponding product and trigger. Set a deadline and an explicit response to missing, invalid or late results. Test re-reading and manual recovery without losing the association between the part and its recorded identity.
If identification shares a cell with gauging or guidance, settle architecture with the smart vs PCpage before freezing hardware. For multi-camera cells, see also the camerashub.
No. Handhelds are for operators. Fixed-mount smart readers are for machines: continuous duty, industrial I/O, and automated triggering.
Most modern imaging readers decode both when licensed. Confirm your symbology list and any DPM option before purchase.
When you must inspect, measure or guide in addition to reading, or when a shared PC vision stack already owns the cell. See area scan and smart vs PC guides linked above.
Retain the failed image and trigger/result log. Check visibility, focus, motion, contrast and symbol damage, then compare the decoded data with the expected value. A no-read and a data-association error require different remedies.
Rarely for decoding. Mono sensors with controlled light are typical. Color lighting (different LED wavelengths) can improve contrast on tinted materials without a color sensor.
Bring real samples, state the read-rate KPI and takt, and run a short feasibility lighting trial. Start from Knowledge and the feasibility checklist.
Define the required code, its smallest element, position range and result deadline. Then test both decoding and the controller’s identity check on representative parts. Use the linked guides for lighting and architecture decisions.
When ID shares a cell with inspection or guidance.
Ring, bar, dome, backlight and strobe for contrast.
Sample-based trials before you freeze the BOM.
Send representative code samples, speed, field of view and the required machine interface.
Related: Kennis / Knowledge, area scan cameras, smart vs PC vision.
Continue with the DPM guide when the code is marked directly on the part. Use the product specifications after the sample test, and the architecture guide if the station also needs inspection.