Speed Density 2.0 (3D VE Tables, Baro)
#751
EvoM Guru
iTrader: (1)
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.
This is exactly what I started doing today.
My ve from my already tuned by target afr set up was very close in some areas, transitional pressures, and off by 10 or so at 240 kpa. That's just a reflections of the already tuned sd ve table being based of ideal afrs vs my maf rom having typical 10. Xx to achieve 11.xx.
I'm gonna unhook my wga from the flapper. This method has tremendously leaped and bounded over the log and lookup map adjust ve flash method
#752
Evolving Member
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.
#754
Evolving Member
iTrader: (11)
What kind of difference are you getting? What rpm? I see around 102-105 VE in that area at around 3700-3900 rpm. I actually didn't even use Evoscan while making my VE map. It's pretty easy to just look at a couple datalogs and get an idea of what it should be in certain areas. Now that I've fixed the 1:1 issue I'm reading almost dead on with my maf tune at WOT. I have a couple small areas to add a little fuel withe VE but overall it was pretty damn easy. Almost too easy lol.
#755
EvoM Guru
iTrader: (1)
220 kpa sees 120% tapering to 114%
240 kpa sees 111 tapering to 103
I took all of my wot logs, combined them in to one log and used map tracer to display that log. Used map as my x axis too
Now that I've worked out the kinks so I can brake load every thing like hell lol
240 kpa sees 111 tapering to 103
I took all of my wot logs, combined them in to one log and used map tracer to display that log. Used map as my x axis too
Now that I've worked out the kinks so I can brake load every thing like hell lol
Last edited by 211Ratsbud; Jul 24, 2013 at 09:34 AM.
#758
EvoM Guru
iTrader: (1)
Is it important to use increasing tps only or ca. Steady state tps data be used aswell?
#760
Evolved Member
iTrader: (6)
what I can say is that I found something that messes the VE calcs logging:
A synapse BOV can be either open or shut at the same load and rpm (i.e 80 load/3000RPM) depending on TPS behavior (movement/speed/up or down).
Like you said, it's important to log only stable/raising tps and no decel at all while doing this method.
#761
Evolving Member
iTrader: (1)
I have a stupid question. Speed Density uses the 3D VE table exclusively even if running open loop full time? I thought i read somewhere that above 90% throttle is switches to the fuel map. I searched for the answer on here but did not find anything to confirm that.
#763
Evolved Member
OK couple of mega noob questions.
I have a JDM 8 and I'm running 96534706 (3d). I read the 9653 MAF rom being based on EDM was never designed for use with a MAP sensor. Now I'm obviously running one (GM3bar) and I have it connected to pin 92 of my 3 plug ECU. I log this input from MUT38. However for SD rom the rom needs to know what boost is, but I have no code to set to 1. scale the GM3bar and 2. tell the rom what address to look at for the MAP sensor input. I'm assuming this rom was written for USDM cars with a MAP sensor and the address for this input coded in accordingly. What do I need to do since I run this rom on a JDM 3 plug?
All I have are these settings for Max VE etc.
What do I set them to and do I need additional code to set GM3bar scaling/address so the rom can use it. Mrfreds thread has all but 9653 code.
I have a JDM 8 and I'm running 96534706 (3d). I read the 9653 MAF rom being based on EDM was never designed for use with a MAP sensor. Now I'm obviously running one (GM3bar) and I have it connected to pin 92 of my 3 plug ECU. I log this input from MUT38. However for SD rom the rom needs to know what boost is, but I have no code to set to 1. scale the GM3bar and 2. tell the rom what address to look at for the MAP sensor input. I'm assuming this rom was written for USDM cars with a MAP sensor and the address for this input coded in accordingly. What do I need to do since I run this rom on a JDM 3 plug?
All I have are these settings for Max VE etc.
What do I set them to and do I need additional code to set GM3bar scaling/address so the rom can use it. Mrfreds thread has all but 9653 code.
#765
Evolved Member
Yep I have scaled both to GM3bar. But how does it know what the output of the MAP sensor is if you never tell it what address to read it from?
When changing from stock to JDM MAP sensor the Mid VE Max voltage/min voltage etc need to be changed. I'd like to know what to do with them for a GM 3 bar too.
When changing from stock to JDM MAP sensor the Mid VE Max voltage/min voltage etc need to be changed. I'd like to know what to do with them for a GM 3 bar too.