Symptom Confirmation and Diagnostic Trouble Code Check

SYMPTOM CONFIRMATION AND DIAGNOSTIC TROUBLE CODE CHECK

The diagnostic system in the CELICA fulfills various functions. The first function is the Diagnostic Trouble Code Check in which a malfunction in the signal circuits to the ECU is stored in code in the ECU memory at the time of occurrence, to be output by the technician during troubleshooting. Another function is the Input Signal Check which checks if the signals from various switches are sent to the ECU correctly.





By using these check functions, the problem areas can be narrowed down quickly and troubleshooting can be performed effectively. The diagnostic functions are incorporated in the following systems in the CELICA.





In diagnostic trouble code check, it is very important to determine whether the problem indicated by the diagnostic trouble code is still occurring or occurred in the past but returned to normal at present. In addition, it must be checked in the problem symptom check whether the malfunction indicated by the diagnostic trouble code is directly related to the problem symptom or not. For this reason, the diagnostic trouble codes should be checked before and after the symptom confirmation to determine the current conditions, as shown in the table. If this is not done, it may, depending on the case, result in unnecessary troubleshooting for normally operating systems, thus making it more difficult to locate the problem, or in repairs not pertinent to the problem. Therefore, always follow the procedures in correct order and perform the diagnostic trouble code check.





Taking into account the points given above, a flow chart showing how to proceed with troubleshooting using the diagnostic trouble code check. This flow chart shows how to utilize the diagnostic trouble code check effectively. Then by carefully checking the results, this chart indicates how to proceed either to diagnostic trouble code troubleshooting or to troubleshooting of the problem symptoms table.