Tuning Wiki
Applies to

Check the hardware and software limits stated in this article.

Sensor roles and hardware scope

Lambda signals matter when checking commanded versus observed mixture, but a sensor indication, feedback correction and commanded target are different quantities. Audi's EA888 Gen3 SSP 920243, pages 56 and 62–63, describes G39 as an upstream broadband LSU 4.2 sensor on a documented 1.8/2.0 litre example, located ahead of the turbo turbine. It also lists G130 after the catalyst, with heaters Z19 and Z29. This does not establish that every Simos 18 variant uses the same sensor, position, wiring or diagnostic strategy: verify engine code, market and original equipment.

The upstream sensor is involved in the primary mixture-feedback path; the downstream sensor supports catalyst and related diagnostic/feedback functions according to the implementation. Do not use a post-catalyst reading as an interchangeable replacement for the pre-catalyst sensor. Oxygen in the exhaust is influenced by combustion and leaks as well as fuelling, so an apparent lean indication alone does not establish a lean mixture delivered to every cylinder.

Heater-control calibration examples

The following labels are extracted from the community SC8S5031_C_OEM Simos 18.1 EGCP upstream-heater reference. These are research examples, not generic settings. Match hardware, ECU ASW/CAL, A2L, branch and units. Representable limits in the source are not recommended sensor voltage or temperature limits.

  • ip_v_efc_ini_lsh_lsl is an initial effective heater-voltage curve in volts. Its temperature axis metadata is NO_INPUT_QUANTITY; the reference equation uses temp_ini_lsl, so verify the selected input on the target.
  • ip_v_efc_rise_lsh_lsl is the nominal linear-sensor heater-voltage warm-up ramp. The time-labelled axis is in seconds with NO_INPUT_QUANTITY; the equation refers to t_pow_rise_lsh_lsl. It is an effective-voltage model request, not a direct duty-cycle or instantaneous terminal-voltage measurement.
  • ip_v_efc_ctl_lsh_lsl is the open-loop effective-heater-voltage map with n_32 in rpm and a °C-labelled second axis whose metadata is NO_INPUT_QUANTITY. The accompanying equation refers to teg_dyn_lsl; verify the actual signal and implementation.
  • ip_v_efc_max_lsh_lsl is an effective heater-voltage limit with a time-labelled axis. c_ttip_min_iplsl_ctl_ena is described as the ceramic-tip temperature for enabling the pump-current controller. These do not give a universal warm-up procedure or justify bypassing heater limits. EGCP linear operating strategy.

The EGCP binary downstream-heater reference separately lists ip_v_efc_ctl_lsh_ls for open-loop heater voltage and ip_v_efc_rise_lsh_ls for its warm-up ramp. The former has an rpm axis and a °C-labelled axis with NO_INPUT_QUANTITY; the latter has a seconds-labelled axis with the same missing runtime-input metadata. Binary and linear entries are separate paths in the reference; confirm actual fitted sensor and active software rather than inferring sensor type from the existence of either table.

Readiness, circuit checks and safe interpretation

In the same extraction, lv_lsh_lsl_ctl_cll[0] is labelled as the linear heater's closed-loop mode, but nearby FR metadata calls it PWM duty: confirm the actual representation. lv_lsl_ready_cdn[0] is labelled forced operative readiness, and c_t_max_lsl_ready_cdn is its maximum-wait calibration. A readiness flag, a heater mode and an emissions monitor's readiness result are distinct. A numeric lambda value during warm-up or a substituted value during a fault is not automatically a trustworthy measurement. EGCP operating strategy.

The upstream heater-circuit reference lists cdn_diag_lsh_lsl[0] as diagnostic conditions, err_diag_lsh_lsl[0] as raw error symptom, and c_teg_dyn_min_diag_lsh_lsl as a temperature condition for a specified fault path. These are not measured sensor voltage or proof the diagnostic test has passed. Availability and enumerations vary; use the correct scan-tool definition and vehicle-specific guided tests.

Bosch's LSU 4.2 motorsport datasheet describes a trimming resistor in its connector, a dedicated interface and sensitivity to leaks and condensation. It describes one sensor family and motorsport part, not exact Simos connector pins or replacement compatibility. Do not split sensor-cell wiring between two independent controllers, apply battery voltage directly to a heater, or assume an aftermarket free-air calibration procedure applies to the factory ECU.

Diagnostics and tuning comparisons

  1. Record full fault codes, freeze-frame, ECU software, sensor locations, exhaust modifications, and whether the fault was intermittent, confirmed or a monitor has not run. Identify the bank, upstream/downstream position, and heater versus signal fault.
  2. Use the manufacturer's repair information to check sensor part and connection, wiring, heater supply/control and exhaust leakage. Consider misfires, fuel pressure and other relevant faults before attributing the symptom to one component. A successful electrical test does not by itself prove an accurate sensor reading.
  3. When comparing an external wideband with the ECU, record both sensor positions, controller and calibration, heater readiness, exhaust tightness, sampling delay and fuel/lambda units. The factory pre-turbine location and a downstream reference may see different temperatures and pressure. Bosch notes accuracy can decline at elevated exhaust pressure for its specific LSU 4.2; do not transfer a pressure correction from another engine or controller without validation.
  4. Log target and actual lambda, correction or trim, closed-loop/ready status when available, engine speed, load, boost, fuel-pressure target and actual, misfire counts and relevant faults. Compare steady and transient regions only after verifying signals and timing. Preserve monitoring and catalyst-related functions.

Worked example: warm-start sputter and sensor codes

A 2015 Mk7 GTI with an EQT Stage 2 93 tune was reported to have intermittent difficult warm starts, with an upstream oxygen-sensor fault suspected. Improvement was later reported after the high-pressure fuel pump was replaced; the exact ECU software, objective root cause and long-term result were not independently verified. A separate vehicle in the same report was documented by an invoice showing P0131, fuel-pressure regulator and misfire codes, and should not be merged with the first case. Both accounts illustrate that a sensor-related code warrants diagnosis rather than automatically proving the sensor or pump is at fault.

Related: lambda control · fuel trim · cold start · misfire diagnosis · high-pressure fuel pump. References reviewed 17 November 2026.

Continue the conversation

If this topic interests you, consider joining the following forums. They host material referenced in this article.