Start with the request that changes
On the VAG ME7.1/ME7.5 examples discussed here, a throttle closure or fall in ignition timing can result from several requests and limits. It is an observation to trace, not a diagnosis of traction control, overboost or a faulty throttle on its own. Identify the software, transmission, tyre and wheel-speed inputs, hardware and current fault state.
Record time, gear, engine speed and its rate of rise, pedal, requested and actual throttle, requested and permitted torque or load where defined, measured load, ignition and individual knock corrections. Add requested and measured pressures with their sensor locations, wastegate command, clutch/brake/traction or transmission status where available, and faults. Retain the time leading up to and after the event.
Fast RPM rise and the rev-limit path
In a forum-reported modified 1.8T case, traction control was first suspected because the symptom appeared in lower gears. Tracing the torque requests, including minmx_w, was suggested. Changing an RPM-prediction setting was later reported to move the apparent intervention to a higher speed, and further changes to other limiter settings followed. That is a reported multi-change result, not proof that every first-gear throttle event is caused by the rev limiter.
For comparison, Bosch's ME7.3.1H Alfa function sheet, NMAXMD, describes a torque-based speed controller that predicts engine speed during a positive RPM gradient. It is a different engine and software: it establishes a possible design pattern, not the exact logic or settings in a VAG image. The ME7Logger M-box torque definition labels minmx_w as a nominal indicated torque for engine-speed limiting. Verify whether a corresponding signal exists and is correctly defined for the actual ECU.
Compare similar operating points in different gears and look at RPM acceleration as well as RPM itself. The speed controller may act before a static displayed limit when speed is rising rapidly, if that strategy is active. This is a reason to inspect the relevant request and enable conditions, not an instruction to disable or raise an engine protection limit.
Anti-judder status is a lead, not a complete diagnosis. Bosch's Audi 132 kW ME7.1 ARMD description distinguishes the active condition B_ar from the torque contribution dmar_w and from steady and transient thresholds. A later forum report described behaviour from a different threshold path than initially expected. Log the active condition, contribution, torque and ignition together with the actual gear and clutch state. See ignition oscillation and anti-judder diagnosis.
Pressure and throttle are measured in different places
A forum-reported 2.7T M-box part-throttle case was complicated by a high wastegate cracking pressure, throttle restriction, pressure difference, altered MAF scaling and multiple calibration changes. A proposed diverter-valve spring change was reported not to solve the initial problem. Smoother behavior was later reported after a diagnostic limit was changed, but that change also affected monitoring and does not prove the underlying pressure and air models were correct. The discussion contains conflicting interpretations; it is not a generic diverter-valve or threshold recipe.
Compare a manifold pressure estimate with the corresponding manifold request, and a pre-throttle pressure sensor with the appropriate pre-throttle request. Pressure can differ across a partially closed throttle. A fault-driven fallback, a falling torque request and a physical pressure-control limitation are different observations. Inspect the first divergence before adjusting another map.
Continue with ME7 boost and load log review, M-box throttle-airflow and fallback and map axes and torque-model consistency. Community outcomes are reports and have not been independently reproduced by this wiki.