Pinpoint Test H : Invalid Data Received From Another Module
WARNING: This page is about a different variant/trim than selected.
- Refer to Module Communications Network
for schematic and connector information.
Normal Operation and Fault Conditions
The TCCM expects to receive network data from other modules on HS-CAN2. The TCCM will set a DTC when it receives invalid or incomplete messages from a module. A suspect module may send an invalid messages is there is a fault with one or more input sensors. 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 TCCM U0418:00 Invalid Data Received from Brake System Control Module "A": No Sub Type Information The TCCM received invalid wheel speed or brake switch data from the ABS module. TCCM U0439:00 Invalid Data Received From All Terrain Control Module: No Sub Type Information The TCCM received invalid drive mode data from the ATCM. Possible Sources
- Suspect module fault
- High network traffic event
- Intermittent network connection
- H1 CHECK SUSPECT MODULE FOR DTC (DIAGNOSTIC TROUBLE CODE)
- Enter the following diagnostic mode: On Demand and CMDTC self-test for the suspect module.
Are any DTC set in the suspect module?
Yes DIAGNOSE and REPAIR all DTC in the suspect module. No GO to H2 - H2 ATTEMPT TO DUPLICATE THE DTC (DIAGNOSTIC TROUBLE CODE)
- Enter the following diagnostic mode: Clear and Retest the TCCM CMDTC self-test.
- Road test the vehicle.
- Enter the following diagnostic mode: TCCM CMDTC self-test.
Did the invalid data DTC set again?
Yes GO to H3 No The system is operating correctly at this time. The concern may have been caused by a high network traffic event. - H3 INSPECT HS-CAN2 (HIGH-SPEED CONTROLLER AREA NETWORK 2) CONNECTORS
- Refer to Module Communications Network for schematic and connector information.
- DISCONNECT and INSPECT the HS-CAN2 connectors between the TCCM and the suspect module.
- Check for the following:
- corrosion (install new connector or terminals - clean module pins)
- damaged or bent pins - install new terminals/pins
- pushed-out pins - fully seat pin, install new pins or connector as necessary
- CONNECT all connectors. Make sure each connector seats and latches correctly.
- Operate the system and verify if the concern is still present.
Is the concern still present?
Yes CHECK OASIS for any applicable TSB. If a TSB exists for this concern, DISCONTINUE this test and FOLLOW TSB instructions. If no TSB address this concern, INSTALL a new suspect module. For U0121, ABS GUIDED ROUTINE 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.