Tuning Wiki
Applies to

Check the hardware and software limits stated in this article.

Bosch MG1 is a family of petrol engine control units used in many different vehicles and software generations. Switchable maps are not one common MG1 memory layout or a feature of every factory ECU: the examples below describe named third-party software for specific supported images. Identify the actual ECU hardware, software and feature version before adopting any detail.

Example 1: BMW B48/B58 with MG Flasher custom code

MG Flasher's switchable-map tuning guide describes one running calibration in a base area plus selectable alternatives in a custom-code area. Its five slots are slot 0, the base calibration in the OEM/main area, and optional slots 1–4. A feature-level setting, individual slot enables, per-map enables and the slot-specific map values all matter. Slots and maps disabled in the configuration must not be assumed to change.

The vendor's application guide discusses selected B48/B58 generations and custom-code and map versions. Its published Gen 2 A2L file identifies an MG1CS201 project; it is an example definition, not evidence that every B48/B58 vehicle uses that controller, image, software or feature. The deprecated file name contains R4C9H5C5B while its internal project metadata identifies R4C2H5C5B; resolve that discrepancy with the supplier before treating it as a matching definition. Check the actual ECU ID and a matching definition.

Illustrative read path for this documented product: suppose a supported map has its per-map switch enabled, the feature is enabled and slot 2 is valid and enabled. The selected slot can use the slot-2 copy of that map. If the per-map switch is off, the vendor says that map instead refers to slot 0 even when another slot is selected. Thus two modes may intentionally share one calibration while differing in another. The public guide describes the configuration and locations at a high level; it does not document a universal machine-code hook, common pointer address or patch offset.

ItemRole in this examplePractical check
Feature settingEnables map switching for the custom tune.Confirm the written file and app configuration.
Slot 0Base/default data in the OEM/main area.Identify the actual base calibration and fuel requirements.
Slots 1–4Optional data sets in a custom-code area.Only use enabled slots with valid, populated values.
Per-map settingEnables switching of an individual map across slots.Verify every intended map and every enabled slot.
Map dataValues actually consumed when that map and slot are enabled.Check axes, units, limiters and associated controls.

The vendor's guide says map enabling applies to all slots for that map, so every enabled slot needs valid data. Its map validity tool distinguishes populated and unpopulated map slots. The vendor's B48/B58 guide specifically warns that certain listed Gen 2 off-the-shelf versions have switchable slots that are not populated with alternate calibrations. Availability of a slot or a dashboard indicator does not prove that a different, correctly tuned map is present.

The same application guide reports selection using steering-wheel controls or an in-app diagnostic menu, with the available behaviour dependent on custom-code and vehicle version. It describes certain fuel maps in terms of octane and ethanol blends, but the label on a slot does not measure the fuel in the tank. Its compatibility notes contain version-specific qualifications and must be checked against current vehicle data; do not transpose an earlier button sequence to an arbitrary file.

Example 2: MG1/MED17 file-difference implementation

A separate Chip & Tune MG1/MED17 MultiFile tool, described as beta, takes an original and up to seven other files of the same software version. The vendor says its tool extracts the differences, places alternate maps in available flash and adds selection logic. It describes certain VAG and Mercedes MG1/MED17 applications, cruise or pedal selection, rev-counter feedback and optional EEPROM storage of the chosen mode. The vendor reports automatic checksum correction for this tool. Verify the exact ECU, software and current terms before relying on it.

This is not evidence of eight complete firmware images or a relocatable whole-calibration pointer. The inputs are full files, but the documented output contains stored differences and custom selection logic. By contrast, the supplier's CSV-based tool describes creating switchable copies of selected defined maps in MG1, MED17 and MEVD17. Its exact source-code hook, data addresses and all shared values are not publicly established by those product descriptions.

Coverage and validation

  • Identify both hardware and software numbers, ECU replacement history, valid file definitions, selector inputs, output indication, mode count and whether the selected state persists after a reset.
  • Make a map matrix: requested torque, charge and boost targets, torque/air/boost limits, fuel, ignition and protections. Record which are switched, shared, disabled or unknown. The matrix is an investigation aid, not a claim that a product switches every category.
  • Check file size and whether a normal calibration-only operation covers the custom area. Follow the exact tool and ECU supplier's supported flash and verification workflow; a modified file's checksums do not by themselves prove signature or secure-boot acceptance.
  • Confirm actual values and mode state, including low-load transitions, invalid inputs, reboot and brownout. Validate all enabled maps and coherent torque, fuelling and protective behaviour before increasing load. Preserve protections and comply with applicable road and emissions rules.

Related: Switchable maps overview; selected map and table switching; RAM pages and overlays. AURIX overlay is a separate development mechanism and is not established by a vendor advertising MG1 map slots.

ECU-specific guides: Bosch EDC15 · Bosch ME7 · Bosch MG1 · Bosch MED17 · Bosch EDC17 · Simos 18 · Simos 19.