INJECTION Fault finding - Interpretation of faults

17
17-19
SAGEM2000 PROGRAM No: A3 VDIAG No.: 08

DF017 PRESENT OR STORED

FLYWHEEL SIGNAL INFORMATION

1.DEF : Flywheel target fault 2.DEF : No tooth signal 1.OBD : (On Board Diagnostic) OBD fault: flywheel target 2.OBD : OBD fault: no flywheel signal NOTES The pressure sensor should not be faulty when performing this fault finding test. Conditions for applying the fault finding procedure to a stored fault: The fault is declared present after operating the starter motor for 10 seconds or after the engine has been running for 2 minutes. 1.DEF 2.DEF Checkthe position of the flywheel sensor. Checkthe cleanness and condition of the sensor, cable and its connections. Replace any parts if necessary. Disconnect the battery. Disconnect the computer. Checkthe cleanness and condition of the connections. Connect the bornier in place of the computer and checkthe insulation, continuity and absence of interference resistanceon the following connections: Computer track E4, connector B Flywheel signal sensor Computer track F3, connector B Flywheel signal sensor (See the connector track numbers in the corresponding wiring diagram). Repair if necessary. Check theflywheel signal sensor resistance. (See the value in the "HELP" section). Replace the sensor if necessary. Checkthe cleanliness and condition of the flywheel. Note: If the target assembly has been altered, remember to adjust the programmed values. If the problem has still not been solved, deal with the other faults and then proceed to the conformity check. AFTER REPAIR If the fault was identified as "1.DEF or 2.DEF", it may change and become "1.OBD or 2.OBD"; this is normal. Follow the instructions to confirm repair:

 If the fault is present and identified as "1.DEF or 2.DEF", continue to deal with the fault. If the fault is stored and identified as "1.DEF or 2.DEF", ignore it. If the fault is present or stored and identified as "1.OBD or 2.OBD", ignore it. Deal with any other possible faults. Clear the fault memory

17
INJECTION Fault finding - Interpretation of faults
17-20
SAGEM2000 PROGRAM No: A3 VDIAG No.: 08

DF017

(Continued) 1.OBD 2.OBD NOTES Run the engine until the fan switches on. If, after following the instructions, the identification has become "1.DEF or 2.DEF", the electrical fault is detected. Accordingly, it should be dealt with as a current breakdown identified as "1.DEF or 2.DEF". If, after following the instructions, the identification has become "1.OBD ou 2.OBD", the electrical fault had been present on a number of occasions, but is no longer detected. Consequently, the circuit should be checked without replacing the parts which are not clearly identified as being faulty. This verification should be based on the fault finding procedure for faults characterised as "1.DEF or 2.DEF

17
INJECTION Fault finding - Interpretation of faults
17-20
SAGEM2000 PROGRAM No: A3 VDIAG No.: 08

DF017

(Continued) 1.OBD 2.OBD NOTES Run the engine until the fan switches on. If, after following the instructions, the identification has become "1.DEF or 2.DEF", the electrical fault is detected. Accordingly, it should be dealt with as a current breakdown identified as "1.DEF or 2.DEF". If, after following the instructions, the identification has become "1.OBD ou 2.OBD", the electrical fault had been present on a number of occasions, but is no longer detected. Consequently, the circuit should be checked without replacing the parts which are not clearly identified as being faulty. This verification should be based on the fault finding procedure for faults characterised as "1.DEF or 2.DEF". AFTER REPAIR If the fault was identified as "1.DEF or 2.DEF", it may change and become "1.OBD or 2.OBD"; this is normal. Follow the instructions to confirm repair: If the fault is present and identified as "1.DEF or 2.DEF", continue to deal with the fault. If the fault is stored and identified as "1.DEF or 2.DEF", ignore it. If the fault is present or stored and identified as "1.OBD or 2.OBD", ignore it. Deal with any other possible faults. Clear the fault memory