EcuTek's EA888 Evo4 RaceROM adds selectable calibration modes on supported Simos 19.3 and 19.6 software. The mode-specific torque, ignition, lambda and boost-limit features below are RaceROM functions, not proof that an unmodified ECU has the same map switching or that the patch supports every ECU software revision. EcuTek's Evo4 product overview identifies both variants; check the exact controller, calibration, RaceROM version and current tool coverage before use.
What a mode can select
In EcuTek's RaceROM v1 guide, up to four map-switch modes can have separately enabled torque request, ignition, lambda and boost-limit functions. Special features can also be enabled for selected modes. A mode number alone does not establish that each replacement map is enabled: inspect the feature-enable settings and matching software. Configuration and available functions may differ between patch revisions.
The guide describes a steering-wheel method for the supported layout: with cruise control off, hold SET, use plus or minus to select a mode shown on the tachometer, then hold SET again to store it. Its example displays mode 2 at 2,000 rpm. These are product- and control-layout-specific instructions, not an indication of actual engine speed or a method for every Simos 19. EcuTek also lists mode changes through ECU Connect. Check the supplier's current instructions and confirm the selected mode with supported feedback.
Demand, limits and measured result
EcuTek describes high- and low-speed mode-specific torque-demand maps, selected using the original speed-switch point. An enabled demand is still subject to other relevant limits and hardware. RaceROM's per-mode boost-target maximum is a ceiling, not a command that guarantees that pressure: the original torque and airflow strategy can request less. EcuTek specifies these RaceROM limit maps as gauge pressure in hPa; do not compare them directly with an absolute-pressure log without accounting for ambient pressure and sensor location.
RaceROM's base-limit override changes the handling of certain original torque limits, but EcuTek says it does not override the transmission control module's limit received over CAN. Its Evo4 overview warns that under-reporting engine torque can cause slip or harsh shifting. Check the active gearbox calibration and actual torque coordination; an apparently lower reported value does not reduce physical clutch load. Preserve the protective limits appropriate to the hardware and use a calibrated definition for the exact file.
Fuel, ignition and ethanol
Configure the mode for the actual fuel and hardware. EcuTek describes fixed ethanol values per mode and a separate CAN-based ethanol-sensor option. A fixed value is an assumption and cannot detect a different tank blend. RaceROM's flex-fuel implementation can blend mode-specific boost-limit, ignition and lambda maps; availability depends on the feature file, sensor and configuration. Follow the port-injection and ethanol guide for sensor scaling, fuel supply and hold-state considerations.
EcuTek says that its flex blend weight determines the proportion of the normal and ethanol maps. A boost-limit blend is still a blend of ceilings rather than proof of achieved boost. Likewise, a base ignition target is not necessarily final cylinder timing after corrections. Verify actual blend and sensor input, lambda feedback and all available cylinder timing and knock corrections for the intended operating conditions.
Validate each mode
- Record ECU and software identification, patch and tool versions, transmission, installed hardware and fuel. Verify what each enabled feature and each mode is intended to do.
- In a suitable controlled test, select and store the intended mode using the supported interface; confirm the displayed mode or logger state before assessing its results. Repeat for each configured mode.
- Where supported, compare pedal, engine speed and gear with torque demand and applicable limits, boost or manifold-pressure target and actual, lambda target and feedback, fuel-pressure target and actual, ignition timing, per-cylinder corrections and temperatures. Check reference pressure, units and sample timing.
- Investigate a low request separately from a request that is not achieved. If a mode change does not produce the expected result, first verify active mode, feature enables, fuel and applicable ECU/TCU limits before changing further maps.
RaceROM also offers a separately enabled rolling anti-lag feature in certain modes; selecting a calibration mode does not by itself prove that feature is enabled. Confirm the feature configuration and current product documentation. This page does not prescribe launch or anti-lag values.
Rolling anti-lag on the documented RaceROM
EcuTek describes rolling anti-lag (RAL) as a separately configured RaceROM feature for its supported EA888 Evo4 software. It combines ignition retard and percentage fuel cut to build boost while limiting acceleration. The provider also describes stationary use as a launch assist; that does not establish that RAL and the transmission’s launch control are the same system. The feature, map names and behaviour below are specific to EcuTek’s guide, not a factory Simos 19 function. EcuTek EA888 Evo4 RaceROM guide.
In the documented configuration, Rolling Antilag Mapswitch Enable selects which map-switch modes permit the feature, with a separate option for the fuel-cut rev-hold function. EcuTek describes pressing and holding the cruise-control plus button to request RAL once configured. Check the current documentation, actual switch layout, active mode and feature settings; the plus button also has a different role while selecting a map-switch mode. The guide mentions a cruise-state override for dynamometer testing; its presence is not evidence that it is appropriate for normal operation.
Relevant RaceROM controls include RAL Lambda Setpoint and RAL Ignition Base correction. EcuTek states that RaceROM ignition must be in use for its RAL ignition correction to apply. It also documents RAL Maximum Duration and RAL Cool Down Duration; the guide states that the cooldown is triggered only when the maximum duration is reached. Consequently, a short activation does not by itself demonstrate that cooldown will follow. These labels and dependencies should be checked against the installed feature version; the guide does not establish universally suitable settings.
Before assessing the feature, verify the intended mode and configured limits, engine and exhaust condition, fuel, and gearbox compatibility. Use a suitable controlled test environment and examine supported, correctly defined logs for engine speed, throttle, pressure target and actual, lambda target and feedback, ignition, per-cylinder corrections and temperatures. Retarded ignition and fuel cut can increase exhaust and turbo thermal stress; a modelled temperature channel is not proof of the hottest component temperature. Check duration and cooldown behaviour against the installed product before repeated tests, and investigate faults or unexpected operation rather than relying on a single boost number. EcuTek RaceROM guide; Simos 19 DSG torque coordination.
Sources
- EcuTek VW AG EA888 Evo4 product overview. Supported ECU variants, RaceROM overview and transmission coordination. Accessed 17 November 2026.
- EcuTek VW AG EA888 Evo4 RaceROM v1. Mode selection and enable settings, torque, boost-limit units, flex-fuel blending and custom functions. Product-specific instructions; access and feature coverage can change. Accessed 17 November 2026.
- COBB Mk8 engine monitor list. Examples of product-specific torque, pressure, lambda and cylinder timing channels. Accessed 17 November 2026.