Please download and install both the V7.5 and V8 software packages.
Both the V7.5 and V8 software were updated for this beta test release, you must update both software packages.
ATTENTION - BETA SOFTWARE RELEASE:
The EFILive beta software is available to all users. We strongly recommend that you do not install the beta software over the top of your production systems. It is possible that the beta test software may fail and your production system may not be recoverable. If you conduct a tuning business, please take the necessary precautions to protect your business. EFILive recommends that beta testers use a separate FlashScan V2 device (when installing the latest beta firmware) and only install the EFILive beta test software on a separate PC, laptop or virtual machine.
Release Notes:
Key Features:
- Controller Authorization to manage heightened security protocols for 2017 GM controllers.
- The first release of 2017 GM vehicle support including updated E92 Corvette and E82 ECM for LGX 3.6L V6.
- Changes to Remote Linking/Unlinking of AutoCal.
- Updated documentation to support recently added features.
Please note, with many new OS's released for 2017 models over several different ECM types, unsupported OS's may take some time to be completed and may not be currently supported in this release.
IMPORTANT:
The EFILive software version numbers have been updated from: V7.5.7 to V7.5.8 and from V8.2.2 to V8.2.3. That version number change reflects two major compatibility updates:
- The *.ctz and *.coz tune files have been updated.
Tune files that are saved with version V7.5.8 and later or with version V8.2.3 and later are not compatible with previous software versions. Tune files created with previous software versions are 100% compatible with this latest software version.
- The *.obj read/flash script files have been updated.
Script files distributed with this software version will not operate on devices with firmware V2.07.103 and earlier. So if you create a *.bbx quick setup file for your customers' AutoCal devices using this software version, then you must ensure that the target AutoCal devices are using firmware V2.07.104 or later.
Version Numbers:
After installing this beta release you should have the following software, boot block, firmware versions installed:
EFILive V7 software: V7.5.8 Build 311 To view the installed version, select Help->About (in the V7 Scan or Tune software).
EFILive V8 software: V8.2.3 Build 305 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.104 (Sep 17, 2016)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 enhanced PID FSST:FCLA (closed loop fuel active) displays the loop status backwards. I.e. it shows open for closed loop and closed for open loop.
Workaround:
Use the generic FUELSYS PID instead.
Issue 4:
DMA PIDs (i.e. PIDs with names ending in _M) do not log correct values when using the V8 pass-thru scanner.
Workaround:
Use the V7 pass-thru scanner or black box logging to log DMA PIDs.
Issue 5:
Reading and flashing in the V7 tune tool fails if the V7 scan tool property setting: [Advanced]->Priority is set to anything other than 3.
Workaround:
Ensure the property setting [Advanced]->Priority is set to 3.
Or preferably use the V8 tune tool read/flash options or the standalone BBx read/flash options.