Making automated or repetitive changes to tune files can be accomplished by scripts.  Scripting can be used to read tune file and controller information, as well as modify items including comments, history, tune file security settings and remote settings as well as reading/modifying calibration data.

The Lua scripting language and runtime interpreter is used by the EFILive V8 software to implement scripting. A range of example scripts are included in the \Documents\EFILive\V8\Scripts folder.   Detailed documentation on how to script construction and application is located in the EFILive Command Line Reference.pdf.

The ten most recent used scripts are listed in the Script drop down.

To compile and test the script for syntax errors select [Compile].

Scripts can only be applied to open, unrestricted tune file.  Any restrictions should be applied after the script is applied.

The [Run] function will apply the script to the tune file, or the script can be saved for later use and applied via the EFILive Command Line Interface.

To display success or error messages when compiling or running a script the Show Output option should be selected.

Where a script is applied, any changes made to the tune file cannot be undone.  Changes that may have already been made to the security settings, comments or history will not be available until the tune file is saved.

For example, using E67 {B5102} Low Octane Spark Map a script can be created ensure that each cell in the low octane spark map is always less than the equivalent cell in the high octane spark map.  If the lower cell is greater than or equal to the high cell then the low cell is set to one less than the high cell.  

The script to compare and execute these changes is in the image below.

After running the script, Low Octane Spark Map is modified.

Additional documentation is included in EFILive Command Line Reference.pdf.