How To Proceed With Troubleshooting
HINT:
- Use the following procedure to troubleshoot the lighting system.
- *: Use the GTS.
PROCEDURE
VEHICLE BROUGHT TO WORKSHOP
|
CUSTOMER PROBLEM ANALYSIS
HINT:
- In 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
|
PRE-CHECK
(a) Measure the auxiliary battery voltage with the ignition switch off.
Standard Voltage:
11 to 14 V
If the voltage is below 11 V, recharge or replace the auxiliary battery before proceeding to the next step.
(b) Check the fuses and relays.
(c) Check the connector connections and terminals to make sure that there are no abnormalities such as loose connections, deformation, etc.
|
CHECK COMMUNICATION FUNCTION OF CAN COMMUNICATION SYSTEM*
(a) Using the GTS, check for CAN communication system DTCs.
for HEV Model: Click here ![]()
for Gasoline Model: Click here ![]()
Result | Proceed to |
|---|---|
CAN DTCs are not output |
A |
CAN DTCs are output |
B |
| B | GO TO CAN COMMUNICATION SYSTEM for HEV Model: Click here for Gasoline Model: Click here |
|
CHECK FOR DTC*
(a) Check for DTCs.
Body Electrical > Main Body > Trouble Codes Body Electrical > Headlight Control > Trouble Codes Body Electrical > Headlight Control (Sub) > Trouble CodesResult | Proceed to |
|---|---|
Malfunction is duplicated but DTCs are not output |
A |
Malfunction cannot be duplicated and DTCs are not output |
B |
DTCs are output |
C |
| B | USE SIMULATION METHOD TO CHECK |
| C | GO TO DIAGNOSTIC TROUBLE CODE CHART |
|
CHECK VEHICLE CONTROL HISTORY*
(a) Using the GTS, check for Vehicle Control History (RoB).
Body Electrical > Headlight Control > UtilityVehicle Control History (RoB)
NOTICE:
Make sure to record the output Vehicle Control History.
Result | Proceed to |
|---|---|
Vehicle Control History codes are not output |
A |
Vehicle Control History (RoB) codes are output |
B |
| B | GO TO VEHICLE CONTROL HISTORY |
|
PROBLEM SYMPTOMS TABLE
(a) Refer to Problem Symptoms Table.
Click here ![]()
Result | Proceed to |
|---|---|
Fault is not listed in Problem Symptoms Table |
A |
Fault is listed in Problem Symptoms Table |
B |
| B | GO TO PROBLEM SYMPTOMS TABLE |
|
OVERALL ANALYSIS AND TROUBLESHOOTING*
(a) Operation Check.
Click here ![]()
(b) Terminals of ECU.
Click here ![]()
(c) Data List / Active Test.
Click here ![]()
(d) On-vehicle Inspection.
(e) Inspection.
|
ADJUST, REPAIR OR REPLACE
|
CONFIRMATION TEST
| NEXT | END |