LEMON Manuals: Even more car manuals for everyone
Home >> Lincoln >> 2022 >> Navigator Base, 4WD >> Repair and Diagnosis >> Electrical >> Gauges >> Instrumentation, Message Center And Warning Chimes (Diagnosis And Testing, General Procedures, Removal And Installation) >> Diagnosis And Testing >> Instrumentation, Message Center and Warning Chimes - Vehicles With: Head Up Display (HUD) >> Pinpoint Tests >> Pinpoint Test K: Lost Communication With A Module

Pinpoint Test K: Lost Communication With A Module

  1. Normal Operation and Fault Conditions 

    REFER to: Controller Area Network (CAN) Module Communications Network - System Operation and Component Description .

    DTC Fault Trigger Conditions 

    DTC Description Fault Trigger Condition
    HUD U0100:00 Lost Communication With ECM/PCM 'A': No Sub Type Information Sets in continuous memory in the HUD module if gearshift data messages received from the PCM through the GWM are missing for 5 seconds or longer.
    HUD U0140:00 Lost Communication With Body Control Module: No Sub Type Information Sets in continuous memory in the HUD module if ignition status data messages received from the BCM through the GWM are missing for 5 seconds or longer.
    HUD U0146:00 Lost Communication With Serial Data Gateway 'A': No Sub Type Information Sets in continuous memory in the HUD module if adaptive cruise control data messages received through the GWM over the HS-CAN3 are missing for 5 seconds or longer.
    HUD U0155:00 Lost Communication With Instrument Panel Cluster (IPC) Control Module: No Sub Type Information Sets in continuous memory in the HUD module if HUD adjustment data messages received from the IPC over the HS-CAN3 are missing for 5 seconds or longer.
    HUD U0212:00 Lost Communication With Steering Column Control Module: No Sub Type Information Sets in continuous memory in the HUD module if steering wheel switch data messages received from the SCCM through the GWM are missing for 5 seconds or longer.
    HUD U023A:00 Lost Communication With Image Processing Module A: No Sub Type Information Sets in continuous memory in the HUD module if front camera data messages (lane keep assist, traffic sign, adaptive cruise control, highway assist, forward collision warning) received from the IPMA through the GWM are missing for 5 seconds or longer.

    Possible Sources 

    • Communication concern
    • Battery voltage concern
    • CAN module fault determined by a lost communication DTC being set
    • GWM
    • HUD module

  2. K1 VERIFY THE CUSTOMER CONCERN

    • Ignition ON.

    • Verify there is an observable symptom present.

    Is an observable symptom present? 

    Yes  GO to  K2
    No  CLEAR the DTC. The system is operating normally at this time. The DTC may have been set due to high network traffic or an intermittent fault condition.

  3. K2 CHECK THE COMMUNICATION NETWORK

    • Using a diagnostic scan tool, perform the network test.

    Do all modules pass the network test? 

    Yes  GO to  K3
    No  REFER to: Controller Area Network (CAN) Module Communications Network .

  4. K3 CHECK THE HUD (HEAD UP DISPLAY) MODULE CONTINUOUS MEMORY DIAGNOSTIC TROUBLE CODES (CMDTCS)

    • Using a diagnostic scan tool, perform the HUD module self-test.

    • Clear the Diagnostic Trouble Codes (DTCs).

    • Wait 10 seconds.

    • Repeat the IPC self-test.

    Are any non-network Diagnostic Trouble Codes (DTCs) present? 

    Yes  DIAGNOSE all non-network Diagnostic Trouble Codes (DTCs). REFER to Diagnostic Trouble Code (DTC) Chart .
    No  GO to  K4

  5. K4 PERFORM THE SELF-TEST

    • Determine which lost communication Diagnostic Trouble Codes (DTCs) set during the HUD module self test.

    • Using a diagnostic scan tool, perform the self-test for the module(s) that set a lost communication fault in the HUD module.

    Are any non-network Diagnostic Trouble Codes (DTCs) present? 

    Yes  REFER to the applicable DTC Chart.
    No  GO to  K5

  6. K5 CHECK THE GWM (GATEWAY MODULE A) DIAGNOSTIC TROUBLE CODES (DTCS)

    • Using a diagnostic scan tool, check the GWM Continuous Memory Diagnostic Trouble Codes (CMDTCs).

    Are any Diagnostic Trouble Codes (DTCs) set? 

    Yes  REFER to: Controller Area Network (CAN) Module Communications Network .
    No  GO to  K6

  7. K6 RECHECK THE HUD (HEAD UP DISPLAY) MODULE DIAGNOSTIC TROUBLE CODES (DTCS)

    • Using a diagnostic scan tool, clear the HUD module Diagnostic Trouble Codes (DTCs).

    • Ignition OFF.

    • Ignition ON.

    • Wait 10 seconds.

    • Using a diagnostic scan tool, perform the continuous memory self-test.

    • Check the HUD module Diagnostic Trouble Codes (DTCs).

    Are any lost communication Diagnostic Trouble Codes (DTCs) still present? 

    Yes  GO to  K7
    No  The system is operating correctly at this time. The DTC may have set due to high network traffic or an intermittent fault condition.

  8. K7 CHECK FOR OTHER CAUSES OF COMMUNICATION NETWORK CONCERN

    NOTE: If new modules were installed prior to the DTC being set, the module configuration can be incorrectly set during the PMI or the PMI may not have been carried out.

    • CHECK the vehicle service history for recent service actions related to the module(s) in question, GWM or HUD module. If recent service history is found:

      • verify correct replacement module was installed

        • vehicle parts build may be used to verify correct part fitment

      • verify the configuration of replacement module was correct

        • re-configure module using as-built data if prior configuration is suspect

      • verify the module was not obtained from a like vehicle and installed into customer vehicle

        • return the swapped module to source vehicle and obtain new replacement module

    • Operate the system and determine if the observable symptom is still present.

    Is the observable symptom still present? 

    Yes  GO to  K8
    No  The system is operating correctly at this time. The concern may have been due to incorrect parts replacement procedures or incorrect module configuration.

  9. K8 CHECK FOR CORRECT OPERATION OF THE MODULE IN QUESTION

    • Ignition OFF.

    • Disconnect and inspect the module connector(s).

    • 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

    • Reconnect the module connector(s). Make sure they (it) seat(s) and latch(es) correctly.

    • Operate the system and determine if the concern is still present.

    Is the concern still present? 

    Yes  CHECK OASIS for any applicable service articles: 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, INSTALL a new module in question. REFER to the applicable removal and installation procedure.
    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.
scientia non olet · About LEMON Manuals