LEMON Manuals: Even more car manuals for everyone: 1960-2025
Home >> Ford >> 2020 >> Escape Titanium Plug-In Hybrid >> Repair and Diagnosis >> Engine Performance >> Engine Control Systems >> Electric Powertrain Control (2 Of 2) >> Diagnosis And Testing >> Electric Powertrain Control >> Pinpoint Tests >> Pinpoint Test Bf : Invalid Data Received
April 5, 2026: LEMON Manuals is launched! Read the announcement.

Pinpoint Test Bf : Invalid Data Received

  1. NOTE: The Inverter System Controller (ISC) is referred to as the SOBDMC (Secondary On-Board Diagnostic Control Module C) in the scan tool.

    Normal Operation and Fault Conditions 

    REFER to: Electric Powertrain Control - System Operation and Component Description .

    DTC Fault Trigger Conditions 

    DTC Description Fault Trigger Condition
    SOBDMC U0401:00 Invalid Data Received from ECM/PCM A: No Sub Type Information This DTC sets when invalid network data is received from the ECM.
    SOBDMC U0412:00 Invalid Data Received From Battery Energy Control Module "A": No Sub Type Information This DTC sets when invalid network data is received from the BECM.
    SOBDMC U0418:00 Invalid Data Received from Brake System Control Module "A": No Sub Type Information This DTC sets when invalid network data is received from the ABS module.
    SOBDMC U045A:56 Invalid Data Received From Parking Assist Control Module "A": Invalid/Incompatible Configuration This DTC sets when invalid network data is received from the PAM.
    SOBDMC U049C:00 Invalid Data Received From Battery Charger Control Module "A": No Sub Type Information This DTC sets when invalid network data is received from the PAM.
    SOBDMC U0515:82 Invalid Data Received From Remote Function Actuation Module: Alive/Sequence Counter Incorrect/Not Updated This DTC sets when invalid network data is received from the RFA module.
    SOBDMC U053B:00 Invalid Data Received From Image Processing Module A: No Sub Type Information This DTC sets when invalid network data is received from the IPMA.

    Possible Sources 

    • Communications network concern
    • Suspect Module

  2. BF1 CHECK FOR RECENT SERVICE ACTIONS FOR THE MODULE IN QUESTION

    • 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 in question and the Inverter System Controller (ISC). If recent service history is found:

      • Verify correct replacement module was installed, vehicle parts build list 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 vehicle with concern, 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  BF2
    No  The system is operating correctly at this time. The DTC may have been set due to high network traffic or an intermittent fault condition.
  3. BF2 CHECK FOR DIAGNOSTIC TROUBLE CODES (DTCS) FROM THE MODULE SENDING INVALID DATA

    • Ignition ON.

    • Using a diagnostic scan tool, carry out the self-test for the module in question sending the invalid data.

    Are any DTCs present from the module sending the invalid data? 

    Yes  DIAGNOSE the module sending the invalid data. REFER to the appropriate Service Information.
    No  DIAGNOSE the observable symptom.