Hi. Does anyone knows how to tune VE maps on lancer? Need help on those. Thanks

 

There is no right or wrong way of doing things in my opinion.

There are some general pointers I could give you to make it easier.

First lets understand that the whole system is fuel control so as long as the fuel in the end is the desired AFR your shooting for it doesn't matter how you got there.

Secondly lets understand that the VE map itself is more like a Fine tuning knob and as such it runs out of room to grow or shrink pretty rapidly if you don't have great settings in the kpa vs load table.

So for the most part keep the VE table pretty flat to start out with you could use my example if you wanted and mess with the more course adjustment knob (kpa vs load table) first. Start with 1:1 kpa to load and work from there. To test it you just set it and start driving paying attention to where the AFR is with a wideband. A wideband is a complete must here you will not get anywhere guessing with speed density.

Once you've played with the kpa vs load map to your liking you can smooth out abnormalities with the fuel using the VE map. High values mean more fuel, richer, and less is the opposite so pretty easy. A graphing utility like evoscan is a great tool here but it could be done with a careful observation of what vacuum kpa correlates to the rpm and afr.

Another general note is the map should be smooth looking engines don't suddenly change characteristics they gradually change from one section to the other. If you have cliffs in your design its probably flawed in some other area your not testing yet.

Thats about it. Once you got fuel working to the point of satisfaction I would start tuning the timing map then.

 

Epic advice. I did nearly this exact approach. The one thing I did that made life difficult was I tried just leaving kpa2load linear and 1to1....which made me have some low spots in my ve map that didn't really make sense. The more I ironed out the kpa2load to match overall results like "in general my car is rich at 60kpa, so decrease kpa2load at 60kpa" the less I saw those odd peaks and valleys in my ve map.

Also, I had to adjust my timing map pretty quick, since my kpa2load put me in a much lower load range compared to maf....so my timing was too advanced, and causing dangerous knock.

Love that vta bov though...makes it all worth it. Also...don't get thrown off, the ve maps are generally kpa (not load) vs VE, so don't compare load to kpa, you have to use the kpa you log to get the value that's referenced. There is an evo thread on tuning SD, and it's pretty easy to follow. If you use SD2.0, then you have to adapt that to fit your needs, it's a learning exp.

 

Thanks a lot for your detailed explanation Roadspike. But my rom doesn't seems to have kpa vs load table.

 

It's SD1.0 then, the original one? You'd use this guide then, right here:https://www.evolutionm.net/forums/ec...ched-roms.html

 

Thanks for your info! I'm having a JDM lancer GLX 4G18 engine. so with definition file I must choose from?

<!-- ** JCSB SPEED DENSITY MAP sensor "calibration" scaling definitions ** -->

<!-- ** JDM Evo 9 // UDSM Evo 10 3 bar ** -->
<scaling name="MAP 16bit" units="kPa" toexpr="x/3" frexpr="x*3" format="%.1f" min="0" max="350" inc="0.3333" storagetype="uint16" endian="big"/>

<!-- ** OMNI 3 bar ** -->
<scaling name="MAP 16bit" units="kPa" toexpr="x*0.3074" frexpr="x/0.3074" format="%.1f" min="0" max="350" inc="0.3074" storagetype="uint16" endian="big"/>

<!-- ** GM 3 bar ** -->
<scaling name="MAP 16bit" units="kPa" toexpr="x*0.3014" frexpr="x/0.3014" format="%.1f" min="0" max="350" inc="0.3014" storagetype="uint16" endian="big"/>

<!-- ** AEM (Kavlico) 3.5 bar ** -->
<scaling name="MAP 16bit" units="kPa" toexpr="x*0.4213-43.1" frexpr="(x+43.1)/0.4213" format="%.1f" min="0" max="400" inc="0.4213" storagetype="uint16" endian="big"/>

<!-- ** OMNI 4 bar ** -->
<scaling name="MAP 16bit" units="kPa" toexpr="x*0.4072" frexpr="x/0.4072" format="%.1f" min="0" max="450" inc="0.4072" storagetype="uint16" endian="big"/>

<!-- ** Kavlico 5 bar ** -->
<scaling name="MAP 16bit" units="kPa" toexpr="x*0.6320-64.7" frexpr="(x+64.7)/0.6320" format="%.1f" min="0" max="550" inc="0.6320" storagetype="uint16" endian="big"/>

 

Well.....do you know which sensor that is that the car uses? If not, you might have to buy a known one like omni 4bar. Does your map sensor have a model or item number? Of, as dealer what part it is and look if it compares to 3bar, 1bar, or something else. I goggled but didn't see anything.,

 

Yes. Indeed I tried searching but I can't get any info about my map sensor. As looking for a map sensor in my country is also quite a hassle too. Thanks for advice.

Another question, is it possible for me to assume that load and kpa are equal? As I don't even have the kpa vs load definition and mapping in my rom. Or any evoscan logs can define my loads reference to the manifold air pressure?