This reference records definition metadata found in one publicly indexed WinOLS project labelled VW Polo 1.2 TSI 105 PS Siemens Simos10.1.0 V2A360ZWS74. It is a starting point for identifying related functions, not a calibration for another ECU.
Source and verification
The public project directory lists VW Polo 1.2 TSI 105 PS Siemens Simos10.1.0 V2A360ZWS74 damos.ols. The inspected file was 7,116,703 bytes and had SHA-256 60859cd3f74e1362db522b68de3a8d2c1b5b415df9d91794a338cb5b94368ba4. Its authorship, sharing rights, physical donor ECU, stock status and compatibility with any vehicle have not been established. File names and project labels are not proof of applicability. No calibration file is hosted here.
The dimensions and axis associations below are reported by the third-party py-ols parser when reading that exact project. Selected names and descriptions were also found in its raw bytes. This does not independently validate the parser, map dimensions, scaling, axis links or the calibration itself. Confirm the definitions in a suitable editor and against the identified ECU software before use.
Ignition definitions
ip_iga_bas_0andip_iga_refare described as basic and reference ignition angle maps. Each is reported as 12 × 16, with engine speed andMAF_HBaxes. The project describes the latter as lower-resolution MAF, with units of mg/stk. That label alone does not establish the physical sensor or calculation used for the axis.ip_iga_bas_tempandip_iga_ref_tempare reported as 6 × 8 maps relating the respective temperature-correction basis to coolant and cylinder-inlet air temperatures. Separate positive and negative temperature weighting maps are associated with speed andMAF_HB.- The project also labels
ip_iga_bas_cor_mplh_chandip_iga_bas_cor_mplh_oppas basic ignition corrections for double injection, with corresponding reference-angle entries. These are reported as 8 × 8 maps using engine speed and predicted air mass for basic fuel injection. The labels do not establish the selection logic or full final-angle calculation.
Knock-related definitions
ip_fac_thd_knk[0..3]are described as knock-factor tables per cylinder; the parser reports each as 4 × 16 against engine speed andMAF_HB.ip_knkwb[0..3]andip_knkwd[0..3]are described respectively as the beginning and duration of the knock measurement window for each cylinder. The parser reports 4 × 8 maps on those same two axes.
The array labels do not establish which index corresponds to which physical cylinder, or prove that every entry is active in the target software. A window or threshold definition is not an ignition-retard map, and these labels alone do not establish how knock detection, adaptation or protection works.
Using the information
Identify the actual ECU hardware and software first; then verify the matching definitions, units and axis orientation. Review ignition timing alongside cylinder-specific knock retard, intake and coolant temperatures, fuel quality and fault information where those signals are available. A missing or zero retard indication alone does not establish that combustion is knock-free. Retain the intended knock-detection and temperature protections, and investigate sensor or fuel issues before changing a calibration.