Tuning Wiki

MD1 torque fuel and tuning basics

A practical introduction to diesel MD1 torque requests, torque-to-fuel modelling, injection and related limits.

Updated by llandowtuninguk@gmail.com   Revision 1

Applies to
Bosch MD1

Check the hardware and software limits stated in this article.

The short answer

In the diesel vehicle applications covered here, Bosch MD1 is generally torque-oriented. The ECU can coordinate the driver's requested output with other requests and limits in torque terms, then determine the fuel and air control needed to produce the permitted output. Injection quantity (IQ) remains central to delivering that torque.

BitSoftware's BMW diesel MD1 module explicitly lists requested torque, torque limitations and injection quantity from torque, as well as air, injection and rail-pressure functions. Bosch describes torque coordination in its general EDC literature. These sources support the explanation below, but they do not establish an identical calculation sequence or map layout in every MD1 application.

From pedal to fuel

  1. Read requests and conditions: Pedal position and engine speed contribute to the driver's requested output. Cruise control, idle control and other vehicle systems can also affect requests where supported.
  2. Coordinate and limit: The ECU selects or combines the applicable requests and limits. Engine operating conditions, drivetrain requirements and a gearbox or stability-system intervention can affect permitted torque.
  3. Relate torque to fuel: A calibrated relationship determines the fuel quantity associated with the operating point. Air-related, injection-quantity or other protective limits may also act.
  4. Control delivery: The ECU commands fuel metering and timing along with the air system. On a common-rail application it also controls rail pressure and injector events.

This is a conceptual flow: real functions can operate in parallel, apply limits at different stages or use separate starting and other operating-mode strategies.

Torque model and injection quantity

A torque model represents how engine output relates to fuel and operating conditions. ECU torque values are often calculated or estimated, not a direct measurement at the crankshaft. Friction, auxiliary loads, engine speed, air and combustion affect the relationship. Check whether a displayed value represents requested, limited, estimated, indicated or output torque before comparing it with another figure.

IQ is commonly expressed as milligrams of fuel per cylinder per combustion cycle, often displayed as mg/stroke. Some tools or signals distinguish total cycle fuel from individual injection events or use other units. Verify the definition and scaling: there is no single fixed conversion between Nm and mg/stroke across all operating points.

A torque-to-fuel relationship is not simply another maximum-torque limiter. Changing that relationship without understanding it can make calculated torque less representative and affect vehicle-system coordination, reported values or protections. Verify its function and units for the exact software.

Common requests and limits

  • Driver and other requests: A pedal demand can be interpreted in torque terms; supported cruise, idle, transmission or traction functions can add requests or interventions.
  • Torque and drivetrain limits: Limits can depend on speed, temperature, component protection, faults or external requests. BitSoftware lists inner and outer torque limits and condition-dependent limits for its BMW MD1 example.
  • Air and smoke limits: Fuel can be constrained according to available air and combustion requirements. Requested boost is not measured air mass; leaks, sensor faults or turbo response can change what is available.
  • Fuel and other protections: Injection quantity, pressure, speed, temperature and diagnostic strategies may impose additional constraints. A familiar map label does not prove its units, axes or exact role.

Increasing a single limit does not ensure more output when a request or another limit remains restrictive. Removing a protective function can conceal a fault or increase smoke, heat and mechanical loading.

An illustrative example

Imagine a driver request of 320 Nm, limited to 290 Nm for the operating condition. Suppose the model relates that target to 55 mg/stroke and an air-related limit permits 48 mg/stroke. In this simplified example delivery might be limited to around 48 mg/stroke before other corrections. These numbers are invented and do not describe a real calibration or prescribe a universal order of operations.

Basic functions in a diesel application

  • Fuel delivery: The ECU determines injection quantity and timing. A common-rail system also regulates fuel pressure and commands the injectors; pilot, main or post injections can be used according to the engine and operating mode.
  • Air, boost and EGR: The ECU can manage air supply, turbocharger boost and exhaust-gas recirculation. It uses available sensor signals, including pressure, air mass and temperatures, to assess operating conditions.
  • Starting and running: Depending on equipment, functions can include starting fuel, glow control, idle control and smooth running.
  • Exhaust aftertreatment: Where fitted, diesel particulate filter regeneration and NOx control, including selective catalytic reduction (SCR), require additional sensors and coordination. The BMW MD1 calibration list includes particulate-filter, exhaust-temperature and SCR functions; fitment varies.
  • Diagnostics and vehicle integration: The ECU monitors sensors and actuators, records diagnostic trouble codes, exchanges information with other systems and can use substitute values or reduced-power operation when appropriate.

MD1 family boundaries

Passenger-car diesel MD1 examples are not definitions for all MD1 units. Bosch's MD1CE200-LE is a large-engine controller for diesel, gas and dual-fuel applications; its installation, fuel system and software must be assessed separately. MD1 does not guarantee common-rail injection, a particular emissions system, processor, map address or diagnostic channel.

Like the torque-oriented EDC17 examples, diesel MD1 still controls fuel quantity. The shared principle does not make their calibrations, files, tools or protection logic interchangeable.

A practical starting point

  1. Record the vehicle, engine, injection and emissions equipment, full ECU hardware number and software and calibration identifiers. Keep a recoverable original read and establish a healthy baseline.
  2. Match definitions and any reading or writing tool to that exact hardware and software. Record the source, function, axes, units and scaling for each relevant request, conversion and limit.
  3. Consider torque requests and limits, injection quantity and timing, measured air and boost together. Where applicable include rail-pressure control and aftertreatment. Keep torque reporting and vehicle-system interventions coherent.
  4. Where diagnostics support them, compare requested and limited torque or IQ, air mass, requested and actual boost, temperatures, rail pressure and relevant faults. Diagnose unexpected limits before changing calibration and verify the outcome under controlled conditions.

Sources