BB Logging beta update: March 26, 2008

[Blacky]

I've noticed in the last two updates that in the Scan Tool when you go to 'Enter VIN' and want to enter the 'Op system' only a few of the operating system show up when you click the 'down arrow'. I can type in 19980400 but before this all the operating systems were on the list.

My mistake, the list of operating systems is generated by scanning the \Program Files\EFILive\V7.5\Calibration folder (and subfolders) for files ending in *.cal. Since we've updated to using *.calz files it is not finding the supported operating systems.

I'll fix it in the next release.

Regards
Paul

[ChipsByAl]

Thanks Blacky, that will work better than just adding in EXT.WO2AFR1 in the appropriate look up table.
Al

[Kevin Doe]

I made those additions to my sae_generic.txt file, saved the file, retarted my Scan program. I found the new Calc PIDs I made, but they don't show up as supported. How can I make the pid supported? It has an X through the PID.

[Blacky]

I made those additions to my sae_generic.txt file, saved the file, retarted my Scan program. I found the new Calc PIDs I made, but they don't show up as supported. How can I make the pid supported? It has an X through the PID.

I still recommend not changing sae_generic.txt but instead add your own calc PIDs to cal_pids.txt. That way when new updates are released they won't overwrite your changes. Sae_generic.txt is usually overwritten during updates.

Right click on any calculated PID that shows up as not supported and select More info, it should explain why EFILive thinks it is not supported.

Regards
Paul

[Kevin Doe]

I still recommend not changing sae_generic.txt but instead add your own calc PIDs to cal_pids.txt. That way when new updates are released they won't overwrite your changes. Sae_generic.txt is usually overwritten during updates.

Right click on any calculated PID that shows up as not supported and select More info, it should explain why EFILive thinks it is not supported.

Regards
Paul

Ok, I removed the custom PIDs from the sae_generic.txt file, and added them to the location you specified. However now the scan software isn't finding it. None of my pids show up with them in the new calc_PIDs.txt file.

I created the folder User configuration and put the file in there. Any ideas?

EDIT, I just relized that I did not need to create the "User Configuration" folder in teh V7.5 area in the program files, it was already there in the my documents area. Got it figured out, thanks.

[joecar]

While BB logging V2 shows the correct values of the pids;

When I pull copy the log from V2 to my PC and view it using the scantool, it looks like junk (see attached, log of idling in my driveway).

I believe I followed all the steps (and read the readme first).

What did I miss...?

Also: The log file shows [Manual] instead of [Auto]... I selected LS1 99+ Auto.

[Goldfinger911]

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?

[joecar]

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".

[joecar]

Also, you can see in my log in post #26 that there are markers all thru the log...

I didn't place them there (I didn't press the Fn or Ctrl-Fn keys).

[joecar]

Also, viewing the live data logging on V2, AFR had no decimal places.