Page 1 of 3 123 LastLast
Results 1 to 10 of 26

Thread: April 2017, Beta Release 2

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

    Default April 2017, Beta Release 2

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

    Download EFILive V7.5 (Updated to build 326 on April 21 to fix issue #4)
    Download EFILive V8

    ATTENTION - BETA SOFTWARE RELEASE
    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. lf you conduct a tuning business, please take the necessary precautions to protect your business. EFlLive recommends beta testers use a separate FlashScan V2 device (when installing the latest beta firmware) and only install the EFlLive beta test software on a separate PC, laptop or virtual machine.

    Release Notes:
    Key Features:
    • Added extended descriptions for encoded PID values for most PIDs.
    • Fixed Cummins "Fast CAN" mode for CMD/CME controllers.
    • Fixed "Save As..." option so that it correctly defaults to the file's original folder.
    • Fixed V8 pass-thru scanning not working on VPW based controllers.
    • Fixed signed bitmask definitions in *.cax files (fixed in build 326).


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

    • EFILive V7 software: V7.5.10 Build 326 To view the installed version, select Help->About (in the V7 Scan or Tune software).
    • EFILive V8 software: V8.2.5 Build 318 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.115 (Apr 18, 2017) 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 FPRACOM and FPRADES PIDs are not being handled correctly by the V7 scan tool software. If you include those PIDs in a V7 data log it may appear that multiple PIDs in the log file are corrupt.
    Workaround:
    Don't select those PIDs when logging LBZ/LMM using V7 or BBL.
    If you already have a log file with those PIDs in it that appears to be corrupt, try opening the log file in V8 to automatically strip out those two PIDs.

    Issue #4:
    Defining a bitmask on a signed negative value in a *.cax file definition causes the tune file to fail to load.
    Workaround:
    Update to V7.5.10 Build 326.
    Last edited by Blacky; July 2nd, 2017 at 04:03 PM.
    Before asking for help, please read this.

  2. #2
    Junior Member
    Join Date
    Oct 2011
    Posts
    35

    Default

    With a bitmask applied to a 32b signed value, the tune tool will fail to load the tune. If the value is defined as unsigned, it will load the tune properly.
    03 6spd

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

    Default

    Quote Originally Posted by BlackCPG View Post
    With a bitmask applied to a 32b signed value, the tune tool will fail to load the tune. If the value is defined as unsigned, it will load the tune properly.

    Can you send me an example tune file and cax that fails to load?
    I've tried a signed 32 bit value with a 16 bit mask and it loades fine here :(

    Send to paul@efilive.com

    Regards
    Paul
    Before asking for help, please read this.

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

    Default

    Quote Originally Posted by Blacky View Post
    Can you send me an example tune file and cax that fails to load?
    I've tried a signed 32 bit value with a 16 bit mask and it loades fine here :(

    Send to paul@efilive.com

    Regards
    Paul
    Never mind, I reproduced the fault.
    I've updated the first post with V7.5 build 326 with the fault fixed.

    Regards
    Paul
    Before asking for help, please read this.

  5. #5
    Junior Member
    Join Date
    Oct 2011
    Posts
    35

    Default

    Quote Originally Posted by Blacky View Post
    Never mind, I reproduced the fault.
    I've updated the first post with V7.5 build 326 with the fault fixed.

    Regards
    Paul
    Thank you!! Ignore my email...
    03 6spd

  6. #6
    Lifetime Member oztracktuning's Avatar
    Join Date
    Nov 2005
    Posts
    594

    Default

    Hi Paul
    Flashing a LS1B PCM today caused trouble. It took about 8min or longer to flash and twice came up with errors at the end saying checksum errors. This was on two different ecus and using 129005 OS.

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

    Default

    Quote Originally Posted by oztracktuning View Post
    Hi Paul
    Flashing a LS1B PCM today caused trouble. It took about 8min or longer to flash and twice came up with errors at the end saying checksum errors. This was on two different ecus and using 129005 OS.
    Can you please send me the trace files of those failed and successful flashes?

    Regards
    Paul
    Before asking for help, please read this.

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

    Default

    Quote Originally Posted by oztracktuning View Post
    Hi Paul
    Flashing a LS1B PCM today caused trouble. It took about 8min or longer to flash and twice came up with errors at the end saying checksum errors. This was on two different ecus and using 129005 OS.
    Confirmed that 4x mode is being ignored for VPW cal-flashing and full-flashing. Will be fixed in next update.
    Still investigating the checksum errors
    ...
    Regards
    Paul
    Before asking for help, please read this.

  9. #9
    Joe (Moderator) joecar's Avatar
    Join Date
    Apr 2003
    Posts
    27,798

    Default

    Hi Paul,

    In the scantool, I add some calc pids, then the following situations evolve:
    a. I go File->Save and Save Log File is greyed out;
    b. I go File->Save As->Save Log File As and the save dialog places the filename Log_0001.efi (which happens to exist in my fodler) instead of the current filename of the log file;

    ( note that situation b. can cause you to accidentally overwrite the wrong log file ).

    V7
    Last edited by joecar; May 2nd, 2017 at 05:31 AM.

  10. #10
    Joe (Moderator) joecar's Avatar
    Join Date
    Apr 2003
    Posts
    27,798

    Default

    ( question: when I add a specific vdb and I save the log file (after adding calc pids) the scantool saves the vdb filename in the log file, is that correct...? )

    V7

Page 1 of 3 123 LastLast

Similar Threads

  1. April 2017, Beta Release 1
    By Blacky in forum Software Updates and Installation Help
    Replies: 17
    Last Post: April 18th, 2017, 01:31 PM
  2. April 2016: EFILive Beta 2 Test Release
    By Blacky in forum EFILive Beta Software
    Replies: 6
    Last Post: April 30th, 2016, 07:49 AM
  3. Known issues with the April 2016 Beta Test Release
    By Blacky in forum EFILive Beta Software
    Replies: 39
    Last Post: April 18th, 2016, 04:07 PM
  4. Known issues with the April 2016 Beta Test Release
    By Blacky in forum Software Updates and Installation Help
    Replies: 2
    Last Post: April 10th, 2016, 07:23 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
  •