How To Proceed With Troubleshooting
HINT:
*: Use the GTS.
PROCEDURE
VEHICLE BROUGHT TO WORKSHOP
|
CUSTOMER PROBLEM ANALYSIS
(a) Interview the customer and confirm the problem.
Click here ![]()
|
CHECK DTC, FREEZE FRAME DATA AND VEHICLE CONTROL HISTORY (RoB)*
(a) Check and record DTCs and Freeze Frame Data.
for DTC Check / Clear: Click here ![]()
for Freeze Frame Data: Click here ![]()
(b) Clear the DTCs and Freeze Frame Data.
for DTC Check / Clear: Click here ![]()
for Freeze Frame Data: Click here ![]()
(c) Reconfirm the DTCs.
(1) Reconfirm the DTCs based on the recorded DTCs and Freeze Frame Data.
for DTC Check / Clear: Click here ![]()
for Freeze Frame Data: Click here ![]()
HINT:
- When CAN communication system DTCs are output, repair the CAN communication system first.
Click here
.gif)
- If DTCs related to momentary interruptions are output, perform troubleshooting for those DTCs first.
Click here
.gif)
- If the GTS cannot communicate with the skid control ECU, inspect the CAN communication system.
Click here
.gif)
- If there is no response from the electric brake booster (brake booster with master cylinder assembly) or skid control ECU (brake actuator assembly), inspect the supply power circuit.
Click here
.gif)
(d) Check the Vehicle Control History (RoB).
Click here ![]()
Vehicle Control History (RoB)
Chassis > Brake/EPB > UtilityVehicle Control History (RoB)
Chassis > Steering Angle Sensor > UtilityVehicle Control History (RoB)
Result | Proceed to |
|---|---|
DTCs are not output. (Problem symptom occurs.) |
A |
DTCs are output. |
B |
DTCs are not output. (Problem symptom does not occur.) |
C |
DTCs are not output. (Vehicle control history (RoB) is stored.) |
D |
| A | CONFIRM PROBLEM SYMPTOMS |
| B | REPAIR CIRCUITS INDICATED BY OUTPUT DTCS* |
| C | USE SIMULATION METHOD TO CHECK |
| D | PERFORM TROUBLESHOOTING AND REPAIR REGARDING VEHICLE CONTROL HISTORY (RoB)* NOTICE: After performing troubleshooting and repair regarding vehicle control history (RoB), clear the vehicle control history (RoB). |