Tune by Statistics - VemsTune

[emil@vems.se]

In the next version, some changes are started to the tune by statistics
now removes outliers in the data, adjustable of course
next step is that it will draw a bell curve showing your data spread
and after that, weighting according to how close to the actual site your are will be added.

[multiplex]

sounds like some awesome features in the works

i have one question - how does running map multiplication effect the ve stats?  Does it need to take this into consideration when calculating the results?

Also,  how can i save changes i make to the filter?  I see a button there, but its always grayed out.  I usually filter out my idle area so that isn't effected

[gunni]

You can select the cells to "fix" . so that not all areas are changed even if you let the check go through them.

Running map multiplication will not change anything.

The VE map works the same either way, i.e 10% more in the VE table adds 10% to the final pulsewidth.

[Jamo]

Any recommendations on the values to enter for lambda delay, variance multiplier and min # data in cell?

[z0tya]

And how can I close out the transients from statistics?

[gunni]

The log you do is the bases for any good tuning.

so it´s best to do a specific driving, like alot of steady state cruising and such in various gears.
in-town traffic ain´t exactly going to help the tune get better.

If you can keep it at 2000rpm steady in a few gears, then same for 3k and 4k, maybe 3-5sec per rpm and gear so that everything stabilizes. Then a WOT run if the mixture is close enough.

[Jamo]

The results I have had with tune by statistics I personally had were not as good in comparison to MLV using the very hard option.

Tune by statistic leaned out a lot of my figures for some strange reason, I'll test it in the next vemstune version

[paul_f]

To use the tune by statistics should the EGO limits be set to 0 for the logs?

[MWfire]

To use the tune by statistics should the EGO limits be set to 0 for the logs?

no

[Jamo]

The results I have had with tune by statistics I personally had were not as good in comparison to MLV using the very hard option.

Tune by statistic leaned out a lot of my figures for some strange reason, I'll test it in the next vemstune version

newer versions have been a lot better, I'll have to do a side by side comparison of MLV on my next logging run

[paul_f]

Does tune by statistics not work if you are running alphaN?
The axis are MAP x Engine speed, so all my data is at 100kpa (as I don't have the MAP attached to the throttle bodies

Although I have just spotted that MAP(load) multiplication has switched itself on, even though it was definately off in an earlier config

I'll turn it back off and try some more logging.

[rob@vems.co.uk]

It should work just fine with AlphaN, its only interested in matching the tables as they stand with the lambda delta between target and reading.

[paul_f]

I'll try it again tomorrow now I have switched off MAP (load) multiplication which switched itself on (maybe at the same time as Wideband changed to narrowband)
However the log I took today came up with this

[BigD]

What am I doing wrong? Why is VEMSTUNE tune by stats giving me such radical numbers in places (if I didn't filter out the off-throttle lean figures, some of the +s were in the 20s!!! That would drown my engine (I know from my last track outing and some figures I had causing rich misfires):

(I know the map is out of whack, this was in the middle of tuning it)

http://i.imgur.com/mdkrs.png

[mattias]

Did you read my posts earlier in this thread?

Only adjust cells which have low min/max figures and low variance, that usually also means a large number of hits. Your job as a tuner then is to realise that the neighbouring cells, even if you have not visited them, are just about the same. This is a great tool if used properly. Overall, smooth out your VE table - having it look like that is only going to make any "auto tune" tool have a difficult time getting it right.

Copy the "104" kPa line all the way to the top. Press and hold ctrl on each cell, then arrow up to copy them to cells above it while moving up.