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
Tuning
Parent
Simos 18
Applies to
Simos 18.1
Tool groups
None
Manufacturers
Volkswagen Group

Changes from revision 2 to revision 2

Removed text is struck through; added text is highlighted.

Scope and sensor data path

A flex-fuel sensor and a sensor-dependent calibration must both be configured and working. A fixed-blend calibration, a sensorless estimation strategy, a live sensor and a CAN input are different configurations; the installed system decides which signal is actually used. COBB's MQB flex-fuel guide documents its own input selection and update/hold behaviour, and cautions that fuel between a sensor and engine may not yet have the same composition during mixing. Do not assume those feature names or selection rules apply to every Simos 18 file.

The map and signal names below are research examples from community-extracted SC8S5031_C_OEM ALFU ethanol-sensor acquisition, not proof that a particular 18.x vehicle is equipped or configured for a sensor. Confirm ASW/CAL, sensor hardware and location, signal type, source selection, feature version, axes and units. A sensor-related definition is not evidence that an aftermarket patch uses the same code path.

Frequency, temperature and filtering

ip_perc_ff_sens converts the raw sensor-frequency signal frq_perc_ff_sens_raw in Hz to an ethanol percentage in the cited extraction. ip_temp_fuel_sens converts t_temp_fuel_sens_raw, a pulse-time input in ms, to fuel temperature in °C. Check the correct sensor's output specification and the active input implementation: temperature and ethanol content are different outputs, and neither curve is a boost or ignition map. perc_ff_sens_raw and perc_ff_sens_mmv are raw and processed ethanol-content runtime values; temp_fuel_sens_raw and temp_fuel_sens_mmv are temperature-path values. c_crlc_perc_ff_sens and c_crlc_temp_fuel_sens are correlation constants for the respective smoothing calculations. These are not interchangeable physical sensors, and the temperature is local to the sensor rather than necessarily the injector or HPFP. c_t_dly_afu_sens_acq is labelled as the wait for the first valid sensor value, in seconds. Its copied table caption describes another quantity; verify implementation, configured conditions and signal validity. The representable range is not an advised delay. ALFU acquisition reference.

Fuel transport and the value used

The ALFU acquisition description discusses a ring buffer for the delay between the ethanol sensor and cylinder. It lists c_nr_dly_afu_sens_buf as a number of delay steps, c_mff_sp_afu_int as an integral-update threshold, and fac_afu_ratio_sens_mmv_buf[11] as stored runtime data. Its narrative speaks of fuel mass, while c_mff_sp_afu_int is labelled in litres in the field metadata and its copied calibration notes are inconsistent. Resolve the scaling, meaning and buffer size in the matched implementation before any interpretation; do not copy an arbitrary value or equate buffer steps to seconds.

fac_afu_ratio_sens_mmv_dly is a delayed sensor-based runtime ratio associated with fuel reaching the cylinder in the ratio-determination reference. It is a modelled delay, not an independent ethanol measurement at the injector. lv_fac_afu_ratio_sens_vld indicates that the sensor path is active and its signal valid; fac_afu_ratio is the determined ratio used by the broader strategy. Validity alone does not prove fuel mixing is complete or the sensor is accurate.

For the stated COBB MQB implementation, Flex Fuel Ethanol Hold Content Boost and Flex Fuel Ethanol Hold Content RPM define separate thresholds: exceeding either one holds the last used ethanol value according to that guide. Threshold to Update MFF Value specifies how much sensor-reported content must change before the value used in calculations updates; COBB's example requires the change to exceed the threshold. These product-specific labels do not prove that a sensor has failed when raw and used values differ, and do not repair an unreliable signal.

The SC8S5031 ratio reference also lists state_alfu as the alternative-fuel detection state, with distinct entries labelled sensor error and sensor value in its example. lv_fac_afu_ratio_vld concerns validity of the overall determined ratio, whereas lv_fac_afu_ratio_sens_vld concerns the sensor path. The state encoding and fault reaction must be checked in the exact ASW and logger; neither flag identifies the chemical makeup of fuel independently.

Electrical and plausibility diagnosis

The ALFU sensor-diagnosis reference lists lv_cdn_diag_AFU_SENS_SCG / lv_cdn_diag_AFU_SENS_SCP as diagnostic-condition signals, lv_end_diag_AFU_SENS_SCG / lv_end_diag_AFU_SENS_SCP as end-of-diagnostic signals, and lv_sym_AFU_SENS_SCG / lv_sym_AFU_SENS_SCP as symptom signals. These are runtime states, not calibrations. An inactive or incomplete monitor does not prove a healthy circuit. The ALFU plausibility reference labels c_frq_afu_sens_err_min_diag and c_frq_afu_sens_err_max_diag frequency thresholds for a hardware-error diagnostic in Hz. c_sens_t_temp_rng_1_diag and c_sens_t_temp_rng_2_diag concern measurable temperature-pulse time in ms. These are diagnostic thresholds, not recommended sensor-scaling edits, and a named diagnostic condition alone does not identify a failed part.

For COBB's documented Mk7/Mk7.5 implementation, its flex-fuel DTC list distinguishes C0BB1/C0BB2 electrical faults, C0B10/C0B11 fuel-content or conductivity/permittivity faults, C0B12 implausible frequency, C0B13 ethanol-content limit reached or exceeded, C0B14 lambda-based plausibility, and C0B15/C0B16 temperature-related errors. COBB says C0B13 can accompany reduced power due to fuel-system limits; it does not alone establish a sensor failure. These code descriptions are product-specific; use the installed platform's definitions and current diagnostic procedure. Water or other contamination, incorrect sensor, wiring and oxygen-sensor faults are among the possible causes identified in the list, not diagnoses proven by a code.

Practical investigation

Identify the kit, sensor, software/patch version, source and location. Record raw and used content, fuel temperature, enable and validity status, codes and freeze-frame; include recent filling, likely blend and driving conditions. Capture the fault before clearing it. Check supply, ground, connectors and signal integrity using the kit and vehicle service documentation. If the design permits, compare sensor output and ECU-reported raw frequency at the same moment with a suitable instrument. Avoid assuming connector pins or transfer characteristics from an unrelated kit. Compare a representative fuel sample with the sensor reading using a suitable ethanol-content test and the tester's instructions. Allow for sensor location, residual fuel and mixing. Examine fuel pressure, lambda target and actual, fuel trims and oxygen-sensor health if mixture-related plausibility is involved. Preserve diagnostics and validate the actual fallback behaviour with the calibration provider; a held or manually fixed value is not evidence of live sensing.

In a Mk7 Golf R owner discussion, the owner reported fluctuating ethanol readings and C0B13/C0B16 after flashing a flex-fuel tune; a replacement sensor and moving a ground had not resolved it at the time. The cause and ECU software were not independently established. The case supports checking the complete sensor, wiring and fuel context rather than inferring a fix from the codes alone.

Related: ethanol and flex fuel · fuel temperature modelling · fuel trim · lambda control · low-pressure fuel supply. References reviewed 17 November 2026.

Rendered revisions

Open each version to inspect formatting, tables and photographs.

Revision 2: Simos 18 ethanol sensor signal and flex-fuel diagnosis

Scope and sensor data path

A flex-fuel sensor and a sensor-dependent calibration must both be configured and working. A fixed-blend calibration, a sensorless estimation strategy, a live sensor and a CAN input are different configurations; the installed system decides which signal is actually used. COBB's MQB flex-fuel guide documents its own input selection and update/hold behaviour, and cautions that fuel between a sensor and engine may not yet have the same composition during mixing. Do not assume those feature names or selection rules apply to every Simos 18 file.

The map and signal names below are research examples from community-extracted SC8S5031_C_OEM ALFU ethanol-sensor acquisition, not proof that a particular 18.x vehicle is equipped or configured for a sensor. Confirm ASW/CAL, sensor hardware and location, signal type, source selection, feature version, axes and units. A sensor-related definition is not evidence that an aftermarket patch uses the same code path.

Frequency, temperature and filtering

  • ip_perc_ff_sens converts the raw sensor-frequency signal frq_perc_ff_sens_raw in Hz to an ethanol percentage in the cited extraction. ip_temp_fuel_sens converts t_temp_fuel_sens_raw, a pulse-time input in ms, to fuel temperature in °C. Check the correct sensor's output specification and the active input implementation: temperature and ethanol content are different outputs, and neither curve is a boost or ignition map.
  • perc_ff_sens_raw and perc_ff_sens_mmv are raw and processed ethanol-content runtime values; temp_fuel_sens_raw and temp_fuel_sens_mmv are temperature-path values. c_crlc_perc_ff_sens and c_crlc_temp_fuel_sens are correlation constants for the respective smoothing calculations. These are not interchangeable physical sensors, and the temperature is local to the sensor rather than necessarily the injector or HPFP.
  • c_t_dly_afu_sens_acq is labelled as the wait for the first valid sensor value, in seconds. Its copied table caption describes another quantity; verify implementation, configured conditions and signal validity. The representable range is not an advised delay. ALFU acquisition reference.

Fuel transport and the value used

The ALFU acquisition description discusses a ring buffer for the delay between the ethanol sensor and cylinder. It lists c_nr_dly_afu_sens_buf as a number of delay steps, c_mff_sp_afu_int as an integral-update threshold, and fac_afu_ratio_sens_mmv_buf[11] as stored runtime data. Its narrative speaks of fuel mass, while c_mff_sp_afu_int is labelled in litres in the field metadata and its copied calibration notes are inconsistent. Resolve the scaling, meaning and buffer size in the matched implementation before any interpretation; do not copy an arbitrary value or equate buffer steps to seconds.

fac_afu_ratio_sens_mmv_dly is a delayed sensor-based runtime ratio associated with fuel reaching the cylinder in the ratio-determination reference. It is a modelled delay, not an independent ethanol measurement at the injector. lv_fac_afu_ratio_sens_vld indicates that the sensor path is active and its signal valid; fac_afu_ratio is the determined ratio used by the broader strategy. Validity alone does not prove fuel mixing is complete or the sensor is accurate.

For the stated COBB MQB implementation, Flex Fuel Ethanol Hold Content Boost and Flex Fuel Ethanol Hold Content RPM define separate thresholds: exceeding either one holds the last used ethanol value according to that guide. Threshold to Update MFF Value specifies how much sensor-reported content must change before the value used in calculations updates; COBB's example requires the change to exceed the threshold. These product-specific labels do not prove that a sensor has failed when raw and used values differ, and do not repair an unreliable signal.

The SC8S5031 ratio reference also lists state_alfu as the alternative-fuel detection state, with distinct entries labelled sensor error and sensor value in its example. lv_fac_afu_ratio_vld concerns validity of the overall determined ratio, whereas lv_fac_afu_ratio_sens_vld concerns the sensor path. The state encoding and fault reaction must be checked in the exact ASW and logger; neither flag identifies the chemical makeup of fuel independently.

Electrical and plausibility diagnosis

  • The ALFU sensor-diagnosis reference lists lv_cdn_diag_AFU_SENS_SCG / lv_cdn_diag_AFU_SENS_SCP as diagnostic-condition signals, lv_end_diag_AFU_SENS_SCG / lv_end_diag_AFU_SENS_SCP as end-of-diagnostic signals, and lv_sym_AFU_SENS_SCG / lv_sym_AFU_SENS_SCP as symptom signals. These are runtime states, not calibrations. An inactive or incomplete monitor does not prove a healthy circuit.
  • The ALFU plausibility reference labels c_frq_afu_sens_err_min_diag and c_frq_afu_sens_err_max_diag frequency thresholds for a hardware-error diagnostic in Hz. c_sens_t_temp_rng_1_diag and c_sens_t_temp_rng_2_diag concern measurable temperature-pulse time in ms. These are diagnostic thresholds, not recommended sensor-scaling edits, and a named diagnostic condition alone does not identify a failed part.

For COBB's documented Mk7/Mk7.5 implementation, its flex-fuel DTC list distinguishes C0BB1/C0BB2 electrical faults, C0B10/C0B11 fuel-content or conductivity/permittivity faults, C0B12 implausible frequency, C0B13 ethanol-content limit reached or exceeded, C0B14 lambda-based plausibility, and C0B15/C0B16 temperature-related errors. COBB says C0B13 can accompany reduced power due to fuel-system limits; it does not alone establish a sensor failure. These code descriptions are product-specific; use the installed platform's definitions and current diagnostic procedure. Water or other contamination, incorrect sensor, wiring and oxygen-sensor faults are among the possible causes identified in the list, not diagnoses proven by a code.

Practical investigation

  1. Identify the kit, sensor, software/patch version, source and location. Record raw and used content, fuel temperature, enable and validity status, codes and freeze-frame; include recent filling, likely blend and driving conditions. Capture the fault before clearing it.
  2. Check supply, ground, connectors and signal integrity using the kit and vehicle service documentation. If the design permits, compare sensor output and ECU-reported raw frequency at the same moment with a suitable instrument. Avoid assuming connector pins or transfer characteristics from an unrelated kit.
  3. Compare a representative fuel sample with the sensor reading using a suitable ethanol-content test and the tester's instructions. Allow for sensor location, residual fuel and mixing. Examine fuel pressure, lambda target and actual, fuel trims and oxygen-sensor health if mixture-related plausibility is involved. Preserve diagnostics and validate the actual fallback behaviour with the calibration provider; a held or manually fixed value is not evidence of live sensing.

In a Mk7 Golf R owner discussion, the owner reported fluctuating ethanol readings and C0B13/C0B16 after flashing a flex-fuel tune; a replacement sensor and moving a ground had not resolved it at the time. The cause and ECU software were not independently established. The case supports checking the complete sensor, wiring and fuel context rather than inferring a fix from the codes alone.

Related: ethanol and flex fuel · fuel temperature modelling · fuel trim · lambda control · low-pressure fuel supply. References reviewed 17 November 2026.

Revision 2: Simos 18 ethanol sensor signal and flex-fuel diagnosis

Scope and sensor data path

A flex-fuel sensor and a sensor-dependent calibration must both be configured and working. A fixed-blend calibration, a sensorless estimation strategy, a live sensor and a CAN input are different configurations; the installed system decides which signal is actually used. COBB's MQB flex-fuel guide documents its own input selection and update/hold behaviour, and cautions that fuel between a sensor and engine may not yet have the same composition during mixing. Do not assume those feature names or selection rules apply to every Simos 18 file.

The map and signal names below are research examples from community-extracted SC8S5031_C_OEM ALFU ethanol-sensor acquisition, not proof that a particular 18.x vehicle is equipped or configured for a sensor. Confirm ASW/CAL, sensor hardware and location, signal type, source selection, feature version, axes and units. A sensor-related definition is not evidence that an aftermarket patch uses the same code path.

Frequency, temperature and filtering

  • ip_perc_ff_sens converts the raw sensor-frequency signal frq_perc_ff_sens_raw in Hz to an ethanol percentage in the cited extraction. ip_temp_fuel_sens converts t_temp_fuel_sens_raw, a pulse-time input in ms, to fuel temperature in °C. Check the correct sensor's output specification and the active input implementation: temperature and ethanol content are different outputs, and neither curve is a boost or ignition map.
  • perc_ff_sens_raw and perc_ff_sens_mmv are raw and processed ethanol-content runtime values; temp_fuel_sens_raw and temp_fuel_sens_mmv are temperature-path values. c_crlc_perc_ff_sens and c_crlc_temp_fuel_sens are correlation constants for the respective smoothing calculations. These are not interchangeable physical sensors, and the temperature is local to the sensor rather than necessarily the injector or HPFP.
  • c_t_dly_afu_sens_acq is labelled as the wait for the first valid sensor value, in seconds. Its copied table caption describes another quantity; verify implementation, configured conditions and signal validity. The representable range is not an advised delay. ALFU acquisition reference.

Fuel transport and the value used

The ALFU acquisition description discusses a ring buffer for the delay between the ethanol sensor and cylinder. It lists c_nr_dly_afu_sens_buf as a number of delay steps, c_mff_sp_afu_int as an integral-update threshold, and fac_afu_ratio_sens_mmv_buf[11] as stored runtime data. Its narrative speaks of fuel mass, while c_mff_sp_afu_int is labelled in litres in the field metadata and its copied calibration notes are inconsistent. Resolve the scaling, meaning and buffer size in the matched implementation before any interpretation; do not copy an arbitrary value or equate buffer steps to seconds.

fac_afu_ratio_sens_mmv_dly is a delayed sensor-based runtime ratio associated with fuel reaching the cylinder in the ratio-determination reference. It is a modelled delay, not an independent ethanol measurement at the injector. lv_fac_afu_ratio_sens_vld indicates that the sensor path is active and its signal valid; fac_afu_ratio is the determined ratio used by the broader strategy. Validity alone does not prove fuel mixing is complete or the sensor is accurate.

For the stated COBB MQB implementation, Flex Fuel Ethanol Hold Content Boost and Flex Fuel Ethanol Hold Content RPM define separate thresholds: exceeding either one holds the last used ethanol value according to that guide. Threshold to Update MFF Value specifies how much sensor-reported content must change before the value used in calculations updates; COBB's example requires the change to exceed the threshold. These product-specific labels do not prove that a sensor has failed when raw and used values differ, and do not repair an unreliable signal.

The SC8S5031 ratio reference also lists state_alfu as the alternative-fuel detection state, with distinct entries labelled sensor error and sensor value in its example. lv_fac_afu_ratio_vld concerns validity of the overall determined ratio, whereas lv_fac_afu_ratio_sens_vld concerns the sensor path. The state encoding and fault reaction must be checked in the exact ASW and logger; neither flag identifies the chemical makeup of fuel independently.

Electrical and plausibility diagnosis

  • The ALFU sensor-diagnosis reference lists lv_cdn_diag_AFU_SENS_SCG / lv_cdn_diag_AFU_SENS_SCP as diagnostic-condition signals, lv_end_diag_AFU_SENS_SCG / lv_end_diag_AFU_SENS_SCP as end-of-diagnostic signals, and lv_sym_AFU_SENS_SCG / lv_sym_AFU_SENS_SCP as symptom signals. These are runtime states, not calibrations. An inactive or incomplete monitor does not prove a healthy circuit.
  • The ALFU plausibility reference labels c_frq_afu_sens_err_min_diag and c_frq_afu_sens_err_max_diag frequency thresholds for a hardware-error diagnostic in Hz. c_sens_t_temp_rng_1_diag and c_sens_t_temp_rng_2_diag concern measurable temperature-pulse time in ms. These are diagnostic thresholds, not recommended sensor-scaling edits, and a named diagnostic condition alone does not identify a failed part.

For COBB's documented Mk7/Mk7.5 implementation, its flex-fuel DTC list distinguishes C0BB1/C0BB2 electrical faults, C0B10/C0B11 fuel-content or conductivity/permittivity faults, C0B12 implausible frequency, C0B13 ethanol-content limit reached or exceeded, C0B14 lambda-based plausibility, and C0B15/C0B16 temperature-related errors. COBB says C0B13 can accompany reduced power due to fuel-system limits; it does not alone establish a sensor failure. These code descriptions are product-specific; use the installed platform's definitions and current diagnostic procedure. Water or other contamination, incorrect sensor, wiring and oxygen-sensor faults are among the possible causes identified in the list, not diagnoses proven by a code.

Practical investigation

  1. Identify the kit, sensor, software/patch version, source and location. Record raw and used content, fuel temperature, enable and validity status, codes and freeze-frame; include recent filling, likely blend and driving conditions. Capture the fault before clearing it.
  2. Check supply, ground, connectors and signal integrity using the kit and vehicle service documentation. If the design permits, compare sensor output and ECU-reported raw frequency at the same moment with a suitable instrument. Avoid assuming connector pins or transfer characteristics from an unrelated kit.
  3. Compare a representative fuel sample with the sensor reading using a suitable ethanol-content test and the tester's instructions. Allow for sensor location, residual fuel and mixing. Examine fuel pressure, lambda target and actual, fuel trims and oxygen-sensor health if mixture-related plausibility is involved. Preserve diagnostics and validate the actual fallback behaviour with the calibration provider; a held or manually fixed value is not evidence of live sensing.

In a Mk7 Golf R owner discussion, the owner reported fluctuating ethanol readings and C0B13/C0B16 after flashing a flex-fuel tune; a replacement sensor and moving a ground had not resolved it at the time. The cause and ECU software were not independently established. The case supports checking the complete sensor, wiring and fuel context rather than inferring a fix from the codes alone.

Related: ethanol and flex fuel · fuel temperature modelling · fuel trim · lambda control · low-pressure fuel supply. References reviewed 17 November 2026.