Known issues with the October 2015 Public Pre-Release
Currently known issues and possible workarounds for the October 2015 Public Pre-Release of the EFILive Software and Firmware
Download the current/stable release software here: http://www.efilive.com/latest/cat/download-efilive
Download the public pre-release software here: https://forum.efilive.com/showthread...ic-Pre-Release
Public pre-release software versions:
- Software: V7.5.7.296
- Software: V8.2.2.287
- FlashScan/AutoCal firmware: V2.07.92
Issue 1:
If you are Black Box Logging PIDs from an ECM and TCM simultaneously and you have selected a PID from the transmission controller (TCM) that has an identically named PID in the engine controller (ECM), then when the log file is loaded back into the V8 software for viewing, that TCM PID will be displayed as if it originated from the ECM. The PID's data will have correctly been logged from the TCM, only its name will appear to indicate that it was logged from the ECM.
Workaround:
None.
It is a restriction of the *.efi (V7.5 log file format). That restriction will be removed and the TCM PIDs will display their true origin once the V8 scan tool software is available.
Issue 2:
In the V8 Scan Tool, opening or switching to a different dashboard that contains one or more PIDs that are not supported for the currently selected controller type will trigger an "Access Violation".
Workaround:
Manually select the correct controller type for the dashboard before opening or switching the dashboard.
Please see post #2 below regarding "Dashboard" vs "Scan Display".
Issue 3:
The EXT.AD1 and EXT.AD2 PIDs are named incorrectly in the sae_generic.txt file.
The Serial wide band BEN factor PIDs are missing from the sae_generic.txt file.
Workaround:
Download and save the corrected sae_generic.txt file into the folder: \Program Files (x86)\EFILive\V7.5\Configuration - overwrite the existing file.
Issue 4:
V7.5 dashboard names are not being saved correctly into log files during black box logging. That means the requested dashboard does not load automatically when opening those BBX log files.
Workaround:
None. Will be fixed in the next update.
Issue 5:
Full flashing is not yet supported for E86B controllers with boot block 12664192.
Workaround:
Download the attached E86B_12664192.zip file and unzip it into the folder: \Program Files (x86)\EFILive\V8, overwrite existing files.
If you are using Black Box Flashing, then after unzipping the attached file you must perform a [Check Firmware] option from the main V8 screen to update the files to your FlashScan device. If the files were unzipped successfully to your PC then E86B_F.obj file should display as "Update Required".
Issue 6:
Calculated AFR PIDs that should refer to EXT.AD2, instead refer to AD1.
Workaround:
Download and save the corrected sae_generic.txt file into the folder: \Program Files (x86)\EFILive\V7.5\Configuration - overwrite the existing file.
Issue 7:
Calculated PIDs that are defined in the V8 scan tool using a prefix (i.e. source name) other than "CALC" (e.g. WO2A.AFR_LC11) are not automatically loaded/displayed when opening log files that contain those PIDs.
Workaround:
After opening the log file, re-select the desired calculated PIDs.
Will be fixed in the next update.
