Code
U0591
Generic
U — Network/User
Invalid Data Received From Vehicle Control Module
Views:
UK: 0
EN: 3
RU: 1
AI status
Completed
Completed
100%
Causes
- Faulty or intermittent wiring/connectors on the vehicle communication bus
- Poor or missing power or ground to one or more control modules
- Failed or marginal CAN/LIN transceiver inside a control module
- Incorrect or incompatible module software/calibration (recent reflash or replacement)
- Network termination fault or high bus impedance (open/shorted termination resistors)
- Electromagnetic interference or aftermarket device causing bus corruption
Symptoms
- Malfunction Indicator Lamp (MIL) or multiple warning lamps illuminated
- Loss or intermittent loss of function for the affected system(s)
- Modules reporting communication errors or 'bus off' conditions
- Stored communication DTCs in other modules (U0100 series, U0140, etc.)
- Erratic behavior of vehicle functions controlled over the bus
- No start or reduced drivability if critical module communication is lost
What to check
- Use a scan tool to read all U-codes and related module codes and view freeze frame data
- Note when the code sets (after key cycles, driving, during certain events)
- Visually inspect connectors, pins and wiring for damage, corrosion, or loose terminals
- Verify battery voltage and charging system health (stable 12–14.5 V during checks)
- Check module power and ground circuits for proper voltage/continuity
- Measure CAN/LIN bus voltages at several module connectors with key ON
Signal parameters
- CAN bus idle voltages: CANH ≈ 2.5–3.5 V, CANL ≈ 1.5–2.5 V (vehicle-specific)
- Dominant/recessive differential voltage around 2 V during active bits (depend on protocol)
- Typical CAN bit rates: 125 kbps, 250 kbps, 500 kbps (verify vehicle-specific rate)
- Normal bus termination: ~60 ohms between CANH and CANL (two 120Ω resistors in parallel)
- LIN is typically single-wire serial with ~0–12 V signals referenced to ground (vehicle-specific)
- Look for intermittent voltage spikes, missing recessive level, or stuck-dominant condition
Diagnostic algorithm
- Record all DTCs and freeze frame data from all control modules. Note related U-codes or B/C/P codes.
- Attempt to clear codes and re-run the failing conditions to verify reproducibility.
- Inspect physical wiring and connectors at the suspected source module(s) and at multiple points along the bus. Repair any damage found.
- Verify battery voltage and check grounds for proper continuity and tightness. Repair poor power/ground connections.
- With key ON, measure CANH/CANL voltages at several module connectors. Confirm idle voltages and termination resistance (~60 Ω).
- Use an oscilloscope to examine waveform quality on CAN lines while exercising communications to detect noise, reflections, or missing frames.
- If a specific source module is identified, unplug that module and see if the code changes or other modules report new communication errors (helps isolate the faulty unit).
- Check software/calibration levels for involved modules. If a recent reflash or module replacement occurred, verify correct programming and VIN alignment.
- Remove or disable any aftermarket electronics that interface with vehicle networks and retest.
- If physical layer and software are correct but invalid data persists, consider replacing the suspected faulty module per manufacturer guidance and reprogramming as required.
- After repairs, clear codes, verify communication stability, and perform a test drive to confirm the issue is resolved.
Likely causes
- Loose/damaged connector at the module that sent the invalid data
- Damaged wiring harness or chafed conductor on CAN high/low
- Poor ground at chassis or module ground point causing noisy signals
- Software mismatch after module replacement or partial reprogram
- Failed CAN transceiver in either the sending or receiving module
- Intermittent fault caused by vibration or corroded terminal
Fault status
Status
One control module reports receiving invalid or corrupted data from another module on the vehicle communication network. Communication/data integrity problem detected — further diagnosis of wiring, module transceivers, and software is required.
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 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
