Bosch MED17 includes many petrol ECU variants with different software layouts. The following examples are specific third-party implementations; they do not establish factory map-switching support or identical code and memory addresses across MED17 controllers.
Version-scoped example: simos.app MED17 Main Patch
The simos.app MED17 Main Patch guide documents two to five configurable slots on named software builds. Its list includes, for example, MED17.5 D175X55H_M08W20, MED17.5.2 D1752V02C000_MY13E31, MED17.5.21 D17521V36C002_M28I9C and MED17.1.27 D17127V50C001_M33V52. The complete supported list and differences are in the guide. A family name or matching engine is not proof of support for another binary.
The patch's user interface supplies 2–5 modes. In the documented default cruise-control setup, a sustained assigned-button press enters selection, up/down browses slots, the rev counter indicates the current selection and a confirmation or selection timeout commits it. The guide also describes optional ESC-button and indicator-stalk inputs with different constraints; the indicator-based method is ignition-on, engine-not-running and unavailable for several named builds. Reused ESC input can still operate traction control. Check the exact software and settings rather than copying a button sequence from another ECU.
What the slots actually contain
The vendor describes each slot as its own configurable collection of features, not a complete copy of every factory calibration table. The important details are specific:
- Torque limit: a per-slot ceiling indexed by engine speed and gear. It is compared with the ECU's own limit and can only reduce it; the guide notes this function is unavailable on software
1037396225. - Boost limit: a per-slot ceiling on the absolute boost-pressure setpoint by speed and gear. It caps the requested pressure; it does not by itself increase the target.
- Driver-request torque: slots 2–5 can optionally override the applicable stock pedal maps; slot 1 remains stock, and reverse and maps that are empty in stock stay stock.
- Ignition: MED17.5 has a per-slot spark offset against the stock basic ignition map's rpm/load axes, not a wholesale independent replacement of every ignition function. The stated implementation and range apply only where the guide says.
- Other features: the documented patch supplies per-slot feature switches; being switched on does not by itself mean every unrelated ECU protection or calibration is duplicated.
Torque-limit maps share a single rpm axis between slots, and boost-limit maps likewise share their own axis. The guide requires these axes to rise. For a conceptual comparison, a lower torque or boost ceiling in a wet-weather mode may reduce outputs when it is the limiting value; it cannot raise an otherwise lower factory ceiling. Actual results depend on the complete ECU control path, operating conditions and calibration. This explanation is not a recommended tune.
On the specifically listed MED17.1.27 software D17127V50C001_M33V52, the vendor describes an optional mapping from the vehicle's Normal, Sport or Eco drive profile to a chosen slot. Other drive modes leave the current slot unchanged; a manually chosen slot remains until a subsequent drive-mode change. The guide says the drive-mode link is off by default. Do not infer this feature from an ECU family name.
The same source describes VIN-linked patch behaviour and a full-flash requirement when adding or removing the patch, while later parameter-only changes use a calibration flash for its supported workflow. It explicitly states that MED17 flashing through simos.app itself is not yet available in the cited guide. Check current supported tooling, release and exact ECU before proceeding; do not interpret this as a method to bypass ECU protections.
Alternative approach: selected maps or file differences
The beta Chip & Tune CSV-based tool describes selecting specific maps using definitions and creating switchable copies on supported MED17, MEVD17 and MG1 images. Its separate MultiFile tool says it extracts differences from matching software files, stores alternate maps in available flash and adds selection logic. Those are different products with different documented input and output workflows; neither published description establishes a universal pointer address, complete firmware-bank selection or availability for every MED17.
Another service: app selection and startup-only values
TuningHost's MED17/EDC17 service describes its own app and Bluetooth diagnostic interface, not the simos.app button method. It states that some changes may be made while driving, certain fuel-related modes require the vehicle stationary, and some startup-loaded settings require an ignition cycle. It also cautions that alternative data may be stored outside the usual data block and therefore not be rewritten by a calibration-only OBD flash. These are supplier-specific statements and do not prove a standard memory layout; confirm the precise ECU, complete programming coverage and mode restrictions.
Checks before use
- Record ECU hardware and software identifiers, patch and definition versions, and original known-good file and supported recovery path.
- Make a per-slot inventory of the exact axes, maps, limiters, feature switches and shared data. Determine whether a target, an override, a correction or a lower-only ceiling is actually being changed.
- Verify input conflicts, feedback, requested versus active slot and what happens on reset, loss of signal and a rejected request. Validate the supplier's exact flash regions and checksum/authentication process.
- Log requested and actual torque, air and boost, fuelling, ignition, intervention and faults. Validate every slot and the transition at controlled low load before progressing, keeping component and engine protections appropriate.
Related: Switchable maps overview; selected map and table switching; calibration block and address switching.
ECU-specific guides: Bosch EDC15 · Bosch ME7 · Bosch MG1 · Bosch MED17 · Bosch EDC17 · Simos 18 · Simos 19.