The Memory handling in Ver 3.5 is changed to provide more GP outputs from the unused Coil and Injector drivers. The danger before was that when different Map files is downloaded into the Device, it may override critical setup values which could damage the device or components on the engine. Now the critical values cannot be changed by loading a map. It is saved in a separate space in the flash memory. These values can only be changes by adjusting them on a connected device or by Cloning the device.

Below is a block diagram of the map memory and how map data is handled.

The memory is divided into 3 categories. Map setup data, Map Graph and Matrix data and Critical setup data. Below follows a description of the different memory spaces.:

Map Setup Data
In this block all the normal settings are saved. If you load a map file, this setup data can be overwritten or it can be retained by selecting or de-selecting the Save Setup Data.

Note. This setting must be selected before opening the map. Once you open a map file then this setting is ignored as it is now part of the setup. There are values like TPS calibration that must be recalibrated if you load a new map.

Map Graph and matrix data
This memory house all the graphs and matrix data. This influences the actual tuning of individual engines.

Critical I/O setup data
The memory holds settings that will alter the inputs and outputs connections of the device. They are part of the normal setup data but are critical not to change during a map load function. This memory can never be overwritten by loading a map. One way to change these settings is online with the device connected, and then save it to the device. The other is by cloning function.

The Critical settings are:

Tuning Mode

This setting does not change connections to the device but selects different tuning parameters which may not be adjusted by the tuner.

Save Setup Data

This setting determines if the setup block will be overwritten or not. Checked on means it will be overwritten.

Dual Map Selection

This setting will effect which map data is loaded at startup. It effects also which wiring is used on some devices. This setting was already saved permanently in previous versions.

RPM Output pulses

This setting is used by other devices like a tachometer or TCU and should not change by loading a new map.

Coil Combination

This setting is critical because it could free up drivers that may be used for GP outputs. It will effect wiring connections.

Coil Driver Trigger Combination

This setting is only used in Pluto2 and Saturn and is critical setting because it will damage coil or driver if it is set incorrectly.

Injection Type

This setting is critical because it could free up drivers that may be used for GP outputs. It will effect wiring connections

Idle Control

This setting effect wiring connections and is combined with GP outputs,

Fuel Pressure Control

This setting effect wiring connections and is combined with GP outputs,

Duel Injector Control

This setting effect wiring connections and is combined with GP outputs,

Map Lock Password is also saved in this block. Note that if you upgrade a unit with new firmware it will be locked because this memory space was not cleared. Save both your maps before upgrade and load it in afterwards. See the Clone function.

Cloning
Cloning means copying a device map exactly onto another device. This process will save all the settings including the critical setup data exactly as the device map that was saved. This is handy for builders that use the same engines and drivetrains in different builds. It is also handy to load a startup map of a similar engine in the device to assist new customers. Simply lock a device by entering a map lock password. Then load the map into the device without unlocking it. This will initiate an exact data replacement into the locked device. It will also load the map in all the relevant maps for systems with Dual or quad maps. See locking a device below.