Results 1 to 2 of 2

Thread: Current Public Release (May 2018)

  1. #1
    EFILive Developer Site Admin Blacky's Avatar
    Join Date
    Mar 2003
    Posts
    9,003

    Default Current Public Release (May 2018)

    Release Notes:
    Version Numbers:
    After installing the Dec 2017 Public Release Release you should have the following software, boot block, firmware versions installed:

    • EFILive V7 software: V7.5.20 To view the installed version, select Help->About (in the V7 Scan or Tune software).
    • EFILive V8 software: V8.2.16 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.133 (May 03, 2017) To view/update the Firmware, click the [Check Firmware] button in the V8 Scan and Tune software.


    Download here:
    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:
    Adding a key to the [Remote] section of a tune file is only active for the following controllers: LS1B, E38, E40, E54, E60 and E67.
    Workaround:
    None.
    Support for additional controllers will be added in a future update.

    -
    Before asking for help, please read this.

  2. #2
    Junior Member
    Join Date
    Apr 2016
    Posts
    29

    Default

    EDIT: I found a solution to this issue. On Windows 10, there's a new feature "Ransomware Protection" in the system settings. I had "controlled folder access" enabled (this may be the default in Win 10 Pro). In the menus there's an option to allow an app through controlled folder access. I added the EFILive_ScanAndTune.exe to the list of "allowed apps" in the "allow an app through controlled folder access submenu" and it seems to work just fine now. I'll be adding the other executables from EFILive to this list, but it seems possible that Microsoft could be engaged to let your software through. It appears that Win10 Home DOES NOT have this feature at all, so if you guys try to repro, please use Win10 Pro.
    -------------------------------------------------------------------------------------------------------------


    I just tried a clean install of this release (Windows 10 with latest updates from MS), and though the software appears to install, running v8 Scan & Tune gives repeated error dialogues-
    "Cannot create file "C:\Users\MyUser\Documents\EFILive\V8\Config\EFILi veScanAndTune.ini". The system cannot find the path specified."

    "Access Violation at address 00EBBF2A in module "EFILive_ScanAndTune.exe". Read of address 00000000."

    "Access Violation at address 00EBB7AC in module "EFILive_ScanAndTune.exe". Read of address 00000019."

    "Access Violation at address 0096D335 in module "EFILive_ScanAndTune.exe". Read of address 00000000."

    "Access Violation at address 00992615 in module "EFILive_ScanAndTune.exe". Read of address 0000000C."

    After dismissing all of these (several repeat), the software launches, but none of the modules work, Scan, Tune, Tools, etc (I get more access violations.)

    I'm running the EXE as an administrator on the admin account, and have tried the Win10 compatibility settings to run it in WinXP, Win 7 and Win 8 modes to no avail. (I had the same issue with the last public release.)

    This is my main tuning machine, so I'm hoping there's something in the works, previous service packs of Win 10 (or whatever MS calls them now) worked just fine, and there's not a good way to prevent auto updates without shutting off internet access.

    Let me know if there's any additional info I can provide that would be helpful for your team!
    Last edited by required field; 2 Hours Ago at 08:06 AM. Reason: Found solution!

Similar Threads

  1. Beta Test Release #3 (Apr 2018)
    By Blacky in forum Software Updates and Installation Help
    Replies: 1
    Last Post: 2 Weeks Ago, 06:54 AM
  2. Beta Test Release #2 (Feb 2018)
    By Blacky in forum Software Updates and Installation Help
    Replies: 23
    Last Post: March 19th, 2018, 05:54 PM
  3. Beta Test Release #1 (Feb 2018)
    By Blacky in forum Software Updates and Installation Help
    Replies: 29
    Last Post: February 12th, 2018, 06:20 PM
  4. Known Issues With Current Public Release
    By Blacky in forum Software Updates and Installation Help
    Replies: 22
    Last Post: February 17th, 2017, 07:06 AM
  5. Known Issues With Current Public Release
    By Blacky in forum Software Updates and Installation Help
    Replies: 70
    Last Post: January 31st, 2017, 12:02 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
  •