Speed Density 2.0 (3D VE Tables, Baro)
Yea it is set to the OMNI4barmap. My load on MAF is max 300, on SD it went to 400 but boost is the same. Also, I don't have a MAT sensor yet, I was under the impression I could use the Fuel temp sensor but I'm not seeing where to set that up. Could that be throwing the load off?
I can't get the formula to work on my maf. Found an error now the box doesn't come up still reads zero.
I had load issues too. 1:1 solved my issues. Check your load conversion in tephra
I had load issues too. 1:1 solved my issues. Check your load conversion in tephra
Which formula? The VE formula?
I just left the pre-configured kpa2load and map2kpa, the only thing I changed under Speed Density is the VE table.
My 1byte load conversion is the same for both MAF and SD roms.
EDIT: I saw your post on the other thread about the MUT request, It doesn't matter what you put in the MUT request box in evoscan as evoscan doesn't actually use it becaue you are only calling from the 1BYTELOAD and KPA parameters in the eval.
Here is how mine is setup.
For VE parameter:
Display: VE
Logreference: VE
RequestID: 00
EVAL: ([Load1B]/[OMNIKPA_LOAD])*100
Unit: %
Responsebytes:1
Gaugemin:0
Gaugemax:150
chartmin:0
Chartmax:150
Scalingfactor:1
PriorityOffset:0
Loghide:false
You also have to make sure that your Load1Byte logreference is EXACTLY typed like the above, as well as the KPA logreference.
Hope this helps.
I just left the pre-configured kpa2load and map2kpa, the only thing I changed under Speed Density is the VE table.
My 1byte load conversion is the same for both MAF and SD roms.
EDIT: I saw your post on the other thread about the MUT request, It doesn't matter what you put in the MUT request box in evoscan as evoscan doesn't actually use it becaue you are only calling from the 1BYTELOAD and KPA parameters in the eval.
Here is how mine is setup.
For VE parameter:
Display: VE
Logreference: VE
RequestID: 00
EVAL: ([Load1B]/[OMNIKPA_LOAD])*100
Unit: %
Responsebytes:1
Gaugemin:0
Gaugemax:150
chartmin:0
Chartmax:150
Scalingfactor:1
PriorityOffset:0
Loghide:false
You also have to make sure that your Load1Byte logreference is EXACTLY typed like the above, as well as the KPA logreference.
Hope this helps.
Last edited by 90zcrex; Jul 22, 2013 at 07:14 PM.
Here are my SD settings
Last edited by 90zcrex; Jul 22, 2013 at 07:37 PM.
Kpa : load needs to be 1:1 and the highest load in your table will be the highest you can log.
Copy the left column into the right
Copy the left column into the right
Last edited by 211Ratsbud; Jul 22, 2013 at 07:44 PM.
No prob, it's overlooked often because for some reason it doesn't come set up how you need it for 3d. In 2d I think people mess with that.
I can't wait to build a 3d table from a maf set up
I can't wait to build a 3d table from a maf set up
Evolving Member
Joined: Jul 2010
Posts: 133
Likes: 1
From: Overland Park, KS
I may be mistaken but I swear I read somewhere you can get a rough 3d VE map through excel from logging stuff while still on your MAF setup. Is this true? And if it is, does anyone know how to create such excel file?
You don't really need to use excel. You just log your volumetric efficiency while still on maf Rom. And then filll out the VE table in you SD rom with the values you logged. You can set it up so that you can read kpa vs rpm in evoscan logviewer and then just transfer over to your sd ve table.
