Page 1 of 1

EGO settings - authority, step size, etc

Posted: Fri Sep 01, 2006 10:21 am
by Jon k
I think I want to turn on AFR targets and I got a map for the AFR Table, now I just need to know appropriate figures for these.

I have my engine idling ~950 - 1000 so I set the active above to 1300 rpm.

Also, what does switch point do?

After I set these figures up, I enable AFR Target for VE 1, do I just turn on autotune at this point and burn the table every few minutes?

Posted: Sun Sep 03, 2006 1:00 am
by daxtojeiro
If you have a wideband lambda then you can use the Target AFR table, the ego switch point does nothing if you use the table. You can use Autotune as long as you have an authority of around 15-20 and a step size greater than Zero , (1 is best) as it will follow the ego correction and adjust the VE table from that, but it is only a fine tune, youll need to go steady and go through your datalogs to see if your going weak still

Phil

Posted: Sun Sep 03, 2006 1:06 am
by Jon k
daxtojeiro wrote:If you have a wideband lambda then you can use the Target AFR table, the ego switch point does nothing if you use the table. You can use Autotune as long as you have an authority of around 15-20 and a step size greater than Zero , (1 is best) as it will follow the ego correction and adjust the VE table from that, but it is only a fine tune, youll need to go steady and go through your datalogs to see if your going weak still

Phil
I turned it on and cruised with it and noticed that my AFR reading swing more than when running off the table alone. Normal? I have my authority of 15% so when cruising it say EGO correction 85%... meaning I guess I am too rich?

Also - when I turned on autotune, it made some changes but said a lot of "out side of window". What gives?

Posted: Sun Sep 03, 2006 10:31 pm
by daxtojeiro
I would guess they are swinging due to the map still being out, Id do some datalogs and go through it with VEXME, but if you want to use Autotune then you can change its "Window" in the "custom.ini" file of Megatune, but you need to look for this part as this is for MSnS_Extra, the first Autotune you come accross is for MS1 in the file,

#else ; Actually only good for DualTable and MSnS-Extra.
table = veTable1Map
allowAutoTune = on
corrector = egoCorrection
xLimits = 1500, 4000
yLimits = 60, 90
zLimits = 10, 200
xRadius = 200
yRadius = 7
initialStartupInterval = 1.0
updateInterval = 1.0
proportionalGain = 0.5
lumpiness = 5