TROUBLE DIAGNOSIS — INTRODUCTION; Work Flow (Cont'd); Description for Work Flow

EF & EC-7052prose procedure

Work Flow (Cont'd)

CG10, CGA3

DESCRIPTION FOR WORK FLOW

Description for Work Flow

STEP	DESCRIPTION
STEP I	Get detailed information about the conditions and the environment when the incident/symptom occurred using the "DIAGNOSTIC WORK SHEET". (Refer to EC-7050.)
STEP II	Before confirming the concern, check and write down (print out using CONSULT-II or Generic Scan Tool) the (1st trip) Diagnostic Trouble Code (DTC) and the (1st trip) freeze frame data, then erase the code and the data. (Refer to EC-7036.) The (1st trip) DTC and the (1st trip) freeze frame data can be used when duplicating the incident in STEP III & V. Study the relationship between the symptoms specified by (1st trip) DTC, and the symptom described by the customer. (The "Symptom Matrix Chart" will be useful.) Also check related service bulletins for information.
STEP III	Try to confirm the symptom and under what conditions the incident occurs. The "DIAGNOSTIC WORK SHEET" and the freeze frame data are useful to verify the incident. Connect CONSULT-II to the vehicle in "DATA MONITOR (AUTO TRIG)" mode and check real time diagnosis results. If the incident cannot be verified, perform INCIDENT SIMULATION TESTS. (Refer to GI section.) If the malfunction code is detected, skip STEP IV and perform STEP V.
STEP IV	Try to detect the (1st trip) Diagnostic Trouble Code by driving in or performing the "DIAGNOSTIC TROUBLE CODE CONFIRMATION PROCEDURE". Check and read the (1st trip) DTC and (1st trip) freeze frame data by using CONSULT-II or Generic Scan Tool. During the (1st trip) DTC verification, be sure to connect CONSULT-II to the vehicle in DATA MONITOR (AUTO TRIG) mode and check real time diagnosis results. If the incident cannot be verified, perform INCIDENT SIMULATION TESTS. (Refer to GI section.) In case the "DIAGNOSTIC TROUBLE CODE CONFIRMATION PROCEDURE" is not available, perform the "OVERALL FUNCTION CHECK" instead. The (1st trip) DTC cannot be displayed by this check, however, this simplified "check" is an effective alternative. The "NG" result of the "OVERALL FUNCTION CHECK" is the same as the (1st trip) DTC detection.
STEP V	Take the appropriate action based on the results of STEP I through IV. If the malfunction code is indicated, proceed to TROUBLE DIAGNOSIS FOR DTC PXXXX. If the normal code is indicated, proceed to the BASIC INSPECTION. (Refer to EC-7053.) Then perform inspections according to the Symptom Matrix Chart. (Refer to EC-7056.)
STEP VI	Identify where to begin diagnosis based on the relationship study between symptom and possible causes. Inspect the system for mechanical binding, loose connectors or wiring damage using (tracing) "Harness Layouts". Gently shake the related connectors, components or wiring harness with CONSULT-II set in "DATA MONITOR (AUTO TRIG)" mode. Check the voltage of the related ECM terminals or monitor the output data from the related sensors with CONSULT-II. Refer to EC-7069. The "DIAGNOSTIC PROCEDURE" in EC section contains a description based on open circuit inspection. A short circuit inspection is also required for the circuit check in the DIAGNOSTIC PROCEDURE. For details, refer to GI section ("HOW TO PERFORM EFFICIENT DIAGNOSIS FOR AN ELECTRICAL INCIDENT", "Circuit Inspection"). Repair or replace the malfunction parts.
STEP VII	Once you have repaired the malfunctioning part or replaced a component, you need to run the engine in the same conditions and circumstances which resulted in the customer's initial complaint. Perform the "DIAGNOSTIC TROUBLE CODE CONFIRMATION PROCEDURE" and confirm the normal code (Diagnostic trouble code No. P0000 or 0000) is detected. If the incident is still detected in the final check, perform STEP VI by using a different method from the previous one. Before returning the vehicle to the customer, be sure to erase the unnecessary (already fixed) (1st trip) DTC in ECM. (Refer to EC-7036.)

STEP I

DESCRIPTIONGet detailed information about the conditions and the environment when the incident/symptom occurred using the "DIAGNOSTIC WORK SHEET". (Refer to EC-7050.)

STEP II

DESCRIPTIONBefore confirming the concern, check and write down (print out using CONSULT-II or Generic Scan Tool) the (1st trip) Diagnostic Trouble Code (DTC) and the (1st trip) freeze frame data, then erase the code and the data. (Refer to EC-7036.) The (1st trip) DTC and the (1st trip) freeze frame data can be used when duplicating the incident in STEP III & V. Study the relationship between the symptoms specified by (1st trip) DTC, and the symptom described by the customer. (The "Symptom Matrix Chart" will be useful.) Also check related service bulletins for information.

STEP III

DESCRIPTIONTry to confirm the symptom and under what conditions the incident occurs. The "DIAGNOSTIC WORK SHEET" and the freeze frame data are useful to verify the incident. Connect CONSULT-II to the vehicle in "DATA MONITOR (AUTO TRIG)" mode and check real time diagnosis results. If the incident cannot be verified, perform INCIDENT SIMULATION TESTS. (Refer to GI section.) If the malfunction code is detected, skip STEP IV and perform STEP V.

STEP IV

DESCRIPTIONTry to detect the (1st trip) Diagnostic Trouble Code by driving in or performing the "DIAGNOSTIC TROUBLE CODE CONFIRMATION PROCEDURE". Check and read the (1st trip) DTC and (1st trip) freeze frame data by using CONSULT-II or Generic Scan Tool. During the (1st trip) DTC verification, be sure to connect CONSULT-II to the vehicle in DATA MONITOR (AUTO TRIG) mode and check real time diagnosis results. If the incident cannot be verified, perform INCIDENT SIMULATION TESTS. (Refer to GI section.) In case the "DIAGNOSTIC TROUBLE CODE CONFIRMATION PROCEDURE" is not available, perform the "OVERALL FUNCTION CHECK" instead. The (1st trip) DTC cannot be displayed by this check, however, this simplified "check" is an effective alternative. The "NG" result of the "OVERALL FUNCTION CHECK" is the same as the (1st trip) DTC detection.

STEP V

DESCRIPTIONTake the appropriate action based on the results of STEP I through IV. If the malfunction code is indicated, proceed to TROUBLE DIAGNOSIS FOR DTC PXXXX. If the normal code is indicated, proceed to the BASIC INSPECTION. (Refer to EC-7053.) Then perform inspections according to the Symptom Matrix Chart. (Refer to EC-7056.)

STEP VI

DESCRIPTIONIdentify where to begin diagnosis based on the relationship study between symptom and possible causes. Inspect the system for mechanical binding, loose connectors or wiring damage using (tracing) "Harness Layouts". Gently shake the related connectors, components or wiring harness with CONSULT-II set in "DATA MONITOR (AUTO TRIG)" mode. Check the voltage of the related ECM terminals or monitor the output data from the related sensors with CONSULT-II. Refer to EC-7069. The "DIAGNOSTIC PROCEDURE" in EC section contains a description based on open circuit inspection. A short circuit inspection is also required for the circuit check in the DIAGNOSTIC PROCEDURE. For details, refer to GI section ("HOW TO PERFORM EFFICIENT DIAGNOSIS FOR AN ELECTRICAL INCIDENT", "Circuit Inspection"). Repair or replace the malfunction parts.

STEP VII

DESCRIPTIONOnce you have repaired the malfunctioning part or replaced a component, you need to run the engine in the same conditions and circumstances which resulted in the customer's initial complaint. Perform the "DIAGNOSTIC TROUBLE CODE CONFIRMATION PROCEDURE" and confirm the normal code (Diagnostic trouble code No. P0000 or 0000) is detected. If the incident is still detected in the final check, perform STEP VI by using a different method from the previous one. Before returning the vehicle to the customer, be sure to erase the unnecessary (already fixed) (1st trip) DTC in ECM. (Refer to EC-7036.)

Support our work!

TROUBLE DIAGNOSIS — INTRODUCTION; Work Flow (Cont'd); Description for Work Flow

Work Flow (Cont'd)

DESCRIPTION FOR WORK FLOW

Description for Work Flow

See also

Search Manual