Keeping the Engine Running
Once the engine is running, the engine-management module is continuously balancing fuel, spark, air and timing — using information that is not all its own.
In plain language
The engine-management module — the DME — is the computer that keeps the engine running. It decides how much fuel to inject and when, when to fire each spark, how much air to let in, and, on engines equipped for it, how the valves themselves should behave. It makes those decisions many times per revolution, and it adjusts them constantly based on what its sensors report back.
What surprises most people is how much of its information comes from elsewhere in the car. The DME listens to the braking and stability system, the transmission and the driver's selected driving mode. It is not just an engine controller; it is a participant in how the whole vehicle behaves.
What the customer sees
A rough or uneven idle, hesitation, reduced power, poor economy, an engine warning light, or a car that runs but feels restricted. Sometimes an apparently engine-shaped complaint that began with something entirely outside the engine.
What the module is doing
Running closed-loop control: commanding fuel, spark, air and timing, measuring the result through its sensors, and correcting continuously. Alongside that it monitors its own outputs, runs emissions-related self-tests, coordinates torque with the transmission and stability systems, and manages cooling and charging strategy.
What a technician tests
Live data first: what the module believes it is seeing and what it is commanding in response. Then the circuits behind whichever value does not agree with reality. Fuel supply, injector control, ignition control and air metering are each tested as command-plus-result, because a present supply is not the same as a switched driver.
The technical detail
Fuel is delivered in two stages on most of these engines. A low-pressure supply feeds a high-pressure stage on direct-injected engines, and the module both controls and monitors the pressure it asks for. Injection is a driver-switched event on the control side; the presence of supply at an injector says nothing about whether the module is switching it.
Ignition is likewise command-and-result. Each coil needs supply, a ground and a trigger from the module at the right moment. A coil circuit fault, a driver fault and a synchronisation problem all produce a misfire, and they are separated by testing rather than by the code.
Air is electronically controlled, and on some engines so are the valves. Throttle position is a commanded value with position feedback, and where variable valve lift is fitted its actuator has its own position sensing. A plausibility fault on either is the module reporting that what it commanded and what it measured do not agree.
Adaptations record the engine's long-term corrections. When the module has been trimming fuel in one direction for a long time, that record is a symptom of an underlying condition — metering, air, fuel delivery or exhaust feedback — and not a fault in itself.
The DME depends on other modules. Wheel speed, vehicle speed, yaw rate, steering angle, braking torque and the selected driving-dynamics configuration all arrive over the network from the braking and stability side of the car. When that source stops transmitting, the DME records missing-message faults and may limit torque, while the engine's own circuits are perfectly healthy.
Charging closes the loop. Once running, the alternator supplies the vehicle's loads and recharges the battery under a charging strategy that is itself managed. A charging fault eventually reappears as the undervoltage faults described elsewhere in this section.
Why this matters when something goes wrong
Running complaints are diagnosed from live data outwards, because the module's own view of the engine is the fastest way to find the value that does not match reality. The code narrows the area; the data identifies the circuit.
The network dependency is the part most often missed. A car that has lost the stability system's messages can present as an engine complaint — reduced power, a warning light, torque limitation — with a fault list in the DME that names the DME. Checking who is not transmitting before condemning the receiver is what keeps that from becoming an expensive mistake.