A lean-looking trace does not identify the cause
An oxygen sensor interprets residual oxygen in exhaust gas. If combustion misfires, an unburned charge can reach the exhaust and make an oxygen-based reading appear lean even when lack of fuel was not the original cause. A leak upstream of the sensor can also distort the reading. Walker Products' oxygen-sensor guide describes both effects; Bosch's sensor overview explains the oxygen-sensing principle.
The converse is also possible: genuinely insufficient fuel or air-metering errors can cause a lean mixture and a misfire. A lambda spike alone cannot determine which came first, and a single bank sensor cannot prove that every cylinder is receiving the same mixture.
A reported ME7.5 example
In a Golf 1.8T ME7.5 discussion, an owner described a high-load hesitation with intermittent rich/lean readings. A contributor suggested looking for coincident misfires; the owner later reported improved behaviour after changing the spark-plug gap. That does not prove the original cause or establish a suitable gap for another engine. The same discussion initially raised concern about an uneven RPM trace before participants identified a logger timestamp/plotting issue; they discussed a software update to read the older timestamp format.
Check the order of events and the measurement
- Record fault codes and counters, the affected bank or cylinders, operating conditions, sensor type, sensor location and the history of hardware changes.
- Compare requested and measured lambda with RPM, load, pedal, throttle, ignition correction, injector command and cylinder misfire information where supported. Include fuel pressure if available. A bank-average lambda trace can conceal cylinder-to-cylinder differences.
- Investigate ignition, injector operation, compression and air or exhaust leaks using the vehicle's service procedures. Inspect supply pressure and electrical conditions when the event is under load.
- Confirm time ordering, sample rate, channel units and logger version. Exhaust transport, sensor/controller response, filtering and asynchronous logging can shift an apparent relationship; a rapidly alternating trace may not represent individual combustion events accurately.
- After a specific repair or calibration change, repeat the same conditions and check faults, mixture and driveability. Avoid adding fuel or changing a lambda map solely to hide an unverified sensor spike.
A Bosch diagnostic article recommends comparing scan data with exhaust-gas analysis when investigating a lambda complaint. A suitable gas analyser and other independent measurements can help distinguish oxygen, hydrocarbons and mixture behaviour, but must be interpreted at the sampling location and operating state.
See ME7 MAF and lambda log review, lambda control state during boost, cold start and throttle-transition fueling, and ME7 logging and diagnostics. The forum case is a reported observation, not an independently reproduced repair.