How To Proceed With Troubleshooting [08/2014 - ]: Procedure
- VEHICLE BROUGHT TO WORKSHOP
Result
Proceed to NEXT Result: 1
NEXT
See step 2
- CUSTOMER PROBLEM ANALYSIS
- 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 in 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 Result
Proceed to NEXT Result: 1
NEXT
See step 3
- INSPECT AUXILIARY BATTERY VOLTAGE
- Measure the auxiliary battery voltage with the power 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.
Result
Proceed to NEXT
Result: 1
NEXT
See step 4
- Measure the auxiliary battery voltage with the power switch off.
- INSPECT COMMUNICATION FUNCTION OF LIN COMMUNICATION SYSTEM*
- Using the Techstream, inspect the LIN communication function to ensure there are no malfunctions in the communication system (See article. Refer to DTC CHECK / CLEAR [08/2014 - ] ).
Result
Result Proceed to DTC is not output A DTC is output B
Result: 2
B
GO TO DIAGNOSTIC TROUBLE CODE CHART
(See article. Refer to DIAGNOSTIC TROUBLE CODE CHART [08/2014 - ] )
Result: 1
A
See step 5
- Using the Techstream, inspect the LIN communication function to ensure there are no malfunctions in the communication system (See article. Refer to DTC CHECK / CLEAR [08/2014 - ] ).
- PROBLEM SYMPTOMS TABLE
- Refer to Problem Symptoms Table (See article. Refer to PROBLEM SYMPTOMS TABLE [08/2014 - ] ).
Result
Result Proceed to Fault is not listed in Problem Symptoms Table A Fault is listed in Problem Symptoms Table B
Result: 2
B
See step 7
Result: 1
A
See step 6
- Refer to Problem Symptoms Table (See article. Refer to PROBLEM SYMPTOMS TABLE [08/2014 - ] ).
- OVERALL ANALYSIS AND TROUBLESHOOTING*
- Terminals of ECU (See article. Refer to TERMINALS OF ECU [08/2014 - ] ).
- Data List / Active Test (See article. Refer to DATA LIST / ACTIVE TEST [08/2014 - ] ).
Result
Proceed to NEXT
Result: 1
NEXT
See step 7
- REPAIR OR REPLACE
Result
Proceed to NEXT Result: 1
NEXT
See step 8
- CONFIRMATION TEST
Result
Proceed to NEXT Result: 1
NEXT
END