How To Proceed With Troubleshooting
WARNING: This page is about a different car, the 2003 Toyota 4Runner. However, it is still accessible from the selected car via links, so may be relevant.
Troubleshoot in accordance with the following procedures.
- VEHICLE BROUGHT TO WORKSHOP
- CUSTOMER PROBLEM ANALYSIS CHECK AND SYMPTOM CHECK (See PROBLEM SYMPTOMS TABLE )
- INSPECT COMMUNICATION FUNCTION OF LARGE-SCALE MULTIPLEX COMMUNICATION SYSTEM (BEAN)
- Check that there is no abnormality in the communication system by inspecting the communication function of the multiplex communication system.
- (ECU communication stop, communication line abnormal) With code outputs, proceed to A.
- (ECU communication stop, communication line abnormal) Without code outputs, proceed to B.
- A : Go to Next Step
- B : Go To Section Of Each System
- Check that there is no abnormality in the communication system by inspecting the communication function of the multiplex communication system.
- DIAGNOSTIC TROUBLE CODE CHECK (See
DIAGNOSTIC TROUBLE CODE CHART )
- Check for DTCs and make a note of the code that is output.
- Delete the DTC.
- Check if the DTC will be output once again, when the problem symptom is simulated based on the noted code.
- When no code is output (symptom check and simulation is possible), proceed to A.
- When a code is output, proceed to B.
- A : Go To Next Step
- B : Go to step 7
- PROBLEM SYMPTOMS TABLE (See
)
- Without applicable symptoms, proceed to A.
- With applicable symptoms, proceed to B.
- A : Go To Next Step
- B : Go to step 7
- PERFORM TROUBLESHOOTING IN FOLLOWING METHOD, DEPENDING ON MALFUNCTION SYMPTOM
- See PRE-CHECK
- See TERMINALS OF ECU
- ADJUST, REPAIR OR REPLACE
- END