Tuning Wiki
WikiME7.6 tuning maps torque and boostHistory

ME7.6 tuning maps torque and boost

Revision 1

by llandowtuninguk@gmail.com
Add sourced ME7.6 tuning guide

This is a historical revision. Read the current page or return to its history.

Page organisation in this revision
Page type
Technical article
Subject
Tuning
Parent
Bosch ME7.6
Applies to
Bosch ME7.6
Tool groups
Not recorded in this older revision
Manufacturers
Not recorded in this older revision

Scope and starting point

This guide covers the main calibration jobs to investigate on Bosch ME7.6 petrol ECUs, including ME7.6.1, .2, .3, .4 and .H4. Some examples are turbocharged and some are naturally aspirated. Start with the fitted engine, ECU hardware, software and calibration identification; the family name alone is not a map definition. Use the ME7.6 identification and working record.

For a concrete example, Auto-Remap advertises a map pack for an Opel Astra Z20LEL ME7.6.2, Bosch hardware 0261208152 and software 1037374099. Its listing groups maps for torque request, requested load, throttle, turbo pressure, fuel, lambda and ignition. Those are the supplier's labels for that file, not a verified factory function diagram or a definition for other versions. The supplier states that one of the 68 axes checked did not read correctly: verify the definition independently.

How torque, load and boost relate

Bosch's ME-Motronic technical instruction describes a torque-oriented system. The following is a useful conceptual path, not a claim that every ME7.6 version executes these steps in this exact order:

  1. Request: Pedal position and engine speed contribute to a driver torque request. Depending on the application, sport mode, low-speed operation, transmission and other systems can select different requests or interventions.
  2. Coordinate and limit: The ECU combines relevant requests and restrictions, including protection and drivetrain limits. The requested, permitted and estimated torque values are different signals; a relative or indicated torque value is not automatically measured crankshaft Nm.
  3. Translate to air charge: A calibrated engine model relates the torque target to a desired cylinder charge or load. The model also estimates torque from operating conditions so other functions can coordinate their actions. Air-charge, spark and mixture assumptions need to remain coherent.
  4. Control the air: The throttle meters air. On a turbocharged application, boost control also commands the relevant actuator and compares pressure feedback with its target. A load request, a boost target and wastegate duty are related but distinct quantities.
  5. Deliver and check: Fuel and ignition controls work alongside the air path; lambda feedback, knock correction and other limits can change the outcome. Several restrictions can act together or in parallel.

A higher pedal request can change pedal feel without increasing the output allowed at full demand. Raising an air or boost limit cannot produce the intended result if torque demand, throttle, airflow, fuel, temperature protection or another limit remains decisive. Conversely, changing the model merely to hide calculated torque can make the ECU's estimate less representative and disturb monitoring or vehicle-system interventions.

Main map groups to identify

Use the names and axes in a definition matched to the exact software. The descriptions below explain what to investigate; they are not instructions to change every table.

GroupWhat to look forHow to assess it
Driver demand and torque coordinationPedal or torque request against engine speed and pedal position; separate mode, low-speed, gear or transmission requests where fitted. The Z20LEL example lists several request contexts.Compare the active request and permitted torque with pedal position. A low-speed or sport table need not be the full-load table; check selection conditions.
Torque model and desired loadMaps for desired engine load, optimal torque and torque monitoring. The definition may express relative cylinder charge, relative torque or another quantity rather than Nm.Check how request-to-load and load-to-torque relationships use the same operating region. They represent related model functions, not necessarily exact mathematical inverses in all conditions. Confirm axes, units and any ignition or lambda corrections.
Airflow and throttleAir-mass conversion or modelling, throttle airflow and opening-angle maps, and relevant air or load limits. A particular car may use different sensors and estimation paths.Compare actual airflow or manifold pressure, load and throttle angle where the signals exist. A replaced MAF or pressure sensor needs a matching transfer function and supported measurement range, not an arbitrary limit increase.
Boost request, limits and controlOn turbo applications, identify pressure or load targets, pressure and ambient-dependent limits, and wastegate control or linearisation. The example map pack lists separate target, limit and linearisation groups.Log requested and actual pressure, ambient pressure and actuator duty. Confirm whether the actuator opens or closes with increasing duty for that system. A duty map is not the pressure target, and different limits may apply in different conditions.
Fuel, lambda and injectorsRequested lambda, component-protection lambda, injection base and temperature corrections, plus injector flow and voltage or pressure compensation where present.Compare commanded and independently measured lambda under load; check fuel pressure and trims where meaningful. Injector flow alone does not establish correct short-pulse or voltage behaviour. Changing a target does not prove the fuel system delivered it.
Ignition and knockBase and optimal spark tables, temperature corrections and knock-related functions. The vendor example lists base and optimal spark separately.Compare commanded timing, corrections and cylinder knock activity with fuel and temperature conditions. An optimal-torque spark reference is not necessarily the final commanded timing or a safe knock limit.
Protection and monitoringDepending on the software, torque, charge, pressure and temperature limits, component-protection mixture, rpm and plausibility monitoring.Find the active cause of a restriction before altering a threshold. Preserve knock, exhaust-temperature, overspeed and pressure protections; their operation is part of the calibration.

Common Bosch names: a comparison, not an ME7.6 map pack

Bosch's published ME7.3.1H Alfa function sheet uses the names below. They are useful search terms when reading ME documentation, but the sheet is not for ME7.6. The source does not prove that a particular ME7.6 file has the same symbols, dimensions, axes or function. Check a matched ME7.6 definition and actual software before using any name.

Comparison nameMeaning in that ME7.3.1H document
KFPEDPedal characteristic producing a relative driver torque request from pedal position and speed.
KFMIRL / KFMIOPOne relates a torque quantity to nominal charge; the other represents optimum torque against speed and charge. Their relationship is part of the torque model.
MLHFMAir-mass meter transfer characteristic for the documented sensor configuration.
KRKTE / TVUBRelative fuel-mass to injection-time conversion and injector voltage correction, respectively.
LAMFA / KFLBTSDriver-related lambda request and an exhaust-temperature-related component-protection enrichment function.
KFZWOPOptimum ignition angle used in the documented torque model; it is not identified as a universal base spark table.

Similarly, ME7.1 / ME7.5 examples such as LDRXN, KFLDIMX and KFLDRL are not proof that those names or functions are present in a particular ME7.6 calibration. Do not copy an address, scaling, formula or threshold from another ECU. Confirm the relevant load and boost functions on the target software.

What changes between variants?

VariantDocumented examples and practical distinction
ME7.6.1TRW lists an Astra H Z14XEP application. SMS-Soft's ME7.6.x definition module lists specified .1 and .2 software for the small Z10XEP / Z12XEP / Z14XEP engines; it excludes the Z20LEH from that module. Check the actual engine and supported software, including any transmission or mode context.
ME7.6.2Sources list both a 1.4 Z14XEP Meriva and the turbocharged Z20LEL / Z20LER / Z20LEH family. The cited Z20LEL map listing includes turbo target and limiting groups; the turbo-specific work is not transferable to a naturally aspirated example. SMS-Soft publishes a separate Z20LEx turbo module.
ME7.6.3Alientech lists a Corsa D 1.6 Turbo Z16LER example. A vendor's Z16LEL listing describes torque, load, lambda, spark and boost groups for one .3 file. Tool lists disagree on the processor named for some Opel .3 entries, so inspect the exact unit and confirm the method.
ME7.6.4Microtronik lists Opel 1.6 turbo applications; a vendor lists an Insignia A16LET example with hardware 0261S06391 and software 1037509827. Its listed map groups overlap the examples above, but that does not establish identical addresses, scaling, selections or control logic.
ME7.6.H4Also written ME7.6H4 or ME76H4. The A.D.S. catalogue lists Opel Corsa C / Agila Z12XE examples; DFB lists one C167 / 29F400BB configuration. A matched tuning definition has not been established by these sources. Confirm the actual engine and forced-induction hardware before applying any boost-specific discussion.

ME7.6.4 and ME7.6.H4 are different designations. The cited map-pack listings are selected, vendor-defined subsets; differences in their number of entries do not establish the number of ECU functions or prove a family-wide software difference. Fiat-group applications also exist and must be matched to their own engine, hardware and software.

A practical tuning and verification sequence

  1. Identify and preserve: Record vehicle, engine, fuel, gearbox, hardware and all software/calibration identifiers. Save the original read and a hash; establish what memory areas the read includes and a documented recovery path.
  2. Establish a baseline: Check faults, servicing, fuel quality, intake and charge plumbing, ignition and fuel delivery. Record the hardware configuration and stock logs before attributing a problem to calibration.
  3. Verify the definition: Check each relevant map's address basis, data type, axes, units, scaling and operating conditions against the target. Compare a known unmodified file and seek independent evidence; an unfamiliar or nonsensical axis is a reason to stop and investigate.
  4. Plan the air, torque and fuel changes together: Identify the active driver request, torque and charge relationships, limits, throttle and, where fitted, boost control. Include sensor range, injector data, fuel-system capacity, ignition and component protection. Make measured, traceable changes appropriate to the hardware.
  5. Test and compare: On suitable equipment and under controlled conditions, log engine speed, pedal, throttle, requested and actual load or torque, and intake and coolant temperature. On turbo engines add requested and actual manifold pressure, ambient pressure and actuator duty. Where available compare requested and measured lambda, trims, fuel pressure, ignition timing and individual-cylinder knock corrections. Record units, gear and conditions with every run.
  6. Investigate before continuing: If actual boost is low despite high actuator demand, inspect the actuator, control plumbing and leaks as well as calibration. If throttle closes, compare torque and load requests, limits and faults before assigning a cause. If lambda or knock behaviour is unexpected, stop and resolve it. Verify checksum support, write and recovery procedures for the exact unit before programming.

Pressure example: at an ambient pressure of 100 kPa, a manifold pressure of 220 kPa absolute is 120 kPa above ambient. These invented figures illustrate the distinction between absolute and gauge pressure; they are not a boost target. Sensor range, pressure losses, altitude and the active definition still matter.

Sources

Curated reference notes. Applicability follows the cited sources; hardware testing by this wiki is not implied.