Pump FuelBase / OEM map area
Valid
MG Flasher Diagnostics & Maps FeatureMap Validity
Map Validity
Check
Check whether enabled Switchable Maps, Burbles and Flex Fuel areas contain the calibration data they need before a slot can be used. Invalid or disabled options remain unavailable, helping prevent the ECU from selecting an incomplete map area.
Use the latest MG Flasher app. Availability still depends on the connected ECU, compatible Custom Code and the prepared calibration file.
Validation Report
Custom Tune · Slot Data
DATA CHECK
Switchable Maps
Burbles
Flex Fuel
Pump FuelEnabled map data detected
ValidFlex Fuel 1Required map data incomplete
InvalidMap SlotSlot codeword not enabled
DisabledPump FuelEnabled map data detected
ValidIllustrative report only. Actual slots, fuel types and validation results depend on the uploaded tune, enabled codewords, Custom Code version and connected vehicle.
OverviewCheck Map Data
Check Map Data
Before It Can Be Selected.
Compatible Custom Code can use multiple calibration areas for Switchable Maps, Burbles and Flex Fuel. Whenever the related codewords are enabled, the required tables must contain populated data. Map Validity Check reports whether those areas are ready before the user selects a slot or relies on ethanol-based blending.
The DME also performs validity checks during startup. If required data is incomplete, affected map switching or blending can be prevented instead of allowing the ECU to use an unintended calibration area.
What the tool validates
Data presence and enabled map structure
Enabled slotsChecks whether active map slots contain the required populated calibration areas.
Fuel typesSeparates Pump Fuel, Flex Fuel 1 and Flex Fuel 2 data where applicable.
Individual mapsHelps narrow an invalid group down to a specific calibration table.
Validation Status
Valid, Invalid or Disabled.
Each status describes whether the configured data can be used. It is not a power figure, tune-quality score or safety approval.
Valid
The required map data for the checked group is populated and can remain available for supported selection or blending.
Invalid
One or more required calibration areas appear incomplete. The affected option should remain blocked until the file is corrected.
Disabled
The related slot or map codeword is not enabled, so the option is intentionally unavailable and its data is not requested.
Important distinction
A map can be reported as valid when its blending codeword is disabled, because that map is not requested by the active configuration.
How It Works
Three Levels of Validation.
Start with the overall slot result, then narrow the problem to a fuel type, map group or individual table.
Slot & Fuel-Type Validity
Check whether all required maps for a selected slot and fuel type pass as a group.
SwitchableMaps · Slot 3 · PFMap-Type Validity
Review grouped results for Switchable Maps or Burbles to identify the affected feature area.
Burbles · Slot 4 · ValidDataSingle-Map Validity
Narrow the issue to one specific PF, FF1 or FF2 calibration map within a selected slot.
DataValid · MAPNAME · FF1 · Slot 2
Validation Coverage
Built for Multi-Map Custom Code.
The tool is most valuable where one tune contains multiple slots, fuel types or selectable calibration profiles.
01
Slot 0–4Switchable Maps
Verify enabled Pump Fuel, FF1 and FF2 map data before selecting a switchable slot.
Explore Switchable Maps →02
Slot 0–5Burbles
Check the populated data required by each enabled burble profile before it becomes selectable.
Explore Burbles →03
PF / FF1 / FF2Flex Fuel
Confirm that blending uses valid Pump Fuel and Flex Fuel tables for the enabled strategy and slot.
Explore Flex Fuel →
In-App Workflow
Inspect the Custom Tune Before Use.
Map Validity Check complements a tuner’s review by exposing supported validity results inside MG Flasher.
Prepare
Upload the Custom Tune
Start with a properly prepared BIN file based on the correct software and Custom Code map pack.
Connect
Open the Latest MG Flasher App
Use a supported ENET connection for the vehicle workflow or open the relevant custom-tune validation process.
Validate
Run the Validity Check
Review enabled slots, fuel types and map groups for valid, invalid or disabled status.
Correct
Fix Invalid Data
Return the file to the tuner or calibration editor and populate the required maps before flashing or selection.
Live Control IntegrationInvalid Slots Stay
Invalid Slots Stay
Unavailable.
Live Control checks whether supported slots are enabled and valid. A disabled slot can be shown as unavailable because its codeword is off, while an invalid slot can be blocked because required map data is incomplete.
This prevents the user from selecting a slot that the current tune is not prepared to use.
Explore Live Control →
Example Slot States
Slot 0AvailableValid
Slot 1AvailableValid
Slot 2BlockedInvalid
Slot 3UnavailableDisabled
Illustrative status display. Actual Live Control labels and availability depend on the installed tune, ECU software and current app.
Important Limitations
Validity Is Not Calibration Approval.
Passing the data check does not prove that the tune is safe, correctly calibrated or appropriate for the vehicle.
Not a Dyno Test
The tool does not measure power, torque, fueling quality or real-world performance.
Not a Safety Certification
A populated table can still contain unsuitable calibration values. The tuner remains responsible for the tune.
Not a Hardware Check
Map validity does not confirm that required fuel pumps, sensors, exhaust hardware or drivetrain upgrades are installed.
Not a Replacement for Review
The BIN file should still be checked by a qualified tuner before flashing or using advanced Custom Code features.
Does Not Repair the File
The tool reports supported validity results. Missing or unsuitable calibration data must still be corrected by the tuner.
Advanced DetailHow Null Data
How Null Data
Is Detected.
During DME startup, Custom Code checks map cells using the appropriate 8-bit, 16-bit or 32-bit data size. The validity logic looks for repeated null-style byte patterns such as zero-filled, maximum-filled or `0xC3`-filled data that commonly indicate an unpopulated calibration area.
Specific maps and Custom Code releases can include documented exceptions where zero or maximum values are legitimate. Those exceptions are handled by the supported validity logic for the relevant release.
Illustrative Null Patterns
8-bit
0x00 · 0xFF · 0xC316-bit
0x0000 · 0xFFFF · 0xC3C332-bit
0x00000000 · 0xFFFFFFFF · 0xC3C3C3C3The public page simplifies the process. Exact exceptions and supported map definitions depend on the Custom Code release.
Requirements
Use the Latest App, Correct File and Compatible Custom Code.
The feature depends on a supported custom-tuning workflow and the map definitions available for the connected ECU software.
Latest MG Flasher App
Use the current supported app release containing the Map Validity Check workflow.
Compatible Custom Code
The ECU software and installed Custom Code must expose the required validity data for the feature.
Correct Base File
Prepare the tune from the correct stock or Custom Base Map for the vehicle software version.
Enabled Codewords
Slot, map and blending codewords must match the maps intended to be used in the calibration.
Legal & Responsible Use
Review Terms & ConditionsA Valid Result Is Not Approval for Road Use.
Map Validity Check confirms supported data-presence conditions only. It does not approve calibration quality, emissions compliance, hardware suitability, drivability or engine safety.
The tuner remains responsible for the calibration file. The vehicle owner and user must verify applicable emissions, noise, road-use and motorsport regulations before flashing or using a modified calibration.
FAQ
Map Validity Check FAQ.
Common questions about map slots, invalid data, Custom Code and in-app validation.
What does Map Validity Check do?
It reports whether supported enabled map areas contain usable populated data for features such as Switchable Maps, Burbles and Flex Fuel.
Which MG Flasher app version should I use?
Use the latest supported MG Flasher app. Older app releases can be blocked or may not contain the current validation workflow.
Does Map Validity Check repair an invalid tune?
No. It reports the supported result. Missing, incomplete or unsuitable calibration data must be corrected by the tuner before the affected option is used.
What does Custom Code mean on this page?
Custom Code is MG Flasher software installed inside a compatible DME. It enables supported multi-map, On-The-Fly and Flex Fuel functions that can use the validated calibration areas.
What does an Invalid slot mean?
It means one or more required calibration areas for that enabled slot or fuel type did not pass the supported data-validity logic.
What is the difference between Invalid and Disabled?
Invalid means required enabled data is incomplete or unsuitable for selection. Disabled means the related slot or map codeword is not enabled and the data is not expected to be used.
Does a Valid result prove that the tune is safe?
No. It confirms the supported data-presence checks, not calibration quality, hardware compatibility, drivability or engine safety.
Why is a disabled map reported as valid?
If the related blending codeword is disabled, that map is not requested by the active strategy, so the validity logic can treat it as valid for the current configuration.
Can the tool identify one specific invalid map?
Supported single-map validity parameters can narrow an issue to a specific map, fuel type and slot.
Can I select an invalid slot in Live Control?
No. Invalid or disabled slots can appear unavailable and cannot be selected through supported Live Control interfaces.
Validate Before You Select
Identify Invalid Map Data Before Use.
Use the latest MG Flasher app with a compatible file and ECU setup to identify invalid or disabled data before selecting advanced multi-map features.