LEMON Manuals: Even more car manuals for everyone: 1960-2025
Home >> Ford >> 2020 >> Escape Titanium Plug-In Hybrid >> Repair and Diagnosis >> Brakes >> Brakes Control Systems >> Abs Guided Routine >> Pinpoint Tests >> Pinpoint Tests AW: SASM Communication Concern With PCM >> Possible Causes
April 5, 2026: LEMON Manuals is launched! Read the announcement.

Possible Causes

  1. AW1: CHECK THE COMMUNICATION NETWORK 
    • Ignition ON, engine OFF.
    • Press the Read Vehicle Information button to view the results of the modules communicating on the network.
    • Retrieve the continuous memory DTCs.
    • Does the PCM pass the network test? 
      Yes No
      RETRIEVE and RECORD all PCM DTCs. REFER to the Electronic Engine Controls article. If there are no DTCs in the PCM, Go to  AW3. Go to  AW2.
  2. AW2: CHECK THE GWM COMMUNICATION 
    • Ignition ON, engine OFF.
    • Press the Read Vehicle Information button to view the results of the modules communicating on the network.
    • Retrieve the continuous memory DTCs.
    • Does the GWM pass the network test? 
      Yes No
      DIAGNOSE the PCM does not communicate with the diagnostic scan tool. REFER to the Module Communications Network article. DIAGNOSE the GWM does not communicate with the diagnostic scan tool. REFER to the Module Communications Network article.
  3. AW3: RECHECK THE SASM DTCS 
    • Clear the SASM DTCs.
    • Ignition OFF.
    • Ignition ON, engine OFF.

      Carry out the SASM self-test.

    • Are any of the DTCs listed in the Fault Trigger Conditions Table retrieved again? 
      Yes No
      Go to  AW4. The system is operating correctly at this time. The DTC may have been set due to high network traffic or an intermittent fault condition.
  4. AW4: REVIEW THE SASM SELF-TEST FOR VOLTAGE-REALTED DTCS 
    • Review the results from the SASM self-test.
    • Is DTC U3003:1C or U3003:17 present? 
      Yes No
      For DTC U3003:1C, GO to PINPOINT TEST BD .
      For DTC U3003:17, GO to PINPOINT TEST BE .
      For all others, No fault found.      		 Go to  AW5.
  5. AW5: CHECK FOR GWM DTCS 

    Carry out the GWM self-test.

    • Are any DTCs present? 
      Yes No
      DIAGNOSE the GWM DTC. REFER to the Module Communications Network article. Go to  AW6.
  6. AW6: CHECK FOR PCM DTCS 

    Carry out the PCM KOEO self-test.

    • Are any DTCs present? 
      Yes No
      DIAGNOSE the PCM DTC. REFER to the Electronic Engine Controls article. Go to  AW7.
  7. AW7: 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 PCM or SASM. If recent service history is found:
      • Verify the correct replacement module was installed. HVBOM may be used to verify correct part fitment.
      • Verify the configuration of replacement module was correct. Re-configure the 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 No
      Go to  AW8. The system is operating correctly at this time. The concern may have been due to incorrect parts replacement procedures or incorrect module configuration.
  8. AW8: CHECK FOR COMMUNICATION DTCS IN OTHER MODULES 
    • Ignition ON, engine OFF.
    • Retrieve the continuous memory DTCs.
    • Is DTC U0100:xx set in 1 or more modules in addition to the SASM? 
      Yes No
      Go to  AW9. Go to  AW10.
  9. AW9: VERIFY PCM OPERATION 
    • Ignition OFF.
  10. AW10: VERIFY SASM OPERATION 
    • Ignition OFF.
    • SASM connector disconnected.
    • GWM connector disconnected. (C2431)
scientia non olet · About LEMON Manuals