U0100 means "lost communication with ECM/PCM A": another module on the vehicle network expected messages from the engine computer and stopped receiving them. In most cases the ECM itself is fine. The usual causes are a power or ground problem at the ECM, a blown fuse, a weak battery, or a fault in the CAN bus wiring or connectors. Diagnose U0100 lost communication with the ECM in this order: check battery voltage, check the ECM's fuses, powers and grounds, measure the CAN lines, then run a full-system scan to see which modules can still talk. Only condemn the ECM once all of that passes.
Launch Dealer SA is based in Midrand, South Africa, and supplies LAUNCH diagnostic tools to workshops in South Africa and across Africa. This guide covers the generic network checks that apply to most modern vehicles. For model-specific pin numbers and wiring colours you still need the manufacturer's wiring diagram. If you are new to reading codes, start with our fault codes guide.
What U0100 means
Codes that start with U are network (communication) codes. They are set by a module that is listening, not by the module that has gone quiet. When the ABS unit, the instrument cluster, the body module or the transmission computer stops hearing the ECM's regular messages for long enough, it stores U0100.
That has two practical consequences:
- The code is usually stored in a module other than the ECM. You often find U0100 in the ABS, cluster or gearbox module, and you may find nothing in the engine computer at all, because it could not be reached.
- The symptom depends on the vehicle. Depending on how the network is built, you may see a no-start, the engine running but the gauges dropping out, several warning lights at once, or limp mode in the gearbox.
U0100 can also be stored as an old, intermittent event after a flat battery, a jump start or a disconnected connector. Note whether it is current or historic before you start pulling wiring apart. You will see this code on all kinds of vehicles, including U0100 on Toyota and U0100 on Ford Ranger bakkies, but the diagnosis follows the same logic.
Power and ground first
A module that has lost power or ground cannot talk, so it looks exactly like a network fault. Start here, because it is the cheapest check and the most common cause.
- Battery and charging. Check the resting battery voltage and the voltage while cranking. A weak battery can drop the voltage low enough for modules to reset and set communication codes. Load-test it if you have any doubt.
- Fuses and relays. Check every fuse and relay that feeds the ECM using the wiring diagram, including the main relay and any ignition-switched feed. Test fuses with a meter or test light, not by eye.
- Powers at the ECM connector. Back-probe the ECM's battery and ignition feeds with the key on. Measure them under load, because a corroded terminal can show the right voltage with no load and collapse when the ECM draws current.
- Grounds. Do a voltage-drop test on the ECM grounds and the engine-to-body earth straps. A bad ground is a classic cause of U0100, especially on vehicles that have had engine work, accident repairs or water exposure.
If the ECM has no power or no ground, fix that first and recheck. Many U0100 jobs end at this step.
CAN high and low checks
If power and ground are good, look at the network itself. Most modern vehicles use a high-speed CAN bus with two twisted wires, CAN high and CAN low. These are generic CAN values. Always confirm the exact pins and expected values for the vehicle in its manual.
- Voltage at rest. With the network awake, CAN high and CAN low each typically sit around 2.5 V relative to ground when the bus is idle. When modules transmit, CAN high rises and CAN low falls by roughly the same amount. A line stuck at 0 V, stuck at battery voltage, or with both lines reading the same while traffic should be present points to a short.
- Termination resistance. A high-speed CAN bus normally has two 120 ohm terminating resistors, one at each end. With the battery disconnected, measuring across CAN high and CAN low at the diagnostic connector should give about 60 ohm. About 120 ohm suggests one terminator or one branch of the network is open. A reading near 0 ohm suggests the two lines are shorted together.
- Shorts to ground or power. With the battery disconnected, check each CAN line to ground and to battery positive. Either one should not show a short.
- Wiring and connectors. Inspect the harness between the diagnostic connector and the ECM, especially where it passes the engine bay, near the battery, and at any connector that has been unplugged recently. Look for corrosion, pushed-back pins and chafed insulation.
An oscilloscope gives the clearest picture of the CAN signal, but a good multimeter and the wiring diagram will find most faults.
Full-system scan: who is talking
This is where the scan tool saves the most time. A full-system scan polls every module the tool knows about on that vehicle and shows which ones respond. That gives you a map of the problem:
- Only the ECM is missing. If every other module responds and the ECM does not, focus on the ECM's own power, ground, connector and its branch of the network.
- Several modules are missing. If a group of modules drops out together, the fault is more likely in a shared part of the network, a shared power feed, or one faulty module dragging the bus down.
- Nothing communicates. Check the diagnostic connector's own power and ground first, then look for a short across the whole bus.
Save the scan report before you start testing. Run it again after each repair to confirm the modules are back online and the U codes have changed from current to historic. Then clear the codes and run a final scan.
A tool that only reads engine codes through generic OBD2 cannot show you this picture. You need a full-system tool with coverage for the make you are working on. Our live data guide explains what to watch once communication is restored.
Common causes
In rough order of how often they turn up in a workshop:
- Battery, charging or jump-start problems causing low or unstable voltage.
- Blown fuses or a failed main relay feeding the ECM.
- Poor grounds, including corroded earth straps and loose ground bolts.
- Connector problems at the ECM or along the network, such as corrosion, water ingress or pins pushed back after repairs.
- Harness damage, such as chafing, rodent damage or poorly done previous repairs.
- Aftermarket accessories (alarms, trackers, audio) spliced into the network or power feeds.
- Another module shorting the bus. Unplugging modules one at a time while you watch the termination resistance or bus voltage can find a module that is pulling the network down.
When it is the ECU
The ECM itself is the least likely cause, and it is an expensive one to get wrong. Consider it only when:
- powers and grounds at the ECM are good under load,
- the CAN lines at the ECM connector read correctly,
- the rest of the network communicates, and
- the ECM still does not respond to the scan tool.
Even then, check for water damage or corrosion inside the connector before replacing anything. A replacement ECM usually needs coding, immobiliser matching or online programming before the vehicle will run, so confirm what the job involves before you quote. If you are unsure whether your tool can do that for a particular vehicle, check with us.
Which LAUNCH tool fits the job
For network faults the key features are full-system scanning across the makes you see, saved reports, and live data. Two options in stock right now:
- [LAUNCH X431 PROS Elite](/products/launch-x-431-pros-elite-professional-diagnostic-scanner) (R11,590): full-system bi-directional diagnostics with CAN FD and DoIP support listed on the product page. A strong choice for a general workshop that needs reliable full-system scans and reports.
- [LAUNCH X431 PRO3 APEX](/products/launch-x431-pro3-apex-obd2-scanner) (R21,490): lists CAN FD, DoIP and J2534 support and comes with a non-16-pin adapter set, which helps on older and imported vehicles.
For a larger multi-brand workshop, the LAUNCH X431 V+ 5.0 PRO3 (R31,500) is a full-system bi-directional option. Every tool is sold for your sales territory. Software coverage differs by make and model, so tell us what you work on before you buy.
Can't get to Midrand? Book a WhatsApp video demo. You can also visit us at Shop AG008, Midrand Motor City.
FAQ
Can a bad battery cause U0100?
Yes. A weak or failing battery, a bad charging system or a recent jump start can drop the voltage low enough for modules to reset and lose communication. Test and charge the battery first, clear the codes, and see if U0100 returns before you look further.
What is the difference between U0100 and U0001?
U0100 points to lost communication with one module, the ECM/PCM. U0001 points to a problem with the high-speed CAN communication bus itself. If you see U0001 with several "lost communication" codes, suspect the shared network wiring or a module pulling the bus down rather than the ECM alone.
Can I drive with U0100?
It is not advisable. Depending on the vehicle, U0100 can cause stalling, a no-start, limp mode, or gauges and safety systems that stop working. Get it diagnosed before relying on the vehicle, especially if the code is current.
Questions we get asked
Can a bad battery cause U0100?
Yes. A weak or failing battery, a bad charging system or a recent jump start can drop the voltage low enough for modules to reset and lose communication. Test and charge the battery first, clear the codes, and see if U0100 returns before you look further.
What is the difference between U0100 and U0001?
U0100 points to lost communication with one module, the ECM/PCM. U0001 points to a problem with the high-speed CAN communication bus itself. If you see U0001 with several lost-communication codes, suspect the shared network wiring or a module pulling the bus down rather than the ECM alone.
Can I drive with U0100?
It is not advisable. Depending on the vehicle, U0100 can cause stalling, a no-start, limp mode, or gauges and safety systems that stop working. Get it diagnosed before relying on the vehicle, especially if the code is current.


