B11E2

Code

Generic B — Body

Body Control Module — CAN bus communication fault

Brand: Generic

Type: B — Body

Views: UK: 13 EN: 23 RU: 20

AI status

Completed

ready

Completed 100%

Page language: EN

Causes

Open or short in CAN bus wiring
Poor or intermittent connector/terminal contact
Failed BCM or another communicating module
Missing or incorrect termination resistors
Low battery voltage or poor ground
Aftermarket device interfering with the bus

Symptoms

Multiple body functions nonfunctional or intermittent (locks, lights, windows, wipers, alarms)
Stored communication fault codes and/or lamp on dash (CEL or communications warning)
Modules not responding to scan tool or lost module message
Systems operate erratically or only after ignition cycles
Possible no-crank/no-start if BCM controls immobilizer or related networked modules

What to check

Read DTCs and freeze-frame data with a capable scan tool; note stored and pending codes and network topology
Visually inspect BCM connector, wiring harness, and nearby harness routing for damage, corrosion or water ingress
Verify battery voltage and engine/chassis grounds are good (measure at battery and BCM ground point)
Measure resistance across CAN H and CAN L with ignition ON (expect ~60 Ω if two 120 Ω terminators present)
Probe CAN H and CAN L with a multimeter/oscilloscope while ignition ON and engine off to verify voltages and signal activity
Disconnect aftermarket modules and retest

Signal parameters

CAN bus idle common-mode: ~2.5 V on CAN H and CAN L (recessive)
Dominant state: CAN H ≈ 3.5 V, CAN L ≈ 1.5 V (voltage difference ≈ 2.0 V)
Resistance between CAN H and CAN L with ignition ON: ≈ 60 Ω (two 120 Ω terminators in parallel)
Expected bus bit rates: commonly 125 kbps, 250 kbps, 500 kbps, or 1 Mbps depending on vehicle
Normal message frequency: depends on network; look for steady periodic frames from BCM and other nodes
High error frame rate or tx/rx error counters incrementing on oscilloscope/scan tool indicate physical or node faults

Diagnostic algorithm

Record all stored and pending codes and note which modules report loss of communication.
Perform a visual inspection of BCM connector, wiring, and related ground points for damage, corrosion, water, or loose pins.
Verify battery voltage and clean/tighten main chassis and BCM ground connections.
With ignition ON, measure DC voltage on CAN H and CAN L at the BCM connector; verify both near 2.5 V and that there is a differential when bus is active using an oscilloscope.
Measure resistance between CAN H and CAN L with ignition ON; confirm ≈ 60 Ω. If open or very high, check terminations and trunk wiring.
Use an oscilloscope or CAN bus analyzer to monitor traffic; identify missing expected messages, excessive error frames, or a node going bus-off.
Isolate sections of the bus: disconnect non-essential modules or unplug suspected nodes one at a time to find the bad device or short.
Inspect and continuity-test wiring from the BCM to the main CAN trunk and between connectors; repair any damaged wiring or corroded pins.
Clear codes and retest after each repair. If a single module is confirmed faulty, reprogram or replace the failed module per manufacturer procedures.
If network signals and wiring are good but fault persists, obtain BCM software updates and consider replacement only after confirming physical layer integrity.

Likely causes

Damaged CAN H or CAN L wiring near BCM (pin damage, chafing, rodent)
Loose BCM connector or bent pins
Short to battery or ground on one CAN line
Open circuit (broken wire) between BCM and main CAN trunk
Failed or out-of-spec termination (missing 120 Ω resistors resulting in ≠60 Ω across H-L)
Another module repeatedly going bus-off and flooding the network with error frames

Fault status

⚠️ Status

BCM detected CAN bus communication fault — no valid messages or excessive errors on network. Check physical layer (wiring, termination, grounds) and node health.

🟡 Repair difficulty: Medium

⏱️ Diagnostic time: 0.5-3.0 hours