Storing Calibration Changes Permanently
Overview
When calibration changes are made whilst the ECU is connected to GWv4, the changes are sent to the ECU and it will operate using those values, but the configuration may not saved permanently.
To make the changes ‘permanent’, the ECU must copy the RAM ‘shadow copy’ into ’non-volatile memory’ (NVM) - typically either EEPROM or Flash memory.
Unless the changes are copied to NVM, when the ECU is powered on again, it will load the prior NVM contents into RAM - losing any changes from the prior session. This behavior is dependent upon the ECU type and configuration.
Auto Store
Auto Store, controlled by option 
Auto EE, is a switch that controls whether the ECU will automatically save changes to non-volatile memory. This feature is accessible from application menu .
If modifying the calibration of an ECU that does not have Auto Store enabled, GWv4 will post a notification to inform that Auto Store is disabled.
Tip
It is best to turn Auto Store OFF when the calibration process is completed and the ECU is not being actively tuned, taking care to ensure that the calibration has been stored to the ECU and backed up on the PC. This will guard against any accidental changes in the field, for example due to an unexpected program error that could corrupt the calibration RAM. If Auto Store is OFF then the ECU is more likely to recover itself following a power cycle.
Storing Changes Manually
If Auto Store is OFF, then the ECU will not automatically save changes.
Using the command will instruct the ECU to save any changes into non-volatile memory.
ECU Storage Status
If the ECU detects that its RAM copy of the calibration does not match the non-volatile copy, EE will be displayed in the application status bar. The term EE is derived from EEPROM.
The 
Error EE Checksum channel will be set to ON if the ECU detects that there is un-stored calibration data.
While the ECU is programming the non-volatile memory, the Stat Prog EE channel will be set to ON.
Warning
If the ECU is powered off during the programming of non-volatile memory, the ECU may be left in an inconsistent state. It is best to first close the connection and GWv4 will check that the ECU is in a safe state to be powered off.