Application and starting point
Volkswagen's SSP 337, pages 6 and 20–21 identifies MED9.1 on the AXX 2.0 FSI Turbo: a four-cylinder, four-valve-per-cylinder engine with airflow meter G70, charge-pressure sender G31, boost-control solenoid N75 and direct injection. These are AXX example details, not a complete list of MED9 hardware. Identify the engine, vehicle, hardware and software before selecting definitions; the MED9.1 software matching guide explains what to record.
Save and verify the original read, establish the vehicle's fault status and mechanical condition, and log a repeatable baseline before changing calibration. Keep fuel type, intake and coolant temperatures, gear and ambient conditions with the run. Use suitable load and speed conditions for the vehicle and test environment.
Follow the request through the model
The following names and roles are taken from Aliant Auto's published MED9.1 SEAT Leon Cupra example. They are signposts for finding and checking functions, not a universal map list. The guide's title says “20V”; VW identifies its AXX 2.0 FSI Turbo example as four valves per cylinder. Verify vehicle details, axes, variants, units and actual control logic for the exact software.
| Map labels in the example | Role to investigate | Useful check |
|---|---|---|
| KFPED | Driver torque request from pedal position and engine speed. | More pedal sensitivity is not the same as more available torque. |
| KFMIRL and KFMIOP | Requested torque to load and the related load-to-torque model. | Check that the paired models, axes and limiters remain consistent over the used range. |
| LDRXN | One engine-load ceiling in the example. | A request above a limit can be clipped; other limits and interventions may also apply. |
| KFLDIMX and KFLDRL | Boost-control integral limit and duty linearisation. | Compare requested and actual pressure and actuator behaviour; do not assume a controller setting is the cause of a leak or mechanical fault. |
| LAMFA and KFLBTS | Example lambda request and component-protection enrichment functions. | Identify which function and operating state are active when comparing target and measured lambda. |
| KFZW and KFZWOP families | Ignition maps and an optimum-timing reference used by the model. | Distinguish actual spark control from the model reference; verify timing and knock data in logs. |
As a conceptual example, if a torque-to-load request were 160% and an applicable load ceiling were 140%, that ceiling could cap the request at 140% at that operating point. These are illustrative numbers, not recommended values; the real outcome depends on all active limits, model scaling and operating conditions.
Log and interpret the result
- Compare pedal and throttle, requested and actual load and boost, engine speed, airflow, intake temperature, and available torque intervention or limit flags. Confirm whether pressure is absolute or gauge and use consistent units.
- Log requested and actual lambda, high-pressure rail request and actual, low-pressure supply where available, ignition timing and per-cylinder knock correction or misfires. A repeatable pressure or mixture error needs diagnosis before further load is added. See MED9.1 fuel-pressure and logging checks.
- Change only verified functions in measured steps. Recheck part load as well as the area changed, and retain each version and its log. Validate required checksums with a tool supported for the exact ECU before writing. Keep thermal, knock and other protective strategies operational; a missing intervention in a short log is not proof of a safe calibration.
SSP 337 describes homogeneous operation for the AXX and a separate cold-start catalyst-heating strategy; record operating state when interpreting lambda. Sources describe particular implementations and have not been vehicle-tested by this wiki.