BB Logging beta update: March 26, 2008

[joecar]

Looking closer at my log in post #26, the timestamps are all incorrect.

[joecar]

I get the exact same results while logging as 99+ LS1 Manual. It said my car revved to 11900rpm. Hahaha. Something is definitely wrong.

Paul- What else do you need from us to help you troubleshoot?

That's what I see when viewing the log file using the scantool...

but when I was recording the log, V2 showed correct values (they showed that my car was at warm idle).

[Kevin Doe]

I had a similar issue with seemingly corrupt files. I noticed that my corrupt files corresponded to the blue LED not flashig while logging data.

I reformatted my SD card and the issue seems to have went away. For the root cause, I have no idea.

[joecar]

Ok, I'm reformatting as I read write this...

Edit: reformatting via the V2 commands, right...?

[ChipsByAl]

Right. Did it work Joe?

Al

[Blacky]

Another question:

Using V2 only, how do I view a log file...?

I did this:
- F2 scan tool
- F1 Data logging
- F2 Display data

and it says "No PIDs selected".

You can't play back a log on FlashScan.
In future it will be available.

The "Display" option just displays real-time PID values without creating or writing to a a log file.

Regards
Paul

[Blacky]

The corrupt log files is due to a mismatch in the PID definitions of the wide band O2 status PIDs: WO2ST1 and WO2ST2. They are defined as 16 bit values in the PC scan tool and only 8 bit vales in the FlashScan *.pmm files. That causes the PC Scan Tool to read frames 2 bytes too long from the log files which means after the first frame, the data turns to junk (or FlashScan is writing frames 2 bytes too short - depends on your point of view).

I haven't tried yet, but I'm pretty sure if you remove both of those PIDs form the Options.ini file PID list(s), the problem will go away.

I will fix it in the next update.

Regards
Paul

[Treurentner]

Hi Paul,

maybe I have the same problem.
I did a clean install (on a new PC) of V 7.5 and unzipped the latest BB update over the existing files. The previously logged BB files seem corrupted while viewing with EFI live scantool (V7.5.4 build 46), but on the old (not updated) Laptop installation everything is displayed ok.

Regards

Marco

[oztracktuning]

If i try to use this latest update March 26th to look at BB logs captured with the Mar 20th edition they are all garbled on the screen for some reason??

[joecar]

I deleted WO2ST1 and WO2ST2 from Options.ini, I re-logged, and now the scantool correctly displays the log (see attached)...

Altho the scantool shows [Manual].

Also, in Options.ini I replaced AFR with EQIVRATIO, and during logging V2 shows EQIVRATIO units as "V";
it's units should be "EQ" or nothing.... can I change this...?