2011 Running a little rich

I understand that. But the sensor controller still receives a signal, no matter what the ratio is at the sensor. So does it just peg and only read to that limit or does it give a error or what? The Denso sensors/ecu I've used reads down to 7.2 AFR, but it's basically a garbage number anywhere outside of 14.7+/- 1. It may be a moot point in regards to this discussion, but somehow that app is showing a number outside the range of 11.3ish

 

the truck reports back AFR figures in lambda, 1.00 being stoich. You can setup various programs with a different stoich number, E85's stoich is ~ 9.8:1. So if the program is set to E85 fuel, and the truck is reporting 1.00, you will see 9.8 AFR commanded (9.8 x 1.0) If regular gas is used, stoich is 14.7, so set the program to that and the afr figure will change to that, lambda staying the same.

 

Nd4 is just confusing me now. Hahaha. I think I'll just buy a scan gauge or something similar to get some fuel reports and settle this once and for all.

I've been a bit busy, but tomorrow I will hook up the ODB2 again and get the live data fuel trim info to you guys....

 

Me too. He didn't answer my question, though I am not the best at conveying my thoughts clearly. The answer probably would be of little help to you, so I just dropped it. The main point that I think he was trying to make was to be sure that the torque app is configured to display AFR for gasoline and not for ethanol, E85, diesel, etc.

 

Forget about trying to read 02 sensor signals. They fluctuate rapidly and often don't have a discernable pattern when just looking a a data pid.

You want short/long term fuel trims. they will provide a more stable indication of which direction the fuel system is going (or attempting to go)

 

100% LT is all that matters.