BB Logging beta update: March 26, 2008

Quote:

---

Originally Posted by 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...?

:cheers:

---

Yes, you can change it by adding an entry to the *PCU section in Options.ini. Use 1.0 for the factor and 0.0 for the offset since the value should be ok, just the units text needs changing.
Then select "Custom" units display in FlashScan. While logging, "Enter" toggles between Cutom and Metric units.

You can do that for any PID. Using the correct values for factor and offset you can change any PID to be displayed in any custom units that you would like.

I have fixed the units for the next release.

Regards
Paul

Paul,

I was reading thru the files LS1B_A_PIDs.txt and LS1B_M_PIDs.txt and
I noticed that SW1 appears twice instead of SW1 and SW2...
I noticed that V2 shows only SW1.

Cheers,
Joe

Quote:

---

Originally Posted by joecar

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

:cheers:

---

In LS1B_M_PIDs.txt and LS1B_A_PIDs.txt 'EQIVRATIO [2] Equivalence Ratio (V)'. Couldn't the (V) be changed to (AFR) or ()? :nixweiss:

Quote:

---

Originally Posted by Ninety8C5

In LS1B_M_PIDs.txt and LS1B_A_PIDs.txt 'EQIVRATIO [2] Equivalence Ratio (V)'. Couldn't the (V) be changed to (AFR) or ()? :nixweiss:

---

See post #41 above.
Regards
Paul

Quote:

---

Originally Posted by Ninety8C5

In LS1B_M_PIDs.txt and LS1B_A_PIDs.txt 'EQIVRATIO [2] Equivalence Ratio (V)'. Couldn't the (V) be changed to (AFR) or ()? :nixweiss:

---

The .txt files appear to me to be after the fact (and they don't get loaded onto the V2 is a giveaway) for documentive/verification purposes.

Quote:

---

Originally Posted by joecar

The .txt files appear to me to be after the fact (and they don't get loaded onto the V2 is a giveaway) for documentive/verification purposes.

---

True, but the text files are generated by the same process that generates the *.pmm files and should contain the exact same data that is in the *.pmm files. So if the units are wrong in the text files then they will be wrong in the *.pmm files.

(Except the previous beta release where there was a bug in the program that generated the text files and some of the units were shown incorrectly in the text file when they were correct in the *.pmm files. There's an exception to every rule.)

Regards
Paul

Quote:

---

Originally Posted by Blacky

True, but the text files are generated by the same process that generates the *.pmm files and should contain the exact same data that is in the *.pmm files.

---

Oh, similar in concept to a compiler/assembler output listing. ;)

Quote:

---

Originally Posted by joecar

Oh, similar in concept to a compiler/assembler output listing. ;)

---

Yes.

Quote:

---

Originally Posted by Blacky

It is a lot more stable than the early releases, I recommend holding off until we figure out the last few niggly problems. Should be about 2 weeks.

Regards
Paul

---

Does this mean that we can't/shouldn't try the serial wideband stuff until the next update if we're using it for production work?????

Paul, could I test the BBL/serial WB firmware on my spare V2 and not install it on the V2 with all the STREAMS and just use it for logging???

Right now, my analog inputs 1 & 2 on my main V2 are fried and I currently take both V2s in the car...one for logging and one for flashing.....

Would it be safe to test it on the "logging" V2 so as not to put myself out of business????

I really wanna try this!
Chuck CoW

Chuck, I would still wait.

Paul,

If I haven't already mentioned this:
- on V2 display, SW2 is not mentioned;
- on scantool PIDs tab, TEMP2 is disabled.

Paul, BALRCYL1 is missing from the LLY txt file, and I noticed it didn't appear on the V2 (but 2-8 are there). Just FYI.

If I connect V2 to vehicle with key off, V2 powers on;

then when I turn key on, V2 does not detect any controllers...
how do I get it to detect controllers (other than re-connecting it...?)...?

Otherwise the sequence is to connect V2 to vehicle after key on.

Build 46 scantool seems to only do one level of calc pids in calc_pids.txt...

i.e. it displays only the calc_pids that do not depend on other calc pids.

Is Serial WB Data pass thru working?`

The V2 doesn't reconnect to the Module it was logging when you start the vehicle again; IIRC, one of the earlier releases did. Also, if paused, it won't unpause once it has lost contact with the module.

Quote:

---

Originally Posted by joecar

Build 46 scantool seems to only do one level of calc pids in calc_pids.txt...

i.e. it displays only the calc_pids that do not depend on other calc pids.

---

This is weird... it does this on my PC at work... and on my PC at home it works correctly. :nixweiss:

I forgot to end a log before removing the V2 from the vehicle... so now I can't view that particular log using the scantool, is there a way to "terminate" the log file so it can be viewed...?

Quote:

---

Originally Posted by 9secVette

Absolute Nightmare

---

Profound! Glad you could take the time out of our busy day to offer your input on issues found in the Beta during your testing.

Well so far what I have found is that PIDs for the pass thru are always invalid but this time you can log them and it will transfer data correctly.

The software hangs a lot with "conflicting" drivers (RR+v2) and when the software hangs you simply have to shut down the pc the hard way most of the time because you cannot kill the process... I was using a different laptop today and it was a real pill until I found the drivers it liked, somehow they are different for different computers.

Quote:

---

Originally Posted by Chuck CoW

Would it be safe to test it on the "logging" V2 so as not to put myself out of business????

I really wanna try this!
Chuck CoW

---

Yes try the new firmware on your spare V2, so long as you have at least one V2 left on the current firmware.

Regards
Paul

Quote:

---

Originally Posted by joecar

If I connect V2 to vehicle with key off, V2 powers on;

then when I turn key on, V2 does not detect any controllers...
how do I get it to detect controllers (other than re-connecting it...?)...?

Otherwise the sequence is to connect V2 to vehicle after key on.

---

Hotkey: Ctrl+OK will re-detect protocols and controllers.

Regards
Paul

Lots of comments on this thread have been posted, I am making a list of them and will work though them one by one. I will not answer them directly, unless I need more info. I'll just work on fixing them.

Regards
Paul

Awesome as always.... thank you paul!

Just something with Blackbox logging with the V2 and the latest beta firmware on my twin turbo LS1.

Did a longish log yesterday. Opened it in the latest V7.5.4 Build 44 and got this:

http://www.splitpixel.com.au/temp/BBL_V75.jpg

tried opening it direct from the SD card, copying from EFILive_Explorer and still the same.

Ive got a copy of V7.5.1 Build 32 and if I open it, it thinks for a couple of seconds (as opposed to V7.5.3 which is instantanious) and then the "This has over 3000 frames, etc..." dialog box and I get this:

http://www.splitpixel.com.au/temp/BBL_V7.jpg

Shame coz I logged some Serial WBO2 stuff I want but I cant see it in V7.5.1 but I will keep it until the next software release ;) Ive done shorter logs and they appear fine.

Jez

Quote:

---

Originally Posted by JezzaB

Just something with logging with the V2 and the latest beta firmware.

Did a longish log yesterday. Opened it in the latest V7.5.4 Build 44 and got this:

http://www.splitpixel.com.au/temp/BBL_V75.jpg

tried opening it direct from the SD card, copying from EFILive_Explorer and still the same.

Ive got a copy of V7.5.1 Build 32 and if I open it, it thinks for a couple of seconds (as opposed to V7.5.3 which is instantanious) and then the "This has over 3000 frames, etc..." dialog box and I get this:

http://www.splitpixel.com.au/temp/BBL_V7.jpg

Shame coz I logged some Serial WBO2 stuff I want but I cant see it in V7.5.1 but I will keep it until the next software release ;) Ive done shorter logs and they appear fine.

Jez

---

DITTO... i forgot to mention this.

Quote:

---

Originally Posted by 9secVette

Absolute Nightmare

---

Hi 9secVette... :wave:
Actually, it's not a nightmare in any sense of that word... :cheers:

This is beta testing... we didn't hose up our PC/V2/PCM, so it's all going rather well... :cheers: ...

We're BB logging data and we can post some meaningful logs if you care to view them (see attached... this log contains enough information to diagnose a failing bank 1 cat).

Of course, you must understand that if you want to beta test, you have to be prepared to expect the worst and to post up any problems/suggestions; if you or your customers depend on zero downtime, then it's best to wait.

Cheers,
Joe
:cheers:

Jez,
Chris,
Shouldn't you be using build 46...?

Jez,
Your first pic looked just like mine... have you tried what post #37 says: showpost.php?p=66308&postcount=37

Edit: oh, do those 2 pids affect how WB is logged...?

(my WB is off my car right now, I'm fixing it's wiring)

Cheers
Joe
:Cheers:

Nope.. Haven't tried that... actually... didn't read that... hm.. anyways... wb is very important.. I'm glad at least I can log WB Serial data now and to make matters worse... my RR DIES :(

It seems that the latest release does not like the SPARKADV PID for the 19980400 OS. It does not show up on the display data, does not show up in the log and when I display the log it is not a valid PID. It is in the Options.ini file and if I pick a 99+ system it is displayed.

Did not read the entire thread but here hare my observations from today (using the March 0326 FW and the latest build) :
- TCM flashing works
- Logging in passthrough works, but selecting the controller was a little odd, had to select with ignition on!
- Clearing DTCs works for all controllers from PC but I was unable to clear B1025 and a Cxxxx DTC standalone.
- BBL did not work, got the message that PID TP was unknown.


Tests were all performed on my 05 LLY Duramax truck.

FRPACT appears to be missing from the LLY PMM file as well... Just FYI.

This is probably old news by now, but I had no problems with either pass-through or bb logging a 99+ LS1 PCM. Things seem to run a little quicker than they used to. I'll try a few other processors and let you know the results.

showthread.php?t=7684

Quote:

---

Originally Posted by joecar

Build 46 scantool seems to only do one level of calc pids in calc_pids.txt...

i.e. it displays only the calc_pids that do not depend on other calc pids.

---

If I open a log file captured prior to BBL update, then on the PIDs tab I see my calc pids from my calc_pids.txt file.

But, If I open a BBL captured log file, I don't see all my calc pids... I see only the ones that do not depend on other calc pids.

Compare the attached calc.pids.txt file to the attached image of PIDs tab sorted by last column...
the PIDs tab is missing the following pids from the calc_pids.txt file:
CALC.AFR
CALC.EQ
CALC.EQ_WB1
CALC.EQ_WB2
CALC.BEN_WB1
CALC.BEN_WB2

and all of the predefined wideband BEN calc pids are missing also.

:doh2:

All the calc pids that show up in the pids tab do not depend on other calc pids...

CALC.AFR_WB1 and CALC.AFR_WB2 showed up (they depend only on EXT.AD1 and EXT.AD2).

The above was with the March 26 update.

So I then did this (in the sequence shown):
1. copied the March 20 update,
2. copied the March 26 update,

Now it seems that all the valid calc pids from calc_pids.txt show up, but I still don't see the invalid calc pids nor the predefined wideband calc pids.

Oh, I saw your post about collating pids.

Quote:

---

Originally Posted by joecar

Oh, I saw your post about collating pids.

---

I think this issue might have a different cause, I've got it on the list of things to investigate... Thanks for the detailed info.
Paul

Paul,

This is weird... it only happens on my laptop... my desktop is perfectly fine...