Everything there is to know about MegaTune Auto-Tune

[MiseryQ]

Played around with this again today so far no major hiccups.
It will lean the mixture on a long highspeed decel but it was only by -4%.

Have'nt compared tonights VEX with the original but the changed by lunchtime were'nt drastic.

[efahl]

Does autotune ignore data when the AE is active?

Andy,

No, but ego correction goes to 100%, so in effect AE turns the autotune off.

Eric

[efahl]

Go get build 615 and you will be able to change the autotune controller parameters.

This is from the MS-II ini file, the "veTable1Map" must correspond to the table that you wish to modify. The default settings are given here. Stick this in the ini after the TableEditor section, or in the custom.ini to keep it around between updates.

Code: Select all

[AutoTune] ; Users should copy this section to custom.ini to modify it.
   table = veTable1Map ; Should be the map3d_id of a TableEditor entry.
      ; Vertex tolerance parameters
      xRadius = 300
      yRadius =  10

      ; Tuning block parameters
      xLimits = 1000, 8000
      yLimits =   20,  110

      ; Controller parameters
      initialStartupInterval = 1.0
      updateInterval         = 1.0
      proportionalGain       = 0.5

"X" is RPM in all the ini files I've seen, although someone could have swapped them. Y is normally MAP, TP or load. The limit parameters box the tuning points, no changes will be made outside the box. The radius parameters dictate how close the operating point must be to the tuning point for autotune to operate, if the operating point falls outside this smaller box, then no action is taken.

Initial startup is the time in seconds between when the operating point approaches a tuning point and when the first adjustment is made. The update interval is the time between each subsequent adjustment. Proportional gain is how much of the ego correction is used to adjust the VE value. If you set it to 1.0, and the ego correction indicates a 15% error, then the VE will be adjusted by 15%, while gain of 0.5 will adjust VE by 7.5%. I'd suggest keeping this at 0.5 or lower.

[WolfGTI]

Swithching to Build 615 now. - Will post up new log info tomorrow.

[efahl]

I may be getting greedy, but if the autolearn feature could be combined with the AFR target table feature, then the car would almost tune itself.
Any chance of that happaning?

It already does. Your AFR target table drives the EGO correction, which in turn is used to derive the autotune data. Just set the whole table the way you like, start with VE well rich in the high power areas, set the autotune parameters to move fairly slowly, then drive around and do a "burn" occasionally...

[efahl]

now have you thought of a auto tune for the ignition maps? where it +1 degree's until it hits knock then steps back about 2-3 degree's with some form of limiting feature as to how much it can keep playing with a certain area of the map?

i would figure in 1 degree advance steps and 3-4 degree retard steps per knock event once you have a autotuned modified spark map that you should be pretty well covered for maximum for close to maximum efficiency versus engine safety

No, that won't work at all. MBT has nothing to do with the knock limit for 90% of the table (100% of it, if you have sufficiently high octane fuel)... In order to do ignition autotune you'll need ion sensing or a torque transducer or some other feedback device producing a true indicator of what is good timing.

Even tuning to AFR is pretty lame when it comes to finding maximum power. How do know that your engine produces max power at 12.2:1 or 13.2:1 unless you've actually done dyno testing? How do you know it's doing it safely unless you also measure EGTs? All engine designs are different, so pulling a number out of the air and claiming that it's a good one is pretty sketchy.

Eric

[WolfGTI]

Latest Map after run in this morning.

[whittlebeast]

Look at the 50 and 60 KPA lines at low rpm.....Is that possible that that is the correct answer. Or is that a missfire feading raw fuel into the exhaust confusing the 02 .... or some other obscure answer. Just thinking out loud

I found lots of these type things when I went from Alpha-N to MAF

AW

[WolfGTI]

Look at the 50 and 60 KPA lines at low rpm.....Is that possible that that is the correct answer. Or is that a missfire feading raw fuel into the exhaust confusing the 02 .... or some other obscure answer. Just thinking out loud

I found lots of these type things when I went from Alpha-N to MAF

AW

Could it be the stumble from the AE, I switched the AE on now - the car has a stumble when the gas is pressed - works flawlessly when the car is dead cold (this morning @ 60F) then the stumble came in as it warmed up.

[efahl]

Latest Map after run in this morning.

Still lookin' kind of lumpy... What's that 39 doing in the lower left?