Menu +
Generic selectors
Exact matches only
Search in title
Search in content
Post Type Selectors

DTC P0087:00 [PCM (SKYACTIV-G)]

DTC P0087:00 [PCM (SKYACTIV-G)]

SM2334366


id0102t4008200

Note
• To determine the malfunctioning part, proceed with the diagnostics from “Function Inspection Using M-MDS”.



Details On DTCs

Description

Fuel pressure sensor circuit range/performance problem

Detection condition
Determination conditions
• If any of the following conditions is met under condition A or condition B:
Condition A:
― The actual fuel pressure is lower than the target fuel pressure by 1.2 MPa {12 kgf/cm2, 174 psi} or more even though the fuel pressure feedback amount is maintained high.
Condition B:
― The PCM detects that the actual fuel pressure is 1.7 MPa {17 kgf/cm2, 247 psi} or less continuously or intermittently.
Preconditions
• Engine speed: 500 rpm or more *1
• The following DTCs are not detected:
― Fuel pressure sensor: P0089:00, P0192:00 and P0193:00
― High pressure fuel pump: P0091:00 and P0092:00
*1: Standard can be verified by displaying PIDs using M-MDS
Malfunction determination period
Condition A:
5 s period
Condition B:
• Specified time
Drive cycle
• 1
Self test type
• CMDTC self test
Sensor used
• Fuel pressure sensor
Fail-safe function
• Limits intake air amount
• Stops high pressure fuel pump control
Vehicle status when DTCs are output
• Not applicable
Possible cause
• Air suction in fuel line due to fuel is runout
• High pressure fuel pump connector or terminals malfunction
• Fuel pressure sensor connector or terminals malfunction
• PCM connector or terminals malfunction
• Fuel pressure sensor malfunction
• Fuel delivery system malfunction (insufficient fuel pressure)
• Fuel injector malfunction
• High pressure fuel pump malfunction
― Relief valve (built-into high pressure fuel pump) malfunction
• PCM malfunction



System Wiring Diagram

• Not applicable



Function Explanation (DTC Detection Outline)

• The PCM calculates the target fuel pressure appropriate to the engine conditions relative to the actual fuel pressure based on the fuel pressure sensor signal and provides feedback to the high pressure fuel pump control. If the difference between the actual fuel pressure and the target fuel pressure relative to the feedback amount is large, the PCM determines a malfunction in the fuel pressure sensor and stores a DTC.



Repeatability Verification Procedure

1. Warm up the engine to allow the engine coolant temperature to reach 80 °C {176 °F} or more.
2. Start the engine and leave it idling for 1 min.

Note
• The target calculated by the PCM is increased and the DTC P0087:00 determination conditions are met by repeating the Step 3 operation.
3. Shift to 1st gear and accelerate/decelerate the vehicle to 30—50 km/h {19—31 mph}.

Note
• Match the engine coolant temperature in the recorded freeze frame data/snapshot data, the vehicle speed, and engine speed values to the best extent possible while driving the vehicle.
4. Try to reproduce the malfunction by driving the vehicle for 5 min based on the values in the freeze frame data/snapshot data.



PID Item/Simulation Item Used In Diagnosis

PID/DATA monitor item table

PIDs

Reference

FUEL_PRES

Simulation item table

Simulation items

Reference

FUEL_PUMP_REQ



Function Inspection Using M-MDS

Step

Inspection

Results

Action

1
PURPOSE: VERIFY RELATED REPAIR INFORMATION OR SERVICE INFORMATION AVAILABILITY
• Verify related Service Bulletins, on-line repair information, or Service Information availability.
• Is any related Information available?
Yes
Perform repair or diagnosis according to the available information.
• If the vehicle is not repaired, go to the next step.
No
Go to the next step.
2
PURPOSE: IDENTIFY TRIGGER DTC FOR FREEZE FRAME DATA
• Is the DTC P0087:00 on freeze frame data?
Yes
Go to the next step.
No
Go to the troubleshooting procedure for DTC on freeze frame data.
3
PURPOSE: RECORD VEHICLE STATUS WHEN DTC WAS DETECTED TO UTILIZE WITH REPEATABILITY VERIFICATION
• Record the freeze frame data/snapshot data.

Note
• Recording can be facilitated using the screen capture function of the PC.
Go to the next step.
4
PURPOSE: VERIFICATION IF MALFUNCTION CAUSED BY LACK OF FUEL
• Verify the snapshot data FLI. (See SNAPSHOT DATA TABLE [PCM (SKYACTIV-G)].)
• Is the snapshot data FLI 5% or less?
Yes
Refill the fuel.
Go to Troubleshooting Diagnostic Procedure to perform the repair completion verification.
No
Go to the next step.
5
PURPOSE: INSPECT FOR OTHER RELATED DTCs
• Perform the DTC inspection for the PCM. (See DTC INSPECTION.)
• Are any other DTCs displayed?
Yes
Repair the malfunctioning location according to the applicable DTC troubleshooting.
Go to the next step.
No
Go to the next step.
6
PURPOSE: VERIFY CONNECTOR CONNECTIONS
• Start the engine.
• Access the FUEL_PRES PID using the M-MDS. (See PID/DATA MONITOR INSPECTION.)
• Does the PID value fluctuate when the following connectors are shaken?
― Fuel pressure sensor
― PCM
Yes
Repair or replace the applicable wiring harness or connector parts.
Go to Troubleshooting Diagnostic Procedure to perform the repair completion verification.
No
Go to the next step.
7
PURPOSE: VERIFY FUEL PRESSURE (LOW-SIDE) MALFUNCTION
Note
• Verify the fuel pressure on the low pressure side with the operation of the high pressure fuel pump turned off.
• Bleed the remaining pressure in the fuel line using the following procedure.
1. Switch the ignition off.
2. Disconnect the high pressure fuel pump connector.
3. Remove the fuel pump relay. (See RELAY LOCATION [(US)].)
4. Start the engine and wait until the engine stalls.
• Switch the ignition off.
• Install the fuel pump relay.
• Switch the ignition ON (engine off).
• Display PID FUEL_PRES and simulation item FUEL_PUMP_REQ using the M-MDS. (See PID/DATA MONITOR INSPECTION.) (See SIMULATION INSPECTION.)
• Turn simulation item FUEL_PUMP_REQ on.
• Is the FUEL_PRES PID value 475—555 kPa {4.85—5.65 kgf/cm2, 68.9—80.4 psi}?
Yes
Go to Troubleshooting Diagnostic Procedure to perform the procedure from Step 2.
No
Go to Troubleshooting Diagnostic Procedure to perform the procedure from Step 1.



Troubleshooting Diagnostic Procedure

Intention of troubleshooting procedure
• Step 1
― Inspect the fuel supply system (low pressure side).
• Step 2
― Perform a unit inspection of the fuel pressure sensor.
• Repair completion verification
― Verify that the primary malfunction is resolved and there are no other malfunctions.

Step

Inspection

Results

Action

1
PURPOSE: VERIFY IF MALFUNCTION RELATED TO FUEL PIPE (LOW PRESSURE SIDE) AFFECTS DIAGNOSTIC RESULTS
• Is there any malfunction?
Yes
Replace the fuel pump unit and perform the repair completion verification.
No
Inspect the fuel system pipes (low to high pressure sides) for fuel leakage and restriction.
• If there is any malfunction:
― Repair or replace the malfunctioning location and perform the repair completion verification.
• If there is no malfunction:
― Go to the next step.
2
PURPOSE: INSPECT FUEL PRESSURE SENSOR FOR MALFUNCTION
• Is the part normal?
Yes
Go to the next step.
No
Repair or replace the malfunctioning location and perform the repair completion verification.
Repair completion verification 1
PURPOSE: VERIFY THAT VEHICLE IS REPAIRED
• Install/connect the part removed/disconnected during the troubleshooting procedure.
• Clear the DTC recorded in the memory. (See CLEARING DTC.)
• Replicate the vehicle conditions at the time the DTC was detected using the following procedure.
― Implement the repeatability verification procedure. (See Repeatability Verification Procedure.)
• Perform the DTC inspection for the PCM. (See DTC INSPECTION.)
• Is the same Pending DTC present?
Yes
Refer to the controller area network (CAN) malfunction diagnosis flow to inspect for a CAN communication error.
If the CAN communication is normal, perform the diagnosis from Step 1.
No
Go to the next step.
Repair completion verification 2
PURPOSE: VERIFY IF OTHER DTCs DISPLAYED
• Perform the DTC inspection. (See DTC INSPECTION.)
• Are any other DTCs displayed?
Yes
Repair the malfunctioning location according to the applicable DTC troubleshooting.
No
DTC troubleshooting completed.