Dacia Solenza 2004, Repair Manual

Page: 119 / 891

IGNITION AND INJECTION
17
17 - 25
Diagnostic – General
This document is presenting the diagnostic for the injection computers SIRIUS 32, which have
nr.program E1 and Diag.variant 10.
In order to perform the diagnostic of this injection system, it is necessary to use the following
elements:
- Diagnostic Technical Note
- Functional electric diagram of the respective vehicle
- CLIP technical tester, 90 ways terminal (ELE 1497).
DIAGNOSTIC PERFORMING STEPS
- CLIP tester connection to the diagnostic socket for identification of the SIRIUS 32 computer
type, of the “E1” program and the diagnostic variant “10”.
- Information identification in the document “Diagnostic” corresponding to the injection system.
- Reading and observing of the working instructions presented in the diagnostic documentation.
- Reading of the failures memorized by the injection computer, by means of the CLIP tester and
causes identification by means of chapter “ Failures interpretation”
DO NOT ERASE THE MEMORIZED FAILURES BEFORE READING THEM BY
MEANS OF THE CLIP TESTER
Write the memorized failures, after having previously red by means of the CLIP tester, in order
to be taken into consideration and treated, if these are to be themselves erased.
1. Treat all existent failures.
2. Memorized failures:
Perform the operations mentioned in “Recommendations” corresponding to each failure, in order
to confirm the failure.
If the failure is becoming present, then it must be treated.
3. For vehicle provided with OBD.
If the failure is memorized and the OBD indicator is on, read the failure context remarks, the
corresponding state at” OBD indicator lighting requesting”, in order to establish if this is the cause
for indicator lighting.
In such case, treat the failure as being present.
REMARK
: the state “ OBD indicator lighting requesting” may be YES or NO and may be
consulted by selecting menu “ FUNCTIONS”, then OBD INDICATOR LIGHTING”.
Perform the conformity checking (evidencing of eventually disturbances not yet declared by the
system self-diagnostic).
Validate the reparation performing (failure cause elimination).
Take benefit of the information from the failure-locating tree, in case the problem is persisting.
vnx.su