Operation CHARM: Car repair manuals for everyone.

GF07.16-P-3200GZ CDI European On-Board Diagnosis (EOBD) Function




GF07.16-P-3200GZ CDI European On-Board Diagnosis (EOBD) Function
ENGINE 642 in MODEL 164.8 /1 except CODE (494) USA version up to Model Year 2008
/ YoM 07
ENGINE 642.9 in MODEL 463 up to 31.5.12
- except CODE (494) USA version





Shown on model 164

0100 STAR DIAGNOSIS

A1 Instrument cluster
A1e58 Engine diagnosis indicator lamp
N3/9 CDI control unit
N93 Central gateway control unit
X11/4 Data link connector

European On-Board Diagnosis (EOBD) has the following tasks:
^ Monitoring emission-related components and systems during travel
^ Determining and storing malfunctions
^ Display of malfunctions via the engine diagnosis indicator lamp
^ Transfers detected faults to STAR DIAGNOSIS through a uniform interface

The following systems and functions are electronically monitored:
^ Exhaust gas recirculation (EGR)
^ Smooth running control (cylinders 1 to 6)
^ Fuel system
^ Glow system
^ Intake and charge air system

Readiness code
This code makes it possible to recognize that test procedures (function chains) relating to fault recognition have been completed.

The readiness code encompasses the electronic systems:
^ AGR
^ Fuel system
^ Smooth running control

The readiness code is flagged, if 2 driving cycles including a cold start have been concluded with a fault.

Warm-up cycle
Systems that are not constantly monitored are checked only when a warm-up cycle is executed.
One warm-up cycle consists of:
^ Engine start
^ Temperature increase greater than 4.5°C
^ Final temperature greater than 60°C
^ Engine switch-off
^ Computer run-on at least 10 s (wait for cooling fan run-on)

Driving cycle
One driving cycle consists of:
^ Engine start
^ 35 s at idle
^ Engine switch-off
^ Computer run-on at least 10 s (wait for cooling fan run-on)

The CDI control unit (N3/9) checks its input and output signals in terms of plausibility and detects possible faults.

Fault detection
The following errors and fault statuses are detected:
^ Signals over or below the limit value (e.p. line open circuit, short circuit, defective sensor)
^ Plausibility of signals
^ Function chains with faults
^ Fault messages via Control Area Network (data bus/CAN bus) (CAN), from the CDI control unit and from the fully integrated transmission control (VGS) control unit (Y3/8n4)

Fault storage
Faults detected are stored in the fault memory along with the freeze frame data. If the fault is not confirmed during the following driving cycle, it is deleted. Emission-related faults are always entered, as they have high priority.
Following 40 fault-free driving cycles, an exhaust gas relevant fault is deleted from the fault memory.

Freeze frame data and operating conditions

If a fault is detected, the following freeze frame data are saved along with the fault code:
^ Vehicle speed
^ Engine speed
^ Coolant temperature
^ Boost air temperature
^ Boost pressure
^ Engine load status

Consequential faults
If a faulty signal is detected and the corresponding fault code is set, all tests where this signal is required as a reference parameter are aborted. This prevents consequential faults from being stored.

Fault memory readout
Stored faults can be read out using STAR DIAGNOSIS at status "Circuit 15 ON" or at status "Circuit 61 ON" via the data link connector. The fault memory can only be cleared at status "circuit 15 ON".
The fault memory is not erased if the battery (G1) is disconnected.

CDI control unit power-down
After faults are erased, it is necessary to wait until the processor has completed power-down sequence after circuit 15 is switched off. The processor power-down sequence lasts a maximum of 10 s. If the cooling fan run-on is active, it is necessary to wait for the run-on time to complete.