BB Logging beta update: April 14, 2008

Printable View

Show 40 post(s) from this thread on one page

April 19th, 2008
Chevy366

Quote:

Originally Posted by Hyper99

Did you set COM In and COM Out to Wide-02 also?

Duh , thanks that was it , how do you say moron , oh yeah like that !
Did not dawn on me to set the COMs , I was like the V2 has only one RJ45 connection why two COMs , must be for Analog .

Many thanks .
April 19th, 2008
Hyper99

No problem
I remembered it because I missed it the first time around:doh2:

Glad I could help
April 19th, 2008
hymey

Quote:

Originally Posted by Black02SS

Was able to test Serial for LM-1 and LOVE it. Can't wait for the FJO to be supported. It is simply awsome. Only issue I saw was the values actually went past 20.9 on decel up to 120:1.1 AFR. Made the BEN show 6.0. LOL

Make sure you turn DFCO off when logging bens.
April 20th, 2008
Chevy366

Quote:

Originally Posted by Hyper99

No problem
I remembered it because I missed it the first time around:doh2:

Glad I could help

Here is a thought , make the default setting be WBO2 for COM1 and COM2 , I can see the need for a selectable WBO2 controller , i,e, Innovate , PLX etc ... , but default the COMs to a on state .:doh:
April 20th, 2008
Lennart

From todays experiments:
LLY TP PID does not work on the V2 but TP_A does!
The TP PID does display on the PC correctly.
When logging data it will overwrite existing files without any notice!
(after a reflash to the latest FW I might add)
What are the rules to the names, when is the counter reset?
Selecting LLY Auto does not work, no frames will be logged or updated data displayed.
DVT is pretty sweet! Turning on/off is a little weird sometimes as the setting will remain on even when shutting off the feature (e.g. idle speed)
April 20th, 2008
lakingslayer

Quote:

Originally Posted by Lennart

From todays experiments:
LLY TP PID does not work on the V2 but TP_A does!
The TP PID does display on the PC correctly.
When logging data it will overwrite existing files without any notice!
(after a reflash to the latest FW I might add)
What are the rules to the names, when is the counter reset?
Selecting LLY Auto does not work, no frames will be logged or updated data displayed.
DVT is pretty sweet! Turning on/off is a little weird sometimes as the setting will remain on even when shutting off the feature (e.g. idle speed)

I have all the above symptoms also except for the LLY auto not working. I use LLY auto for my logs. Do you see any weird frames when playing back your log on the PC?
April 20th, 2008
Lennart

Quote:

Originally Posted by lakingslayer

I have all the above symptoms also except for the LLY auto not working. I use LLY auto for my logs. Do you see any weird frames when playing back your log on the PC?

I did have one log file that was filled with notes rather than data.
April 20th, 2008
swingtan

Lennart and lakingslayer, the "weird frames or "logs full of notes" sounds like the problem I'm having as well. I've found that repeated tries at opening the file eventually seems to get a clean read and displays "sane" data. I have no idea if the data is actually correct though.

The way the logs look when they open in "corrupted" form reminds me of the first BBL logs I tried on the E38 when the V2 would cause I/O problems between the ECM and other modules, bringing up dash alerts and dropping corrupted data into the log file. This was back around the start of this year. When opening these files in ScanTool, I'd get the same weir looking data displayed as I get now. It's almost like the BBL files don't have an <EOF> character and ScanTool ends up with random data at the end of the log.

Simon.
April 20th, 2008
Blacky

Quote:

Originally Posted by lakingslayer

The PCM TP PID does not work for the LLY so I've been using the PCM TP_A PID. When I load it into the scan tool and try to display the log I don't see the TP_A PID or in the Data tab. I'm also seeing the same issue as with the April 7th release of the data not reading correctly at some frames. I've attached a pic.

Can you send me a *.efi file that has the random data problems?
Send to [email protected]
Thanks
Paul
April 20th, 2008
Blacky

Quote:

Originally Posted by tunedbyGM

Here is a thought , make the default setting be WBO2 for COM1 and COM2 , I can see the need for a selectable WBO2 controller , i,e, Innovate , PLX etc ... , but default the COMs to a on state .:doh:

Yes, they will be defaulted to WBO2 in the "public" release.

There are two COM settings, one for in and one for out. For example, you may be reading COM data from a wideband, but outputting data to a dyno controller. You can do that from FlashScan's single RS232 connector if you make up a custom Y serial cable.

P.S. The dyno data is output on the serial port now. I will publish the data spec soon.

Regards
Paul
April 20th, 2008
Blacky

Quote:

Originally Posted by swingtan

Lennart and lakingslayer, the "weird frames or "logs full of notes" sounds like the problem I'm having as well. I've found that repeated tries at opening the file eventually seems to get a clean read and displays "sane" data. I have no idea if the data is actually correct though.

The way the logs look when they open in "corrupted" form reminds me of the first BBL logs I tried on the E38 when the V2 would cause I/O problems between the ECM and other modules, bringing up dash alerts and dropping corrupted data into the log file. This was back around the start of this year. When opening these files in ScanTool, I'd get the same weir looking data displayed as I get now. It's almost like the BBL files don't have an <EOF> character and ScanTool ends up with random data at the end of the log.

Simon.

There appears to be a bug in the frame count value. The frame count value is written into the file as a 16 bit value ("%d") but should be written as a 32 bit value ("%ld"). That will cause problems if the log file is longer than 65535 frames. A fix is being made now.

If any of you have log files of less than 65535 frames that are showing corrupt frames, please send them to me at [email protected].

Regards
Paul
April 20th, 2008
GMPX

Quote:

Originally Posted by dc_justin

Still seeing the T42 base pressure bug. Screenshots below

Same TCM OS, just a different EFILive release I assume?
April 20th, 2008
swingtan
Quote:

Originally Posted by Blacky

There appears to be a bug in the frame count value. The frame count value is written into the file as a 16 bit value ("%d") but should be written as a 32 bit value ("%ld"). That will cause problems if the log file is longer than 65535 frames. A fix is being made now.

If any of you have log files of less than 65535 frames that are showing corrupt frames, please send them to me at [email protected].

Regards
Paul

I have a few, as I was also finding that opening old log files caused this issue. I just tried opening a log from 24/1/2008 that is 8842 frames long and the first 4 tries resulted in a corrupt display. The fifth try brought up a clean dash page. All I did was to double click the log file and allow ScanTool to open automatically.

I just noticed that data is stored in the "temporary cache" folder when the files are opened. There are 2 files for each opening of the *.efi log file..

Corrupt version:
- efi_cache.0 = 0KB in size
- efi_filter.0 = 0KB in size
OK Version:
- efi_cache.1 = 262KB in size
- efi_filter.1 = 0KB in size
The original logfile is 262KB in size......

Did you still want log examples ?

Simon
April 20th, 2008
dc_justin

Quote:

Originally Posted by GMPX

Same TCM OS, just a different EFILive release I assume?

Yep. The same file was opened in both versions of the software. In fact, every 07 T42 file I've opened has had the same problem.
April 20th, 2008
hymey

Quote:

Originally Posted by swingtan

Hi Paul,

I tried some more BBL-ing this morning and while the recording works well, I still can't read any of the DMA PID's in the log file, when loading into scan tool.

Simon

Any feedback for this blacky?
April 20th, 2008
Blacky

Quote:

Originally Posted by hymey

Any feedback for this blacky?

I'm working on it tonight... (no rest for me).
Paul
April 20th, 2008
GMPX

Quote:

Originally Posted by Lennart

DVT is pretty sweet! Turning on/off is a little weird sometimes as the setting will remain on even when shutting off the feature (e.g. idle speed)

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
April 20th, 2008
swingtan

1 Attachment(s)

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.....
April 20th, 2008
Blacky

Quote:

Originally Posted by hymey

Blacky I am having the same problem as swingtan. When logging all the pids are showing and recording. I load the logged data to my PC once the scan tool opens all the dma pids are missing from the recording. If I try and add them it wont allow it. It states that the pids can only be selected if I clear the logged data.

Other than that, all is going smooth. And it flashes very fast with the new calz files. I also noticed in the VVE that thr rpm increments increase by 200rpm all the way whereas before it would increase by 200rpm then 400 rpm further down the column.

Cheers

Joel

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
April 20th, 2008
Blacky

Quote:

Originally Posted by joecar

Paul,

In scantool build 48, doing Print All (button or menu) causes immediate access violation...

Print single works ok, but it's tedious to generate a report of everything by doing single reports of each tab.

Cheers
Joe

Hi Joe,

I still can't reproduce this problem here.
Can you tell me the settings you have checked in Properties->Printing?
Thanks
Paul
April 21st, 2008
swingtan

Quote:

Originally Posted by Blacky

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.
April 21st, 2008
joecar

1 Attachment(s)

Quote:

Originally Posted by Blacky

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...
April 21st, 2008
Lennart

Quote:

Originally Posted by GMPX

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.
April 21st, 2008
JoshH

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?
April 21st, 2008
Blacky

Quote:

Originally Posted by swingtan

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
April 21st, 2008
Blacky

Quote:

Originally Posted by JoshH

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
April 21st, 2008
swingtan

Quote:

Originally Posted by Blacky

What is the operating system of the ECM that you are logging?
Regards
Paul

Hi Paul,

OS is 12607218.
April 21st, 2008
JoshH

Thanks Paul. That did it. I knew it was something stupid I was doing wrong.
April 21st, 2008
GMPX

Quote:

Originally Posted by Lennart

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 :music_whistling_1:
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
April 21st, 2008
swingtan

Quote:

Originally Posted by GMPX

Wow this thread is a mess to follow :music_whistling_1:

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.
April 21st, 2008
POLARIS_600cc

Quote:

Originally Posted by GMPX

Wow this thread is a mess to follow :music_whistling_1:
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

Just thought I would let you know I was playing around with the DVT controls and there was no delay for me. Also I was messing with idle speed and vnt position at the same time and both worked. I did not try idle speed and rail pressure changes together. I also was not logging any of this. My truck is an 06 LBZ

EDIT: I also just noticed I have @hotmail.com in my username, since your an admin could you pm me with info on how to take that out, or feel free to just do it. Thanks.
April 21st, 2008
mr.prick

when will we have the ability to select
how logged data is applied with RTACS,
other than multiply? :cussing:
http://forum.efilive.com/showpost.ph...68&postcount=1
sorry to nag at this topic again.:grin:

FWIW
i`ve had no problems since this last update.:w00t:
April 21st, 2008
GMPX

Quote:

Originally Posted by POLARIS_600cc

Just thought I would let you know I was playing around with the DVT controls and there was no delay for me. Also I was messing with idle speed and vnt position at the same time and both worked. I did not try idle speed and rail pressure changes together. I also was not logging any of this. My truck is an 06 LBZ

EDIT: I also just noticed I have @hotmail.com in my username, since your an admin could you pm me with info on how to take that out, or feel free to just do it. Thanks.

Thanks for the feedback, I removed the @hotmail from your name, you might need to clear the cookie to log back in, see how you go.

Cheers,
Ross
April 21st, 2008
GMPX

Quote:

Originally Posted by swingtan

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.

Trust me, I'd be happy to play with vBulletin admin all day, stress free work sounds good. But you are right, things are probably getting missed.

Cheers,
Ross
April 21st, 2008
swingtan

Quote:

Originally Posted by Blacky

What is the operating system of the ECM that you are logging?
Regards
Paul

Paul, RE: the AFR reading being off. Forget this one as I just realised what I did. I think I selected an E40 controller instead of E38.......... Funny that it seemed to work so well actually.

Sorry for the side track......

Simon
April 21st, 2008
Black02SS

Quote:

Originally Posted by Black02SS

Was able to test Serial for LM-1 and LOVE it. Can't wait for the FJO to be supported. It is simply awsome. Only issue I saw was the values actually went past 20.9 on decel up to 120:1.1 AFR. Made the BEN show 6.0. LOL

Quote:

Originally Posted by hymey

Make sure you turn DFCO off when logging bens.

I understand that but the values should have a min and max limits that Live shows. ie. 0.0-20.9
April 21st, 2008
Blacky

Quote:

Originally Posted by mr.prick

when will we have the ability to select
how logged data is applied with RTACS,
other than multiply? :cussing:
http://forum.efilive.com/showpost.ph...68&postcount=1
sorry to nag at this topic again.:grin:

FWIW
i`ve had no problems since this last update.:w00t:

It is implemented in the current beta software.
Quote from the release notes: EFILive beta V7.5.4 (Build 44)

Quote:

RTACS now supports Addition, subtraction, multiplication and division as well as the current BEN factor percentage adjustment. Just add the operator (+, -, * or /) you wish to use followed by a comma before the first PID name in the *.RRR key like this: Bxxxx.RRR=+,<pidname> Leave it blank to use the standard BEN factor %.

Regards
Paul
April 21st, 2008
Blacky

Quote:

Originally Posted by Black02SS

I understand that but the values should have a min and max limits that Live shows. ie. 0.0-20.9

Hmmm, the max should be 25.00AFR (1.701 lambda). I will check why it is going above that value.

Regards
Paul
April 22nd, 2008
Lennart

Quote:

Originally Posted by GMPX

Wow this thread is a mess to follow :music_whistling_1:
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 tried that already....logging or not does not make a difference. Just logged it for you to see :-)
April 22nd, 2008
ringram

Had an issue where a log file was corrupt and only 2kb in size. It should have been around 8-9Mb.

Other than that all is well. It would be good if you could indicate a default pid selection in the .ini file so you didnt have to manually select it each time. Kind of go straight to record..

Show 40 post(s) from this thread on one page

All times are GMT -12. The time now is 10:55 PM.