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 ME7
Applies to
Bosch ME7
Tool groups
Not recorded in this older revision
Manufacturers
Not recorded in this older revision

Changes from revision 1 to revision 3

Removed text is struck through; added text is highlighted.

What this guide coversThis is the shared starting point for the VAG ME7.1 and ME7.5 material discussed by S4Wiki. Its tuning method applies at the level of concepts: software identification, injector and air-mass calibration, requested lambda, torque/load control and measured validation. The exact functions, maps, limits and supported tools must be established for the software in front of you.Understand the control chainThe pedal contributes to a torque request. The ECU coordinates that request with limits and interventions, calculates a requested cylinder charge or load, and controls the throttle and, on turbocharged applications, boost to provide it. Fueling follows the estimated air charge, selected lambda target and injector model. Ignition timing contributes both to combustion and to fast torque intervention.These systems interact. A MAF correction can change the load used by ignition and torque functions. A torque limit can reduce load even when the boost controller is capable of more. A richer lambda request can be overridden by an even richer component-protection request. Learn which quantity a table represents before changing its values.Prepare the reference setReference or toolPurposeWhat to matchOriginal ECU readRecoverable baseline and identification evidenceECU part number, software identifier, read format and file hashFunktionsrahmen (FR)Function descriptions and signal relationshipsDocument version, application and function variantMap editor and XDF or other definitionLocate tables, axes, scalars and conversionsExact software, file layout, units, scaling and byte orderChecksum softwareCheck and, where supported, correct image-integrity dataSupported image format and software familyLogger and diagnostic toolCompare requests, limits, model outputs and measured resultsECU configuration, channel definitions and operating stateLambda measurementEstablish whether delivered mixture follows the intended targetSensor type, calibration, placement and time alignmentA function description explains a control strategy; it does not supply every address for every binary. A definition supplies addresses and conversions, but a familiar name alone does not prove that its axes or scaling are correct. Retain both sources with the original file.A useful tuning orderEstablish a healthy baseline. Identify the fitted injectors, fuel-pressure arrangement, MAF and housing, pressure sensor, turbo/wastegate system and lambda measurement. Investigate existing faults and unexpected measurements.Make the fuel and air models coherent. Establish the primary injector calibration, latency and minimum usable pulse width, then evaluate the MAF conversion and fuel trims. Keep hardware changes explicit.Understand requested mixture. Follow driver-demand, knock-related and component-protection enrichment into the final lambda request. Observe which path is active during the test.Understand load and torque limits. Trace the pedal request, torque/load conversion and effective load ceiling before altering boost-control response.Evaluate boost control. Compare requested pressure, actual pressure, wastegate command and adaptation. Relate the result to the mechanical system and its attainable airflow.Evaluate ignition and interventions. Review the active timing table, temperature corrections, knock correction and torque intervention together.Repeat across conditions. Check part load as well as high load, different temperatures and ambient pressures, and both transient and steady operation.Keep each change explainableRetain the original image, edited image, definition revision and edit description. Record the expected effect, the signals used to judge it, and the result. Keep a route back to the previous working revision. When a result is unexpected, identify the active request or limit before changing another table.Variant-specific examplesUse Bosch ME7.1 for S4 M-/L-box examples and Bosch ME7.5 for the source’s 1.8T logging and configuration examples. Shared guides deliberately keep their software addresses, stock numbers and hardware layouts in those branches.Source context and adaptationAdapted, paraphrased and reorganised from S4Wiki contributors’ Tuning, revision 5324, under Creative Commons Attribution 4.0 International. This wiki adds scope labels, cross-links and interpretation notes. The cited software observations have not been independently reproduced by this wiki.Source sections: Getting Started, Fueling, Boost, Timing.Identify the softwareS4Wiki introduces the Bosch Funktionsrahmen and matching stock binaries and definitions.Working recordRecord the complete ECU label and software identification.Retain the original read and its checksum in your working notes.Record the definition filename, source revision and represented units.Link each observation to the examined hardware and software.Continue with ME7 reading writing and checksums and ME7 logging and diagnostics.

Sources

Curated reference notes. Applicability follows the cited sources; hardware testing by this wiki is not implied.

S4Wiki: Tuning — source for expanded ME7 references. S4Wiki contributors; Creative Commons Attribution 4.0 International. Paraphrased, expanded and reorganised by Tuning Wiki. Source revision oldid 5324; accessed 2026-11-10.NefMoto Open Source ECU flashing software. NefMoto and project contributors; GPL-3.0. Source revision 9d46721a7cf6; accessed 2026-11-10.S4Wiki: Tuning. S4Wiki contributors; source site states Creative Commons Attribution. Source revision oldid 5324; accessed 2026-11-10.NefMoto Open Source ECU flashing software. NefMoto and project contributors; GPL-3.0. Source revision 9d46721a7cf6; accessed 2026-11-10.

Page organisation changed

FieldRevision 1Revision 3
Page typeTechnical articleTechnical article
SubjectTuningTuning
ParentBosch ME7Bosch ME7
Applies toBosch ME7Bosch ME7.1, Bosch ME7.5
Tool groupsNot recorded in this older revisionNot recorded in this older revision
Vehicle makesNot recorded in this older revisionNot recorded in this older revision

Rendered revisions

Open each version to inspect formatting, tables and photographs.

Revision 1: ME7 getting started

Identify the software

S4Wiki introduces the Bosch Funktionsrahmen and matching stock binaries and definitions.

Working record

  1. Record the complete ECU label and software identification.
  2. Retain the original read and its checksum in your working notes.
  3. Record the definition filename, source revision and represented units.
  4. Link each observation to the examined hardware and software.

Continue with ME7 reading writing and checksums and ME7 logging and diagnostics.

Sources

Curated reference notes. Applicability follows the cited sources; hardware testing by this wiki is not implied.

Revision 3: ME7 getting started

What this guide covers

This is the shared starting point for the VAG ME7.1 and ME7.5 material discussed by S4Wiki. Its tuning method applies at the level of concepts: software identification, injector and air-mass calibration, requested lambda, torque/load control and measured validation. The exact functions, maps, limits and supported tools must be established for the software in front of you.

Understand the control chain

The pedal contributes to a torque request. The ECU coordinates that request with limits and interventions, calculates a requested cylinder charge or load, and controls the throttle and, on turbocharged applications, boost to provide it. Fueling follows the estimated air charge, selected lambda target and injector model. Ignition timing contributes both to combustion and to fast torque intervention.

These systems interact. A MAF correction can change the load used by ignition and torque functions. A torque limit can reduce load even when the boost controller is capable of more. A richer lambda request can be overridden by an even richer component-protection request. Learn which quantity a table represents before changing its values.

Prepare the reference set

Reference or toolPurposeWhat to match
Original ECU readRecoverable baseline and identification evidenceECU part number, software identifier, read format and file hash
Funktionsrahmen (FR)Function descriptions and signal relationshipsDocument version, application and function variant
Map editor and XDF or other definitionLocate tables, axes, scalars and conversionsExact software, file layout, units, scaling and byte order
Checksum softwareCheck and, where supported, correct image-integrity dataSupported image format and software family
Logger and diagnostic toolCompare requests, limits, model outputs and measured resultsECU configuration, channel definitions and operating state
Lambda measurementEstablish whether delivered mixture follows the intended targetSensor type, calibration, placement and time alignment

A function description explains a control strategy; it does not supply every address for every binary. A definition supplies addresses and conversions, but a familiar name alone does not prove that its axes or scaling are correct. Retain both sources with the original file.

A useful tuning order

  1. Establish a healthy baseline. Identify the fitted injectors, fuel-pressure arrangement, MAF and housing, pressure sensor, turbo/wastegate system and lambda measurement. Investigate existing faults and unexpected measurements.
  2. Make the fuel and air models coherent. Establish the primary injector calibration, latency and minimum usable pulse width, then evaluate the MAF conversion and fuel trims. Keep hardware changes explicit.
  3. Understand requested mixture. Follow driver-demand, knock-related and component-protection enrichment into the final lambda request. Observe which path is active during the test.
  4. Understand load and torque limits. Trace the pedal request, torque/load conversion and effective load ceiling before altering boost-control response.
  5. Evaluate boost control. Compare requested pressure, actual pressure, wastegate command and adaptation. Relate the result to the mechanical system and its attainable airflow.
  6. Evaluate ignition and interventions. Review the active timing table, temperature corrections, knock correction and torque intervention together.
  7. Repeat across conditions. Check part load as well as high load, different temperatures and ambient pressures, and both transient and steady operation.

Keep each change explainable

Retain the original image, edited image, definition revision and edit description. Record the expected effect, the signals used to judge it, and the result. Keep a route back to the previous working revision. When a result is unexpected, identify the active request or limit before changing another table.

Variant-specific examples

Use Bosch ME7.1 for S4 M-/L-box examples and Bosch ME7.5 for the source’s 1.8T logging and configuration examples. Shared guides deliberately keep their software addresses, stock numbers and hardware layouts in those branches.

Source context and adaptation

Adapted, paraphrased and reorganised from S4Wiki contributors’ Tuning, revision 5324, under Creative Commons Attribution 4.0 International. This wiki adds scope labels, cross-links and interpretation notes. The cited software observations have not been independently reproduced by this wiki.

Source sections: Getting Started, Fueling, Boost, Timing.

Sources

Curated reference notes. Applicability follows the cited sources; hardware testing by this wiki is not implied.