BB Logging beta update: March 26, 2008

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.