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

Scope: the S4 M-box

This article describes the throttle-airflow and backup-load discussion for the Audi S4 2.7T M-box, identified by S4Wiki as 8D0907551M. It is a diagnostic reference, not a recommendation to disconnect the MAF or operate without fault detection. Map names, signal meanings and fallback logic must be checked in the identified ECU software. A separate Bosch ME7.3.1H Alfa function sheet uses some of the same signal names, but does not establish identical M-box logic.

Two ways of describing incoming air

The MAF path measures air passing the hot-film sensor. The throttle path estimates flow using throttle position and the applicable air-path model. The M-box source calls the latter alpha-N and describes it as a fallback if the primary MAF signal is unavailable. The two paths are not two independent physical flow meters.

Example signalWhat to check
mshfm_wMAF-derived mass flow and its conversion; establish units in the logger.
msdk_wThrottle-path airflow estimate; interpret with the model and its learned state.
wdkba, engine speedThrottle and RPM conditions at the same time as the airflow signals.
pvdks_w, pus_wPre-throttle and ambient pressure in the cited logger definitions, with their correct units.

Compare like units and reasonably stable operating points first. Transients, sampling or filtering differences, purge or other air paths, leaks, MAF conversion and throttle-model calibration can all affect the relationship. A mismatch is a reason to investigate these possibilities; its shape alone does not prove one particular map is wrong. Record fault codes and adaptations before resetting anything. ME7Logger alias list; Bosch ME7.3.1H Alfa function sheet, BGMSZS and EGFE signal descriptions.

WDKUGDN and throttle flow

For the M-box, S4Wiki describes WDKUGDN as a speed-dependent angle at the transition into an effectively unthrottled range. Its reported pressure-ratio threshold of 0.95 is specific to that documented implementation. KFMSNWDK and KFWDKMSN have separate roles in the throttle-flow relationships; check the function and axis definitions for the actual image before treating a curve as a correction.

Do not confuse this M-box transition with sonic choked flow. The MxT ME7 guide calls WDKUGDN a choke point, while the M-box reference distinguishes the two. NASA describes choked flow as the condition in which flow through a restriction reaches Mach 1 at its smallest area. The physical terms and the ECU’s transition should be evaluated separately. S4Wiki Alpha-N, revision 5321; NASA Glenn: mass-flow choking.

The Tuning Database ME7 guide groups KFWDKMSN with fuel enrichment. Bosch's Audi 132 kW ME7.1 function sheet instead describes it as the inverse of a throttle-flow map, and a separate ME7.3.1H Alfa sheet labels it a desired throttle-angle map. These are related reference examples, not an independent verification of the complete M-box implementation. See ME7 map names and definition checks.

What the pressure-ratio curve represents. A NefMoto discussion asks whether KLAF needs a new shape for a larger throttle or turbo. In the separate Audi 132 kW ME7.1 BGMSZS description, KLAF is a normalised flow characteristic addressed by downstream-to-upstream throttle pressure ratio; opening area, upstream pressure and temperature have their own roles. That document describes a sonic-flow region below about 0.528 and a distinct near-unthrottled transition at about 0.95. These refer to different phenomena in that application. Identify the function and pressure locations before treating a physically derived curve as a hardware-size multiplier; check the exact ECU rather than copying this example's values.

How a target angle is calculated: a separate 1.8T example

The translated Bosch Audi transverse 132 kW 1.8T ME7.1 function description, FUEDK 21.90, describes a target-angle path tied to the intake-manifold charge model. It starts with requested cylinder charge and charge-control correction, estimates the required manifold pressure and throttle airflow, and accounts for pressure and temperature before converting the normalised flow request into an angle. Purge flow and the learned throttle air-bleed offset also enter the documented calculation. This is a different engine and software reference; it does not independently prove identical M-box implementation.

In that function, KFWDKMSN supplies a target-angle relationship matched to the installed throttle and is described as the inverse of the throttle-flow map KFMSNWDK. The related relationships, their axes and normalisation must remain coherent when investigating a different body; reversing a table's values without accounting for axes, interpolation and operating range is not a calibration method. Beyond the unthrottled transition the documented logic handles the remaining angle range separately, and KFWDKSMX can limit the target. Confirm the active functions and definitions for the ECU being tested.

FUEDK also describes median filtering of the normalised target flow during small requested-charge changes and a different path for larger changes. Therefore a difference between logged pedal movement and throttle response may reflect the request, operating state, limit or filtering as well as hardware. Compare the defined target and actual throttle angles, requested charge, pressure signals and relevant state at sufficient sample rate before attributing the difference to one map. This function description does not establish that a particular throttle conversion is safe or correctly calibrated.

Basic settings and fault response: Audi 2.7T example

Audi's Self-study Programme 198 describes the 2.7-litre biturbo with ME7.1, but does not identify the S4 M-box software number. For that engine family it explains that basic setting moves the throttle to predefined positions, stores and checks the two angle-sender readings, and evaluates the response of the mechanical assembly. It can be cancelled when test conditions are not met. This describes a position and mechanism check, not proof that the airflow model matches a replacement throttle.

For its listed VW/Audi petrol examples, Ross-Tech's alignment guide specifies no engine fault codes, at least 11.5 V battery voltage, a clean throttle at idle with the accelerator released, and coolant between 5 °C and 95 °C. It advises cycling ignition after clearing faults. Use the specific vehicle workshop procedure, diagnostic protocol and conditions rather than assuming these limits apply to every ME7 system.

SSP 198 also distinguishes fault responses: a single implausible throttle-angle sender can permit a restricted emergency mode if the other signal and airflow are plausible; loss of drive places the plate at its spring position; uncertainty about the plate position leads to a more restrictive mode. Record faults and investigate wiring, supply, both sensor signals and mechanics before attributing a problem to a map. Those responses are documented for the programme's vehicle, not a universal promise for every application.

Selecting a different electronic throttle body

Diameter alone does not establish interchangeability. The Bosch Motorsport electronic throttle data sheet lists bodies from 32 to 82 mm, including a 52 mm F02U.V01.184-02 and an 82 mm 0280.750.101. These examples demonstrate the range of hardware available; the sheet does not establish that either is a compatible M-box or other ME7 replacement.

Identify both original and proposed part numbers, mounting and sealing, plate movement and spring rest position. Check the exact connector and pin functions, sensor supply and both feedback tracks across travel, motor wiring and electrical characteristics against the ECU's requirements. Even a matching plug or successful adaptation does not prove electrical, control or airflow-model compatibility. A different effective opening area can also change the relationship between angle and airflow; investigate the matched software's throttle model rather than applying a generic bore-area multiplier.

Example of why a shared connector is not enough. Bosch Motorsport's 2017 catalogue, pages 182–184, lists a 50 mm body 0 280 Y05 107-10 and a 52 mm body F 02U V01 184-01 with the same listed connector and 58 mm flange diameter. Yet its table assigns pin 1 to potentiometer 2 on the 50 mm unit and potentiometer 1 on the 52 mm unit; pin 3 is motor positive on the 50 mm and motor negative on the 52 mm. The catalogue also gives opposite opening directions. These are specific motorsport catalogue examples, not verified M-box replacement parts or a wiring instruction. Check the current exact-part documentation and connector orientation before comparing any terminals; a similar plug and flange do not establish compatibility.

After a supported replacement, use the applicable vehicle procedure to perform and verify throttle basic settings. Ross-Tech's alignment guide gives group 060 for its listed VW/Audi drive-by-wire examples, with different steps for KW-1281 and KWP-2000/CAN, and identifies prerequisites. Confirm the protocol, fault status and procedure for the particular car; completing alignment learns positions and does not validate an unproven conversion.

Check the function, not the abbreviation

MxT describes FUEREG as fuel adaptation in this discussion. The M-box reference instead identifies it as charge control, and Bosch’s separate ME7.3.1H Alfa sheet also describes a charge controller. Neither is evidence that a WDKUGDN change simply switches closed-loop lambda control off. Determine the actual flags and functions in the ECU being investigated; do not reset learned values or change a transition curve merely to hide a part-throttle airflow difference.

For a heavily modified M-box example involving high wastegate cracking pressure and disputed part-throttle behavior, see ME7 torque intervention during rapid acceleration. That case illustrates why measured pre-throttle pressure, modelled manifold pressure, their requests and fault-driven interventions need separate interpretation.

Sources and attribution

Based on S4Wiki contributors’ Alpha-N, revision 5321, Creative Commons Attribution 4.0; adapted, reorganised and qualified by Tuning Wiki. M-box software behaviour is reported by that source and has not been independently reproduced here. Additional tool context comes from TracqiTechnology/MxT contributors’ ME7 Calibration Guide, rewritten for this page; Apache License 2.0, full text. The Bosch function sheet cited above is for a different ME7.3.1H Alfa application.

Related: ME7 fueling and MAF calibration · ME7 torque, load and boost control · Adaptations and calibration drift.