2003 3BMXV04.4LEV (540i), 3BMXT04.4E53 & 3BMXT04.6XHP
WARNING: This page does not describe the selected car, but rather 14 other vehicles, including the 2003 BMW Z8, 2003 BMW Z4, 2003 BMW X5, 2003 BMW M5, and 2003 BMW M3. However, it is still accessible from the selected car via links, so may be relevant.
- General Description - Catalyst monitoring is based on monitoring its oxygen storage capability. Engine closed loop feedback control generates lambda (air/fuel ratio) oscillations in exhaust gas. These oscillations are dampened by oxygen storage activity of catalyst. Amplitude of remaining lambda oscillations downstream of catalyst indicates storage capability. To determine catalyst efficiency, oscillation of upstream sensor is needed to calculate oxygen input and output (catalyst) by engine air mass and lambda-deviation. Downstream sensor signal for a threshold catalyst then is derived from this basic value. Anytime real sensor signal downstream corresponds to model, a defective catalyst is recognized. See Fig 1.
- Computation Of Efficiency Factor - Signal of lambda-controller is filtered and multiplied by engine air mass. A value is now added which considers downstream sensor layer. This result is representative of oxygen load into catalyst. Standard amplitude of downstream sensor is computed by averaging measured signals. Difference between standard amplitude and oxygen load is integrated and divided continuously by a time range during which catalyst monitoring is active. This factor is an indicator of catalyst efficiency and it is determined continuously in a certain engine speed and engine load range within the time of monitoring.
- Fault Evaluation - After time range of monitoring has elapsed, efficiency factor (GW) is compared with threshold value. If GW is less than threshold value, a fault is detected and MIL is illuminated after next driving cycle.
- Check Of Monitoring Conditions - Monitoring principle is based on detection of relevant oscillations of downstream sensor signal during regular lambda control. It is necessary to check driving conditions for exceptions where no regular lambda control is possible (fuel cut off). During such periods, and for a certain time afterward, computations of amplitude values and postprocessing is halted so distortion of monitoring information is avoided. See Fig 2.