Results 1 to 8 of 8

Thread: November 2016: EFILive Beta Test Release

Threaded View

Previous Post Previous Post   Next Post Next Post
  1. #1
    EFILive Developer Site Admin Blacky's Avatar
    Join Date
    Mar 2003
    Posts
    9,119

    Default November 2016: EFILive Beta Test Release

    Please download and install both the V7.5 and V8 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.

    IMPORTANT:
    During the beta test phase, the EFILive software and firmware version numbers have been updated multiple times as follows:

    1. Version 7.5 software: V7.5.7 to V7.5.8 and again to V7.5.9.
    2. Version 8 software: V8.2.2 to V8.2.3 and again to V8.2.4.
    3. Firmware: V2.07.104 to V2.07.105 and again to V2.07.106

    Those version number changes reflect two major compatibility updates:

    • The *.ctz and *.coz tune files' internal formats have been updated.
      Any tune file saved with one version cannot be opened using a previous version.
      A tune file saved with a previous version can be opened with a later version.
      For the purpose of determining tune file compatibility, the third digit of the software version number is used.
    • The *.obj read/flash script files have been updated. If you create a *.bbx quick setup file for your customers' AutoCal devices using this software and firmware version, then you must ensure that the users' AutoCal devices are also using this software and firmware version.


    Release Notes:
    Key Features:
    • 2017 Cummins support.
    • 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.

    Version Numbers:
    After installing this beta release you should have the following software, boot block, firmware versions installed:

    • EFILive V7 software: V7.5.9 Build 313 To view the installed version, select Help->About (in the V7 Scan or Tune software).
    • EFILive V8 software: V8.2.4 Build 307 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.106 (Oct 27, 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.
    Last edited by Blacky; November 21st, 2016 at 04:19 PM.
    Before asking for help, please read this.

Similar Threads

  1. September 2016: EFILive Beta Test Release
    By Blacky in forum EFILive Beta Software
    Replies: 42
    Last Post: October 18th, 2016, 07:53 AM
  2. July 2016: EFILive Beta Test Release
    By Blacky in forum EFILive Beta Software
    Replies: 28
    Last Post: September 5th, 2016, 02:18 PM
  3. May 2016: EFILive Beta 3 Test Release
    By Blacky in forum EFILive Beta Software
    Replies: 10
    Last Post: June 6th, 2016, 06:30 PM
  4. April 2016: EFILive Beta 2 Test Release
    By Blacky in forum EFILive Beta Software
    Replies: 6
    Last Post: April 30th, 2016, 07:49 AM
  5. April 2016: EFILive Beta Test Release
    By Blacky in forum Software Updates and Installation Help
    Replies: 0
    Last Post: April 9th, 2016, 02:46 PM

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •