Pinpoint Test G: Invalid Data Received From Another Module
- Normal Operation and Fault Conditions
The AWD module expects to receive network data from other modules on HS-CAN1. The AWD will set a DTC when it receives an invalid or incomplete messages from another module. Incomplete or corrupted messages typically result from high network traffic preventing the complete message from being received within the calibrated time limit.
DTC Fault Trigger Conditions
DTC Description Fault Trigger Condition AWD U0415:00 Invalid Data Received from Anti-Lock Brake System (ABS) Control Module 'A': No Sub Type Information This DTC sets when the AWD module received a message from the suspect module, but the message was not complete. AWD U0422:00 Invalid Data Received From Body Control Module: No Sub Type Information This DTC sets when the AWD module received a message from the suspect module, but the message was not complete. AWD U0423:00 Invalid Data Received from Instrument Panel Cluster Control Module: No Sub Type Information This DTC sets when the AWD module received a message from the suspect module, but the message was not complete. AWD U0428:00 Invalid Data Received From Steering Angle Sensor Module: No Sub Type Information This DTC sets when the AWD module received a message from the suspect module, but the message was not complete. AWD U1011:00 Invalid Internal Control Module Monitoring Data Received from ECM/PCM: No Sub Type Information This DTC sets when the AWD module received a message from the suspect module, but the message was not complete. AWD U1012:00 Invalid Internal Control Module Monitoring Data Received from Anti-Lock Brake System (ABS) Control Module: No Sub Type Information This DTC sets when the AWD module received a message from the suspect module, but the message was not complete. AWD U1014:00 Invalid Internal Control Module Monitoring Data Received from Restraints Control Module: No Sub Type Information This DTC sets when the AWD module received a message from the suspect module, but the message was not complete. Possible Sources
- High network traffic event
- Intermittent network connection
- Suspect module
- G1 ATTEMPT TO DUPLICATE THE DTC (DIAGNOSTIC TROUBLE CODE)
- Enter the following diagnostic mode: Clear and Retest the AWDCMDTC self-test.
- Road test the vehicle.
- Enter the following diagnostic mode: AWD module CMDTC self-test.
Did the invalid data DTC set again?
Yes GO to G2 No The system is operating correctly at this time. The concern may have been caused by a high network traffic event. - G2 INSPECT FD-CAN (FLEXIBLE DATA RATE CONTROLLER AREA NETWORK) CONNECTORS
- Refer to MODULE COMMUNICATION NETWORK for schematic and connector information. DISCONNECT and INSPECT the FD-CAN connectors between the AWD and the suspect module.
- Repair:
- corrosion (install new connector or terminals - clean module pins).
- damaged or bent pins - install new terminals/pins.
- pushed-out pins - install new pins as necessary.
- Connect all connectors. Make sure each connector seats and latches correctly.
- Operate the system and verify the concern is still present.
Is the concern still present?
Yes CHECK OASIS for any applicable TSB, GSB, SSM, or FSA. If a service article exists for this concern, DISCONTINUE this test and FOLLOW the service article instructions. If no service articles address this concern, DIAGNOSE the suspect module. No The system is operating correctly at this time. The concern may have been caused by module connections. ADDRESS the root cause of any connector or pin issues.