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

[joecar]

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

[Blacky]

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

Still not implemented. :(

[swingtan]

Excellent work! I'm now trying to get my head around the "Dynamic" section in the E38 Fuel group. It's early days yet but the excitement is growing.

It did prompt me to remember something that I worked out way back in January and may have forgotten to pass on.

In the PE tables, B0156 provides a TPS% level to enable PE. I found that measured TPS% was vastly different to the PE% displayed in the table. I had all sorts of troubles trying to work it out so I started remapping the measured TPS% vs TuneTool TPS%. The results showed that there was a logarithmic offset between the 2 values, as shown in the attached image.

While there are differing thoughts on weather PE should be controlled by TPS%, MAP or both, there is a question as to what other TPS% settings may be effected by this offset?

Simon.

[joecar]

Still not implemented. :(

Paul,

That's ok, take your time... I was going by the quick reference guide...

I'm having some cat codes so I am playing around with mode 6.

Cheers
Joe

[swingtan]

I did a couple of logs this afternoon. Replaying them in ScanTool has dropped a couple of the PIDs off. They exist in the log file but do not display. I copied the previous options.ini file back into the config filesystem as I didn't see any info in the readme to say there were changes and it was fine before.

The following PIDs no longer show up in the ScanTool...

• ECM, INVLVTMP_M
• ECM, OCTSCL_M
• ECM, AFRATIO_M

Sample log file is attached.

[hymey]

Has anyone tried pass thru logging yet?

[Blacky]

I did a couple of logs this afternoon. Replaying them in ScanTool has dropped a couple of the PIDs off. They exist in the log file but do not display. I copied the previous options.ini file back into the config filesystem as I didn't see any info in the readme to say there were changes and it was fine before.

The following PIDs no longer show up in the ScanTool...

• ECM, INVLVTMP_M
• ECM, OCTSCL_M
• ECM, AFRATIO_M

Sample log file is attached.

Is it possible you've exceeded the channel count?
24 for VPW, 42 for CAN?

Regards
Paul