Pinpoint Test H : Invalid Data Received From Another Module
- H1 CHECK SUSPECT MODULE FOR DTC (DIAGNOSTIC TROUBLE CODE)
- Enter the following diagnostic mode: On Demand and CMDTC self-test for the suspect module.
Did the invalid data DTC set again?
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 conectors 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, refer to ABS GUIDED ROUTINE TESTING .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.