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 M3.8.3
Applies to
Bosch M3.8.3
Tool groups
None
Manufacturers
Audi, Škoda, Volkswagen

What the sample identifies

TracqiTechnology/MxT supplies an 06A906018CG XDF whose header describes Bosch M3.8.3, Audi A3 1.8T AGU 150 PS and Bosch 0261206518. The repository's companion binary is 262,144 bytes; the XDF describes a 0x40000-byte region. These are properties of the published example, not proof that an arbitrary read is complete or that every ECU with a similar label uses this calibration.

The XDF header does not establish a software ID for the example. Independently, an owner reports a unit with 06A906018CG, Bosch 0261206518 and software 1037352127 in a Motronic research discussion. That is a separate reported combination, not proof of the software version of MxT's sample. Read and match the actual ECU and file identifiers.

What is and is not defined

The XDF contains a table labelled MLHFM, described there as hot-film airflow linearisation, and a constant labelled MLOFS. It does not define complete fuel, boost and ignition map sets. Labels and values are the project's claims and have not been independently validated here; no complete tuning definition should be inferred from this file.

There is a specific inconsistency to resolve: the XDF declares 266 entries on the MLHFM axis and in its data, whereas the project's general README describes a 256-point Motronic MLHFM. Neither statement establishes the correct table length for a given ECU. Treat the definition as an example to investigate, not as verified evidence for either count, its boundaries or its scaling.

Verification before calibration

  1. Match vehicle, ECU hardware, complete software identification and original read to the definition's documented target. Record the exact file and definition revisions.
  2. Verify each proposed map's address, dimensions, data type, axis values, units and conversion independently against reliable information for that software. Compare the resulting values with plausible original behaviour, rather than accepting a label in isolation.
  3. For airflow changes, compare measured sensor response and logged airflow across relevant operating points. Confirm fuel delivery, injectors and measurement equipment before using fuel trims to infer metering errors. Do not assume a corrected MAF curve also corrects every load, fuelling or boost function.
  4. Use a verified definition for any additional map and retain the original and change record. Seek software-specific evidence if map boundaries or roles remain uncertain.

Continue with AGU tuning and diagnosis. Example attribution: TracqiTechnology/MxT, source revision e80501a0000f, Apache-2.0 licence. No vehicle or ECU testing by this wiki is implied.