High speed barcode verification: size the strobe pulse

A moving barcode can decode reliably during setup and still fail when line speed increases or the package tilts. The first decision is how much motion the image can tolerate, followed by whether the lighting can deliver sufficient signal within that interval.

This guide is for engineers planning high speed barcode verification immediately after printing or before downstream handling. You will calculate an initial pulse duration, check its overlap with camera exposure, and identify the documentation needed before pairing a light with a controller. You will also separate production read checks from calibrated print-quality grading: sharp images support both, but decoding success does not establish a grade.

Decide what the station must prove

Define the inspection claim before choosing hardware. Reading a code, checking its content and measuring print quality require different evidence.

For standardized grading, identify the applicable method, such as ISO/IEC 15415 for two-dimensional symbols or ISO/IEC 15416 for linear symbols. Confirm the requirements for illumination geometry, wavelength, measurement aperture and calibration before designing the station.

The distinction matters commercially. An inline station may provide useful process monitoring without being suitable for a customer's formal verification requirement. Agree on the required report and acceptance method before ordering parts.

Our guide to judging barcode read confidence explains why decoder confidence and validated acceptance are different questions.

Calculate the allowable motion blur

Use the smallest module or narrow bar, the image sampling and the maximum instantaneous line speed. Average conveyor speed can hide acceleration, slip or web vibration.

Start with an engineering blur budget rather than a universal barcode rule. For example, limiting motion to half an image pixel is a conservative starting point for evaluating sharpness, not a verification standard.

Consider an illustrative inspection with these requirements:

• Field width along motion: 96 mm.
• Horizontal image width: 2400 pixels.
• Minimum module width: 0.32 mm.
• Maximum object speed: 1500 mm/s.
• Initial blur allowance: 0.5 pixel.

The arithmetic is:

An initial optical pulse target of 12 microseconds would produce approximately:

These are application calculations, not specifications for any product below. Validate the sampling and blur allowance using actual symbols, including the smallest modules and least favorable print contrast.

Use the resolution calculator to check the pixel requirement before narrowing the reader selection.

For the broader relationship between integration time and motion, use the moving-part exposure guide.

Check the optical pulse inside the exposure window

A short electrical trigger does not automatically create a short, correctly timed optical pulse. Controller delay, light rise time and camera trigger latency all affect the image.

With sufficiently suppressed ambient illumination, a pulse contained within a global exposure window can determine the effective motion-freezing interval. Under continuous illumination, the camera's exposure time determines that interval instead.

Consider an illustrative timing budget:

1. Set the active camera exposure window to 20 microseconds.
2. Start a 12-microsecond optical pulse 4 microseconds after exposure begins.
3. Finish the optical pulse at 16 microseconds.
4. Leave 4 microseconds of nominal clearance at each exposure boundary.

If relative timing uncertainty is 2 microseconds, the nominal clearance leaves only 2 microseconds at the affected boundary. Check the worst-case optical waveform, not just the configured delay.

A pulse longer than exposure can still produce an image if it covers the entire integration interval. However, motion blur then follows the illuminated exposure interval, and electrical heating still reflects the full pulse duration. A long pulse is not a substitute for calculating both quantities.

Where documented, use an exposure-active output or a common hardware timing source. If the camera does not respond to the intended trigger, follow the camera trigger-line configuration checks before adjusting illumination.

Rolling-shutter acquisition requires a separate timing assessment because rows may integrate at different times. A short flash can create uneven bands unless the documented acquisition mode supports the required timing.

Select lighting geometry before adding intensity

More light cannot recover bars hidden by a saturated reflection. Establish a geometry that preserves the quiet zone and module boundaries across the permitted package positions.

For initial trials, bar lights allow you to vary illumination angle without moving the camera. Compare a directional arrangement against a diffused arrangement using the same sample set. Use the lighting finder to narrow the physical format after those trials.

The LS-BAR-1047 bar light is listed as Type Standard. The LS-BAR-1276 bar light is listed as Type Diffused.

These are geometry candidates, not a documented overdrive pairing. The supplied catalog entries do not establish their permitted pulse current, minimum pulse duration or repetitive pulse limits.

Check illumination across the entire code, including its quiet zone and the corners of the allowed reading region. Repeat with package rotation and height variation. A reflection that misses the symbol at nominal position may cross it during production.

For reflective packaging, the plastic-lid print lighting guide explains why changing illumination geometry can matter more than increasing brightness. Formal grading may constrain those choices, so confirm the measurement method first.

Match the controller to documented electrical limits

Choose light controllers by output compatibility and timing behavior, not by the largest power figure. A constant-voltage light and a bare constant-current LED assembly do not necessarily accept the same drive arrangement.

The LS-CTL-0070 controller has Strobe listed as a feature. The LS-CTL-0290 controller is described as a digital constant-voltage light controller.

Values as printed in each product's data sheet; open a part for its drawing and full specifications.

The comparison helps identify candidates, but it does not prove a safe pulse-current setting. In particular, a digital control interface does not establish hardware-trigger timing, and a strobe feature does not establish permission to overdrive a connected light.

Before selecting a pairing, obtain documentation for:

• The light's drive type, polarity and connector wiring.
• Permitted continuous current and repetitive pulse current.
• Pulse-width and repetition-rate limits at the intended current.
• Controller trigger levels, latency, jitter and minimum output pulse.
• Channel limits, shared power limits and simultaneous-channel operation.
• Behavior during missing triggers, startup and communication loss.

Use the controller finder to shortlist output types, then the controller configurator to organize the proposed pairing. Have unresolved electrical limits confirmed before energizing the assembly.

The closest companion guide covers strobe overdrive, duty cycle and timing in more detail.

Calculate repetition rate and duty cycle separately

Motion blur depends on illuminated integration time. Electrical duty cycle depends on the complete output pulse and how often it occurs. Keep those calculations separate.

Suppose the illustrative process requires 80 images per second, with one pulse per image:

That low calculated duty cycle does not authorize a particular peak current. Semiconductor peak limits, internal light electronics and controller output behavior still apply. A short pulse can exceed a component limit even when average power appears modest.

Include every pulse source. Two lighting exposures per item double the pulse frequency at the same item rate. Retries and closely spaced products can also create bursts that differ from the average production rate.

For approximately rectangular pulses, average electrical power is roughly pulse voltage multiplied by pulse current and duty cycle. This estimate is useful for checking an energy budget, but it does not replace the documented pulse envelope or thermal limits.

Check reader throughput without confusing it with decode count

The reader must acquire the required images, complete processing and deliver a decision before the reject deadline. A code-per-second figure is not automatically an independent image-trigger rate.

Browse fixed code readers through the camera and reader finder, but compare acquisition timing separately from interface and resolution.

The LS-CRD-0028 fixed code reader is listed at 30 fps and 60 codes/s, with a Global shutter.

The worked example requires 80 separate acquisitions per second. The published frame-rate entry therefore does not meet that requirement; the higher code-count figure does not resolve the difference. This reader belongs in a slower-process comparison unless a separately documented operating mode meets the actual acquisition requirement.

Also check external-light synchronization, exposure adjustment, trigger buffering and decision-output latency. None should be assumed from resolution or shutter type alone.

For the processing and data-validation stages after acquisition, use the camera barcode decoding workflow.

Validate sharpness and measurement stability

Lock exposure, gain and lighting settings during comparison tests. Otherwise automatic adjustment can conceal whether a change improved illumination or simply increased amplification.

Capture stationary and moving samples at the same geometry. Compare edges along the motion direction, decoder consistency and the stability of any measured symbol characteristics. Include several print batches rather than one unusually good label.

Next, acquire images with the strobe disabled while leaving exposure unchanged. Inspect whether ambient illumination contributes recognizable edges or a smeared background. If it does, the short flash alone does not describe the image's motion exposure.

Check for saturated pixels in bright modules or substrate regions. Increasing gain cannot restore clipped detail or establish calibrated reflectance. Matching one contrast value on one reference target does not, by itself, validate the full grading method.

Preprocessing can help locate a symbol or normalize an image for reading. However, resizing, sharpening or thresholding can alter measurements relevant to grading. Keep the qualified measurement path distinct from optional decoder preprocessing; the barcode preprocessing guide addresses that separate task.

Use a release checklist before ordering

The usual answer is not always a shorter, brighter flash. Continuous illumination may be sufficient at lower speeds, while glare may require geometry changes. Formal verification may require a dedicated measurement arrangement rather than adapting a general reader.

Use this checklist to close the design:

• Inspection claim: distinguish readability, content validation and standardized grading.
• Sampling: calculate pixels per smallest module at the widest permitted field.
• Motion: include maximum speed, vibration and movement during exposure.
• Timing: verify optical pulse overlap and worst-case relative jitter.
• Electrical compatibility: obtain documented limits for the specific light-controller pairing.
• Repetition: include retries, multiple exposures and burst spacing.
• Throughput: verify acquisition rate and decision deadline independently.
• Image evidence: retain stationary, moving, strobe-off and difficult-sample images.
• Measurement evidence: define calibration checks and acceptance criteria where grading is claimed.

Start a lighting configuration once the geometry and pulse budget are known. If the documentation does not establish a compatible pairing, send the speed, module size, field width, required trigger rate and inspection objective through applications support before selecting parts.