Packaging Inspection System Architecture: From Trigger to Reject

Every downstream tolerance inherits the variability of how the package arrives. A carton that can rotate 15 degrees and shift 20 mm forces a wider field of view, which costs resolution, which raises the lighting requirement. Fixing presentation with a guide rail is often cheaper than the imaging it saves.

Characterize presentation before specifying hardware: orientation range, lateral position range, height variation, spacing between units, and whether motion is continuous or indexed.

• Continuous conveyor: strobed acquisition and a tight exposure budget; reject timing tracked by encoder.
• Indexed / dwell station: longer exposure available, simpler illumination, higher mechanical cost.
• Random rotation: located-feature inspection rather than fixed regions, or mechanical orientation upstream.
• Variable height: depth-of-field budget checked at both extremes, not just nominal.

A hardware trigger from a photo-eye, or a position from the line encoder, defines when the image is taken and — just as importantly — which unit that image belongs to. Unit identity is what allows the verdict to reach the right package at the reject point.

Strobed illumination synchronized to the trigger freezes motion at short exposure. The blur budget should be a fraction of the smallest feature being judged; for printed code content that is a stroke width, for closure position it may be a millimetre.

Trigger source

Photo-eye for discrete units; encoder position where units are tracked over distance to the rejector.

Exposure

Short enough that motion blur stays below the blur budget for the smallest judged feature.

Shutter

Global shutter for moving product; rolling shutter distorts geometry and corrupts measurements.

Illumination

Strobed, shielded from ambient and from adjacent stations, geometry chosen for the substrate.

Unit tracking

Each trigger associated with a unit index so verdicts and rejects cannot desynchronize.

• Presence and count: is the expected item, insert, leaflet or component there?
• Orientation: right way up, right way round, flap and seam position within tolerance.
• Closure and cap: cap presence, seating height, cocked-cap detection, induction seal region, closure rotation where visible.
• Label and code: identity, placement, and verified content — usually the highest-consequence check.
• Mixed-product prevention: product or component identity confirmed against the active work order.
• Package quality: crush, gross deformation, gaping seal areas, contamination in the seal region where the imaging supports it.

Multi-SKU packaging lines live or die on recipe management. The active recipe should be selected by the work order or PLC product register, versioned, and auditable. Reason codes on failures — wrong code, no label, cocked cap, wrong orientation, unreadable image — turn a reject count into diagnosable information.

Three verdicts, always: PASS, FAIL and NO READ. A NO READ is the system telling you the image was not usable, which is a different problem from a defective package and deserves a different response.

• Reject window expressed in encoder counts or milliseconds, with worst-case latency measured during commissioning.
• Fail-safe default on missing verdict, communication loss or camera fault — usually reject on regulated product — and tested as part of acceptance.
• Consecutive-fail policy: alarm, stop, or continue rejecting, decided before commissioning.
• Reject confirmation sensing where the mechanism allows, so an unconfirmed reject is not treated as a success.
• Recovery behavior after an e-stop or jam, so unit tracking cannot silently shift by one position.

The record is what makes an inspection station useful after the fact. At minimum: timestamp, unit identity or index, active recipe and revision, verdict, reason code, measured values for the checks that produced a number, and a retained image for failures.

Retention policy should be explicit and finite — failure images plus a sampled set of passes is a common, defensible arrangement. Define the schema in writing so the data can be consumed by MES or a quality report without reverse engineering.

Acceptance should be a written criterion tested at production speed on a labeled panel containing clean product and each defect class in scope, with escapes and false rejects reported separately. Include the fail-safe tests: pull a cable, block the light, force a timeout, and confirm the system behaves as specified.

Handoff should leave the plant with a documented recipe model, reason-code list, the validation results, and the maintenance actions that require a re-validation run.