U1635 – CAN Communication Bus Fault.

Generic selectors
Exact matches only
Search in title
Search in content
Post Type Selectors

The ODBII code U1635 indicates a fault in the CAN (Controller Area Network) communication bus, suggesting a communication issue between modules in the vehicle’s network.

The severity of ODBII code U1635 CAN Communication Bus Fault is moderate.

Common Causes For: U1634 U1634: “Vehicle Communication Bus Malfunction”

  • Faulty CAN bus wiring or connectors
  • Malfunctioning CAN bus modules
  • Short circuits in the CAN bus
  • Open circuits in the CAN bus
  • Interference from other electrical components
  • Poor ground connections
  • Faulty or damaged sensors on the CAN network
  • Software or firmware issues in the control modules

Common misdiagnosis for U1635 CAN Communication Bus Fault.

  • Faulty Engine Control Module (ECM)
  • Faulty Body Control Module (BCM)
  • Defective wiring or connectors
  • Faulty sensors
  • Battery or charging system issues
  • Faulty transmission control module (TCM)
  • Incorrectly programmed modules
  • Grounding issues

Common Troubleshooting Steps

The OBD-II code U1635 indicates a CAN (Controller Area Network) communication bus fault. This code typically suggests that there is a problem with the communication between various modules in the vehicle. Here are some common troubleshooting steps to diagnose and resolve the issue:

  • Check for Additional Codes: Use an OBD-II scanner to check for any other trouble codes that may be present. Other codes can provide additional context for the problem.
  • Inspect the Wiring and Connectors:
  • Visually inspect the wiring harnesses and connectors associated with the CAN bus. Look for signs of damage, corrosion, or loose connections.
  • Pay special attention to the connectors on the modules that are part of the CAN network.
  • Check the CAN Bus Termination Resistors:
  • Ensure that the CAN bus has the correct termination resistors (typically 120 ohms) at both ends of the bus. A missing or faulty resistor can cause communication issues.
  • Test the CAN Bus Voltage:
  • Use a multimeter to measure the voltage levels on the CAN High and CAN Low wires. The typical voltage levels should be around 2.5V when idle and should vary when data is being transmitted.
  • If the voltage levels are outside the expected range, there may be a fault in the bus.
  • Inspect Modules on the CAN Bus:
  • Identify all the modules connected to the CAN bus and check for any that may be malfunctioning. A faulty module can disrupt communication.
  • Disconnect each module one at a time and check if the code clears or if communication is restored.
  • Check for Short Circuits or Open Circuits:
  • Use a multimeter to check for shorts or opens in the CAN bus wiring. This includes checking for continuity between the CAN High and CAN Low wires and ground.
  • Scan for Module Communication:
  • Use a scan tool to check if you can communicate with all the modules on the CAN bus. If some modules are unresponsive, it may indicate a problem with those specific modules or their connections.
  • Inspect Ground Connections:
  • Ensure that all ground connections for the modules on the CAN bus are secure and free of corrosion. Poor ground connections can lead to communication issues.
  • Check for Interference:
  • Look for any sources of electrical interference that may be affecting the CAN bus communication, such as aftermarket accessories or modifications.
  • Update or Reprogram Modules:
  • In some cases, a software update or reprogramming of the affected modules may be necessary to resolve communication issues. 1
  • Consult Service Manual:
  • Refer to the vehicle’s service manual for specific diagnostic procedures and wiring diagrams related to the CAN bus system. 1
  • Professional Diagnosis:
  • If the issue persists after performing these steps, consider seeking help from a professional mechanic or automotive technician who has experience with CAN bus systems. By following these troubleshooting steps, you should be able to identify and resolve the underlying issue causing the U1635 code.

Leave a Comment

You must be logged in to post a comment.