HOW TO PROCEED WITH TROUBLESHOOTING
Troubleshooting · Vehicles built Jul 2010 – Jun 2012
Versions by build date: May 2007 – Jul 2008 Aug 2008 – Jun 2010 Jul 2010 – Jun 2012 from Jul 2012
- HINT:
- Use the following procedures to troubleshoot the key reminder warning system.
- The intelligent tester should be used in steps 4 and 6.
- Use the following procedures to troubleshoot the key reminder warning system.
| 1.VEHICLE BROUGHT TO WORKSHOP |
| |||||
| 2.CUSTOMER PROBLEM ANALYSIS CHECK |
- 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.
- 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.
- The following 5 items are important points in the 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
| |||||
| 3.INSPECT BATTERY VOLTAGE |
Measure the battery voltage.
- Standard voltage:
- 11 to 14 V
| |||||
| 4.INSPECT COMMUNICATION FUNCTION OF CAN COMMUNICATION SYSTEM |
Use the intelligent tester to check if the CAN communication system is functioning normally.
- Result:
Result
Proceed to
(ECU connected, communication line malfunctioning) DTC is not output.
A
(ECU connected, communication line malfunctioning) DTC is output.
B
(Click here)
|
|||||
| |||||
| 5.PROBLEM SYMPTOMS TABLE |
- Result:
Result
Proceed to
Fault is not listed in problem symptoms table
A
Fault is listed in problem symptoms table
B
|
|||||
| |||||
| 6.OVERALL ANALYSIS AND TROUBLESHOOTING |
DATA LIST / ACTIVE TEST (Click here)
TERMINALS OF ECU (Click here)
| |||||
| 7.REPAIR OR REPLACE |
| |||||
| 8.CONFIRMATION TEST |
| |||||