Tuning Wiki

This is a historical revision. Read the current page or return to its history.

Page organisation in this revision
Page type
Technical article
Subject
Tuning
Parent
Bosch Motronic 7
Applies to
Bosch ME7.1, Bosch ME7.5
Tool groups
None
Manufacturers
None

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

GroupExamplesInterpretation
Driver and operating statePedal, nmot, wdkba, gear, temperaturesShows what was requested and whether the comparison is at a similar operating point.
Loadrlsol_w, rl_w, available limit and intervention signalsCompare requested and calculated relative charge; the LDRXN curve is a ceiling, not a demand that must always be reached.
Pressureplsol_w, pvdks_w, pssol_w, ambient pressureSeparate the upstream boost request and measurement from the manifold request. Establish location, absolute/gauge reference and model effects.
Actuatorldtvm and, where available, the individual regulator contributionsRelate final modulated command to requested and achieved pressure; verify the actuator’s response and duty convention.
CombustionRequested and measured lambda, ignition, cylinder knock correctionShows whether mixture, knock or a torque action accompanies the event.

Follow the first point where the traces diverge

  1. 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.
  2. 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.
  3. 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.
  4. Air follows but delivered torque or timing changes: inspect knock, temperatures and fast torque interventions as well as the active ignition path.

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.