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 1 to revision 1

Removed text is struck through; added text is highlighted.

Cylinder balance, misfire and mixture are different signals

Cylinder balancing uses engine-running information and fuel correction paths to manage differences between cylinders under permitted conditions. A roughness signal is derived or processed ECU information, not a direct cylinder-pressure or individual lambda measurement. An aggregate oxygen-sensor reading and a cylinder-balancing factor do not establish that each cylinder has the same mixture or combustion. A rough idle, misfire counter or large learned factor alone does not identify an injector fault.

The engineering names below are research examples from the community SC8S5031_C_OEM Simos 18.1 CYBL balancing manager, balancing adaptation and additive-fuel intervention references. Verify the target ASW/CAL, cylinder indexing, fuel system, operating mode, units and active function. A defined field is not proof that a logger exposes it or a branch is enabled; these are not recommended values.

Operating conditions and adaptation

The manager lists c_tco_min_er_bal_hom and c_tco_max_er_bal_hom as coolant-temperature bounds, with separate idle, low- and high-range speed and fuel-mass conditions. ip_mff_sp_max_er_bal_hom_rng_h[0] and ip_mff_sp_max_er_bal_hom_rng_l[3] are example maximum fuel-mass-setpoint curves against n_32 rpm, with mg/stroke outputs. They define a function window in this example, not overall injector capacity or a fuel target. Verify array meanings and all enable conditions. CYBL manager. lv_er_bal_hom_ena is a runtime enable signal in the same reference; ctr_er_bal_hom_ena is a counter. An inactive function or an unexposed channel does not prove that the system passed or failed a diagnostic. ip_fac_cor_ad_er_bal_hom weights calculation of new homogeneous balancing adaptation outside the idle range. The displayed axes are rpm and mg/stroke but both list NO_INPUT_QUANTITY; id_fac_cor_ad_er_bal_hom is a separate idle-range weighting curve with an unidentified input. Confirm actual signals and selectors before use. c_fac_cor_ad_min_er_bal_hom and c_fac_cor_ad_max_er_bal_hom are adaptation-factor bounds, not manufacturer-approved injector deviation limits. CYBL adaptation reference.

Controller and additive fuel path

The homogeneous balancing controller lists ip_fac_ctl_i_er_bal_hom as an integral controller factor indexed by er_stnd_mmv_dif_bal_hom; the copied table description refers instead to a low-range offset. Resolve the discrepancy in a matched definition before drawing conclusions. fac_ctl_er_bal_hom_cyl and er_stnd_mmv_dif_bal[3] are runtime control or roughness quantities, not maps or direct measured cylinder lambda.

The separate CYBL additive-fuel reference identifies ip_mff_add_p_er_bal and ip_mff_add_i_er_bal as proportional and integral controller curves against er_stnd_mff_add_er_bal, with mg/stroke output. The extraction renders the roughness-axis units inconsistently; verify the matched definition and scaling. ip_fac_mff_add_er_bal is a weighting map against engine speed and mff_sp_mv in mg/stroke, and ip_fac_t_ast_mff_add_er_bal is an after-start weighting curve against t_ast in seconds. These are not injector linearisation or global short-term trim tables.

mff_add_er_bal[3] and mff_add_er_bal_cor[3] are runtime correction values, and lv_mff_add_er_bal_obd_max_neg[3] / lv_mff_add_er_bal_obd_max_pos[3] are diagnostic-related flags. The reference's indexing and whether corrections are applied must be checked for the target. Record adaptation and state before any service-directed reset; resetting a learned value does not repair an air leak, injector, ignition or mechanical fault.

Interpreting roughness data

The separate ENRD roughness reference lists er_stnd and er_stnd_cyl[3] as normalised and cylinder-related roughness quantities. The latter is labelled in microseconds despite its normalised-roughness description; verify the actual scaling and physical interpretation rather than calling it an injector pulse time. Crank signal conditioning, cylinder mapping, operating conditions and the logger's sampling can influence interpretation. Misfire detection has its own logic and should be read separately.

EcuTek's EA888 combustion-mode documentation lists ER_BAL as a combustion-mode inhibition index associated with cylinder balancing. That product-specific label does not mean an active fault or establish which injectors are fitted. Compare the requested and active combustion modes and inhibitions when a supported logger exposes them.

Diagnostic example and workflow

In a 2017 Golf R owner discussion, the owner reported rough idle and a cylinder 2 misfire count, several repairs, and later an improvement after flywheel replacement. Engine work and other changes were also reported; the exact ECU software, mechanism and a controlled independent test were not established. The account is a reason to consider mechanical and drivetrain influences alongside ignition, air, fuel and sensor faults, not proof that a flywheel causes any particular misfire count.

Record codes and freeze frame, temperatures, injection mode, rpm, load and per-cylinder misfire and roughness signals where supported. Check sensor validity, plugs and coils, injector characterisation and electrical condition, pressure target and actual, air leaks and mechanical condition using the current vehicle-specific procedure. Compare like-for-like warm and cold conditions and any changes in supported signal state. One symptom or reset should not be used to bypass diagnosis or emissions monitoring.

Related: misfire detection · fuel trims · combustion modes and MPI split · direct injector characterisation · idle control. References reviewed 17 November 2026.

Rendered revisions

Open each version to inspect formatting, tables and photographs.

Revision 1: Simos 18 cylinder balancing and roughness adaptation

Cylinder balance, misfire and mixture are different signals

Cylinder balancing uses engine-running information and fuel correction paths to manage differences between cylinders under permitted conditions. A roughness signal is derived or processed ECU information, not a direct cylinder-pressure or individual lambda measurement. An aggregate oxygen-sensor reading and a cylinder-balancing factor do not establish that each cylinder has the same mixture or combustion. A rough idle, misfire counter or large learned factor alone does not identify an injector fault.

The engineering names below are research examples from the community SC8S5031_C_OEM Simos 18.1 CYBL balancing manager, balancing adaptation and additive-fuel intervention references. Verify the target ASW/CAL, cylinder indexing, fuel system, operating mode, units and active function. A defined field is not proof that a logger exposes it or a branch is enabled; these are not recommended values.

Operating conditions and adaptation

  • The manager lists c_tco_min_er_bal_hom and c_tco_max_er_bal_hom as coolant-temperature bounds, with separate idle, low- and high-range speed and fuel-mass conditions. ip_mff_sp_max_er_bal_hom_rng_h[0] and ip_mff_sp_max_er_bal_hom_rng_l[3] are example maximum fuel-mass-setpoint curves against n_32 rpm, with mg/stroke outputs. They define a function window in this example, not overall injector capacity or a fuel target. Verify array meanings and all enable conditions. CYBL manager.
  • lv_er_bal_hom_ena is a runtime enable signal in the same reference; ctr_er_bal_hom_ena is a counter. An inactive function or an unexposed channel does not prove that the system passed or failed a diagnostic.
  • ip_fac_cor_ad_er_bal_hom weights calculation of new homogeneous balancing adaptation outside the idle range. The displayed axes are rpm and mg/stroke but both list NO_INPUT_QUANTITY; id_fac_cor_ad_er_bal_hom is a separate idle-range weighting curve with an unidentified input. Confirm actual signals and selectors before use. c_fac_cor_ad_min_er_bal_hom and c_fac_cor_ad_max_er_bal_hom are adaptation-factor bounds, not manufacturer-approved injector deviation limits. CYBL adaptation reference.

Controller and additive fuel path

The homogeneous balancing controller lists ip_fac_ctl_i_er_bal_hom as an integral controller factor indexed by er_stnd_mmv_dif_bal_hom; the copied table description refers instead to a low-range offset. Resolve the discrepancy in a matched definition before drawing conclusions. fac_ctl_er_bal_hom_cyl and er_stnd_mmv_dif_bal[3] are runtime control or roughness quantities, not maps or direct measured cylinder lambda.

The separate CYBL additive-fuel reference identifies ip_mff_add_p_er_bal and ip_mff_add_i_er_bal as proportional and integral controller curves against er_stnd_mff_add_er_bal, with mg/stroke output. The extraction renders the roughness-axis units inconsistently; verify the matched definition and scaling. ip_fac_mff_add_er_bal is a weighting map against engine speed and mff_sp_mv in mg/stroke, and ip_fac_t_ast_mff_add_er_bal is an after-start weighting curve against t_ast in seconds. These are not injector linearisation or global short-term trim tables.

mff_add_er_bal[3] and mff_add_er_bal_cor[3] are runtime correction values, and lv_mff_add_er_bal_obd_max_neg[3] / lv_mff_add_er_bal_obd_max_pos[3] are diagnostic-related flags. The reference's indexing and whether corrections are applied must be checked for the target. Record adaptation and state before any service-directed reset; resetting a learned value does not repair an air leak, injector, ignition or mechanical fault.

Interpreting roughness data

The separate ENRD roughness reference lists er_stnd and er_stnd_cyl[3] as normalised and cylinder-related roughness quantities. The latter is labelled in microseconds despite its normalised-roughness description; verify the actual scaling and physical interpretation rather than calling it an injector pulse time. Crank signal conditioning, cylinder mapping, operating conditions and the logger's sampling can influence interpretation. Misfire detection has its own logic and should be read separately.

EcuTek's EA888 combustion-mode documentation lists ER_BAL as a combustion-mode inhibition index associated with cylinder balancing. That product-specific label does not mean an active fault or establish which injectors are fitted. Compare the requested and active combustion modes and inhibitions when a supported logger exposes them.

Diagnostic example and workflow

In a 2017 Golf R owner discussion, the owner reported rough idle and a cylinder 2 misfire count, several repairs, and later an improvement after flywheel replacement. Engine work and other changes were also reported; the exact ECU software, mechanism and a controlled independent test were not established. The account is a reason to consider mechanical and drivetrain influences alongside ignition, air, fuel and sensor faults, not proof that a flywheel causes any particular misfire count.

Record codes and freeze frame, temperatures, injection mode, rpm, load and per-cylinder misfire and roughness signals where supported. Check sensor validity, plugs and coils, injector characterisation and electrical condition, pressure target and actual, air leaks and mechanical condition using the current vehicle-specific procedure. Compare like-for-like warm and cold conditions and any changes in supported signal state. One symptom or reset should not be used to bypass diagnosis or emissions monitoring.

Related: misfire detection · fuel trims · combustion modes and MPI split · direct injector characterisation · idle control. References reviewed 17 November 2026.

Revision 1: Simos 18 cylinder balancing and roughness adaptation

Cylinder balance, misfire and mixture are different signals

Cylinder balancing uses engine-running information and fuel correction paths to manage differences between cylinders under permitted conditions. A roughness signal is derived or processed ECU information, not a direct cylinder-pressure or individual lambda measurement. An aggregate oxygen-sensor reading and a cylinder-balancing factor do not establish that each cylinder has the same mixture or combustion. A rough idle, misfire counter or large learned factor alone does not identify an injector fault.

The engineering names below are research examples from the community SC8S5031_C_OEM Simos 18.1 CYBL balancing manager, balancing adaptation and additive-fuel intervention references. Verify the target ASW/CAL, cylinder indexing, fuel system, operating mode, units and active function. A defined field is not proof that a logger exposes it or a branch is enabled; these are not recommended values.

Operating conditions and adaptation

  • The manager lists c_tco_min_er_bal_hom and c_tco_max_er_bal_hom as coolant-temperature bounds, with separate idle, low- and high-range speed and fuel-mass conditions. ip_mff_sp_max_er_bal_hom_rng_h[0] and ip_mff_sp_max_er_bal_hom_rng_l[3] are example maximum fuel-mass-setpoint curves against n_32 rpm, with mg/stroke outputs. They define a function window in this example, not overall injector capacity or a fuel target. Verify array meanings and all enable conditions. CYBL manager.
  • lv_er_bal_hom_ena is a runtime enable signal in the same reference; ctr_er_bal_hom_ena is a counter. An inactive function or an unexposed channel does not prove that the system passed or failed a diagnostic.
  • ip_fac_cor_ad_er_bal_hom weights calculation of new homogeneous balancing adaptation outside the idle range. The displayed axes are rpm and mg/stroke but both list NO_INPUT_QUANTITY; id_fac_cor_ad_er_bal_hom is a separate idle-range weighting curve with an unidentified input. Confirm actual signals and selectors before use. c_fac_cor_ad_min_er_bal_hom and c_fac_cor_ad_max_er_bal_hom are adaptation-factor bounds, not manufacturer-approved injector deviation limits. CYBL adaptation reference.

Controller and additive fuel path

The homogeneous balancing controller lists ip_fac_ctl_i_er_bal_hom as an integral controller factor indexed by er_stnd_mmv_dif_bal_hom; the copied table description refers instead to a low-range offset. Resolve the discrepancy in a matched definition before drawing conclusions. fac_ctl_er_bal_hom_cyl and er_stnd_mmv_dif_bal[3] are runtime control or roughness quantities, not maps or direct measured cylinder lambda.

The separate CYBL additive-fuel reference identifies ip_mff_add_p_er_bal and ip_mff_add_i_er_bal as proportional and integral controller curves against er_stnd_mff_add_er_bal, with mg/stroke output. The extraction renders the roughness-axis units inconsistently; verify the matched definition and scaling. ip_fac_mff_add_er_bal is a weighting map against engine speed and mff_sp_mv in mg/stroke, and ip_fac_t_ast_mff_add_er_bal is an after-start weighting curve against t_ast in seconds. These are not injector linearisation or global short-term trim tables.

mff_add_er_bal[3] and mff_add_er_bal_cor[3] are runtime correction values, and lv_mff_add_er_bal_obd_max_neg[3] / lv_mff_add_er_bal_obd_max_pos[3] are diagnostic-related flags. The reference's indexing and whether corrections are applied must be checked for the target. Record adaptation and state before any service-directed reset; resetting a learned value does not repair an air leak, injector, ignition or mechanical fault.

Interpreting roughness data

The separate ENRD roughness reference lists er_stnd and er_stnd_cyl[3] as normalised and cylinder-related roughness quantities. The latter is labelled in microseconds despite its normalised-roughness description; verify the actual scaling and physical interpretation rather than calling it an injector pulse time. Crank signal conditioning, cylinder mapping, operating conditions and the logger's sampling can influence interpretation. Misfire detection has its own logic and should be read separately.

EcuTek's EA888 combustion-mode documentation lists ER_BAL as a combustion-mode inhibition index associated with cylinder balancing. That product-specific label does not mean an active fault or establish which injectors are fitted. Compare the requested and active combustion modes and inhibitions when a supported logger exposes them.

Diagnostic example and workflow

In a 2017 Golf R owner discussion, the owner reported rough idle and a cylinder 2 misfire count, several repairs, and later an improvement after flywheel replacement. Engine work and other changes were also reported; the exact ECU software, mechanism and a controlled independent test were not established. The account is a reason to consider mechanical and drivetrain influences alongside ignition, air, fuel and sensor faults, not proof that a flywheel causes any particular misfire count.

Record codes and freeze frame, temperatures, injection mode, rpm, load and per-cylinder misfire and roughness signals where supported. Check sensor validity, plugs and coils, injector characterisation and electrical condition, pressure target and actual, air leaks and mechanical condition using the current vehicle-specific procedure. Compare like-for-like warm and cold conditions and any changes in supported signal state. One symptom or reset should not be used to bypass diagnosis or emissions monitoring.

Related: misfire detection · fuel trims · combustion modes and MPI split · direct injector characterisation · idle control. References reviewed 17 November 2026.