Pinpoint Test N: Invalid Data Received From Another Module
WARNING: This page is about a different car, the 2023 Ford F-150 Lightning and 2023 Ford F-150. However, it is still accessible from the selected car via links, so may be relevant.
- Refer to TWO WHEEL DRIVE/FOUR WHEEL DRIVE SYSTEMS
for schematic and connector information. Refer to MODULE COMMUNICATIONS NETWORK
for schematic and connector information.
Normal Operation and Fault Conditions
The TCCM expect to receive network data from other modules on FD- CAN. The TCCM will set a DTC when it receives an invalid or incomplete message 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 TCCM U0418:00 Invalid Data Received from Brake System Control Module 'A': No Sub Type Information The TCCM received an invalid wheel speed message data from the ABS. TCCM U0418:82 Invalid Data Received from Brake System Control Module 'A': Alive/Sequence Counter Incorrect/Not Updated The TCCM received an invalid wheel speed message data from the ABS. TCCM U0439:00 Invalid Data Received From All Terrain Control Module: No Sub Type Information The TCCM received an invalid mode selection message data from the ATCM. Mode changes may be prevented when this DTC is present. Possible Sources
- High network traffic event
- Intermittent network connection
- Suspect module
- N1 CHECK SUSPECT MODULE FOR DTC
- Enter the following diagnostic mode: On Demand and CMDTC self-test for the suspect module.
- Road test the vehicle.
Are any DTC set in the suspect module?
Yes DIAGNOSE and REPAIR all DTC in the suspect module. No GO to N2 - N2 ATTEMPT TO DUPLICATE THE DTC
- Enter the following diagnostic mode: Clear and Retest the TCCMCMDTC self-test.
- Road test the vehicle.
- Enter the following diagnostic mode: TCCMCMDTC self-test.
Did the invalid data DTC set again?
Yes GO to N3 No The system is operating correctly at this time. The concern may have been caused by a high network traffic event. - N3 INSPECT HS-CAN2 CONNECTORS
Refer to TWO WHEEL DRIVE/FOUR WHEEL DRIVE SYSTEMS for schematic and connector information.- DISCONNECT and INSPECT the FD -CAN 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 - install new pins 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. No The system is operating correctly at this time. The concern may have been caused by module or network connections. ADDRESS the root cause of any connector or pin issues.