A machine vision LED trigger circuit has two jobs that must be verified together: deliver the required optical pulse and place that pulse inside the camera’s useful exposure interval. A clean logic pulse at a connector proves neither. Input conditioning, driver startup, cable impedance, LED current rise and sensor timing can each change the light actually captured by the image.
This guide treats the trigger path as a measurable timing and energy chain. It is aimed at engineers building an inspection light controller or integrating a lighting board with a camera. The output is a timing budget, a pulse-energy calculation and an acceptance record that can travel with prototype and production files. General continuous-current topology selection remains with the LED driver circuit design guide; a strobe requires additional transient and synchronization checks.
Budget the optical pulse from the exposure requirement backward
Define the window that matters to the sensor
Record the camera model, shutter mode, exposure setting, region of interest and selected output signal. A trigger command, exposure-active signal and flash-window signal can describe different events. The correct signal depends on camera behavior, not just the availability of an output pin. Save the camera configuration alongside the controller firmware so a change in acquisition mode does not silently invalidate the lighting setup.
distinguishes exposure-active and flash-window behavior. For rolling shutters, the useful common exposure interval needs particular attention; global-shutter behavior differs. Confirm support and timing for the exact camera model. Do not assume a signal with a familiar name means that every pixel is integrating throughout that entire signal.
Begin with an optical requirement: allowable motion blur, required image contrast and the useful illumination interval. Then allocate electrical timing to satisfy it. If the light is bright enough but late, increasing current does not solve the missing overlap. If the pulse is well timed but has a long sloping leading edge, nominal pulse width can overstate the useful exposure at the intended light level. The acceptance definition should say which portion of the optical waveform counts.
Separate fixed latency, jitter and edge settling
Fixed latency can often be compensated when it is stable and the interface allows a programmable offset. Jitter cannot be removed by subtracting one average number. Rise and fall behavior are another contribution: the light may be present before it reaches the required level, and remain after the command ends. Record minimum and maximum latency, edge times and pulse width across operating conditions rather than using a single oscilloscope screenshot as the complete specification.
Consider an illustrative 30 碌s usable exposure interval and a required 20 碌s optical plateau. The remaining 10 碌s is available for placement margins and uncertainty; it is not automatically ten microseconds of permissible jitter. If the plateau nominally starts 5 碌s after the window opens, it ends 5 碌s before the window closes. A bounded 卤2 碌s placement uncertainty leaves only 3 碌s margin at either limiting edge, before any additional width error is counted.
This example assumes the plateau duration is already measured optically and its edge definition is agreed. If instead the 20 碌s value describes the electrical command, the driver and emitter response must be added to the budget. A logic analyzer can capture command timing, but it cannot replace a photodetector observation. For an industrial controller board, keep that distinction in the test specification rather than labeling all timing measurements as camera synchronization.
Check the trigger’s electrical interface
Identify whether the source is a logic output, open collector, isolated output or industrial-voltage signal. Establish voltage levels, polarity, permissible current, default state and return connection from the actual camera and controller documentation. A pull-up changes rise time and current; it is not just a schematic convenience. A filtering network may reject interference but also add delay or shorten a narrow pulse. Test those effects with the cable that will be installed.
Specify behavior during power sequencing. The lighting board should have a defined safe idle state while the camera, controller and supply start in different orders. Also define what happens if the trigger remains asserted, arrives too quickly or is disconnected. A maximum-on-time control and a repetition-rate limit may be appropriate design provisions, but their implementation and limits must be chosen from the emitter and driver requirements. Software timing alone should not be assumed to constrain every hardware fault.
When reviewing the layout, keep the input threshold reference clear of pulsed power-return drops. A receiver can see an apparent extra transition when its local reference moves. The route should be reviewed as a signal-and-return pair appropriate to that interface, including protection and isolation where required. Adding a longer software debounce interval after a layout error can make the waveform look clean while violating the available exposure window.
Include the first pulse after a long idle
highlights a specific problem: long intervals between flashes can change stored charge and disturb the next short pulse. Its LT3932 example maintains relevant circuit states for repeatable flashing. That is a device-specific solution, not a reason to assume any PWM-dimmable driver will deliver the same first pulse after minutes of inactivity.
Include a cold first pulse, the first pulse after a long idle and a pulse in a sustained burst in the comparison. Measure each at the same current and optical observation points. If only the first pulse differs, investigate the driver’s startup state and energy reservoir before changing the camera timing. If every pulse moves when the cable changes, investigate the installed trigger and power path instead. A small diagnostic matrix helps distinguish these mechanisms without guessing.
Design the pulsed-current path and the acceptance test together
Use peak, average and charge calculations for different questions
For an assumed 2 A rectangular pulse lasting 20 碌s at 100 pulses per second, duty cycle is 20 脳 10鈭�6 脳 100 = 0.002, or 0.2%. The ideal average LED current is 4 mA. If the string voltage during the pulse is assumed to be 12 V, electrical energy delivered to the string is 12 脳 2 脳 20 脳 10鈭�6 = 0.00048 J, or 0.48 mJ per pulse. The corresponding ideal average string input power is 48 mW.
These small average numbers do not make the peak harmless. The LED, current regulator, connector and switching path still see the pulse. Allowed peak current depends on the emitter’s pulse conditions, junction temperature and specified limits. Average electrical power is not optical power, and neither automatically establishes junction temperature. Review the LED board construction and thermal interface using the actual emitter package, not only the calculated duty cycle.
A charge calculation answers a separate preliminary question. If a hypothetical output-side reservoir alone supplied the full 2 A for 20 碌s, the withdrawn charge would be 40 碌C. Limiting its ideal capacitive droop to 0.2 V would require C = Q/螖V = 200 碌F. That is a screening model, not a component recommendation. Real current sharing with the regulator, capacitance under bias, ESR, ESL, loop stability and the allowed output network must all be considered.
Do not apply that 2 A directly to an input capacitor in a buck converter. Input current depends on input voltage, efficiency and switching behavior. Also avoid adding a large output capacitor solely to satisfy the simple charge equation: the selected driver may have constraints that make that change unsuitable. The , for example, gives its own control, current-sensing and external-component requirements. Use the actual controller documentation when moving from screening arithmetic to circuit design.
Keep the measurement path separate from the pulse-power path
Identify the closed pulse-current loop on the schematic and then on the PCB. Include the LED cable when the emitter is remote. Minimize unnecessary loop area within the chosen topology and keep sensitive control nodes out of the switching region. Give the current-sense connections the intended terminal reference so a copper voltage drop is not mistaken for LED current. General buck-converter layout guidance supports the power-stage review, while the strobe-specific timing remains a separate acceptance task.
Reserve access for the trigger input, conditioned trigger, driver control and a suitable current measurement. Include an optical detector location or fixture reference in the test drawing. The test-point planning guidance helps keep fixture access practical. Probe loading and added inductance still need review; a measurement setup that changes the pulse cannot be treated as an invisible observer.
Check polarity and pin identity on the remote-light connector. Record cable length, wire arrangement and any shield connection. A short bench cable can conceal overshoot or delay present with the installed harness. Test an open light connection and other specified fault conditions using the device manufacturer’s procedures and an appropriate setup. Do not invent a universal hot-plug or short-circuit procedure from the fact that a driver advertises protection features.
Make production acceptance reproduce the engineering question
| Condition | Measure | Preserve in the record |
|---|---|---|
| First pulse after idle | Optical delay, plateau and current | Idle duration, supply and temperature |
| Sustained burst | Pulse variation and thermal behavior | Rate, count, mounting and airflow |
| Installed cable | Input edges, current and optical timing | Cable identity and detector geometry |
| Power sequence or invalid trigger | Idle state and bounded response | Sequence and required fault behavior |
Define numerical acceptance limits from the imaging task and component ratings before collecting the final results. A bright image alone is not a calibrated light-output measurement, but a detector waveform alone does not prove the image meets inspection needs either. Keep electrical timing, optical repeatability and application-image acceptance as three related records. This makes a failure actionable instead of reducing it to light too dim or camera missed a frame.
For assembled prototype evaluation, supply firmware, camera settings, fixture requirements and the exact LED BOM. For the bare PCB build, specify the stackup, copper and thermal-interface requirements that the released circuit relies on. Confirm which measurements are included in the quotation; the presence of this design guide does not imply that every optical or camera test is a standard manufacturing service.
A useful inquiry includes the trigger interface, required optical window, current waveform target, emitter identity, cable arrangement, quantity and unresolved design questions. Attach scope traces only with their timebase, probe setup and operating condition. Discuss the lighting-controller build and test requirements once those boundaries are clear, or identify the missing information when requesting early engineering input. The result should be a buildable and testable specification, not simply a circuit that flashes once on the bench.