2. Crash test facility and sled infrastructure

A full-scale crash test is only as trustworthy as the facility that hosts it. Before any instrumentation channel is zeroed or any dummy is seated, the track, tow system, barrier, lighting, and data acquisition (DAQ) room must all be verified as a coherent measurement environment. This section walks through the physical and architectural layers of a crash test facility, focusing on how each subsystem constrains what you can measure and how you should prepare for a run.

Test Track Layout and Geometry

A typical full-scale crash test track is a straight, level runway 200–300 m long and 6–10 m wide, surfaced with reinforced concrete or high-friction asphalt. The first 30–50 m form the staging and acceleration zone, where the tow vehicle or sled is released and brought to target speed. The middle section is the measurement zone, containing the impact point, barrier, and camera positions. The final 50–80 m is the deceleration and recovery zone, where the tow system is braked or the test article is allowed to run out.

Track grade must be held within ±0.5% over the measurement zone; a 1% grade over 20 m introduces roughly 0.1 g of unintended longitudinal acceleration, which contaminates low-severity occupant metrics. Lateral alignment is equally critical: the impact point is usually marked with a laser or chalk line, and the test article's centerline must be aligned to within ±25 mm of the barrier target. For offset deformable barrier (ODB) tests, the 40% overlap is set by a jig, not by eye.

Tow Systems: Acceleration and Release

Two tow architectures dominate. Cable-and-winch systems use a steel cable wound on a hydraulic or electric winch; the tow vehicle is pulled to speed and released by a quick-release shackle. Linear motor or pneumatic sled systems accelerate a guided sled directly, which is standard for component-level sled tests. In both cases, the tow force profile determines the pre-impact velocity and the residual yaw at release.

A practical example: to reach 64 km/h (17.8 m/s) over a 40 m acceleration distance, the required average acceleration is a = v²/(2s) = 17.8²/(2×40) ≈ 3.96 m/s² ≈ 0.40 g. If the tow system can only deliver 0.30 g, the acceleration distance must increase to about 53 m. This is why track length and tow capability are specified together, not independently.

Release timing is the most common source of velocity error. The quick-release must fire within ±5 ms of the target trigger, and the tow cable must not impart lateral impulse. After release, the test article coasts; aerodynamic drag and rolling resistance reduce speed by roughly 0.5–1.5 km/h over the final 10 m, which must be accounted for in the target speed calculation.

Barriers and Impact Surfaces

The barrier defines the boundary condition of the crash. Common types include:

• Rigid concrete wall — used for full frontal and side impact; effectively infinite stiffness, so all deformation occurs in the vehicle.
• Deformable barrier (MDB/ODB) — a honeycomb or aluminum honeycomb-faced trolley that absorbs energy and mimics a vehicle front end.
• Pole and narrow object — rigid cylinder for side pole and roof crush tests.
• Moving deformable barrier (MDB) — a trolley carrying a deformable face, used in side impact; its mass and velocity are part of the test specification.

Barrier anchoring matters as much as barrier type. A rigid wall must be bolted to a foundation rated for the peak impact force — for a 1,500 kg vehicle at 64 km/h, peak force can exceed 500 kN. Any compliance in the anchor system appears as extra deformation in the force-displacement curve and biases occupant loading.

Lighting and High-Speed Imaging

High-speed cameras at 1,000–10,000 fps need enormous light. A typical setup uses 2–4 kW HMI or LED floodlights per camera, positioned to produce even illumination without shadows on the impact face. Color temperature should be matched (5,600 K) so that white balance is consistent across cameras. Flicker is a real risk: mains-powered lights at 50/60 Hz can produce banding at high frame rates, so DC-driven or high-frequency ballast lights are preferred.

Camera placement follows the measurement plan: frontal, side, overhead, and onboard. Each camera needs a rigid mount isolated from track vibration, and a calibration frame (grid or cube) is filmed before the test to allow photogrammetric reconstruction of dummy kinematics.

Data Acquisition Room Architecture

The DAQ room is the electromagnetic and logical heart of the facility. Its architecture has four layers:

1. Transducer layer — accelerometers, load cells, potentiometers, and pressure sensors on the vehicle, dummy, and barrier.
2. Signal conditioning layer — amplifiers, anti-alias filters, and bridge completion, usually located near the transducers or in an onboard DAQ module.
3. Digitization layer — onboard or trackside DAQ recording at 10–20 kHz per channel with 16-bit resolution.
4. Control and storage layer — the control room, where the test conductor arms the system, triggers the tow release, and monitors real-time channels.

Grounding and shielding are not optional. A single-point ground reference for the DAQ, isolated from the tow system's power ground, prevents ground loops that appear as 50/60 Hz noise on low-level accelerometer channels. Cable runs should be twisted-pair, shielded, and routed away from motor and winch power cables.

1. Verify all channels zeroed with vehicle at rest.
2. Confirm sample rate ≥ 10 kHz and anti-alias filter at 1/3 sample rate.
3. Check trigger source: tow release contact + backup optical gate.
4. Record 2 s pre-trigger and 5 s post-trigger minimum.
5. Verify camera sync pulse shared with DAQ time base.
6. Confirm single-point ground and shield continuity.
7. Arm system, confirm "ready" status, then release tow.

Integrated Facility View

The SVG below shows how the track, tow system, barrier, lighting, and DAQ room connect as one measurement chain. The key insight is that the trigger signal originates at the tow release and must reach both the DAQ and the cameras within the same time base; any latency between them corrupts the synchronization between force data and video.

Practical Verification Before a Run

Facility readiness is confirmed by a dry run: tow the vehicle at low speed (10–15 km/h) without impact, and check that all channels record, the trigger fires, and camera sync is within one frame. If a channel shows 50/60 Hz noise, inspect the ground reference and cable routing first. If the trigger timestamp drifts between DAQ and video, verify the shared sync pulse and cable length compensation. These checks take 20–30 minutes and routinely prevent the loss of an entire test day.