Tuning Wiki
Browse Audi
Applies to

Check the hardware and software limits stated in this article.

Scope: keep the OEM example separate from the forum car

Audi SSP 920223 documents early 4.0 TFSI MED17.1.1 examples including CEUC in the S6/S7 and CEUA/CGTA in the A8/S8. The separate NefMoto RS6/RS7 thread concerns a reported C7 RS6; it does not establish that every engine, turbo, gearbox or software version shares its maps. Record the engine code, ECU and TCU identities, hardware, fuel, definition and any custom code. Audi SSP 920223, pp. 7–9 and 84; NefMoto: MED17.1.1 RS6 / RS7 Tuning.

Hardware context changes the interpretation

In Audi's documented example, spring force opens the wastegates and vacuum closes them, with N75 controlling both actuators. G31/G447 supply charge-pressure feedback; G71 is the manifold-pressure sensor. The request for torque governs charge-pressure control, and pressure/temperature signals are used to register load. Confirm the fitted mechanism before interpreting wastegate command direction or importing a base-boost procedure. Audi SSP 920223, pp. 58–59 and 84.

Use pressure channels at the same physical location when checking tracking. A charge-pressure reading and manifold pressure are not interchangeable across a partly closed throttle. Keep bank, units, pressure reference and whether the channel is measured or modelled with each logged value.

What the RS6/RS7 follow-ups actually establish

The author initially reports a load/torque ceiling, then identifies a gearbox restriction. A later complaint remains after that stage. Advanced logging leads the discussion to rlxvd as the restrictive contribution. After a protection-related change, the author reports more boost but a new limp condition on longer pulls, and later points to KLDLUL and its axis. This is a sequence of reported findings, not one verified universal fix. First page; follow-ups.

The replies name rlmaxmd_w, rlxvd_w, rlxred_w, rlmxks_w and pressure-derived PVDSRXABS as contributors to investigate around rlmxs_w. They also flag cylinder-specific timing-correction coverage at higher load. Treat all these as software-specific tracing leads; verify the symbols, scaling, selectors and axis contents. The thread's suggested blanket increases, file addresses and numeric torque/boost claims are not adopted here.

Trace the selected limit, then the intervention

The following comparison method is diagnostic guidance inferred from the case, rather than an OEM calibration procedure.

  1. Log driver demand, ECU torque requests/limits, TCU torque requests/limits, selected gear and operating state. A gearbox's reported maximum torque is not a direct measurement of engine output.
  2. Follow requested load and its selected maximum. Capture each available contributing limit at the same timestamps. Identify the restrictive input and its enable conditions rather than assuming the familiar map is active.
  3. Compare pressure request/feedback, throttle request/angle, pre-control and final wastegate command, regulator state and relevant thermal/protection estimates. Distinguish a reduced setpoint from a controller that cannot track its setpoint.
  4. Review fuel pressures, lambda, per-cylinder ignition correction and fault/freeze-frame information through the onset of the problem. Compare a short pull with the sustained-load condition that triggers the complaint.
  5. Before extending a load range, inspect the populated axes and dependent correction maps in the exact software. A change to a headline load request does not establish valid ignition corrections, torque reporting or protections at the new operating points.

A lower selected load can be an intended component-protection action. Establish the physical reason and validate the model against the fitted hardware. Suppressing that contribution without understanding it leaves the protective function unvalidated.

Diagnostic identifiers and RAM logging expose different evidence

VehiCAL's own documentation distinguishes Basic logging of predefined diagnostic identifiers from Advanced full-RAM logging. Its protocol list also distinguishes MED17 communication/application groups and patch requirements. Confirm support and definitions by initialising the exact ECU; owning a logger or selecting a family label does not establish that the required internal variables are available. VehiCAL Basic versus Advanced; supported protocols.

A missing channel is not evidence that a function is inactive. An implausibly fixed pressure or limit deserves a definition, scale and selection-state check before it is treated as a physical ceiling. Retain raw logs and the logger/software version so later comparisons use the same interpretation.

Modified boost pre-control is a different calibration

VehiCAL's VAG 4.0TT MED17 boost patch changes KFDPTAVE/TVLDSTDPW pre-control to engine-speed/boost-setpoint axes with duty-cycle output. The vendor says actuator linearisation and PID feedback remain, and that the new table axes/values require calibration. Therefore the patch does not make the complete boost controller open loop. Identify the installed patch and matching map definitions before comparing a modified file with factory actuator-pressure/flow-based descriptions. VehiCAL 4.0TT MED17 boost patch documentation.

The vendor's stated read/write workflow uses boot/bench and checksum correction. That instruction belongs to this patch; it does not establish the flashing method for every MED17.1.1. Defaults supplied by a patch are not evidence of a validated calibration for an upgraded turbo.

Sources and related pages

Audi SSP 920223 (May 2012) is OEM design/function training material, read on an independent mirror; use current vehicle-specific service information for repair. NefMoto supplies reported case history; VehiCAL documents its own logger and patch. Sources reviewed 16 November 2026. MED17.1.1 hub · MED17 family · separate MED17.1.62 EA855 EVO guide.

Continue the conversation

If this topic interests you, consider joining the following forums. They host material referenced in this article.