Start with the operating state
These examples use signal names from the ME7Logger alias list and the MxT ME7 guide for supported VAG ME7 applications. Match each signal, scaling and unit to the exact ECU software and logger definition. A shared name does not prove identical behaviour across every ME7 variant.
Record the file and definition versions, engine hardware, fuel, fault and adaptation state, ambient conditions, gear and test conditions. Include enough time before and after the event to distinguish a transient from a settled result. Compare repeatable runs at similar conditions before attributing a change to calibration.
Signals that explain the chain
| Group | Examples | Interpretation |
|---|---|---|
| Driver and operating state | Pedal, nmot, wdkba, gear, temperatures | Shows what was requested and whether the comparison is at a similar operating point. |
| Load | rlsol_w, rl_w, available limit and intervention signals | Compare requested and calculated relative charge; the LDRXN curve is a ceiling, not a demand that must always be reached. |
| Pressure | plsol_w, pvdks_w, pssol_w, ambient pressure | Separate the upstream boost request and measurement from the manifold request. Establish location, absolute/gauge reference and model effects. |
| Actuator | ldtvm and, where available, the individual regulator contributions | Relate final modulated command to requested and achieved pressure; verify the actuator’s response and duty convention. |
| Combustion | Requested and measured lambda, ignition, cylinder knock correction | Shows whether mixture, knock or a torque action accompanies the event. |
Follow the first point where the traces diverge
- Request falls: inspect available torque, load, temperature and diagnostic limits. A lower request can be intentional; a ceiling that is not reached is not by itself proof of intervention.
- Request remains but comparable pressure does not follow: examine leaks, supply and actuator behaviour, turbine capability, boost-control state and transient response. A high or low duty value alone does not identify the faulty component.
- Pressure is plausible but charge differs: check sensor range, air metering, temperature, cam state and the pressure-to-charge model. A load error alone does not prove that a particular model table should be rescaled.
- Air follows but delivered torque or timing changes: inspect knock, temperatures and fast torque interventions as well as the active ignition path.
Read an optimiser suggestion as a hypothesis. At the reviewed revision, the MxT guide describes selecting wide-open-throttle samples where pssol_w and pvdks_w are close, grouping the final ldtvm command by RPM, and using those samples to suggest KFLDRL and KFLDIMX values. It then uses requested-versus-actual load for a KFPBRK suggestion. The same guide elsewhere identifies pvdks_w as pre-throttle, so first establish whether the pressure comparison represents the same location and state.
Final wastegate duty contains the effects of the active regulator and its limits; it is not automatically the same quantity as a post-regulator linearisation table entry. An average or a ratio can show where to investigate, but does not independently identify the cause or validate a complete table. Review the input samples, map axes and the specific control strategy before relying on a proposed value. MxT ME7 Calibration Guide, Optimizer; ME7 torque, load and boost control.
For a source-scoped example of a settled boost trace differing from spool response, including changes in cam state and test conditions, see ME7 boost control: comparing spool and steady state.
A reported fault without a code. A 1.8T TT discussion describes intermittent N75 operation with no stored fault, despite ECU and wiring checks. The contributor later reported that the problem stopped after substituting the accelerator pedal; no final diagnostic log or confirmed failure mechanism was supplied. If a similar symptom occurs, include pedal plausibility and its wiring in the diagnostic process, using the vehicle-specific procedure. This single report does not justify replacing a pedal without testing it.
Recognise a range limit
A flat trace may indicate sensor, signal conversion, internal representation or logger clipping; it can also reflect a real plateau. Compare the raw signal where available with the sensor specification, calibration, fault status and operating conditions. MxT flags possible saturation, but the largest value observed in a log does not by itself identify the installed pressure sensor. Replacing a sensor alone does not establish that its conversion, internal range, definitions and protection functions are suitable for the new range.
Sources and related pages
Adapted and expanded from TracqiTechnology/MxT contributors’ ME7 Calibration Guide and ME7 tuning harness; Apache License 2.0, full text. Signal names are cross-checked against the ME7Logger alias list. The workflow adds the pressure-location and interpretation qualifications explained in ME7 torque, load and boost control. See also ME7 ignition and knock reference and logging a drivability complaint.