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
Volkswagen

Scope and the event to investigate

This guide concerns VAG 2.0 FSI/TFSI MED9.1 engine management paired with the six-speed wet-clutch 02E/DSG family. Record the engine ECU and TCU hardware/software, gearbox code, coding, fitted clutch hardware and calibration provenance. Keep engine and gearbox faults with the log. A hesitation can have several causes; identify the intervention before changing a limiter.

MDNORM and the meaning of reported torque

For program 41W038_PQ35, 20 August 2004, Bosch MDRWS, page 337, defines MDNORM as an indicated-torque normalisation reference. The CANECU signal table, page 4049, describes torque quantities relative to that reference. Label every logged torque with its signal definition, units and reference; an engine-model percentage, indicated torque, clutch torque and measured wheel torque are different quantities.

Volkswagen SSP 308, printed page 51, identifies current engine torque as a basis for calculating clutch pressure in its 02E example. Calibration implication: altering torque reporting can alter a control input used by the gearbox. An apparently improved acceleration trace does not establish correct clutch control or a validated hardware torque capacity.

What the 2019 discussion establishes

The Golf 6 R “DSG Fix limiter” thread contains a proposal to lower MDNORM, followed by disagreement about torque reporting, clutch-pressure feed-forward, adaptation and which TCU limits apply. prj's reply and jochen_145's later explanation argue against corrupting the torque supplied to the gearbox; gman86 reports satisfactory experience in a narrower tuning context.

The thread supplies neither a universal DSG limiter value nor matched engine/TCU logs and endurance evidence validating an MDNORM shortcut for another vehicle. Equally, its warnings do not prove that every such modification causes immediate slip. Use the manufacturer-described torque/pressure relationship to define what to measure, and verify the actual software paths before selecting a change.

Capture engine and gearbox behaviour together

Observed behaviourEvidence to obtain
Engine torque appears capped while air/load continues to rise.Check normalisation, output range and the exact reported-torque signal. A flat computed value is not independent evidence of a mechanical torque plateau.
Permitted torque falls during a shift or at a particular temperature.Capture the TCU request, selected/target gear, shift state and temperature with the engine response. Establish whether the request is a normal phase of control, protection or an unexpected constraint.
Engine and selected gearbox-shaft speeds separate.Compare the separation with clutch state, requested slip and pressure where supported. Judge a steady loaded condition separately from an intentional clutch handover or launch.
Throttle closes or ignition is retarded without a demonstrated TCU request.Check engine limits, traction intervention, mixture/fuel pressure and faults using the torque, boost and ignition guide. The shape of the boost trace alone does not identify the source.

Use timestamped captures with enough sampling rate for the event. Record pedal, rpm, load, boost request/actual, throttle, ignition/intervention, lambda and fuel pressure alongside available gearbox torque requests, gear/clutch states, shaft speeds, pressure and temperatures. If only separate module recordings are available, document their timing limits; do not claim a causal sequence that the samples cannot resolve. Diagnostic channel assignments depend on the software and logger.

KFMIOPS does not identify DSG Sport mode

The April 2013 FAQ exchange guesses that the “S” maps might be for DSG Sport; a later reply suggests stratified operation instead. In the cited Bosch implementation, MDBAS, page 736, explicitly identifies KFMIOPS with stratified operation. That name is not evidence of a transmission-mode selector. Trace the selected map and operating mode in the actual binary; the presence of a map does not prove that its branch is used on the fitted engine.

The workflow above is editorial diagnostic reasoning, not a prescribed TCU limit, clutch pressure or MDNORM value. Preserve meaningful torque reporting and protection while investigating; validate any eventual engine/TCU calibration as a matched system. Manufacturer training material describes its original implementation, and the cited forum reports were not reproduced by this wiki. Sources reviewed 16 November 2026.

A translated map name and a separate S3 report

In a 2020 Audi S3 8P discussion, the owner initially interpreted the German term associated with KFMIOPS as a gearbox shift function. A reply corrected the translation to stratified operation, consistent with the Bosch implementation cited above; the reply's further assertion that the map is unused on all TFSI cars is not established by that label alone.

The owner later reports reduced wide-open-throttle shift jerks after several calibration changes, including an initial configuration that coincided with a new 1–2 thud, and asks about long-term gearbox effects. There are no independently reviewed matched engine/TCU traces or durability results. The account does not identify a single proven cause or establish a safe limiter value. Compare defined engine torque, gearbox request, shaft speeds and clutch state before attributing a shift symptom to one map.