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
Diagnostics
Parent
Bosch EDC15
Applies to
Bosch EDC15
Tool groups
Not recorded in this older revision
Manufacturers
Not recorded in this older revision

Changes from revision 1 to revision 2

Removed text is struck through; added text is highlighted.

Scope

Diagnostic tools can expose requests, calculated quantities, limits, sensor readings and actuator states. Their names do not prove which maps exist or that an indicated quantity was physically measured. Availability, units and meaning depend on the ECU, vehicle and tool. The examples below use the diesel parameter descriptions in the Snap-on Volkswagen/Audi manual, printed pages 136–139; the manual does not establish that each value exists on every EDC15 or every diesel.

Fuel quantity and interventions

Injection quantity: an indicated quantity for the operating condition, commonly displayed in milligrams per cylinder stroke in the manual. “Desired” is described there as a permissible quantity after corrections; check the exact tool’s definition before treating it as a physical measurement. Driver, torque and smoke quantities: the manual distinguishes a driver-related request, an engine-speed/load-related torque limitation and a smoke-related limitation. Comparing available values under the same conditions can help identify which demand or restriction is relevant; it does not prove a universal selection order. Cruise, traction control and automatic-transmission quantities: the same manual lists separate quantities associated with cruise control, traction control and transmission-related torque intervention. These are conditional on the vehicle and equipment. Start quantity: a separate quantity may be reported during starting. Do not compare a starting value directly with a warm driving value without checking operating state and units.

If a request is higher than a reported limit, investigate the conditions that make that limit relevant before changing a calibration. Limits can protect hardware or manage smoke, and other corrections may still apply. Snap-on, printed pages 137–139; Bosch, printed page 53.

Air, boost and temperatures

The Snap-on manual lists desired and actual boost, intake-air temperature, coolant and fuel temperature, and desired and actual air-mass readings for its covered vehicles. Compare values only in the same operating conditions and confirm whether pressure is absolute or relative to atmosphere. A pressure reading is not a substitute for measured air mass; EGR, restrictions, leaks, sensor issues and control response can affect interpretation.

The manual describes substitute values for certain sensor failures in its examples. Bosch likewise explains that fallback strategies differ by vehicle manufacturer. A plausible displayed value can therefore be a substitute: review fault codes and the relevant service information before assuming the sensor is working. Snap-on, printed pages 136–138; Bosch, printed page 74.

Timing and cylinder balance

Where the actual application provides them, compare desired and actual start-of-delivery or start-of-injection data with their stated units and reference. Snap-on describes a needle-lift-feedback example, while Bosch also documents pump timing-device and unit-injector BIP feedback. The named event and feedback mechanism are not interchangeable. See EDC15 injection systems and timing feedback.

Cylinder injection-difference or smooth-running values can show how the controller is compensating between cylinders. Bosch describes using crankshaft-speed variation to adjust individual cylinder quantities; Snap-on lists example cylinder-difference parameters. A correction is a control response, not a diagnosis of a particular injector or mechanical fault. Check the applicable test conditions, reference cylinder or average, units and vehicle-specific limits. Bosch, printed pages 52–53; Snap-on, printed pages 137–139.

Practical recording checklist

Record the vehicle, engine, injection system, ECU hardware and software identifiers, diagnostic tool and the conditions under which the issue occurs.Save relevant fault codes and freeze-frame information where available. Record engine speed, temperature and operating state alongside live values.Compare available requests, limits and feedback at the same point in time. Include air mass, boost, temperatures and the timing or rail-pressure values appropriate to the actual hardware.Use the manufacturer’s procedure and specifications for that exact vehicle to investigate discrepancies. Recheck after a repair or calibration change; do not use a generic threshold as a pass/fail value.

For example, Saab’s 2001 9-3 D223L describes separate diagnostics in the VP44 pump and glow-control module that are reported to the engine ECU. That architecture must not be assumed for another EDC15 application. Saab WIS, 2001 9-3 D223L.

Fault memory and scan-tool accessBosch describes checks of sensor signal ranges and plausibility, actuator circuits and system response. In those general EDC examples a fault record can include its status and operating conditions when it occurred. Record available codes and freeze-frame information before clearing them. A code identifies a detected problem or implausibility; the sensor, wiring, supply and the conditions that enabled the test may all need checking. The checks and stored information vary by vehicle. Bosch, printed pages 78–80.For its VW/Audi software, Snap-on says that the combined codes-and-data display may contain only a selection of available measuring groups and can refresh more slowly. A missing value in one screen therefore does not prove the ECU lacks it. In that tool, reading measuring-value blocks and entering basic settings are different operations; use the exact vehicle and tool instructions before running a functional or basic-setting procedure. Snap-on, printed pages 42–43.If a scan tool cannot communicate, verify vehicle identification, power, connections and the appropriate diagnostic interface before concluding that the ECU has failed. Snap-on describes a wiring conflict involving some older VW/Audi radio replacements and the diagnostic K-line that can put the scan tool at risk. This is an application-specific possibility, not a universal EDC15 pinout or diagnosis; consult the correct wiring information. Snap-on, printed pages 154–156.

Sources

Snap-on Volkswagen/Audi Vehicle Communication Software Manual, EAZ0031B01E Rev. A, August 2013, printed pages 42–43, 136–139 and 154–156; independent PDF mirror; accessed 10 November 2026. Generic tool descriptions, with vehicle-dependent availability.Robert Bosch GmbH, Electronic Diesel Control (EDC), 2001, printed pages 50–56, 74 and 78–80; independent PDF mirror; accessed 10 November 2026. The general control descriptions cover more than EDC15.Saab Workshop Information System, 2001 9-3 D223L, EDC 15 brief description; independent reproduction; accessed 10 November 2026.Snap-on Volkswagen/Audi Vehicle Communication Software Manual, EAZ0031B01E Rev. A, August 2013, printed pages 136–139; independent PDF mirror; accessed 10 November 2026. Generic tool descriptions, with vehicle-dependent availability.Robert Bosch GmbH, Electronic Diesel Control (EDC), 2001, printed pages 50–56 and 74; independent PDF mirror; accessed 10 November 2026. The general control descriptions cover more than EDC15.Saab Workshop Information System, 2001 9-3 D223L, EDC 15 brief description; independent reproduction; accessed 10 November 2026.

Rendered revisions

Open each version to inspect formatting, tables and photographs.

Revision 1: EDC15 diagnostic data and troubleshooting

Scope

Diagnostic tools can expose requests, calculated quantities, limits, sensor readings and actuator states. Their names do not prove which maps exist or that an indicated quantity was physically measured. Availability, units and meaning depend on the ECU, vehicle and tool. The examples below use the diesel parameter descriptions in the Snap-on Volkswagen/Audi manual, printed pages 136–139; the manual does not establish that each value exists on every EDC15 or every diesel.

Fuel quantity and interventions

  • Injection quantity: an indicated quantity for the operating condition, commonly displayed in milligrams per cylinder stroke in the manual. “Desired” is described there as a permissible quantity after corrections; check the exact tool’s definition before treating it as a physical measurement.
  • Driver, torque and smoke quantities: the manual distinguishes a driver-related request, an engine-speed/load-related torque limitation and a smoke-related limitation. Comparing available values under the same conditions can help identify which demand or restriction is relevant; it does not prove a universal selection order.
  • Cruise, traction control and automatic-transmission quantities: the same manual lists separate quantities associated with cruise control, traction control and transmission-related torque intervention. These are conditional on the vehicle and equipment.
  • Start quantity: a separate quantity may be reported during starting. Do not compare a starting value directly with a warm driving value without checking operating state and units.

If a request is higher than a reported limit, investigate the conditions that make that limit relevant before changing a calibration. Limits can protect hardware or manage smoke, and other corrections may still apply. Snap-on, printed pages 137–139; Bosch, printed page 53.

Air, boost and temperatures

The Snap-on manual lists desired and actual boost, intake-air temperature, coolant and fuel temperature, and desired and actual air-mass readings for its covered vehicles. Compare values only in the same operating conditions and confirm whether pressure is absolute or relative to atmosphere. A pressure reading is not a substitute for measured air mass; EGR, restrictions, leaks, sensor issues and control response can affect interpretation.

The manual describes substitute values for certain sensor failures in its examples. Bosch likewise explains that fallback strategies differ by vehicle manufacturer. A plausible displayed value can therefore be a substitute: review fault codes and the relevant service information before assuming the sensor is working. Snap-on, printed pages 136–138; Bosch, printed page 74.

Timing and cylinder balance

Where the actual application provides them, compare desired and actual start-of-delivery or start-of-injection data with their stated units and reference. Snap-on describes a needle-lift-feedback example, while Bosch also documents pump timing-device and unit-injector BIP feedback. The named event and feedback mechanism are not interchangeable. See EDC15 injection systems and timing feedback.

Cylinder injection-difference or smooth-running values can show how the controller is compensating between cylinders. Bosch describes using crankshaft-speed variation to adjust individual cylinder quantities; Snap-on lists example cylinder-difference parameters. A correction is a control response, not a diagnosis of a particular injector or mechanical fault. Check the applicable test conditions, reference cylinder or average, units and vehicle-specific limits. Bosch, printed pages 52–53; Snap-on, printed pages 137–139.

Practical recording checklist

  1. Record the vehicle, engine, injection system, ECU hardware and software identifiers, diagnostic tool and the conditions under which the issue occurs.
  2. Save relevant fault codes and freeze-frame information where available. Record engine speed, temperature and operating state alongside live values.
  3. Compare available requests, limits and feedback at the same point in time. Include air mass, boost, temperatures and the timing or rail-pressure values appropriate to the actual hardware.
  4. Use the manufacturer’s procedure and specifications for that exact vehicle to investigate discrepancies. Recheck after a repair or calibration change; do not use a generic threshold as a pass/fail value.

For example, Saab’s 2001 9-3 D223L describes separate diagnostics in the VP44 pump and glow-control module that are reported to the engine ECU. That architecture must not be assumed for another EDC15 application. Saab WIS, 2001 9-3 D223L.

Sources

Revision 2: EDC15 diagnostic data and troubleshooting

Scope

Diagnostic tools can expose requests, calculated quantities, limits, sensor readings and actuator states. Their names do not prove which maps exist or that an indicated quantity was physically measured. Availability, units and meaning depend on the ECU, vehicle and tool. The examples below use the diesel parameter descriptions in the Snap-on Volkswagen/Audi manual, printed pages 136–139; the manual does not establish that each value exists on every EDC15 or every diesel.

Fuel quantity and interventions

  • Injection quantity: an indicated quantity for the operating condition, commonly displayed in milligrams per cylinder stroke in the manual. “Desired” is described there as a permissible quantity after corrections; check the exact tool’s definition before treating it as a physical measurement.
  • Driver, torque and smoke quantities: the manual distinguishes a driver-related request, an engine-speed/load-related torque limitation and a smoke-related limitation. Comparing available values under the same conditions can help identify which demand or restriction is relevant; it does not prove a universal selection order.
  • Cruise, traction control and automatic-transmission quantities: the same manual lists separate quantities associated with cruise control, traction control and transmission-related torque intervention. These are conditional on the vehicle and equipment.
  • Start quantity: a separate quantity may be reported during starting. Do not compare a starting value directly with a warm driving value without checking operating state and units.

If a request is higher than a reported limit, investigate the conditions that make that limit relevant before changing a calibration. Limits can protect hardware or manage smoke, and other corrections may still apply. Snap-on, printed pages 137–139; Bosch, printed page 53.

Air, boost and temperatures

The Snap-on manual lists desired and actual boost, intake-air temperature, coolant and fuel temperature, and desired and actual air-mass readings for its covered vehicles. Compare values only in the same operating conditions and confirm whether pressure is absolute or relative to atmosphere. A pressure reading is not a substitute for measured air mass; EGR, restrictions, leaks, sensor issues and control response can affect interpretation.

The manual describes substitute values for certain sensor failures in its examples. Bosch likewise explains that fallback strategies differ by vehicle manufacturer. A plausible displayed value can therefore be a substitute: review fault codes and the relevant service information before assuming the sensor is working. Snap-on, printed pages 136–138; Bosch, printed page 74.

Timing and cylinder balance

Where the actual application provides them, compare desired and actual start-of-delivery or start-of-injection data with their stated units and reference. Snap-on describes a needle-lift-feedback example, while Bosch also documents pump timing-device and unit-injector BIP feedback. The named event and feedback mechanism are not interchangeable. See EDC15 injection systems and timing feedback.

Cylinder injection-difference or smooth-running values can show how the controller is compensating between cylinders. Bosch describes using crankshaft-speed variation to adjust individual cylinder quantities; Snap-on lists example cylinder-difference parameters. A correction is a control response, not a diagnosis of a particular injector or mechanical fault. Check the applicable test conditions, reference cylinder or average, units and vehicle-specific limits. Bosch, printed pages 52–53; Snap-on, printed pages 137–139.

Practical recording checklist

  1. Record the vehicle, engine, injection system, ECU hardware and software identifiers, diagnostic tool and the conditions under which the issue occurs.
  2. Save relevant fault codes and freeze-frame information where available. Record engine speed, temperature and operating state alongside live values.
  3. Compare available requests, limits and feedback at the same point in time. Include air mass, boost, temperatures and the timing or rail-pressure values appropriate to the actual hardware.
  4. Use the manufacturer’s procedure and specifications for that exact vehicle to investigate discrepancies. Recheck after a repair or calibration change; do not use a generic threshold as a pass/fail value.

For example, Saab’s 2001 9-3 D223L describes separate diagnostics in the VP44 pump and glow-control module that are reported to the engine ECU. That architecture must not be assumed for another EDC15 application. Saab WIS, 2001 9-3 D223L.

Fault memory and scan-tool access

Bosch describes checks of sensor signal ranges and plausibility, actuator circuits and system response. In those general EDC examples a fault record can include its status and operating conditions when it occurred. Record available codes and freeze-frame information before clearing them. A code identifies a detected problem or implausibility; the sensor, wiring, supply and the conditions that enabled the test may all need checking. The checks and stored information vary by vehicle. Bosch, printed pages 78–80.

For its VW/Audi software, Snap-on says that the combined codes-and-data display may contain only a selection of available measuring groups and can refresh more slowly. A missing value in one screen therefore does not prove the ECU lacks it. In that tool, reading measuring-value blocks and entering basic settings are different operations; use the exact vehicle and tool instructions before running a functional or basic-setting procedure. Snap-on, printed pages 42–43.

If a scan tool cannot communicate, verify vehicle identification, power, connections and the appropriate diagnostic interface before concluding that the ECU has failed. Snap-on describes a wiring conflict involving some older VW/Audi radio replacements and the diagnostic K-line that can put the scan tool at risk. This is an application-specific possibility, not a universal EDC15 pinout or diagnosis; consult the correct wiring information. Snap-on, printed pages 154–156.

Sources