Your camera's strobe output switches the light on only while the sensor integrates. At a 6 µs exposure the pulse on the wire is barely wider than the integration itself — too short for many light controller trigger inputs, and shorter than some drivers need just to register the edge. You want the line high for 200 µs while the exposure stays at 6 µs. The counter section of a GenICam feature tree does exactly this: sourced from the megahertz tick and triggered on exposure start, it holds the output line active for a duration you set in counts. This how-to gives the settings, the tick arithmetic, the duty-cycle ceiling, the bench checks and the fallbacks for cameras without a counter.
Why the default pulse ends with the exposure
Out of the box, the strobe line is sourced by the exposure: high while the sensor integrates, low when it stops. Your short exposure therefore puts an equally short pulse on the wire. For the image that is correct — pixels only need light while they collect charge. For everything downstream of the camera it is usually too short.
Two things fail first. Opto-isolated trigger inputs on industrial light controllers commonly specify a minimum pulse width in the 10–100 µs band, so a 6 µs pulse may never register and the light never fires at all. The pulse also often has other consumers — a PLC input, a reject handshake, a second camera — that need tens of microseconds to react to such a fast edge.
Stretching the output does not stretch the image. The sensor still integrates for its full 6 µs, so a part moving at 300 mm/s keeps its 300 mm/s × 6 µs = 1.8 µm motion blur, and the noise benefits of a short exposure stay too. The camera strobe output timing guide maps the pulse against exposure and timestamp, and how strobe pulse width freezes motion blur explains why a wider drive pulse never softens the image.
What you need
- A camera whose GenICam tree contains the counter section: Counter Selector, Counter Event Source, Counter Trigger Source and Counter Duration. Counter support is a per-model feature, so search the tree for "Counter" before planning the wiring.
- Your camera SDK's GenICam feature browser — every major SDK ships one.
- A light controller with an external strobe or trigger input; the light controllers finder filters for strobe-capable models.
- Wiring matched to the controller input: the TTL levels and pull-ups guide covers 3.3 V, 5 V and 24 V inputs and the series resistor choice.
- An oscilloscope, or a spare camera input line for the loopback check described below.
A digital control box with a strobe feature takes the camera pulse on its trigger input and does the switching:
- Output
- Constant voltage 24 V
- Channels
- 4 channels
- Control
- Digital
- Feature
- Strobe
Set the counter to time the pulse
- Open the feature tree in your SDK's GenICam browser and search for "Counter". If no counter features appear, jump to the no-counter section below.
- Set "Counter Selector" to "Counter 0".
- Set "Counter Event Source" to "MHzTick". The counter now counts 1,000,000 ticks per second, so one tick is 1 µs. A GenICam counter can count events or ticks; sourcing it from the tick turns it into a stopwatch.
- Set "Counter Trigger Source" to "Exposure Start". The counter restarts on every frame, which makes the pulse repeat without further configuration.
- Set "Counter Duration" to 200. The unit is counts, not microseconds — the tick rate does the conversion shown in the formula block below.
- Open the digital I/O line settings, select the line wired to your light — Line 2 in a single-light layout — and set its "Line Source" to "Counter 0 Active". The line now carries the counter's active window instead of the exposure window.
- Set the line as an output and match its electrical level to the controller input before powering the light side.
These settings produce a 200 µs high pulse that starts at every exposure:
The duty-cycle table and the 5,000 fps ceiling
The timeline with these settings: the line rises at exposure start (t = 0), the exposure closes at 6 µs, and the counter keeps counting until the line falls at 200 µs. The light sees a pulse about 200 ÷ 6 ≈ 33 times longer than the exposure, and the driver sees an edge it can actually register.
| Line rate | Frame period | Duty cycle |
|---|---|---|
| 100 fps | 10 ms | 2% |
| 500 fps | 2 ms | 10% |
| 1,000 fps | 1 ms | 20% |
| 2,500 fps | 400 µs | 50% |
| 5,000 fps | 200 µs | 100% — never off |
Duty is the light's average on-fraction: 0.0002 s × 500 fps = 0.1, so 10% of every second. Average LED power scales with it, and keeping duty low is exactly why strobe mode extends LED lifetime.
The table also sets the ceiling. The pulse needs a frame period longer than its own 0.0002 s, so keep the line rate below 1 ÷ 0.0002 s = 5,000 fps. At exactly that rate the pulse fills the whole period, the light runs effectively continuous and the strobing benefit is gone. Full-resolution GigE models sit well below that anyway; small-ROI builds can reach it.
Prove the pulse before production
Put a scope across the controller's trigger input and trigger the camera once: expect a high time of 200 µs within a couple of microseconds. The residual error is the 1 µs tick granularity plus edge delays — a few microseconds in total on a healthy set-up.
Without a scope, loop the pulse into a spare input line and grab one frame while reading the camera's GPIO input and output pins at the same time: the input edge timestamps the pulse you sent. To check the light rather than the wire, a fast photodiode in the light path shows the optical pulse — the LED strobe rise time guide gives the measurement method. If the short drive looked dim and the stretched drive fixed it, the array was probably drooping at pulse start; the LED strobe current droop guide shows how to confirm it.
When your camera has no counter
Search the tree for "Timer" as well. Cameras with a timer section do the same job through a timer selector and a duration value in microseconds, with identical wiring on the line side.
Some cameras shorten the path further with a strobe duration parameter on the output line itself. One line scan family documents 0 to 5,000 µs in 1 µs steps, and a value of 0 means the strobe simply follows the exposure — set 200 and you are done. Smart cameras often expose their strobe line through a plain enable-and-wire setting; the smart camera strobe output guide shows that path.
With neither feature, widen the pulse outside the camera. PLC timer logic for a fixed-duration output pulse re-triggers a longer pulse from the camera's short edge, and a 555 timer monostable strobe driver does the same job in hardware when no PLC sits in the panel. For buffering in the pulse path, the buffer relay between camera and strobe guide covers when a relay or PLC module belongs there.
Choose the duration before you set 200
Size the pulse from three lower bounds and one ceiling. Lower bounds: the driver's minimum trigger width, commonly 10–100 µs on opto-isolated inputs; the LED settle time, under 1 µs for small LEDs and a few to a few tens of µs for high-current arrays through a driver; and the slowest device sharing the pulse, often a PLC scan needing tens of microseconds. Add roughly 50% margin on the largest and you land at 100–200 µs, which is why 200 counts is the default worth standardizing on. Ceiling: line rate ≤ 1 ÷ duration, so 5,000 fps at this pulse width.
One catch: a longer pulse after exposure start does not light the exposure itself — the LED is still ramping during the first microseconds either way. If the light must already be at full output when the exposure opens, use an output delay or an earlier trigger event if the camera offers one, then repeat the photodiode test to measure the true on-delay.
Checks before you close the panel
- "Counter Event Source" reads "MHzTick" and "Counter Duration" reads 200 — a wrong tick source rescales the whole pulse.
- The output line's "Line Source" reads "Counter 0 Active", not the exposure source.
- Line rate below 5,000 fps and duty inside the light's strobe rating.
- Scope or loopback shows the full stretched pulse at the controller input.
- Camera exposure still reads 6 µs and image brightness sits on target.
Parts for the switched side
The pulse comes from the camera; the switching happens in the controller. A 4-channel, 200 W digital control box such as the LS-CTL-0070 takes the strobe input directly. For a current-controlled array, the 2-channel, 240 W LS-CTL-0487 runs constant current off the same pulse, and the 400 W LS-CTL-0264 drives two high-power heads over its network option.
- Output
- Constant current, Constant voltage 24 V
- Channels
- 2 channels
- Control
- Digital
- Channels
- 2 channels
- Control
- Digital
- Feature
- High power
- Output
- Constant voltage 24 V
Size the whole chain — camera, pulse settings, controller, cabling — in the lighting configurator or the light controller finder. More strobe timing guides sit on the lighting topic page, and if the camera side is due for replacement the area scan cameras finder narrows by interface, resolution and shutter. If the pulse math will not close for your frame rate, describe the timeline through the contact page and we will run the numbers with you.
Questions
How many counts equal 200 µs at the MHz tick?
With Counter Event Source set to MHzTick the counter adds one count per microsecond, so 200 counts are exactly 200 µs. The conversion is one-to-one for any microsecond target: 50 µs needs 50 counts and 5 ms needs 5,000. If a camera only offers a slower tick, divide the target time by the tick period instead — 200 µs at a 0.1 µs tick is 2,000 counts.
What duty cycle does a 200 µs strobe add at high frame rates?
Multiply the pulse by the frame rate. At 250 fps the light is on 200 µs × 250 = 50 ms per second, a 5% duty cycle; at 2,000 fps it reaches 40%. Keep the average power inside the light's strobe rating, which its specification states as a maximum duty figure — strobe-mode thermal behavior is what LED lifetime figures assume.
My camera's output line only mirrors the exposure — can the light still stay on longer?
Not from that line: it follows the sensor and drops right after integration ends. Either widen the pulse outside the camera — a PLC timer or a hardware one-shot re-triggered by the short edge — or choose a model whose feature tree contains the counter section. Counter support is listed per model, so settle it before wiring the panel.
Can one counter pulse trigger two light controllers at once?
Yes, if the output can supply both trigger inputs. Opto-isolated inputs draw a few to roughly 20 mA each, so two in parallel normally works; more than that, or a mix of voltage levels, needs a small buffer stage. Keep the inputs wired in parallel and both lights inside the same pulse window so brightness matches frame to frame.
Does a longer strobe pulse shorten the LEDs' life?
Life follows duty cycle, not pulse width alone. A 200 µs pulse every 10 ms heats the array exactly like a 10 µs pulse every 1 ms — both are 2% on-time. Inside the rated duty, strobing keeps the junction cooler than continuous operation, which is why the L70 lifetime improves in strobe mode; the limit to respect is the maximum duty cycle.


