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 MED9.1
Applies to
Bosch MED9.1
Tool groups
None
Manufacturers
Audi, Volkswagen

Changes from revision 1 to revision 1

Removed text is struck through; added text is highlighted.

Scope and starting point

These notes concern the VAG 2.0 FSI Turbo/TFSI examples discussed below. Identify the engine, ECU software, coding and fitted intake-manifold hardware before transferring a definition or interpreting a log. Use the software and definition matching guide and keep the original calibration with the test record.

Check the active map and variant

In the May 2013 NefMoto MED9.1 FAQ discussion, majorahole corrected a misidentified enrichment map while investigating a lambda change that had little effect. B234R's reply described separate open-flap enrichment and coding-dependent map variants; majorahole subsequently reported an improved AFR result. This is a reported case, not a complete definition for every file. The discussion mentions a “115H” file without establishing a unique full software identity for a transferable calibration.

The Bosch MED9.1 function document for 41W038_PQ35, 20 August 2004 independently identifies KFLBTS and KFLBTSLBKO as component-protection lambda maps for closed and open charge-motion flaps. See LAMBTS 19.130.3, pages 2576–2579. It does not prove the number or addresses of coding variants in a later binary.

Volkswagen SSP 337, page 17 describes the AXX tumble flaps as closed at low loads within its illustrated 1000–5000 rpm region. Keep that load qualification: an rpm-only assumption that the flaps remain closed throughout a full-load pull is not supported by this passage. Record commanded and actual flap state where the software exposes them.

Compare the final request before the measured mixture

A LAMFA or KFLBTS cell is not the complete lambda request. Bosch LAMKO 21.50.1, pages 2582–2587 coordinates requests and applies limits; its selection depends on operating state. The July 2015 NefMoto follow-up corrects the idea of a single temperature switch between two maps. Use the discussion as a prompt to trace the actual software, rather than applying a universal “one threshold selects LAMFA or BTS” rule.

ObservationNext check The final requested lambda does not change.Confirm the edited map, axes, selected coding variant, operating state and any active protection request before changing more cells. The request changes but measured lambda does not follow.Compare supply and rail pressure, injection data and fault status using the fuel-pressure guide. Separate request selection from fuel delivery. The result differs with flap state or ignition intervention.Check the corresponding enrichment variant and protection path. Keep ignition timing and correction data with the lambda log. The discrepancy occurs only during a transition.Check time alignment, sample rate and request timing in the exact software. A settled map value cannot explain a transient by itself.

With verified RAM logging, useful research labels in the cited Bosch document include lamfa_w, lambts_w, B_lambts and lamsbg_w. Their addresses and diagnostic availability must be established for the target binary. A log showing only final specified and measured lambda cannot by itself identify which source map was active.

Keep protection calibration evidence

The September 2015 continuation reports disabling enrichment corrections to regain control, followed by a reply arguing for retaining correction under adverse conditions. This is not a validated shortcut. Retain component protection while diagnosing unexpected enrichment; establish the active path and measurement evidence before changing its calibration.

The Bosch application notes, page 2581 relate protection thresholds to temperatures at specified exhaust locations and call for comparison with measured component temperatures. A modeled temperature channel and an aftermarket turbo's advertised temperature rating are not interchangeable evidence for raising a threshold.

Record rpm, load, gear, coolant and intake temperatures, fuel specification, final requested and measured lambda, fuel pressures, ignition intervention and available flap/protection states together. Document which temperature channels are measured or modeled. These are diagnostic working notes, not universal lambda targets, threshold values or a vehicle-tested calibration. Sources accessed 16 November 2026.

Rendered revisions

Open each version to inspect formatting, tables and photographs.

Revision 1: MED9.1 2.0 TFSI lambda requests and map selection

Scope and starting point

These notes concern the VAG 2.0 FSI Turbo/TFSI examples discussed below. Identify the engine, ECU software, coding and fitted intake-manifold hardware before transferring a definition or interpreting a log. Use the software and definition matching guide and keep the original calibration with the test record.

Check the active map and variant

In the May 2013 NefMoto MED9.1 FAQ discussion, majorahole corrected a misidentified enrichment map while investigating a lambda change that had little effect. B234R's reply described separate open-flap enrichment and coding-dependent map variants; majorahole subsequently reported an improved AFR result. This is a reported case, not a complete definition for every file. The discussion mentions a “115H” file without establishing a unique full software identity for a transferable calibration.

The Bosch MED9.1 function document for 41W038_PQ35, 20 August 2004 independently identifies KFLBTS and KFLBTSLBKO as component-protection lambda maps for closed and open charge-motion flaps. See LAMBTS 19.130.3, pages 2576–2579. It does not prove the number or addresses of coding variants in a later binary.

Volkswagen SSP 337, page 17 describes the AXX tumble flaps as closed at low loads within its illustrated 1000–5000 rpm region. Keep that load qualification: an rpm-only assumption that the flaps remain closed throughout a full-load pull is not supported by this passage. Record commanded and actual flap state where the software exposes them.

Compare the final request before the measured mixture

A LAMFA or KFLBTS cell is not the complete lambda request. Bosch LAMKO 21.50.1, pages 2582–2587 coordinates requests and applies limits; its selection depends on operating state. The July 2015 NefMoto follow-up corrects the idea of a single temperature switch between two maps. Use the discussion as a prompt to trace the actual software, rather than applying a universal “one threshold selects LAMFA or BTS” rule.

ObservationNext check
The final requested lambda does not change.Confirm the edited map, axes, selected coding variant, operating state and any active protection request before changing more cells.
The request changes but measured lambda does not follow.Compare supply and rail pressure, injection data and fault status using the fuel-pressure guide. Separate request selection from fuel delivery.
The result differs with flap state or ignition intervention.Check the corresponding enrichment variant and protection path. Keep ignition timing and correction data with the lambda log.
The discrepancy occurs only during a transition.Check time alignment, sample rate and request timing in the exact software. A settled map value cannot explain a transient by itself.

With verified RAM logging, useful research labels in the cited Bosch document include lamfa_w, lambts_w, B_lambts and lamsbg_w. Their addresses and diagnostic availability must be established for the target binary. A log showing only final specified and measured lambda cannot by itself identify which source map was active.

Keep protection calibration evidence

The September 2015 continuation reports disabling enrichment corrections to regain control, followed by a reply arguing for retaining correction under adverse conditions. This is not a validated shortcut. Retain component protection while diagnosing unexpected enrichment; establish the active path and measurement evidence before changing its calibration.

The Bosch application notes, page 2581 relate protection thresholds to temperatures at specified exhaust locations and call for comparison with measured component temperatures. A modeled temperature channel and an aftermarket turbo's advertised temperature rating are not interchangeable evidence for raising a threshold.

Record rpm, load, gear, coolant and intake temperatures, fuel specification, final requested and measured lambda, fuel pressures, ignition intervention and available flap/protection states together. Document which temperature channels are measured or modeled. These are diagnostic working notes, not universal lambda targets, threshold values or a vehicle-tested calibration. Sources accessed 16 November 2026.

Revision 1: MED9.1 2.0 TFSI lambda requests and map selection

Scope and starting point

These notes concern the VAG 2.0 FSI Turbo/TFSI examples discussed below. Identify the engine, ECU software, coding and fitted intake-manifold hardware before transferring a definition or interpreting a log. Use the software and definition matching guide and keep the original calibration with the test record.

Check the active map and variant

In the May 2013 NefMoto MED9.1 FAQ discussion, majorahole corrected a misidentified enrichment map while investigating a lambda change that had little effect. B234R's reply described separate open-flap enrichment and coding-dependent map variants; majorahole subsequently reported an improved AFR result. This is a reported case, not a complete definition for every file. The discussion mentions a “115H” file without establishing a unique full software identity for a transferable calibration.

The Bosch MED9.1 function document for 41W038_PQ35, 20 August 2004 independently identifies KFLBTS and KFLBTSLBKO as component-protection lambda maps for closed and open charge-motion flaps. See LAMBTS 19.130.3, pages 2576–2579. It does not prove the number or addresses of coding variants in a later binary.

Volkswagen SSP 337, page 17 describes the AXX tumble flaps as closed at low loads within its illustrated 1000–5000 rpm region. Keep that load qualification: an rpm-only assumption that the flaps remain closed throughout a full-load pull is not supported by this passage. Record commanded and actual flap state where the software exposes them.

Compare the final request before the measured mixture

A LAMFA or KFLBTS cell is not the complete lambda request. Bosch LAMKO 21.50.1, pages 2582–2587 coordinates requests and applies limits; its selection depends on operating state. The July 2015 NefMoto follow-up corrects the idea of a single temperature switch between two maps. Use the discussion as a prompt to trace the actual software, rather than applying a universal “one threshold selects LAMFA or BTS” rule.

ObservationNext check
The final requested lambda does not change.Confirm the edited map, axes, selected coding variant, operating state and any active protection request before changing more cells.
The request changes but measured lambda does not follow.Compare supply and rail pressure, injection data and fault status using the fuel-pressure guide. Separate request selection from fuel delivery.
The result differs with flap state or ignition intervention.Check the corresponding enrichment variant and protection path. Keep ignition timing and correction data with the lambda log.
The discrepancy occurs only during a transition.Check time alignment, sample rate and request timing in the exact software. A settled map value cannot explain a transient by itself.

With verified RAM logging, useful research labels in the cited Bosch document include lamfa_w, lambts_w, B_lambts and lamsbg_w. Their addresses and diagnostic availability must be established for the target binary. A log showing only final specified and measured lambda cannot by itself identify which source map was active.

Keep protection calibration evidence

The September 2015 continuation reports disabling enrichment corrections to regain control, followed by a reply arguing for retaining correction under adverse conditions. This is not a validated shortcut. Retain component protection while diagnosing unexpected enrichment; establish the active path and measurement evidence before changing its calibration.

The Bosch application notes, page 2581 relate protection thresholds to temperatures at specified exhaust locations and call for comparison with measured component temperatures. A modeled temperature channel and an aftermarket turbo's advertised temperature rating are not interchangeable evidence for raising a threshold.

Record rpm, load, gear, coolant and intake temperatures, fuel specification, final requested and measured lambda, fuel pressures, ignition intervention and available flap/protection states together. Document which temperature channels are measured or modeled. These are diagnostic working notes, not universal lambda targets, threshold values or a vehicle-tested calibration. Sources accessed 16 November 2026.