factors such as movements (moving the wires and the relay manually), heat (using hot air), and water
(humidity).
Movements, heat or humidity can be the failure causes which are difficult to be reproduced. Therefore,
with the vehicle stopped, the failure reproduction simulation test described below can be performed.
Besides, if it is considered that a component causes the failure and a tester, etc. is connected to that
component so as to confirm the failure phenomenon, it is also possible to assess functionality.
Counterchecking, storing and clearing the failure code/frozen image data
By checking the failure code/frozen image data after having confirmed the malfunction phenomenon
reproduction, it can be determined if the system indicated by the failure code before the reproduction
confirmation works properly or not. Afterwards, proceed with one of the following steps.
1. When a failure code is detected at the moment of checking, and this code is detected after the
malfunction reproduction confirmation, it means that the problem still remains in the diagnosis circuit.
Remove failures according to the codes detected.
2. If no abnormal code is detected, although the failure has been found during the malfunction repro-
duction confirmation, it is probable that a different defect from the one connected to the diagnosis system
is being detected. Remove the failure according to the malfunction phenomenon.
3. If no malfunction is detected during the malfunction reproduction confirmation, and the regular code
is indicated when the failure code is checked, it is assumed that an abnormal situation, as bad contacts
of cables and connectors was previously detected, but it does no longer exist currently. Check cables
and connectors of the system connected to the failure code detected before the malfunction phenom-
enon reproduction confirmation.
Visual check
Check cables and connectors of the systems indicated at the moment of the initial check of the failure
code, according to the "visual check and contact pressure check" procedure.
Check and repair according to the table of self-diagnosis codes
Before troubleshooting, perform the basic check to identify the possible malfunction causes. For ex-
ample, if by checking the spark, it turns out that there are no problems, it can be inferred that the ignition
system works properly. Besides, the defect causes can be identified also according to the information
obtained from the customer
N.B.
- IF THE MALFUNCTION CAN NOT BE DETECTED THROUGH THE DIAGNOSIS SYSTEM, AL-
THOUGH THERE IS A MALFUNCTION PHENOMENON, IT MEANS THAT SUCH DEFECT IS NOT
INCLUDED WITHIN THE DETECTION RANGE OF THE DIAGNOSIS SYSTEM OR THAT THE DE-
FECT IS IN A SYSTEM DIFFERENT FROM THOSE CONNECTED TO THE DIAGNOSIS SYSTEM.
Checking malfunctions which are detected intermittently
Inspect the parts where the malfunction is detected intermittently, as cable harness and connectors, as
described in the section "Checking malfunctions which are detected intermittently and bad contacts".
During the inspection, focus checks on the circuits connected to the failure code systems indicated at
the moment of the failure code initial check
PORTER 1.3 16V Iniection System
IS - 407
To Next Page
Loading...
Need help?
General
