Page 7 of 11 FirstFirst ... 56789 ... LastLast
Results 61 to 70 of 104

Thread: BB Logging beta update: April 14, 2008

  1. #61
    swingtan
    Guest

    Default

    Quote Originally Posted by Blacky View Post
    The problem was the E38 and E67 DMA PIDs are prefixed with E38 and E67 respectively. Black Box Logging was adding the prefix GM in the *.efi files. When the *.tun files were loaded into the scanner, it could not find (for example) the PID GM.AFRATIO_DMA because the PID is actually called E38.AFRATIO_DMA.

    If you really need the data from those log files, you can edit the *.efi files using Hexedit (from www.bpsoft.com). Change the GM.xxxxxx_M PID names to E38.xxxxxx_M names. In Hexedit that will require you to insert a character after the GM. I.e change the existing "GM" prefix to "E3" and then insert an "8" to make the prefix "E38".

    Regards
    Paul
    Thanks Paul,

    I've edited a few log files and the data comes up well. By the way, all the log files I've tried this evening open fine, including the one I was having trouble with earlier today. I did plug in the V2 this afternoon and EFILive_Tune.exe had a "fatal exception" error. I restarted it, flashed a tune and now ScanTool seems to be OK....... Perhaps the "corrupt log file" problem is OS related.

    Simon.

  2. #62
    Joe (Moderator) joecar's Avatar
    Join Date
    Apr 2003
    Posts
    28,400

    Default

    Quote Originally Posted by Blacky View Post
    Hi Joe,

    I still can't reproduce this problem here.
    Can you tell me the settings you have checked in Properties->Printing?
    Thanks
    Paul
    See attached pic...
    Attached Thumbnails Attached Thumbnails Click image for larger version. 

Name:	Clipboard02.png 
Views:	231 
Size:	24.1 KB 
ID:	3090  

  3. #63
    Senior Member
    Join Date
    Oct 2005
    Posts
    175

    Default

    Quote Originally Posted by GMPX View Post
    Lennart, the DVT's should disable pretty much instantly, there is also some timers in the ECM that should shut them off if Flashscan is no longer broadcasting the override messages.
    So on your idle speed control, as soon as you untick the idle speed control box the ECM should return to normal operation.
    When you say the idle speed remains in DVT mode, for how long is this for?

    Cheers,
    Ross

    Ross,

    I am sending you a log file while I was using the DVT controls.
    The idle speed will not return to normal by disabling the DVT switch. Rail pressure seems to work fine, though.
    Should I be able to change more than one setting at once?
    I was unable to change rail pressure while idle speed was changed.
    Idle speed did return to normal, don`t know what it takes, though.....it is not time but perhaps 0+% TP over time....
    VNT seems to work as well, even though it sounds like it only works in one direction....once it is a 0% you will not get the hissing back by moving the slider.
    2005 RCSB 2500HD GMC Sierra DURAMAX LLY
    1955 Chevy Truck 1st series, being restored
    2002 Mercedes C270 CDI

  4. #64
    Lifetime Member
    Join Date
    Feb 2007
    Posts
    517

    Default

    I guess I'm retarded. I updated my firmware to v2.04.71, then followed the directions for the boot block upgrade, but now I can't get my firmware to update to v2.05.16 and the flash cable is stuck in the blinking LED mode. WTF did I do wrong?

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

    Default

    Quote Originally Posted by swingtan View Post
    I have an update for the PID's issue. I tried pass-through logging this afternoon and noticed that E38.AFRATIO_DMA was reading wrong. It was reading 0.56:1.

    Here's the log file.....
    What is the operating system of the ECM that you are logging?
    Regards
    Paul
    Before asking for help, please read this.

  6. #66
    EFILive Developer Site Admin Blacky's Avatar
    Join Date
    Mar 2003
    Posts
    9,606

    Default

    Quote Originally Posted by JoshH View Post
    I guess I'm retarded. I updated my firmware to v2.04.71, then followed the directions for the boot block upgrade, but now I can't get my firmware to update to v2.05.16 and the flash cable is stuck in the blinking LED mode. WTF did I do wrong?
    After the boot block upgrade you can no longer use the FlashScan Firmware Programming software that you would have used in the past. Instead you must use the EFILive_Explorer.exe program that is part of the BBL beta software download.
    After you have downloaded and unzipped the BBL Beta software zip file, you can find that program here \Program Files\EFILive\V8\EFILive_Hapi\EFILive_Explorer.exe

    Regards
    Paul
    Before asking for help, please read this.

  7. #67
    swingtan
    Guest

    Default

    Quote Originally Posted by Blacky View Post
    What is the operating system of the ECM that you are logging?
    Regards
    Paul
    Hi Paul,

    OS is 12607218.

  8. #68
    Lifetime Member
    Join Date
    Feb 2007
    Posts
    517

    Default

    Thanks Paul. That did it. I knew it was something stupid I was doing wrong.

  9. #69
    Lifetime Member GMPX's Avatar
    Join Date
    Apr 2003
    Posts
    13,128

    Default

    Quote Originally Posted by Lennart View Post
    Ross,

    I am sending you a log file while I was using the DVT controls.
    The idle speed will not return to normal by disabling the DVT switch. Rail pressure seems to work fine, though.
    Should I be able to change more than one setting at once?
    I was unable to change rail pressure while idle speed was changed.
    Idle speed did return to normal, don`t know what it takes, though.....it is not time but perhaps 0+% TP over time....
    VNT seems to work as well, even though it sounds like it only works in one direction....once it is a 0% you will not get the hissing back by moving the slider.
    Wow this thread is a mess to follow
    It's quite odd that the disables have no immediate effect. Out of interest, can you try the idle speed control (and VNT too as well I guess) whilst you are not logging at the same time. Perhaps some messages are just not getting through whilst logging at the same time. Not suggesting this is the solution, just curious to see if it cures the intermittent response from the ECM.

    Thanks,
    Ross
    I no longer monitor the forum, please either post your question or create a support ticket.

  10. #70
    swingtan
    Guest

    Default

    Quote Originally Posted by GMPX View Post
    Wow this thread is a mess to follow

    Ross
    I agree, but at the moment we don't have a proper tracking system for bugs / issues found with the BBL beta releases. I guess you "could" set up a proper logging and tracking system, but that would just take your time away from releasing the next update......

    Simon.

Page 7 of 11 FirstFirst ... 56789 ... LastLast

Similar Threads

  1. BB Logging beta update: April 26, 2008
    By Blacky in forum FlashScan V2 BB Logging
    Replies: 121
    Last Post: July 19th, 2008, 04:44 PM
  2. BB Logging beta update: May 19, 2008
    By Blacky in forum FlashScan V2 BB Logging
    Replies: 105
    Last Post: June 11th, 2008, 10:22 AM
  3. BB Logging beta update: May 12, 2008
    By Blacky in forum FlashScan V2 BB Logging
    Replies: 45
    Last Post: May 27th, 2008, 09:01 AM
  4. BB Logging beta update: May 06, 2008
    By Blacky in forum FlashScan V2 BB Logging
    Replies: 87
    Last Post: May 22nd, 2008, 10:57 AM
  5. BB Logging beta update: April 07, 2008
    By Blacky in forum FlashScan V2 BB Logging
    Replies: 71
    Last Post: April 14th, 2008, 10:31 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
  •