This is from a datalog $6E, open loop. I drove for 15 minutes at 70 mph, and the O2 sensor never got above 50mv. I mean every once in a while it would jump to around 400 or so, but for 99.9 percent of the time it stayed inbetween 0 and 50 mv. Do I have a header leak, is my 02 sensor skrew'd.
Or is it not getting hot enough because I have a 1-wire sensor and shorty headers?

 

I dont see anything really wrong with your O2 sensor or tune. You have a high O2 crossover count. If that count keeps growing and resets back to 0, then the O2 sensor is switching from above 450mV to below 450mV,,, thats what the cross counts are. BTW: for an O2 sensor, 450mV is 14.7:1 AFR.

The 137 BLM value means that the ECM has detected a slight lean condition and is adding fuel on top of the normal calculation amount (128 is baseline). You could address this situation by increasing the MAF table that contains t 40 gms/sec by about 7.0%... Of course you should increase the neghboring cell about the same. You should get more data in oder to fix the MAF tables.

Edit: I am also running a one wire O2 sensor and shorty headers.

 

Thanks for the input, i was under the impression that the o2 sensor should be @450 or so. And as for the BLM, it "stays" @137 ALL the time. I just figured that since it was in "open-loop" the BLM was fixed there or something. The chip is set to never go into closed-loop for testing. Thank you for your help.

 

The O2 sensor will bounce around alot. Mine goes from double digits up into the 700 hundreds. That is normal as far as I know. Everytime the O2 value crosses the 450 mV point, the ECM adds one to the cross counts. It is surprising how much the O2 sensor bounces around! One would think that it would settle in somewhere.

Also, if you are running in open loop mode, the BLM will never change.

Now I gotta ask you, why would you conduct testing in open loop? FWIW: I conduct all of my testing and tuning sesions in closed loop. What I am missing?