Tuning Wiki
Applies to

Check the hardware and software limits stated in this article.

Noise, detection and correction are different observations

These notes cover the VAG ME7.1/ME7.5 examples in the sources. Identify the engine, sensor arrangement, ECU software, firing order and logger definitions. A knock sensor measures structure-borne vibration, as Bosch's sensor description explains; the ECU processes a signal in the context of its configured detection strategy.

A long NefMoto knock-voltage discussion describes filtering, measurement windows and a learned noise reference. It cautions that a commonly logged diagnostic voltage represents a processed reference rather than a universal raw knock meter. Its absolute value cannot be compared against one generic voltage threshold for every engine and cylinder. Verify what the selected logger channel actually represents.

Per-cylinder ignition correction, a momentary knock-detection flag and learned knock adaptation are also different quantities. A correction can persist after the triggering event or reflect another active strategy. A short-lived flag can be missed between logger samples, so an unobserved flag is not proof that no knock occurred. Record sensor faults, speed, load, intake temperature, mixture, actual ignition and the relevant corrections together.

Sensor faults can produce safety retard

Volkswagen's Engine Management Systems self-study programme 840293, page 23, describes an ME7.1.1 example with knock sensors G61 and G66. It states that failure of one sensor invokes a safety retarded ignition angle for its affected cylinder group while control remains active for the other group. If both fail, the document describes emergency knock control with broad ignition retard and reduced available power. This is an example of a fault response, not a claim that every ME7 engine groups cylinders or responds identically.

That distinction matters when a log shows persistent retard: check fault codes, the affected sensor group and the relevant safety-retard state as well as per-cylinder knock correction. Volkswagen cautions that sensor mounting torque affects the signal; use the current repair information for the exact engine, mounting and fastener, rather than assuming a universal torque figure. A fault-free or inactive displayed correction alone does not validate the sensor or prove that combustion is knock-free.

Why a learned correction can follow an operating region

In Bosch's Alfa 2.0 ME7.3.1H function and data sheet, KRRA describes separate stored knock-adaptation cells for cylinders and load/speed regions. In that documented function, the boundaries use hysteresis when load or engine speed falls to avoid rapid switching between regions. A correction changing near a boundary can therefore depend on the route into an operating point as well as the point itself; it is not automatically evidence of a new knock event at that instant.

The same description distinguishes a detection-driven retard step from the later, conditional advance of a cylinder's correction through a counter. Thus a correction may remain after the initiating event, and recovery is not a direct count of knock events. This is an explanation of the cited Alfa strategy, not a claim that every ME7 uses the same state, map names or thresholds. Compare repeated runs with similar prior load and speed, retain adaptation and control-state information, and verify the logger's signal definition before interpreting the shape or attempting a calibration change.

Reported cases: leading cylinder, mechanical noise and sampling

In a forum-reported R32 case, exhaust-induced false knock was initially suspected because one cylinder repeatedly showed correction after an exhaust change. An optional leading-cylinder function and its cylinder-specific offset were later reported to explain the repeated correction in that software. The initial noise diagnosis was not established, and the forum report is not an independent combustion measurement.

The Audi 1.8T ME7.1 function description lists a leading-cylinder threshold and WKRLZOF offset; a separate Bosch ME7.3.1H Alfa sheet also lists leading-cylinder assignments. These documents establish that such a function exists in those examples, not that it is active or configured the same way in every ME7. Its purpose and conditions must be checked for the actual file.

Mechanical noise is a hypothesis, not a confirmed knock event. In a forum-reported lightweight clutch and flywheel case, gearbox rattle was suspected to be linked to a cylinder-specific idle misfire and knock correction. The symptom became intermittent and the suspected correction was not captured with the event, so the cause was not established. Compare cylinder misfire counters, ignition corrections, operating state and mechanical condition at the same time; distinguish an engine-speed-based misfire indication from knock-sensor processing. Do not suppress knock protection merely to make a trace look cleaner.

Check how ignition samples are produced. A sawtooth in one ignition output trace has been suggested in forum discussion to result from samples associated with different cylinders; a follow-up discusses differing knock corrections as one possible reason. Verify whether that behaviour applies to the chosen logger and ECU; compare per-cylinder corrections and relevant ignition stages before calling the trace anti-judder or treating it as noise. See ignition oscillations and anti-judder logging.

A useful investigation sequence

  1. Confirm the correct cylinder and bank mapping, faults, sensor mounting and wiring, fuel, operating point and any recent hardware changes. Compare repeatable events under matched conditions.
  2. Inspect all available cylinder corrections, actual ignition, relevant detection and adaptation state, and, where defined, leading-cylinder or safety-retard status. Validate channel definitions and sampling.
  3. Separate a repeatable mechanical vibration from a suspected combustion event using appropriate independent measurement and engine inspection. A reduction in displayed correction after changing detection settings is not evidence that knock has gone away.

Keep the detection, offsets and protective functions understood and functional while investigating. See ME7 ignition and knock reference, ignition coil dwell and engine knock. Forum conclusions are attributed reports and have not been independently vehicle-tested by this wiki.

Continue the conversation

If this topic interests you, consider joining the following forums. They host material referenced in this article.