The EFILive software and FlashScan/AutoCal firmware are all capable of saving detailed diagnostic information about their internal operations. When you report a problem or request help from EFILive Support you will almost certainly be asked to provide the appropriate trace files and/or log files (referred to collectively as support files) from your system. EFILive Support can analyze those support files to try and determine the cause of the problem you are reporting.

So how do you know what support files to send to EFILive Support? That really depends on the type of problem you are reporting.

Problems when reading, flashing or locking/unlocking a controller using the V7.5 pass-thru software:

V7 trace files (*.blx files) are located in your 'My Documents\EFILive\V7.5\Bug reports' folder. The files are named 'YYYYMMDD_HHMMSS_upload.blx' (for read attempt) or 'YYYYMMDD_HHMMSS_download.blx' (for flash attempt). The 'YYYYMMDD_HHMMSS' in the filename as substituted as below:

  • YYYY is the year
  • MM is the month
  • DD is the day
  • HH is the hour
  • NN is the minute
  • SS is the second

Please make sure you select only the relevant file(s) based on the date and time in the filename.

Problems when reading, flashing or locking/unlocking a controller using the V8 pass-thru software:

V8 trace files (*.htx files) are located in your 'My Documents\EFILive\V8\Trace' folder. The files are named 'YYYYMMDD_HHMMSS_T_CCC.htx'. The 'YYYYMMDD_HHMMSS_T_CCC.htx' in the filename as substituted as below:

  • YYYY is the year
  • MM is the month
  • DD is the day
  • HH is the hour
  • NN is the minute
  • SS is the second
  • T is the Operation (R=Read, W=Cal-flash, F=Full-Flash, L=Lock)
  • CCC is the controller code

Please make sure you select only the relevant file(s) based on the date and time in the filename.

Problems when reading, flashing or data logging a controller using the FlashScan/AutoCal standalone option:

Support files are not automatically saved by FlashScan or AutoCal in standalone mode, you must manually select the following options to save the support file:

  • FlashScan: F1 Scan Tool -> F3 Scan options -> F1 Save Trace File
  • AutoCal (standard menu): Save Trace File AutoCal (advanced menu):
  • Scan Tool -> Save Trace File

The FlashScan and AutoCal devices maintain an internal buffer of the most recent messages sent to and received from the vehicle. That buffer is stored in RAM memory and is wiped clean each time the device is powered off or rebooted. Therefore you MUST save the trace file before powering off or rebooting the device.

The support file will be saved in the "Scan" folder on the device, it will be called USR_xxxx.efx where xxxx is a unique number and can be retrieved using the V8 EFILive Explorer program.

Problems when data logging using the V7.5 pass-thru software:

Depending on the type of error, an error report may or may not be automatically generated. Automatically generated error reports will pop up on the screen. If the error report is not automatically generated, you can manually generate it by selecting the menu option: File->Generate error report or press the hotkey: Ctrl+G.

Once the report is generated, click the [Save] button on the report to save the file.

EFILive V7.5 application fails to start or displays an error when starting:

To force the EFILive V7 software to create and save a log file you must start the application with the command line parameter /l (forward slash, lowercase L for log) . To add command line parameters to the EFILive V7.5 software you must modify the application's shortcut Target field.

Locate the "EFILive Tune Tool" or "EFILive Scan Tool" desktop icon of the application that you wish to log. Right click the icon and select "Properties". Append the following three characters to the Target field: /l (space, forward slash, lowercase L) as shown in the image below:

Then run the EFILive V7.5 software using the modified shortcut until you have reproduced the problem.

The support file will be saved in the \Program Files\EFILive\V7.5 folder, it will be called StartupLog.txt. On some systems, the EFILive V7.5 application cannot create or save the StartupLog.txt file in the "Program Files" folder unless it is started with administrator privileges. To do that, right click on the EFILive desktop icon and select "Run as Administrator".

EFILive V8 application fails to start or displays an error when starting:

To force any of the V8 applications to create a log file, hold down one of the Ctrl keys on the keyboard when starting the application. The application's start up log will be saved in the folder: \My Documents\EFILive\V8\Trace

Each application will save a log file with a unique name:

  • EFILive Scan and Tune: EFILive_ScanAndTune_StartupLog.txt
  • EFILive Explorer: EFILive_Explorer_StartupLog.txt
  • EFILive Control Panel: EFILive_Hapi_StartupLog.txt

NOTE: If you are starting V8 Scan and Tune from the desktop icon, and you hold down the Ctrl key when double clicking the icon, unexpected (but technically correct) things happen:

  • If the EFILive Scan and Tune desktop icon is currently highlighted as the selected icon, then holding down the Ctrl key while double clicking on it does not actually start the application. That is because the first click (of the double click) un-selects the icon (because the Ctrl is pressed), the second click simply highlights it again and you're back where you started without actually starting the application
  • On some Windows configurations, holding down the Ctrl key while starting an application can cause the application to start as a minimized window with just an icon on the task bar. In that case, the user should expand the EFILive window by clicking on the task bar icon.

Further information on trace and log files can be found in our latest V8 software in the EFILive V8 reference guide. Click Start->All Programs->EFILive->V8->Documents->EFILive V8 Reference, or access this document from the Help menu contained within our V8 software.