Torque Monitoring | TuningBot

Key takeaways

Torque monitoring is the independent audit: modelled torque versus permitted request.
It runs on a separate calculation path so a corrupted main map cannot hide.
Consistency with monitoring is what separates a safe tune from a dangerous one.

Torque monitoring protects drivetrain components by validating that estimated engine torque is consistent with allowed limits. Modern ECUs cross-check multiple torque pathways to detect manipulation or mechanical anomalies.

Overview

The ECU compares requested torque, modeled torque and measured torque proxies (airmass, injection quantity) to detect discrepancies.

Controlled Signals

IQ request
Air mass
Boost pressure
Rail pressure
Driver wish torque

Maps Involved

Driver Wish
Torque Limiters (gear, temperature, smoke)
Smoke Model → load estimation
Engine Efficiency Maps

ECU Logic

Driver Wish → Torque Request
       ↓
Torque Limiters Applied
       ↓
Torque Model (airmass, fuel, pressure)
       ↓
Torque Monitoring Cross-Checks
       ↓
If mismatch → Limp Mode

Calibration Objectives

Avoid false torque deviation trips
Maintain consistent torque pathways
Ensure safe mechanical loads

Calibration Strategy

Harmonize torque limiters before raising torque
Avoid breaking relationship between airflow and IQ
Correct smoke model early in the process

Diagnostics

P061B / P06xx torque correlation faults
Airflow-to-IQ mismatch
Smoke model inconsistent values

Best Practices

Consistency beats peak torque
Validate torque model under transient conditions

In Calibration Practice

The monitoring level independently estimates torque from air, fuel and timing and compares it against the driver’s request; disagreement beyond the calibrated margin triggers intervention up to fuel cut. Performance files that raise output without touching the monitoring path eventually meet it — correct work keeps request, delivery and monitoring telling the same story.

What is torque monitoring and why does it matter for tuning?

An independent check that re-derives delivered torque from raw signals and compares it against the allowed request. If a tune raises output but leaves the monitor untouched, the mismatch trips interventions up to injection cut. It must be kept consistent, not bypassed.

Why do some tunes randomly lose power under load?

Classic monitoring conflict: raised torque exceeds what the untouched monitor permits, so it intervenes exactly when you ask for full power. The fix is calibrating the monitor to the new torque reality, not disabling the audit.

Related: on supported vehicles this system is directly addressed by our torque monitoring disable service. See also Thermal Protection in the knowledge base.