Automatic ECA Input
A compatible ethanol sensor can continuously provide the DME with the current ethanol content.
Get MG Flasher updates, new features, engine support, releases and important announcements.
Let a compatible MG Flasher calibration adapt to the ethanol content in the tank. Flex Fuel Blending can automatically adjust supported tuning parameters from pump fuel through higher ethanol blends using an ECA sensor or a manually configured ethanol value.
New to MG Flasher? How It Works →Visual example only. The tuner defines the ethanol breakpoints, maps and supported parameters for the installed calibration.
Ethanol content can change every time the vehicle is refuelled. A fixed ethanol calibration assumes one specific blend, while MG Flasher Flex Fuel Blending can use the measured or configured ethanol value to interpolate supported tuning parameters in real time.
The result is a more flexible workflow for compatible OTS maps and custom calibrations. The exact output, supported blend range and hardware requirements still depend on the vehicle, fuel system and tune.
A compatible ethanol sensor can continuously provide the DME with the current ethanol content.
Without a sensor, a known ethanol value can be configured in the app or through supported Custom Code controls.
Supported boost, fueling, ignition and other calibration areas can blend according to tuner-defined logic.
Map validation, sensor diagnostics and optional MG Flasher Limp Mode help protect compatible setups.
MG Flasher can interpolate between Pump Fuel, Flex Fuel 1 and Flex Fuel 2 calibration tiers. The tuner decides which tables blend and how ethanol content maps to the blending factor.
The base calibration tier used at the lower end of the configured ethanol range.
Blend factor: 0%An intermediate calibration tier for the tuner-defined mid-range ethanol target.
Blend factor: 100%An optional higher-ethanol calibration tier when blending factors extend above 100%.
Blend factor: 200%A one-stage setup can interpolate between the Pump Fuel and Flex Fuel 1 tables. The ethanol content assigned to each end point is defined by the calibration.
A two-stage setup can continue from Flex Fuel 1 toward Flex Fuel 2. Valid FF2 calibration data is required wherever the configured blend factor exceeds 100%.
Flex Fuel Blending uses an ethanol value as its input. That value can come from a compatible ECA sensor or from Ethanol Content Override. The override can be controlled in the app or through the existing 5K Custom Code Menu position.
A compatible CAN-based Ethanol Content Analyzer continuously supplies the DME with the measured ethanol content. Flex Fuel Blending then applies the tuner-defined interpolation between the enabled PF, FF1 and FF2 calibration tiers.
The ECA provides the ethanol value. The tuner-defined PF, FF1 and FF2 tables determine how that value changes boost, fuel, ignition and other supported calibration areas.
Visual example only. Exact ethanol breakpoints and blended calibration areas are defined by the installed OTS map or custom tune.
Flex Fuel Blending does not have a separate CCM menu position. The manual value is supplied through Ethanol Content Override, which occupies the 5K position in the Custom Code Menu.
The RPM gauge and CEL are controlling the ethanol input used by Flex Fuel Blending. They are not directly selecting PF, FF1 or FF2 calibration tiers.
The slow blink confirms that the CCM root menu is active.
While the CEL blinks slowly, move through the CCM root menu until the tachometer points to 5K for Ethanol Content Override.
Interface demonstration only. The manual ethanol value must accurately match the fuel mixture. Exact availability depends on ECU software, Custom Code version and calibration configuration.
The feature is configured in Custom Options before flashing a supported OTS map or compatible custom calibration.
Verify that the connected ECU software supports Custom Code v7.3.x or newer.
Choose a supported MG Flasher OTS map or a custom tune with the required flex-fuel tables populated.
Open Custom Options, enable Ethanol and enter the Ethanol settings submenu.
Activate the blending option, then select the installed ECA or configure the manual ethanol values.
Complete the flash and monitor the dedicated Flex Fuel status and ethanol data where available.
Ethanol increases fuel-system demand. The required hardware depends on the engine, power target, fuel mixture and calibration—not only on whether Flex Fuel Blending is enabled.
Required for fully automatic ethanol detection. The sensor must communicate with the DME over a supported CAN configuration.
Examples in the MG Flasher guide include Motiv ReFlex, Zeitronix and Fuel-It compatible setups.Higher ethanol blends and power targets may exceed the capacity of the factory HPFP. Upgrade requirements vary by platform.
Do not assume a stock fuel system is suitable for full E85 or a high-output calibration.Higher ethanol demand can also require LPFP upgrades. A compatible low-pressure sensor can support additional protection logic.
MG Flasher documentation recommends monitoring fuel pressure for demanding ethanol setups.Supported ReFlex integration can provide ethanol, low-pressure fuel and port-injection data to MG Flasher Custom Code.
Correct CAN ID selection and configuration are required to avoid data conflicts.Compatible Custom Code configurations include validation and diagnostic mechanisms designed to prevent unsafe blending when required data is missing or a supported sensor reports a fault.
The DME checks enabled PF, FF1 and FF2 calibration areas for usable data. Invalid data can disable blending rather than allow an unintended interpolation.
A supported sensor timeout or reported error can disable Flex Fuel Blending and return the strategy to its configured pump-fuel fallback.
With compatible hardware and configuration, critically low LPFP pressure can trigger MG Flasher protection logic and reduce engine load.
MG Flasher can record diagnostic codes for supported Flex Fuel, ethanol sensor, ReFlex and low-pressure fuel faults.
The app is used to select the ethanol input method during flashing, confirm the installed Custom Code version, monitor supported Flex Fuel parameters and diagnose compatible sensor or fuel-pressure faults.
Flex Fuel Blending is not automatically available on every supported vehicle. Exact availability depends on the ECU software, Custom Code version, engine platform, calibration data and fuel-system setup.
The installed ECU software must support a compatible v7.3 or newer Custom Code release.
The OTS map or custom tune must include the required enabled PF, FF1 and—where used—FF2 map data.
The DME needs a valid ethanol input from a compatible sensor or a correctly configured manual value.
The HPFP, LPFP, injectors and related hardware must support the required fuel volume and power target.
The public workflow is similar, but the calibration source determines which blending tables, ethanol targets and hardware combinations are supported.
Compatible MG Flasher OTS maps use MG Flasher's configured automatic blending logic when the feature and required patches are available for the ECU software.
A custom tuner can populate and configure the PF, FF1 and FF2 maps around the vehicle's exact hardware, ethanol range and performance goals.
Flex Fuel Blending works alongside MG Flasher map switching, ethanol controls, logging and supported hardware integrations.
Combine map slots with compatible flex-fuel calibration data for advanced multi-map setups.
Explore Feature → 02Display or manually override the ethanol input used by compatible Custom Code functions.
Explore Feature → 03Integrate supported port-injection, ethanol and low-pressure fuel data with MG Flasher.
Explore Feature → 04Manage supported Ethanol Override and Custom Code settings directly through the app.
Explore Feature →Common questions about automatic ethanol adaptation, hardware, compatibility and MG Flasher Custom Code.
Flex Fuel Blending allows a compatible calibration to interpolate supported tuning parameters according to the ethanol content measured by an ECA sensor or supplied through a manual override.
Flex Fuel Blending requires a compatible Custom Code v7.3.x or newer release for the connected ECU software.
An ECA sensor is required for fully automatic ethanol detection. Without a sensor, a known ethanol content can be configured manually, but the accuracy of the blending input depends on the value entered by the user.
Not exactly. Switchable Maps selects a map slot. Flex Fuel Blending interpolates between enabled PF, FF1 and FF2 calibration tiers inside the active compatible setup according to tuner-defined logic.
Do not assume that the stock fuel system supports full E85 or a high-output ethanol tune. Required HPFP, LPFP, injector and related upgrades depend on the vehicle, engine, blend and power target.
With compatible safety configuration, a supported sensor timeout or fault can disable Flex Fuel Blending, apply a pump-fuel fallback strategy, reduce load through MG Flasher Limp Mode and record a diagnostic code.
Yes, where a compatible MG Flasher OTS map, ECU software and required Flex Fuel patch are available. The app can notify the user when a required reference or patch is missing.
Yes. A compatible custom tune can use tuner-defined PF, FF1 and FF2 data, blending factors, enabled map categories and supported hardware configurations.
Download MG Flasher, connect through a supported ENET method and use the app to check the exact ECU software and available Custom Code support before purchasing or flashing.
Find your engine, check ECU compatibility in the app and confirm the correct fuel-system hardware and calibration.
