Validation with dyno and road logs
Validation with dyno and road logs: Engine mechanical power can be calculated from torque and speed as P(kW)=T(Nm)×rpm/9549. The page also includes a worked example and measurement sequence.
Technical frame
Validation with dyno and road logs: Engine mechanical power can be calculated from torque and speed as P(kW)=T(Nm)×rpm/9549. The page also includes a worked example and measurement sequence.
The technical values here expose the standard, protocol or physical relationship directly; model-specific service values are linked through the matching model/variant dossier.
The goal is not only to define the term but to let the reader calculate and interpret what the data means in a scan, scope or physical test.
Concrete technical facts
- Engine mechanical power can be calculated from torque and speed as P(kW)=T(Nm)×rpm/9549.
- Dyno wheel power is not crankshaft power; drivetrain loss should not be assumed as a fixed percentage without declaring the method.
- ECU torque models can include driver demand, air charge, fueling/ignition, transmission, traction, thermal and component-protection limits.
- When a limiter is active commanded torque/power can be reduced, so low actual output does not automatically mean a fuel/turbo hardware fault.
- Tuning validation should align lambda, knock correction, fuel/rail target-actual, boost target-actual, EGT/temperature and torque-limit state in one log.
- Before/after comparisons need the same fuel, temperature, gear, tire and test procedure to be meaningful.
Worked example
- Power example: 320 Nm at 4000 rpm gives P≈320×4000/9549=134.0 kW; the same 320 Nm at 2000 rpm is only about 67.0 kW.
Measurement and verification sequence
- Control before/after conditions including fuel, temperature and gear.
- Log torque request/limits, boost, lambda, ignition/knock and fuel pressure together.
- Report dyno weather correction and measurement point.
- If protection/limiter is active, solve the cause rather than chasing output alone.
Fault-separation logic
- Is a valid command present and are power/ground/network healthy?
- Does feedback follow the command?
- Does an independent physical measurement confirm the output?
- Is the fault limited to a specific temperature/load/speed condition?
- Does the result remain stable when the original condition is repeated after repair?
Technical sources
Continue investigating
Model-specific real technical data · Measurement references · Technical diagnostic atlas