BB Logging beta update: May 12, 2008

IMPORTANT
IF YOU HAVE NOT ALREADY DONE SO,
YOU MUST UPDATE FLASHSCAN'S BOOT BLOCK TO V2.05.08(0426)
BEFORE
YOU ATTEMPT TO UPGRADE THE FIRMWARE TO V2.05.16 OR LATER.

Under no circumstances should you attempt to use boot block V2.05.06 (released March 26, 2008).
See this link for more info on what is wrong with V2.05.06
http://forum.efilive.com/showthread.php?t=7804

Download here: http://download2.efilive.com/Softwar...ay_12_2008.zip (19Mb)
This download includes and supersedes all previous BBL beta downloads.

The Readme_First.pdf file included in the zip file has been updated. Please read the first page about new folder names and locations.

The FlashScan AutoCal V2.5 Release Notes _beta_.pdf file has some important "Known Issues" documented for EFILive_Explorer.exe. Please read them.

The FlashScan AutoCal V2.5 Quick Reference _beta_.pdf file has been updated with a couple of new menu options and a new hotkey.

Make sure you update your FlashScan (and/or AutoCal) firmware and boot block using the latest *.ffw files from the \Program Files\EFILive\V8\Firmware folder.

For those of you waiting for the AutoCal beta test units, they should ship this week.

Regards
Paul

Hi guys,

I have one small bug for this release.

In the ScanTool, under PIDs, there is a new "system" option called "Coditions" that holds the GM.EOPS PID. I know it's getting a bit picky and there is probably some more exciting work to do, but thought I'd let you know anyway.

Simon.

Quote:

---

Originally Posted by swingtan

Hi guys,

I have one small bug for this release.

In the ScanTool, under PIDs, there is a new "system" option called "Coditions" that holds the GM.EOPS PID. I know it's getting a bit picky and there is probably some more exciting work to do, but thought I'd let you know anyway.

Simon.

---

Please continue to be picky, these things need to be fixed and with my spelling/typing skills I need all the help I can get. :good:

Regards
Paul

we had just been discussing the transmission description in the scan tool that says LB7/LLY transmission and LBZ/LMM transmission. This description is slightly inaccurate, in that there are certain circumstances in which those descriptions don't apply to the transmission one would desire to log.

Off the top of my head.
1. Vortec 8.1L gas engines in Silverados had Allison 5 speeds.
2. '06 LLY's were equipped with an Allison 6 speed.

Just a suggestion, maybe change the description to Allison 5 speed and Allison 6 speed instead of the aforementioned misleading descriptions.

Umm, yes good idea. :doh:
Paul

Quote:

---

Originally Posted by bballer182

we had just been discussing the transmission description in the scan tool that says LB7/LLY transmission and LBZ/LMM transmission. This description is slightly inaccurate, in that there are certain circumstances in which those descriptions don't apply to the transmission one would desire to log.

Off the top of my head.
1. Vortec 8.1L gas engines in Silverados had Allison 5 speeds.
2. '06 LLY's were equipped with an Allison 6 speed.

Just a suggestion, maybe change the description to Allison 5 speed and Allison 6 speed instead of the aforementioned misleading descriptions.

---

ok not sure what the go is here but this is the problem i have just found. In my options.ini file i am logging KR under the LS1. On the V2 it displays KR and registers if there is any knock but if i record the data onto the sd card then view the log on the laptop it says the KR is not selected in the PID selection and hasn't logged it.

Quote:

---

Originally Posted by SV8346

ok not sure what the go is here but this is the problem i have just found. In my options.ini file i am logging KR under the LS1. On the V2 it displays KR and registers if there is any knock but if i record the data onto the sd card then view the log on the laptop it says the KR is not selected in the PID selection and hasn't logged it.

---

It should be fine, can you send me the *.tun file please, and I'll see what's wrong ([email protected]). Include a link to this post.

Regards
Paul

sent

How do you get rid of unsupported pids for BBL I have one for my LMM I don't recall what it is but if it is important I will get it here to post. It has had this same unsupported pid since the first release of BBL.

Paul,

When I do retrieve Mode $06 or Mode $06 (all), V2 says "Mode $06 Data Not Retrieved".

Is Mode $06 only the failed monitors, and is Mode $06 (all) all the monitors...?

When I save all diagnostics to file it doesn't save Mode $06 data (see attached).

The pids mentioned in my Options.ini seem to log correctly (attached also); the scantool says [Manual] even tho I logged LS1B_A.

Cheers,
Joe