Trouble Codes
The following table applies to the engines Z 10 XE and Z 12 XE (Motronic 1.5.5) in the Agila. It should be regarded as an example for the troubles codes that control the MIL.
| Trouble code | Monitoring strategy | Fault criterion | Additional parameters | MIL activation | |
|---|---|---|---|---|---|
| Oxygen sensor (front) | 0130 | Plausibility of sensor voltage | Voltage too large/small | Engine temperature, exhaust gas temperature | In 3rd driving cycle |
| 0133 | Signal period | Period or adaptation values of oxygen control | Adaptation value, engine load, sensor availability | In 3rd driving cycle | |
| Oxygen sensor (rear) | 0136 | Plausibility of sensor voltage | Voltage too large/small | Engine temperature, exhaust gas temperature | In 3rd driving cycle |
| 0139 | Signal dynamics | Change in voltage not adequate | Overrun fuel cutoff not active, sensor availability, monitoring time | In 3rd driving cycle | |
| Sensor heating (front) | 0135 | Internal resistance | Limit violation | Exhaust gas temp., sensor availability, battery voltage | In 3rd driving cycle |
| Sensor heating (rear) | 0135 | Internal resistance | Limit violation | Exhaust gas temp., sensor availability, battery voltage | In 3rd driving cycle |
| Trouble code | Monitoring strategy | Fault criterion | Additional parameters | MIL activation | |
|---|---|---|---|---|---|
| Catalytic converter | 0420 | Amplitude of oxygen sensors (rear) | Mean exceeds limit | Sensor availability, oxygen integrator, mass air flow, rpm, engine load | In 3rd driving cycle |
| Misfires | 0300 0301 0302 0303 0304 | Irregular running | Percentage of misfires | Crankshaft speed, engine load | Flashes immediately with damage to catalytic converter, otherwise in 3rd driving cycle |
| Exhaust gas recirculation valve | 0403 | Circuit check | Short circuit/interruption | In 2nd driving cycle | |
| 1405 | Position sensor | Actual value outside tolerance limit | Position sensor, setpoint from characteristic map | In 2nd driving cycle | |
| Mass air flow meter | 0100 | Plausibility of mass air flow | Value too large/small | Throttle valve position, battery voltage | In 2nd driving cycle |
| Phase sensor | 0340 | Check of signal jump | Comparison with setpoint | Rpm sensor | In 3rd driving cycle |
| Cooling water temperature sensor | 0115 | Plausibility check | Short circuit/interruption, signal smaller than setpoint | Time after starting engine | In 2nd driving cycle |
| Trouble code | Monitoring strategy | Fault criterion | Additional parameters | MIL activation | |
|---|---|---|---|---|---|
| Rpm sensor | 0335 | Plausibility of signal | Comparison with phase sensor signal for presence and benchmark | Phase sensor signal | In 2nd driving cycle |
| Injectors | 0201 0202 0203 0204 | Circuit check | Short circuit/interruption | After 5 seconds | |
| Tank vent valve | 0443 | Circuit check | Short circuit/interruption | In 2nd driving cycle | |
| Fuel supply | 0171 | Mixture adaptation in part load range | Limit for too lean | Oxygen control, engine temperature, rpm, engine load | In 3rd driving cycle |
| 0172 | Mixture adaptation in part load range | Limit for too rich | Oxygen control, engine temperature, rpm, engine load | In 2nd driving cycle | |
| 0170 | Mixture adaptation when idling | Limit for too lean/rich | Adaptation made in part load range | In 2nd driving cycle |
Two freeze frames can be stored for each trouble code. Engine data that was available when the fault occurred can be stored in these freeze frames. Data for the first occurrence of the fault in the first freeze frame and data for the last occurrence of this fault in the second frame (if the fault occurred more than once). This applies to all trouble codes that are required by OBD and are indicated by the MIL. Freeze frames can be analysed with readily available readout devices.
All other faults are indicated by the engine electronics telltale.
Two data records are stored for all faults when they occur. These fulfil the same function as the freeze frames for MIL–activating faults. The content of these data records is more comprehensive and the records can be read out using TECH 2.
The vehicle diagnosis concept, which is structured in the same way in TIS 2000, should be followed when diagnosing faults with the aid of the Checking Procedures. It is used to troubleshoot in a minimum amount of time with the strategy below. Troubleshooting is based on an electronic system. A trouble code or fault symptom points to a functional group, e.g. current circuit for coolant temperature sensor, and from there to a component, e.g. temperature sensor.
This procedure is assisted by a corresponding subdivision into Tables A, B and C in the Checking Procedures. The main check (Table A) is the introduction into the diagnosis performed on the selected system. The operations listed there should be performed one after the other. If no fault occurs in a test step, then continue with the next step. If there is a fault, the functional group concerned is diagnosed in Table B. To do this, trouble codes or fault symptoms that occur are evaluated. Then the defective current circuit is checked by measuring with the aid of the corresponding troubleshooting chart in Table C. After the repair is complete, the corresponding test of the functional group (Table B) should be repeated. If this test is successful, the remaining tests in the main test should also be performed. Then the electronic system is completely fit for use again.