ben73

I have looked around for a definate answer on this one but have found contradicting info...
My understanding is that the 2nd VE table is added to the main VE table. Is that correct?
This makes it difficult to tune properly with the BLM's and correction factors collected from winALDL, so I zeroed out the 2nd table from 400-3200rpm and added their respective values to the 400-3200 rpm rows in the main VE table. Am I correct in thinking that it is ok to do this?
If the only purpose of the 2nd table is to be added to the 1st, it shouldn't make a difference right??
Anybody know this for sure?
Thanks,
Ben.

Low C1500

Your right about the second table just being added to the first. They used an adder table to save space (its just a 2D table), if they didn't do this they would need a big main table (which is 3D) to get up to 6225 rpm.

Any way, add all the numbers from 400 - 2800 rpm, then just zero them out in the adder table, make sure not to zero the 0 rpm cell, and don't add the 3200 rpm adder cell, to the main one, then just leave the adder with the old values from 3200 and up.


If you think about a while you'll see why you don't add the 3200 over.

ben73

Thanks for your reply. I have thought about it for a while and cannot see why you wouldn't zero out the 3200 cell in VE2, wanna enlighten me??
Also, the values in VE2 from 3600 and above, are they applied at those RPM's regardless of MAP value??
Thanks,
Ben.

Low C1500

The adder table from 3200 and higher is added to the main table 3200 rpm row. So if you add the 3200 rpm adder cell you'l have almost 100% VE, then the ecm will try to add 3600rpm adder cell to the main table 3200 cell. Ends up having nothnig but 100% VE above 3200rpm.

So for all values above 3200, the ecm just adds the adder cell for that rpm to all the main table map values.

kevm14

Above 3200rpm, the VE takes the shape of 3200rpm's MAP values, plus the adder. It works ok because it's high rpm, apparently.

Ronny

iTrader: (1)

i was just about to zero out table 2 when i came across this thread. the 3200 rpms table 2 comment is what confuses me. i could not get 20 map 3200 leaner in table 1. I was at zero there. so i took from table 2, at 3200, from 34.8 down to 32.8 to lean out 20map at 3200 in table 1.

was that a mistake?

now as i read it i dont zero out table 2 at 3200. reason being it is added to table 1. OK but that is true for 2800 as well. now at 3600 rpms is apparently where the issue is! in my case that adder is 38.3. are you saying that if i have 3200 at 32.8(table1) plus the 38.8(table2) i would have a total of 71.6 at 20 map at 3600 rpms. which is what i believe is true. if i set 3200 at table 1 at 71.6 then at 3600 rpms the adder is another 38.3 putting me way up to 109.90. is this final example the issue with zeroing out 3200 at table 2 ? maybe i understand but need a confidence builder.

Grumpy

VE drops after a point in the RPM range.
If you 0 out the VEII table then you lose the ability to drop the VE at higher RPM.

It would be a big advantage if folks could data log PW with the TBIs to see what effects these changes make.

Low C1500

I think you got it ronny, the ecm would just give you 100% VE at higher than 3200, most motors would still run ok cause most people have weak injectors, so they can't srpay in enough fuel as the ECM is calling for

Ronny

iTrader: (1)

thanks i will not zero out 3200. now please explain why the 400rpm is not zeroed out in table 2?

Ronny

iTrader: (1)

i misspoke i meant the 0 rpm cell !!

Dewey316

it is not zero'd out because there is no value in VE%1 for the 0 rpm cell.