MotorCodex Español

U0140 — Lost Communication — Body control module (BCM)

Moderate

Quick answer

U0140 means modules on the vehicle’s communication network lost contact with the body control module (BCM). Symptoms look electrical-gremlin: lights, wipers, locks, or gauges misbehaving while the engine runs fine. Start with the basics that cause most network codes: battery health, clean tight grounds, and any recently installed accessory.

What it means

Modern vehicles run dozens of computers connected by a network (CAN bus) — two wires carrying everyone’s messages. U0140 sets when expected messages from the body control module (BCM) stop arriving.

Network codes feel intimidating but follow ordinary electrical logic: a module goes silent because it lost power or ground, its network wiring is damaged, the whole bus is disturbed, or — least often — the module itself died.

Two patterns matter: ONE lost-comm code points at that module and its wiring; MANY lost-comm codes at once point at shared causes — the bus wiring, a failing battery, or one faulty module dragging the network down. Low system voltage is the great impersonator here: a dying battery can set a storm of U-codes that all vanish with a healthy battery.

Common causes

Ordered from most to least likely.

  1. 1.

    Weak battery or poor ground connections

    The #1 cause of intermittent network codes — modules brown-out and drop off the bus.

  2. 2.

    Blown fuse or lost power feed to the module

    Check every fuse related to the silent module first.

  3. 3.

    Damaged CAN wiring or connectors

    Chafed twisted-pair wiring, water in a connector, corroded pins.

  4. 4.

    Aftermarket electronics tapped into the bus

    Remote starts, stereos, and trackers installed onto CAN wiring are infamous for this.

  5. 5.

    Failed module

    Real, but the last conclusion — only after power, ground, and wiring test good.

How to diagnose it, step by step

Cheapest and most likely checks first.

  1. 1 Scan every module and map who’s missing

    A full-system scan shows which modules respond and which U-codes exist where. One silent module vs. many tells you whether to chase a module or the bus.

  2. 2 Test the battery and grounds

    Load-test the battery, then clean and tighten the main grounds (battery-to-body, body-to-engine). Do this before any wiring archaeology — it resolves a remarkable share of network codes.

  3. 3 Check fuses and power at the module

    Find the silent module’s fuses and verify battery voltage and ground at its connector.

  4. 4 Review recent work and accessories

    If the code appeared after a stereo, remote start, or any repair, that installation is suspect number one — inspect where it tapped power and network wiring.

  5. 5 Test the CAN bus if multiple modules are down

    With the battery disconnected, resistance across the CAN pair at the OBD port (pins 6 and 14) should read ≈60 Ω. Far off means a bus wiring problem or a failed terminating module.

Parts & tools you may need

  • Full-system OBD-II scanner (reads all modules, not just engine)
  • Digital multimeter
  • Battery load tester (or free test at a parts store)
  • Electrical contact cleaner and dielectric grease

Disclosure: some links are affiliate links. If you buy through them, we may earn a commission at no extra cost to you.

Related codes

Frequently asked questions

Can I drive with U0140?
Often the vehicle remains drivable with the affected system degraded. Treat losses of safety modules (ABS) with respect, and remember intermittent network faults tend to get worse, not better.
Why did several U-codes appear at once?
A shared cause: the bus wiring, low system voltage (weak battery), or one failed module disturbing the network. Don’t chase each code separately — find the common factor.
Did a jump start cause this?
It can — voltage spikes during jump starts occasionally upset or damage modules. Many post-jump U-codes are just stored history: clear them and see what returns.
Do I need a dealer?
For battery/ground/fuse/wiring causes, no — a multimeter and patience suffice. If a module is genuinely dead, replacement often requires programming, which usually means dealer or a well-equipped shop.