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 EDC17
Applies to
Bosch EDC17
Tool groups
None
Manufacturers
None

Bosch EDC17 covers many diesel control units, processors, vehicle platforms and software versions. A multimap service for one version is not evidence of a universal EDC17 selector, map address or switch input. The examples below identify what the respective suppliers say and what they do not disclose.

Example: EDC17 multimap using a diagnostic app

TuningHost's MED17/EDC17 service describes merging vehicle-specific files into one modified image and controlling its modes through an app with a Bluetooth diagnostic adapter. The supplier says this particular service does not use cruise-control buttons and dashboard indication for switching. It reports that some power-related modes can be changed while driving, fuel-related changes are restricted to stationary ignition-on operation, and some values loaded at startup need an ignition cycle. Those restrictions belong to this supplier's implementation; follow its exact ECU-specific instructions.

The supplier requests the original ECU's full file and says an OBD-only or virtual read is not accepted for this service. It warns that alternate maps may be placed outside the usual data block if that block lacks space. Its practical consequence is that a later calibration-only OBD write may not rewrite an alternate map stored elsewhere. This is a vendor-described risk, not proof that every EDC17 has the same block layout. Establish what the exact read and write include, which regions are modified and how the resulting image is verified before applying a change.

The provider states that the selection may be retained in nonvolatile storage and that its implementation is specific to the original control unit. It publishes exclusions including certain PSA diesel vehicles and Renault applications; verify the provider's full current list. Its documentation does not establish a generic public map address, assembly hook, a base-pointer scheme, or an independent ECU teardown for all claimed vehicles.

Alternative example: selector logic in a prepared flash file

EcuTracer's multi-map service advertises 2–4 profiles and selection logic in a prepared flash file for listed ECU families and example EDC17 variants. For that documented service it describes an accelerator-pedal sequence with ignition on and engine off, persistent selection and vehicle-dependent indication. It advertises checksum recalculation. These are vendor claims for its service; the exact switch routine, software compatibility and calibration scope must be confirmed for the vehicle. Do not combine its ignition-off switching rules with another supplier's live-switching instructions.

Another description by the same supplier discusses using existing variants or adding a routine in free flash, depending on the ECU. Treat this as its high-level account; it does not prove that an arbitrary EDC17 file has spare memory or that a particular factory variant mechanism is safely driver-switchable. The exact firmware must be examined and tested.

Technical interpretation

Typical logical stages are: obtain and validate a requested mode; determine when a change is permitted; choose the applicable calibrated values or paths; provide active-mode feedback; and initialise or restore state at start-up. These are general engineering stages, not a disassembly of the cited products. A supplier may switch selected tables, use broader calibration variants or combine existing and added logic. Confirm which mechanism is implemented before making a claim about base pointers, code blocks or complete images.

For diesel operation, build a specific inventory of driver-request torque, torque limiting, air and boost control, smoke or air-mass limits, injection quantity, duration and timing, rail pressure and temperature/component protection. These functions interact; a requested torque or boost change can be limited elsewhere, and a larger allowed fuel quantity is not a complete safe calibration. Names and locations vary by software, and this list does not assert that any supplier switches all of them.

Some values are read at startup or copied into RAM, while other values may be read continuously. A running mode change must not be assumed to update a cached startup value. Switching indication, stored mode, actual lookup path and learned adaptations should be checked separately. Gate and validate transitions where the design requires it and retain the protective functions appropriate to the engine and drivetrain.

Integrity, programming and validation

  1. Identify ECU hardware and software, file read type and the exact version of the vendor's patch or service. Confirm support against that original ECU and retain a known-good recovery route.
  2. Document selected versus shared functions, axes and data regions. Confirm what gets written in a calibration-only flash, a full flash and any separate nonvolatile memory. A large enough file does not establish that all bytes can safely be reused.
  3. Use the supported integrity and programming workflow. A checksum is not a cryptographic signature, and a successful simple checksum does not establish secure-boot or authenticated-programming acceptance.
  4. Confirm which input is used, permitted operating conditions, default mode, persistence and feedback. Test invalid signals, resets and interrupted requests in a controlled setting.
  5. Verify actual operating values and the chosen calibration in each mode; log torque, charge air, boost, fuel quantity and pressure, timing, temperatures, diagnostics and relevant interventions where available. Validate transitions and progressively increase load only after safe low-load results.

Related: Switchable maps overview; selected map and table switching; calibration block and address switching; RAM calibration pages and overlays. A processor's overlay feature is not proof that an individual production ECU exposes or uses it for driver mode switching.

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