LED strobe current droop: diagnose pulse startup

A light pulse can reach its commanded current, dip shortly afterward, and then recover before the pulse ends. For machine-vision integrators, that behavior can produce inconsistent images even when the trigger and exposure settings remain unchanged. Diagnose the electrical waveform before changing the camera. The process below separates supply limitations, wiring losses, pulse loading, and controller settling, then explains when a manufacturer-documented preconditioning setting deserves evaluation.

Identify what is actually dropping

Start by distinguishing LED current, controller input voltage, and image brightness. They describe different parts of the system. A darker image alone does not prove that current decreased.

Record the trigger, LED current, and controller input voltage on the same time base. Where possible, capture supply-terminal voltage simultaneously. Use a compatible current probe or the manufacturer's documented current-monitoring method. An external monitor may have limited bandwidth, so confirm that it can resolve the feature being investigated.

For image-only symptoms, use the first-frame darkness diagnosis before attributing the fault to the light controller.

Check supply headroom at the controller input

Measure voltage at the controller terminals, not just at the supply. The controller receives the voltage remaining after cable and connector losses.

Check the documented input range and the operating conditions attached to it. A voltage inside the absolute input range does not necessarily provide the required performance at every output current and load voltage.

Controller topology matters. Some designs require input voltage above the LED load voltage, while others can raise the output voltage internally. Do not apply a universal rule that the supply must exceed the LED voltage by a fixed margin. Use the selected controller's documented load envelope.

Capture the complete pulse, including the leading edge and recovery. A supply may briefly sag, enter a limiting mode, and recover while a handheld meter reports an acceptable average.

If the supply output itself falls, check its transient-load capability, current-limit behavior, and any documented derating. Also check whether other loads switch at the same instant. Follow documented procedures before testing a dedicated supply; do not disconnect required protective connections.

Separate wiring losses from supply behavior

A healthy supply cannot compensate for excessive loss between its terminals and the controller. Include both conductors, connectors, terminals, and any distribution components in the measurement.

For a first estimate, treat the complete supply-and-return path as a resistance:

Suppose the measured input current reaches 8 A and the complete wiring loop measures 0.20 ohm. The estimated resistive loss is:

That is a wiring estimate, not a controller specification. Fast edges can also produce inductive voltage disturbances, so resistance alone does not explain every transient.

Measure the actual voltage difference during the pulse. Correct loose or damaged connections, and select conductor size and routing using the equipment documentation and applicable electrical requirements. Avoid changing several connections at once; otherwise, the improvement cannot be traced to its cause.

For trigger-side electrical questions, the camera GPIO wiring checks explain a separate fault path. A valid trigger does not establish that the power path is adequate.

Calculate pulse loading, not just average current

Long pulses can demand sustained power rather than a brief energy burst. Repetition rate then determines how much recovery time remains between pulses.

For identical, nonoverlapping rectangular pulses:

These estimates assume approximately constant voltage and current during the pulse, with negligible LED power between pulses. They describe the load side, not the complete supply requirement.

Consider an illustrative load operating at 18 V and 6 A for 0.25 s, repeated twice per second:

The load requires approximately 108 W while illuminated, despite averaging 54 W across the cycle. Supply selection must also account for controller losses, other loads, and documented transient requirements. Average power alone cannot establish compatibility.

Now suppose the measured current falls from 6.0 A to 5.1 A near pulse startup:

Record how long that dip lasts and whether it overlaps image exposure. Do not assume that a 15% electrical-current change produces exactly the same percentage change in pixel intensity.

The strobe duty-cycle and timing guide covers the related operating-envelope checks. For motion-driven exposure selection instead, use the barcode strobe pulse-sizing article.

Test controller settling and configuration changes

Once input voltage is stable, investigate whether the dip depends on the controller's recent operating state.

Compare these conditions without exceeding any rating:

1. The first pulse after power-up.
2. The first pulse after a current or pulse-duration change.
3. Later pulses with the configuration unchanged.
4. A pulse after a long idle interval.
5. A pulse after the normal production interval.

Read back supported settings after writing them. A successful software command does not always mean that every requested value has become active. Check documented status information and any required configuration-settling interval.

If only the first pulse after a change is affected, controller initialization or internal regulation settling becomes more plausible. If every pulse sags when another channel fires, shared loading becomes more plausible. Neither observation proves the cause without the corresponding voltage and current measurements.

Keep camera gain, exposure, and image processing fixed during this test. If electrical current is repeatable but image intensity still varies, the closed-loop lighting control explanation helps distinguish electrical regulation from optical repeatability.

Evaluate documented preconditioning settings carefully

Some controller designs offer a documented preparation or preconditioning function that establishes internal operating conditions before the main pulse. Such a function may help when the regulation system starts from an unsuitable initial state. It cannot repair insufficient supply capacity, excessive cable loss, or an incompatible light.

Before enabling anything, obtain the manufacturer's documentation for the exact controller hardware and firmware revision. Confirm:

• Whether the function exists on that revision.
• Which current, pulse-duration, and repetition limits apply.
• Whether preparation emits light or changes trigger latency.
• Whether additional energy or duty-cycle restrictions apply.
• What must happen after configuration changes or power cycling.

Record the original configuration, then change only the documented setting under evaluation. Repeat the same waveform capture and compare droop magnitude, recovery time, trigger latency, and pulse-to-pulse repeatability.

Do not disable protection, shorten a mandatory recovery interval, or raise current to hide the dip. If a requested operating point is rejected, obtain a documented supported configuration or select different hardware.

Firmware and instructions should come from the manufacturer or its authorized distributor. An application note about another controller does not establish support on the installed unit.

Choose controller and supply candidates by verified capability

Use light controllers as a starting category, then narrow candidates through the light-controller finder. Distinguish constant-current regulation, constant-voltage output, and documented strobe operation. These labels answer different questions.

The LS-CTL-0180 is listed as a digital constant-current controller. That catalog classification alone does not establish its pulse response or support for a preconditioning function.

The LS-CTL-0070 is listed with a Strobe feature and Constant voltage 24 V output. That listing does not establish current regulation through a particular LED load or support for a preparation mode.

Treat these as examples of catalog distinctions, not interchangeable solutions or confirmed matches for the worked example. Request the missing pulse-envelope and electrical-interface information before selecting a part.

For the input source, review power supplies through the accessory finder. Match the documented input requirements, transient loading, and connection requirements rather than selecting solely by nominal output power.

Do not add external capacitance unless the relevant documentation permits it. Additional capacitance can alter startup current, protection behavior, and system stability.

Verify the correction with repeatable captures

A waveform that improves once is not yet a validated correction. Repeat the operating states that originally exposed the problem.

Capture a batch of 20 consecutive pulses as an initial screening test, then repeat after an idle interval and after a permitted configuration change. This sample size is a practical starting point, not a reliability qualification.

Record the following for each condition:

• Minimum controller input voltage.
• Commanded and measured plateau current.
• Lowest current during the startup disturbance.
• Time required to enter the application's acceptable current band.
• Trigger-to-light delay and its variation.
• Image intensity over a fixed region with unchanged camera settings.

Define the acceptable band from the inspection requirement and documented equipment capability. For example, a project might require current within ±5% during exposure, but that is an application criterion, not a universal controller specification.

Retain the waveform files, firmware identification, configuration readback, and wiring arrangement. These make vendor support requests much more actionable than a report that the light occasionally dims.

Know when the usual diagnosis is wrong

A startup dip is not always a supply problem. If the input voltage remains stable, a larger supply may change nothing. Likewise, increasing commanded current may deepen a limiting event rather than restore a flat pulse.

If current stays stable while optical output falls, investigate LED temperature behavior and the light's documented operating limits. If brightness varies only in images, check exposure overlap, automatic camera controls, saturation, and processing changes.

Measurement errors can also imitate droop. Check current-probe zero, bandwidth, saturation, and any droop specification relevant to the pulse duration. Compare against a documented alternative measurement method when the waveform looks implausible.

Finally, a disturbance outside the exposure window may not explain the inspection fault. It still needs an electrical compliance check, but the camera problem may have a separate cause. Do not shift exposure merely to conceal an operating-limit violation.

Finish with a supported operating-point checklist

Before ordering hardware or accepting a settings change, confirm these items:

• Supply: terminal voltage and transient performance support the complete pulse sequence.
• Wiring: measured loop loss leaves adequate controller input margin.
• Controller: the load, current, duration, and repetition rate fall within documented limits.
• Light: peak current, pulse duration, and duty cycle are permitted together.
• Configuration: startup and post-change behavior are understood and repeatable.
• Preconditioning: any preparation function is explicitly supported and remains within rated limits.
• Verification: electrical captures and fixed-camera images both meet the inspection requirement.

Follow the light's optical-safety instructions during testing, and do not open power supplies to diagnose an external waveform.

Start the controller configuration process with the measured load and pulse requirements, or send the waveform evidence through technical support for a compatibility review.