U0100 Code: Lost Communication With ECM/PCM

What Does U0100 Mean?

U0100 is a network code — the “U” prefix marks faults in the communication system that lets a car’s dozen-or-more computers talk to each other, rather than a fault in any single system like the engine or brakes.

Modern cars connect their control modules — engine, transmission, ABS, airbags, body control, instrument cluster and more — over a shared data network, most commonly CAN bus (Controller Area Network). Each module broadcasts its own status constantly and listens for messages from the others. U0100 specifically means that whichever module set the code has stopped receiving expected messages from the engine control module (ECM), sometimes combined with the powertrain control module (PCM) on cars that merge the two.

Common Symptoms

• Multiple, seemingly unrelated warning lights illuminating together — engine, ABS, traction control, airbag and others, since several modules can each report the same underlying communication loss independently.
• Instrument cluster faults — gauges reading incorrectly, warning chimes with no obvious cause, or a cluster that goes briefly blank.
• Starting problems or the engine failing to start at all, on cars where the network fault prevents the ECM from being properly recognised at start-up.
• Transmission behaving oddly, since automatic transmissions rely on engine data delivered over the same network.
• Intermittent electrical glitches that come and go, particularly if the underlying cause is a marginal connection rather than a complete break.
• No noticeable symptom at all beyond the stored code, on a fault that was brief or has since cleared itself.

Common Causes

1. A weak or discharged battery. Modules can drop off the network or behave erratically at voltages that are too low for reliable communication, well before the voltage is low enough to prevent starting outright. See battery keeps dying overnight if this is a recurring pattern.
2. A corroded or loose ground connection. Network communication is highly sensitive to a clean, solid ground reference — a corroded engine-to-body earth strap is a classic and often-overlooked cause.
3. Damaged CAN bus wiring. The two-wire twisted pair that carries network data can be chafed, pinched or corroded anywhere along its length, particularly at connectors exposed to moisture.
4. A blown fuse powering the ECM. Cuts communication at the source, cheap and quick to check.
5. A recently disconnected or low battery during other work. Some modules need to properly reinitialise after a voltage interruption, and a code set during that process can be a leftover rather than an ongoing fault — worth clearing and rechecking after a normal drive.
6. Water intrusion at a connector. Particularly around the engine bay or under the vehicle, where connectors are exposed to spray and road salt.
7. A genuinely failed ECM. Possible, but well down the list — this is the conclusion to reach only after the more common and cheaper causes have been ruled out.

How to Diagnose It

1. Check the battery and charging system first

Measure resting and cranking voltage. A battery or alternator that cannot maintain stable voltage is a strong candidate and costs nothing to check — see battery light on while driving for the full test procedure if the charging side is in doubt.

2. Check grounds

Inspect the main engine-to-body earth strap and any accessible chassis grounds near the ECM. Look for corrosion, and confirm connections are tight. A poor ground is one of the more common root causes behind network faults generally.

3. Read every stored code, not just U0100

If several modules have each logged their own version of “lost communication with ECM”, that confirms the fault is upstream — power, ground or a shared wiring section — rather than a problem specific to one module.

4. Inspect accessible wiring and connectors

Look at the ECM’s main connectors for corrosion or a connector not fully seated, and follow any accessible network wiring for obvious damage, particularly near areas prone to chafing or moisture.

5. Clear the code and observe

If the likely cause was a low-voltage event — a jump start, a battery disconnect, or a very cold start — clear the code and drive normally. A code that does not return after several complete drive cycles was likely a one-off rather than an ongoing problem.

Possible Fixes

Start at the top of this list. Battery, grounds and fuses account for the overwhelming majority of U0100 cases and cost little to rule out — the ECM itself is rarely the answer.

Can I Drive With U0100?

If the car will not start reliably, or symptoms are getting worse rather than staying stable, do not continue driving on the assumption it will sort itself out — have the charging system and grounds checked before anything else.

When to See a Mechanic

Get it checked reasonably promptly if:

• Multiple warning lights are on together, not just one.
• The instrument cluster behaves oddly — blank sections, incorrect readings, unexplained chimes.
• The transmission is shifting differently from usual.
• The car has intermittent starting problems alongside the code.
• Clearing the code and driving normally does not stop it returning.

Mention whether the battery has been disconnected, jump started, or replaced recently — that context often explains a code that turns out to be a leftover from a voltage interruption rather than an active fault. More in our electrical and battery section.

Frequently Asked Questions