EDIT:
I gave it my best shot..

http://jeffbeagley.com/random/VE%20Calculator.xlsx

Is someone on here willing to help me finish this? Would be nice if we could scale the rpm and kpa values appropriately and it work correctly for anyone.

 

subscribed

new to tuning and have been tuning my 2.4 6262 on sd from scratch.
still learning so i dont know much but if this will help dial in the sd tables im in.

 

I did just make this real quick without using any Interpolating.

This makes my SD Tables look AWFUL lol! Looks like I'll be going for a drive now.

 

Updated one here
http://jeffbeagley.com/random/VE%20Calculator%202.xlsx

Would be nice to have it interpolated to a large graph.. but thinking about it I do not believe its truly necessary. This should provide a great starting point for you to setup your SD tables.

 

I built up a spread sheet that does all the interpolation and deals with the axis conversion. The limitation is that the new axis fall within the bounds of the 2d axis. Catching those out of range values is a decent amount more work. It needs some clean up to be more user friendly.

Had to use the help function to remember how to do array lookups...

Shoot me a pm and I can send it over for comparison.

 

I thought this would give you the 2d table values when you input values in the 3d table obtained from logging.

 

It's more for folks who are tuning Speed Density from scratch... And to see what their current setup is doing. I only found out last week that RPMVE helped calculate Final VE.

Hopefully this helps folks visualize a little better.

 

This thread got me thinking and I have decided to try to create a spreadsheet that would give you the (2) 2d tables from a 3d table. To test it out I would need some logs that include rpm, load and map from some maf sensor equipped cars. I can dig some up but if anyone can send me some it would help too. You can email to mhay.cac(at)gmail.com.

 

Going 3D to 2D won't work.

That's the entire point of 3D mapping... You get resolution that you can never get with 2D tables.

Why would you want to go today direction anyway?

 

Obviously 3D is better but not everyone is running the 3D SD because some of the ROMS don't seem to work properly. Currently the two 2D tables are adjusted by what amounts to basically trial and error to approximate a 3D table. So if a spreadsheet could spit out two 2D tables that are a close approximation to logged values in a 3D table I think it would save a lot of tuning time.

 

This should be kept in mind when playing with these tables.