2. High-speed video capture for airbag deployment

Airbag deployment is one of the fastest events you will ever need to measure in a vehicle safety laboratory. From the moment the ECU fires the squib to the instant the cushion reaches full inflation, the entire sequence typically completes in 30–80 ms. Capturing that sequence in a way that supports quantitative CAE correlation — not just a visually impressive clip — requires deliberate choices about camera selection, frame rate, resolution, lighting, synchronization, and calibration. This section walks through each of those decisions and shows how they interact.

Camera Selection and Sensor Architecture

Two camera families dominate airbag deployment testing: high-speed CMOS cameras with global shutters, and (less commonly) high-speed CCD cameras. For airbag work, a global shutter is mandatory. A rolling shutter exposes rows sequentially, so a cushion moving at 200–300 m/s across the frame will be skewed by several pixels per row — an error that directly corrupts any displacement or velocity measurement. Global-shutter CMOS sensors expose all pixels simultaneously, eliminating that artifact.

Sensor size and pixel pitch matter as much as headline resolution. A 1-inch sensor with 10 µm pixels collects far more light per pixel than a 1/2-inch sensor with 3 µm pixels, which means you can run shorter exposure times without unacceptable noise. For airbag work, exposure times of 1/5000 s to 1/20000 s are common; at 1/10000 s, a cushion surface moving at 250 m/s travels 25 mm during exposure, so motion blur is already a real concern. Larger pixels buy you the light budget to keep exposure short.

Memory depth is the practical constraint. A camera shooting 1280×1024 at 10,000 fps generates roughly 13 GB/s of raw data. Most high-speed cameras buffer to internal RAM (typically 8–64 GB) and then download after the event. You must calculate whether your desired resolution, frame rate, and record duration fit within that buffer. A typical airbag test records 200–500 ms of pre-trigger and post-trigger data, which at 10,000 fps and 1 MP is 2–5 GB — comfortably within a 32 GB buffer.

Frame Rate and Resolution Trade-offs

The frame rate must be high enough that the fastest feature you need to track moves less than a few pixels between frames. As a rule of thumb, target at least 10 frames across the fastest transient. If the cushion fabric accelerates to 250 m/s and you need to resolve its motion to within 5 mm, then at 10,000 fps the cushion moves 25 mm per frame — too coarse. At 20,000 fps it moves 12.5 mm per frame, and at 40,000 fps it moves 6.25 mm. The right number depends on your measurement goal.

Resolution and frame rate trade against each other on the same sensor. Reducing the region of interest (ROI) is the standard way to buy frame rate: a camera that does 10,000 fps at full 1280×1024 may reach 40,000 fps at 320×256. For airbag work, you often only need to see the cushion and the occupant's head, so a cropped ROI is usually acceptable. The table below summarizes typical configurations.

Lighting

At 1/10000 s exposure, you need enormous illuminance. Tungsten and halogen lamps are too slow to reach full output and too hot; the standard solution is high-intensity LED or metal-halide continuous lighting, often 2–8 kW per camera position. LEDs are preferred because they can be strobed in sync with the camera exposure, which both increases peak intensity and reduces heat load on the test article.

Lighting geometry matters for quantitative work. Backlighting produces a silhouette that is ideal for edge detection and displacement tracking, but it hides surface texture. Front lighting reveals fabric weave and seam detail but creates specular highlights that can confuse tracking algorithms. A common compromise is diffused front lighting plus a backlight panel behind the cushion, giving both edge contrast and surface visibility. Avoid direct on-axis light, which produces hot spots that saturate the sensor and destroy local contrast.

Synchronization

Every camera, light, and data channel must share a common time base. The standard approach is a central trigger generator that issues a TTL pulse at T=0 (squib fire) and distributes it to all cameras, the data acquisition system, and the lighting controller. Cameras run in external-trigger mode so that frame 1 of every camera corresponds to the same instant.

Even with a common trigger, you must verify synchronization. A simple method is to place a flashing LED or a rotating slotted disc in the field of view of every camera; the LED is driven by the same trigger generator, so any frame offset between cameras shows up as a phase difference in the LED's position. For stereo or multi-view setups, residual sync error should be under one frame interval — at 10,000 fps, that is 100 µs.

Calibration Targets

Quantitative analysis means converting pixel coordinates to millimeters. That requires a calibration target with known geometry, imaged in the same plane as the motion you care about. For 2D analysis, a dot grid or checkerboard with a known pitch (e.g., 20 mm) is sufficient. For 3D or stereo, you need a target that presents features at multiple depths — a 3D calibration frame with markers on orthogonal planes.

The calibration target must be rigid, flat, and positioned so that it fills the measurement volume. After capture, you run a calibration solve (using the camera model and the known marker positions) to obtain the intrinsic parameters (focal length, principal point, distortion) and extrinsic parameters (camera pose). The residual reprojection error should be under 0.5 pixels for a good solve. If it is higher, check for target flex, insufficient marker coverage, or a lens with strong uncorrected distortion.

Putting It Together: A Worked Configuration

Consider a driver-side airbag test where the goal is to correlate cushion seam displacement with CAE predictions. A reasonable starting configuration is:

• Cameras: two global-shutter CMOS cameras, 1280×1024, 10,000 fps, 1-inch sensor, 50 mm lens, positioned for a stereo view of the cushion.
• Lighting: two 4 kW LED panels diffused from the front, one 2 kW backlight panel behind the cushion.
• Exposure: 1/10000 s, aperture f/4, ISO 3200 (or equivalent gain).
• Synchronization: central trigger generator, TTL fan-out to both cameras, LED controller, and DAQ. Verify with a flashing LED in both fields of view.
• Calibration: 3D calibration frame with 20 mm marker pitch, imaged before the test. Solve for intrinsics and extrinsics; accept if reprojection error < 0.5 px.
• Recording: 300 ms total (100 ms pre-trigger, 200 ms post-trigger) at 10,000 fps = 3,000 frames per camera. At 1.3 MP and 10-bit, that is roughly 3.9 GB per camera — within a 32 GB buffer.

After the test, download the frames, apply the calibration solve, and run a tracking algorithm (e.g., normalized cross-correlation or feature-based optical flow) on the seam markers. The output is a time series of 3D coordinates, which you can differentiate to get velocity and acceleration, then overlay against the CAE prediction. If the tracking loses the seam during the fastest phase, the usual causes are insufficient lighting (check saturation), motion blur (shorten exposure), or a calibration error (check reprojection residual).

The configuration above is a starting point, not a universal recipe. The correct frame rate, resolution, and lighting depend on what you need to measure. The discipline is to work backward from the measurement requirement: define the smallest feature and the fastest motion, then choose the frame rate and resolution that resolve them, then choose the lighting and exposure that make those settings viable, and finally verify synchronization and calibration before you ever fire a squib.