Page 1 of 4 123 ... LastLast
Results 1 to 10 of 37

Thread: June 2016 Release Candidate 2

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

    Default June 2016 Release Candidate 2

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

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

    Release Notes:
    Version Numbers:
    After installation, you should have the following software, boot block and firmware versions installed:
    EFILive V7 software: V7.5.7 Build 308 To view the installed version, select Help->About (in the V7 Scan or Tune software).
    EFILive V8 software: V8.2.2 Build 301 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.101 (June 06, 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 V8 software shows the checksum as incorrect for some CME tune files even when the checksum is correct.
    Workaround:
    Fixed in V8 RC2 Update 1.

    Issue 4:
    When an LMM tune file with operating system 12620015 is loaded into V7.5 no calibrations are available.
    Workaround:
    Download the attached 12620015.calz file and save it into the folder: \Program Files (x86)\EFILive\V7.5\Calibrations\E35, overwrite the existing file, you may need admin privileges to overwrite the existing file.

    .
    Attached Files Attached Files
    Last edited by cindy@efilive; March 5th, 2017 at 03:41 PM.
    Before asking for help, please read this.

  2. #2
    Lifetime Member
    Join Date
    Nov 2005
    Posts
    1,753

    Default

    Software in first post has now been updated.

    Cheers
    Cindy

  3. #3
    Joe (Moderator) joecar's Avatar
    Join Date
    Apr 2003
    Posts
    28,403

    Default

    Quote Originally Posted by cindy@efilive View Post
    Software in first post has now been updated.

    Cheers
    Cindy
    Thanks for the heads up.

  4. #4
    New Member
    Join Date
    Mar 2011
    Posts
    8

    Default

    I received this error when I was trying to open BBX on an Autocal for a customer using RC2. Have not come across this one before. Have uninstalled, downloaded new copy and reinstalled RC2.
    Attached Thumbnails Attached Thumbnails Click image for larger version. 

Name:	EFLive Error.PNG 
Views:	312 
Size:	183.0 KB 
ID:	19921  

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

    Default

    Quote Originally Posted by mrmanners View Post
    I received this error when I was trying to open BBX on an Autocal for a customer using RC2. Have not come across this one before. Have uninstalled, downloaded new copy and reinstalled RC2.
    That error occurs when you have a non *.bbx file that has been saved (or renamed) with a *.bbx extension. True *.bbx files contain multiple config files. If any file is named with a *.bbx extension that does not have all the required config files inside it, then you will see that error.

    Regards
    Paul
    Before asking for help, please read this.

  6. #6
    New Member
    Join Date
    Mar 2011
    Posts
    8

    Default

    Quote Originally Posted by Blacky View Post
    That error occurs when you have a non *.bbx file that has been saved (or renamed) with a *.bbx extension. True *.bbx files contain multiple config files. If any file is named with a *.bbx extension that does not have all the required config files inside it, then you will see that error.

    Regards
    Paul
    It throws that error before I am able to select a bbx file.

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

    Default

    Quote Originally Posted by mrmanners View Post
    It throws that error before I am able to select a bbx file.
    If the most recently used BBX config file has mistakenly/accidentally got a *.bbx extension then, when EFILive automatically tries to load that config file when you open the BBX window, it sees the *.bbx extension and attempts to load it as a bbx multi stream file instead.

    Close all EFILive software and open the file:\My Documents\EFILive\V8\Config\EFILiveScanAndTune.ini using Notepad.
    Look for the section [MRU Files] and the key "Options". That is the file that is automatically loaded when you open the BBX window. If that file name ends with *.bbx then that is why you see the error.
    Remove that line from the *.ini file using Notepad then re-save the ini file.
    Restart the EFILive software.

    Regards
    Paul
    Before asking for help, please read this.

  8. #8
    New Member
    Join Date
    Mar 2011
    Posts
    8

    Default

    Quote Originally Posted by Blacky View Post
    If the most recently used BBX config file has mistakenly/accidentally got a *.bbx extension then, when EFILive automatically tries to load that config file when you open the BBX window, it sees the *.bbx extension and attempts to load it as a bbx multi stream file instead.

    Close all EFILive software and open the file:\My Documents\EFILive\V8\Config\EFILiveScanAndTune.ini using Notepad.
    Look for the section [MRU Files] and the key "Options". That is the file that is automatically loaded when you open the BBX window. If that file name ends with *.bbx then that is why you see the error.
    Remove that line from the *.ini file using Notepad then re-save the ini file.
    Restart the EFILive software.

    Regards
    Paul
    Thanks Paul, I will take a look.

  9. #9
    Junior Member
    Join Date
    Jun 2016
    Posts
    23

    Default

    Hello Paul

    I have some problems running the EFI Live tune tool. I run windows in VMware, but I have never experienced problems running programs.
    Attached Thumbnails Attached Thumbnails Click image for larger version. 

Name:	Skjermbilde 2016-06-23 kl. 10.57.55.png 
Views:	311 
Size:	29.7 KB 
ID:	19931  
    Last edited by EspenT; June 22nd, 2016 at 08:25 PM.

  10. #10
    Junior Member
    Join Date
    Jun 2016
    Posts
    23

    Default

    Quote Originally Posted by EspenT View Post
    Hello Paul

    I have some problems running the EFI Live tune tool. I run windows in VMware, but I have never experienced problems running programs.

    a "touch calc_pids.txt" from bash crated a empty file and that seems to do the trick Is that file missing in the installer? Does it contain important data?

Page 1 of 4 123 ... LastLast

Similar Threads

  1. June 2016 Release Candidate 1
    By Blacky in forum Software Updates and Installation Help
    Replies: 20
    Last Post: June 13th, 2016, 09:44 AM
  2. May 2016: EFILive Beta 3 Test Release
    By Blacky in forum EFILive Beta Software
    Replies: 10
    Last Post: June 6th, 2016, 06:30 PM
  3. March 2016: EFILive Pre-Release
    By Blacky in forum Software Updates and Installation Help
    Replies: 30
    Last Post: April 7th, 2016, 06:32 PM
  4. Known issues with the March 2016 Pre-Release
    By Blacky in forum Software Updates and Installation Help
    Replies: 6
    Last Post: March 23rd, 2016, 04:16 PM
  5. March 05, 2011 release candidate 2
    By Blacky in forum Software Updates and Installation Help
    Replies: 32
    Last Post: March 20th, 2011, 01:36 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
  •