MG Flasher Saved On-The-Fly SettingsEEPROM
EEPROM
Storage
Keep supported On-The-Fly settings saved in the ECU so you do not need to select the same map slot, burble profile, cooling state or Anti-Lag RPM after every compatible power cycle, flash, battery change or maintenance event.
Use compatible Custom Code v7.0.1 or newer.
EEPROM storage was introduced in v7.0, but the original save-trigger issue was corrected in v7.0.1.
Long-Term Storage
Supported settings remembered by the ECU
Memory TypeNon-volatile
Save TriggerIgnition ON
Working Save SupportCC v7.0.1+
OverviewSave a Setting.
Save a Setting.
Keep It After Restart.
EEPROM is the ECU’s long-term memory. Unlike a temporary value that exists only while the ECU is powered, a supported saved setting can remain available after the vehicle is switched off.
MG Flasher uses this memory for selected On-The-Fly settings. Custom Code is the MG Flasher software installed inside a compatible DME that enables these controls and their storage behaviour.
Why it matters
Less Reconfiguration
Selected OTF settings can remain consistent between drives, helping the Custom Code experience feel more integrated and predictable.
PersistentSurvives supported power cycles
AutomaticSaved after the required ignition sequence
Feature-AwareApplies only to supported OTF values
Stored Settings
Which On-The-Fly Settings Can Be Preserved?
The exact list depends on the installed Custom Code version, but current documentation identifies the following core On-The-Fly settings.
Switchable Map Slot
The selected Slot 0–4 position can be retained on supported configurations.
Explore Switchable Maps →Burble Aggressiveness
The selected supported burble profile can be preserved between power cycles.
Explore Burbles →Max Cooling Status
The enabled or disabled Max Cooling state can be written to long-term storage.
Explore Max Cooling →Standing RPM Setpoint
The configured stationary Anti-Lag RPM setpoint can be retained where supported.
Explore Anti-Lag →
Newer On-The-Fly features may also use EEPROM.
Do not assume that every Live Control option is stored. Persistence must be implemented for the specific feature, Custom Code release and ECU software.
Storage Scope
Not Every Live Setting Is Automatically Saved.
Seeing a control in the app does not by itself confirm EEPROM persistence. The feature must be explicitly supported by the installed Custom Code release and ECU software.
Supported Values Persist
Use the documented list and current feature guidance to confirm which values are stored.
Some States Can Reset
A control can work in Live Control or diagnostics without being designed for long-term EEPROM storage.
Read the Stored Value
Use Custom Code Diagnostics to read supported EEPROM values when the saved state is uncertain.
Save Procedure
Save with One Ignition Cycle.
After changing a supported On-The-Fly setting, turn the ignition off, wait about five seconds and turn it on again. The ignition-on event triggers the supported EEPROM write.
Adjust
Change the On-The-Fly Setting
Use Live Control, the steering-wheel Custom Code Menu or Custom Code Diagnostics to select a supported value.
Power Down
Turn Ignition Off
Switch the ignition off after the desired setting has been selected.
Wait
Pause for About 5 Seconds
Allow a short pause before initiating the next ignition state.
Save Trigger
Turn Ignition On
The ignition-on event triggers storage of the supported value in EEPROM.
Example
Enable Max Cooling → Ignition OFF → wait 5 seconds → Ignition ON
The selected state is then written to the ECU’s long-term memory on a compatible setup.
Memory Types
Why the Setting Survives Power-Off.
Understanding the distinction helps explain why an ignition cycle is required.
RAM
Used for values that are active while the ECU is powered and operating.
- Fast working memory
- Can change immediately
- Not intended as permanent storage
EEPROM
Used to retain supported configuration values after the ECU is switched off.
- Non-volatile memory
- Stores supported OTF preferences
- Write triggered by ignition cycle
Custom Code DiagnosticsRead, Set and Save
Read, Set and Save
EEPROM Values.
Custom Code Diagnostics can display the current EEPROM values of supported On-The-Fly features and provides tools for reading or setting them directly from the MG Flasher app.
The general diagnostics area includes Read All EEPROM, Set All EEPROM for controlled troubleshooting and Save EEPROM, which initiates the documented ignition-cycle storage process. Read the current value first and prefer an individual feature diagnostic when one is available.
Explore On-The-Fly Settings Diagnostics →01
Read All EEPROMView active values and states for supported OTF options.
02
Set All EEPROMA troubleshooting function that sets predefined values.
03
Save EEPROMInitiates the ignition-cycle process used to trigger saving.
Set All EEPROM is not a normal setup shortcut.
Use it only for controlled troubleshooting. Read the current values first and change only the setting required by the diagnostic procedure.
Version History
v7.0.1 Fixed the Save Trigger.
The feature was introduced in v7.0, but the first release contained a save-trigger bug.
EEPROM Introduced
Long-term storage support was added, but the saving process was not triggered correctly.
Save Trigger Fixed
The ignition-cycle save process was corrected. Use a compatible current release where available.
Compatibility
Only Supported Settings Are Saved.
EEPROM persistence is provided by compatible Custom Code and is not universal across every ECU, release or On-The-Fly setting.
Supported ECU
The ECU software must support a compatible Custom Code release.
Custom Code Version
Use v7.0.1 or newer where EEPROM storage is available.
Supported OTF Feature
The setting itself must be configured for EEPROM persistence.
Correct Save Sequence
An ignition cycle is required to trigger the write process.
Legal & Responsible Use
Review Terms & ConditionsA Saved Setting Keeps the Feature State Active.
EEPROM storage preserves a supported selection; it does not confirm that the selected feature is suitable, safe or legal for every driving situation.
Follow the requirements and warnings on the relevant feature page. The vehicle owner and user are responsible for legal compliance, vehicle condition and safe operation.
FAQ
EEPROM Storage FAQ.
Common questions about persistent Custom Code settings and the ignition-cycle save process.
What is EEPROM Storage in MG Flasher?
EEPROM Storage writes supported On-The-Fly values to the ECU’s long-term memory so they can remain available after compatible power cycles, flashes, battery changes and maintenance events.
What does EEPROM mean?
EEPROM is non-volatile ECU memory. In practical terms, it is where supported settings can be kept after the vehicle is switched off.
Does every Live Control setting get stored?
No. A setting must be explicitly implemented for EEPROM persistence in the installed Custom Code release and ECU software.
What does Custom Code mean on this page?
Custom Code is MG Flasher software installed inside a compatible DME. It enables supported On-The-Fly features and their storage behaviour.
Which Custom Code version introduced EEPROM Storage?
EEPROM Storage was introduced in Custom Code v7.0. A bug in that release prevented the saving process from being triggered correctly, and it was fixed in v7.0.1.
How do I trigger EEPROM saving?
Change a supported OTF setting, turn ignition off, wait approximately five seconds, then turn ignition on. The ignition-on event triggers saving.
Which settings can be stored?
Current documentation lists Switchable Map slot selection, Burble aggressiveness, Max Cooling status and the stationary Anti-Lag RPM setpoint. Newer compatible features may also use EEPROM.
Do all MG Flasher settings use EEPROM?
No. Only supported settings implemented for EEPROM persistence are stored. Availability depends on the ECU software and active Custom Code release.
Can I check EEPROM values in the app?
Yes. Custom Code Diagnostics can read current EEPROM values for supported On-The-Fly options and provides related troubleshooting controls.
Will EEPROM settings survive a battery change?
The feature is designed to preserve supported values through battery changes and other maintenance tasks, subject to compatibility and correct operation of the installed Custom Code version.
Keep Your On-The-Fly Settings
Keep Supported On-The-Fly Settings Saved.
Check ECU compatibility, install a supported Custom Code release and use the correct ignition-cycle save procedure.