Home

Toyota Workshop

GSIC - Global Service Information Center

HOW TO TROUBLESHOOT ECU CONTROLLED SYSTEMS > HOW TO PROCEED WITH TROUBLESHOOTING

OPERATION FLOW

HINT:

Perform troubleshooting in accordance with the procedure below. The following is an outline of basic troubleshooting procedure. Confirm the troubleshooting procedure for the circuit you are working on before beginning troubleshooting.

1.VEHICLE BROUGHT TO WORKSHOP

NEXT

2.CUSTOMER PROBLEM ANALYSIS

Ask the customer about the conditions and environment when the problem occurred.

NEXT

3.INSPECT BATTERY VOLTAGE

Standard voltage:: 11 to 14 V
If the voltage is below 11 V, recharge or replace the battery before proceeding to the next step.

NEXT

4.SYMPTOM CONFIRMATION AND DTC (AND FREEZE FRAME DATA) CHECK

Visually check the wire harnesses, connectors and fuses for open and short circuits.
Warm up the engine to the normal operating temperature.
Confirm the problem symptoms and conditions, and check for DTCs.
Result:
Result
Proceed to
DTC is output
A
DTC is not output
B

GO TO STEP 6

A

5.DTC CHART

Find the output DTC in the DTC chart. Look at the Trouble Area column for a list of potentially malfunctioning circuits and/or parts.

NEXT.

GO TO STEP 7

6.PROBLEM SYMPTOMS CHART

Find the problem symptoms in the problem symptoms table. Look at the Suspected Area column for a list of potentially malfunctioning circuits and/or parts.

NEXT

7.CIRCUIT INSPECTION OR PARTS INSPECTION

Identify the malfunctioning circuit or part.

NEXT

8.ADJUST, REPAIR OR REPLACE

Adjust, repair or replace the malfunctioning circuit or parts.

NEXT

9.CONFIRMATION TEST

After the adjustment, repairs or replacement of components, confirm that the malfunction no longer exists. If the malfunction does not recur, perform a confirmation test under the same conditions and in the same environment as when the malfunction first occurred.

NEXT

END

CUSTOMER PROBLEM ANALYSIS

HINT:

When troubleshooting, confirm that the problem symptoms have been accurately identified. Preconceptions should be discarded in order to make an accurate judgment. To clearly understand what the problem symptoms are, it is extremely important to ask the customer about the problem and the conditions at the time the malfunction occurred.
Gather as much information as possible for reference. Past problems that seem unrelated may also help in some cases.

The following 5 items are important points for problem analysis:

What
Vehicle model, system name
When
Date, time, occurrence frequency
Where
Road conditions
Under what conditions?
Driving conditions, weather conditions
How did it happen?
Problem symptoms

SYMPTOM CONFIRMATION AND DIAGNOSTIC TROUBLE CODE

HINT:

The diagnostic system in this vehicle has various functions.

The first function is the Diagnostic Trouble Code (DTC) check. A DTC is a code stored in the ECU memory whenever a malfunction in the signal circuits to the ECU occurs. In a DTC check, a previous malfunction's DTC can be checked by a technician during troubleshooting.

Another function is the Input Signal Check, which checks if the signals from various switches are sent to the ECU correctly.
By using these functions, the problem areas can be narrowed down and troubleshooting can be more effective. Diagnostic functions are incorporated in the following systems of this vehicle.

System	Symptom Confirmation and Diagnostic Trouble Code
System	DTC Check (Normal Mode)	DTC Check (Check Mode)	Sensor Check/Test Mode (Input Signal Check)	Data List	Active Test
SFI System (2ZR-FXE) (w/ EGR)	○	○	-	○	○
SFI System (2ZR-FXE) (w/o EGR)	○	○	-	○	○
Hybrid Control System	○	-	-	○	○
Hybrid Battery System	○	-	-	○	○
Cruise Control System	○	-	-	○	○
Dynamic Radar Cruise Control System	○	-	-	○	○
Electronic Shift Lever System	○	-	-	○	-
Electronically Controlled Brake System	○	-	○	○	○
Power Steering System	○	-	-	○	-
Audio and Visual System	○	-	-	○	-
Navigation System (for Radio and Display Type)	○	-	-	○	-
Navigation System (for Navigation Receiver Type)	○	-	-	○	-
Intelligent Parking Assist System	○	-	-	○	-
Rear View Monitor System	-	-	-	-	-
LIN Communication System	○	-	-	○	-
CAN Communication System	○	-	-	-	-
Power Door Lock Control System	-	-	-	○	○
Wireless Door Lock Control System	○	-	-	○	○
Entry and Start System (for Entry Function)	○	-	-	○	○
Entry and Start System (for Start Function)	○	-	-	○	○
Engine Immobiliser System	○	-	-	○	○
Theft Deterrent System	○	-	-	○	○
Blocking System	○	-	-	-	-
Lighting System (Interior)	-	-	-	○	○
Meter / Gauge System	○	-	-	○	○
Clock System	-	-	-	-	-
Airbag System	○	○	-	○	-
Pre-Crash Safety System	○	-	-	○	○
Front Power Seat Control System	-	-	-	-	-
Seat Belt Warning System	-	-	-	○	○
Seat Heater System	-	-	-	-	-
Air Conditioning System	○	-	-	○	○
Solar Ventilation System	-	-	-	○	-
Power Window Control System	○	-	-	○	○
Window Defogger System	-	-	-	○	○
Sliding Roof System	○	-	-	○	○
Power Mirror Control System	-	-	-	-	-
Wiper and Washer System	-	-	-	-	-
Lighting System (Exterior)	○	-	-	○	○
Horn System	-	-	-	-	-

In the DTC check, it is very important to determine whether the problem indicated by the DTC either: 1) still occurs, or 2) occurred in the past but has returned to normal. In addition, the DTC should be compared to the problem symptom to see if they are related. For this reason, DTCs should be checked before and after confirmation of symptoms (i.e., whether or not problem symptoms exist) to determine current system conditions, as shown in the flowchart below.

Never skip the DTC check. Failing to check for DTCs, depending on the case, may result in unnecessary troubleshooting for systems operating normally or lead to repairs not related to the problem. Follow the procedure listed in the flowchart in the correct order.

The following flowchart shows how to proceed with troubleshooting using the DTC check. Directions from the flowchart will indicate how to proceed either to DTC troubleshooting or to the troubleshooting of each problem symptom.

1.DTC CHECK

NEXT

2.MAKE A NOTE OF DTC DISPLAYED AND THEN CLEAR MEMORY

NEXT

3.SYMPTOM CONFIRMATION

Result:

Result	Proceed to
No symptoms exist	A
Symptoms exist	B

GO TO STEP 5

A

4.SIMULATION TEST USING SYMPTOM SIMULATION METHODS

NEXT

5.DTC CHECK

Result:

Result	Proceed to
DTC is not output	A
DTC is output	B

TROUBLESHOOT FOR PROBLEM INDICATED BY DTC

A

6.SYMPTOM CONFIRMATION

Result:

Result	Proceed to
No symptoms exist	A
Symptoms exist	B

If a DTC was displayed in the initial DTC check, the problem may have occurred in a wire harness or connector in that circuit in the past. Check the wire harness and connectors.

END

A

TROUBLESHOOT FOR EACH PROBLEM SYMPTOM

The problem still occurs in a place other than the diagnostic circuit (the DTC displayed first is either for a past problem or a secondary problem).

SYMPTOM SIMULATION

HINT:

The most difficult case in troubleshooting is when no problem symptoms occur. In such a case, a thorough problem analysis must be carried out. A simulation of the same or similar conditions and environment in which the problem occurred in the customer's vehicle should be carried out. No matter how much skill or experience a technician has, troubleshooting without confirming the problem symptoms will lead to important repairs being overlooked and mistakes or delays.

For example:: With a problem that only occurs when the engine is cold or as a result of vibration caused by the road during driving, the problem can never be determined if the symptoms are being checked on a stationary vehicle or a vehicle with a warmed-up engine. Vibration, heat or water penetration (moisture) is difficult to reproduce. The following symptom simulation tests are effective substitutes for the conditions and can be applied to a stationary vehicle. Important points in the symptom simulation test:
In the symptom simulation test, the problem symptoms as well as the problem area or parts must be confirmed. First, narrow down the possible problem circuits according to the symptoms. Then, connect the tester and carry out the symptom simulation test, judging whether the circuit being tested is defective or normal. Also, confirm the problem symptoms at the same time. Refer to Problem Symptoms Table for each system to narrow down the possible causes.
To reproduce DTCs, it is necessary to satisfy the respective DTC detection conditions.

VIBRATION METHOD: When a malfunction seems to occur as a result of vibration.
Text in Illustration
*1
Vibrate Slightly
*2
Shake Slightly
*3
Vibrate Slightly
1. PART AND SENSOR
  Apply slight vibration with a finger to the part of the sensor suspected to be the cause of the problem, and check whether the malfunction occurs.
  NOTICE:
  Applying strong vibration to relays may open the relays.
2. CONNECTORS
  Slightly shake the connector vertically and horizontally.
3. WIRE HARNESS
  Slightly shake the wire harness vertically and horizontally.
  HINT:
  The connector joint and fulcrum of the vibration are the major areas that should be checked thoroughly.
HEAT METHOD: When a malfunction seems to occur when the area in question is heated.
1. Heat the component that is the possible cause of the malfunction with a hair dryer or similar device. Check if the malfunction occurs.
  NOTICE:
  1. Do not heat components to more than 60°C (140°F). Exceeding this temperature may damage the components.
  2. Do not apply heat directly to parts in an ECU.

WATER SPRINKLING METHOD: When a malfunction seems to occur on a rainy day or in high-humidity.
1. Sprinkle water onto the vehicle and check if the malfunction occurs.
  NOTICE:
  1. Never sprinkle water directly into the engine compartment. Indirectly change the temperature and humidity by spraying water onto the front of the radiator.
  2. Never apply water directly onto the electronic components.
  HINT:
  If the vehicle has or had a water leak problem, the leak may have damaged the ECU or connections. Look for evidence of corrosion or short circuits. Proceed with caution during water tests.

HIGH ELECTRICAL LOAD METHOD: When a malfunction seems to occur when the electrical load is high.
1. Turn on the heater blower, headlights, rear window defogger and all other electrical loads. Check if the malfunction recurs.

DIAGNOSTIC TROUBLE CODE CHART

Look for output Diagnostic Trouble Codes (DTCs) (from the DTC checks) in the appropriate section's Diagnostic Trouble Code Chart. Use the chart to determine the trouble area and the proper inspection procedure. A description of each of the chart's columns is shown in the table below.

Item	Description
DTC No.	Indicates the diagnostic trouble code.
Detection Item	Indicates the system or details of the problem.
Trouble Area	Indicates the suspected areas of the problem.
See page	Indicates the page where the inspection procedure for each circuit is to be found, or gives instruction for checking and repairs.

PROBLEM SYMPTOMS TABLE

HINT:

Use the table below to help determine the cause of problem symptoms. If multiple suspected areas are listed, the potential causes of the symptoms are listed in order of probability in the "Suspected Area" column of the table. Check each symptom by checking the suspected areas in the order they are listed. Replace parts as necessary.

Item	Description
Symptom	-
Suspected Area	Indicates the circuit or part which needs to be checked.
See page	Indicates the page where the inspection procedure is located.

INSPECTION

A description of the main points for inspection of suspected areas is shown in the following table.

Item	Description
Description	The major role and operation of the circuit or system and its component parts are explained.
DTC No., DTC Detection Condition and Trouble Area	Indicates the diagnostic trouble codes, DTC detection conditions and suspected areas for a problem.
Wiring Diagram	This is a wiring diagram for the circuit or system. This diagram can be used together with the Electrical Wiring Diagram to thoroughly understand the circuit. Wire colors are indicated by alphabetical codes. B = Black, L = Blue, R = Red, BR = Brown, LG = Light Green, V = Violet, G = Green, O = Orange, W = White, GR = Gray, P = Pink, Y = Yellow, SB = Sky Blue The first letter indicates the basic wire color and the second letter indicates the color of the stripe.
Inspection Procedure	This shows the procedure not only to determine whether the circuit is normal or abnormal, but also to determine whether the problem is located in the sensors, actuators, wire harness or ECU.
Illustration of the ECU connector during the check	The illustration shows whether the connector being checked is connected or disconnected. The connections for an electrical tester are indicated by (+) or (-) after the terminal name. For inspections between a connector and body ground, information about the ground is not shown in the illustration.

What	Vehicle model, system name
When	Date, time, occurrence frequency
Where	Road conditions
Under what conditions?	Driving conditions, weather conditions
How did it happen?	Problem symptoms