Lost communication with ECM/PCM

What U0100 means

Modern vehicles use a Controller Area Network (CAN bus) to allow engine, transmission, ABS, body control, and other modules to share data without direct point-to-point wiring. U0100 is a generic OBD-II network communication fault that indicates the ECM or PCM stopped receiving expected messages — typically the heartbeat or broadcast frame — from a specific control module. The U-series (U0xxx) of codes specifically covers communication loss rather than sensor or circuit faults. Because so many vehicle functions depend on module-to-module communication, U0100 often occurs alongside numerous other active faults that are actually secondary to the communication failure.

Symptoms

• Multiple warning lights illuminated simultaneously (check engine, ABS, traction control, transmission, etc.)
• Transmission stuck in failsafe mode (limp mode) — limited gears available
• Engine cranks but will not start in severe cases
• Erratic or unresponsive instrument cluster gauges
• Loss of features dependent on the affected module (cruise control, stability control, etc.)

Common causes

• Corroded, loose, or damaged CAN bus wiring connector at the affected module — the most common cause
• Failed or internally shorted control module pulling the CAN bus low and disrupting all module communication
• Blown fuse or failed relay in the power feed to the affected module, causing it to go offline
• Low battery voltage or poor battery ground connections — CAN bus communication degrades below roughly 10V
• Damaged CAN bus wiring (chafed insulation, cut wires) causing a short or open in the network

Severity & driving advice

Severity: High — Can prevent starting or trigger limp mode. Often masks the true fault behind many secondary codes — professional diagnosis is recommended.

Can I drive? May not be drivable. Limp mode or no-start: transport to a shop.

Diagnostic approach

1. Read all stored codes with a capable bi-directional scan tool — A basic code reader may not display U-codes. Use a factory-level or professional scan tool that can communicate with all modules. Identify which specific module is missing from the network — companion codes like U0101 (TCM), U0121 (ABS module), or U0140 (BCM) pinpoint the offline device.
2. Check battery voltage and all ground connections — Measure battery voltage with the engine off (should be 12.4–12.6V) and running (13.8–14.4V). Inspect the main battery negative cable connections to the chassis and engine block. A marginal ground can cause intermittent CAN bus dropouts without setting a battery or charging fault.
3. Check fuses and power feeds for the suspected offline module — Identify the power and ground circuits for the module shown in the companion U-code. A blown fuse, failed relay, or open ground will take that module entirely off the CAN bus. Restore power/ground before attempting any further module diagnosis.
4. Inspect the CAN bus wiring harness and module connector — Trace the CAN High and CAN Low wires from the affected module back toward the OBD port. Look for chafing against heat shields or body panels. Unplug the module's connector and inspect for corrosion, bent pins, or pushed-back terminals. CAN bus resistance between CANH and CANL at the OBD port should typically read 60Ω with no modules powered (two 120Ω termination resistors in parallel).

Typical repair costs

Make & model notes

Chrysler / FCA: 2007–2013 Jeep, Dodge, and Chrysler products frequently develop U0100 from corrosion in the PCM connector (C4 connector on the firewall). The grey multi-pin connector is directly exposed to water intrusion. Inspect and re-pin or replace the connector before condemning the PCM itself.

General Motors: GM trucks and SUVs with 2003–2007 EBTCM (electronic brake and traction control module) assemblies can cause U0100 when the module develops an internal power supply fault and drops off the high-speed CAN bus. The module may need programming after replacement.

FAQ