MLV autotune feature

[Yves]

A question : I'm currently installing one WB per cyl. This is going to mean that I have no WB per bank anymore. What does MLV look at to tune the fuel ?

[LT401Vette]

MLV by default uses the AFR or AFR1 for AFR.
However, you can select what channel to use in the Advanced side of the VE Analyze dialog.

So if you have a WB in each cyl, you would want to create a new AFR Calculated field that represents the average of all your WB sensors.
Add up all the active AFR channels, then divide by the number of sensors.

Then in the Advanced side of the dialog, set VE Analyze to use the new Calculated Field.

You would also want to do the same thing for your egoCorrection.


BTW, TunerStudio's VEAL takes care of this for you.

[Yves]

MLV by default uses the AFR or AFR1 for AFR.
However, you can select what channel to use in the Advanced side of the VE Analyze dialog.

So if you have a WB in each cyl, you would want to create a new AFR Calculated field that represents the average of all your WB sensors.
Add up all the active AFR channels, then divide by the number of sensors.

Then in the Advanced side of the dialog, set VE Analyze to use the new Calculated Field.

You would also want to do the same thing for your egoCorrection.


BTW, TunerStudio's VEAL takes care of this for you.

I thought that it was possible to have EGO correction on each individual WB ?

As for autotune. I haven't had much luck with it so far. For some reason the VE analyse function in MLV Always gave better results.

[Speedy_G]

As for autotune. I haven't had much luck with it so far. For some reason the VE analyse function in MLV Always gave better results.

Same for me.
Sometimes i'm driving very long a operating point (~same rpm and load) but Autotune does just nothing.
No Filter and even Easy or Very Easy.

Then i load the datalog into VE-Analyser and he does the right thing with same filters.

Because of this, I use the autotune only for the very first rides to get a working table. But then everything via VE Analyser from the datalog. Its faster and better somehow.

[LT401Vette]

Interesting.
Can you send / post an msq of your setup?
It would be good to see if there is a reason, perhaps something about your configuration is not supported properly.

[Yves]

Here you go.

[Yves]

Does veal in TS have the same issue ?

[LT401Vette]

Which issue? The original multiple widebands?

TS handles the WB per cyl.

[Yves]

Which issue? The original multiple widebands?

TS handles the WB per cyl.

VEAL in MLV uses either AFR 1 or AFR 2. What does TS use when using autotune, also AFR 1 or AFR 2 ?
I don't see an option to change it to something else, like can be done in MLV.
Or does it take all 8 values and averages them ?

[LT401Vette]

For MS3, TS looks at the number of sensors set in AFR / EGO Control, then uses AFR1-n / n
So yes the average.

Same for egoCorrection

[LT401Vette]

However, it should be noted, that is how TS works now, it didn't always.
It used to be you would have to do custom ini work for the averaging to work.

[Yves]

Ok, Phil, that answers my question that the option is still usable.

However I find it odd that EGO correction would work on an average. With one WB per cyl it would be too hard to get individual ego per cyl. Also in TS, you have to option to attach a WB to one cyl. Why would you do that if the ecu does ego based on an average. That would defeat the option of WB's except for engine stability sake.

[LT401Vette]

MS3 uses 1 egoCorrection per O2 sensor, not averaging.

It is during VE Analyze that I use the average egoCorrection of all attached O2 sensors as only one table is being updated for all cylinders.
Then with Trim Table Autotune, a single WB and egoCorrection are used.

[Yves]

MS3 uses 1 egoCorrection per O2 sensor, not averaging.

It is during VE Analyze that I use the average egoCorrection of all attached O2 sensors as only one table is being updated for all cylinders.
Then with Trim Table Autotune, a single WB and egoCorrection are used.

OK, thanks. Great.

[Yves]

did some further testing and it seems that the trim autotune doesn't work well when ego correction is on as well. I'm going to start a new thread in the TS section as that is more appropriate.