Tuning Wiki

Selected-table switching changes a defined group of maps or scalars while the remaining ECU software and calibration continue to be shared. For example, one mode may use a different requested boost, ignition and fuel target from another without replacing sensor scaling, every torque limiter or the complete firmware. A mode is a selection of calibrations; its name does not prove which individual maps are actually used.

This page explains concepts and documented products. Hardware, software version, flash layout and the applied patch determine whether a technique works on a particular ECU. The vendor examples do not reveal all internal implementation details. Return to the Switchable maps overview.

How selected maps are switched

The ECU determines a mode from a driver input or another condition. A mode-dependent choice then supplies a value or selects a table for a specific function. Possible designs include separate table pointers, a lookup branch, a table-indexed selection, an additional mode axis or a correction to the normal result. These are engineering patterns, not claims about a particular commercial patch.

As a simple example, mode 1 and mode 2 could each have their own boost request and ignition table while a common coolant correction and common safety limiter remain shared. A complete implementation must identify the exact functions and every call site which consumes those maps. An apparent duplicate in a file may instead be for a transmission variant, fuel type, hardware option or unused data. Duplicate data does not by itself establish that it is a switchable mode.

Space calculation: a 16 × 16 table with 16-bit values occupies 512 bytes for its values. Four such mode tables occupy 2,048 bytes for values; three additional copies beyond the original require 1,536 bytes. Axes, descriptors, alignment, code, other tables and checksums add overhead. This is an illustrative layout, not an ECU-specific map definition. Shared axes save space only if the actual lookup format allows it.

ME7.x example: separate boost, ignition and fuelling sets

Chip & Tune's ME7.x MapSwitch description describes a patch for compatible VAG Bosch ME7.x petrol software, with examples including 1.8T and 2.7T. The vendor says the switching logic is patched into the original software and that the maps are subsequently edited in a compatible editor. Pedal or cruise-control input selects a mode, with rev-counter and engine-lamp feedback. The display time and speed threshold for switching are configurable.

This demonstrates a documented set of individually editable calibration functions, not proof that all ME7 software supports the patch, that all maps in the ECU change, or that the product implements a particular pointer structure. Confirm the file, software ID, advertised feature set, supplied map definitions, checksum handling and exact switching conditions with the vendor. The vendor says checksums must be corrected by the user.

Illustrative ME7 mode matrix

FunctionMode 1Mode 2Verification needed
Boost requestOriginal or calibrated table ACalibrated table BActive request and actual boost; dependent limiters and protection remain appropriate.
IgnitionTable ATable BBoth tables and all relevant ignition corrections; observe knock and interventions.
Fuel targetTable ATable BRequested and measured mixture; transient and closed-loop behaviour.
Temperature and fault protectionsShared unless documented otherwiseSame shared data unless documented otherwiseDo not assume a table is switched or protected solely from its name.

This table is a planning example, not a specification of the vendor patch or a ready-to-flash tune. ME7 torque, load and boost calculations interact; increasing a requested value can be capped elsewhere or create inconsistent model behaviour. The selected maps must be tuned and tested as one combination, with protections retained.

EDC15: distinguish a group of blocks from individual tables

The Chip & Tune EDC15 MapSwitch description says its supported 512 KB and 1 MB files use three code blocks as independent maps; missing blocks may be copied and switching logic added. It describes pedal or cruise selection and optional nonvolatile selection storage. This is a useful contrast with switching one chosen map: its description is block-based and does not establish the exact per-table selection or support across the EDC15 family.

A diesel calibration group may include driver demand, torque limitation, smoke limitation, boost request, injection quantity or duration and timing. Identify what the particular block contains and which data remain common; do not assume that changing a smoke or boost target alone creates a complete independent tune. Check axes, conversions, units and software variant using verified definitions. The cited vendor specifies its own checksum and file requirements.

Modern example: selected maps in MG1, MED17 and MEVD17

The supplier describes a CSV-based MG1/MED17/MEVD17 tool which works at the level of individual selected maps. The vendor says it takes a full read and a WinOLS CSV or mappack and makes switchable copies of exactly those maps; suggested examples include ignition, fuel, boost and torque limiters. It labels the tool beta. Availability and map suggestions depend on the exact ECU software. This does not establish that a specific production ECU natively supports this feature or disclose the internal method.

Build a map inventory before selecting items: original and alternate addresses, dimensions, axis locations, scaling, the function in which each is used, mode coverage and whether a definition is verified. A mappack identifies candidate data; it does not prove every lookup, diagnostic path, dependency, checksum or safety function has been accounted for. A correction, model or protective limit may be elsewhere and remain shared.

Modern worked example: Nissan VR30

EcuTek's VR30 Twin Turbo RaceROM factsheet describes four-way mode selection using cruise controls or an app, with tachometer feedback. It lists four ignition base and maximum maps, four air–fuel target maps, and four boost target maps indexed by gear and engine speed. A separate charge-air failsafe and per-mode boost control are also listed.

That is useful evidence for which functions that documented product exposes, not proof that every table in the ECU has four copies or that the same features exist on another Nissan, ROM or ECU. It also shows why verification must cover requested and measured results: the selected target, limiters, closed-loop controls and protection functions jointly determine actual behaviour.

Aftermarket ECU example

Motorsport Electronics' switchable-map documentation describes two sets of ignition, fuel and boost maps, selectable from configured digital or analogue inputs or a VVT condition. It allows the user to select all supported groups or only a particular group, such as ignition. The manual instructs the user to confirm the selected-map indicators for the armed state. Its ME platform is the manufacturer name, not Bosch Motronic ME7.

Haltech's rotary trim example instead illustrates an additional switch-position axis in a boost target map and other functions. A map axis, a multiplier and an independently stored table can produce similar driver-facing options while using different underlying calibration structures.

Designing and validating a switch

  1. Identify the exact ECU, software ID and approved feature implementation. Record the known-good file and recovery path. Check input assignment against existing vehicle functions.
  2. Make a matrix of every mode against each selected and shared map, scalar, limiter, axis and correction. Confirm table sizes and references from reliable definitions and, where available, trace or log the actual value used.
  3. Define switch request, valid range, default, persistence, indicator and behaviour for invalid or lost signals. Debounce inputs and gate or delay switching when needed.
  4. Make a coherent mode change at a defined boundary. A single pointer write does not guarantee consistency across unrelated tasks, cores, cached data, controller state or independently switched functions.
  5. Verify the actual active mode and ECU outputs after startup, restart, brownout, rapid requests and failed input. Include integrators and learned fuel/idle corrections that may carry over between modes.
  6. Validate each mode separately and the transition in a controlled environment. Log demand, actual torque or load, boost, fuelling, ignition and knock where applicable, temperature, faults and protective interventions. Keep hardware and protective limits appropriate to every mode.

On a modern ECU, checksum validation is distinct from signatures, authenticated programming, secure boot and runtime integrity. Additional storage does not guarantee that modified code or calibration will be accepted. Respect the exact software and tool requirements and relevant emissions and road-use rules.

Related method pages