LEMON Manuals: Even more car manuals for everyone
Home >> Ford >> 2018 >> Focus SEL, 4D Hatchback >> Repair and Diagnosis >> External Pages >> Different variant/trim >> Section 41 (Four-Wheel Drive Systems (Except Electric)) >> Diagnosis And Testing >> Four-Wheel Drive Systems >> Pinpoint Tests >> Pinpoint Test F : DTC (Diagnostic Trouble Code) U0140:87 >> Pinpoint Test F : DTC (Diagnostic Trouble Code) U0140:87

Pinpoint Test F : DTC (Diagnostic Trouble Code) U0140:87

WARNING: This page is about a different variant/trim than selected.

  1. F1 VERIFY THE SCAN TOOL COMMUNICATES WITH THE BCM (BODY CONTROL MODULE)

    • Connect the diagnostic scan tool.

    • Check that a vehicle session can be established using the scan tool.

    Can a vehicle session be established? 

    Yes  GO to  F2
    No  DIAGNOSE the BCM does not respond to the diagnostic scan tool. REFER to: Communications Network .
  2. F2 CHECK THE AWD (ALL-WHEEL DRIVE) CONTINUOUS MEMORY DIAGNOSTIC TROUBLE CODES (CMDTCS)

    • Ignition ON.

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

    • Clear the DTCs.

    • Wait 10 seconds.

    • Repeat the AWD self-test.

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

    Yes  DIAGNOSE all non-network DTCs. REFER to DTC Chart: AWD Module .
    No  GO to  F3
  3. F3 PERFORM THE BCM (BODY CONTROL MODULE) SELF-TEST

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

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

    Yes  DIAGNOSE all non-network DTCs. REFER to: Body Control Module (BCM) .
    No  GO to  F4
  4. F4 RECHECK THE AWD (ALL-WHEEL DRIVE) DIAGNOSTIC TROUBLE CODES (DTCS)

    • Using a diagnostic scan tool, clear the AWD DTCs.

    • Ignition OFF.

    • Ignition ON.

    • Wait 10 seconds.

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

    • Check the AWD DTCs.

    Is DTC U0140:87 still present? 

    Yes  GO to  F5
    No  The system is operating correctly at this time. The DTC may have set due to high network traffic or an intermittent fault condition.
  5. F5 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 BCM or AWD. If recent service history is found:

      • verify correct replacement module was installed

        • HVBOM 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  F6
    No  The system is operating correctly at this time. The concern may have been due to incorrect parts replacement procedures or incorrect module configuration.
  6. F6 CHECK FOR CORRECT BCM (BODY CONTROL MODULE) OPERATION

    • Ignition OFF.

    • Disconnect and inspect the BCM and related in-line connectors.

    • 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 BCM and all related in-line connectors. Make sure they seat and latch correctly.

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

    Is the concern still present? 

    Yes  CHECK OASIS for any applicable Technical Service Bulletins (TSBs). If a TSB exists for this concern, DISCONTINUE this test and FOLLOW TSB instructions. If no Technical Service Bulletins (TSBs) address this concern, Refer to BCM 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.