TL;DR
- Tuning is changing targets and limits so the ECU can control torque safely under your real conditions.
- Modern ECUs are torque-based: they decide airflow, fueling, and spark to hit a torque request.
- Validation beats screenshots: consistent conditions and repeat runs are the only way to trust changes.
A mental model (text diagram)
Driver intent → Torque request → ECU torque model → Airflow (boost/throttle) + Fuel + Spark
↑ ↓
Sensors (air, temps, knock, fuel) ← Outcome (torque delivered)Required vs optional fields
Required (almost always): RPM, throttle/torque intervention, boost target/actual (boosted), IAT, knock/timing correction.
Optional (use-case): fuel pressure, lambda/AFR, coolant/oil temps, gear, traction signals.
What each field indicates (short table)
| Field | What it tells you | Why it matters |
|---|---|---|
| IAT | heat state | affects knock margin and consistency |
| Knock correction | combustion safety response | tells you margin is being spent |
| Throttle/torque limit | ECU intervention | explains “boost drop” feelings |
How to keep logs comparable
- Same road/direction/gear
- Similar starting temps
- Multiple runs
Validation plan for this topic
Start with one written hypothesis from this page: A useful log is small and intentional: capture the inputs, the ECU’s decisions, and the outcomes that prove repeatability. Do not begin the test until the vehicle is mechanically healthy, the fuel is known, and the operator can use a legal controlled environment. Keep gear, engine-speed window, load request, and starting temperature as consistent as the platform allows.
For What to log on a tuned car, align these signals on the same time axis:
- test context - establishes what the system was asked to do or the condition entering the event.
- requested and measured load - shows the primary response rather than a dashboard summary.
- fuel and ignition response - provides the safety or control context that can explain an apparently good or bad result.
- temperature and intervention - tests whether another system, not the headline variable, actually set the limit.
Mark the start and end of the relevant event before interpreting it. Look for sequence: request, response, deviation, intervention, and recovery. A value that changes after throttle lift cannot explain the event that happened before it. Compare at least two clean repetitions and retain the original file, calibration identifier, fuel, ambient condition, and any warning or driver note.
What counts as a useful result
A useful result either supports the hypothesis under comparable conditions or disproves it clearly enough to change the next action. It is also useful to learn that maintenance, sensor quality, traction, or temperature made the test invalid. Do not average invalid and valid attempts together, and do not hide a protection event because the final headline number improved.
Stop and investigate
Reduce load and investigate persistent correction, misfire, unexpected lean operation, falling fuel pressure, uncontrolled temperature rise, fluid leakage, new mechanical noise, or an intervention that was not present in the baseline. A generic internet threshold is not a substitute for the platform’s factory documentation, the calibration provider’s limits, and review by a qualified professional.
For the full control-of-variables method, use Repeatability and consistency. For signal ordering and context, use How to read a datalog.
Common mistakes
- Logging everything and learning nothing (too much noise).
- Comparing one run at random temperatures.
Diagnostics / what logs tell you (high level)
| Signal | What it usually means | What to check |
|---|---|---|
| RPM | Context for everything else | Compare in the same gear and load range |
| Throttle angle / torque intervention | How the ECU is controlling torque | Look for closures that explain boost drop |
| Boost target vs actual | Control quality and limits | Oscillation can be hardware or control strategy |
| IAT / temps | Margin and repeatability | Heat soak changes results dramatically |
| Knock / timing correction | Combustion safety response | Sustained corrections = reduce load/verify fuel/temps |
FAQ
Do I need OBD logs to validate?
They help, but you can still validate repeatability with consistent timing data and controlled conditions.
Related guides
- Hub: Tuning hub
- More in this pillar: - /academy/tuning/how-to-read-a-datalog/
- Related (other pillars): - /academy/mods/heat-management-for-tuned-cars/
- Reference: Glossary
- Brands: Brand pages