Tuning Wiki

EDC17 torque fuel and tuning basics

An introduction to EDC17 torque requests, torque-to-fuel modelling, injection, air control and related limits.

Updated by llandowtuninguk@gmail.com   Revision 2

Applies to
Bosch EDC17

Check the hardware and software limits stated in this article.

The short answer

EDC17 is generally torque-oriented: the ECU considers the driver's requested output and other requests and limits in a torque structure, then determines the fuel and air control needed to produce the permitted output. Injection quantity (IQ) remains essential because the engine produces that torque by burning fuel. Bosch's description of torque-controlled EDC explains the general principle, and BitSoftware identifies torque requests, torque limitations and torque-to-fuel conversion in its BMW EDC17CP09 calibration coverage.

This is a conceptual introduction. It is not a verified function diagram for every EDC17 file. The location, sequence, units and implementation of requests, conversions and limits vary by manufacturer and software.

From pedal to fuel

  1. Read requests and conditions: Pedal position and engine speed contribute to the driver's requested output. Depending on the vehicle, cruise control, idle, transmission and traction or stability systems can also make requests or interventions.
  2. Coordinate and limit: The ECU combines or selects applicable requests and applies relevant torque limits and corrections. These can reflect engine, drivetrain, temperature or other operating conditions.
  3. Relate torque to fuel: A calibrated torque model relates the allowed torque to an injection quantity at the current operating point. Other functions can apply fuel-quantity, air-related or protective limits.
  4. Control delivery: The ECU commands injection timing and metering together with the air system. In a common-rail application it also regulates rail pressure and injector operation.

This flow is simplified. Controls and limits may operate in parallel or at different stages; startup and other operating modes can use separate strategies.

Torque model and injection quantity

The torque model represents the relationship between engine output, fuel and operating conditions. The ECU's reported or estimated torque is not necessarily measured crankshaft torque. Friction, auxiliary loads, engine speed, air and combustion affect the relationship. Check whether a diagnostic value is requested, limited, estimated, indicated or output torque before comparing it with another value.

IQ is commonly expressed as milligrams of fuel per cylinder per combustion cycle, often displayed as mg/stroke. Some values refer to total cycle fuel while others refer to a particular injection event. Confirm each signal's definition, units and scaling. There is no single fixed conversion from Nm to mg/stroke across all operating points.

A torque-to-fuel conversion is a relationship, rather than simply a maximum-torque limiter. Making the ECU's torque estimate less representative can affect torque reporting, vehicle-system coordination or protective functions. Verify the function and units for the exact software before making changes.

Common limits

  • Torque and drivetrain limits: Permitted torque can be constrained by engine operating conditions, component protection or vehicle-system interventions, such as a gearbox shift or traction control. Available functions depend on the vehicle.
  • Air and smoke limits: Fuel may be constrained according to available air and the target combustion conditions. Requested boost is not the same as measured air mass; a leak, sensor fault or turbo response can affect what is available.
  • Fuel and temperature limits: Injection quantity, speed, pressure, temperature and fault-handling functions can impose further limits. A value may be expressed in Nm, fuel quantity or another unit; a map name alone does not establish its meaning.

Raising one limit does not guarantee more output if another request or limit remains restrictive. Removing a protective function can conceal a fault or increase smoke, heat and mechanical loading.

An illustrative example

Suppose a driver request corresponds to 300 Nm and a relevant torque limit reduces it to 270 Nm. For illustration only, imagine the model relates that target to 50 mg/stroke at this operating point, while an air-related limit permits 45 mg/stroke. Delivery might then be constrained to about 45 mg/stroke before other corrections. These numbers are invented and do not define a real calibration or a universal calculation order.

Basic engine functions

  • Fuel injection: The ECU calculates how much fuel to deliver and when. On applicable common-rail systems it commands injector events and regulates rail pressure. Pilot, main and post injections may be used according to the engine and operating mode.
  • Air, boost and EGR: The ECU can manage turbocharger boost, intake air and exhaust-gas recirculation. Measured air mass, boost pressure and temperatures help it assess actual conditions.
  • Starting and running: Depending on equipment, functions include starting fuel, glow control, idle speed and smooth running.
  • Aftertreatment: Where fitted, particulate-filter regeneration and NOx aftertreatment such as selective catalytic reduction (SCR) involve additional sensors and control strategies. Audi's documented EDC17 2.0 TDI example includes particulate-filter and reducing-agent system components; not every EDC17 vehicle has the same hardware.
  • Diagnostics and coordination: The ECU monitors sensors and actuators, stores diagnostic trouble codes and may use substitute values or reduced-power strategies. It also exchanges information with other vehicle systems where supported.

A practical starting point

  1. Record the vehicle, engine, injection and emissions equipment, ECU hardware number and complete software and calibration identifiers. Retain a recoverable original read and establish a healthy baseline.
  2. Match definitions to the exact software. Record the function, axes, units, scaling and evidence for each request, conversion and limiter; do not transfer addresses or assume identical labels imply identical behaviour.
  3. Consider torque requests and limits, fuel quantity, timing, measured air, boost control and, where fitted, rail pressure and aftertreatment together. Keep torque reporting and vehicle interventions coherent.
  4. Where supported, compare requested and limited torque or IQ, measured air, requested and actual boost, temperatures and rail pressure. Diagnose unexpected limits and faults before changing calibration, and verify the result under controlled conditions.

BMW EDC17CP09 example

BitSoftware’s CP09 module lists more than one type of torque limit, along with requested torque, torque-to-injection conversion, rail-pressure, injection, air and boost functions. It also lists different boost-control data for regeneration and other operating conditions. This is the vendor’s software coverage for the named BMW ECU, not evidence that every EDC17 file contains the same maps or uses the same sequence. See Bosch EDC17CP09.

Audi’s two documented 2.0 TDI systems show why fuel pressure, injector type, sensor fallback and aftertreatment must be checked per installation: EDC17 Audi 2.0 TDI system examples.

Sources