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

Changes from revision 4 to revision 5

Removed text is struck through; added text is highlighted.

Scope and symptom

These notes concern VAG ME7.1/ME7.5 examples after a lightweight flywheel, clutch, mount or related hardware change. Identify the ECU and software, transmission, clutch switch, flywheel and clutch specification, injectors, fuel and previous calibration changes. Similar stalls or oscillations can have different causes.

At the same engine speed, a lower-inertia flywheel stores less rotational energy and can change the speed response when the clutch loads or unloads the engine. The clutch's engagement characteristics and drivetrain compliance also affect the event. This does not mean every light-flywheel car needs a particular controller change, or that the flywheel alone caused the symptom.

For the underlying mechanics and practical hardware choices, see flywheel inertia and engine response, dual-mass to single-mass conversions and the complete flywheel section.

For the hardware and operation of a friction clutch, see clutch types and operation.

Separate the operating events

EventWhat to distinguish Stationary idleWarm or cold engine, clutch pedal state, electrical and air-conditioning loads, actual versus target speed, mixture, air leaks and injector behaviour. Low-speed clutch take-upPedal and clutch-switch states, gear, vehicle speed, throttle, speed and torque response. A stable idle before take-up does not establish stability while the clutch loads the engine. Coasting, declutching and stoppingWhether overrun fuel cut was active and when fuel resumed, the idle-control state, gear and speed signals, target speed and the subsequent undershoot or stall.

Use controlled, repeatable conditions and record the event leading up to and after the symptom. Check clutch and brake switch operation, faults, air and exhaust leaks, fuel pressure, injector data and lambda before attributing the behaviour to a controller gain. Engine mechanical faults or a slipping or dragging clutch can produce similar symptoms.

What the available evidence establishesThe evidence for a controller-side fix is limited to tuner reports on a public forum, not controlled comparisons. In a modified ME7.5 case, a very light flywheel and an aggressive clutch were reported to cause oscillation during take-up. The logs reportedly showed load request, throttle and ignition moving together while the pedal was held, and a change to the rolling-speed proportional-control parameter PVDNV was reported to resolve that particular oscillation. It has not been reproduced across other cars.Other reports in the same thread describe different stalling and fueling issues: an aggressive controller change improved one event but introduced oscillation elsewhere, and the eventual improvement was attributed to idle-controller calibration after several intervening changes. No single transferable value emerges. The reports also indicate that short-pulse fueling and the timing of fuel resumption can mimic or compound a control problem.The Bosch ME7.3.1H Alfa function sheet (manufacturer documentation) labels PVDN and PVDNV as stationary and rolling proportional-gain references respectively. That supports the distinction, but it is a different application: names, axes, active conditions and control structure must be verified in the actual VAG file. Do not copy its values or assume raising either gain is the correct response.What the forum cases establishIn a modified ME7.5 case, a tuner reported oscillation during take-up with a very light flywheel and aggressive clutch. The logs reportedly showed load request, throttle and ignition moving together while the pedal was held. The tuner reported that a change to the rolling-speed proportional-control parameter PVDNV resolved that particular oscillation. This was an owner/tuner report, not a controlled comparison across other cars.A later participant in the same thread reported different stalling and fueling issues; an aggressive controller change improved one event but introduced oscillation elsewhere. In a later follow-up, that participant attributed the eventual improvement to idle-controller calibration after several intervening changes. The thread does not isolate one transferable value. It also warns that short-pulse fueling and the timing of fuel resumption can mimic or compound a control problem.The separate Bosch ME7.3.1H Alfa function sheet labels PVDN and PVDNV as stationary and rolling proportional-gain references respectively. That supports the distinction, but it is a different application: names, axes, active conditions and control structure must be verified in the actual VAG file. Do not copy its values or assume raising either gain is the correct response.

Capture control state and fuel return

Where the matching definition makes them available, record engine and target speed, vehicle speed, pedal and actual throttle, clutch and brake states, gear, idle and idle-controller states, requested and actual load or torque, final ignition, misfire information, requested and measured lambda, injector-related signals and fuel-cut state. Use focused channel sets and retain sampling rates and timestamps; adding too many channels can obscure a short event.

The Audi 132 kW ME7.1 function description, LLRMD, distinguishes the idle-control-active condition B_llrein from other operating conditions, including a rolling-vehicle condition. These flags describe different states, not interchangeable diagnoses. The same document's BBSAWE describes gear- and temperature-dependent fuel-cut/resumption logic. A nonzero calculated injection-time signal does not by itself prove a cylinder was injected; see overrun fuel-cut and injector log signals.

Preserve diagnosis as well as drivability. In that Audi implementation, Bosch explicitly warns against generally preventing overrun fuel cut in the function's gear-0 condition because vehicle-speed diagnosis would no longer be possible. This is a specific documented software constraint; gear 0 is a function state and should not automatically be equated with a physical neutral switch in every vehicle. Trace the exact logic before considering any change.

After resolving a demonstrated cause, verify stationary and rolling behaviour, take-up, overrun recovery and other relevant temperature and accessory-load conditions. Related: idle ignition and torque reserve, injector changes and idle diagnosis and gear recognition. Forum-reported outcomes have not been independently reproduced by this wiki.After resolving a demonstrated cause, verify stationary and rolling behaviour, take-up, overrun recovery and other relevant temperature and accessory-load conditions. Related: idle ignition and torque reserve, injector changes and idle diagnosis and gear recognition. Forum outcomes have not been independently reproduced by this wiki.

Rendered revisions

Open each version to inspect formatting, tables and photographs.

Revision 4: ME7 lightweight flywheel clutch and stalling diagnosis

Scope and symptom

These notes concern VAG ME7.1/ME7.5 examples after a lightweight flywheel, clutch, mount or related hardware change. Identify the ECU and software, transmission, clutch switch, flywheel and clutch specification, injectors, fuel and previous calibration changes. Similar stalls or oscillations can have different causes.

At the same engine speed, a lower-inertia flywheel stores less rotational energy and can change the speed response when the clutch loads or unloads the engine. The clutch's engagement characteristics and drivetrain compliance also affect the event. This does not mean every light-flywheel car needs a particular controller change, or that the flywheel alone caused the symptom.

For the underlying mechanics and practical hardware choices, see flywheel inertia and engine response, dual-mass to single-mass conversions and the complete flywheel section.

For the hardware and operation of a friction clutch, see clutch types and operation.

Separate the operating events

EventWhat to distinguish
Stationary idleWarm or cold engine, clutch pedal state, electrical and air-conditioning loads, actual versus target speed, mixture, air leaks and injector behaviour.
Low-speed clutch take-upPedal and clutch-switch states, gear, vehicle speed, throttle, speed and torque response. A stable idle before take-up does not establish stability while the clutch loads the engine.
Coasting, declutching and stoppingWhether overrun fuel cut was active and when fuel resumed, the idle-control state, gear and speed signals, target speed and the subsequent undershoot or stall.

Use controlled, repeatable conditions and record the event leading up to and after the symptom. Check clutch and brake switch operation, faults, air and exhaust leaks, fuel pressure, injector data and lambda before attributing the behaviour to a controller gain. Engine mechanical faults or a slipping or dragging clutch can produce similar symptoms.

What the forum cases establish

In a modified ME7.5 case, a tuner reported oscillation during take-up with a very light flywheel and aggressive clutch. The logs reportedly showed load request, throttle and ignition moving together while the pedal was held. The tuner reported that a change to the rolling-speed proportional-control parameter PVDNV resolved that particular oscillation. This was an owner/tuner report, not a controlled comparison across other cars.

A later participant in the same thread reported different stalling and fueling issues; an aggressive controller change improved one event but introduced oscillation elsewhere. In a later follow-up, that participant attributed the eventual improvement to idle-controller calibration after several intervening changes. The thread does not isolate one transferable value. It also warns that short-pulse fueling and the timing of fuel resumption can mimic or compound a control problem.

The separate Bosch ME7.3.1H Alfa function sheet labels PVDN and PVDNV as stationary and rolling proportional-gain references respectively. That supports the distinction, but it is a different application: names, axes, active conditions and control structure must be verified in the actual VAG file. Do not copy its values or assume raising either gain is the correct response.

Capture control state and fuel return

Where the matching definition makes them available, record engine and target speed, vehicle speed, pedal and actual throttle, clutch and brake states, gear, idle and idle-controller states, requested and actual load or torque, final ignition, misfire information, requested and measured lambda, injector-related signals and fuel-cut state. Use focused channel sets and retain sampling rates and timestamps; adding too many channels can obscure a short event.

The Audi 132 kW ME7.1 function description, LLRMD, distinguishes the idle-control-active condition B_llrein from other operating conditions, including a rolling-vehicle condition. These flags describe different states, not interchangeable diagnoses. The same document's BBSAWE describes gear- and temperature-dependent fuel-cut/resumption logic. A nonzero calculated injection-time signal does not by itself prove a cylinder was injected; see overrun fuel-cut and injector log signals.

Preserve diagnosis as well as drivability. In that Audi implementation, Bosch explicitly warns against generally preventing overrun fuel cut in the function's gear-0 condition because vehicle-speed diagnosis would no longer be possible. This is a specific documented software constraint; gear 0 is a function state and should not automatically be equated with a physical neutral switch in every vehicle. Trace the exact logic before considering any change.

After resolving a demonstrated cause, verify stationary and rolling behaviour, take-up, overrun recovery and other relevant temperature and accessory-load conditions. Related: idle ignition and torque reserve, injector changes and idle diagnosis and gear recognition. Forum outcomes have not been independently reproduced by this wiki.

Revision 5: ME7 lightweight flywheel clutch and stalling diagnosis

Scope and symptom

These notes concern VAG ME7.1/ME7.5 examples after a lightweight flywheel, clutch, mount or related hardware change. Identify the ECU and software, transmission, clutch switch, flywheel and clutch specification, injectors, fuel and previous calibration changes. Similar stalls or oscillations can have different causes.

At the same engine speed, a lower-inertia flywheel stores less rotational energy and can change the speed response when the clutch loads or unloads the engine. The clutch's engagement characteristics and drivetrain compliance also affect the event. This does not mean every light-flywheel car needs a particular controller change, or that the flywheel alone caused the symptom.

For the underlying mechanics and practical hardware choices, see flywheel inertia and engine response, dual-mass to single-mass conversions and the complete flywheel section.

For the hardware and operation of a friction clutch, see clutch types and operation.

Separate the operating events

EventWhat to distinguish
Stationary idleWarm or cold engine, clutch pedal state, electrical and air-conditioning loads, actual versus target speed, mixture, air leaks and injector behaviour.
Low-speed clutch take-upPedal and clutch-switch states, gear, vehicle speed, throttle, speed and torque response. A stable idle before take-up does not establish stability while the clutch loads the engine.
Coasting, declutching and stoppingWhether overrun fuel cut was active and when fuel resumed, the idle-control state, gear and speed signals, target speed and the subsequent undershoot or stall.

Use controlled, repeatable conditions and record the event leading up to and after the symptom. Check clutch and brake switch operation, faults, air and exhaust leaks, fuel pressure, injector data and lambda before attributing the behaviour to a controller gain. Engine mechanical faults or a slipping or dragging clutch can produce similar symptoms.

What the available evidence establishes

The evidence for a controller-side fix is limited to tuner reports on a public forum, not controlled comparisons. In a modified ME7.5 case, a very light flywheel and an aggressive clutch were reported to cause oscillation during take-up. The logs reportedly showed load request, throttle and ignition moving together while the pedal was held, and a change to the rolling-speed proportional-control parameter PVDNV was reported to resolve that particular oscillation. It has not been reproduced across other cars.

Other reports in the same thread describe different stalling and fueling issues: an aggressive controller change improved one event but introduced oscillation elsewhere, and the eventual improvement was attributed to idle-controller calibration after several intervening changes. No single transferable value emerges. The reports also indicate that short-pulse fueling and the timing of fuel resumption can mimic or compound a control problem.

The Bosch ME7.3.1H Alfa function sheet (manufacturer documentation) labels PVDN and PVDNV as stationary and rolling proportional-gain references respectively. That supports the distinction, but it is a different application: names, axes, active conditions and control structure must be verified in the actual VAG file. Do not copy its values or assume raising either gain is the correct response.

Capture control state and fuel return

Where the matching definition makes them available, record engine and target speed, vehicle speed, pedal and actual throttle, clutch and brake states, gear, idle and idle-controller states, requested and actual load or torque, final ignition, misfire information, requested and measured lambda, injector-related signals and fuel-cut state. Use focused channel sets and retain sampling rates and timestamps; adding too many channels can obscure a short event.

The Audi 132 kW ME7.1 function description, LLRMD, distinguishes the idle-control-active condition B_llrein from other operating conditions, including a rolling-vehicle condition. These flags describe different states, not interchangeable diagnoses. The same document's BBSAWE describes gear- and temperature-dependent fuel-cut/resumption logic. A nonzero calculated injection-time signal does not by itself prove a cylinder was injected; see overrun fuel-cut and injector log signals.

Preserve diagnosis as well as drivability. In that Audi implementation, Bosch explicitly warns against generally preventing overrun fuel cut in the function's gear-0 condition because vehicle-speed diagnosis would no longer be possible. This is a specific documented software constraint; gear 0 is a function state and should not automatically be equated with a physical neutral switch in every vehicle. Trace the exact logic before considering any change.

After resolving a demonstrated cause, verify stationary and rolling behaviour, take-up, overrun recovery and other relevant temperature and accessory-load conditions. Related: idle ignition and torque reserve, injector changes and idle diagnosis and gear recognition. Forum-reported outcomes have not been independently reproduced by this wiki.