B1C60

Code

LAND ROVER B — Body

retransmit

Brand: LAND ROVER

Type: B — Body

Views: UK: 15 EN: 22 RU: 21

AI status

Completed

ready

Completed 100%

Page language: EN

Causes

Intermittent or failed communication on a vehicle data bus (CAN, LIN, FlexRay, etc.)
Damaged, corroded or loose connector or pin at one or more modules
Short or open in the bus wiring or shield
Poor ground or low battery/voltage irregularity
Faulty control module requesting or failing retransmits
Excessive network load or noise (aftermarket devices, damaged shield)

Symptoms

Intermittent or permanent loss of function for systems controlled over the affected bus (e.g., instruments, ABS, body functions)
Multiple communication-related DTCs present across modules
Modules appear to go asleep or wake repeatedly
Instruments flicker or show incorrect data
Poor starting or engine management anomalies if powertrain bus affected

What to check

Read all stored and pending DTCs from every module on all vehicle networks and note freeze frame data
Check battery voltage and health; ensure good charging system and stable supply during tests
Visually inspect connectors and wiring for the modules reporting communications or in common harness areas (corrosion, pushed out pins, broken clips)
Backprobe module connector power and ground circuits; verify solid grounds and proper supply voltages
Check bus termination resistances (e.g., ~60 ohms for two 120Ω CAN terminations in parallel) with power off where appropriate
Wiggle test harnesses and connectors while monitoring DTCs and live data to try to reproduce the fault

Signal parameters

Typical CAN idle (recessive) approx. 2.5 V on CAN_H and CAN_L relative to ground; dominant state pulls CAN_H ≈ 3.5–4.0 V and CAN_L ≈ 1.0–1.5 V (differential ≈ 2 V)
Bus termination: two 120 Ω resistors in parallel (~60 Ω) on CAN high-speed networks
LIN idle ~ battery voltage via pull-up; dominant low to near 0 V
Expected message timing: check OEM network specification for message frequency and payload sizes (compare to live capture)

Diagnostic algorithm

Retrieve all network-related codes from every module; record module IDs and timestamps. Clear codes and attempt to reproduce the issue.
Confirm vehicle battery and charging system are within spec; ensure no low-voltage events during testing.
Inspect visually: open connector seals, check pin corrosion, bent pins, water intrusion in relevant modules and junction blocks. Repair or reseal as needed.
Verify power and ground at suspect modules (backprobe): repair poor ground connections and wiring faults.
With ignition on, measure bus idle voltages on CAN_H and CAN_L at a junction using a voltmeter — compare to expected values. If abnormal, power down and measure termination resistances.
Use a diagnostic CAN/LIN interface or oscilloscope to capture comms while exercising affected systems. Look for missing frames, CRC errors, repeated retransmit flags, constant dominant states, or excessive error frames.
Isolate sections: disconnect modules or segments to see if the bus behavior changes (do this per OEM safe procedures). Replace/repair harness sections showing faults.
If wiring and terminations are good and faults persist localized to one module, consider software update/reflash of the module per OEM bulletin. If that fails, replace the suspected faulty control module and verify.
After repairs, clear codes and perform full test drive and network capture to confirm the retransmit condition no longer appears.

Likely causes

Corroded/loose connector at an affected module
Broken or chafed CAN/LIN wiring harness in a common routing area
Bad ground at body/control module chassis mounting point
Faulty module with internal communications fault
Aftermarket accessory injecting noise or loading the bus

Fault status

⚠️ Status

Stored when a module detects missing/failed message reception and requests retransmission on a vehicle communication bus. Indicates a communication integrity or wiring/connector/module issue rather than a specific component mechanical fault.

🟡 Repair difficulty: Medium

⏱️ Diagnostic time: 1.5-4 hours

Similar codes

Your experience will help others

+100 karma for a short comment :)

Was this AI description helpful?

Your feedback helps improve AI descriptions.

👍 Like 0 👎 Dislike 0

Send to email