U1690 – Module Communication Failure

The ODBII code U1690 indicates a “Module Communication Failure,” meaning there is a problem with communication between the vehicle’s control modules, which may affect their ability to share data or function properly.

The severity of ODBII code U1690 is generally considered moderate.

Common Causes For: U1689 Invalid Data Received from Vehicle Control Module.

• Faulty wiring or connectors
• Failed or malfunctioning control module
• Poor ground connections
• Corroded or damaged pins in connectors
• Communication network issues (e.g., CAN bus problems)
• Software or firmware issues in modules
• Intermittent electrical connections
• Low battery voltage or power supply issues

Common misdiagnosis for U1690 U1690: “Module Communication Failure”

• Faulty wiring or connectors
• Defective control module
• Software issues or updates needed
• Battery or power supply problems
• Grounding issues
• Intermittent communication issues
• Other unrelated sensor failures

Common Troubleshooting Steps

The OBD-II code U1690 indicates a “Module Communication Failure,” which typically means that there is a problem with communication between the vehicle’s control modules. Here are some common troubleshooting steps to diagnose and resolve this issue:

• Check for Other Codes: Start by scanning the vehicle for any other diagnostic trouble codes (DTCs). Other codes may provide additional context or indicate which module is having communication issues.
• Inspect Wiring and Connectors:
• Check the wiring harnesses and connectors associated with the affected modules. Look for signs of damage, corrosion, or loose connections.
• Pay special attention to ground connections, as poor grounding can lead to communication failures.
• Verify Power Supply: Ensure that the affected modules are receiving the proper voltage and ground. Use a multimeter to check the power supply to the modules.
• Check for Module Faults:
• If a specific module is indicated in conjunction with the U1690 code, consider testing or replacing that module.
• If multiple modules are affected, the issue may be more systemic.
• Inspect the CAN Bus:
• The Controller Area Network (CAN) bus is responsible for communication between modules. Check for shorts, opens, or other issues in the CAN bus wiring.
• Use an oscilloscope to monitor the CAN bus signals if you have access to one.
• Look for Software Issues:
• Ensure that all modules have the latest software updates. Sometimes, communication issues can be resolved with a software update.
• If a module has been recently replaced, ensure it has been properly configured and programmed.
• Perform a Hard Reset: Disconnect the vehicle’s battery for a few minutes to reset the modules. Reconnect the battery and see if the code reappears.
• Check for Interference: Sometimes, aftermarket accessories or modifications can interfere with module communication. If any modifications have been made, consider removing them temporarily to see if the issue resolves.
• Consult Technical Service Bulletins (TSBs): Check for any TSBs related to the U1690 code for your specific vehicle make and model. Manufacturers may have specific recommendations or known issues.
• Professional Diagnosis: If the issue persists after performing the above steps, it may be necessary to consult a professional technician or dealership for further diagnosis. They may have specialized tools and knowledge to pinpoint the problem. By following these steps, you should be able to identify and resolve the underlying issue causing the U1690 code.