"Auto-tune: Tuning point outside window", Always D

[69 1/2 Six Pack Bee]

I am trying the autotune feature and I have followed the instructions as how to use it and which parameters to set.

The "Auto-tune: Tuning point outside window" is constantly displayed and I am not getting any correction obviously.

I have calibrated my wideband to "Innovate 0-5"in the "tools", in the EGO Control window the Single wideband is selected, the authority is @ 10%, active above 1300, and 160F, below 80%TPS & below 90MAP. and the controller is "simple"

The VE table is not too far off and I have the AFR target set where I think it ought to be.
WHat else could keep the "Autotune" from doing it's job?
Thanx,
Bud

Running MS-I, V2.2 w/daughtercard and V2.35 CAN code.

[grawill]

As I understand it.. (please correct me if I got something wrong)
That message means the green dot (the current RPM/MAP of your motor) is too far away from the cross hairs (where the correction is to be made.)

There are settings inside your ini file to set just how far away from a tune point (where rpm and map bins meet) the green dot can be for a correction to be made at that tune point.

Look in your custom.ini file (inside your car folder of MegaTune)

Code: Select all

[AutoTune]
#if MS_I
   table = veTableMap ; Should be the map3d_id of a TableEditor entry.
      allowAutoTune = on            ; Displays the check box on the specified tuning dialog.
      corrector     = egoCorrection ; Variable used for correction algorithm.

      ; Tuning block parameters
      ;    Global limits on tuning, outside the box and nothing happens.
      xLimits = 1500, 4000 ; RPM
      yLimits =   60,   90 ; MAP
      zLimits =   10,  200 ; VE

      ; Vertex tolerance parameters
      ;   How close you must be to a vertex before tuning takes place.
      xRadius = 200 ; RPM
      yRadius =   7 ; MAP

      ; Controller parameters
      initialStartupInterval = 1.0 ; Seconds before first adjustment
      updateInterval         = 1.0 ; Seconds between each consecutive adjustment.
      proportionalGain       = 0.5 ; Proportion of (100-corrector) to use for adjustment.
      lumpiness              = 5   ; Maximum percent adjustment above or below neighboring VE points.

That is similar to what you would find for MSI (NOT the extra code or MSII)

Make sure allowAutoTune = ON is "on" then go into MegaTune under Tuning - VE Table. You should have a small box to check under the graph. Put a check in that box and you should see the "cross hairs" auto follow the green dot. It will start making corrections depending on what you have set in the ini file from above.

Hope that helps..
Ted

[69 1/2 Six Pack Bee]

I thought the "Autotune" feature was already installed in the latest iterrations of the code. I go into the tuning dropdown menu and click the VE tuning and then I check the autotune box...seems simple enough
The autotune has only changed 2, count 'em,..2 bins in the whole map (Above 60KPA) after driving around for more than an hour this evening.

Is there something I am missing?
Thanx,
Bud

[krisr]

Autotune by default in MT will only tune between 1200-4000rpm and 60-90kpa. You need to modify your custom.ini file to change the 'window'.

Don't let it autotune your idle unless you have reasonable AFR's for idle or you will be chasing your tail... ask me how I know ... do it manually and aim for peak vacuum, also personally i'd tune WOT peak HP runs on the dyno, not on the road/strip. More of a controlled environment etc.

One thing I learnt last night, if you have a large cam with lots of overlap, keep your AFR's reasonable and shoot for economy via spark advance.

[69 1/2 Six Pack Bee]

thanx for the help.

[donjr5]

That custom.ini is in the /mtcfg directory in your particular project folder (car1 or whatever you call yours). Mine was set at a default xLimits=1500,5000 which I changed to 1200, 4500 and yLimits to 20, 100 (I'm not boosted).
I tried the autotune feature for the first time yesterday....It was great.

[efahl]

Is there something I am missing?

Bud,

Sort of. I intentionally set the parameters on the auto-tune to be narrow and fairly useless, just so people will not blindly dive into it thinking it's the solution to the world's problems. I want you to have to think about it a bit and figure out what is good for your motor and then reset the parameters in the custom.ini file specifically for it. This is really impossible to do in a generic fashion, and besides I like the idea of getting the old brain jumpstarted for things like this.

Eric

[MurrayA4]

Eric,
I appreciate your desire to ensure that modifications to the Autotune parameters be made only after some thought /understanding has been given.I figured that the values for:

initialStartupInterval = 1.0 ; Seconds before first adjustment updateInterval = 1.0 ; Seconds between each consecutive adjustment.

were too conservative,1 second is forever,so I tried changing these values to 0.75 sec.-Result Autotune won't start up ? Any clues ?

[efahl]

were too conservative,1 second is forever,so I tried changing these values to 0.75 sec.-Result Autotune won't start up ? Any clues ?

Murray,

Merely changing the time constants shouldn't affect anything, I've done that many times in testing (even set them to zero). Try setting them back and see if that fixes things, I'm guessing something else happened...

Be careful about setting the values too low, you can induce instability in the control algorithm and it will oscillate. Your 0.75 s value is probably quite far away from doing this, but it's something you want to keep an eye on...

Eric

[69 1/2 Six Pack Bee]

Hey, Eric,

I have ben tinkering with the .ini file to tailor it to my specific need. But so far, I am having trouble with my LC-1 (I sent it back Friday to have Innovate look at it) so I cannot start tuning until I get it back in and hooked up.
It is a little difficult to tune a table when the info is skewed

I am not sure that the WBO2 is totally at fault here but I will know where to start looking if it is not the culprit.

I like the Autotune feature to say the least no I am hoping to get it to do what I want
Thanx,
Bud