01 How Starting and Stopping Your Car Engine Can Affect Its Pe… • 02 Engine Timing: A Comprehensive Guide for Successful Adjustm… • 03 How Does Nitrous, Superchargers, and Turbochargers Boost Yo… • 04 Ford F-150: The King of Trucks or a Mere Pretender? • 05 Automotive Abbreviations: A Guide for Car Enthusiasts • 06 P0116 – Engine Coolant Temperature Range Fault: Causes and … • 07 P0042, P0043, P0044: H02S heater control circuit (Bank 1 s… • 08 Can a Bad Alternator Cause Power Steering Problems? • 09 Understanding Engine Control Modules (ECMs) and Their Funct… • 10 Ways to Avoid Knocking in an SI Engine When the Compression… •

DTC codes / U01xx · Lost communication with a control module / U0100

U0100Lost Communication With ECM/PCM A

U0100 means the modules that need to talk to the engine control module (ECM) or powertrain control module (PCM) have stopped receiving its messages over the controller area network (CAN) bus. The detecting module sets this code when it times out waiting for the ECM/PCM heartbeat, so the fault is a communication loss rather than a confirmed internal engine computer failure.

SystemNetwork
Code typeGeneric (all makes)
SeverityHigh
Fix difficultyProfessional
AreaLost communication with a control module

Symptoms you may notice

  • The check engine light, and often the ABS, traction control, and airbag lights, illuminate together because multiple modules have lost the ECM/PCM signal.
  • The engine may crank but not start, or it may start and then stall immediately because the PCM cannot command fuel and spark.
  • The transmission may default to a limp mode with harsh or delayed shifts, or the speedometer and tachometer may sit dead.
  • Dashboard warning chimes and messages such as 'Service Stabilitrak' or 'Transmission Fault' appear even though those systems are not the root cause.
  • Often no symptoms besides the warning light, especially when the communication dropout is intermittent and the vehicle otherwise runs normally.
  • Non-critical accessories like the radio, climate control, or power windows may behave erratically if they share the same CAN segment.

Common causes, most likely first

  1. A weak or dead 12-volt battery, corroded terminals, or a poor ground connection that drops module supply voltage below the threshold needed for reliable CAN communication.
  2. Wiring damage in the CAN bus, including chafed, pinched, or broken twisted-pair wires between the ECM/PCM and the gateway or other modules.
  3. Corroded, loose, or backed-out pins in the ECM/PCM connectors or in an intermediate harness connector.
  4. A failed or intermittent ECM/PCM power relay or blown fuse that feeds the engine computer, leaving it unpowered while other modules stay awake.
  5. An internal fault in the ECM/PCM itself, which is less common but does happen and is often the first part replaced by mistake.
  6. A shorted or failed module on the same CAN segment that pulls the bus voltage down and blocks all communication, not just the ECM/PCM.
  7. Aftermarket accessories or poor previous repairs that tapped into CAN wiring and introduced noise or a short.

How to diagnose and fix it

  1. Perform a battery and charging system test first, including a load test and a check for voltage drop at the ECM/PCM power and ground pins.
  2. Inspect the ECM/PCM connectors and the harness for corrosion, loose pins, chafing, and rodent damage, then clear the code and see if it returns.
  3. Use a scan tool to check whether the ECM/PCM responds at all and to read communication status on each module; a no-response condition points to power, ground, or bus wiring.
  4. Measure CAN bus resistance and voltage at the diagnostic link connector (DLC) with the battery disconnected and then with the key on to identify a shorted segment or missing termination.
  5. Disconnect suspect modules one at a time from the CAN bus to see if communication to the ECM/PCM returns, which isolates a module that is dragging the bus down.
  6. If power, ground, and bus wiring all test good and the ECM/PCM still does not communicate, substitute a known-good ECM/PCM or perform a bench check before condemning the original unit.
  7. After any repair, clear all codes, perform a road test, and verify that the ECM/PCM communication is stable and that no related codes return.

What U0100 does not always mean

  • U0100 is frequently misread as a dead ECM/PCM, but a weak battery or a corroded ground strap is a far more common cause and costs far less to fix.
  • A single failed module on the CAN bus can take down communication for every other module, so the code may point at the ECM/PCM while the real culprit is an ABS or body control module.
  • Intermittent U0100 codes that appear only in cold weather or after a bump often trace to a harness connector with a backed-out pin rather than a failed computer.
  • Some vehicles set U0100 during a low-voltage event such as jump-starting or a battery replacement, and the code clears permanently once stable voltage is restored.
  • Aftermarket remote starters, alarms, and stereo installs that splice into CAN wiring are a common source of communication faults that look like an ECM/PCM failure.

Can I keep driving with U0100?

Do not drive the vehicle if it cranks but will not start or stalls, because the ECM/PCM is not controlling the engine and you risk a breakdown in traffic. If the vehicle runs normally and only the warning light is on, limit driving to a short trip to a repair shop and avoid highways until the communication fault is diagnosed.

Tools that help

Tools we recommend are in the Auto Veteran shop on Amazon. As an Amazon Associate we earn from qualifying purchases.

Guidance is general and written for all OBD-II vehicles. Exact tests and values vary by model, so confirm the fault before replacing parts.

Running on fumes Free guides aren't free to make. Top up the tank. Any amount, one time. Fuel the Garage