Scope and evidence
This guide concerns excessive boost and throttle closure on a MED17.5 car after a turbo/actuator change, as reported in a NefMoto “med17.5 WG tuning” case and its second-page follow-ups. The public case does not establish a complete hardware/software identity or a transferable calibration, and its map names are search leads to verify in the exact definition and software.
An early suggestion involved a throttle-flow coefficient and drew on a MED9 naturally aspirated-to-supercharged conversion. Later replies challenged that transfer and distinguished throttle modelling from wastegate setup. Reducing a throttle-flow coefficient does not establish that the turbo's overboost has been corrected.
Map pointers for MED17.5 boost control
| Area | Names reported | Question to resolve in the matching definition |
|---|---|---|
| Base boost | KFPLGU, KFDPLGU | Does the calibration represent the fitted actuator's base-pressure behaviour? |
| Wastegate flow and linearisation | KFWG1, KFTVPWG1Q, FAKWG | How does the factory model represent the new turbo and actuator? |
| Alternative pre-control path | KFWGTV, CWAWGTV | Which path is enabled, and what are its actual axes, units and output? |
| Feedback | KFPWG, KFIWG | What error and control state feed the proportional and integral terms? |
These names are forum-reported pointers, not verified universal MED17 symbols. No address, factor, codeword setting or tuned value is established here. The case author reported success after the revised advice, while another participant reported a similar symptom despite changing feedback maps; neither supplies a general validation dataset. Follow-ups, replies 15–20.
Separate three kinds of problem
The following is a practical investigation framework, rather than a repair proven by the forum case.
| Observation | Next comparison |
|---|---|
| The specified load or pressure falls before actual boost falls. | Trace torque requests, selected load/pressure limits and operating/protection state before changing controller gains. |
| Actual pressure exceeds its request while throttle closes. | Check the physical actuator response, command convention, base boost and pre-control/model outputs. Throttle closure alone does not identify which upstream error caused it. |
| Pressure oscillates around a stable request. | Separate pre-control error from feedback corrections, saturation, adaptation and mechanical response using time-aligned signals. |
Confirm hose routing, actuator type, adjustment and travel against the fitted turbo's instructions. Establish what the logger's wastegate command means physically. An editor label such as “WG position” or a displayed zero is insufficient evidence of valve position or duty polarity, and an ambiguous instruction should not be turned into a full-load test.
Log engine speed, pedal, gear, throttle request/angle, requested and actual pressure at the same location, ambient pressure, load request/actual/limit, available wastegate pre-control and final command, regulator state, lambda, fuel pressure, ignition correction and temperatures. Record the turbo/actuator details, software identity and any installed code patch. A requested wastegate position is not a measured position unless a fitted sensor and the channel definition establish that.
Validate beyond the pull that looked better
Check warm steady operation, spool, pedal transitions, light load/cruise, shifts and sustained load in controlled conditions. Confirm both pressure tracking and the intended torque response. Keep protections active and investigate why they intervene; a change that suppresses throttle closure or a fault without correcting the underlying behaviour is incomplete.
A pneumatic-actuator setup should not be transferred to an electric wastegate, and another MED17 variant should not be assumed to have the same control direction. For a different documented mechanism, see the MED17.1.1 4.0 TFSI example.
Not established
- The complete hardware and software identity of the reported car.
- Verified addresses, factors, codeword settings or tuned values for the listed maps.
- A general validation dataset for the reported fix.
Sources and related pages
NefMoto discussions reviewed through the available follow-ups on 16 November 2026. Forum conclusions remain reported cases. See MED17.5, the family reference and the separately scoped MED17.5.21 altitude case.
Related control-path checks: injection windows and throttle intervention, lambda requests and component protection, and torque reporting and DSG shift diagnosis. These guides keep the later forum corrections and the manufacturer implementation scope explicit.
For turbo options and their installation requirements on selected EA888 2.0 TSI/TFSI engines, see EA888 Gen 1 and Gen 2 turbo upgrades and K04 conversions.
For selected Gen 1/2 intercoolers and charge-pipe installation notes, see the EA113 and EA888 intercooler comparison. Check for leaks after changing any charge-air component.
For selected EA888 Gen 1/2 intake and turbo-inlet systems, see the intake comparison. Confirm the upstream pipework and sensor arrangement when diagnosing a changed system.