Applicability: The engineering identifiers below are examples from the community SC8S5031_C_OEM Simos 18.1 cross-reference, not universal map definitions. Match the exact hardware, software, A2L, axes, scaling, units, cylinder indexing and configuration before using them; extracted descriptions can contain errors. The Volkswagen diagnostic bulletin has wider vehicle applicability and is not a Simos-specific calibration definition. SC8S5031 community reference.
What the ECU is looking for
The engine-roughness calculation uses crankshaft segment timing to derive roughness-related quantities; the misfire function compares detection criteria with operating-dependent thresholds. The SC8S5031 roughness reference describes static, dynamic and curvature components and per-cylinder signals. Roughness is an inference from crankshaft behaviour, not a direct view of combustion. Driveline oscillation, interventions, signal faults and operating-state exclusions can affect interpretation.
A detection threshold is part of the monitoring strategy, not a power target. Changing or disabling monitoring to hide a count can mask real combustion problems or catalyst-damaging misfires. No universal safe threshold or calibration value follows from these names.
Threshold and correction maps
The following examples come from the SC8S5031 misfire application reference and misfire detection reference. Confirm each selector and table in the target file:
ip_thd_afs_er[3][3]: AFS-mode engine-roughness detection threshold, with engine speednand misfire loadload_misaxes. The array selection uses transmission-type and combustion-mode indices; do not infer the index mapping for another file.ip_thd_afs_er_is[3][3]: corresponding AFS idle-speed, no-gear threshold;ip_thd_afs_er_is_dri[3][3]is a separately indexed idle-related variant. The extracted label does not establish the exact_driselection conditions.ip_fac_thd_app_er_toil: engine-roughness threshold weighting for oil-temperature effects, against engine speed and oil temperature.ip_fac_thd_app_er_cyl_knk: threshold weighting to compensate for the influence of knock-control spark retard, against engine speed and misfire load. It is a misfire-detection correction, not an ignition target or knock limit.ip_fac_thd_iv_er: speed-dependent threshold adaptation when cylinder cut-off is active;ip_fac_thd_tco_eris a coolant-temperature-dependent threshold factor. Verify the active path and units in the matched definition.
Runtime signals and limitations
In the detection reference, lv_det_thd_delta, lv_det_thd_fil and lv_det_thd_mis describe separate single-event criteria before the fade-out test; lv_det_mis describes a confirmed single event after that test. thd_er_clc is a calculated threshold measurement. These are runtime measurements, not editable threshold maps or necessarily the names exposed by a scan tool. Availability, scaling, sampling rate and cylinder mapping depend on logger and software.
Check the active detection state, cut interventions and the number of events observed over a comparable period before interpreting a quiet log. The Simos.app Main Patch guide states that its spark-and-fuel-cut launch and rolling anti-lag implementation pauses misfire detection. This is a product-specific behaviour, not a claim about every launch strategy: absence of misfire reports during that intervention cannot prove that combustion was normal.
Diagnostic workflow
- Record ECU software, fuel, modifications, trouble codes and freeze-frame conditions, including rpm, load, gear, temperatures and when the symptom occurs. Compare the same operating conditions before and after any repair.
- Volkswagen TSB 01-16-13, transaction 2033805/10, identifies P0300 as random/multiple misfire, P0301–P0308 as cylinder-specific misfires, and P130A as Hide Cylinder. The bulletin applies to the listed 2008–2025 gasoline VW vehicles, excluding Routan and ID.4. Address other logged faults first and check the bulletin and repair information for the vehicle.
- Use cylinder-specific evidence and guided diagnostics to investigate connections, grounds, fuel quality, plugs, coils, injectors and mechanical causes as appropriate. VW describes controlled component swaps and checking whether the fault moves; a P0300 alone does not identify a defective component. Follow the correct repair procedure for high-pressure fuel components.
- Compare commanded and actual lambda and fuel pressure, load, timing and cylinder-specific events where supported, while noting cut and combustion-mode states. A knock-correction value is a different measurement and does not identify a misfire cause. Verify the repair under the originally recorded conditions.
Owner-reported load-dependent example
A 2017 Mk7 Golf R owner reported intermittent multi-cylinder misfires primarily under light load and an EPC/“Hide Cylinder” event in Sport mode. They reported no improvement after changing plugs, coils and the PCV valve; a fuel replacement helped temporarily. They later reported an improvement after intake-valve cleaning and injector replacement performed together. ECU software and independent diagnostic confirmation were not provided, and the combined work does not establish whether deposits, an injector or another change caused the symptoms. Compare the operating conditions and perform directed checks before replacing components.
For coil charge time, voltage correction and replacement-coil checks, see Simos 18 ignition coil dwell control.
For crank and cam sensor events, synchronization and correlation-fault diagnosis, see Simos 18 crankshaft and camshaft synchronization.
Related: knock detection and control · direct injection and fuel pressure · launch control · rolling anti-lag · tuning and log diagnosis.
For tuned EA888 plug selection and ignition-hardware diagnosis, see Simos 18 spark plugs, coils and tuned-engine misfire diagnosis.
For cylinder-balancing adaptation, roughness-based correction and diagnostic limitations, see Simos 18 cylinder balancing and roughness adaptation.