Currently known issues and possible workarounds for the August 07, 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.291
- Software: V8.2.2.284
- FlashScan/AutoCal firmware: V2.07.89
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:
EFILive_Explorer.exe reports incompatible version with EFILive_Hapi.exe.
Workaround:
Download and install Update 1.
Issue 3:
Changing the units of any PID in the V8 chart display to something other than the default metric units does not result in the PID being displayed in the selected units. Instead the PID remains displayed using its default metric units.
Workaround:
None, will be fixed in the next update.
Issue 4:
After right-clicking on a Scan Item entry in the [F5: BBX] window and changing the controller type so that the new controller type does not support one or more of the previous controller's selected PIDs, the software may fail with an access violation.
Workaround:
Don't change the controller type, instead create a new entry for the new controller type and then delete the entry for the old controller type. Will be fixed in the next update.
Issue 5:
The "Remote Key" setting is ignored for the following controllers: E37, E67, AL5.
Workaround:
None. Will be fixed in the next update.