B2279

Code

Generic B — Body

Body Control Module Communication Fault

Brand: Generic

Type: B — Body

Views: UK: 4 EN: 10 RU: 7

AI status

Completed

ready

Completed 100%

Page language: EN

Causes

Loss of power or ground to BCM
Open, shorted, or high-resistance wiring/connectors on network lines
CAN/LIN bus fault (short to battery/ground, bus-off condition)
Blown fuse or faulty relay supplying BCM
Software corruption or module flash failure
Faulty BCM or another module causing network issues

Symptoms

Multiple body systems inoperative or intermittent (lights, locks, wipers)
Instrument cluster warnings for communication or module faults
Inability to communicate with BCM using a scan tool
Stored or active related network DTCs (U-codes, other B-codes)
Vehicle may fail to lock/unlock, start, or enable certain features

What to check

Check battery voltage and health; verify stable 12V supply with key on
Scan vehicle for related DTCs on other modules (U-codes, B-codes)
Visually inspect BCM connector(s) for corrosion, bent pins, or water intrusion
Check relevant fuses and relays feeding BCM
Perform a wiggle test on wiring harness while monitoring communication
Measure CAN/LIN bus voltages and continuity

Signal parameters

CAN bus: two-wire differential signal. Typical idle voltages ~2.5V on CAN_H and CAN_L; dominant state shifts CAN_H higher and CAN_L lower (differential present). Expected differential under dominant ~1.0–2.5V depending on network.
Common CAN data rates: 125 kbps, 250 kbps, 500 kbps (verify vehicle specification).
LIN bus: single-wire serial line, idle pulled up to battery voltage through resistor; expect idle near VBATT and low pulses during traffic.
Wake/sleep behavior: BCM should respond to wake commands from gateway or diagnostic tool; long-term inactivity may indicate bus-off or module asleep.

Diagnostic algorithm

Retrieve freeze frame and full DTC list from BCM and gateway; note related U- and B-codes and history.
Verify battery voltage >=12.4V with ignition off and >=13.5V with engine running or charging system active. Recharge or load-test battery if low.
Inspect BCM connectors, harness routing, and grounds for corrosion, water, or damaged insulation; repair any physical defects.
Check fuses/relays for BCM power and replace if blown. Verify power/ignition feeds at BCM connector with a meter.
Using a good-quality diagnostic scanner, confirm whether the BCM appears on the network and can be commanded. Note if the module is intermittently present.
Probe CAN_H/CAN_L (or LIN) at the BCM and at other module nodes: measure idle voltages, continuity, and resistance between CAN_H and CAN_L (~60 ohms for two 120-ohm terminators in parallel).
If bus voltages are abnormal, isolate sections of the bus by disconnecting modules or harness branches to find a short or faulty node.
Inspect for modules in bus-off state (some tools report). Clear codes and attempt to re-establish communication; if bus-off persists, identify offending node.
If wiring and power/ground are good but communication fails, consider reflashing BCM software or performing module reset per manufacturer procedures.
If all previous steps fail and replacement is required, replace BCM with a known-good unit and program/configure to vehicle specifications. Re-scan and verify full system functionality.
Safety note: Avoid live pin-to-pin backprobing that can short terminals. Follow vehicle manufacturer procedures for module programming and immobilizer alignment.