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

Changes from revision 6 to revision 12

Removed text is struck through; added text is highlighted.

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.

A zero is also a state-dependent signal. In the Bosch Audi ME7.1 LDRPID description, lde is forced to zero when B_ldr is inactive. Check that boost regulation is active before treating a zero deviation as accurate tracking. ME7 boost adaptation and integral limits separates the learned correction, current limit, integral output and final duty.

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 forum-reported 1.8T TT case describes intermittent N75 operation with no stored fault, despite ECU and wiring checks. The problem reportedly stopped after the accelerator pedal was substituted; 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.Connect the duty trace to the hardware. Forum discussion of external-wastegate control compares lower-port and dual-port strategies. A duty percentage alone does not identify which way the particular valve moves or whether the actuator follows it. Check the pressure source, solenoid ports and normal state, wastegate configuration, spring and chamber pressures. See ME7 wastegate and boost-control hardware.Check hardware when a plot suggests intervention. In a forum-reported modified 1.8T case, throttle intervention was initially suspected but the fault was later reported as a collapsed turbo-inlet hose, and fixing it resolved the symptom. In a separate BFB 1.8T case, model-related changes brought calculated manifold and measured pre-throttle pressure closer, but drivability symptoms were still reported and the cause remained disputed. Neither trace is a unique diagnosis. Check actual pedal and throttle, pressure locations, airflow, faults and operating state; see inlet restriction and charge-air leak diagnosis.Separate an overboost event from the response to itVolkswagen's Self-Study Programme 231, pages 18 and 30, lists charge-pressure limit diagnosis for its cited ME7.1, ME7.5 and ME7.5.10 applications and illustrates a protective response when maximum permitted pressure is exceeded. The illustrated system detects excess pressure using a pressure sender and responds by opening the wastegate to bypass exhaust flow. The description is a functional overview, not a universal threshold, timer, or guarantee that a defective actuator will move when commanded.For a log showing a spike followed by reduced boost, retain the period before the spike, the pressure sensor and request at matching locations, the control command and any available fault or protection state. A lower pressure after a spike may be a response to the event rather than its original cause. Investigate the sensor, pressure plumbing, solenoid, wastegate movement and control calibration using the specific vehicle's procedure; raising a diagnostic limit does not fix the underlying overshoot.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.

On a modified pressure-scaling implementation, check whether the logger already converts each channel to physical pressure before comparing it with a gauge or local ambient pressure. The ME7 5120 pressure-scaling guide explains an illustrative conversion and the distinction between sensor range and ECU representation.

When the event is concentrated in a low gear or rapid RPM rise, inspect the torque-request and engine-speed-limiting paths as well as boost and traction status. The rapid-acceleration intervention guide describes a reported 1.8T case and a separate Bosch function example.

For an implausible pressure channel, see pressure-sensor scaling and validation. For changes between hot and cold runs, see intake temperature and boost interpretation.

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.

Rendered revisions

Open each version to inspect formatting, tables and photographs.

Revision 6: ME7 boost and load log review

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.

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.

On a modified pressure-scaling implementation, check whether the logger already converts each channel to physical pressure before comparing it with a gauge or local ambient pressure. The ME7 5120 pressure-scaling guide explains an illustrative conversion and the distinction between sensor range and ECU representation.

When the event is concentrated in a low gear or rapid RPM rise, inspect the torque-request and engine-speed-limiting paths as well as boost and traction status. The rapid-acceleration intervention guide describes a reported 1.8T case and a separate Bosch function example.

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.

Revision 12: ME7 boost and load log review

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.

A zero is also a state-dependent signal. In the Bosch Audi ME7.1 LDRPID description, lde is forced to zero when B_ldr is inactive. Check that boost regulation is active before treating a zero deviation as accurate tracking. ME7 boost adaptation and integral limits separates the learned correction, current limit, integral output and final duty.

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.

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 forum-reported 1.8T TT case describes intermittent N75 operation with no stored fault, despite ECU and wiring checks. The problem reportedly stopped after the accelerator pedal was substituted; 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.

Connect the duty trace to the hardware. Forum discussion of external-wastegate control compares lower-port and dual-port strategies. A duty percentage alone does not identify which way the particular valve moves or whether the actuator follows it. Check the pressure source, solenoid ports and normal state, wastegate configuration, spring and chamber pressures. See ME7 wastegate and boost-control hardware.

Check hardware when a plot suggests intervention. In a forum-reported modified 1.8T case, throttle intervention was initially suspected but the fault was later reported as a collapsed turbo-inlet hose, and fixing it resolved the symptom. In a separate BFB 1.8T case, model-related changes brought calculated manifold and measured pre-throttle pressure closer, but drivability symptoms were still reported and the cause remained disputed. Neither trace is a unique diagnosis. Check actual pedal and throttle, pressure locations, airflow, faults and operating state; see inlet restriction and charge-air leak diagnosis.

Separate an overboost event from the response to it

Volkswagen's Self-Study Programme 231, pages 18 and 30, lists charge-pressure limit diagnosis for its cited ME7.1, ME7.5 and ME7.5.10 applications and illustrates a protective response when maximum permitted pressure is exceeded. The illustrated system detects excess pressure using a pressure sender and responds by opening the wastegate to bypass exhaust flow. The description is a functional overview, not a universal threshold, timer, or guarantee that a defective actuator will move when commanded.

For a log showing a spike followed by reduced boost, retain the period before the spike, the pressure sensor and request at matching locations, the control command and any available fault or protection state. A lower pressure after a spike may be a response to the event rather than its original cause. Investigate the sensor, pressure plumbing, solenoid, wastegate movement and control calibration using the specific vehicle's procedure; raising a diagnostic limit does not fix the underlying overshoot.

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.

On a modified pressure-scaling implementation, check whether the logger already converts each channel to physical pressure before comparing it with a gauge or local ambient pressure. The ME7 5120 pressure-scaling guide explains an illustrative conversion and the distinction between sensor range and ECU representation.

When the event is concentrated in a low gear or rapid RPM rise, inspect the torque-request and engine-speed-limiting paths as well as boost and traction status. The rapid-acceleration intervention guide describes a reported 1.8T case and a separate Bosch function example.

For an implausible pressure channel, see pressure-sensor scaling and validation. For changes between hot and cold runs, see intake temperature and boost interpretation.

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.