U0100: lost communication with the engine module — and why the car still drives

U0100 “Lost Communication With ECM/PCM” is the most frequent U-series code. The wording sounds alarming, but it does not mean the engine module died. It means something more modest: one of the modules on the bus stopped receiving messages from it.

That distinction matters, and it is the one most often missed.

Who is actually complaining

U0100 is written not by the engine module about itself but by somebody else about it: the ABS module, the transmission module, the instrument cluster, the body control module.

So it is a complaint: “I cannot hear it.” The cause can sit at any of three levels:

1. The engine module genuinely went silent.
2. The bus between them is broken or shorted.
3. The complainant itself is malfunctioning.

How the bus works is covered in CAN fundamentals.

Causes by probability

1. A voltage sag (most common)

A weak battery, a poor terminal contact, a corroded ground. During cranking the voltage drops below threshold, modules lose contact for a moment, and honestly log it.

The key signature: U0100 is not alone. A dozen codes from unrelated systems sit alongside it with the same timestamp. That is a cascade, not ten failures — the mechanism is covered in ghost and false codes.

The procedure is simple: fix the supply, clear everything, drive a cycle, see what returns. Usually nothing does.

2. Wiring and connectors

A break or corrosion in the bus itself. Most often where the harness flexes or passes through a bulkhead.

A quirk of the bus: losing one of the two lines does not always stop communication. Many modules can operate on a single line with reduced noise immunity. So the picture wanders: communication present, then absent.

3. A flat or dead battery

Separate from point 1 because the cause is visible. After a failed start, after a jump start, after a week parked — U0100 appears on its own and disappears after charging.

4. Water in a connector or module

After a wash, after rain, after a windscreen replacement. Produces a wandering picture that changes between sessions.

5. Aftermarket electronics on the bus

Alarms and trackers wired into CAN — usually incorrectly. A very common cause, and easily tested by disconnecting them.

6. The control module itself

Last on the list. Modules rarely die, and usually only after an impact, water ingress, or a voltage spike.

Why the car keeps driving

The question arises immediately: if there is no communication with the engine module, how is the engine running?

Because the engine module does not need the bus to run the engine. It reads its own sensors and drives its own actuators directly. The bus exists for exchange with everybody else: send RPM to the cluster, coordinate shifts with the transmission, permit stability control to operate.

So the typical U0100 picture is an engine that runs while everything around it fails: speedometer and tachometer dead, transmission in limp mode, ABS inoperative, air conditioning off.

The search order

1. Read all codes across all systems and check timestamps. A cascade means look at power.
2. Check voltage: 12.4–12.7 V overnight, 13.8–14.4 V running. The procedure is in parasitic drain diagnostics.
3. Inspect terminals and grounds. A corroded ground produces exactly this picture and is cured with a wire brush.
4. Disconnect aftermarket electronics and drive a cycle.
5. Check the module roll call. Who answers and who does not is a map of the problem.
6. Only then hunt for a break in the bus.

The first four steps solve most cases and need nothing more than a multimeter.

U0100’s relatives

The logic is identical; only the addressee changes:

Code	Who is silent
U0100	Engine control module
U0101	Transmission module
U0121	ABS module
U0140	Body control module
U0151	Restraints control module
U0155	Instrument cluster

Several U-codes across different modules at once is no longer coincidence — it is either power or harness damage. When buying a car this is one of the most important signals; see rebuilt salvage cars.

In short

• U0100 is written by whoever cannot hear the engine module, not by the module.
• The most common cause is a voltage sag, and then the code never appears alone.
• The engine runs without the bus; everything around it stops.
• Power, grounds, and aftermarket electronics first; wiring last.
• Several U-codes together form a damage map, not a list of failures.

Download the app — codes across every system, timestamps, and the module roll call are read with an ELM327 adapter over Bluetooth SPP on Android.