Applicability: The engineering identifiers below are from the community SC8S5031_C_OEM Simos 18.1 cross-reference unless another source is named. Identify the engine, hardware, ECU software, calibration and installed patches; match the A2L, axes, units, signs, indices and selectors. Extracted descriptions sometimes conflict. Values, addresses and states from another software version are not a calibration for this vehicle. SC8S5031 reference.
What switches?
Switchable valve lift selects between discrete cam profiles; it does not replace continuous intake/exhaust cam phasing. Volkswagen's SSP 522, pages 13–15 shows four sliding exhaust-cam pieces and electrical actuators on its CHHA/CHHB examples. EcuTek describes exhaust-only AVS on the EA888 Gen 3 MQB applications covered by its EA888 guide. Confirm the engine code and hardware rather than assuming all Simos 18 engines share that arrangement.
Request, hysteresis and delay
ip_vlft_spis a binary valve-lift setpoint map in the SC8S5031 VVLI reference, with engine speed and torque-derived air-mass setpointmaf_sp_tqias axes. It is not simply a fixed RPM switch or measured-airflow table. The table describes 1 as LFT_1 and 0 as standard; an extracted narrative elsewhere on the same page conflicts about low-lift polarity. Verify the target's actual semantics and hardware instead of copying a value.c_n_hys_vlft_1_spandc_maf_sp_tqi_hys_vlft_1_spare speed and air-mass hysteresis calibrations in the example. They can make the switch-back boundary different from the outgoing boundary, helping avoid repeated switching near a threshold.ip_t_dly_vlft_sp[1]is a lift-request transition delay versus engine speed and coolant temperature in the example;id_idx_gear_t_dly_vlft_spis a gear-dependent delay-map selector. Delay direction depends on the strategy and selector. The source cautions that switching must happen in time; no delay or hysteresis values should be copied between applications.ip_fac_maf_sp_cor_vvlis an altitude-related correction factor for the setpoint calculation, with speed and ambient-pressure axes in the displayed example. Both axis runtime inputs are markedNO_INPUT_QUANTITYand the attached caption is inconsistent, so verify the actual sources in the matching ASW.
Transition coordination
ip_tq_tran_vlft_stnd_ofs is a torque offset for transition to standard lift, versus engine speed and predicted cylinder air mass in the VVLI state-coordination example. It is a transition-related torque calibration, not the normal lift request table. c_n_max_vvl_ctl is a maximum-speed threshold associated with control to LFT_1 in the controller reference; it is distinct from the normal request boundary and depends on the hardware.
Actuator timing is a different calibration
The VVLI timing reference lists ip_t_dly_swi_vvl_acr as actuator dead time versus battery voltage and modelled actuator reference temperature, and ip_t_swi_vvl_acr as total actuator switching time versus speed and reference temperature. The output is milliseconds in that example. These describe actuator behaviour, not the load/RPM switch boundary. t_dly_swi_vvl_acr is a runtime measurement. Confirm actual actuator characteristics and preserve switching protections.
The same timing reference describes c_fac_tco_toil_t_swi_vvl_acr as weighting coolant and oil temperatures for a modelled actuator reference temperature, not proof of a temperature sensor at the actuator. ip_fac_t_swi_vvl_acr is a switching-time factor against filtered battery voltage. The extracted narrative gives conflicting factor-direction statements, so confirm the runtime calculation and hardware-specific supplier data rather than inferring a correction direction from this excerpt.
Request versus realised state
vlft_sp_req, lv_inh_vlft_1 and lv_inh_vlft_stnd appear as runtime request/inhibition signals in the setpoint reference. The request-coordination reference lists lv_vvl_swi_auth and lv_vvl_swi_ctl_inh for switching authorisation and inhibition. state_vvl_chg is a cylinder bitmask of actuators required to switch, not proof they achieved the new profile. VVLI controller. The community cross-reference labels a vlft_sp_req logger PID as a lift position, but describes the underlying signal as an uncorrected request; do not treat it as a physically confirmed position. Availability, state encoding and cylinder indexing must be checked.
For its supported MQB applications, COBB defines Valve Lift Set Point as a request and Valve Lift State as a high-lift state using its own displayed encoding. Do not infer the same polarity as ip_vlft_sp or assume that the display independently senses physical position. Compare request, reported state and relevant diagnostics.
Evaluating a transition
Log speed, torque-related air-mass request and actual, both cam position requests and actuals, lift request/state, intake-flap state, ignition and knock, lambda, boost and faults through both directions of a switch. Compare at similar temperatures and loads, including transient and partial-load operation. A change in lift may select different torque, air and ignition model tables; a step or hesitation can involve several systems. EcuTek describes determining transition points by testing on its documented engine; its example is not a universal changeover RPM. EcuTek EA888 guide.
Related: camshaft timing · valve lift tuning · torque model · ignition timing · bigger turbos · log diagnosis.