What's wrong with BBL to cause this?

[gmh308]

Ran up some logs today, but they seem all corrupted.

The attached log is all over the place...rpm's at 10,000 plus, airflows of 4g/cyl, inj PW's of 207ms.

Export to CSV and the time stamps are all over the place and the PID values are all over the place too, the readout on the V2 is normal when logging, but this is what comes up on the [normally fantastic and without peer] scan tool.



Anyone have any ideas? Known issue that I missed?

:(

[joecar]

Hi Ian,

What V7/V8 build versions do you have installed...?
What V2 firmware...?

[gmh308]

Hey Joe, its been working fine in the past, Scan is 7.5.6/139, and V2 is Boot 2.6.2 & 2.6.16.

Cheers Ian

[swingtan]

try these....

http://forum.efilive.com/showthread....g-reading-prob

http://forum.efilive.com/showthread....-Full-Of-Notes

http://forum.efilive.com/showthread....g-file-problem

[Blacky]

Ran up some logs today, but they seem all corrupted.

Anyone have any ideas? Known issue that I missed?

:(

Can you send that *.efi file to me at paul@efilive.com, thanks
Paul

[gmh308]

try these....

http://forum.efilive.com/showthread....g-reading-prob

http://forum.efilive.com/showthread....-Full-Of-Notes

http://forum.efilive.com/showthread....g-file-problem

Thanks Simon. Looked through those and went in search of errant other programs. In the end, the Windows 7 PC had done over 900 hours of uptime with at least a hundred hibernates. Probably 200.

So I shut everything down and did a restart. No change. Still displays bad.

Can you send that *.efi file to me at paul@efilive.com, thanks
Paul

I did however try the same log on a a Vista PC, and it works fine. Have emailed the log Paul. Am sure it will be fine, though a number of parameters are missing from the screen view selection, as well as the file export function, that were being logged on the V2...i.e. g/cyl.

Thanks kindly, Ian

[swingtan]

Well, thinking some more on this.

I used to get this all the time under W-XP. Now under W7, I've never had this problem even when I've tried to replicate it. I don't think it's the OS change that has directly fixed this though, as I had one other rather bad issues under XP.

My user profile had gone rouge, seriously large actually. My profile under Xp was 14MB in size where is should have been more like 3MB. I think this is where things really went bad. I had a few other issues and all were resolved with the OS change ( which of course resulted in the new profile ). So maybe try creating a new user with a fresh profile and see if the problem remains or goes.

Simon

[gmh308]

Well, thinking some more on this.

I used to get this all the time under W-XP. Now under W7, I've never had this problem even when I've tried to replicate it. I don't think it's the OS change that has directly fixed this though, as I had one other rather bad issues under XP.

My user profile had gone rouge, seriously large actually. My profile under Xp was 14MB in size where is should have been more like 3MB. I think this is where things really went bad. I had a few other issues and all were resolved with the OS change ( which of course resulted in the new profile ). So maybe try creating a new user with a fresh profile and see if the problem remains or goes.

Simon

Thanks Simon, tried a new W7 user. Same result. Scan seems to munch the log.

[swingtan]

Post the log, I'll rip it open in my "log-tool" perl script and have a look. If it's really the log it's self, then we should be able to see what is going on and may even be able to recover some of the data.

Simon

[gmh308]

Post the log, I'll rip it open in my "log-tool" perl script and have a look. If it's really the log it's self, then we should be able to see what is going on and may even be able to recover some of the data.

Simon

Thanks Simon. Here it is. Am sure it will check out fine and the issue comes down to something else wierd.

E38_0076.zip