I have been using this feature since it came out! Very nice! Dont forget the Mivec map!

Evan Smith

 

I tried to smooth just timing, this is not an easy task.
It would be cool to have an automated solution for this

 

The fact that even with interpolation the jumps are less subtle with smoothed maps and this has been proven to cause issues with a lot of people. 4 to 10 between cells has a midpoint of 7 and 4to8 has a midpoint of 6. It has been my experience that the ECU does not necessarily like larger jumps between cells....

Based on the above example it does matter as the interpolated values are different. The interpolated value is in between the two cells not always in the middle if I am not mistaken.
YMMV

 

Oh absolutely, the interpolated values are different! Sorry if i gave the wrong impression. The mechanical systems don't like big jumps and the jumps will be bigger with a map full of jagged cells. The ECU itself doesn't have to "try harder" to do the calculations was all i was trying to point out. It can interpolate big jumps just as easily as small ones. You might loose some percision but i doubt it. Your engine trying to deal with a 60% increase in injector pulse between cells would be another matter

I suppose it's splitting hairs but that's what i like to do, computers are cool

 

I have been thinking about upgrading to 1.35, just for this feature, but concerned w/ 2 things...

1. W/ my limited comp. knowledge, I was hoping it would be an easy task, but was assuming it wasnt as easy as Jack_of_trades makes it out to be...
Could you possibly start a "how to" on this when you have some free time, for us, not so knowledgable people?

2. Im using 1.29 w/ most of the .xml "patches", minus the Tephra stuff. What Im concerned about is: Are all of the new patches in there? ex. (3D MUT table, and the new boost control tables. I would assume yes, but what do I know... And are there any other probs w/ this version, besides the freezing?

I think this is an awesome feature! Just need to know how to use it...

TIA

 

My noob will be showing but...

How is the best way to even start the smoothing process? Is it better to smooth the low points "up"? Or smooth the high points "down"? Or to only smooth the areas between the high and low points? What is more important vertical smoothness? Or Horizontal smoothness?

Which is more critical in avoiding knock, smoothing the fuel or smoothing the timing? I would assume timing...

 

Given enough time and motivation I just might put my grad degree to use and use some fancy math. but until then I'm just blowing smoke. But there are a lot of numerical methods for surface data smoothing. I was starting to apply a few of them already to smoothing the logs for HP calcs, this would would just take into into another dimension.

but like I said, smoke ...

 

Ok my 2nd attempt.

Will test this 1 tomorrow.

 

Man, I just did some driving on this map and am reporting back via a PC. Off boost driveability seemed smooth, but WOT felt a LOT more smoother. I had a few occasions of sparatic knock >3cts which I will have to take a look at the log and fix, but other than that, smoothing makes a BIG difference.

 

Wow, lots of people posted in here today,lol. The maps are in raw bit values and just use a formula to show a more "user friendly" value in the cells. Timing is in increments of 1 so its the easiest to tweak since you basically are seeing it the same way the ECU does. The Fuel maps are adjustable from 0 to 128 if memory serves me. Refining the increments just gives you more adjustment points so you can dial it in a little better.


I threw some new spark plugs in my car today and just took it for a ride. Wow, I'm in love with my car all over again! Thing pulls like a BEAST compared to before. I am now able to run 25* of timing at 7K RPM @22psi where I couldn't climb towards 20* before without knock coming in to join the party. It totally works and I love it. If you wonder why I can run so much timing, I'm running an Aquamist HFS-5 kit with 100% Denatured Alcohol.

 

Can someone post the before and after picture of the timing maps associated to the before and after graphs?

 

Does anyone feel map smoothing would be beneficial to the MIVEC map? I'm currently using the JDM RS mivec map right now and its nowhere near smooth.

 

I noticed a smoother power band in mine as well as everyone who uses it Smoothin is a good thing! it was smoother until I got M3 cams so it has been alterd, more changes to come.

 

It can't hurt to smooth the transistions in any map. Another thing I noticed, my power graphs in evoscan are a LOT smoother now too! Used to have dips and peaks, now its a nice smooth line.

 

Ok I worked out a very basic autosmoothing version. Nothing more than a center weighted average of the cells surrounding the original cell. For non-edge cells that means average(x) = (x+x+x+a+b+c+d+e+f+g+h)/11). Except on the edge cells which are just the straight average of the original cell and its surrounding 5 cells.

A bunch of cells I left completely alone because the load/rpm is low and the resulting values just didn't aid in smoothing out the curve but seemed to give lower timing than I really would want anyway. They are shaded gray.

Obviously this is just a way to get a good start before you hand tweak. But boy does it take out the grunt work.

That was for timing. For fuel I did the same basic thing but instead of doing a direct link on some cells I just tested for it being 14.7 and kept it at 14.7otherwise it was center-weight averaged. Again the edge cells just averaged.

On both timing and fuel I did some conditional formatting to key in on changes both in the main tables as well as the "difference" tables.

Finally I've got them both set up so that you can compare stock, to modded, to smoothed.

I'm not really done playing around increasing the "logic" of the conditional smoothing but I can tweak this thing forever without ever being "done" and figured it is better just to release versions.

http://jumptronix.com/evo/EVO%20Map%...osmoothing.xls

EDIT: oh yeah and on the timing I rounded to an integer. I wanted to use the ceiling function to always increase timing but it doesn't seem to work with negative numbers and I got too lazy to set up a conditional or create my own version of a ceiling function. Another option I'm considering is limiting all changes to +/- 1 and then letting the user iterate till you get it at smooth as you want with as few changes as possible. Or allow for a settable threashold value below which there is no change. and and ... yeah it is 12:45am, Law and Order SVU is on (with Tank from The Matrix as the bad guy), and I have 10 different ideas running through my head. hehe and I could easily make those threshold values unique for each RPM and/or load but that just seems like silly over engineering.