U0100 – Lost communication with ECM/PCM

Last updated: April 9, 2026

U0100 means your vehicle lost communication with the ECM/PCM, so other modules cannot “see” the engine computer on the network. You may get a no-start, a stall, or a car that runs in limp mode. In other cases it only turns on warning lights and stores codes. According to factory diagnostic data, this code indicates a loss of data messages from the ECM/PCM, not a confirmed bad ECM/PCM. SAE J2012 makes U-codes intentionally general. That vagueness forces you to identify which network segment, power feed, ground, or connector caused the drop-out.

🔍Look up your vehicle's recalls, specs & safety ratings — free VIN decoder with NHTSA data

U0100 Quick Answer

U0100 points to a network communication loss with the ECM/PCM. Check ECM/PCM power and grounds first, then verify CAN network integrity and connector condition before you suspect a module.

What Does U0100 Mean?

U0100 is defined as “Lost communication with ECM/PCM.” Another control module set the code because it could not communicate with the ECM/PCM. In practice, that means the module lost critical engine data like torque requests, RPM, throttle, and emissions status. The vehicle may disable functions that depend on that information.

Technically, modules monitor network message traffic and expect valid ECM/PCM data within a certain time window. When those messages stop, the receiving module flags U0100 and often sets additional U-codes. The code does not prove the ECM/PCM failed. You must confirm whether the ECM/PCM went offline due to lost power/ground, a network fault, or an internal reset.

Theory of Operation

Modern vehicles use a controller network to share data between modules. The ECM/PCM broadcasts engine operating data over the network while the ignition stays on. Other modules use that data for shifting, stability control, HVAC load control, and charging strategy. A scan tool also relies on that same path to talk to the ECM/PCM.

U0100 sets when the receiving module stops seeing ECM/PCM messages. Power or ground loss at the ECM/PCM can take it offline instantly. A short, open, or high resistance in CAN wiring can block messages. A corroded connector can create intermittent dropouts that look like a “bad computer,” especially on bumps or during cranking.

Symptoms

U0100 symptoms depend on whether the ECM/PCM actually goes offline or only drops out intermittently.

• Scan tool no-communication with the ECM/PCM, missing ECM/PCM in the module list, or intermittent scan tool dropout
• No-start with normal cranking because fuel injection or spark control stops when the ECM/PCM is offline
• Stall while driving that feels like an ignition switch cut, sometimes restarting after a key cycle
• Limp mode with limited throttle response or fixed gear operation when other modules lose engine torque data
• Multiple U-codes in several modules, often pointing to a common “lost comm” event
• Warning lights such as MIL, traction control, ABS, or power steering warnings triggered by missing ECM/PCM data
• Intermittent gauges like tachometer or temperature display acting erratic if the cluster depends on ECM/PCM messages

Common Causes

• ECM/PCM power feed loss (fuse, relay, or power distribution fault): When the ECM/PCM loses B+ or ignition feed, it stops transmitting network messages and other modules log U0100.
• High-resistance ECM/PCM ground path: Corrosion, a loose ground bolt, or a partially broken ground cable can let the ECM/PCM boot intermittently, which breaks communication during crank or electrical load.
• CAN bus open circuit (CAN-H or CAN-L): A break in either network wire stops differential signaling, so modules cannot “hear” the ECM/PCM even if it still powers up.
• CAN bus short to power or short to ground: A short forces the bus out of its normal biased state and blocks message traffic, which often triggers multiple U-codes with U0100 among them.
• Connector problems at the ECM/PCM (water intrusion, backed-out pins, fretting): Small increases in terminal resistance can drop network integrity or module power/ground just enough to cause intermittent loss of communication.
• Harness damage near the engine or battery (rub-through, heat damage, rodent damage): Movement and vibration can open the network or power circuits briefly, which sets U0100 without leaving an obvious hard failure.
• Another module or accessory pulling the network down: A shorted module, aftermarket device, or wrong radio/alarm install can load the CAN lines and prevent the ECM/PCM from communicating.
• ECM/PCM internal fault or software issue: If power, grounds, and network wiring check good, the ECM/PCM may stop responding due to an internal failure or corrupted logic that requires OEM-level confirmation.

Diagnosis Steps

Tools you need: a scan tool that can run a full network scan and show module “present/not present,” a DVOM for voltage-drop testing, and basic back-probing tools. A wiring diagram and fuse/relay layout are mandatory. If you have a lab scope, use it to confirm CAN signal quality during an intermittent U0100 event.

1. Confirm U0100 as stored, pending, or history and record freeze frame data. Focus on ignition state, vehicle speed, battery voltage, and any companion U-codes. Freeze frame shows conditions when the fault set. Use a scan tool snapshot during a road test to catch intermittent dropouts live.
2. Run a full network scan and note if the ECM/PCM appears “online.” If the ECM/PCM does not show up, treat U0100 as a no-communication condition first. If it shows up, look for other modules reporting lost comms and follow the pattern.
3. Check for pending vs confirmed behavior. Many communication faults act like Type B logic on some platforms. A pending U0100 that does not return may point to a brief voltage dip or connector issue. A hard fault often returns immediately at key-on when the ECM/PCM stays offline.
4. Inspect fuses, relays, and power distribution that feed the ECM/PCM before probing the ECM/PCM connectors. Verify the correct fuses for both battery and ignition feeds. Load-test suspect fuses and relay outputs with the circuit powered, not with an ohmmeter.
5. Verify ECM/PCM powers and grounds with voltage-drop testing under load. Back-probe the ECM/PCM power feed while the circuit is operating and check drop across the feed path. Then voltage-drop the ECM/PCM ground path while cranking or with key-on loads active. Keep ground drop under 0.1V with the circuit operating.
6. Check the ECM/PCM wake-up and ignition feed logic. Watch for power that disappears during crank, relay chatter, or a feed that only fails with accessories on. A module can pass a static check and still reset under load.
7. Inspect the ECM/PCM connectors and the harness routing. Look for water tracks, green corrosion, spread terminals, and pushed-back pins. Pay close attention to areas near the battery, underhood fuse box, and tight bends by brackets.
8. Verify CAN bus integrity at an accessible connector or at the ECM/PCM connector with ignition OFF for resistance checks. Compare readings to the service information for the vehicle. Do not guess values. If resistance indicates an open or short, isolate by disconnecting modules per the OEM pinpoint test path.
9. Check CAN line bias and activity with ignition ON. Communication line bias voltage only appears when the network powers up, so ignition-off voltage readings do not help. If you use a scope, confirm both lines show clean differential activity and no line stuck high or low.
10. If the network looks healthy, isolate a network “bully.” Disconnect aftermarket devices first, then disconnect suspected modules one at a time following the wiring diagram. Re-run the network scan after each change and note when the ECM/PCM returns online.
11. After repairs, clear codes and confirm the fix. Run a key cycle, re-scan for module presence, and road test under the freeze frame conditions. Capture a scan tool snapshot during the test drive if the fault acted intermittent. Verify U0100 stays cleared and no new U-codes set.

Professional tip: When U0100 appears with a no-crank or stall complaint, load-test the ECM/PCM grounds first. A ground that drops to several tenths of a volt during crank can reboot the controller. The scan tool will show “lost comm” long before you spot the ground issue visually.

Possible Fixes

• Restore ECM/PCM power feed: Repair the failed fuse connection, relay, or power distribution fault confirmed by loaded voltage-drop testing.
• Repair ECM/PCM ground integrity: Clean and tighten ground points, replace damaged ground cables, and re-test with a loaded voltage-drop to confirm less than 0.1V drop.
• Repair CAN bus wiring faults: Fix opens, shorts to power, or shorts to ground in CAN-H/CAN-L and secure the harness to prevent repeat rub-through.
• Service ECM/PCM and network connectors: Remove corrosion, correct terminal fit, repair pin damage, and address water intrusion sources before reassembly.
• Remove or rewire aftermarket equipment affecting the network: Correct splices, restore twisted-pair routing, and eliminate devices that load the CAN lines.
• OEM-level ECM/PCM verification and programming: If all external circuits test good, follow the manufacturer test plan for module failure and perform reflash or replacement only after confirmation.

Can I Still Drive With U0100?

You should treat U0100 as a “no-trust” network fault. The vehicle may still start and drive if the ECM/PCM comes back online quickly, but drivability can change without warning. Many vehicles default to limp mode, fixed throttle strategy, or harsh shifting when other modules lose ECM/PCM data. If the engine stalls, will not restart, or the transmission locks in one gear, stop driving and tow it. Also avoid highway driving if the code appears with multiple warning lights, low system voltage, or a dead scan tool connection. Those signs point to a power, ground, or CAN issue that can drop the ECM/PCM offline again at any moment.

How Serious Is This Code?

U0100 ranges from an inconvenience to an immediate no-start, depending on when communication drops. If the fault stores as history and the car drives normally, you may have a momentary voltage dip or connector issue. If U0100 sets as current and several modules show “no communication,” the risk jumps fast. The ECM/PCM supplies torque, throttle, fueling, and emissions control decisions. Losing it can cause stalling, reduced power, and unpredictable shift behavior. Ignoring the fault can also create collateral codes, mislead diagnosis later, and strand the vehicle. Treat repeated U0100 as high severity until you prove power, grounds, and network integrity.

Common Misdiagnoses

Techs often replace the ECM/PCM too early on a U0100 code. That mistake happens when the scan tool cannot connect and the technician assumes the module died. . Another common miss involves CAN wiring. A rubbed-through CAN-H/CAN-L pair, water in a splice pack, or an aftermarket remote start can pull the bus down and “silence” the ECM/PCM. Avoid wasted spending by first checking module power and ground with a loaded voltage-drop test, then proving the network stays alive with a full module scan.

Most Likely Fix

The most frequent repair direction for U0100 is restoring clean power and ground to the ECM/PCM. That usually means repairing a poor ground, replacing a failing battery, fixing a loose terminal, or correcting a fuse/relay feed that drops under load. The next most common direction involves the CAN network. Look for corrosion at connectors, water intrusion at harness junctions, or wiring damage near the radiator support and battery tray. After the repair, confirm stability by running the engine, wiggling the harness, and repeating a full module scan. Drive time needed to confirm varies by platform, so follow service information for enable conditions and recheck for pending U0100.

Repair Costs

Network and communication fault repairs vary by root cause — wiring/connectors are often the source, but module-level repairs or replacements can be significantly more expensive.