LT1 $EE Open Loop WBO2 Tuning

[Casey96SS]

Looking at running OLSD permanently. Have the tune pretty close in CLSD. VE tables are as good as they are going to get and PE mode is dialed in. Still having issues with split BLM at idle. Plus the car seems a little more crisp and consistent on open loop.

Do I still use the VE tables to adjust the fueling for open loop? Does the Open Loop AFR target table come into play at all?

Lastly, I can get trimalyzer to show my WBO2 readings vs MAP and RPM. Would I just use this data to adjust the VE tables point by point manually or is there a more automated way like when using the fuel trims?

Thanks for any input!

[LeMarky Dissod]

Every LT1 intake manifold contains a 2nd much smaller intake manifold that is throttled EXCLUSIVELY by the IAC motor.
Unless all of 'IAC intake manifold' runners are very clean, there'll be some split BLMs, even if you drill the throttle body's IAC hole.

The VE tables do adjust fueling in closed loop and open loop speed density.
Both the Open Loop AFR table and the VE tables use MAP, so they affect each other.
The more accurate the VE tables are - and the more accurate the injector tables are - the better equipped the Open Loop AFR table is.

Someone with more trimalyzer experience can answer your last question.

Don't forget to disable the CAT Protect Enrichment.

[steveo]

when you are tuning open loop with a wideband, the afr target is critical because that's what you're trying to attain to correct your VE table.

if you're tuning with something other than eehack (such as trimalyzer) you'll want to run a single target AFR across the entire table for the temperature range you're tuning in (14:1 or something would be good).

if you are running eehack, it has been designed for open loop wideband tuning with a variable AFR target, although not many people realize that. you need to install the eehack patch set that's in EEX so you have AFR target in the datastream. then the analyzer will check your wideband vs your target and develop a VE correction table based on that.

once your VE table is correct you can play with the AFR target vs MAP and not worry about watching the wideband

[Casey96SS]

Thanks for the input guys! That does help get me pointed in the right direction.

If I understand this correctly, I will be adjusting the VE tables to achieve values listed in the Open Loop AFR Target table? Once that is done, I can adjust the Open Loop AFR target table to adjust the fueling as needed for best performance and drive-ability?

Yes I do have AFR target showing in EEHack. Would I use the analyzer in EEHack or trimalyzer to adjust the VE tables?

Swamped with work this week but hopefully I can play around with this soon. Thanks!

[steveo]

Would I use the analyzer in EEHack or trimalyzer to adjust the VE tables?

explained in my reply above

not really sure why you'd use trimalyzer if you're logging with eehack anyway, the onboard analyzer in eehack is almost as good

[Casey96SS]

explained in my reply above

not really sure why you'd use trimalyzer if you're logging with eehack anyway, the onboard analyzer in eehack is almost as good

Got it. I am assuming there is no way to modify, copy, and paste the values in Tunerpro using the analyzer in EEhack? Didn't see anything. Just wanted to make sure before I calculate the cell by cell changes manually. Thanks again!

[steveo]

you're correct, with eehack you do it manually. it seems like extra work but you'll find after 1 or 2 passes, the corrections that need to be made are only a few cells. if you've already been narrowband tuning your VE table, there really shouldn't be much work to do at all. if you see big changes needing to be made, it might be a red flag.