74
75
GAP Diagnostic 2019-07-15 All Rights Reserved
User Manual : Version 33, Firmware V3.0
3.1.4 Faults definitions
The IIDTool provides a definition of faults observed. Fault codes structure is described in
.
3.2 Completing the Diagnosis-2
nd
Key
It is possible to make a reliable diagnosis and ensure the success of a repair using IIDTool functions
in a few steps.
Steps to complete a diagnosis
1- Take notice of faults present on ECUs of the vehicle using the Fault function (
2- Note all displayed faults indicating a possible malfunction and compare these faults with symp-
toms.
3- Decode (if necessary) fault codes starting with the letters P, B or C (
)
4- If necessary, correct issues reported by faults codes. In order of priority, the faults P, B and C
should be addressed.
5- After a repair, clear the fault codes using the Clear Faults function (
6- Calibrate or use a service routine if required (
)
7- If required, proceed with some
8- Ensuring absence of the same fault by checking again the list of faults.
Summary
Read Fault -> Repair -> Calibrate or use a Service Routine (when needed) -> Clear faults
Note :
The presence of numerous faults can signal a Cascade Effect. Follow these steps to complete
the diagnosis.
3.2.1 Diagnostic procedure in the presence of a Cascade Effect
A cascading effect may be suspected when there are many warning lights and the presence of a fault
code beginning with the letter U referring to another system (
).
Steps for diagnosis of a cascading effect
1- Follow each steps to complete a diagnosis and correct the defects for each Fault beginning with
the letter P, B or C
2- Verify that U-type faults are absent.
3- If present, correct the U-type faults referring to a part of the system (not communication related
faults).
Note :
U-type communication fault presence without symptoms is normal
.
Summary of Contents for IIDTool Pro
Page 190: ...190 IIDTool Appendix...