CORV3TT3

Very weird...

Flashed an updated calibration to one of the banks. I was working on AE- didn't change anything else. Closed it out and rotated the key to lock. Car had been running just fine 15 minutes before and was still warm.

Well, I started it up and with the laptop open and the WUD up, the BLM showed 144.

I data logged it... the car seemed to run rather rich for itself (around 11 for AFR... 13.4- 13.8 is what I would have expected and would have been the cAFR)

No, it wasn't in closed loop. I drove it for a bit, perhaps a 1/2 mile and it went to 128 (went into closed loop) and then in OL DE it jumped back to 144.

No codes... nothing. Good voltage. Good fuel pressure. Just really weird.

I shut it off and restarted the car. BLM went back to 128.

I'm stumped. This is the second time I've seen this in about two weeks or so. Really stumped here.




FWIW- I dreaded sending RBob an email with the datalog because I hate to bother anyone with emails and questions. Was hoping to hear something like "yeah, that's happened to me. I did such and such and that solved the problem", "yeah, that's what happens if you don't rotate the banks", or "that happened to me when I shut it down too fast after a flash" or something...

I'm out of ideas.

EDIT: The high BLM was only present when the Closed Loop Indicator was 0. Seemed like everything was ok when CL was 1 or 2. In all of what I know... my understanding has been that 128 is supposed to be the starting point for BLM and INT values. I really have no clue why or how it would read 144 intermittently when it closed loop wasn't active.

RBob

iTrader: (1)

The CL value is which BLM cell is in use, 0 for idle, 1 for cruise, and 2 for decel.

The three BLM cells are held in nonvolatile RAM (battery backed), at key-on they are checked against these two values:

BLM - Max/Min BLM at Key-on (init)

And brought to the limit if greater or less then it. Your log starts after the engine has been running for a bit with the BLM showing 144 at idle. So can't see when this occurred. And the BIN is PromID 38 with the log showing PromID 39.

Check the BIN with the PromID of 39, the above table.

RBob.

CORV3TT3

Thanks for the explanation on the cells... whenever we chat, I always learn so much!




Alright... I just checked that table... it is 128/128 on BINs with an ID of 39 and 38.

I also checked the last few BINs that I have used/built off. All show 128/128.


Not sure how the PROM ID and BIN don't match... I am sure its user error though.

Dominic Sorresso

Whenever I put in a new bin, I pull the BATT and start fresh w BLMs.

CORV3TT3

That makes sense.

The BLMs seem like they were carrying over from somewhere but not in the BIN itself.

lakeffect2

For the rest of else, Please explain why you pull the battery and it's advantage in doing so.

CORV3TT3

Ensures the BLM memory would be wiped clean- you do the same to wipe OBD-I codes.