No Active Intervention Request
The vehicle is delivering torque without a detected wheel-slip or high-load shift event requiring reduction.
Selected limit removedGet MG Flasher updates, new features, engine support, releases and important announcements.
The transmission control unit (TCU) can request engine-torque reduction. On supported Gen 1 and Gen 2 setups, MG Flasher Custom Code dynamically removes selected TCU-requested limits when no intervention is required, while still allowing torque reduction during detected wheel slip, launches and demanding gear changes.
Part of the MG Flasher software layer Explore Custom Code →The transmission control unit can request torque reduction from the engine ECU. On a tuned vehicle, those requests can restrict the intended engine output even when the current operating condition does not require intervention.
The current MG Flasher strategy is dynamic rather than one fixed app-set limit. It removes supported TCU-requested limits when intervention is not required and allows the requested reduction to remain during detected wheel slip, a launch or a demanding gear change.
The current feature responds to documented drivetrain conditions instead of using the original static app-set limiter.
The vehicle is delivering torque without a detected wheel-slip or high-load shift event requiring reduction.
Selected limit removedThe TCU-requested torque reduction can remain available during a detected traction event.
TCU reduction retainedDuring a documented high-load transient event, the requested TCU torque reduction can remain active.
TCU reduction retainedThe current strategy is more context-aware than the original implementation.
The feature was initially introduced for Gen 2 vehicles before transmission tuning was widely available. The earlier implementation operated as a static torque limit configured from the MG Flasher app.
The current strategy dynamically removes the relevant limits when no intervention is required and allows them when traction or high-load shift conditions call for torque reduction.
The current feature operates automatically. Users should not expect a current torque-value slider, steering-wheel CCM position, Live Control card or Custom Code Diagnostics control for this function.
TCU Torque Limiter Bypass changes how compatible engine-side Custom Code responds to torque-limit requests from the transmission. It does not flash or recalibrate the TCU. A complete transmission tune can address broader behaviour such as shift strategy, clutch pressure, shift timing and TCU-specific limits.
The correct solution depends on the vehicle, transmission, torque level and tuning goals. Some setups may still benefit from or require a dedicated transmission calibration, and this engine-side feature should not be presented as its replacement.
Current documentation lists the feature for supported vehicles from both generations, but availability still depends on the exact ECU software and compatible Custom Code release.
The current feature documentation states availability on supported vehicles from both generations.
The exact ECU software must support a Custom Code version that includes this feature.
The vehicle’s engine, transmission and calibration must be compatible with the intended torque level.
Use the latest MG Flasher app to identify the connected ECU software and confirm exact support before purchasing or flashing.
ECU software, Custom Code version, transmission type, current calibration and power level can all affect availability and suitability.
TCU Torque Limiter Bypass has no dedicated CCM 1K–7K position, Live Control card or Custom Code Diagnostics control. It operates automatically when the compatible feature is present in the flashed Custom Code configuration.
The feature is designed to improve calibration flexibility without treating every TCU torque request the same way.
Compatible setups can avoid unnecessary TCU-requested torque restriction during normal high-output operation.
The documented torque-reduction request can remain available when wheel slip or a demanding transient event is detected.
The current logic responds to the operating condition rather than relying only on one static value.
The current function runs inside compatible DME Custom Code rather than through a manual app or steering-wheel control.
Removing a software limitation does not increase the mechanical capacity of the transmission, clutch packs, driveline, tires or other components. The tune and requested torque must remain appropriate for the complete setup.
Vehicle condition, transmission condition, clutch capacity, temperature management, tires and calibration quality remain essential at elevated torque levels. Validate meaningful changes in a controlled environment, not on public roads, and verify applicable road-use, insurance and motorsport requirements.
Confirm the transmission and complete driveline are mechanically healthy before raising torque output.
The engine tune, torque model, fuel and hardware must suit the complete vehicle setup.
Available grip, tire condition and temperature affect how much torque can be used effectively.
Transmission and engine temperatures must remain within suitable operating limits.
Review vehicle behaviour and logs after meaningful changes in a safe, controlled environment.
Use an experienced tuner or dealer for high-output, unusual or uncertain configurations.
The vehicle owner, tuner and user remain responsible for drivetrain suitability, legal compliance and safe operation. Performance software may be restricted by local road-use or competition rules.
These features may complement drivetrain and torque management on supported setups.
Define planned engine-torque ceilings independently for supported gears.
Learn More → 02Record supported engine and drivetrain data for calibration and behaviour review.
Learn More → 03Explore the MG Flasher software layer behind supported advanced DME functionality.
Learn More →Common questions about dynamic torque-limit management in MG Flasher.
It dynamically removes supported torque limits requested by the TCU when intervention is not required, while allowing torque limitation during wheel slip, launches or demanding gear changes.
TCU means Transmission Control Unit. It is the transmission controller that can request engine-torque reduction from the DME during supported operating conditions.
No. The current implementation is automatic. It has no dedicated CCM position, Live Control card or Custom Code Diagnostics control.
No. The static app-set limiter describes the original implementation. The current strategy dynamically handles supported TCU torque-limit requests.
No. Those are transmission-calibration functions. TCU Torque Limiter Bypass changes the engine-side response to supported torque-limit requests and is not a full TCU tune.
Current MG Flasher documentation states that the feature is available on supported Gen 1 and Gen 2 vehicles. Exact ECU and Custom Code compatibility must still be confirmed.
No. The feature manages compatible TCU torque-limit requests through engine Custom Code. A full TCU tune can change broader transmission-specific behaviour and calibration.
No. The current strategy is dynamic and can allow torque reduction when wheel slip, a launch or a high-load gear change requires intervention.
No. Software cannot increase the physical torque capacity of the transmission or drivetrain. The calibration must remain suitable for the hardware and vehicle condition.
Connect with the latest MG Flasher app, identify the exact ECU software, check compatible Custom Code support and confirm the feature before flashing.
Confirm the exact ECU software, compatible Custom Code and complete drivetrain suitability before using a calibration with higher torque output.
