Tuning Wiki
Applies to

Check the hardware and software limits stated in this article.

Start with the final request and its source

A lambda table edit that does not alter the observed target leaves several possibilities: the wrong definition, an inactive branch, another coordinated request, or a limit on the result. Establish which signal the logger displays and which request is selected before changing more maps. Separate requested mixture, measured exhaust lambda and learned correction using the fuel and lambda log guide.

Keep the Bosch implementation identified

This example uses the 18 July 2007 EA888 ULEV MED17.5 work-in-progress reference, D175X56H_M08C0;2. Its functions are not established as identical in the CCZA case below.

LAMKO prioritises enabled requests; zlamko identifies the selection but some values are ambiguous. LAMBTS can request enrichment and reduce charge when enrichment capacity is exhausted. Bosch LAMKO 38.40.2, pp. 1589–1590; LAMBTS 19.190.0, pp. 2812–2814.

In that LAMBTS implementation, KFLBTS/KFLBTSLBKO selection depends on charge-motion-flap state; B_lambts accompanies the protection request. The matching definition and enable conditions should be checked. LAMBTS functional description.

The CCZA case: an unresolved rich target

A NefMoto report titled “MED17.5 2.0TSI CCZA always targeting 0.72 lambda…” describes an unchanged rich target despite edits, with a connected oxygen sensor reportedly disabled in software. Replies supplied a software-labelled map list and suggested better logging; one temperature-threshold suggestion was retracted after the symptom had been misread. A later attachment and thanks from the author do not identify a reproduced cause or validated repair.

The case is therefore a source of hypotheses and definition leads. It does not prove that the sensor modification caused the target, that one map controls every high-load condition, or that the lambda number in its title is desirable. The posted addresses should not be transferred to another binary.

A log sequence for request selection

  1. Keep a documented original and the exact change list for the file under test. Record software identity, sensor layout, fuel, fault state, adaptations and any custom code.
  2. Capture the final lambda request beside each available candidate request and its enable flag. Use the exact selector enumeration for that software; an unknown selector value or a missing channel remains unknown.
  3. Compare equivalent warm-up state, rpm, load, gear and thermal history. A requested value may be held or filtered, so record the interval before and after the change in behaviour.
  4. Track protection requests and the relevant exhaust/catalyst temperatures. Mark every temperature as measured or modelled and identify the location represented; a plausible-looking temperature alone does not validate a model.
  5. Review charge/load limiting at the same timestamps. If a protection strategy can no longer obtain its desired mixture, investigate whether another action is reducing engine output. Not every resulting boost reduction is a wastegate calibration error.
  6. Check whether measured mixture follows the final request, allowing for sensor and logging delay. A request-selection problem and a fuel-delivery problem require different evidence even if the displayed lambda is similar.

This sequence is diagnostic reasoning from the distinction between requests, selection and physical response. It is not a factory fault-finding procedure or a prescription to disable an operating branch.

Protect the meaning of the temperature model

Turbo, exhaust, injector, fuel and ignition changes can make a previously validated model require further assessment. Independent temperature evidence should be obtained at an appropriate location and compared with the model through steady and transient conditions. A similar turbo or downpipe does not establish that a donor engine's complete temperature calibration is transferable.

The reason for enrichment should stay visible during validation. Removing a diagnostic, replacing a modelled value or raising a threshold can conceal evidence; none of those actions by itself demonstrates that component temperatures or mixture are acceptable. The component, its supported operating limits and the model assumptions should be identified before a calibration change is selected.

Not established

  • The cause of the CCZA's constant rich target and any validated repair.
  • That the Bosch reference's functions are identical in the CCZA software.

Sources and related pages

Bosch's reference is independently mirrored; the NefMoto CCZA case remains unresolved. Sources reviewed 17 November 2026. Related: Injection windows and throttle intervention · Wastegate and boost-control diagnosis · MED17.5 identification.

Continue the conversation

If this topic interests you, consider joining the following forums. They host material referenced in this article.