Car: EVO IX USDM
zeitronix map sensor.
2d SD

ok after messing with SD for about a week I finally have broken down and have to admit i am very very confused. I kind of understand that on the RPM vs VE table the more u pull back on the VE the leaner your AFR should get. idk why it does i just know it does and you can correlate your front o2 giving you a -% with meaning to go leaner and you are rich (verified on AFR meter). I still have absolutely no clue how the MAP kPa vs Load works at all. I have to thank Roadspike on setting up the map side for me so i could get the car to run without being super pig rich. I have no idea how to scale either side of that table.

So far all i have managed is to get the car to run off boost almost on 14.7 for most of the time. in evoscan i still see the front o2 giving me a -%. Where it goes all terribly wrong is the moment i hit 0psi and greater all i see is AFR 9.6 and front o2 with a positive number.

More wrong: cold start= pig rich

Stop and go traffic = leans, doesn't accelerate for a bit. (tried async vs TPS) some improvement at +10 units across the board started at 5

Jitters= Fix 1 and 2 have almost completely eliminated that from light throttle cruise.

I have read thru the entire sd first test success thread and ended up i think more confused.

Thanks in advanced for those who help me also to the guys who made SD possible!!!

 

So you basically ran into the scenario i was talking about in my 3D SD code where the low RPM and big loads, IE on take off, the car would go super lean for a bit. You may want to consider testing one of my roms as the 3D table should make a lot more sense to you.

Just log kPA for boost and the wideband AFR and use evoscan's map tracing should be straight forward then to firgure out whats going on.

The old 2D version:

SD definitely isn't for everyone it takes quite a bit of learning to really get the hang of it. Try not to mess with the VE settings I gave you to start with so much in the beginning try tuning it out with the map sensor ve vs load table first then optimize VE.

You can tune up idle with the maf smothing table if your idle is rich only tune this when its warm though there are enrichment tables which effect idle AFR when its cold.

 

well i was planing to move to 3d but i still have little idea of how it works in 2d. so i figured i would start there.

What am i looking for when i use the tracing of kPA vs AFR?

So you suggest i mess with Map vs load instead of rpm vs VE, ok so how do you figure out the values for map and load?

also what should i change in evoscan for the formula u gave me to get kPA instead of psi. (unless its as simple as just adding a psi to kPa conversion)

ty so much!!!

also i don't have maf smoothing i have maf scaling and maf compensation

 

Then it would be the compensation table for adjusting idle.

You look for trends left to right for VE and trends up and down for map sensor ve vs load. Essentially if a column is lean or rich the map sensor VE is at fault and if the left and right is rich or lean then the RPM VE needs to be adjusted so its flat and then corrected with map sensor VE.

As you can see a lot of this is map sensor VE which i'm trying to simplify with the 3D map which i consider easier to grasp.

 

Skylineracer Post up a screen shot of your MapVe table and that may lead to more help with your questions. Also are you still running stock injectors?

 

ok is this what i am suppose to do





yes stock injectors

 

Are those the averages i cant tell. Make sure they are so you are adjusting the average of whats happening not just some extreme moment as it will never be perfect.

Whats the scaling on the map sensor VE? it looks way way off.

Also pay no attention to STFT for a way to look at how to adjust as its inacurrate and too wild to tune by. Use only AFR from the wideband to tune and simply compare it to your fuel map.

 

the SD stuff is just how u sent it to me, i have the maf compensation adj to bring back in the afr. as for those graphs the map is in psi still, (this was for a total short drive, should i shorten the data?)

 

should i just post a log?

 

From what I can tell it looks like your Map (KPA) may be off for your map sensor scaling. I do notice that you are using a zeitronix map sensor but I do not believe they should be that high to start with. RoadSpike would beable to tell you if the values are to high of a starting point.

I know the screen shot is not the same map sensor but this is what the stock SD table looks like for 9. Hope this helps you out. If it confuses you more please disregard

 

what u have is more or less what i had when i started.

 

Ah ok. When I started with SD on my car I never touched the Left hand side of the mapve table. I only used the right side and the rpm ve table. You are using a different map sensor so that could be the difference. It almost looks like you are only using the left hand side (map KPA) what I would so is start over and set the map (kpa) side back to what it originally was and make your adjustments with the Load(%) side of that table. This could be why you are going lean on tip in. Have you looked at this sd tutorial https://www.evolutionm.net/forums/ec...ched-roms.html ?
If i remember correctly he was using a omni 3 bar map sensor

 

Is that true?

You can change the scaling from Map16bit to kpa Kavilico 3.5Bar and it will look right.

 

that explains so much! no wonder it ran so bad at first until you adjusted the values. ok so now i should adjust the map and not the load or should it be the other way around like drifterific said.

 

Increase the kPA value (left hand side) for 20,40 load and 90 load cells and those two columns will be leaner.