July 2016, Release Candidate 3

[Blacky]

Please download and install both the V7.5 and V8 software packages.

Both the V7.5 and V8 software were updated in Release Candidate 3, you should download and install both V7.5 and V8 software packages.






Release Notes:
Whats New (http://download.efilive.com/Software/whatsnew_302.htm)


Version Numbers:

After installation, you should have the following software, boot block and firmware versions installed:



EFILive V7 software: V7.5.7 Build 309 To view the installed version, select Help->About (in the V7 Scan or Tune software).
EFILive V8 software: V8.2.2 Build 302 To view the installed version, select Help->About (in the V8 Scan and Tune software).
Boot Block: V2.07.007 (Feb 07, 2014) To view/update the Boot Block, click the [Check Firmware] button in the V8 Scan and Tune software.
Firmware: V2.07.102 (July 08, 2015) To view/update the Firmware, click the [Check Firmware] button in the V8 Scan and Tune software.


Known Issues

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 and fully integrated with the V8 tuning tool software.
Issue 2:
When logging DMA PIDs (i.e. PIDs whose names end with "_M" or "_DMA"), if the ignition is switched off for an extended period while data logging but data logging is not terminated, then when the ignition is switched on again the data log automatically continues. However the DMA PIDs may no longer return valid data.
Workaround:
EFILive recommends stopping the data log and restarting the data log when switching off the ignition for extended periods.
Issue 3:
The "What's New" release notes displayed in the EFILive V8 software show the firmware date as July 04, 2016.
Workaround:
The firmware date should be July 08, 2016.
.

[joecar]

Thanks.

[69camaro5speed]

I did a read on a t43 and it has a update checksum warning, After reading the info that comes up it seems I can hit the update checksum and save the file it will be safe to use because it had read it from a working car?
Is this the fix for the checksum err that can happen with a controller that has be modified with other software then you 20123try to flash it back

[GMPX]

It just says the checksums are disabled (for some reason), not that they are wrong. If they were wrong indicating corruption then you wouldn't fix it, but as they are only disabled then you should be fine to correct them and resave the file.

[Kennedy Diesel]

I get HTTP 404 not found for the links to the software.

http://download.efilive.com/Software/V7.5/EFILiveV7.5.7.309_RC3.exe

[Blacky]

I get HTTP 404 not found for the links to the software.

http://download.efilive.com/Software/V7.5/EFILiveV7.5.7.309_RC3.exe

RC3 has been superseded by the public release here: http://www.efilive.com/latest/cat/download-efilive
There is also a newer (beta) version available here: https://forum.efilive.com/showthread.php?26884-July-2016-EFILive-Beta-Test-Release

Regards
Paul