VE Table Help

[VL400]

The CalcVE term is the Required VE item in my post above. Its what the VE needs to be to make the target equal actual.

RT tuning - get engine on to a load point, check the wideband and if it differs from target AFR you will also see the CalcVE and current VE differ, use the value of CalcVE in your VE table at that load point.
Tuning from logs - setup a histogram that is the same table size as the VE (have a look at the 1 bar ADX, its got one done). Play back a log and it will enter the cal VE items in the table. Look at the number of running samples if you got lots then use the value to modify your current VE table.

In both cases it will still require some smoothing of the table when your done.

[vc81]

Thanks again vl400. When tuning from logs - after playing back a log and the CalcVE items have been entered into the table. Look at the number of running samples if you got lots then use the value to modify your current VE table. What do you mean by - the number of running samples if you got lots ? Does this mean lots of logs?
How do I smooth the table?
Thanks,
vc81

[antus]

in the history table you can pick last sample, average, sample counts (and others). Use sample counts to see how many samples were collected against that cell. Then use average to get a number. if there is only 1 or 2 samples then it probably wont be accurate enough to use. To smooth it, do it by hand. You can adjust one cell, and then view the 3d map and select individual points and move them up and down. You need to apply your logic. If a sample stands out as being wrong, then it probably is wrong. This is where it gets hard, you can not get a smooth and correct table automatically, you will find it just doesnt happen. You need to think about the data you've got, and use it more like a collection of hints to build your own table. Then test again. At least, thats how I do it. I'd be interested if anyone has a better way (without a dyno).

[vc81]

Thanks for your help Antus. Can you please explain what the 2 excel spreadsheets are used for that I posted a few posts back? Are they any use to me? Do they make anything easier?

[antus]

They both do pretty much the same thing. They help you playback logged data and adjust VE tables to suit. But, like all things in IT, garbage in, garbage out. If you dont use it blindly, everything is working correctly and you collect the data with smooth and slow transitions in driving they will help.

Note that they pre-date the calcVE histograms though, but amount to the same thing. What way you do it is up to you.

[vc81]

Ahh Ok. I understand more now. Thanks for your help Antus.

[vc81]

When tuning the VE table in a 12P tune is it a good idea to turn off BLM's, closed loop & lean cruise?

[Holden202T]

depends how your tuning, if your using blms to tune the ve then yeah .... but yeah want to turn off lean cruise at a minimum, and if you are tuning with a wideband probably want to disable closed loop also.

[vc81]

Sorry yea I should have mentioned I'm tuning with a wideband. So what is the best way to disable blm's, closed loop & lean cruise?

[vlad01]

I have a question about VE tables as well. in the case of 2 or 3 bar tunes in boosted applications. How would you tune the 1 bar table(non boost VE table) in certain areas assuming those conditions will never be achieved because of the boost?

In what I have in mind is a centrifugal SC. I would imagine it would be a good idea to sort out the non boost tables first with the SC disconnected and then tune the boost tables and fine adjustments after the SC is reconnected.

My thought is, if the SC internal belts break so far no ones has for the raptor SC since release but it will eventually happen with enough milage. And if it does happen then the idea is the non boost tables will take care of the engine in the event of no boost.

is my theory correct?