This guide uses EcuTek's EA888 Evo4 calibration notes and COBB's Mk8 Volkswagen / 8Y Audi tuning and monitor lists to help interpret ignition timing and knock logs on supported Simos 19 applications. Tool names and features refer to those products and compatible software, not every Simos 19 controller. Identify the ECU, calibration and logger before applying a definition.
Base timing, reference and final timing
EcuTek's Evo4 guide describes separate Ignition Angle and Ignition Ref Angle map sets. It describes the reference angle as a reference maximum on high-octane fuel that also contributes to ignition-efficiency calculations. It describes the other set as the ignition setting to be calibrated. A reference map is not a measured final spark angle or a direct instruction to advance the ignition.
Both sets are indexed by engine state in the EcuTek example, including intake-flap state, valve lift and cam positions. Consequently, an ignition table that looks relevant may not be the one active during a given portion of a log. Match axes, units and indexing to the exact software. COBB also describes combustion-mode-dependent ignition corrections for its Mk8 / 8Y definitions; those corrections and other interventions mean a base value alone does not establish final ignition timing. [COBB tuning guide]
For a concrete indexing example, EcuTek’s Evo4 guide describes a wide-open-pedal condition with the intake flaps open and camshafts at their end positions as using the index Open flap / No Lift / In1 / Ex1. It contrasts this with a light-load example using a different index for the reference air-charge table. These are illustrations of its defined calibration, not a universal mapping of all engine states to table names. Verify the logged flap, lift and cam state, and the definition for the actual file, before concluding which table was used.
The same guide says its RaceROM version 3 provides four map-switch-mode ignition variants that replace nine high- and low-lift, flap-open maps. That replacement is a product- and feature-file-specific behaviour, not a description of an unmodified ECU or every RaceROM version. Confirm the feature-file version, enable state and selected mode alongside the logged operating conditions.
More advance is not automatically more power. COBB warns that if additional timing produces no meaningful torque increase, extra cylinder pressure can impose unnecessary stress. Optimum timing and knock margin depend on fuel, hardware and conditions, so the cited material does not supply a transferable timing number or a universally safe knock-retard limit.
Knock feedback and its limits
EcuTek describes short- and long-term corrections, knock windows and individual-cylinder control in its Mk8 example. COBB notes that one cylinder's correction does not show the whole engine and identifies per-cylinder knock-retard monitors. A correction is an ECU response in the context of its calibration; compare all available cylinders and the operating conditions instead of interpreting a single isolated number as a diagnosis.
A lack of displayed correction does not prove the absence of knock, establish maximum-brake-torque timing, or guarantee that pre-ignition would be detected. Knock-sensor voltage is not itself a direct calibrated measurement of cylinder pressure, and logged values depend on the sensor, ECU, signal processing and tool. Do not make knock detection less sensitive merely to make a log look cleaner; changes to detection windows or response need proper validation.
A practical log review
- Record the ECU and calibration identifiers, tool version, hardware configuration and fuel actually in the tank. Review fault codes and investigate misfire, fuel supply and ignition-system problems before changing timing.
- On a healthy baseline and in a suitable controlled test, record engine speed, gear, throttle or pedal, air charge or manifold pressure, intake temperature and lambda target and actual. Where available add combustion mode, cam positions and valve-lift or flap state so that runs can be compared under similar conditions.
- Log base and final ignition where available, plus all four cylinder timing and knock-retard channels. COBB's fast-monitor list names Ignition Timing Cyl 1–4 and Knock Retard Cylinder 1–4; EcuTek suggests Ignition Angle Base, ignition timing cylinders 1–4 and Knock Retard 1–4. Channel availability and signs depend on the tool and software. Check their descriptions and units before comparing values.
- Compare repeated events at similar speed, air charge, fuel and temperature. A correction concentrated in one cylinder suggests a different investigation from a consistent change across cylinders, but neither pattern establishes a cause by itself. Check the timestamp, sampling rate and transient conditions; investigate fuel, temperature, plugs, coils, mechanical condition and sensor issues as appropriate.
- Use a suitable dyno and controlled comparison when assessing torque response. The ECU's estimated torque is useful context, not an independent measurement that proves a timing change improved output. Preserve protection and reassess if lambda, fuel pressure or temperatures do not track as expected.
COBB separately lists per-cylinder knock voltage, knock window state and an adapted average. These are distinct from per-cylinder retard; the monitor list alone does not define their thresholds or establish that a value on one car is acceptable on another. COBB distinguishes its older pre-CCF monitor list from its fast-monitor list, so confirm the correct logger and tune generation. [COBB monitor list]
Example: compare the cylinders
RacingLine’s RSR-2023-07A v1.03 release includes simplified VCDS samples from its Golf 8 R with its Stage 1+ hardware and 98 RON calibration. In one displayed row at 4,997 rpm it reports ignition angle 5.5° and a knock correction of −1.125° in all four displayed cylinder channels. At 6,538 rpm the row reports ignition angle 13°, with three knock channels at zero and one at −3.375°. These are two samples from a supplier’s particular test and tune, not universal limits, proof of knock severity, or evidence of a fault in the latter cylinder. Check the original trace, channel descriptions and test conditions before interpreting a correction or comparing it with another logger.
The example illustrates why an overall ignition number and a single cylinder cannot describe all four corrections. Compare the full time history and repeatable load, fuel, temperature, lambda and pressure data, and investigate a persistent cylinder-specific pattern using the appropriate diagnostics. The release covers specific ECU IDs across Simos 19.3/19.6 but does not assign a variant to each listed ID. Its Stage 1+ example specifies its R600 intake and intercooler; neither the observed values nor that hardware combination defines a safe target for another car.
RaceROM is a separate product feature
EcuTek describes map-switch-mode ignition maps and ethanol-content blending in its EA888 Evo4 RaceROM documentation. These require the applicable RaceROM patch and supported installation; they are not evidence that an unmodified ECU has the same feature. Confirm the active mode, sensor and blending setup before comparing logs from different fuels or modes. See the port-injection and ethanol guide for that product's fuel-system context.
Sources
- EcuTek: VW AG EA888 Evo4 Engine Tuning, ignition and knock sections. Product-specific map names, indexing and suggested logging.
- EcuTek: VW AG EA888 Evo4 RaceROM v1, flex-fuel ignition section. Product-specific blending and patch feature.
- COBB: MK8 Volkswagen / 8Y Audi Tuning Guide, ignition timing and knock control. Product-specific calibration discussion.
- COBB: Engine Monitor List MK8 Vehicles, pre-CCF and fast logging sections. Product-specific monitor names.