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
Tuning
Parent
Bosch Motronic 7
Applies to
Bosch ME7.1, Bosch ME7.5
Tool groups
None
Manufacturers
Audi, Volkswagen

Changes from revision 1 to revision 1

Removed text is struck through; added text is highlighted.

What changes when fluid is injected?

Water/methanol injection adds a separate delivery system to the engine. Methanol is also a fuel; the blend, amount delivered, spray distribution, temperature and operating conditions all affect the outcome. A lambda sensor reports exhaust oxygen, while an AFR display applies a chosen fuel reference. A gasoline-equivalent AFR display does not by itself identify how much gasoline or methanol reached each cylinder. Verify the sensor, display reference and ECU control state.

The NefMoto S4 water/methanol discussion raises these issues but contains different proposals and some aggressive example calibrations. Its later exchange distinguishes pure methanol from a smaller addition to gasoline. Do not copy timing, lambda, boost, nozzle sizes or map changes from that discussion: determine actual delivery and component limits for the vehicle and fuel.

Know what each fault signal can detect

EvidenceWhat it can and cannot establish Tank levelCan warn of low supply when the level sensor and wiring work; a full tank does not establish pump operation, flow or nozzle condition. Pump command or electrical faultShows a command or a monitored electrical condition; it does not by itself prove the expected fluid reached the intake. Fluid pressureCan identify some supply problems, depending on where it is measured. Pressure alone may not establish nozzle flow or distribution. Measured flowCan detect flow outside the calibrated window at the sensor. Sensor location, delays, leaks or restrictions downstream, and distribution among cylinders remain important. Intake temperature or knock correctionUseful operating data, but not a direct measurement of fluid delivery. A normal-looking value does not prove that injection is working.

For a concrete product example, AEM's 30-3020 failsafe instructions describe monitoring measured flow against injection command and configuring outputs when the observed flow is outside an expected range. Its limits, wiring and diagnostic coverage are product-specific. A separate NefMoto discussion suggests intake-temperature-based corrections; temperature is indirect and should not be treated as proof that the pump, nozzle or all cylinders received fluid.

Follow the fault all the way to the engine

Identify the controller, installed sensors, nozzle locations, electrical supply, fluid mixture and the actual ME7 software. Establish what happens when the key is cycled and when inputs or outputs are disconnected.Document the expected response to low level, pump or electrical faults, insufficient or excessive flow and sensor or wiring faults. The required warning or control action must be connected and verified; a feature in a controller's brochure does not prove it is active on the car.Establish a validated operating strategy for absent injection and how the car reaches it. Disabling a boost-control solenoid, for example, does not guarantee a particular pressure unless the actual valve, plumbing, wastegate and ECU behaviour have been checked.With equipment and conditions appropriate to the installation, verify the complete fault response and its recovery, including response delay and any transition in progress. Recheck mixture, ignition, pressure and fault status rather than assuming a warning light alone protects the engine.

Knock control, intake temperature and the ECU's normal component protections remain relevant, but none is a substitute for verifying delivery and the intended fault response. For the boost hardware, see ME7 wastegate and boost-control hardware. For exhaust temperature context see ME7.1 S4 exhaust temperature and enrichment. The forum examples are reported discussions; this wiki has not tested their individual installations.

Rendered revisions

Open each version to inspect formatting, tables and photographs.

Revision 1: ME7 water methanol injection and fault response

What changes when fluid is injected?

Water/methanol injection adds a separate delivery system to the engine. Methanol is also a fuel; the blend, amount delivered, spray distribution, temperature and operating conditions all affect the outcome. A lambda sensor reports exhaust oxygen, while an AFR display applies a chosen fuel reference. A gasoline-equivalent AFR display does not by itself identify how much gasoline or methanol reached each cylinder. Verify the sensor, display reference and ECU control state.

The NefMoto S4 water/methanol discussion raises these issues but contains different proposals and some aggressive example calibrations. Its later exchange distinguishes pure methanol from a smaller addition to gasoline. Do not copy timing, lambda, boost, nozzle sizes or map changes from that discussion: determine actual delivery and component limits for the vehicle and fuel.

Know what each fault signal can detect

EvidenceWhat it can and cannot establish
Tank levelCan warn of low supply when the level sensor and wiring work; a full tank does not establish pump operation, flow or nozzle condition.
Pump command or electrical faultShows a command or a monitored electrical condition; it does not by itself prove the expected fluid reached the intake.
Fluid pressureCan identify some supply problems, depending on where it is measured. Pressure alone may not establish nozzle flow or distribution.
Measured flowCan detect flow outside the calibrated window at the sensor. Sensor location, delays, leaks or restrictions downstream, and distribution among cylinders remain important.
Intake temperature or knock correctionUseful operating data, but not a direct measurement of fluid delivery. A normal-looking value does not prove that injection is working.

For a concrete product example, AEM's 30-3020 failsafe instructions describe monitoring measured flow against injection command and configuring outputs when the observed flow is outside an expected range. Its limits, wiring and diagnostic coverage are product-specific. A separate NefMoto discussion suggests intake-temperature-based corrections; temperature is indirect and should not be treated as proof that the pump, nozzle or all cylinders received fluid.

Follow the fault all the way to the engine

  1. Identify the controller, installed sensors, nozzle locations, electrical supply, fluid mixture and the actual ME7 software. Establish what happens when the key is cycled and when inputs or outputs are disconnected.
  2. Document the expected response to low level, pump or electrical faults, insufficient or excessive flow and sensor or wiring faults. The required warning or control action must be connected and verified; a feature in a controller's brochure does not prove it is active on the car.
  3. Establish a validated operating strategy for absent injection and how the car reaches it. Disabling a boost-control solenoid, for example, does not guarantee a particular pressure unless the actual valve, plumbing, wastegate and ECU behaviour have been checked.
  4. With equipment and conditions appropriate to the installation, verify the complete fault response and its recovery, including response delay and any transition in progress. Recheck mixture, ignition, pressure and fault status rather than assuming a warning light alone protects the engine.

Knock control, intake temperature and the ECU's normal component protections remain relevant, but none is a substitute for verifying delivery and the intended fault response. For the boost hardware, see ME7 wastegate and boost-control hardware. For exhaust temperature context see ME7.1 S4 exhaust temperature and enrichment. The forum examples are reported discussions; this wiki has not tested their individual installations.

Revision 1: ME7 water methanol injection and fault response

What changes when fluid is injected?

Water/methanol injection adds a separate delivery system to the engine. Methanol is also a fuel; the blend, amount delivered, spray distribution, temperature and operating conditions all affect the outcome. A lambda sensor reports exhaust oxygen, while an AFR display applies a chosen fuel reference. A gasoline-equivalent AFR display does not by itself identify how much gasoline or methanol reached each cylinder. Verify the sensor, display reference and ECU control state.

The NefMoto S4 water/methanol discussion raises these issues but contains different proposals and some aggressive example calibrations. Its later exchange distinguishes pure methanol from a smaller addition to gasoline. Do not copy timing, lambda, boost, nozzle sizes or map changes from that discussion: determine actual delivery and component limits for the vehicle and fuel.

Know what each fault signal can detect

EvidenceWhat it can and cannot establish
Tank levelCan warn of low supply when the level sensor and wiring work; a full tank does not establish pump operation, flow or nozzle condition.
Pump command or electrical faultShows a command or a monitored electrical condition; it does not by itself prove the expected fluid reached the intake.
Fluid pressureCan identify some supply problems, depending on where it is measured. Pressure alone may not establish nozzle flow or distribution.
Measured flowCan detect flow outside the calibrated window at the sensor. Sensor location, delays, leaks or restrictions downstream, and distribution among cylinders remain important.
Intake temperature or knock correctionUseful operating data, but not a direct measurement of fluid delivery. A normal-looking value does not prove that injection is working.

For a concrete product example, AEM's 30-3020 failsafe instructions describe monitoring measured flow against injection command and configuring outputs when the observed flow is outside an expected range. Its limits, wiring and diagnostic coverage are product-specific. A separate NefMoto discussion suggests intake-temperature-based corrections; temperature is indirect and should not be treated as proof that the pump, nozzle or all cylinders received fluid.

Follow the fault all the way to the engine

  1. Identify the controller, installed sensors, nozzle locations, electrical supply, fluid mixture and the actual ME7 software. Establish what happens when the key is cycled and when inputs or outputs are disconnected.
  2. Document the expected response to low level, pump or electrical faults, insufficient or excessive flow and sensor or wiring faults. The required warning or control action must be connected and verified; a feature in a controller's brochure does not prove it is active on the car.
  3. Establish a validated operating strategy for absent injection and how the car reaches it. Disabling a boost-control solenoid, for example, does not guarantee a particular pressure unless the actual valve, plumbing, wastegate and ECU behaviour have been checked.
  4. With equipment and conditions appropriate to the installation, verify the complete fault response and its recovery, including response delay and any transition in progress. Recheck mixture, ignition, pressure and fault status rather than assuming a warning light alone protects the engine.

Knock control, intake temperature and the ECU's normal component protections remain relevant, but none is a substitute for verifying delivery and the intended fault response. For the boost hardware, see ME7 wastegate and boost-control hardware. For exhaust temperature context see ME7.1 S4 exhaust temperature and enrichment. The forum examples are reported discussions; this wiki has not tested their individual installations.