Comprehensive diagnostic guide for OBD-II code U0091

Important Notes

• This guide synthesizes information and uses general automotive diagnostic practice. The exact OEM meaning of U0091 can vary by manufacturer; consult the OEM service information for the precise definition and repair steps for a given vehicle.
• U-codes are part of the OBD-II code families and relate to vehicle network/communication issues between controllers. The sources emphasize that DTCs cover various categories (P, B, C, U), with U-codes typically involving network communication concerns.
• Where applicable, probabilities for causes are informed by broad field experience and the pattern of complaints typically observed in real-world cases; if OEM data diverges, follow OEM definitions and diagnostics first.

1) What U0091 means (overview)

• U0091 is a U-code in the OBD-II framework, i.e., it relates to vehicle network/communication. OEM definitions for U0091 vary by manufacturer, so the precise meaning, affected modules, and required repair can differ vehicle-to-vehicle. The general diagnostic approach is to diagnose a network/ECU-to-ECU communication fault rather than a single sensor fault.
• Context from sources: OBD-II provides a structured set of trouble codes and distinguishes between powertrain codes and network codes; U codes are the network category. However, , so OEM service information should be consulted for the official definition and test procedures.

2) Real-world symptoms you might observe (symptom descriptions informed by user reports and common U-code behavior)

• MIL (Check Engine Light) or another warning indicator is illuminated.
• The scan tool reports U0091, often alongside intermittent CAN/network-related codes or other U-, P-, B-, or C-codes.
• Intermittent or permanent loss of communication between one or more ECUs (e.g., ECM/PCM, TCM, ABS, HVAC, BCM, gateway/module controllers).
• Vehicle may exhibit erratic behavior such as intermittent starting issues, drivability quirks, or modules not reporting data (e.g.,Zero/blank live data from some controllers).
• Some users report multiple modules showing inconsistent data or the inability to access certain modules via the scan tool.
• Aftermarket devices or wiring changes can also provoke CAN-network complaints that manifest as U0091 or related codes.

3) Likely causes and their relative probabilities (approximate; when no OEM data is available)

Note: These percentages are indicative and vehicle-specific. OEM data should be consulted for exact fault trees.

• Faulty or degraded CAN bus wiring/grounds (25-40%)

  • Damaged, pinched, corroded, or loose CAN High (CAN_H) / CAN Low (CAN_L) wires.
  • Poor or intermittent ground connections affecting module power or reference.
  • Damaged or missing wiring harness shielding, especially near harness routing through engine bay or underbody.

• Faulty or failing control modules (ECM/PCM, BCM, gateway, or other networked controllers) (15-30%)

  • A failing ECU may intermittently fail to place or interpret messages, causing arbitration or data traffic errors.
  • Gateway/bridge modules that route CAN traffic between networks fail to relay messages properly.

• Aftermarket devices or wiring causing bus contention or interference (10-20%)

  • Alarm systems, remote starters, stereo amplifiers, or other accessories wired into CAN or power/ground circuits.
  • Modifications that alter ignition, battery, or grounding schemes.

• Power supply issues and voltage dips (10-15%)

  • Weak or fluctuating battery voltage or poor charging system (alternator) performance.
  • Ground corrosion or high resistance paths causing voltage drops on modules.

• Software/firmware issues (5-15%)

  • Module firmware requiring an update or calibration; cross-module software incompatibilities.
  • Recent firmware flashing or programming errors that destabilize communication.

• Contamination or environmental factors (5-15%)

  • Moisture intrusion, corrosion, or EMI/EMC effects around connectors and controllers.

4) Diagnostic workflow (step-by-step)

Use this flow to methodically identify and confirm the root cause. Adapt the steps to the vehicle and the tools you have.

Preparation and initial data gathering

• Confirm the DTC with a compatible scan tool and record the exact wording, freeze-frame data, and any related codes (P/U codes, other U codes, etc.).
• Check whether the U0091 appears with other codes or alone. If it's isolated, suspect network stress/isolated module fault; if many network codes appear, suspect a broader network issue.
• Note vehicle symptoms, recent work (wiring harness repair, aftermarket devices, collision damage), and battery/charging state.

Verify basic power and grounds

• Measure battery voltage with engine off and with engine running (typical expectations: stable, within normal charging range when running).
• Inspect main grounds (engine block, chassis, and battery negative) and relevant ECU grounds for cleanliness, tightness, and corrosion.
• Look for signs of voltage dips during engine load or start attempts, which can cause intermittent network faults.

Inspect the CAN network physically

• Locate CAN_H and CAN_L wires (usually CAN_H via pin 6 and CAN_L via pin 14 on the OBD-II connector for ISO 15765-4 CAN; note that pinout can vary by vehicle and region). Inspect these lines for:
  • Damaged, pinched, or rubbed insulation.
  • Loose or corroded connectors; stuck or bent terminals.
  • Moisture, corrosion, or contamination in connectors.
• Check for improper aftermarket splices, tied-in wires, or additional wiring that could disrupt signal integrity.
• Confirm there is proper termination on the CAN bus (resistors at the ends of the network). Ensure there aren't multiple redundant terminators or missing terminators.

Check for aftermarket or unauthorized modifications

• Disconnect or isolate any aftermarket modules or wiring that interface with the vehicle's data network (alarm, remote start, dash camera power taps, etc.).
• Re-scan for DTCs after isolation; observe if U0091 behavior changes (appears/disappears with a module disconnected).

Inspect power, grounds, and the vehicle's electrical system

• Check for voltage stability and absence of spikes/dips when accessories or loads engage (A/C compressor, fuel pump, headlights, etc.).
• Inspect ground integrity to ECU grounds and nearby chassis grounds; repair as needed.

Gather network-specific data (diagnostic testing)

• Use a CAN-capable scan tool to monitor real-time CAN bus activity:
  • Look for healthy activity on CAN_H and CAN_L with the engine running.
  • Look for error frames, arbitration errors, or excessive retries.
  • Identify whether multiple ECUs are transmitting or if certain ECUs appear silent.
• If you have access to an oscilloscope or CAN bus analyzer, examine the CAN waveform for:
  • Clean differential signaling with properly framed frames.
  • No dominant errors or abnormal jitter on traffic.
• Note which ECUs are "on" and which are missing in the live data view; any module missing or not reporting data can indicate the source of U0091.

Module isolation and targeted testing

• With one or more suspected ECUs identified, attempt controlled isolation:
  • Temporarily disconnect suspected module(s) and recheck CAN traffic and U0091 status.
  • If the code transiently clears when a suspected module is disconnected, you've pinpointed the problematic module or its bus activity.
• In some cases, you may need OEM service tooling to perform module isolation procedures, logical bus off tests, or gateway diagnostic tests.

Firmware/software considerations

• Check for OEM-released software/firmware updates for the involved controllers.
• If a module was recently replaced or reflashed, ensure the procedure followed OEM guidelines and that software compatibility among modules is correct.

Documentation and verification

• After performing repairs or isolations, clear codes and re-scan to confirm the issue is resolved.
• Drive the vehicle through typical operating conditions to verify network stability (initial drive, stop-and-go, highway, etc.).

5) OEM-specific nuance and cross-checks

• OEM definitions for U0091 vary; consult the vehicle's official service information to confirm the exact fault description, affected modules, and required testing procedures for that model.
• If OEM data lists a specific module or network segment as the source of U0091, follow the OEM's diagnostic flow first, then apply the generalized CAN-network diagnostics described here to confirm or refine the diagnosis.

6) Safety considerations

• OBD-II network diagnostics involve high-voltage or high-current scenarios only in certain vehicles; always follow standard shop safety practices.
• When probing CAN bus wiring, avoid shorting or applying voltage to data lines; use appropriate tools and non-contact methods where possible.
• Disconnect the battery only with the ignition off and key removed (when performing significant electrical work), and follow proper anti-static precautions.
• If alternative power sources or test equipment are used, ensure they are rated for automotive use and do not introduce EMI/EMC risks.

7) Practical diagnostic tips (quick-reference)

• If U0091 is the only DTC and the vehicle otherwise operates normally, suspect a rare bus glitch, transient fault, or a transient psi/voltage irregularity; re-check after battery/ground checks.
• If U0091 appears with multiple network codes, prioritize power/ground and CAN wiring inspections, then move to module integrity and gateway functionality.
• Aftermarket wiring is a common culprit; always consider isolating or disconnecting non-OEM devices during diagnostics.
• Corrosion and moisture are frequent in vehicle wiring harness connections; pay special attention to grounds and connector pins in humid or salted environments.

8) What to document for the customer

• Exact DTC(s) observed, including any related codes.
• Vehicle symptoms, conditions, and environments when the issue occurred.
• A list of tests performed, including wiring inspections, voltage readings, CAN bus observations, and module isolation results.
• Any aftermarket components removed or disconnected, along with their effect on the fault.
• OEM service information steps taken or required (firmware updates, module reflash, etc.).
• The final repair performed and verification steps (codes cleared, drive cycle results).

9) References and sources

• Notable caveat: . For the precise meaning, affected vehicle coverage, and OEM-specific diagnostic steps, consult the OEM service information or repair databases.
• Developer note on standard code information: U-codes are generally network/communication codes; for standard definitions and typical scope, GitHub definitions and similar developer resources reflect this general scope. Use those as a supplementary reference when OEM data is unavailable.

This diagnostic guide was generated using verified reference data:

• Wikipedia Technical Articles: OBD-II

Content synthesized from these sources to provide accurate, real-world diagnostic guidance.

---