Tuning Wiki

This is a historical revision. Read the current page or return to its history.

Page organisation in this revision
Page type
Technical article
Subject
Tuning
Parent
Bosch MED17.5
Applies to
Bosch MED17.5
Tool groups
None
Manufacturers
None

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. Check the matching definition and enable conditions. LAMBTS functional description.

What the CCZA thread establishes

In “MED17.5 2.0TSI CCZA always targeting 0.72 lambda…”, the author reports an unchanged rich target despite edits and says a connected oxygen sensor had been disabled in software. Replies supply a software-labelled map list and suggest better logging. One responder retracts a temperature-threshold suggestion after recognising that they had misread the symptom. The author's thanks and a later attachment do not identify a reproduced cause or validated repair.

The thread 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 its title's lambda number is desirable. Do not transfer the posted addresses 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. Do not interpret every resulting boost reduction as 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. Obtain independent temperature evidence at an appropriate location and compare it 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.

Keep the reason for enrichment 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. Identify the component, its supported operating limits and the model assumptions before selecting a calibration change.

Related guides and evidence limits

Injection windows and throttle intervention · Wastegate and boost-control diagnosis · MED17.5 identification.

Bosch's reference is independently mirrored. The NefMoto case remains unresolved. Sources reviewed 17 November 2026.