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
Switchable maps
Parent
Bosch Motronic 7
Applies to
Bosch ME7.1, Bosch ME7.5, Bosch ME7.1.1
Tool groups
None
Manufacturers
None

Bosch Motronic ME7 is a family of petrol engine controllers, not one binary layout. A driver-selectable tune can be implemented with external hardware that selects an entire flash image or with software that selects a defined collection of calibration values. The method, vehicle controls, selected tables and permitted operating conditions depend on the exact ECU hardware and software. This page uses identifiable ME7 examples; it does not assert that an unmodified factory ME7 provides these aftermarket features.

Identify the Bosch and vehicle ECU part numbers, software version, engine, transmission and memory device before judging compatibility. A filename, a similar part number or the ME7.5 family label is not a safe way to choose a file or copy a patch.

Approaches compared

ExampleWhat selectsScopeEvidence limit
ME7.5 / ME7.1.1 external boardBoard switches between two external memory imagesPotentially executable code and calibrationBoard seller describes selected hardware with AM29F400BT; suitability is not established for every ME7.
ME7.1 B5 S4 L- and M-box software routineCustom code handles vehicle inputs and mode indicationFour defined sets of specific calibration entries in the author's published exampleCommunity developer reports, including bench and limited car testing; later discussion reports errors requiring correction.
ME7.5 VAG software patchAdded software uses pedal or cruise controlsMaps defined by the particular patch and fileVendor does not disclose enough to infer the exact lookup architecture for every version.
ME7.5 06A906032HS 0008 exampleCommercial custom code selects relocated calibration copiesFive load/ignition sets and two injector-constant sets according to the supplier's detailed product documentationSupplier reports static validation; independent checksum, bench and vehicle validation remain necessary.

Example 1: external dual-flash board for ME7.5 and ME7.1.1

Inovauto's dual-firmware board listing describes an adapter for particular ME7.5 and ME7.1.1 petrol ECUs using AMD AM29F400BT flash. It says the board selects two independently programmed firmware images. If code and maps occupy the switched memory, the ECU may see a different executable as well as calibration: this is an image switch, not proof that a few specific maps are chosen through software.

The AM29F400B datasheet identifies a 4 Mbit device with 512 KiB byte-mode organisation or 256 Kiwords in word mode, and its own enable and programming signals. The adapter is a separate circuit; the board seller's description is not a generic ECU pinout or evidence that a different device, memory layout or board uses the same selector wiring. Confirm the exact ECU, flash part, boot-block variant, programmer, electrical interface and image compatibility.

Neither a board switch nor a successful start establishes safe live selection. Changing an executable image mid-fetch can disrupt code and retained ECU state. Unless the precise board and its ECU/firmware combination explicitly support and have been validated for live switching, shut the ignition off and let the ECU shut down before selection. Immobiliser, coding and learned data may reside outside the selected flash and remain shared.

Example 2: ME7.1 B5 S4 L-box and M-box software routine

In a developer-authored map-switching discussion, phila_dot describes a custom routine for Audi B5 S4 L-box and M-box ECUs. The author identifies example files as 8D0907551L / 0261207004 / 1037354145 and 8D0907551M / 0261207143 / 1037354837. The supplied examples contain four sets; the first uses original map locations. The author reports bench testing those supplied stock files and separately says the code had run in their car. These are author observations, not a Bosch specification or independent safety validation.

The published initial post identifies KRKTE, KFZW, KFZW2, KFLBTS, KFLAMKRL, LAMFA and LDRXN in the accompanying definition. This is the scope of that described release, not the complete calibration or a guarantee that a similarly named file has the same additions. The author says original locations are selected as the default when RAM is cleared. The routine uses the cruise stalk to request selection or display the current set, and flashes warning lamps for feedback. Its author discusses changes to vehicle-speed and clutch gating across the thread; use the behaviour documented and verified for the exact revision, not a generic button recipe.

The later discussion reports a bug and a wrong definition-file conversion factor for KRKTE. That is a reminder that the presence of a downloadable XDF, flashing lights or an apparently successful start is not proof that all values, units and paths are correct. The same author explains that code, RAM use and references vary between ECU software versions. The publicly available discussion alone is insufficient to state a universal address, pointer format or safe porting recipe.

Example 3: ME7.5 VAG added software

Chip & Tune's ME7 MapSwitch description says switching logic is patched into supported VAG ME7.x petrol software, including examples from 1.8T and 2.7T applications. It describes selecting via pedals or cruise controls, showing the selected map on the engine lamp and rev counter, and configurable display time and switching speed limit. The maps are edited separately after patching. The product page requires checksum correction by the user. Its short public description does not establish the exact set of switched maps, addressing design or mode count for every supported binary.

Specific software example: 06A906032HS 0008

Mapelyx's ME7 product documentation describes a five-mode package for the exact 06A906032HS 0008 software. The supplier says it relocates and selects five sets each of LDRXN, LDRXNZK, KFZW and KFZW2, while KRKTE has two selectable sets rather than five. It describes selector logic and tachometer indication; the supplier's product page specifies a matching definition and warns that output requires independent checksum verification and appropriate bench/vehicle validation. This is a supplier's description of a particular patch, not a finding that all ME7 maps are duplicated or that the design works on other HS software revisions.

This example is useful because five displayed modes do not mean five copies of every parameter. In a mode matrix, record five-way items, two-way items and all shared items separately. Confirm which of the two KRKTE values is selected in each mode with that exact patch's documentation and observed behaviour; the public description does not establish that mapping. Do not infer mode-specific fuel targets, knock protection or torque limits merely from an indicator.

What the map names mean in a tuning investigation

ME7 calibration names can help identify functions but do not themselves establish location, dimensions, units or switchability. In its ME7.1 tuning notes, NefMoto describes LDRXN and LDRXNZK as load-related limits and KFZW/KFZW2 as target ignition-angle maps associated with cam-adjustment states. KRKTE is a conversion constant in the fuelling model, rather than a complete fuel map. Check the exact software definition and control strategy; a name may refer to a different variant or sit behind other limiting and correction functions.

An illustrative review for two modes would record the selected load-limit and ignition data, the actual fuelling targets and injector conversion, torque/load requests, boost control and shared temperature, knock and component-protection functions. This is a planning matrix, not a list of values to copy or a claim that any specific commercial patch switches all of them. Logger units and definitions also vary with ECU and configuration; the ME7Logger standard mapping notes warn that some injection-time conversions depend on processor speed.

Implementation and verification considerations

  1. Determine scope: Document the exact original and patched software IDs, version of the patch, selected and shared tables, input, default, indication, persistence, speed and operating conditions.
  2. Trace the actual readers: Additional tables in unused-looking flash do not affect a lookup unless code addresses them. A patch might select pointers, branch to different lookups or use another mechanism; the cited vendor descriptions do not make these interchangeable or prove a generic ME7 hook. Verify references, segment addressing, axes and conversions for each exact binary.
  3. Consider state: A switch can leave learned idle and fuel trims, controllers and values initialised at start-up shared or temporarily inconsistent. Define behaviour after RAM clearing, loss of the input and key cycles.
  4. Protect the engine: Keep knock, temperature and hardware protections appropriate to every mode. Select a safe transition condition and validate requested and actual load, boost, lambda, ignition, corrections, torque interventions and faults on a suitable controlled setup.
  5. Validate the file: Use appropriate definitions and authorised tools for the exact ECU. Verify applicable checksums and other integrity requirements, maintain a known-good recovery route, and confirm that shared immobiliser and coding data remain compatible. Do not copy hook offsets or map addresses from another binary.

A switch between two fuel-specific calibrations does not measure the mixture in the tank. For flex-fuel systems, the Haltech flex-fuel guide explains why intermediate ethanol blends need measurement and suitable corrections. Its standalone-ECU approach is not evidence that an ME7 natively supports a flex-fuel sensor or that any particular custom ME7 patch handles sensor faults.

Related guides