Step 1: capture the rolling RPM target
The driver reaches the desired engine speed in the selected gear and deliberately holds RES/+. The current development branch captures that RPM and retains it as the reference until the trigger is released or a safety path aborts the strategy. This is different from a fixed launch-style limiter because the target is chosen from the actual rolling condition.
Step 2: use dedicated late-ignition tables
When the activation gates are satisfied, Rolling ALS selects a dedicated KFZW/KFZW2 pair for the active multimap profile. There are five ALS ignition pairs in the design, allowing each normal map to have its own Rolling ALS ignition calibration rather than forcing every profile through one global timing table.
Step 3: REDSOL stages 0 through 4
REDSOL is used as a selective cylinder-reduction request. Each map has an editable capture/hold curve that responds to RPM above the captured target. Stage 0 requests no additional cylinder reduction; stages 1 through 4 progressively request at least that number of cylinders reduced. Hysteresis is included so the selected stage does not chatter when RPM sits near a boundary.
The custom request is also bounded by a per-map maximum. The design compares the ALS request with the factory REDSOL request so Rolling ALS does not weaken a stronger OEM intervention that is already active.
RPM and gear aggression
The development architecture includes modifiers that can soften, leave neutral, or add one REDSOL stage based on the captured RPM region and selected gear. That gives calibration control over how aggressively the strategy reacts without replacing the underlying per-map REDSOL curve.
Safety paths are part of the design
Current logic includes clutch and brake handling, engine-speed and vehicle-speed windows, minimum pedal, coolant-temperature gating, modeled EGT protection, maximum target overshoot and optional pressure/boost guards. A safety abort can latch Rolling ALS off until RES/+ is released, which prevents a map-change or abort event from immediately flowing back into ALS operation.
Why the waitlist exists
The waitlist gives interested ME7.5 owners a way to hear about the release without turning an unfinished development build into a product. You can optionally include your ECU/software string so demand for different revisions is visible while the feature is being validated.