Timing pull on an EA888 log: what the number means and when it matters

Open any datalog from an EA888 Gen3 and the first columns a tuner scrolls to are the four labelled something like "timing retard, cylinder 1" through "cylinder 4". Everything else in the log is context for those four numbers.

What the ECU is doing

The engine has knock sensors bolted to the block. They are microphones. The ECU listens for the ringing frequency of knock in a window around each cylinder's combustion event, and when it hears it, it retards the ignition timing on that cylinder, a few degrees at a time, then slowly gives the timing back if the noise stops. The amount it takes away is the timing pull. It is logged per cylinder because knock is per cylinder.

This is not a fault mode. It is the factory's normal, continuous protection, running on every Gen3 on every drive. A stock car pulls timing on a hot day with bad fuel and the driver never knows.

What normal looks like on a Stage 1

A well-written Stage 1 on the declared fuel shows small, brief pulls: a degree or two, on one cylinder, for a moment, usually where the boost is peaking in the mid range. Then it returns to zero. That pattern says the file is near the knock threshold but on the right side of it, and the ECU is doing its job in the margin the tuner left it.

Zero pull across a whole pull is also fine and means the file is conservative for that day's conditions.

What the patterns mean

One cylinder, sustained pull, every pull. Not a tuning problem. That cylinder has a worn plug, a weak coil, or something mechanical. The other three cylinders are seeing the same file and the same fuel and are not complaining. The fix is a plug or a coil, not a revised file, and a tuner who revises the file to hide it is doing the customer a disservice.

All cylinders, growing pull at high rpm. The charge is too hot or the fuel is not what was declared. Check the intake temperature column; if it climbed through the pull, the car was heat-soaked and the log should be repeated cool. If it did not, the fuel is the first suspect.

Pull everywhere, from low rpm. The file asked for more than this fuel can give. This is the pattern that comes back as a revised file with less timing, and it is the reason the datalog tiers exist.

Pull that appears only after a hard shift. Often the transmission's torque intervention interacting with the boost control, and usually harmless. A tuner reads it alongside the boost columns before deciding.

Why it is the first column

Because timing pull is the engine telling you, in its own words, how close it is to the edge. Boost and lambda say what the file asked for. Timing pull says what the engine thought of it. A tune that is checked against that column is a tune that was checked against the engine.

The knock gauge in the simulator below is a simplified version of the same signal. Push the timing slider past the ceiling and watch what the engine would have been saying.