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

Lambda target and feedback

Lambda expresses air–fuel ratio relative to stoichiometry for the actual fuel: 1 is stoichiometric, below 1 is richer and above 1 leaner. The ECU coordinates a target from several requests and conditions; upstream sensor feedback, controller correction and learned adaptation are separate from that target. AFR displays may use an assumed stoichiometric ratio, so confirm the tool's scaling and fuel before comparing AFR numbers.

The factory-related names below are research examples from the community SC8S5031_C_OEM Simos 18.1 cross-reference, not a universal definition. Match ECU, ASW, CAL, engine, injection equipment, mode and A2L; verify selectors, axes, units and scaling before editing. Array suffixes and representable ranges do not establish the active branch or a recommended value.

Base and coordinated lambda maps

  • ip_lamb_bas[0] is a basic lambda setpoint indexed by engine speed n_32 and predicted cylinder air mass m_air_cyl_pred in mg/stroke. ip_lamb_bas_hpdi[0] and ip_lamb_bas_mpi[0] are separate HPDI and MPI base setpoints with the same input types in this reference. Check the active selection and hardware; a defined MPI map does not prove port injectors are fitted. LASP base setpoint.
  • ip_lamb_fl_sp and the intake-temperature-selected ip_lamb_fl_sp_tia are full-load enrichment contributions against rpm and elapsed full-load time t_fl. c_tia_thd_lamb_fl_sp and c_tia_hys_lamb_fl_sp concern temperature branch selection; ip_lamb_inc_fl and ip_lamb_dec_fl are rate limits, not the full-load target maps. TQDR full-load enrichment.
  • ip_lamb_sp_tqi is a torque-related lambda map against rpm and indicated torque setpoint tqi_sp_maf in Nm. id_rng_lamb_sp_tqi_act and id_rng_lamb_sp_tqi_deac define activation/deactivation ranges, while ip_lgrd_lamb_sp_tqi limits change rate. They are different from the requested lambda itself. TQDR torque-based setpoint.
  • ip_lamb_sp_cast is a single-injection cold-after-start setpoint versus coolant at start tco_st and post-start cycle count cyc_cast; ip_lamb_sp_cast_mplh and ip_lamb_sp_cast_stst are separate multiple-injection and stop-start branches. LASP coordination.
  • ip_fac_lamb_wup is a basic warm-up lambda factor indexed by rpm and predicted air mass, and ip_lamb_bas_add_ast[1] is an after-start correction against accumulated air mass and start-related coolant temperature. They are not the final target. LASP application reference.

Other temperature, catalyst and component-protection requests may influence the coordinated target. Observe the actual target and active mode; a single table edit or a base-map cell does not prove what lambda is commanded.

Feedback and controller maps

The LACO fuel-mass controller reference lists ip_fac_gain_p_lam, ip_fac_gain_i_lam and ip_fac_gain_d_lam as controller gains. Their axis descriptors are time-based and their input metadata is NO_INPUT_QUANTITY; the labels alone do not establish the runtime inputs. ip_fac_lam_max_not_stat_cdn and ip_fac_lam_min_not_stat_cdn limit controller output in nonstationary conditions. These are feedback controls and limits, not lambda target maps.

Runtime examples include fac_dif_lam_in[0] (controller difference) and fac_lam_i[0] (integral share); they are measurements, not calibrations. The SC8S5031 source describes fac_dif_lam_in as a richness-form controller difference using inverted target and measured lambda with downstream trim influence; it should not be assumed to equal a logger’s simple measured-minus-target lambda. The P, I and D gain-map axis references are labelled ldpm_t_dly_soi_lsl_pos_3_laco and ldpm_t1_lsl_up_3_laco in seconds, but both input fields are NO_INPUT_QUANTITY; confirm the actual transport and sensor-response inputs before interpreting the lookup. The LACO application reference describes stop and short-stop states. A general closed-loop flag can remain set during a short stop, so check the actual controller and sensor state. The acceleration-enrichment example includes a lambda-controller stop flag; do not assume feedback operates continuously in every transient or is always off at full load.

Product-specific controls and logs

EcuTek's EA888 RaceROM guide describes its own GDI Lambda Base Target, MPI Lambda base Target and full-load controls. These are product display names, not OEM A2L identifiers; support and interaction depend on the RaceROM feature and calibration. The simos.app Main Patch has a flex-fuel Lambda offset by rpm and load, applied with its ethanol scaling when the slot enables blending. An offset is not the final target, and its semantics should not be transferred to a different patch.

COBB's MQB monitor list identifies AFR as front-sensor derived and AFR Set Point as the target for listed vehicles. Log target and measured lambda/AFR with engine speed, load, injection mode, fuel pressure, controller state, trims, ignition, knock and temperatures as available. Consider sensor readiness, exhaust transport delay, leaks and fuel-cut state; air in the exhaust during fuel cut can appear lean without describing a firing cylinder's mixture.

Under load, compare target and measurement together with fuel delivery and correction; hitting target can still require substantial correction. Preserve sensor diagnostics, feedback and temperature protection, and evaluate the actual engine and fuel rather than copying a universal target.

Related: fuel trim and adaptation · acceleration enrichment · direct injection and fuel pressure · ethanol and flex fuel. References reviewed 17 November 2026.