BB Logging beta update: May 19, 2008

[Blacky]

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_19_2008.zip (20Mb)
This download includes and supersedes all previous BBL beta downloads.

ALL *.pmm files have been updated. you MUST delete ALL *.pmm files from FlashScan (before upgrading the firmware) and from the folder: \Program Files\EFILive\V8\config (before unzipping the downloaded zip file). Failure to do so will cause unpredictable results when you restart FlashScan after updating the firmware to 2.05.17(0519).

The Readme_First.pdf file included in the zip file has not been updated, except to update version numbers.

The FlashScan AutoCal V2.5 Release Notes _beta_.pdf file has some important "Known Issues" asnd updates. Please read them.

The FlashScan AutoCal V2.5 Quick Reference _beta_.pdf file has not been updated.

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

Regards
Paul

[Lennart]

Not sure if this has been posted before, but even though I flashed the latest bootloader 2.05.08(0426) the Explorer and V2 show a date of Apr. 25, 2008.

[Blacky]

You also need to update FlashScan with the latest firmware file: FSProgV2.05.17(0519).efw (from the Firmware folder).

Regards
Paul

[Lennart]

You also need to update FlashScan with the latest firmware file: FSProgV2.05.17(0519).efw (from the Firmware folder).

Regards
Paul

Did that.

[joecar]

Not sure if this has been posted before, but even though I flashed the latest bootloader 2.05.08(0426) the Explorer and V2 show a date of Apr. 25, 2008.

I see the same thing... I think that's ok.

[Blacky]

Not sure if this has been posted before, but even though I flashed the latest bootloader 2.05.08(0426) the Explorer and V2 show a date of Apr. 25, 2008.

Oh, you mean the date of the boot loader still shows as Apr 25. I thought you meant the date of the firmware.

Hmm, looks like I've got a mismatch between the filename (0426) and the date 25 Apr, 2008. What you are seeing is ok, I'll fix the date in the file name next release.

Regards
Paul

[swingtan]

OK, I've found the issue.

It seems the PID names have changed in the latest firmware but don't get translated back to the correct PID in ScanTool. Here's a quick breakdown of the 3 PIDs I noticed.

PID Names for FW Versions

FW-(0512)        FW-(0519)

E38.INVLVTMP_M   GM.INVLVTMP_M
E38.APCYL_M      GM.APCYL_M
E38.AFRATIO_M    GM.AFRATIO_M

Using the previous trick of editing the log file and changing the "GM" to "E38" returns the data in ScanTool.

regards,

Simon

[swingtan]

Hi Guys,

I've performed 2 logs today that are over 50,000 frames long. Both load in ScanTool after fixing the PIDs and both are truncated at 50,000 frames. The scroll bar allows you to scroll past the end of the data in ScanTool, but the lines just stop at the 50,000 frame mark. The Metadata indicates that there are a lot more than 50,000 frames....

FRAMECOUNT=00092371
FRAMECOUNT=00057076

I've attached a screen shot to show the screen.

By the way, is there any chance we can get the "Auto Replot" limit raised? It seems to have an internal limit of 30,000.

Simon.

[Blacky]

You can raise the 50,000 frame limit in the Properties window on the Logging tab page.
I'll change the auto re-plot to be x1000 (the same as the frame limit in the Logging tab page). i.e. that will turn the 30,000 limit into 30,000,000.

Regards
Paul

Hi Guys,

I've performed 2 logs today that are over 50,000 frames long. Both load in ScanTool after fixing the PIDs and both are truncated at 50,000 frames. The scroll bar allows you to scroll past the end of the data in ScanTool, but the lines just stop at the 50,000 frame mark. The Metadata indicates that there are a lot more than 50,000 frames....

FRAMECOUNT=00092371
FRAMECOUNT=00057076

I've attached a screen shot to show the screen.

By the way, is there any chance we can get the "Auto Replot" limit raised? It seems to have an internal limit of 30,000.

Simon.

[joecar]

VPW mode $06 still says "Mode $06 Data Not Retrieved".