Home / DTC / U0143 — Lost Communication With Body Control Module C

U0143 — Lost Communication With Body Control Module C

Detailed page for trouble code U0143.

32,355codes
58brands
9,901generic
22,454specific
Reset
Code

U0143

Generic U — Network/User

Lost Communication With Body Control Module C

Views: UK: 11 EN: 18 RU: 12
AI status
Completed
ready
Completed 100%
Page language: EN

Causes

  • Faulty Body Control Module (BCM C)
  • Open/short in the vehicle data bus (CAN, LIN or manufacturer-specific bus)
  • Missing or low module power or ground
  • Blown fuse or fusible link feeding the BCM
  • Corroded/loose connector pins at the BCM or gateway module
  • Water intrusion or physical damage to wiring or connector

Symptoms

  • Multiple convenience features inoperative (door locks, lighting, wipers, etc.)
  • Warning messages or lamp illumination on the dash related to body systems
  • Remote keyless entry, alarm or immobilizer faults
  • Other control modules report inability to communicate with BCM
  • Intermittent or permanent loss of features controlled by BCM
  • Possible no crank/no start if BCM provides inhibit functions

What to check

  • Read all stored U-codes and freeze frame with a capable scan tool; note module presence list
  • Check battery voltage (should be >12.2 V) and charging system condition
  • Inspect fuses/fusible links that feed the BCM and related modules
  • Visually inspect BCM connector and wiring for corrosion, bent pins, or water damage
  • Check for recent repairs or aftermarket accessory installations that tap into the data bus or power
  • Verify other modules on the same bus are present and communicating

Signal parameters

  • CAN High and CAN Low differential voltage at the BCM (idle ~2.5 V each, differential ~0 V; active frames ±1 V differential)
  • Presence and frequency of expected BCM message IDs on the bus (scan tool datastream)
  • Module supply voltage (VBATT) and ground continuity at the BCM
  • Wake/sleep line status if vehicle uses a separate wake signal
  • Bus error counters / bus-off status reported by other modules
  • LIN or other secondary bus traffic if BCM uses sub-buses

Diagnostic algorithm

  1. Retrieve freeze frame and all U/P codes; record which modules appear on the network.
  2. Verify battery voltage and stable supply; charge or replace battery if low.
  3. Inspect BCM fuses and related power distribution; replace any blown fuses and retest.
  4. Visually inspect BCM connector and harness for damage, corrosion, moisture or rodent damage; repair as needed.
  5. Check for aftermarket devices (alarms, remote starters) and disconnect them for testing.
  6. Using a scan tool, attempt to communicate with BCM C directly. Note whether the module responds, times out, or is absent.
  7. With ignition on, monitor CAN High/Low at the BCM connector with a multimeter or scope. Look for proper idle voltages and clean differential waveform; check for shorts to battery or ground.
  8. If bus signals are absent or noisy, isolate sections of the bus (disconnect nodes one at a time) to identify the fault source or bus-off node.
  9. Verify BCM supply and ground continuity at the module pins; repair wiring faults or poor grounds.
  10. If wiring and bus are good but module does not respond, check for available BCM software updates and reprogramming requirements, then consider replacement per manufacturer procedure.
  11. After repairs, clear DTCs, perform relearn/programming if required, and verify operation on a test drive. Re-scan to confirm code does not return.

Likely causes

  • Loss of BCM power or ground (battery disconnected, blown fuse, poor ground)
  • Faulty or corroded BCM connector causing intermittent pins
  • CAN bus short to ground/voltage or high resistance on CAN High/Low
  • BCM internal failure or software lockup
  • Gateway/module sleep/wake issue preventing BCM from responding

Fault status

⚠️ Status
Lost communication with Body Control Module C — module not responding on vehicle network. Check power, grounds, connectors, and data-bus integrity before replacing module.
🟡 Repair difficulty: Medium
⏱️ Diagnostic time: 1.0 - 3.0 hours

Similar codes

Your experience will help others
+100 karma for a short comment :)
Send to email