EvolutionM - Mitsubishi Lancer and Lancer Evolution Community

EvolutionM - Mitsubishi Lancer and Lancer Evolution Community (https://www.evolutionm.net/forums/)
-   ECU Flash (https://www.evolutionm.net/forums/ecu-flash-179/)
-   -   96531706 speed density questions (https://www.evolutionm.net/forums/ecu-flash/510789-96531706-speed-density-questions.html)

drifterific Aug 24, 2010 11:54 PM

96531706 speed density questions
 
So I am having trouble wrapping my head the speed density tuning. From what I have read from Scheides guide to speed density tuning is that you want to scale your RPM-VE and your MAP-VE. But from reading other threads on speed density you want to keep your MAP-VE at a 1:1 ration while only tuning your RPM-VE. So theres contradicting theroies on tuning speed density. Is there a more upto date how-to for speed density?

My STFT fuel trims are staying at around 25% at idle and this is causing me to throw a check engine light. So I thought I would try Scaling my RPM-VE down 16% to see if it made a difference and the car idled in the 18 afr range. The car currently idles at about 14.3 and my cruise fuel trims are within (plus/minus) 2%. Also My Fuel trim low always stay at around 12.5 and never move. Any thoughts on this? My Fuel Trim High stays at about .01 all the time. I have even had the car idling for 30 minutes and it never changed.

I know I do not have any boost leaks cause I have tested it. My mods are Apexi intake filter, custom short route upper intercooler pipe, custom lower intercooler pipe, tial bov, EPM o2 dump and 3in down pipe, 3 in test pipe, HKS catback exhaust, OMNI 4 bar, GM Air Intake Temp Sensor. Im still currently on stock injectors until I get this speed density tuning completed then I will be installing PTE 1000cc injectors.


Thanks for the help.



Evoscan log
https://docs.google.com/leaf?id=0B5y...ut=list&num=50

EcuFlash Bin file
https://docs.google.com/leaf?id=0B5y...ut=list&num=50

l2r99gst Aug 25, 2010 06:01 AM

You need to tune both tables. VE varies with map and RPM, which is why there are two tables to begin with. Jcsbanks would have made a 3D VE table, but opted for the two 2D tables for sake of simplicity. The 2D tables are multiplied out to create your virtual 3D table. If you want more info on how to tune SD and how it works, read kscbanks thread entitled something like 'SD: first test success'.

Your car needs a lot more VE added to idle...that's why your LTFT Lo is pegged at 12.5 and your STFT is adding fuel as well.

Also, be sure that your map VE tables is scaled for whatever map sensor that you are using.

drifterific Aug 25, 2010 01:46 PM

1 Attachment(s)
Alright So I started tweaking both the MAP-VE and the RPM-VE and my LTFT Low started to come down. So I need to find the scalings for the Omni 4 bar map sensor to put into the MAP-VE table and then start scaling from there?

Also I noticed that there were 2 options for omni 4 bar map sensor, they were omni 4 bar map sensor and omni 4 bar map sensor-adj. Right now im using the omni 4 bar map sensor setting just like the write up. Could that be causing any issues? I notice that all of my tables look way different from everyone elses.

Also I attached a screen shot of my settings.

I noticed also that my values for this section of the rom is different from the other thread that I posted in. https://www.evolutionm.net/forums/ec...mat-scale.html

Here are my values

SD IAT ADC SENSOR (ENTER MAT SENSOR SCALING)
0.12 260.6
0.14 260.6
0.16 260.6
0.18 260.6
0.2 253.4
0.22 246.2
0.24 240.8
0.25 235.4
0.27 230
0.29 226.4
0.31 221
0.33 217.4
0.35 213.8
0.37 210.2
0.39 206.6
0.41 203
0.43 199.4
0.45 197.6
0.47 194
0.49 192.2
0.51 190.4
0.53 186.8
0.55 185
0.57 183.2
0.59 181.4
0.61 177.8
0.63 176
0.65 174.2
0.67 172.4
0.69 170.6
0.71 168.8
0.73 167
0.76 165.2
0.78 163.4
0.8 161.6
0.82 159.8
0.84 158
0.88 156.2
0.9 154.4
0.92 152.6
0.96 150.8
0.98 149
1 147.2
1.04 145.4
1.06 143.6
1.1 141.8
1.14 140
1.16 138.2
1.2 136.4
1.24 134.6
1.25 132.8
1.29 131
1.33 129.2
1.37 127.4
1.41 125.6
1.45 123.8
1.49 122
1.53 120.2
1.57 118.4
1.61 116.6
1.65 114.8
1.69 113
1.75 111.2
1.78 109.4
1.82 107.6
1.88 105.8
1.92 104
1.96 102.2
2.02 100.4
2.06 98.6
2.12 96.8
2.18 95
2.22 93.2
2.25 91.4
2.31 89.6
2.37 87.8
2.43 86
2.47 84.2
2.53 82.4
2.57 80.6
2.63 78.8
2.69 77
2.73 75.2
2.78 73.4
2.84 71.6
2.88 69.8
2.94 68
3 66.2
3.04 64.4
3.1 62.6
3.16 60.8
3.2 59
3.24 57.2
3.29 55.4
3.35 53.6
3.39 51.8
3.43 50
3.49 48.2
3.53 46.4
3.57 44.6
3.63 42.8
3.67 41
3.71 39.2
3.75 37.4
3.78 35.6
3.82 33.8
3.86 32
3.9 30.2
3.94 28.4
3.96 26.6
4 24.8
4.04 23
4.08 21.2
4.1 19.4
4.14 17.6
4.16 15.8
4.2 14
4.22 12.2
4.24 10.4
4.27 8.6
4.29 6.8
4.31 5
4.33 3.2
4.35 1.4
4.37 -0.4
4.39 -2.2
4.41 -4
4.43 -5.8
4.45 -7.6
4.47 -9.4
4.49 -11.2
4.51 -13
4.53 -16.6
4.55 -20.2
4.57 -22
4.59 -25.6
4.61 -29.2
4.63 -34.6
4.65 -40

Settings in the XML for the Omni 4 bar map sensor

<scaling name="BoostErrorPsi OMNI4barMAP" units="psi" toexpr="(x-128)/(8*4.23)" frexpr="x*8*4.23+128" format="%.1f" min="-3.8" max="3.8" inc="0.1" storagetype="uint16" endian="big"/>

<scaling name="PSIa16 OMNI4barMAP" units="PSIa" toexpr="x/(4.23*2)" frexpr="x*(2*4.23)" format="%.1f" min="0" max="39.2" inc="0.1" storagetype="uint16" endian="big"/>


<scaling name="PSIa8 OMNI4barMAP" units="PSIa" toexpr="x/(4.23*2)" frexpr="x*(2*4.23)" format="%.1f" min="0" max="30.1" inc="0.1" storagetype="uint8" endian="big"/>


<scaling name="kPa OMNI4barMAP" units="kPa" toexpr="x*0.4072" frexpr="x/0.4072" format="%.1f" min="0" max="450" inc="0.4072" storagetype="uint16" endian="big"/>





Here are the Omni 4 bar map sensor-adj

<scaling name="PSIa8 OMNI4barMAP-Adj" units="PSIa" toexpr="(x/(4.23*2))+7.4" frexpr="(x-7.4)*(2*4.23)" format="%.1f" min="0" max="30.1" inc="0.1" storagetype="uint8" endian="big"/>

Sorry for the long post

95630706 Aug 25, 2010 01:56 PM

That would make sense that they are different. The values I posted where (or should be) from the JDM 3bar MAP not the Omni 4 bar that you are using.

l2r99gst Aug 25, 2010 01:57 PM

Your IAT scaling looks OK to me...at least the top portion that I looked at.

As far as the map scaling, I was just mentioning to make sure you have the correct scaling for you sensor or the map VE table will be off. If you have the OMNI 4-bar map, then just make sure the scaling for map 16bit is set correctly, that's all.

drifterific Aug 25, 2010 02:13 PM


Originally Posted by 95630706 (Post 8614757)
That would make sense that they are different. The values I posted where (or should be) from the JDM 3bar MAP not the Omni 4 bar that you are using.


Ah ok that makes a lot of sense now. Thanks.

drifterific Aug 25, 2010 02:17 PM

1 Attachment(s)

Originally Posted by l2r99gst (Post 8614760)
Your IAT scaling looks OK to me...at least the top portion that I looked at.

As far as the map scaling, I was just mentioning to make sure you have the correct scaling for you sensor or the map VE table will be off. If you have the OMNI 4-bar map, then just make sure the scaling for map 16bit is set correctly, that's all.


Yeah I have my maps set up for the Omni 4-bar. I just noticed that there were two different ones. I posted a picture of the settings and circled them. Thanks for all the help you guys.

drifterific Aug 25, 2010 10:06 PM

So I get my cruise and idle fuel trims dialed in today at (plus/minus) 1.5%, so I tell myself that I am good to go to unplug my maf. Well when I unplug the maf my fuel trims go all out of whack again. Is this supposed to happen or was I supposed to do this from the beginning? Sorry for all the questions.

l2r99gst Aug 26, 2010 06:23 AM

Where is your MAT sensor wired into?. Sounds like maybe you have it wired into your fuel temp sensor, but have your setting in your ROM set to IAT instead of fuel temp.

drifterific Aug 26, 2010 01:02 PM

I have it wired into the pin 77 fuel temp sensor acd and I have the "SD Option: IAT Input for MAT set up for 0x0E.

l2r99gst Aug 26, 2010 01:27 PM

Sounds like you have it set up correctly. Your trims shouldn't have changed when you unplugged your MAF sensor. Nothing should have changed. Unless you just mean that they are drifting around as usual

drifterific Aug 26, 2010 02:10 PM

Yeah when I had the maf attached my LTFT mid and low were within 2% but when I unplug the maf my LTFT mid went all the way to -12. I got everything back within 2% now. I noticed that in evo scan I am still getting a reading from "Manifold Air Temp Scaled" request 11. I also added Manifold Air Temp request 09 and they are both reading the same. Also the reading seems a bit high to me. It usually sits around 100 at idle when the ambient air temp is 84(today)

l2r99gst Aug 26, 2010 03:46 PM

OK, I thought u meant your trims immediately went out of whack once u unplugged your MAF. Everything sounds fine to me...your trims drifting were probably just VE needed more fine tuning for certain map and RPM.

Your MAT temp of 100 sounds about right, too, with those ambient temps and idling for a bit.

drifterific Aug 26, 2010 03:54 PM

ok thats good to know. Thank you for all your help l2r99gst.

drifterific Aug 27, 2010 01:57 PM

Is tuning injectors on SD different from maf? I had all my SD fuel trims with in 2%+/- and when I installed the injectors I expected the fuel trim to get out of line but it seems no matter what scalings I am using they will not get close. I am using PTE 1000cc injectors. I used the numbers from the Injector latency super merge but they were pretty far off


All times are GMT -7. The time now is 06:52 PM.


© 2024 MH Sub I, LLC dba Internet Brands