Code
U0147
Generic
U — Network/User
Lost Communication With Serial Data Gateway Module B
Views:
UK: 24
EN: 21
RU: 16
AI status
Completed
Completed
100%
Causes
- Power or ground fault to Gateway Module B
- Damaged or disconnected connector(s) at the gateway or along the data bus
- Faulty Gateway Module B (internal failure)
- Open, short, or high resistance in CAN/LIN/serial data wiring
- Missing or incorrect network termination resistor(s)
- Intermittent wiring fault (corrosion, chafing, broken wire)
Symptoms
- One or more control modules not present on scan tool or showing ‘no communication’
- Multiple unrelated warning lights or modules reporting errors
- Loss of features that require networked modules (e.g., instrument cluster info, infotainment, remote functions)
- Intermittent or permanent inoperative systems that route through the gateway
- Stored U0147 with or without other U-codes
What to check
- Read current and pending codes from ALL modules with a capable scan tool; note other network-related U-codes
- Verify vehicle battery voltage (12V nominal) and charge level during testing
- Inspect fuses and relays supplying Gateway Module B
- Visually inspect connectors and wiring to the gateway and along the main data bus for corrosion, damage, or disconnection
- Use a scan tool to confirm whether Gateway Module B is present and responding on the network
- Check for noise, high error counters, or bus-off states on CAN/LIN networks by viewing network data or error counters with a diagnostic tool
Signal parameters
- Battery voltage: 12.0–14.5 V during testing
- CAN bus idle: CANH ≈ 2.5 V, CANL ≈ 2.5 V (small difference ~0 V)
- CAN dominant state: CANH ≈ 3.5 V, CANL ≈ 1.5 V (differential ~2 V)
- Termination resistance: ~120 Ω across CANH–CANL measured at vehicle harness ends (approx. 60 Ω when measured from one end to center of split)
- LIN bus idle typically near battery or ground reference depending on vehicle (check manufacturer spec)
- Message rate: expected periodic gateway heartbeat frequency and presence of module-specific messages (use scan tool)
Diagnostic algorithm
- Retrieve and record all DTCs from all networked modules. Note time stamps and any related codes.
- Verify battery state of charge and charging system; ensure stable supply (12–14.5 V) during tests.
- Visually inspect connectors, seals, and wiring leading to Gateway Module B. Repair corrosion, bent pins, or loose terminals.
- Check fuses/relays for the gateway’s power feed; restore any blown fuses and re-test communications.
- Using a scan tool, verify if Gateway Module B appears on the network. If absent, check module power and ground circuits for continuity and correct voltage.
- With ignition on, measure CANH and CANL at the gateway connector and at other nodes. Look for correct idle voltages and expected differential when transmitting. If voltages are out of range, trace wiring for opens/shorts or damaged sections.
- Inspect termination resistors; isolate sections of the bus by disconnecting branches or modules to locate a short or faulty node causing bus errors.
- If bus physical layer and power are good but the gateway is unresponsive, attempt a module reset (clear codes and power-cycle). If supported, reflash/update the gateway software per manufacturer procedure.
- If reprogramming is unsuccessful and wiring/power/termination are confirmed good, consider replacing Gateway Module B. Verify repair by confirming normal network traffic and clearing codes.
- After repair, erase codes and perform a full network scan and functional check of systems routed through the gateway. Road-test as required to confirm durability.
Likely causes
- Blown fuse or poor power/ground to Gateway Module B
- Loose/disconnected connector at the gateway or a nearby module
- Open or short on the CAN/LIN bus (physical damage or corrosion)
- Faulty Gateway Module B hardware or failed internal processor
Fault status
Status
Loss of communication with Serial Data Gateway Module B: the diagnostic tool cannot receive expected serial network messages or the gateway is not forwarding data between vehicle networks.
Repair difficulty: Medium
Diagnostic time: 1.0-3.0 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 ManualAudi A3 (1997) – 1.6L 4-cylinder (2‑valve) Engine Mechanical Components Service Manual (AEH, AKL, APF) – Edition 07.2002
Workshop ManualAUDI A3 (2004) Workshop Manual — 2.0L FSI Turbo (4‑cyl, 4‑valve) Engine, Mechanics — Edition 03.2017
Workshop ManualAudi A3 2004 — Electrical System (Workshop Manual, Edition 02.2018)
Workshop ManualAudi A4 / A4 Cabriolet – 4.2 l V8 (5‑valve, timing chains) – Workshop Manual (Mechanics) – Edition 04.2007
Workshop ManualAudi A4 / A4 Cabriolet — Auxiliary Heater Workshop Manual (Edition 08.2004)
Workshop ManualAudi A4 / A4 Cabriolet (1.8T 4‑cyl turbo) — Motronic Injection & Ignition System Service Manual (Edition 01.2015)
Workshop ManualAudi A8 (2003) — Electrical System Workshop Manual (Edition 08.2014)
Workshop ManualAudi Q4 e-tron (Type F4) - Self-study Programme SSP 685
Workshop ManualAudi Q8 (2018) — Electrical System Workshop Manual (Edition 05.2019)
Workshop ManualAudi Servicing Manual — 7‑Speed Dual Clutch Transmission 0CJ / 0CL / 0CK / 0DN / 0DP / 0HL (Edition 05.2018)
Workshop ManualLAND ROVER 3
Land Rover Defender 300Tdi — Workshop Manual (1996 model year)
Workshop ManualLand Rover Defender Workshop Manual Supplement & Body Repair Manual (1999 & 2002 MY)
Workshop ManualLand Rover Range Rover — Electrical Library (LRL 0453ENG, 2002)
Workshop ManualYour 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
U0147
HYUNDAI
U — Network/User
Lost Communication With Gateway “B”
Views:
UK: 14
EN: 18
RU: 16
AI status
Completed
Completed
100%
Causes
- Power or ground fault to Gateway Module B
- Damaged or disconnected connector(s) at the gateway or along the data bus
- Faulty Gateway Module B (internal failure)
- Open, short, or high resistance in CAN/LIN/serial data wiring
- Missing or incorrect network termination resistor(s)
- Intermittent wiring fault (corrosion, chafing, broken wire)
Symptoms
- One or more control modules not present on scan tool or showing ‘no communication’
- Multiple unrelated warning lights or modules reporting errors
- Loss of features that require networked modules (e.g., instrument cluster info, infotainment, remote functions)
- Intermittent or permanent inoperative systems that route through the gateway
- Stored U0147 with or without other U-codes
What to check
- Read current and pending codes from ALL modules with a capable scan tool; note other network-related U-codes
- Verify vehicle battery voltage (12V nominal) and charge level during testing
- Inspect fuses and relays supplying Gateway Module B
- Visually inspect connectors and wiring to the gateway and along the main data bus for corrosion, damage, or disconnection
- Use a scan tool to confirm whether Gateway Module B is present and responding on the network
- Check for noise, high error counters, or bus-off states on CAN/LIN networks by viewing network data or error counters with a diagnostic tool
Signal parameters
- Battery voltage: 12.0–14.5 V during testing
- CAN bus idle: CANH ≈ 2.5 V, CANL ≈ 2.5 V (small difference ~0 V)
- CAN dominant state: CANH ≈ 3.5 V, CANL ≈ 1.5 V (differential ~2 V)
- Termination resistance: ~120 Ω across CANH–CANL measured at vehicle harness ends (approx. 60 Ω when measured from one end to center of split)
- LIN bus idle typically near battery or ground reference depending on vehicle (check manufacturer spec)
- Message rate: expected periodic gateway heartbeat frequency and presence of module-specific messages (use scan tool)
Diagnostic algorithm
- Retrieve and record all DTCs from all networked modules. Note time stamps and any related codes.
- Verify battery state of charge and charging system; ensure stable supply (12–14.5 V) during tests.
- Visually inspect connectors, seals, and wiring leading to Gateway Module B. Repair corrosion, bent pins, or loose terminals.
- Check fuses/relays for the gateway’s power feed; restore any blown fuses and re-test communications.
- Using a scan tool, verify if Gateway Module B appears on the network. If absent, check module power and ground circuits for continuity and correct voltage.
- With ignition on, measure CANH and CANL at the gateway connector and at other nodes. Look for correct idle voltages and expected differential when transmitting. If voltages are out of range, trace wiring for opens/shorts or damaged sections.
- Inspect termination resistors; isolate sections of the bus by disconnecting branches or modules to locate a short or faulty node causing bus errors.
- If bus physical layer and power are good but the gateway is unresponsive, attempt a module reset (clear codes and power-cycle). If supported, reflash/update the gateway software per manufacturer procedure.
- If reprogramming is unsuccessful and wiring/power/termination are confirmed good, consider replacing Gateway Module B. Verify repair by confirming normal network traffic and clearing codes.
- After repair, erase codes and perform a full network scan and functional check of systems routed through the gateway. Road-test as required to confirm durability.
Likely causes
- Blown fuse or poor power/ground to Gateway Module B
- Loose/disconnected connector at the gateway or a nearby module
- Open or short on the CAN/LIN bus (physical damage or corrosion)
- Faulty Gateway Module B hardware or failed internal processor
Fault status
Status
Loss of communication with Serial Data Gateway Module B: the diagnostic tool cannot receive expected serial network messages or the gateway is not forwarding data between vehicle networks.
Repair difficulty: Medium
Diagnostic time: 1.0-3.0 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
U0147
LAND ROVER
U — Network/User
Lost communication with gateway B
Views:
UK: 9
EN: 9
RU: 4
AI status
Completed
Completed
100%
Causes
- Power or ground fault to Gateway Module B
- Damaged or disconnected connector(s) at the gateway or along the data bus
- Faulty Gateway Module B (internal failure)
- Open, short, or high resistance in CAN/LIN/serial data wiring
- Missing or incorrect network termination resistor(s)
- Intermittent wiring fault (corrosion, chafing, broken wire)
Symptoms
- One or more control modules not present on scan tool or showing ‘no communication’
- Multiple unrelated warning lights or modules reporting errors
- Loss of features that require networked modules (e.g., instrument cluster info, infotainment, remote functions)
- Intermittent or permanent inoperative systems that route through the gateway
- Stored U0147 with or without other U-codes
What to check
- Read current and pending codes from ALL modules with a capable scan tool; note other network-related U-codes
- Verify vehicle battery voltage (12V nominal) and charge level during testing
- Inspect fuses and relays supplying Gateway Module B
- Visually inspect connectors and wiring to the gateway and along the main data bus for corrosion, damage, or disconnection
- Use a scan tool to confirm whether Gateway Module B is present and responding on the network
- Check for noise, high error counters, or bus-off states on CAN/LIN networks by viewing network data or error counters with a diagnostic tool
Signal parameters
- Battery voltage: 12.0–14.5 V during testing
- CAN bus idle: CANH ≈ 2.5 V, CANL ≈ 2.5 V (small difference ~0 V)
- CAN dominant state: CANH ≈ 3.5 V, CANL ≈ 1.5 V (differential ~2 V)
- Termination resistance: ~120 Ω across CANH–CANL measured at vehicle harness ends (approx. 60 Ω when measured from one end to center of split)
- LIN bus idle typically near battery or ground reference depending on vehicle (check manufacturer spec)
- Message rate: expected periodic gateway heartbeat frequency and presence of module-specific messages (use scan tool)
Diagnostic algorithm
- Retrieve and record all DTCs from all networked modules. Note time stamps and any related codes.
- Verify battery state of charge and charging system; ensure stable supply (12–14.5 V) during tests.
- Visually inspect connectors, seals, and wiring leading to Gateway Module B. Repair corrosion, bent pins, or loose terminals.
- Check fuses/relays for the gateway’s power feed; restore any blown fuses and re-test communications.
- Using a scan tool, verify if Gateway Module B appears on the network. If absent, check module power and ground circuits for continuity and correct voltage.
- With ignition on, measure CANH and CANL at the gateway connector and at other nodes. Look for correct idle voltages and expected differential when transmitting. If voltages are out of range, trace wiring for opens/shorts or damaged sections.
- Inspect termination resistors; isolate sections of the bus by disconnecting branches or modules to locate a short or faulty node causing bus errors.
- If bus physical layer and power are good but the gateway is unresponsive, attempt a module reset (clear codes and power-cycle). If supported, reflash/update the gateway software per manufacturer procedure.
- If reprogramming is unsuccessful and wiring/power/termination are confirmed good, consider replacing Gateway Module B. Verify repair by confirming normal network traffic and clearing codes.
- After repair, erase codes and perform a full network scan and functional check of systems routed through the gateway. Road-test as required to confirm durability.
Likely causes
- Blown fuse or poor power/ground to Gateway Module B
- Loose/disconnected connector at the gateway or a nearby module
- Open or short on the CAN/LIN bus (physical damage or corrosion)
- Faulty Gateway Module B hardware or failed internal processor
Fault status
Status
Loss of communication with Serial Data Gateway Module B: the diagnostic tool cannot receive expected serial network messages or the gateway is not forwarding data between vehicle networks.
Repair difficulty: Medium
Diagnostic time: 1.0-3.0 hours
Similar codes
Workshop Manuals
Repair manuals for LAND ROVER
3
Land Rover Defender 300Tdi — Workshop Manual (1996 model year)
Workshop ManualLand Rover Defender Workshop Manual Supplement & Body Repair Manual (1999 & 2002 MY)
Workshop ManualLand Rover Range Rover — Electrical Library (LRL 0453ENG, 2002)
Workshop ManualYour 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