BB Logging Update Dec 14, 2007

[Cougar281]

Firmware .14 does not act any different than .13 on the LLY.
Maybe there is something I am doing wrong....
I go to F1 "Select Vehicle", select LLY Manual, select F1 or F2 to record or display data.
After selecting either one a screen comes up with a timer in the top row.
Below is a row called frames which is at 0.
Then there are a number of PIDs, more than in the options.ini file like AD1, AD2, Temp1, Temp2
Not sure if they belong there.

Same here, although I didn't notice the different PIDs.

[lakingslayer]

Firmware .14 does not act any different than .13 on the LLY.
Maybe there is something I am doing wrong....
I go to F1 "Select Vehicle", select LLY Manual, select F1 or F2 to record or display data.
After selecting either one a screen comes up with a timer in the top row.
Below is a row called frames which is at 0.
Then there are a number of PIDs, more than in the options.ini file like AD1, AD2, Temp1, Temp2
Not sure if they belong there.

FWIW mine works with those PIDS even though they don't do anything.

[lakingslayer]

My V2 is not booting up correctly with either V2.05.13 or V2.05.14. With the V2.05.14 I've noticed that the V2 boots up for a split second like said before and then the LED's do a very dim rapid flashing. When I first opened up E-Explorer it says the V2 isn't there. I select the Flashscan button at the bottom right of the tool and it gets the V2 main screen to display but says it still isn't connected. I select the Flashscan button on the E-Explorer tool again and it connects to the V2.

Now after I went through that exercise 3 times the Tool will recognize the flashscan but the screen still stays in the blank mode when connecting to the E-Explorer. It takes one press of either the refresh or properties keys in E-Explorer to wake up the Flashscan unit but if left idle it will go back to the blank screen state with the dim flashing LED's.

One other thing to watch out for is when formatting the SD cards and the V2 goes into this mode. I let mine sit there for a while and when I rebooted the V2 with E-Explorer I tried to use the V2 to read the SD card size but couldn't. Of course the blue LED that was on while formatting was still on. I shut down the V2 and powered it back up and the SD card was empty and formatted.

[Blacky]

Firmware .14 does not act any different than .13 on the LLY.
Maybe there is something I am doing wrong....
I go to F1 "Select Vehicle", select LLY Manual, select F1 or F2 to record or display data.
After selecting either one a screen comes up with a timer in the top row.
Below is a row called frames which is at 0.
Then there are a number of PIDs, more than in the options.ini file like AD1, AD2, Temp1, Temp2
Not sure if they belong there.

You're doing everything correctly. The displayed PIDs will always include the 8 external PIDs (4x5V voltages, 2x12V Switches and 2x Thermocouple temperatures).

I'm still working on the cause of the problem...

Regards
Paul

[Blacky]

One other thing to watch out for is when formatting the SD cards and the V2 goes into this mode. I let mine sit there for a while and when I rebooted the V2 with E-Explorer I tried to use the V2 to read the SD card size but couldn't. Of course the blue LED that was on while formatting was still on. I shut down the V2 and powered it back up and the SD card was empty and formatted.

Good catch.
I'll need to make read/write of the SD card rest the low power countdown timer.

Regards
Paul

[dfe1]

BB logged LS1 PCM with .14 firmware and everything seemed to work fine. TOS now appears to read correctly. V2 still powers off a few seconds after it's plugged in, even after I deleted the settings file and redid the settings with the V2 keyboard. Holfgin down "OK" button for approximately a second brings it back to life and it stays alive.

[Wasted Income]

Mine is doing the exact same as others (powering down with rapid, VERY dim LEDs) but I've also noticed that I can no longer change my splash screen via EFI Explorer. I will try to BBL my LLY on the way to work tomorrow.

[Blacky]

I have found and fixed the power down issue. The "time to low power" was not being initialized at startup. Actually due to a typo in the code almost all of the settings were not being initialized correctly.

Regards
Paul

[lakingslayer]

Damned computers still let us do typo's

[Chalky]

I am kind of glad you guys are working out the kinks during my winter hibernation. BBL should be a work of art by the time the snow clears and I am back on the road.