LEMON Manuals: Even more car manuals for everyone
Home >> Ford >> 2022 >> Transit Connect Titanium, Gas/Ethanol >> Repair and Diagnosis >> External Pages >> Different car >> Section 346 (Four-Wheel Drive Systems (2 Of 2)) >> Diagnosis And Testing >> Four-Wheel Drive Systems - Raptor, Vehicles With: 4HI-LOC Torque on Demand Transfer Case >> Pinpoint Tests >> Pinpoint Test L : Missing Or Invalid Data Received From Another Module

Pinpoint Test L : Missing Or Invalid Data Received From Another Module

WARNING: This page is about a different car, the 2020 Ford F-150. However, it is still accessible from the selected car via links, so may be relevant.
  1. 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 and ATCM expect to receive network data from other modules on HS-CAN2. The TCCM and ATCM 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
    ATCM U0422:00 Invalid Data Received From Body Control Module: No Sub Type Information The ATCM received an invalid backlight illumination level from the BCM. Backlight illumination will be level 12 (Day Mode) when this DTC is present.
    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. Mode changes to or from 4L may be prevented when this DTC is present.
    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

  2. L1 ATTEMPT TO DUPLICATE THE DTC (DIAGNOSTIC TROUBLE CODE)

    • Enter the following diagnostic mode: Clear and Retest the TCCM or ATCMCM DTC self-test.

    • Road test the vehicle.

    • Enter the following diagnostic mode: TCCM or ATCMCM DTC self-test.

    Did the invalid data DTC set again? 

    Yes  GO to  L2
    No  The system is operating correctly at this time. The concern may have been caused by a high network traffic event.
  3. L2 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 or ATCM 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. 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 U0422, Refer to BCM Guided Routine . For U0418, Refer to ABS GUIDED ROUTINE .
    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.