Haltech F9A - Manual (Page 57)

56
SECTION THREE
Software Features
Chapter 9
File Storage and Retrieval
Once your Haltech F9 system is configured you should store the entire set of maps and the
Identification to disk. In fact, it is wise to save maps regularly during tuning so that you can
return to a known map while you are experimenting in different areas. You can use the file
storage and retrieval to enhance the flexibility of your race engine by storing the optimum
maps for each race track.
The File storage and retrieval functions can be accessed from the Main Menu by pressing
sI
for files. This function allows you to load engine maps and identification from
computer disk. You can also save the engine maps and the identification to computer disk.
9.1 Saving Maps and Identification
9.1.1 The Save Command
To store all the maps and identification to computer disk with the system running Online,
press
sI
then
6
at the Files sub-menu. The list of maps already stored will appear on the
screen.
You can save maps that you have generated Offline to later be loaded into the ECU. You can
also save different versions of a map to save time while tuning track-side. You can even have
different maps for different circuits.
9.1.2 Giving Your Map A Filename
Choose a name to identify your saved file. If you choose the same name as a map that has
already been saved, the old file will be overwritten and replaced with the file you are
currently saving with the same name. If you do not wish to erase any files already saved,
choose a new filename - one that does not appear on the screen.
The name you choose should not include any spaces or full stops and can be up to eight
characters in length. The name must start with a letter from the alphabet, not a number. For
the sake of your own memory, try to select a name that you will be able to recognise in six
months time.
As you perfect the maps for a particular application you might add a number to the end of the
name to indicate which map is most recent. For example you might call the maps for a Turbo,
Turbo1, Turbo2, etc.