U0100: Lost Communication with ECM/PCM

What U0100 tells you, and what it does not

Other modules on the network report that they can no longer reach the main engine computer, this usually means a power, ground or wiring problem affecting that module rather than the network itself.

The code sits in the engine computer network link area and is reported by the comprehensive component monitor. It names the circuit or the condition where the computer saw a reading outside its expected range. It does not name a failed part, and several genuinely different faults set this same code, which is the whole reason the causes below are ordered rather than listed.

What people usually notice

• Engine may not start
• Multiple warning lights on together
• Transmission shifting oddly
• Dash gauges reading incorrectly or going blank

What causes U0100?

The causes below are ordered by how often they turn out to be the answer, cheapest and most common first. That order matters more than the list itself: the expensive component named in the code text is very rarely the first thing to replace, and working down from the top is what stops a engine computer network link fault becoming an expensive guess.

Corroded or loose connector at the engine computer is the one to rule out before anything else. The most common and cheapest cause to check first.

Working out which cause it is

Start with freeze frame. There is no engine freeze frame here since the engine computer itself is the one not communicating, check which other modules reported the same loss. That snapshot is taken at the instant the code set, and it is the single most useful piece of evidence you have, which is also why clearing the code before reading it is such a costly habit.

Diagnosing this one properly means commanding a component and watching whether it responds, which a read-only tool cannot do at any price. Full system network access is needed to confirm whether the engine computer itself or another module and its wiring is the cause.

The order worth working in

• 1. Corroded or loose connector at the engine computer: The most common and cheapest cause to check first.
• 2. Blown fuse powering the computer: A cheap and common cause to check next.
• 3. Low or dead battery, or a charging system problem: Insufficient voltage can knock the computer off the network.
• 4. A bad engine or body ground strap: A poor ground reference can disrupt communication.
• 5. Wiring damage near the engine computer harness: A break in this wiring stops the computer from communicating.
• 6. Failed engine computer: Least likely, but possible after ruling out simpler causes.

What U0100 means for driving the car

Other modules cannot get engine data, so things like the transmission, cruise control or dash gauges may misbehave, or the engine itself may stall, do not rely on the vehicle for a long trip until this is fixed.

This is a severity 3 of 4 code, which means continuing to drive normally risks damage that costs considerably more than the repair in front of you. Treat the lamp as an instruction rather than a notification.

What does it cost to ignore U0100?

A vehicle that cannot communicate with its engine computer can stall unexpectedly or fail to start, this should not be left unaddressed.

There is also the diagnostic cost of waiting. Freeze frame data, pending code history and the readiness monitor state all describe the fault as it was when it set, and all of it is lost the moment somebody clears the code to make the lamp go out.