Power Enrichment OBDI

[LZeppelin513]

BTW thanks for taking the time to explain this stuff for me.

[robertisaar]

So a bit over a half sec to go from no pedal to full. That's somewhat fast, yet on average DTPS will be somewhere between the very first two data points on the graph. Even if you hit full pedal twice that fast (which is probably close to as fast as someone will be slamming the pedal down) it will still be looking up values before the third data pt on the graph.

That just seems crazy to me that there would be such poor resolution for usable DTPS values in the table and then have the majority of the graph be basically useless.

that's just what GM does..... they do oddball crap that makes no sense at times. they have both alpha-n and speed-density idle, but either can kick in at seemingly random times. they make a VE main + adder setup that takes up more space in the algorithm to setup for than what they save in calibration room compared to just running a single full sized table. a BPC based airflow/fuel flow calculation instead of a real injector flowrate/cylinder size/VE setup.... all kinds of stuff like this that doesn't quite make sense... sometimes, i wonder how much time it would take to literally start the entire algorithm over and use none of the GM code compared to how much time i put into patching around the stupid things.... things like this are time killers.

BTW thanks for taking the time to explain this stuff for me.

no problem, you're just giving me more reasons to fix the half-assed methods GM came up with.

[LZeppelin513]

I have switched back to nast1(loving it) from $A1. I am still having some issues with AE but its getting closer.

The main issue is that I go rich when I go WOT for the cells where AE and PE overlap. One problem is that AE lingers much longer that I want. For example, the last WOT run I recorded, AE continued for 5 cells after 100 percent TPS was reached (ie too long after no more D-TPS). I want it to stop when it should, in my case 12.5 ms after D-TPS drops bellow 1.18%, instead of over 500 ms.

[robertisaar]

F104 may be your answer...

based on what i've read via TGO, that table is used to filter TPS position in use with AE... i'm not entirely certain on how it works, but i haven't looked at it in a while. i guess it's used to filter out the "need for AE fueling" accumulation word, but i could be wrong.

[LZeppelin513]

OK thanks I'll try and play with it. If you had to guess, in my case should i be decreasing or increasing it.

[robertisaar]

based on the value size, i would say that increasing it would take it out faster?

i'll have to look at the code to see what it actually does though.