Standing launch
Scope: These are EA888 Simos 18 examples, mainly 18.1. Exact ECU hardware, engine, transmission, software, calibration and patches determine whether a function or definition applies. Community labels are research leads: confirm the target A2L, axes, units, scaling, selectors and logs. Neither listed names nor file ranges are recommended settings.
Launch control manages engine speed and torque before moving off. Stock capabilities, DSG and manual conditions, and custom patch behaviour vary. A launch limiter is not automatically rolling anti-lag or no-lift shift. A Simos 18 launch and no-lift discussion contains historical user and tuner claims; its descriptions are not proof of current support on every ECU.
simos.app Main Patch example
The simos.app Main Patch documentation documents a patch-specific per-slot launch enable and these settings: Max rpm, Ignition angle, Max torque, Boost cap, Ramp in, Cut type, Max speed to arm, Minimum oil temperature and Minimum coolant temperature. These are names in that product, not universal OEM map identifiers.
For this implementation the supplier describes launch with the brake held on DSG or clutch depressed on manual and the throttle floored, subject to speed and temperature gates. It says brake or clutch release or lifting the throttle ends the intervention immediately, without a ramp-out; the configured torque setpoint is also released on brake or clutch release. Fuel cut stops injection on selected cylinders. Its separately selectable spark-plus-fuel-cut strategy initially retains injection while cutting spark on selected cylinders, and adds progressive fuel cuts at and above the limit; the supplier warns of greater exhaust, turbine and catalyst heat. The guide states misfire detection is paused during launch. These claims concern the described patch; verify the installed revision and do not treat the absence of a fault code as evidence of normal combustion.
Factory-related launch signals and calibrations
The following are research examples from the community SC8S5031_C_OEM Simos 18.1 cross-reference. Match the ECU software, A2L, transmission configuration and mode before interpreting selectors, scaling or units; an OEM-related identifier does not establish that a custom launch patch is installed.
ip_fac_put_sp_bol_atjsandip_fac_put_sp_bol_atjs_4wdare race-start pressure-upstream-throttle setpoint factor curves against engine speed in the published CHRG reference. Their outputs are factors, not pressure targets or launch RPM. Confirm when the 4WD selection applies.c_n_max_fcut_ofs_lcis an engine-speed offset for all-cylinder fuel cut in a launch context;c_n_max_fcut_ofs_vstis a separate stopped-vehicle case. An offset is not itself the launch rev target. ENSL engine-speed limitation.c_t_max_tql_ovb_drof_tot_actandc_t_max_tql_ovb_drof_efc_actconcern maximum durations of torque-based overboost relative to the launch request and the pressure-setpoint condition respectively. They are not overall launch timers.lv_tql_ovb_req_drof_sptis a runtime launch-related overboost-request signal. TQSP overboost reference.lv_can_max_acc_ctl_actis a runtime CAN launch-control signal, not a map or proof that a particular aftermarket launch feature is active. CHRG application reference.
Other product-specific launch controls
The COBB Volkswagen Launch Control Tuning Guide describes its custom feature for listed Mk7 applications. Product table names include Load Target, Load Target Offset, Rev Limit, Rev Limit Slot, Target Throttle Angle, Ignition Reduction, Ignition Timing Activation Offset, Launch Control Delay and Launch Control Time Out. These labels are not OEM A2L identifiers.
In that documented implementation, with its clutch/brake-bypass feature configured, Load Target uses undriven-wheel speed and engine speed, while Rev Limit uses undriven-wheel speed and rev-limit slot; otherwise the zero-speed column is used. The guide states that Ignition Reduction uses manifold pressure and applies only under its specified near-limit and front-wheel-speed conditions. These are version-specific descriptions, not instructions to bypass an interlock. The COBB MQB feature guide separately documents rev-limit-slot and load-offset adjustments for its listed maps and vehicles.
Documentation conflict: COBB's launch table guide describes one master-switch value as enabled, while its MQB tuning guide describes the same value as disabling launch. Do not infer polarity from either statement alone; verify the actual ROM, feature version and definition.
In a manual Seat Ibiza 1.8 example, EcuTek RaceROM describes configurable Custom Map A for enable conditions, B for boost target, C for ignition, D for a fuel-quantity multiplier/cut and E for torque limiting. These letters are assignments in that example, not fixed factory launch maps; check actual custom-map availability, input configuration and logic.
Logging launch activation
COBB lists LC Active, LC Rev Limit, LC Engine Load Target, LC ETC Target and LC Activation Delay Time as monitor names. Its newer MQB monitor description presents LC State as a compound sum of readiness, inhibition and active flags, whereas an older monitor page describes a binary state. Verify the specific logger and feature version rather than universally decoding it either way. COBB Spark Reduction combines custom-feature spark intervention and is not exclusively a knock signal.
Verify the actual setup
Check ECU and transmission compatibility, active slot, pedal and brake or clutch state, temperature gates and speed, and record the exact patch revision. Log engine speed, torque request, boost target/actual, ignition, fuel/cut state, temperatures and gearbox behaviour where supported. A standing-launch event is distinct from a rolling event; repeated operation imposes load and heat on engine, exhaust and drivetrain.
Related guides: bigger turbos · wastegate and boost control · fuel-system and MPI upgrades · ethanol and flex fuel · torque model and DSG · ignition and knock · launch control · rolling anti-lag.
Separate guides: traction control tuning · flat-foot shifting.
References reviewed 17 November 2026. Forum accounts are reported observations, not independently verified fixes.