How to Use
WARNING: This page is about a different variant/trim than selected.
CAUTION:
- Always check the odometer value to verify that the repair corresponding to the DTC has not already been performed because the DTC storage record cannot be cleared.
NOTE:
- The determination time after the DTC is recorded differs depending on the DTC. Therefore, the order (record number) in which the DTC is recorded and the order in which the malfunction occurred may not match.
- If several DTCs are displayed when performing the self-test, use the DTC storage record and perform diagnosis using the following procedure.
- Divide DTCs into groups referring to the odometer value.
- Check the recorded order and perform diagnosis in the order from the initially stored group.NOTE:
- If the odometer values for several DTCs are almost the same, diagnosis can be performed efficiently by considering the DTCs as one group because it is highly possible that they were stored due to the same cause.
- If the pending code is displayed by reading out the DTC storage record, repair the malfunctioning location referring to the DTC troubleshooting. (See DTC TABLE ).NOTE:
- If there is a poor connector or wiring harness connection, a malfunction may be detected temporarily and pending code may be stored (if it is a DTC of two-drive cycle type). Then, the malfunction is canceled, the pending code is cleared and cannot be stored. In this case, the pending code which was previously stored in the DTC storage record can be verified.
Use scenario
- If there is a poor connector or wiring harness connection, a malfunction may be detected temporarily and pending code may be stored (if it is a DTC of two-drive cycle type). Then, the malfunction is canceled, the pending code is cleared and cannot be stored. In this case, the pending code which was previously stored in the DTC storage record can be verified.