What a DAQ system is: sensors, logger, ECU and sampling rates
A data acquisition system turns physical quantities into time-stamped numbers. Understanding the chain sensor → conditioning → ADC → logger, and choosing sensible sampling rates, decides whether the data can answer your questions at all.
What a DAQ system is: sensors, logger, ECU and sampling rates: L1 Foundation explanation
The stopwatch tells you how much; the logger tells you where and why. A race car data acquisition (DAQ) system is an electronic memory that records user-defined channels as a function of time while the car runs. After the run you download it and analyse it in dedicated software (MoTeC i2, Bosch WinDarab, Cosworth Toolbox, AiM RaceStudio, Marelli WinTAX, McLaren ATLAS).
Segers groups what teams use data for into six jobs:
- Vehicle performance – objective evidence to pair with the driver's subjective comments.
- Driver performance – comparing laps and drivers, especially when cars are shared (endurance, Pro-Am).
- Development – deciding where development effort goes.
- Reliability and safety – oil pressure, temperatures, voltage, tyre pressures; spotting a failure before it happens.
- Vehicle parameters – extracting numbers for simulation (aero maps, roll stiffness, tyre grip).
- Running logs – mileage of engines, gearboxes, dampers and life-limited parts.
Channels fall into three families: vital functions (oil/water temperature and pressure, fuel pressure, battery voltage, gearbox/diff temperature, RPM), driver activity (throttle, brake pressure, steering, gear, clutch) and chassis (speed, accelerations, damper position, ride height, tyre temperatures and pressures, loads).
The classic six basic channels are engine RPM, wheel speed, throttle position, steering angle, lateral and longitudinal acceleration, plus a lap beacon. Even a modern GT3 car logging 300+ channels is analysed mostly through those six. The next logical additions are brake pressure, four damper potentiometers and infrared tyre temperatures.
Typical numbers: a club car logs 20–40 channels; a GT3 or LMP2 logs 200–400 including ECU channels; a Hypercar or F1 car logs thousands, many at kHz rates.
What a DAQ system is: sensors, logger, ECU and sampling rates: L2 Practitioner explanation
Architecture. Every system has the same chain: a sensor turns a physical quantity into a voltage, frequency or digital message; signal conditioning (excitation, amplification, bridge completion, filtering) makes it readable; an analogue-to-digital converter (ADC) samples it; the logger time-stamps and stores it.
In a modern car the parts sit on a CAN network:
- ECU – runs the engine and logs (or transmits) engine channels: RPM, throttle/pedal, lambda, MAP, injection, knock, fuel used, gear.
- Dash-logger – often the main logger and the driver display (MoTeC C1xx, Bosch DDU, AiM MXG, Cosworth ICD).
- Expansion modules / PDM – extra analogue inputs, power distribution, TPMS receivers, IR tyre sensors, GPS/IMU.
- Telemetry – a radio link streaming a subset of channels live to the pit wall.
Sampling rates – a practical guide:
| Channel group | Typical rate |
|---|---|
| Fluid / air temperatures | 1–10 Hz |
| Fluid pressures (oil, fuel) | 10–50 Hz |
| Driver inputs, IMU, wheel speeds | 100–200 Hz (50 Hz is the bare minimum) |
| Damper potentiometers (for shock-speed histograms) | 200–1000 Hz |
| GPS position / speed | 10–25 Hz |
| Knock, upright accelerometers | kHz range |
Faster is not free: memory, CAN bus load and file size all grow. A quick budget is
where is bytes per sample (usually 2). Forty channels at 100 Hz plus eight damper/load channels at 500 Hz is kB/s, about 58 MB per hour – trivial for a 2 GB logger, but CAN bus load is often the real limit.
Trackside habits: download after every run, including installation laps and engine warm-ups; check the logger configuration (rates, calibrations, beacon) before the car leaves the garage; keep spare sensors, looms and connectors in the kit.
What a DAQ system is: sensors, logger, ECU and sampling rates: L3 Advanced explanation
Where the data chain fails. Most bad conclusions come from data that looked fine but wasn't:
- CAN latency and sample-and-hold. A channel sent by the ECU at 50 Hz but logged at 200 Hz appears as a staircase. Differentiate it and you get spikes, not a rate. Channels from different devices can be offset by 10–40 ms, which matters when you compare throttle (ECU) with longitudinal g (logger IMU) to measure response delays.
- Bus load. Classic CAN runs at 1 Mbit/s; above roughly 60–70 % load, low-priority messages start to be delayed or dropped. CAN-FD and Ethernet loggers relieve this on top-level cars.
- Aliasing. If a signal has content above half the sampling rate, that energy folds back into the band as a false lower frequency. A 25 Hz wheel-hop logged at 30 Hz shows up as a 5 Hz oscillation – right in the body-mode range – and can send you chasing a damper problem that isn't there. The defence is an analogue anti-alias filter before the ADC plus a rate well above twice the highest frequency of interest (rule of thumb: 5–10× for clean shape).
- Resolution. A 12-bit ADC splits its range into 4096 steps; a 16-bit one into 65 536. Quantisation matters most when you differentiate (damper velocity, brake-pressure rate).
- Time base. Distance is usually integrated from wheel speed; lock-ups, wheelspin and tyre-radius growth corrupt it. GPS-fused speed (0.1–0.2 % speed accuracy) fixes most of this.
Regulation context. In many series the electronics are spec or sealed: FIA F2/F3 and IndyCar run control electronics with a homologated sensor list, and adding sensors may be forbidden in the event. GT3 and Hypercar cars carry organiser loggers (and in Hypercar, homologated driveshaft torque sensors) used for BoP and power verification. Know which channels you are allowed to log, and which ones the organiser sees.
Design choice. Choose rates per question: if you only want body motion (1–5 Hz), 100 Hz damper logging is plenty; for damper velocity histograms and kerb strikes, log 500 Hz or more.
Key formulas
- data rate (bytes/s)
- sampling rate of channel i (Hz)
- bytes per sample (typ. 2)
- sampling frequency (Hz)
- highest frequency present in the signal (Hz)
Trackside takeaways
Six basic channels (RPM, speed, throttle, steering, lat g, long g) plus a beacon do most of the work; add brake pressure, damper pots and IR tyre temps next.
Match the sampling rate to the question: temps 1–10 Hz, driver/IMU 100–200 Hz, damper pots 200–1000 Hz for velocity work.
CAN-transmitted channels are delayed and stepped; do not differentiate them naively or compare them with logger channels to the millisecond.
Download every run, including installation laps; check vitals before performance.
In spec and BoP series, know which sensors you are allowed to fit and which data the organiser logs.
On your car
Manufacturer-supplied Bosch/Marelli/MoTeC packages with 200–400 channels, ABS/TC channels and an organiser BoP logger. Extra sensors are usually allowed in testing but check event rules.
Check yourself
You can only afford three extra sensor groups on top of the six basic channels. Which set gives the most chassis-analysis value?
- Segers – Analysis Techniques for Racecar Data Acquisition — Ch. 1 Introduction (§1.2 What Is Data Acquisition?, §1.3 Hardware)
- Segers – Analysis Techniques for Racecar Data Acquisition — §19.2 Analog-Digital Conversion: Accuracy Implications · sampling-rate guidelines and aliasing
- Segers – Analysis Techniques for Racecar Data Acquisition — §2.8.6 Basic Tips