HOW TO PROCEED WITH TROUBLESHOOTING
Troubleshooting
- HINT:
- The intelligent tester can be used in steps 3, 4, 5, 6, 7 and 11.
| 1.VEHICLE BROUGHT TO WORKSHOP |
| |||||
| 2.CUSTOMER PROBLEM ANALYSIS |
Confirm problem symptoms.
| |||||
| 3.CHECK MULTIPLEX COMMUNICATION SYSTEM |
Check for DTCs (Click here).
- HINT:
- The skid control ECU sends the AWD indicator signals (AWD warning) to the gateway ECU via the CAN communication, and the gateway ECU sends the signals to the combination meter assembly (meter CPU) via multiplex communication system (BEAN Bus).
- Result:
Result
Proceed to
DTC is not output
A
DTC is output
B
|
|||||
| |||||
| 4.CHECK CAN COMMUNICATION SYSTEM |
Check for DTCs (Click here).
- HINT:
- The skid control ECU of this system is connected to the CAN communication system.
- Therefore before starting troubleshooting, make sure to check that there is no trouble in the CAN communication system.
- Result:
Result
Proceed to
DTC is not output
A
DTC is output
B
|
|||||
| |||||
| 5.CHECK HYBRID CONTROL SYSTEM DTC |
Check for DTCs (Click here).
Record the DTCs.
Clear the DTCs (Click here).
Recheck for DTCs.
Simulate the malfunction and check if the DTCs are output again (Click here).
- Result:
Result
Proceed to
DTC is not output
A
DTC is output
B
|
|||||
| |||||
| 6.CHECK BRAKE CONTROL SYSTEM DTC |
Check for DTCs (Click here).
Record the DTCs.
Clear the DTCs (Click here).
Recheck for DTCs.
Simulate the malfunction and check if the DTCs are output again (Click here).
- Result:
Result
Proceed to
DTC is output
A
DTC is not output
B
DTCs are not output, and the malfunction cannot be simulated or checked
C
|
|||||
|
|||||
| |||||
| 7.DIAGNOSTIC TROUBLE CODE CHART |
| Result |
See procedure |
| C1348 is output |
Click here
|
| Other than C1348 is output |
Click here
|
| |||||
| 8.PROBLEM SYMPTOMS TABLE |
| |||||
| 9.CIRCUIT INSPECTION |
| |||||
| 10.REPAIR |
| |||||
| 11.CONFIRMATION TEST |
| |||||