Code
B1548
MITSUBISHI
B — Body
CAN No communication
Views:
UK: 9
EN: 11
RU: 8
AI status
Completed
Completed
100%
Causes
- Open or shorted CAN bus wiring (CAN High or CAN Low)
- Failed or powered-down control module on the bus
- Missing or failed termination resistor(s) on the CAN bus
- Blown fuse or loss of power/ground to one or more modules
- Corroded or loose connectors, broken pins at modules or junctions
- Aftermarket electronic device interfering with the bus (alarm, radio, tracker)
Symptoms
- One or more control modules not responding to scan tool (no communication)
- Multiple dashboard warning lamps illuminated or intermittent instrument cluster operation
- Loss of functions tied to affected modules (ABS, SRS lights, HVAC, gauges, immobilizer)
- Intermittent or permanent failure of networked systems
- Diagnostic trouble codes stored for multiple modules or U-codes indicating lost communication
What to check
- Use a capable scan tool to read stored DTCs from all modules and note any U-codes
- Visually inspect all CAN-related fuses and relays; confirm battery voltage and good chassis/engine ground
- Inspect wiring harnesses, connectors and junction blocks for corrosion, bent pins, breaks, or water intrusion near the instrument panel and BCM
- Measure CAN termination resistance between CAN High and CAN Low at a convenient connector (should be ~60 ohms with ignition off)
- Check for back-probed voltages on CAN High and CAN Low with ignition ON (see signal_params)
- Disconnect/remove any recently installed aftermarket devices connected to the vehicle network
Signal parameters
- CAN idle voltage (to battery ground): CAN High ≈ 2.5 V, CAN Low ≈ 2.5 V (both center at ~2.5V)
- Dominant/Active voltages during data: CAN High ≈ 3.5 V, CAN Low ≈ 1.5 V (voltage difference present)
- Termination resistance across CAN H and CAN L: approx. 60 ohms (two 120 Ω terminators in parallel)
- Short to battery/ground will show CAN lines pulled toward 12 V or 0 V respectively
- Bus activity: valid periodic CAN traffic visible on a scope or CAN monitor at expected bitrate (commonly 250 kb/s or 500 kb/s on vehicle networks)
Diagnostic algorithm
- Connect a diagnostic scan tool and record all modules’ DTCs and network status (note any U-codes).
- Verify battery voltage is stable (12.4–12.8 V) and check main power/ground circuits to suspected modules.
- Inspect and test CAN bus fuses and relays; replace any blown fuses and retest communication.
- Visually inspect connectors and harnesses along the CAN backbone (instrument panel, BCM, junction boxes). Repair any damaged wiring or corroded pins.
- Measure termination resistance across CAN H and CAN L at a known good connector; if not ≈60 Ω, locate missing/bad terminator or open circuit.
- With ignition ON, measure CAN High and CAN Low voltages at the affected module(s). Compare to expected idle voltages (~2.5 V).
- If voltages are abnormal, isolate the fault by disconnecting modules one at a time (start at ends of the bus) and observe when communications return to identify the offending segment or module.
- Use an oscilloscope or CAN bus analyzer to confirm packet traffic and to identify noise, stuck dominant states, or low amplitude signals.
- If a module is found to be unresponsive but wiring and bus integrity are good, follow manufacturer procedure for module reset or replacement; reprogram or reinitialize as required.
- After repair, clear DTCs, verify all modules respond, and perform a road test or network exercise to confirm stability.
Likely causes
- Blown CAN fuse or loss of ground to the affected module
- Damaged/shorted CAN High or CAN Low wiring near BCM or junction connectors
- Detached or corroded connector at the affected control module
- Failed instrument cluster/BCM preventing bus communications
- Incorrect aftermarket device wiring connected to CAN lines
Fault status
Status
No CAN communication detected by a control module. Networked modules may be unavailable until wiring, power/ground, or the faulty module is repaired.
Repair difficulty: Medium
Diagnostic time: 1-3 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
Code
B1548
Other
B — Body
Power Window Master Circuit Open
Views:
UK: 23
EN: 23
RU: 22
AI status
Completed
Completed
100%
Causes
- Open or shorted CAN bus wiring (CAN High or CAN Low)
- Failed or powered-down control module on the bus
- Missing or failed termination resistor(s) on the CAN bus
- Blown fuse or loss of power/ground to one or more modules
- Corroded or loose connectors, broken pins at modules or junctions
- Aftermarket electronic device interfering with the bus (alarm, radio, tracker)
Symptoms
- One or more control modules not responding to scan tool (no communication)
- Multiple dashboard warning lamps illuminated or intermittent instrument cluster operation
- Loss of functions tied to affected modules (ABS, SRS lights, HVAC, gauges, immobilizer)
- Intermittent or permanent failure of networked systems
- Diagnostic trouble codes stored for multiple modules or U-codes indicating lost communication
What to check
- Use a capable scan tool to read stored DTCs from all modules and note any U-codes
- Visually inspect all CAN-related fuses and relays; confirm battery voltage and good chassis/engine ground
- Inspect wiring harnesses, connectors and junction blocks for corrosion, bent pins, breaks, or water intrusion near the instrument panel and BCM
- Measure CAN termination resistance between CAN High and CAN Low at a convenient connector (should be ~60 ohms with ignition off)
- Check for back-probed voltages on CAN High and CAN Low with ignition ON (see signal_params)
- Disconnect/remove any recently installed aftermarket devices connected to the vehicle network
Signal parameters
- CAN idle voltage (to battery ground): CAN High ≈ 2.5 V, CAN Low ≈ 2.5 V (both center at ~2.5V)
- Dominant/Active voltages during data: CAN High ≈ 3.5 V, CAN Low ≈ 1.5 V (voltage difference present)
- Termination resistance across CAN H and CAN L: approx. 60 ohms (two 120 Ω terminators in parallel)
- Short to battery/ground will show CAN lines pulled toward 12 V or 0 V respectively
- Bus activity: valid periodic CAN traffic visible on a scope or CAN monitor at expected bitrate (commonly 250 kb/s or 500 kb/s on vehicle networks)
Diagnostic algorithm
- Connect a diagnostic scan tool and record all modules’ DTCs and network status (note any U-codes).
- Verify battery voltage is stable (12.4–12.8 V) and check main power/ground circuits to suspected modules.
- Inspect and test CAN bus fuses and relays; replace any blown fuses and retest communication.
- Visually inspect connectors and harnesses along the CAN backbone (instrument panel, BCM, junction boxes). Repair any damaged wiring or corroded pins.
- Measure termination resistance across CAN H and CAN L at a known good connector; if not ≈60 Ω, locate missing/bad terminator or open circuit.
- With ignition ON, measure CAN High and CAN Low voltages at the affected module(s). Compare to expected idle voltages (~2.5 V).
- If voltages are abnormal, isolate the fault by disconnecting modules one at a time (start at ends of the bus) and observe when communications return to identify the offending segment or module.
- Use an oscilloscope or CAN bus analyzer to confirm packet traffic and to identify noise, stuck dominant states, or low amplitude signals.
- If a module is found to be unresponsive but wiring and bus integrity are good, follow manufacturer procedure for module reset or replacement; reprogram or reinitialize as required.
- After repair, clear DTCs, verify all modules respond, and perform a road test or network exercise to confirm stability.
Likely causes
- Blown CAN fuse or loss of ground to the affected module
- Damaged/shorted CAN High or CAN Low wiring near BCM or junction connectors
- Detached or corroded connector at the affected control module
- Failed instrument cluster/BCM preventing bus communications
- Incorrect aftermarket device wiring connected to CAN lines
Fault status
Status
No CAN communication detected by a control module. Networked modules may be unavailable until wiring, power/ground, or the faulty module is repaired.
Repair difficulty: Medium
Diagnostic time: 1-3 hours
Similar codes
Workshop Manuals
Available brands with manuals
2
AUDI 11
6-speed manual gearbox 0B1, front-wheel drive — Workshop Manual (Edition 05.2014)
Workshop Manual199,00 UAH
Audi A3 (1997) – 1.6L 4-cylinder (2‑valve) Engine Mechanical Components Service Manual (AEH, AKL, APF) – Edition 07.2002
Workshop Manual199,00 UAH
AUDI A3 (2004) Workshop Manual — 2.0L FSI Turbo (4‑cyl, 4‑valve) Engine, Mechanics — Edition 03.2017
Workshop Manual199,00 UAH
Audi A3 2004 — Electrical System (Workshop Manual, Edition 02.2018)
Workshop Manual199,00 UAH
Audi A4 / A4 Cabriolet – 4.2 l V8 (5‑valve, timing chains) – Workshop Manual (Mechanics) – Edition 04.2007
Workshop Manual199,00 UAH
Audi A4 / A4 Cabriolet — Auxiliary Heater Workshop Manual (Edition 08.2004)
Workshop Manual199,00 UAH
Audi A4 / A4 Cabriolet (1.8T 4‑cyl turbo) — Motronic Injection & Ignition System Service Manual (Edition 01.2015)
Workshop Manual199,00 UAH
Audi A8 (2003) — Electrical System Workshop Manual (Edition 08.2014)
Workshop Manual199,00 UAH
Audi Q4 e-tron (Type F4) - Self-study Programme SSP 685
Workshop Manual199,00 UAH
Audi Q8 (2018) — Electrical System Workshop Manual (Edition 05.2019)
Workshop Manual199,00 UAH
Audi Servicing Manual — 7‑Speed Dual Clutch Transmission 0CJ / 0CL / 0CK / 0DN / 0DP / 0HL (Edition 05.2018)
Workshop Manual199,00 UAH
LAND ROVER 3
Land Rover Defender 300Tdi — Workshop Manual (1996 model year)
Workshop Manual199,00 UAH
Land Rover Defender Workshop Manual Supplement & Body Repair Manual (1999 & 2002 MY)
Workshop Manual199,00 UAH
Land Rover Range Rover — Electrical Library (LRL 0453ENG, 2002)
Workshop Manual199,00 UAH
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
