Currently known issues and possible workarounds for the July 08, 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.286
- Software: V8.2.2.279
- FlashScan/AutoCal firmware: V2.07.85
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:
FlashScan V1 devices licensed as "Personal" are being incorrectly recognized as Scan-Only devices which prevents flashing controllers. FlashScan V1 devices licensed as "Commercial" are not affected.
Workaround:
Contact EFILive (support@efilive.com) for a free Personal to Commercial upgrade. Include your FlashScan V1 serial number in your email.
Issue 3:
BBX custom PID units are not being saved/reloaded correctly when saving BBX options files.
Workaround:
None. Will be fixed in next update.
Issue 4:
Comparing calculated PID values does not always appear to work consistently.
Workaround:
From Wikipedia:
Future versions of EFILive V8 will provide a floating point comparison function similar to this: SameValue(V1,V2,epsilon) which will return TRUE if the floating point values V1 and V2 differ by epsilon or less.The use of the equality test (if (x==y) ...) requires care when dealing with floating-point numbers.
Even simple expressions like 0.6/0.2-3==0 will, on most computers, fail to be true[41] (in IEEE 754 double precision, for example, 0.6/0.2-3 is approximately equal to -4.44089209850063e-16).
Consequently, such tests are sometimes replaced with "fuzzy" comparisons (if (abs(x-y) < epsilon) ..., where epsilon is sufficiently small and tailored to the application, such as 1.0E−13).
The wisdom of doing this varies greatly, and can require numerical analysis to bound epsilon.