Learn / Engine & Hybrid / Engine vital signs & data monitoring
L1 · Foundation

Engine vital signs & data monitoring

Before looking at performance, confirm the car is healthy: oil and fuel pressure, fluid temperatures, lambda, voltage, rpm. Good alarm channels and trend views catch failures a run before they happen.

Engine vital signs & data monitoring: L1 Foundation explanation

Segers' first rule of data analysis: reliability before performance. A car that stops is infinitely slow, and a car with a hidden problem (low fuel pressure, overheated oil, failing alternator) may simply be down on performance. After every run, check the vital signs before you open the lap comparison.

Core channels and typical healthy values for a racing engine (always check the engine supplier's limits):

ChannelTypical healthyWatch for
Oil pressure (hot, high rpm)4–7 bardrops in long corners (surge), slow decline over run
Oil temperature90–125 °Csustained > 130 °C
Water temperature80–105 °C (pressurised)> 110–115 °C, rising trend in traffic
Fuel pressure (port inj.)3–5 bar, steadydrops at low fuel/long corners (pickup), voltage-related drops
Fuel pressure (direct inj.)100–350 barrail pressure not reaching target
Lambda0.85–0.95 at full loadlean (> 1.0 at full load) → detonation/overheat
Battery voltage13.5–14.4 V runningbelow 13 V = charging problem
Gearbox/diff oil temp80–130 °Ctrend over stint
Max rpm / over-rev counterunder limitspikes on downshifts

Methods (Segers §3.1):

  1. Statistics table — min/max/mean per run or lap. Quick, but misleading: a 0 bar oil pressure minimum may simply be the car stopped in the pits.
  2. Whole-run time graph — trends become obvious: temperatures should rise and stabilise.
  3. Alarm math channels — e.g. low oil pressure only counts when the engine is loaded:

LowOP=(poil<3.0 bar)⋅(n>3000 rpm)\text{LowOP} = (p_{oil} < 3.0\,\text{bar}) \cdot (n > 3000\,\text{rpm})

  1. Driver alarms on the dash, with priorities and the driver knowing what each means and what to do.

Segers' alternator-belt example is the lesson: the voltage was already too low in the run before, nobody noticed, and the car stopped on track.

Key formulas

Low oil pressure alarm (Segers Eq. 3.1)
LowOP=(poil<3.0)⋅(nengine>3000)\text{LowOP} = (p_{oil} < 3.0) \cdot (n_{engine} > 3000)
Cooling margin estimate
Twater,2≈Tamb,2+(Twater,1−Tamb,1)T_{water,2} \approx T_{amb,2} + (T_{water,1} - T_{amb,1})
Oil pressure residual
r=poil,meas−p^oil(n,Toil)r = p_{oil,meas} - \hat p_{oil}(n, T_{oil})

Trackside takeaways

  • Reliability first: check vitals after every run before any performance analysis.

  • Statistics tables hide context — always look at the whole-run trace and trends.

  • Make alarms conditional (rpm, duration) to avoid false triggers; prioritise driver alarms.

  • X-Y plots (oil pressure vs lat g, fuel pressure vs fuel level) expose surge and pickup problems.

  • Use ΔT to ambient to predict water temperature and decide radiator blanking before the session.

  • Implausible steps are usually sensor/ECU defaults; know the difference before calling the car in.

On your car

Production-based engines with dry sump; high lateral g (1.8–2 g) makes oil surge checks vs lat g worthwhile, especially at low oil level late in long stints.

Check yourself

Question 1 / 5L1 · Foundation

A statistics table shows minimum oil pressure 0.1 bar for the run. What is the right next step?

Further reading
  • Segers – Analysis Techniques for Racecar Data Acquisition — §3.1 Check the Car's Vital Signs · statistics table, run trends, alarm channels, oil pressure vs lat g, alternator failure example
  • Segers – Analysis Techniques for Racecar Data Acquisition — §16.1 Fuel Consumption · injector/lambda faults detected via fuel accounting