Rolling anti-lag
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.
Rolling anti-lag (RAL) is a patch feature intended to retain or build boost during a rolling preparation event. Its trigger and execution vary by product. It is distinct from standing launch control, overrun crackles and the torque intervention during a normal DSG shift.
simos.app Main Patch example
The simos.app Main Patch documentation documents per-slot arming and named controls for Trigger hold time, Minimum rpm, Maximum rpm, Maximum acceleration, Minimum oil temperature, Minimum coolant temperature, Maximum active time, Soft/Medium/Hard cut bands, Cut type, Ignition retard vs EGT, Lambda target, Boost cap, Ramp-in time and Ramp-out time. These are product-specific display names.
For this implementation the supplier says the rpm, acceleration and temperature engagement conditions are checked when RAL engages, not continuously throughout the hold. In the documented fuel-cut strategy, injection stops on selected cylinders. In the separately selectable spark-plus-fuel-cut strategy, injection is retained on the cylinders whose spark is cut; starting at the hard band, injection is also progressively stopped on the remaining cylinders as rpm rises. The supplier warns the latter produces greater turbine and catalyst heat. It states that misfire detection is paused while the cut runs, so an absence of codes then does not establish normal combustion. Check the installed version's safety logic and do not assume all patches implement the same exit conditions.
A different custom-map implementation
EcuTek's EA888 RaceROM custom-map example describes separate ignition-retard, boost-target and torque-limit maps for a rolling-launch strategy. It is an example for that product, not a direct naming or behaviour match for the simos.app patch.
simos.app: cut bands, timeout and targets
The Main Patch guide defines Soft cut band, Medium cut band and Hard cut band as separate RPM offsets from the speed captured on engagement. Rpm filter strength affects the speed used for the engagement window, capture and cuts. These are patch-specific controls rather than factory map names; the captured reference and bands should be logged and interpreted together.
The documented Maximum active time ends the hold and requires button release before another engagement; zero removes that timeout in this implementation. Ignition retard vs EGT is an exhaust-temperature-dependent curve, while Lambda target and Boost cap are overrides; the latter uses absolute hPa. A zero value has a separate documented meaning for each control and must not be treated as a universal “off” switch. Ramp-in and ramp-out affect the transition: verify the installed revision, the temperature signal's sensor or model source and actual exit conditions.
SC8S50 SwitchPatch RAL V2 add-on
JohnBaumb's RAL V2 documentation describes a separate add-on for the SC800S50 8V0906259K/5G0906259x family, dependent on switchleg SwitchPatch 29.33 and its matching definition. The author reports testing on one Mk7 Golf R; it is not proof of compatibility with other software or the simos.app Main Patch.
Its definition labels include RAL engagement button, JB-RAL minimum hold, Maximum engagement time and Rev soft / medium / hard limit. The author describes the soft threshold as relative to the captured speed, with the medium and hard thresholds each relative to the preceding step. That differs from the simos.app guide, where all three offsets refer to captured RPM. The author's time-limit counter also advances with both time and ignition events, so the XDF's seconds display is approximate and RPM-dependent. Use the matching patch and definition, not numbers copied from the other implementation.
The add-on author reports that the underlying SwitchPatch can re-engage while the button remains held after timeout; V2 is described as fading out and remaining off until release. This is the author's version-specific observation. Its example logging names RAL hold count, Active (RAL) and Counter (RAL) are runtime channels, not calibration maps; availability and semantics depend on the patch and logger.
EcuTek custom-map details and uncertainty
EcuTek's Simos 18 RaceROM example assigns Custom Map M to an ignition-retard limit and Custom Map N to a minimum boost-target output; it describes a third custom map for a torque-demand limit. These are configurable product slots, not fixed OEM rolling-antilag maps.
The source is internally inconsistent: it calls the torque map O in its overview but J in the setup text, and says the boost map uses the same axes as the ignition map while its setup lists pedal and RPM. Verify the actual map slot, axes, enable input and output function in the installed calibration. The separate EcuTek EA888 Evo4 RAL guide covers Simos 19, so its dedicated RAL map names must not be assumed present on Simos 18.
What to observe
Identify the active patch, slot, input and disengagement conditions, fuel and relevant gearbox mode. Log rpm, throttle and torque, boost target and actual, wastegate state, lambda, ignition/cut status and available exhaust/turbo temperature channels. Confirm whether temperature is measured or estimated and evaluate the actual turbo, catalyst and driveline thermal and mechanical limits.
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.
References reviewed 17 November 2026. Forum accounts are reported observations, not independently verified fixes.