MicroSquirt.com read only forum (Jan.15,2018)

I am running msns-e 029q with megatune v2.25 on a v3 main board.

The car…my 5.0l twin turbo mustang with mods as seen in my sig below.

Alright...i'm having problems tuning my accel enrichment using the tps. It seems that no matter what I do, I cannot get it to rev smoothly. Actually...I can get it to rev smoothly at ide by increasing the accel time to .4 This lets you rev smoothly in neutral but is udderly impossible to drive that way.

Sooo...I went ahead and switched my setting for the AE back to default and took a datalog of it.

Any and all help to point me in the right direction would be appreciated.

Looking at your log, your pulsewidth spikes everytime your AE in activated. Try making the accel time 1.0 and lower the fuel amount.

qadir03 wrote:Looking at your log, your pulsewidth spikes everytime your AE in activated. Try making the accel time 1.0 and lower the fuel amount.

Yep...I used .4 and lowered the fuel amounts and it started to rev MUCH smoother. The problem then was that apparantly tpsdot enrichment is not boost friendly. I'm not really giving up yet on the tpsdot yet...but just trying new things.

I have my msq now saved for that portion...and am now moving on to a new msq with mapdot.

With the setting in my attached msq file it rev's just ok. It's good enough to drive around...but it seems that I'm doing a whole lot of guessing which I hate to do. Also it appears that I have a negative spike with my pw and duty cycle. I'm trying to figure out if this is normal...and if not, what is causing it.

Once again, any and all input would be greatly appreciated.

Edit: Updated with the correct msq

The negative pulsewidth spike it from your AE turning off. You should try the AE decay feature and set the accel value at end of accel to 0. This should smoothen that out for you. I would try getting the hang of Tps dot first. You should be able to tune it with your setup. Again try increasing the accel time to 1.0. and start changing your fuel amount. If you are setting AE from idle, some engines like a richer idle for better throttle response.

Gotcha...I'll give the decay a try.

As far as tpsdot goes...after doing some lengthy reading it sounds as if mapdot is more ideal for turbo apps than tps. Is there truth in this...or does each have their goods and bad for turbo apps?

Map dot works great if you have a really large throttle body or itbs. This is due to the fact that mapdot reacts faster than tps dot. If you look the the logs closely you will see that as soon as you hit the trottle, the mapdot reacts quicker than tps dot. This can help reduce lean spikes during AE. I am using tps dot on 2 turbo cars and they seam to work great. You should focus on using one type of AE function either map dot or tps dot. Playing with both at the same with will confuse you.

qadir03 wrote:Map dot works great if you have a really large throttle body or itbs. This is due to the fact that mapdot reacts faster than tps dot. If you look the the logs closely you will see that as soon as you hit the trottle, the mapdot reacts quicker than tps dot. This can help reduce lean spikes during AE. I am using tps dot on 2 turbo cars and they seam to work great. You should focus on using one type of AE function either map dot or tps dot. Playing with both at the same with will confuse you.

Yes...confusion is no good lol.

As far as the accel time goes....whose to say 1.0 is to much? Will my fuel numbers be way to low to allow smooth accelation?

1.0 is just a number to emphasive increasing accel time, give it a try and change it according to your engine's need

Well, I went ahead and took your advice. I started with an accel time of 1 and ended upping it to 2. The reason being is that after getting it running fairly well, I still had and issue trying to get a slow accel stumble to go away. I've tried decreasing my v/s down all the way down to .1. Nothing really worked.

Also...is there a RELIABLE way to know which v/s needs to be changed? Same goes for the m/s values. Currently I'm guestimating based off the quickness that I accelerate. It seems to work o/k for the faster values, but the slower ones are mouch tougher to figure out.

Anyways, here are a few quick datalogs along with my new new msq.

One more...