Key takeaways
- Logs turn tuning from guesswork into evidence — every claim checked against data.
- The essential channels: RPM, load, lambda, boost target vs actual, timing, knock retard, EGT.
- A change is only real when the log confirms it in the safe window.
Data logging is essential for tuning validation.
Essential Diesel Channels
- Boost (actual vs target)
- IQ (actual vs requested)
- Rail pressure
- EGT
- Turbo speed
Essential Gasoline Channels
- Boost
- Ignition timing
- Knock retard
- Lambda
- Fuel trims
What to Look For
- Targets achieved
- No limiters active
- Safe temperatures
- No knock activity
The Channels That Matter
A useful tuning log is a handful of well-chosen channels: rpm, requested vs actual torque, air mass or manifold pressure against target, rail pressure target vs actual, injection timing and quantity, lambda or trims, knock retard on petrol, and EGT where available. Target-versus-actual pairs are the heart of it — deviation is information, absolute values alone rarely are.
Reading Before and After
Log the stock car first over a repeatable route: third-gear pulls, steady cruise, a cold start. After changes, compare the same windows. Trims walking away from zero, boost trailing target, timing pulled by knock control or EGT climbing toward the ceiling are the early warnings that separate a healthy file from one that merely feels strong.
Which channels should I log when tuning?
How do I read tuning logs to find a problem?
Related: on supported vehicles this system is directly addressed by our DTC removal service. See also Typical Sensor Ranges and Limits in the knowledge base.
