Alpha-N / MSTweak3000

Mike Bonkalski · Post by **Mike Bonkalski** » Mon Sep 05, 2005 1:07 pm

I have my idle dialed in after changing from SD to AN.

Now, I took it out for a drive to get a log to enter into MSTweak to start tuning my VE table.

I set everything up according to the suggestions in the MSTweak instuctions to create a good datalog and I loaded the log into MSTweak and it found crossover points, however it won't associate those points with the TPS, only the MAP values.

I tried to select AN, under the 'Settings', but it keeps reading MAP. Is there a solution to this that I am overlooking?

nobogart · Post by **nobogart** » Wed Oct 12, 2005 3:46 am

i would be interested in this as well.

440fish · Post by **440fish** » Sun Oct 23, 2005 8:31 pm

Any help?

milesinfront · Post by **milesinfront** » Mon Mar 06, 2006 2:04 am

I'm putting my hand up for some info here too! Can MSTweek really be used for Alpha-N tuning???

Post by **efahl** » Mon Mar 06, 2006 7:14 am

milesinfront wrote:I'm putting my hand up for some info here too! Can MSTweek really be used for Alpha-N tuning???

Should work fine. I assume it doesn't care what units are used on the "load" axis, so it should work equally well for AN, SD or MAF...

Eric

milesinfront · Post by **milesinfront** » Mon Mar 06, 2006 11:25 am

Cheers! I'll give it a wirl...

Also, what do the VE numbers mean in AN mode? e.g. in SD they are roughly %VE, what are they in AN, if anything at all.....

for example:- In SD my car was idling at about 30%VE, now in AN it's like 16 or 17.... What does the 16 mean?

MS1 - 029b - MT2.25