U0100 Code: Lost Communication with ECM/PCM

U0100 — Lost Communication with ECM/PCM: What It Means and How to Fix It

U0100 is one of those codes that can send a newer tech into a panic. The scanner lights up with a dozen codes at once, half the modules are reporting faults, and nothing makes sense. Before you start throwing parts at it, you need to understand what U0100 is actually telling you — and more importantly, what it is not telling you.

This article breaks down the U0100 code from the ground up: what network communication codes mean, how the CAN bus system works, how to find the real fault, and when you are dealing with a bad PCM versus a wiring problem. Most of the time, it is not the PCM. Let that sink in before you order a $1,200 module.

What U-Codes Actually Mean

Diagnostic trouble codes are sorted into categories by the first letter. P-codes are powertrain. B-codes are body. C-codes are chassis. U-codes are network communication codes — they tell you that one module lost the ability to talk to another module over the vehicle's communication network.

U0100 specifically means that a module on the network — typically the body control module, the instrument cluster, or another control unit — sent out a request or expected to receive data from the ECM or PCM, and got nothing back. The ECM/PCM went silent on the network. That is the plain-English version of the code.

The critical thing to understand is that U0100 is almost always a symptom code, not a root cause code. The module that set the U0100 is the one that noticed the PCM stopped talking. That does not mean the PCM itself is the problem. The PCM might be completely fine but unable to communicate because it lost power, lost ground, or the physical wire connecting it to the network is broken.

You will also see related codes like U0101 (lost communication with TCM), U0121 (lost communication with ABS module), and U0155 (lost communication with instrument panel cluster). When multiple U-codes show up at the same time, that is a strong indicator the problem is in the shared network infrastructure — the CAN bus itself — rather than any individual module.

CAN Bus Basics: How Vehicle Networks Work

Modern vehicles do not wire every sensor and switch directly to every module that needs that information. That would require hundreds of wires and would make the harness impossible to manufacture and repair. Instead, all the modules on the vehicle share a common communication network called a Controller Area Network, or CAN bus.

The CAN bus uses two wires: CAN High and CAN Low. These two wires form a twisted pair that runs throughout the vehicle, connecting every module that needs to share data. The twisting is intentional — it helps cancel out electrical interference. When you look at a wiring diagram, you will typically see these labeled as CAN H and CAN L, or sometimes CANH and CANL.

Data travels across the CAN bus as a differential signal. CAN High runs at approximately 2.5 volts at rest and swings up toward 3.5 volts when transmitting a dominant bit. CAN Low runs at approximately 2.5 volts at rest and swings down toward 1.5 volts when transmitting. The difference between the two lines is what carries the data. This differential design makes the system resistant to voltage spikes and electrical noise — important on a vehicle with all kinds of motors, coils, and solenoids generating interference.

At each end of the CAN bus there is a terminating resistor. These resistors are 120 ohms each and are installed to prevent the signal from bouncing back down the wire after it reaches the end of the network — a phenomenon called signal reflection. With both terminators in place, if you measure resistance across the CAN High and CAN Low wires at the OBD-II port with everything unplugged and the key off, you should see approximately 60 ohms. That is two 120-ohm resistors wired in parallel. If you see 120 ohms, one terminator is missing or open. If you see near zero ohms, the two wires are shorted together. If you see infinite resistance (OL), both terminators are open or the network wiring is broken.

Most vehicles run at least two separate CAN bus networks: a high-speed CAN for powertrain modules (PCM, TCM, ABS) and a lower-speed CAN for body modules (BCM, instrument cluster, HVAC). A gateway module — often the BCM or a dedicated gateway — bridges communication between these networks. This matters for diagnosis because a fault on the high-speed powertrain CAN might show up as a U0100 set by the BCM even though the BCM itself is on the low-speed network.

Common Causes of U0100

Power and Ground Issues at the PCM

This is the most common cause and the first thing you should check. The PCM needs multiple power and ground circuits to operate. On most vehicles, the PCM has at least two or three power feeds and two or three separate ground connections. If any of the primary power or ground circuits fail, the PCM may still crank and run on backup power but lose the ability to communicate on the network. The module essentially goes dark on the bus.

Corrosion at PCM ground straps is a frequent offender, especially on vehicles in the rust belt or vehicles that have been through flood damage. Pull the PCM connector and inspect the power and ground pins for green corrosion, pushed-back terminals, or signs of heat damage. Then go to the ground strap attachment point on the chassis or engine block and make sure it is clean and tight.

Wiring Damage — Cuts, Chafing, and Shorts

The CAN bus wires run through the vehicle in harnesses that are exposed to heat, vibration, and sharp edges. Common failure points include the main engine harness where it passes over the top of the engine near exhaust components, harness routing points where the wire rubs against a bracket, and the firewall passthrough grommet where wires can chafe on the sheet metal edge.

A shorted CAN High to CAN Low is particularly damaging because it essentially kills the entire network segment. Nothing can communicate. Look for wiring damage anywhere the harness has been repaired before, anywhere it routes near hot components, and anywhere a previous technician may have done aftermarket wiring work.

Water Intrusion

Water in connectors is a major cause of U0100 on GM trucks, Ford trucks, and many European platforms. Water does not just cause corrosion — it can cause a direct short between CAN H and CAN L wires inside the connector, or it can raise the resistance of a ground circuit high enough that the module can no longer communicate properly.

Common water entry points include the PCM connector itself (PCMs are often located in the engine compartment where rain or pressure washing can force water into the connector), firewall grommets that have pulled loose, and underhood fuse and relay centers where the cover seal has deteriorated. On some vehicles — particularly Chrysler minivans from the 2000s — the PCM is mounted in a location that is almost guaranteed to get wet over time.

Aftermarket Electrical Installations

Remote starters, aftermarket radios, alarm systems, and trailer wiring kits are a major source of CAN bus problems. An installer who taps into the CAN wiring without understanding the network can add unintended load to the bus, short the wires during installation, or install a device that floods the network with traffic and crowds out legitimate module communication.

If a vehicle comes in with U0100 and has any aftermarket electrical work, that is where you start. Disconnect the aftermarket device entirely — not just turn it off — and retest. If the U-codes go away, you found your problem.

Failed PCM

Yes, the PCM itself can fail and cause U0100. Internal failures in the PCM's CAN transceiver — the circuit inside the module that actually drives the CAN bus signal — will take the module off the network. This is more common on PCMs with known solder joint failures (GM E38 and E67 controllers have a history of this), PCMs that have been exposed to moisture, and on high-mileage vehicles where the internal capacitors have degraded.

The important rule here: do not replace the PCM until you have confirmed that the network and the PCM's power and ground circuits are good. A failed PCM is the last thing you check, not the first.

Failed Module Pulling Down the Bus

A module other than the PCM can cause U0100. If a module's CAN transceiver shorts internally, it can hold the CAN bus in a permanent dominant state, which prevents all communication on that network segment. This is called a bus-off condition. Every other module sees the bus as stuck and stops trying to communicate. The result is every module setting U-codes against every other module — a flood of communication faults that looks like everything failed at once.

To find a module pulling down the bus, you unplug modules one at a time while watching the CAN bus voltage with a multimeter or lab scope. When the bus voltage returns to normal after unplugging a specific module, that is your culprit.

Diagnostic Procedure

Step 1 — Scan All Modules and Document Everything

Before you clear anything, scan every module on the vehicle and write down every code in every module. The pattern of U-codes tells you a story. If every module has U0100, you likely have a network infrastructure problem (wiring, terminators, or a module holding the bus down). If only one or two modules have U0100, the fault may be more isolated.

Step 2 — Check PCM Power and Grounds First

Pull up the wiring diagram for the PCM power and ground circuits. With the key on and the PCM connector plugged in, verify that all power feeds show battery voltage. Then verify that all ground circuits show less than 0.1 volt drop between the PCM ground pin and the battery negative terminal. A ground with 0.3 volts or more of voltage drop under load is a problem. Do not skip this step — most technicians who replace unnecessary PCMs did not do this step.

Step 3 — Measure Terminating Resistance

Key off. Disconnect the battery negative cable. At the OBD-II port, measure resistance between pin 6 (CAN High) and pin 14 (CAN Low). You should see approximately 60 ohms. If not, refer to the vehicle-specific wiring diagram to locate the terminating resistors — some are inside modules, some are standalone components in the harness — and test them individually.

Step 4 — Scope the CAN Bus

If you have a lab scope, connect it to CAN High and CAN Low at the OBD-II port and observe the waveform with the key on and communication active. A healthy CAN bus shows a clean differential signal with CAN High and CAN Low mirror-imaging each other around the 2.5-volt center point. A flat line on both channels means nothing is communicating. A noisy, erratic signal points to interference or a marginal connection. A single channel that looks abnormal while the other is flat points to a broken wire on that specific line.

Step 5 — Isolate Modules to Find a Bus-Pulling Fault

If the bus is stuck in a dominant state (CAN High stuck near 3.5V, CAN Low stuck near 1.5V, or both stuck near the same voltage), start unplugging modules one at a time, starting with the easiest to access. After each unplug, recheck bus voltage. When the bus comes back to the correct resting state of approximately 2.5 volts on both lines, the module you just unplugged is pulling the bus down.

Step 6 — Inspect Wiring and Connectors

Use the wiring diagram to trace the CAN bus harness from the OBD-II port to the PCM connector. Look for any signs of chafing, repair tape, previous splice work, or proximity to heat sources. Inspect the PCM connector pins under magnification for corrosion, bent terminals, or moisture. If the vehicle has had underhood work recently, look for pinched wires or disturbed connectors in the area that was worked on.

Step 7 — PCM Replacement as Last Resort

If you have confirmed good power and grounds at the PCM, confirmed good CAN bus wiring integrity, confirmed correct terminating resistance, verified no other module is pulling the bus down, and the PCM still does not communicate — now you have built a case for PCM replacement. Document your diagnostic steps. On most platforms, a replacement PCM will require programming and possibly a security relearn procedure, so plan for that time and cost before you commit the customer to the repair.

Vehicles with Known U0100 Issues

Certain platforms show up repeatedly with U0100 in the shop. Knowing the common failure pattern on a specific vehicle saves diagnostic time.

Vehicle	Common Root Cause	Where to Look First
GM Silverado/Sierra 2007-2013	Corroded PCM connector, failed E38/E67 PCM solder joints	PCM connector pins, PCM ground circuit voltage drop
Dodge/Chrysler Minivans 2001-2007	Water intrusion at PCM (mounted near cowl)	PCM connector for moisture and green corrosion
Ford F-150 2004-2008	Chafed CAN wiring in engine harness near firewall	Engine harness routing along firewall, firewall grommet
Jeep Grand Cherokee 2011-2013	TIPM (fuse box) internal failure affecting module power	TIPM relay outputs for PCM power feeds
GM Equinox/Terrain 2010-2017	Corroded ground splice in engine harness	Ground splice packs near firewall, PCM ground terminals
BMW 3/5 Series E90/E60	Aftermarket remote starters overloading K-CAN, DME power relay	Disconnect aftermarket devices, check DME relay and fuse

Wiring Repair Versus Module Replacement

The single most important decision in a U0100 diagnosis is whether you are dealing with a wiring problem or a failed module. Here is a straightforward way to think about it.

If the vehicle has multiple U-codes involving different modules losing communication with each other — not just the PCM — the problem is almost certainly the network wiring or a shared power/ground circuit. A PCM does not take out the TCM, ABS module, and instrument cluster all at once just by failing. But a broken CAN wire or a shorted bus will affect every module on that network segment simultaneously.

If the vehicle has only U0100 and no other U-codes, and the PCM is confirmed to have good power and grounds, and the CAN bus wiring checks out, then a failed PCM becomes a realistic possibility. Internal PCM transceiver failures typically result in the PCM going completely silent — it does not set its own codes because it cannot communicate to report them. Other modules notice the silence and set U0100.

A PCM that is actually running the engine but setting U0100 is a contradiction worth noting. If the engine starts and runs, the PCM is alive. The communication failure is likely intermittent or limited to one network port. Some PCMs have separate CAN ports for different networks, and a failure of one port does not necessarily kill the others.

Wiring repairs on CAN bus circuits need to be done correctly. The twisted pair must be maintained — untwisting the wires over even a short length can degrade signal quality. Use the appropriate crimp splice connectors, heat shrink the repair, and reroute the harness away from whatever caused the original damage. A sloppy splice on a CAN wire that was done right before selling the vehicle is the kind of repair that comes back and bites the next owner.

Clearing Codes and Verifying the Repair

After any repair related to U0100, you need to verify that all modules can communicate before you call it done. The best way to do this is to scan all modules after the repair and confirm that no U0100 or related U-codes return. Then perform a complete drive cycle if any powertrain monitors need to run.

On vehicles where the PCM was replaced, verify the programming is confirmed correct, the VIN in the new PCM matches the vehicle, and any security or immobilizer relearn procedures are completed. A PCM that is not properly programmed to the vehicle will set communication faults of its own and send you back to square one.

U0100 is not a code that forgives sloppy diagnosis. Take the time to understand the network, follow the diagnostic steps in order, and build a clear picture of what is wrong before you replace anything. The technicians who do this well are the ones who do not eat the cost of a PCM they should not have ordered.