Results 1 to 10 of 26

Thread: Known Issues With Current Public 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,490

    Default Known Issues With Current Public Release

    Latest updates (released as an auto-update):

    • EFILive V7 software: V7.5.10.323 (updated Feb 19, 2017)
    • EFILive V8 software: V8.2.5.316 (updated Feb 19, 2017)
    • Boot Block: V2.07.007 (Feb 07, 2014)
    • Firmware: V2.07.113 (Feb 19, 2016) (updated Feb 19, 2017)


    Updates are described here: What's New

    Use these links to download the latest version:
    EFILiveV8.2.5.316_Setup.exe
    EFILiveV7.5.10.323_Setup.exe


    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:
    Some LS1B tune files report "Controller type cannot be determined" when opened in the V7.5 software.
    Workaround:
    Update to V7.5.9 build 322.

    Issue 4:
    After Issue 3 was fixed, the software and firmware numbers were out of sync, causing the V7.5.9.322 V7 software to be detected as incompatible with the V2.07.112 firmware.
    Workaround:
    All version numbers have been re-synchronized.
    Please update to:
    Version 7: V7.5.10.323
    Version 8: V8.2.5.316
    Firmware: V2.07.113

    Issue 5:
    The full-flash and cal-flash counters in FlashScan and AutoCal are not updating when flashing controllers via the V8 software. They only update when flashing via the V7.5 software.
    Workaround:
    None. Will be fixed in the next update.
    Last edited by Blacky; April 2nd, 2017 at 02:12 PM. Reason: Fixed dates
    Before asking for help, please read this.

Similar Threads

  1. Known Issues With Current Public Release
    By Blacky in forum Software Updates and Installation Help
    Replies: 22
    Last Post: February 17th, 2017, 06:06 AM
  2. Known Issues With Current Public Release
    By Blacky in forum Software Updates and Installation Help
    Replies: 70
    Last Post: January 31st, 2017, 11:02 AM
  3. Known issues with June 02, 2015 Public Release
    By Blacky in forum Software Updates and Installation Help
    Replies: 18
    Last Post: July 8th, 2015, 04:07 PM
  4. Known issues with May 01, 2015 Public Release
    By Blacky in forum Software Updates and Installation Help
    Replies: 64
    Last Post: June 2nd, 2015, 09:46 AM
  5. Known issues with April 13, 2015 Public Release
    By Blacky in forum Software Updates and Installation Help
    Replies: 32
    Last Post: April 30th, 2015, 07:33 AM

Posting Permissions

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