SD - first test success
EvoM Guru
iTrader: (50)
Joined: Mar 2006
Posts: 9,675
Likes: 132
From: Tri-Cities, WA // Portland, OR
Multiplying by 100 will put it in the correct units for the VE tables.
Last edited by mrfred; Feb 28, 2009 at 04:53 PM.
Ok here is the logworks maptrace and what i got for the tables using mrfreds equation. I am still lost on how to get the RPM VE.

20kPa: 85%
30kPa: 89%
70kPa: 92%
80kPa: 93%
90kPa: 92%
100kPa: 96%
120kPa: 98%
130kPa: 100%
MAP VE calibration
10kPa: 8.5
20kPa: 17
30kPa: 26.7
50kPa: 45.3
70kPa: 64.4
100kPa: 96
130kPa: 130
310kPa: 310

20kPa: 85%
30kPa: 89%
70kPa: 92%
80kPa: 93%
90kPa: 92%
100kPa: 96%
120kPa: 98%
130kPa: 100%
MAP VE calibration
10kPa: 8.5
20kPa: 17
30kPa: 26.7
50kPa: 45.3
70kPa: 64.4
100kPa: 96
130kPa: 130
310kPa: 310
The way I have been doing mine is to normalize that table with the MAP VE values you are planning to use. From there, everything is scaled by MAP so you can look at the data and figure out what the VE is. Looking at your data, I would say your nominal MAP value is probably ~98%.
One thing to point out is that you need to understand how motors typically work and have a good feel for engine VE to set this up. Motors usually have pretty smooth VE curves where this data can jump around quite a bit in mid load situations that would lead to some ugly VE curves.
JCSBanks, linear interpolation is still used in these tables, right? I've been able to come up with a MAP VE curve that has just a few break points if this is the case.
Also, one other question. There is the MAP VE table that has the MAP values vs. MAP*VE values. On the IX ECU, there seems to be a MAP scalar in the JDM MAP patch (and possibly in this patch?). There isn't a scalar on 94170015. I'm a little confused how a 3 bar, 4 bar, or 5 bar can be used without a scalar telling the ECU what the MAP reading is? If I were using a 3bar JDM instead of the 4 bar Omni, would the difference simply be in my MAP calibration table? With the Omni, my max MAP VE is 102% so at a MAP value of 120, I have 122.4 put in, but how does it know what 120 kPa is without a scalar tell it?
One thing to point out is that you need to understand how motors typically work and have a good feel for engine VE to set this up. Motors usually have pretty smooth VE curves where this data can jump around quite a bit in mid load situations that would lead to some ugly VE curves.
JCSBanks, linear interpolation is still used in these tables, right? I've been able to come up with a MAP VE curve that has just a few break points if this is the case.
Also, one other question. There is the MAP VE table that has the MAP values vs. MAP*VE values. On the IX ECU, there seems to be a MAP scalar in the JDM MAP patch (and possibly in this patch?). There isn't a scalar on 94170015. I'm a little confused how a 3 bar, 4 bar, or 5 bar can be used without a scalar telling the ECU what the MAP reading is? If I were using a 3bar JDM instead of the 4 bar Omni, would the difference simply be in my MAP calibration table? With the Omni, my max MAP VE is 102% so at a MAP value of 120, I have 122.4 put in, but how does it know what 120 kPa is without a scalar tell it?
Last edited by 03whitegsr; Feb 28, 2009 at 11:23 PM.
Yes linear interpolation is used. These VE curves are actually bit flatter than they would be if it wasn't for the MAF scaling still being used, which left as standard, actually makes up a large part of the adjustment. Eric told me to do it this way 
Yes, for MAF emulation purposes (not for EGR faults etc), the only thing to change between MAP sensors is the scaling for the top row (input) of the MAP VE table. It knows it is 120kPa because you change the scaling AND have then corrected the values in the top row to match (the raw values are changed by this and this is how the ECU "knows").

Yes, for MAF emulation purposes (not for EGR faults etc), the only thing to change between MAP sensors is the scaling for the top row (input) of the MAP VE table. It knows it is 120kPa because you change the scaling AND have then corrected the values in the top row to match (the raw values are changed by this and this is how the ECU "knows").
wow guys. Just got back from the maiden run and i am very happy with the results. Car feels great. STFTs were between -1 - 1 mostly in the 0.xxx range. I just need to finish tuning the non SD maps now. Anyway thanks to JC and mrfred for the amazing work. I am very excited get the car fully tuned now 
I also have a log of my short trip. Got a little pull in mostly around town stuff to see how it did. If anyone wants to check it out let me know.

I also have a log of my short trip. Got a little pull in mostly around town stuff to see how it did. If anyone wants to check it out let me know.
I have a IX so i run 88590015. I dont think the mods affect how SD has made it better the car just seems to drive better. especially around town and off throttle. There is much less jerking and the car seems to transition smoother through throttle modulation. I have to drive the car a bit more to how it really has changed but so far i am happy.
As soon as this comes out for 96530006, I'm switching over. I think mrfred is close to finishing it for that ROM, or at least I hope. I see so many people setting up SD and I can't wait. : )
Sigh, it doesn't look like i will be driving today - woke up to 6" of snow and we are expecting another 5-6 throughout the day.
One thing i did notice yesterday is the car did seem to take some time to return to normal idle when coming to stop and putting in the clutch. I have to drive some more to verify.
One thing i did notice yesterday is the car did seem to take some time to return to normal idle when coming to stop and putting in the clutch. I have to drive some more to verify.
Yes, for MAF emulation purposes (not for EGR faults etc), the only thing to change between MAP sensors is the scaling for the top row (input) of the MAP VE table. It knows it is 120kPa because you change the scaling AND have then corrected the values in the top row to match (the raw values are changed by this and this is how the ECU "knows").
11, 21,31,41,61,101,121,340
Do I need to scale for the 4bar as multiples of these values or can I scale it as I feel needed?
From the charting I have done, I feel these values would be the best break points for my car with the 4bar Omni sensor:
10,50,120,160,200,250,300,400
Use your own break points. The bottom row will be the top row multiplied by your desired VE %. So if you have for example 100% VE at 160 upwards, then you'd have 160,200,250,300,400 in the bottom row as well as the top row.


