Miata Turbo Forum - Boost cars, acquire cats.

Miata Turbo Forum - Boost cars, acquire cats. (https://www.miataturbo.net/)
-   MEGAsquirt (https://www.miataturbo.net/megasquirt-18/)
-   -   Autotune troubles (https://www.miataturbo.net/megasquirt-18/autotune-troubles-17110/)

ryry 02-16-2008 01:47 AM

Autotune troubles
 
I can't get autotune to work.

From my custom .ini:

__________________________________________________ _____________
[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, 7000 ; RPM
yLimits = 40, 255 ; MAP
zLimits = 10, 200 ; VE

; Vertex tolerance parameters
; How close you must be to a vertex before tuning takes place.
xRadius = 400 ; RPM
yRadius = 10 ; 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.

#elif MS_II
table = veTable1Map
allowAutoTune = on
corrector = egoCorrection1
xLimits = 1500, 4000
yLimits = 60, 90
zLimits = 10, 200
xRadius = 200
yRadius = 7
initialStartupInterval = 1.0
updateInterval = 1.0
proportionalGain = 0.5
lumpiness = 5

table = veTable2Map
allowAutoTune = on
corrector = egoCorrection2
xLimits = 1500, 4000
yLimits = 60, 90
zLimits = 10, 200
xRadius = 200
yRadius = 7
initialStartupInterval = 1.0
updateInterval = 1.0
proportionalGain = 0.5
lumpiness = 5

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

table = veTable2Map
allowAutoTune = on
corrector = egoCorrection
xLimits = 1500, 5000
yLimits = 20, 100
zLimits = 10, 200
xRadius = 200
yRadius = 7
initialStartupInterval = 1.0
updateInterval = 1.0
proportionalGain = 0.5
lumpiness = 5
#endif
__________________________________________________ ______________

EGO settings:
step size=1
authority=10

What could I be missing? I have been datalogging and using Megaviewlogviewer but haven't really gotten anywhere with that?
What's the deal-e-o? yo

patsmx5 02-16-2008 01:51 AM

You have single wideband selected under EGO and have it on?

magnamx-5 02-16-2008 02:03 AM

Hmm do you have the AF table setup? Is it just not changing the cells or is it not engageing at all? You do know that if you have a disconnect while autotuning it will turn off on the reconnect right? The file looks right so give us some more info on the pysicall and some descriptions of what happens vs what you want please.

cjernigan 02-16-2008 02:05 AM

Change this part too:
http://i27.tinypic.com/35it82q.png

From the manual: http://i32.tinypic.com/ngsztg.png

ryry 02-16-2008 04:28 AM


Originally Posted by cjernigan (Post 215144)

What am I not seeing?

The autotune will appear like it is functioning but it always says out of window or not near vertex. When it was saying this before I thought this was because the default ylimits= 60,90. After adjusting those I was sure all would be good to go, but no.

Wide band is set up. AF table is set up. It will not change cells. The closest it will get is it will say 0%. Very frustrating.

turbobluemiata 02-16-2008 04:33 AM

2nd this thread mine does the same thing never goes past 0% complete???? but it seems like it works???? and says the same things you are saying

cjernigan 02-16-2008 07:50 AM


Originally Posted by ryry (Post 215170)
What am I not seeing?

The autotune will appear like it is functioning but it always says out of window or not near vertex. When it was saying this before I thought this was because the default ylimits= 60,90. After adjusting those I was sure all would be good to go, but no.

Wide band is set up. AF table is set up. It will not change cells. The closest it will get is it will say 0%. Very frustrating.

Change the RPM limit in that part as well, it's still at 4000.

ryry 02-16-2008 11:59 AM


Originally Posted by turbobluemiata (Post 215171)
2nd this thread mine does the same thing never goes past 0% complete???? but it seems like it works???? and says the same things you are saying

Hey mine is blue too. I wonder if that's it!

I will try setting the RPM to a higher limit but shouldn't it have been working below 4000 RPM? I had a 15 mile freeway drive home last night where I was definitely below 4000 for most of it.

ryry 02-16-2008 01:16 PM

What do people have for open loop mode settings?

bryantaylor 02-16-2008 01:17 PM

screw autotune


All times are GMT -4. The time now is 05:54 AM.


© 2024 MH Sub I, LLC dba Internet Brands