U0100 — Lost Communication With ECM/PCM A

What the U0100 code means

A modern car is a network: the engine computer (ECM/PCM), transmission module, ABS, airbag module, instrument cluster, and dozens more exchange data over the CAN bus many times per second. U0100 is stored by the other modules when the engine computer stops answering — they expected its messages and heard silence.

Notice what the code does and does not say. It is set in the modules that are still awake, reporting a missing colleague. The cause could be the ECM itself, but it is at least as often something simpler that silences it: a blown fuse or failed relay cutting its power, a corroded ground strap, a damaged section of CAN wiring, or battery voltage so low during cranking that the module drops off the bus.

Symptoms match the confusion. Depending on the car, you may get a no-crank or crank-no-start, an engine that starts and immediately stalls, a dashboard lit with unrelated warnings, gauges dropping, or a scan tool that suddenly cannot talk to the engine computer while it still reaches the others. That last test is one of the most diagnostic facts available: who can the scanner still see?

Symptoms of U0100

• Engine will not crank, or cranks but will not start
• Engine starts then stalls, sometimes repeatedly
• Multiple unrelated warning lights — ABS, traction, airbag — alongside the check engine light
• Gauges dropping or behaving erratically; transmission stuck in one gear on some models
• Scan tool communicates with other modules but not the ECM
• Other U-codes stored in several modules

What causes U0100?

• Lost power or ground to the ECM — a blown fuse, failed power relay, or corroded ground point starves the computer so it cannot transmit. Always the first checks — they are free and common.
• Damaged CAN bus wiring — chafed harnesses, rodent damage, corroded splices, and damage from previous collision or stereo/alarm work can open or short the two communication wires to the ECM.
• Low system voltage — a weak battery or poor battery cables drop voltage during cranking below what modules tolerate; several go silent at once and U-codes scatter across the car.
• Water intrusion in connectors — flood exposure, windshield leaks, and pressure-washing push moisture into module connectors, corroding pins until communication fails intermittently, often weather-dependent.
• Failed ECM/PCM — internal failure of the computer itself. A real cause, but the conclusion of the diagnostic process — never the opening guess, because replacement plus programming is the expensive outcome.
• Aftermarket device on the network — a faulty OBD-port gadget, tracker, or remote-start module can corrupt bus traffic. Unplugging everything from the diagnostic port is a legitimate early test.

How serious is U0100?

This is as serious as codes get on a road car: the engine computer is the one module the car cannot run without. A vehicle that loses ECM communication may not start, may stall, and gives no promise about when it will do either. If it is running when you read this, do not plan trips on it.

The saving grace is how often the root cause is mundane — a fuse, a ground, a battery — rather than the computer itself. Systematic electrical diagnosis is essential and is exactly what you are paying a good shop for; throwing an ECM at a wiring fault buys the same code in a more expensive box.

How much does it cost to fix U0100?

Diagnosis dominates this code: expect a diagnostic fee toward the higher end because the testing is methodical electrical work. Typical US outcomes, parts and labor:

Prices are typical US ranges and vary by vehicle, location, and shop. Diagnosis usually costs $100–$150 and is often applied to the repair bill if you proceed at the same shop.

How U0100 is diagnosed and fixed

1. Start with the battery: test its condition and the cable connections, and record system voltage during cranking. Rule out low voltage before any module is suspected.
2. Scan every module the tool can reach and list which respond. If the ECM alone is missing, focus on its powers, grounds, and bus connection; if many are missing, think bus-wide or voltage causes.
3. Check the ECM's fuses and power relay, then load-test its power feeds and ground straps at the module connector — a ground that shows voltage drop under load is found, not guessed.
4. Measure CAN bus resistance at the diagnostic connector with the battery disconnected: a healthy terminated bus reads about 60 ohms. Readings near 120 ohms or near zero point to an open or short in the network.
5. Inspect the harness runs to the ECM for chafing, rodent damage, prior repairs, and water in connectors; unplug any aftermarket devices from the OBD port and retest.
6. Only when power, ground, and bus integrity are all proven good and the module still will not communicate is the ECM itself condemned and replaced, with the programming/flash procedure its replacement requires.

Frequently asked questions

Related codes

More in this system: Network codes · Full codes list