Tuning Wiki
Applies to

Check the hardware and software limits stated in this article.

Three different functions

The Tuning Database ME7 guide introduces launch control, no-lift shift and anti-lag. These descriptions explain the intent of each feature; the conditions and the way the ECU reduces torque depend on the actual software and modifications.

FeaturePurposeWhat to establish
Launch controlLimits engine speed under selected launch conditions.Whether speed, clutch, brake, pedal, temperature, gear or other conditions enable it; how and when it releases; the torque-reduction method.
No-lift shift (NLS)Provides a temporary torque or engine-speed intervention during a gear change while the driver keeps the accelerator applied.Switch inputs, enable and exit conditions, intervention duration or speed threshold, and whether the software uses spark, fuel or another method.
Anti-lag (ALS)Aims to maintain turbine energy and response during an applicable transient.The actual airflow, ignition and fueling strategy, operating window, heat exposure and protections. A limiter, a spark cut and a combustion-based anti-lag strategy are not automatically the same implementation.

There is no universal launch speed, guaranteed maintained boost, or common cruise-button adjustment for all ME7 software. The original NefMoto M-box discussion describes a particular spark-interruption approach, while a separate M-box development discussion describes a proposed ignition-retard and enrichment approach. Neither proves that the other's trigger conditions apply to a different ECU.

A stock-function launch example has a timer

In a NefMoto ME7.1 M-box example, a contributor describes repurposing an existing speed-dependent raised-engine-speed limit to produce a lower stationary limit. This is a calibration of a described existing function, rather than evidence that every launch-control implementation needs a custom patch. The thread describes the stationary limit as speed-triggered and does not require a clutch input in that setup.

Important limitation of that reported setup: the author later warns that the raised limit is time-limited, and that extended operation above the lower limit can bring the lower limit back into effect, with throttle reduction until engine speed falls. Their reported maximum interval is approximately 10.9 minutes for that setup; it is not a general ME7 specification. A vehicle may therefore appear normal during a short test and intervene later. Do not copy the thread's offsets, temperatures or limiter settings to another image. Confirm all operating conditions, the moving limit, timers and fallback behavior for the exact software before considering such a strategy.

Inputs and exits can explain a feature that does not work

Check the live clutch, brake, accelerator, vehicle-speed and temperature signals required by the particular implementation, including their polarity and transitions. In one NefMoto discussion, an owner reported that launch operation worked while no-lift shift did not; they traced the issue to a reversed brake-signal interpretation in their D-box setup and subsequently reported it working. That is an individual report, not a universal D-box wiring rule. A stationary launch test by itself does not prove that the separate shift conditions are valid.

Document the release conditions as carefully as activation: clutch release, brake request, pedal change, vehicle-speed transition, time expiry and fault or sensor failure should have an understood result. Log the feature state if exposed, input states, engine speed, throttle, torque intervention, boost and mixture with appropriate sensors. Assess normal driveability and protection behaviour as well as the requested feature.

Review code, limits and heat exposure

Some implementations modify executable code or switch to additional maps. The 2018 M-box development thread explicitly described its initial proposal as untested; a reader reported loss of communication after flashing it and then reported recovery after restoring the original. The author later identified definition and code errors. Treat development files as examples for investigation, not proven files to install. Ask which exact hardware and software the tool supports, what changed, how it was tested, and how the original is recovered. A passing checksum alone does not verify behaviour; see ME7 reading, writing and checksums.

Repeated launches load the clutch, gearbox, differential and driveline; altered combustion and exhaust energy can place additional thermal stress on the turbocharger, exhaust and catalyst. Garrett's turbocharger cooling explanation describes the high exhaust temperatures and heat-transfer environment of a high-output petrol turbo. The NefMoto brake-signal discussion also contains owners' reports of component damage; those anecdotes do not establish a universal failure rate or a single cause. Establish the component ratings, temperature measurement and protection behaviour for the actual hardware.

The guide's suggested generic increases to a factory rev limit are not evidence of a safe limit for a particular engine. Valve control, rotating assembly, turbocharger, temperature, gearing and tire ratings need vehicle-specific evidence. Bosch's Audi 132 kW ME7.1 function description shows an engine-speed torque-control path; exact limiter stages and thresholds are application-specific.

Related reading

ME7 getting started · ME7 logging and diagnostics · ME7 ignition and knock reference · ME7.1 S4 exhaust temperature and enrichment. Forum accounts describe individual examples; this wiki has not independently tested the cited modifications.

Continue the conversation

If this topic interests you, consider joining the following forums. They host material referenced in this article.