Schematic Reference: Engine Controls Schematics
The Powertrain OBD system check is an organized approach to identifying a problem created by an electronic engine control system malfunction. The Powertrain OBD system check is the starting point for any driveability concern diagnosis, because it directs the service technician to the next logical step in diagnosing the concern. Understanding the table and using it correctly will reduce diagnostic time and prevent the replacement of good parts.
DO NOT perform this check if a driveability concern is not present.
Check for faulty electrical connections to the PCM.
An intermittent malfunction may be caused by a problem in any of the engine control electrical circuits. Inspect the PCM, the wiring harness, and the engine control components for any of the following conditions:
• | Backed out terminals. |
• | Improper mating of terminals. |
• | Broken electrical connector locks. |
• | Improperly formed or damaged terminals. |
• | Faulty terminal to wire connections. |
• | Physical damage to the wiring harness. |
• | A broken wire inside the insulation. |
• | Corrosion of electrical connections, splices, or terminals. |
The numbers below refer to the step numbers in the Diagnostic Table.
The Powertrain OBD system check should not be performed unless one of the concerns noted is present. Failure to follow this procedure could lead to misdiagnosis of the system.
The MIL should be on steady with the key on and the engine off.
This step checks whether the PCM and the scan tool can communicate (serial data).
This step checks whether the vehicle will start.
Before proceeding to the applicable DTC table consider all of the items below.
• | Check for related service bulletins. |
• | If multiple DTCs are stored, refer to the DTC tables using the following priority: |
1. | PCM error DTCs (P0601, P0603) |
2. | System voltage DTCs |
3. | Component level DTCs (sensors, switches, relays, output drivers, etc.) |
4. | System level DTCs (Misfire, Fuel trim, HO2S lean or rich, etc.) |
• | First failures of Type B DTCs will store in Last Test Failed, but not in History. When the MIL is on and a DTC is displayed in History, a current fault is indicated. |
• | Transmission DTCs are not located in this section. Refer to Automatic Transmission Diagnostic Information and Procedures. |
• | If the scan tool is unable to record DTC information, then record the DTC information on paper. |
This step detects a MIL circuit that may be shorted to ground.
Before proceeding to Symptoms or Components, check for related service bulletins. The diagnostic tables in this section are designed for use with a properly functioning scan tool. If a faulty scan tool is suspected connect it to another vehicle to verify operation. Serial data communications must be corrected before beginning any other diagnostic procedure. OBD II serial data may not transmit if system voltage is below 9.0 volts or above 16.0 volts. DO NOT clear the DTCs unless directed by a diagnostic procedure. Clearing the DTCs will also clear valuable Freeze Frame/Failure Record data.
Step | Action | Value(s) | Yes | No | ||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
Important:
Check for one or more of the following conditions:
Did any of the above conditions apply? | -- | System OK-Go to Test Descriptions | ||||||||||||||
Is the MIL illuminated? | -- | |||||||||||||||
Does the scan tool display any PCM data? | -- | |||||||||||||||
Start the engine. Did the engine start and run? | -- | |||||||||||||||
Were any DTCs set? | -- | Go to applicable DTC table | ||||||||||||||
Is the MIL ON with no DTCs set? | -- | |||||||||||||||
Compare the scan tool data display with the data values shown in the Engine Scan Tool Data List. Are the displayed values normal or within the typical values range? | -- | Go to Symptoms | Go to the Diagnostic Aids of the DTCs related to that component |