Page 3 of 3 FirstFirst 123
Results 21 to 26 of 26

Thread: Known Issues With Current Public Release

  1. #21
    Junior Member
    Join Date
    Apr 2016
    Posts
    30

    Default

    I'm trying to open some BBX .efi log files in V8, and when opening it, I have to pick the controller, but "AEM UEGO Bank 1" isn't an option in the trans controllers section when opening the file, so I can't view the logged WBO2 PIDS. Selecting that after the fact clears the opened log file.

    https://forum.efilive.com/showthread...l=1#post236815 <- log in this post, I'm on build 316 w/ the matching firmware.

  2. #22
    Lifetime Member Mitco39's Avatar
    Join Date
    Jan 2009
    Posts
    648

    Default

    I stumbled across an issue that was introduced in the last few updates in the V7.5 Tune tool, I understand why the error is there but it used to work previously.

    When running scripts on the 68RFE side of the CMD/CME trucks I am getting an error that says "Does not describe a unique calibration area/rectangle", I know this is because the axis of the table are not neatly defined (as per OEM) and you have repeats. That said the scripts used to work in old revisions before this check was implemented.

    If this check has to stay for other reasons in other controllers what would be a work around to effectively make changes across different OS? For the same OS i can open side by side and copy the changes in the differences window, but different OS's mean a bunch of copy and paste which would take a considerable amount of time.

    Thanks

    MItch

  3. #23
    Member
    Join Date
    Feb 2016
    Posts
    62

    Default

    Quote Originally Posted by Mitco39 View Post
    I stumbled across an issue that was introduced in the last few updates in the V7.5 Tune tool, I understand why the error is there but it used to work previously.

    When running scripts on the 68RFE side of the CMD/CME trucks I am getting an error that says "Does not describe a unique calibration area/rectangle", I know this is because the axis of the table are not neatly defined (as per OEM) and you have repeats. That said the scripts used to work in old revisions before this check was implemented.

    If this check has to stay for other reasons in other controllers what would be a work around to effectively make changes across different OS? For the same OS i can open side by side and copy the changes in the differences window, but different OS's mean a bunch of copy and paste which would take a considerable amount of time.

    Thanks

    MItch
    I get the same message running scripts on E35B with MAF Scaling. I have to go into the scripted tune and change the MAF scaling manually after running the script.

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

    Default

    Quote Originally Posted by required field View Post
    I'm trying to open some BBX .efi log files in V8, and when opening it, I have to pick the controller, but "AEM UEGO Bank 1" isn't an option in the trans controllers section when opening the file, so I can't view the logged WBO2 PIDS. Selecting that after the fact clears the opened log file.

    https://forum.efilive.com/showthread...l=1#post236815 <- log in this post, I'm on build 316 w/ the matching firmware.

    Will be fixed in the next update.
    Regards
    Paul
    Before asking for help, please read this.

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

    Default

    Quote Originally Posted by Mitco39 View Post
    I stumbled across an issue that was introduced in the last few updates in the V7.5 Tune tool, I understand why the error is there but it used to work previously.

    When running scripts on the 68RFE side of the CMD/CME trucks I am getting an error that says "Does not describe a unique calibration area/rectangle", I know this is because the axis of the table are not neatly defined (as per OEM) and you have repeats. That said the scripts used to work in old revisions before this check was implemented.

    If this check has to stay for other reasons in other controllers what would be a work around to effectively make changes across different OS? For the same OS i can open side by side and copy the changes in the differences window, but different OS's mean a bunch of copy and paste which would take a considerable amount of time.

    Thanks

    MItch
    Scripts are automatically generated using col/row labels. That allows scripts to run against multiple different operating systems where the same tables were defined with different labels. Unfortunately, changing the labels' units and not displaying enough precision can sometimes lead to duplicate labels.

    In the past, duplicate labels were allowed and the software simply used the first label (of any duplicates) that it found. However, that was causing some scipts to miss and/or update the wrong row/column of data.

    There is no single magic solution to that problem.

    If you would prefer to, you can manually edit the scripts to use a more suitable method of "finding" the rectangle to be updated:

    If you are updating the entire table, then edit the script and change the rectangle definition from label values to the words: MIN,MIN,MAX,MAX which means the entire table. Obviously this only works if the table is always the same size.

    If you are only updating a portion of the table but you know exactly which rows/columns need to be updated then change it to something like @5,@3,@6,@9 which means all cells between columns 5 to 6 and rows 3 to 9. The order of the values is Left,Top,Right,Bottom.

    Regards
    Paul
    Before asking for help, please read this.

  6. #26
    Lifetime Member GMC-2002-Dmax's Avatar
    Join Date
    Dec 2005
    Posts
    1,294

    Default

    What V7.5 Version will work with V315 and Firmware 112 ?

    Every version from 319-322 I have tried has that error and 323 goes with 316 which I am hesitant to move to from 315

    I was forced to update to V8-316 and V7.5-323 to resolve the issues.

    THANKS !
    Attached Thumbnails Attached Thumbnails Click image for larger version. 

Name:	Firmware Mismatch.png 
Views:	234 
Size:	381.4 KB 
ID:	20866   Click image for larger version. 

Name:	Firmware OK - Control Panel.png 
Views:	249 
Size:	470.4 KB 
ID:	20867  
    Last edited by GMC-2002-Dmax; March 27th, 2017 at 09:20 AM.
    www.mscservices.net


    Tuner of many, many Duramax and Cummins Diesels.


Page 3 of 3 FirstFirst 123

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
  •