Why the definition matters
The same ME7 explanation can describe driver demand, permitted cylinder charge, pressure, actuator duty, injector time and ignition as though they were interchangeable. They are different quantities. The Tuning Database ME7 guide is a useful high-level introduction, but several of its map descriptions conflict with Bosch's documented functions. The table below compares the descriptions with a particular Bosch Audi R4-5V turbo 132 kW ME7.1 function description; it is a cross-check, not a definition for every ME7 file.
Map names that deserve a second look
| Identifier | What to check in the documented example | Why the distinction matters |
|---|---|---|
LDRXN | In Bosch's LDRLMX description, an engine-speed-dependent curve supplies a maximum relative cylinder-charge value in the main limit path, with other corrections and limits also involved. | The Tuning Database guide calls it a two-axis requested boost-pressure map in mbar. A relative-load limit is not a gauge-pressure target; raising a number does not command a corresponding number of millibars. |
KFLDIMX | Bosch lists this as the boost-control integral-regulator limit, with engine speed and a requested pressure-related signal as inputs. | It is a controller limit in the cited strategy, not the absolute boost-pressure ceiling described in the guide. Check the actual conversion and control path rather than matching its values numerically to LDRXN. |
KFMIOP | Bosch's MDMAX description uses engine speed and charge to look up optimum engine torque; it participates in the torque model. | The guide labels it minimum injector opening time. It is not the injector pulse-width map in this Bosch example. KFMIRL is the related torque-to-requested-charge lookup, subject to the surrounding corrections and limits. |
KFWDKMSN | Bosch identifies this as the inverse of a throttle-flow relationship in the Audi function sheet. A separate Bosch ME7.3.1H Alfa function sheet explicitly calls it a desired throttle-angle map indexed by normalized airflow and engine speed. | The guide groups it with fuel enrichment. Establish the throttle model and application before editing it; the Alfa description is corroboration of a related function, not evidence of identical calibration or implementation in an Audi. |
KFZW / KFZW2 | Bosch identifies base ignition maps. In the cited function, the strategy for a two-position cam system switches between maps; a continuously variable system uses a correction to KFZW in the described path. | Do not assume every ME7 variant interpolates two maps directly from cam angle, or assign a particular cam position without tracing that software. |
See Bosch functions LDRLMX, LDRPID, MDMAX, MDFUE, FUEDK and ZWGRU in the Audi document. The descriptions are for the cited software and should be checked against the actual file and its function sheet. For the relationships and shared axes in the S4 M-box, see ME7 map axes and torque-model consistency.
Read the unit as well as the label
A percentage of relative charge, a percentage in a torque model and a percentage of actuator duty have different meanings. A boost pressure can be absolute or relative to ambient and can be measured on either side of a throttle. For example, 2,000 mbar absolute with 1,000 mbar ambient is 1,000 mbar gauge; neither pressure is directly interchangeable with a percentage charge or an actuator command. See ME7 torque, load and boost control.
The source guide identifies LAMFA and KFLBTS as lambda-related maps, but its suggested full-load lambda range should not be treated as a universally safe target. Actual fuel, hardware, temperature, component limits, the active request and independently verified mixture all matter. ME7 fueling and MAF calibration explains why more than one request can affect the final target.
Match the definition to the ECU
- Identify the ECU hardware, software number, engine and read type. Confirm that the definition belongs to that exact image, rather than relying on a car model or a similar software suffix.
- Check the table dimensions, stored type, address, axis source, conversion, units and stock values against the matching definition and function description. An automatically labelled map is a starting hypothesis.
- Trace what consumes the value, its operating conditions and its associated limits or shared axes. Compare active signals and logging units with the expected path before changing cells.
- Retain the original image, definition, comparison and a supported recovery plan; checksum validity does not establish that the calibration or the definition is correct.
Vehicle lists also need scope. The Golf Mk4 service data lists AGU as Motronic M3.8.3 and AGN as M3.8.5, although the Tuning Database guide groups both with ME7.5. Bosch's application catalogue also lists AGU and AGN with earlier Motronic families in its stated Audi applications. Use the ECU and software identification for the particular vehicle, especially where engines or controllers have been swapped.
The same part number can have different map locations. In a forum-reported 1.8T ATW case, supplied injector-map locations produced implausible values. The locations were identified as belonging to software revision 0008, while the image in question (4B0906018P) was revision 0006. The case illustrates why a matching hardware part number is not enough: check the full software identity, file layout, table dimensions, byte order, axes and units against the actual image. The community's locations have not been independently verified here.
Related reading
ME7 getting started · ME7 ignition and knock reference · ME7.1 M-box throttle airflow and fallback · ME7 reading, writing and checksums. The Bosch documents and community examples provide reference evidence; this wiki has not independently tested every implementation.