Results 1 to 5 of 5

Thread: Known issues with the September 2015 Public Pre-Release

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

    Default Known issues with the September 2015 Public Pre-Release

    Currently known issues and possible workarounds for the September, 2015 Public Pre-Release of the EFILive Software and Firmware

    Download the current/stable release software here: http://www.efilive.com/latest/cat/download-efilive
    Download the public pre-release software here: https://forum.efilive.com/showthread...ic-Pre-Release

    Public pre-release software versions:

    • Software: V7.5.7.293
    • Software: V8.2.2.286
    • FlashScan/AutoCal firmware: V2.07.91



    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.

    Issue 2:
    DMA PID links defined in E40_Link.ini are incorrect.
    DMA PID links defined in E92_Link.ini are incorrect.
    Workaround:
    See this post: https://forum.efilive.com/showthread...l=1#post222648.

    Last edited by Blacky; October 28th, 2015 at 08:23 PM.
    Before asking for help, please read this.

  2. #2
    Lifetime Member GMC-2002-Dmax's Avatar
    Join Date
    Dec 2005
    Posts
    1,261

    Default

    Paul,

    What would cause an $053E code on an LMM and an LML remote file saved with only a security Cannot be read or viewed and a restriction for ECM SN# and Flashscan SN# and no restriction applied or in place for the actual VIN#.

    My production machine runs the May 1st, 2015 and I am sending files to dealers/customers using both the May 1st and later versions of software.

    I got two today with that error code ?

    Thanks,

    Tony
    www.ridgerunnerdieselperformance.com

    EMAIL ME

    Tuner of many, many Duramax and Cummins Diesels.


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

    Default

    Quote Originally Posted by GMC-2002-Dmax View Post
    Paul,

    What would cause an $053E code on an LMM and an LML remote file saved with only a security Cannot be read or viewed and a restriction for ECM SN# and Flashscan SN# and no restriction applied or in place for the actual VIN#.

    My production machine runs the May 1st, 2015 and I am sending files to dealers/customers using both the May 1st and later versions of software.

    I got two today with that error code ?

    Thanks,

    Tony
    Before jumping in to try and explain this I found that the error descriptions for $053D and $053E in the PDF error doc are swapped.
    $053D is shown incorrectly as "VIN security restriction in *.ctz file does not match controller's VIN."
    $053E is shown incorrectly as "Device license number is not valid."
    The error descriptions in the [F8: Tools]->[F8: Lookup Errors] tab page show the correct description but the wrong "Cause" and "Action".
    I'll have those error messages fixed in the next update.

    Meanwhile, the error $053E is "VIN security restriction in *.ctz file does not match controller's VIN.". It is caused when the VIN security field contains more than 1 character and those characters do not match the target vehicle's VIN. Because you said that there is nothing in the VIN this error should not occur. Is it possible the VIN has a bunch of space characters in it that are impossible to see?

    Can you please send me the file that won't flash? (paul@efilive.com)

    Regards
    Paul
    Before asking for help, please read this.

  4. #4
    Lifetime Member GMC-2002-Dmax's Avatar
    Join Date
    Dec 2005
    Posts
    1,261

    Default

    I will verify that and let you know.

    The error code pdf had no mention of that code, I found an older pdf version that listed it.

    Thank You.

    On Edit:

    Opening/clearing/saving only the "ECM SN# for a restriction" worked........maybe there was an extra space that was populated by accident in the VIN area ??? .
    www.ridgerunnerdieselperformance.com

    EMAIL ME

    Tuner of many, many Duramax and Cummins Diesels.


  5. #5
    Lifetime Member Ninety8C5's Avatar
    Join Date
    Sep 2003
    Posts
    433

    Cool

    DMA PID links defined in E39_Link.ini are incorrect, also.

Similar Threads

  1. Known issues with Aug 27, 2015 Public Pre-Release
    By Blacky in forum Software Updates and Installation Help
    Replies: 1
    Last Post: September 7th, 2015, 11:36 AM
  2. Known issues with Aug 13, 2015 Public Pre-Release
    By Blacky in forum Software Updates and Installation Help
    Replies: 25
    Last Post: August 27th, 2015, 09:14 AM
  3. Known issues with Aug 07, 2015 Public Pre-Release
    By Blacky in forum Software Updates and Installation Help
    Replies: 18
    Last Post: August 8th, 2015, 10:42 AM
  4. Known issues with July 08, 2015 Public Pre-Release
    By Blacky in forum Software Updates and Installation Help
    Replies: 26
    Last Post: July 27th, 2015, 04:59 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
  •