LEMON Manuals: Even more car manuals for everyone: 1960-2025
Home >> Ford >> 2000 >> ZX2 Automatic >> Repair and Diagnosis >> External Pages >> Different car >> Section 1639 (Module Communications Network) >> Diagnosis And Testing >> Communications Network >> Inspection and Verification
April 5, 2026: LEMON Manuals is launched! Read the announcement.

Inspection and Verification

WARNING: This page is about a different car, the 2011 Mercury Milan, 2011 Lincoln MKZ, and 2011 Ford Fusion. However, it is still accessible from the selected car via links, so may be relevant.
  1. Verify the customer concern.
  2. Visually inspect for obvious signs of electrical damage.
    • If an obvious cause for an observed or reported concern is found, correct the cause (if possible) before proceeding to the next step.
    VISUAL INSPECTION

    Electrical
    • BJB fuse(s):
      • 12 (30A) (no communication with the DCSM)
      • 16 (5A) (no communication with the TCM (3.5L only))
      • 17 (10A) (no communication with the BECM (hybrid only))
      • 19 (25A) (no communication with audio Digital Signal Processing (DSP) module
      • 20 (20A) (no communication with the audio DSP module)
      • 21 (20A) (no communication with the audio DSP module)
      • 23 (10A) (no communication with the PCM, TCM (hybrid only))
      • 32 (30A) (no communication with the DSM)
      • 39 (10A) (no communication with the TCM (hybrid only))
      • 40 (10A) (no communication with the PCM (hybrid only))
      • 42 (10A) (no communication with the ABS module (gasoline engine only))
      • 44 (10A) (no communication with the TCM (3.5L only))
      • 46 (15A) (no communication with the PCM (gasoline engine only))
      • 47 (10A) (no communication with the ABS module (hybrid only), ACCM (hybrid only), DC/DC (hybrid only))
      • 48 (20A) (no communication with the BECM (hybrid only))
    • SJB fuse(s):
      • 5 (10A) (no communication with the SJB)
      • 11 (10A) (no communication with the 4X4 control module)
      • 12 (7.5A) (no communication with the DDM)
      • 13 (5A) (no communication with the APIM)
      • 14 (10A) (no communication with the FCIM, FDIM, ILCM, GPSM)
      • 15 (10A) (no communication with the HVAC module)
      • 20 (15A) (no power to the scan tool)
      • 26 (15A) (no communication with the IPC)
      • 29 (5A) (no communication with the IPC)
      • 32 (10A) (no communication with the RCM)
      • 35 (10A) (no communication with the 4X4 control module, PAM, SOD-L, SOD-R)
      • 39 (20A) (no communication with the ACM)
      • 42 (10A) (no communication with the HCM, PSCM)
      • 46 (7.5A) (no communication with the OCSM)
    • DLC
    • Wiring harness
    • Wiring, terminals or connectors
  3. Connect the scan tool to the Data Link Connector (DLC).
      NOTE: Make sure to use the latest scan tool software release.
      NOTE: The Vehicle Communication Module (VCM) LED prove-out confirms power and ground from the DLC are provided to the VCM.
    • If the Integrated Diagnostic System (IDS) does not communicate with the VCM:
      • Check the VCM connection to the vehicle.
      • Check the scan tool connection to the VCM.
      • GO to PINPOINT TEST AF , to diagnose No Power To The Scan Tool.
  4. Establish a scan tool session.
      NOTE: The scan tool will first attempt to communicate with the PCM, after establishing communication with the PCM, the scan tool will then attempt to communicate with all other modules on the vehicle.
    • If an IDS session cannot be established with the vehicle, (IDS may state "No communication can be established with the PCM"):
      • Choose "NO" when the scan tool prompts whether or not to retry communication.
      • Enter either a PCM part number, tear tag or calibration number to identify the vehicle and start a session (the PCM part number and 4-character tear tag are printed on the PCM label).
      • GO to PINPOINT TEST A , to diagnose The PCM Does Not Respond To The Scan Tool.
  5. Carry out the network test.
    • If the network test passes, retrieve and record the continuous memory DTCs and proceed to Step  6.
    • If the network test fails, GO to SYMPTOM TABLE  to diagnose the failed communication network.
    • If a module fails to communicate during the network test, GO to SYMPTOM TABLE .
  6. Retrieve and review the DTCs.
    • If the DTCs retrieved are related to the concern, go to DTC TABLES . Follow the non-network DTC diagnostics (B-codes, C-codes, P-codes) prior to the network DTC diagnostics (U-codes). For all other DTCs, refer to the Diagnostic Trouble Code (DTC) Table in MULTIFUNCTION ELECTRONIC MODULES -- FUSION, MILAN & MKZ article.
    • If no DTCs related to the concern are retrieved, GO to SYMPTOM TABLE .
scientia non olet · About LEMON Manuals