This is one of the things that trips people up when they first open a diesel ECU file. They go looking for the injection duration map and start pulling values. The car responds. They think they understand what happened. They don’t.
Here’s what’s actually going on inside the ECU.
The ECU doesn’t think in fuel. It thinks in torque.
The sequence looks like this:
- Driver presses the pedal → Driver Wish map converts pedal position + RPM into a torque request (in Nm)
- The torque request passes through limiters — thermal, drivetrain, traction control, transmission
- What comes out the other side is the demanded torque — the actual target the engine has to deliver
- Only then does the ECU ask: “How much fuel do I need to produce this torque at this RPM?”
That last calculation — torque to fuel — goes through efficiency maps, fuel consumption coefficients, and injection duration calculations. The duration map you’re staring at in WinOLS is downstream of all that.
Why does this matter for calibration?
Because if you raise injection duration without raising the torque demand upstream, the ECU will see a torque surplus and limit it back down. You’ve changed a number. The car felt nothing. Or worse — the torque limiter kicks in inconsistently and you get a flat spot.
The torque model isn’t a wall to fight. It’s a structure to work with. Once you understand the order of operations — Driver Wish → Torque Limiters → Torque-to-Fuel → Duration — every map in the file has a clear address. Nothing is random.
The maps aren’t a dark forest. They’re a factory floor with a logical production line.
This is exactly the architecture we build from the ground up in Diesel Fundamental, Chapter 1. Before touching a single value, you need to know where in the production line that value lives.