Key takeaways
- Every sensor has a valid range; readings outside it are rejected as faults.
- Range limits let the ECU detect shorts, opens and drift instantly.
- Tuning must respect the physical range the hardware can actually report.
Knowing normal sensor ranges helps identify problems quickly.
Boost Pressure
- Stock turbo WOT — 150-250 kPa
- Stage 1 — 180-280 kPa
Rail Pressure (Diesel)
- Idle — 250-400 bar
- Full load — 1400-2500 bar
EGT
- Cruise — 250-400°C
- Full load — 500-750°C
- Safe limit — typically <850°C
Lambda (Gasoline)
- Stoichiometric — 1.0 / AFR 14.7
- WOT enrichment — 0.78-0.88
Temperatures
- Coolant normal — 85-100°C
- Oil normal — 90-110°C
- IAT good — 25-50°C
Fuel Trims
- Normal — ±5%
- Acceptable — ±10%
- Investigation — ±15%+
Using Sanity Ranges in Log Review
These ranges are triage values: a signal outside its band flags a sensor, a model or a real mechanical condition for closer inspection. Always judge them in context — rail pressure legitimately sits far below its maximum at idle, EGT belongs near its ceiling on a long full-load pull, and trims swing wide during purge or right after adaptation resets.
When Out-of-Range Is Not a Fault
Transients, altitude, extreme ambient temperatures and active regeneration all push signals beyond everyday bands by design. The pattern to distrust is persistence: a value that lives outside its range at steady state, or a target-actual pair that never converges, is information — and it is exactly the kind the plausibility monitors are watching too.
Why does a sensor reading of zero or maximum set a fault?
Can tuning exceed a sensor’s range?
Related: on supported vehicles this system is directly addressed by our DTC removal service. See also Sensor Plausibility Checks and Cross-Checks in the knowledge base.
