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

I am running MSnsS+Extra 029q with EDIS on a Toyota 4AGE with GSXR 750 ITBs.

I have got the VE table sorted but I am having trouble with AE with either MAPdot or TPSdot it stumbles before picking up. I have using megaLogViewer to see what is happening.

At a constant throttle TPSacc = 100 but when I add throttle to TP value increase but TPSacc jumps wildly to a - value then throws up a massive + value, yet when a take my foot off the throttle it stays at 100 - is this correct and what effect does it have on AE?

I don't get a very stable MAP signal at idle if flicks about from 57 - 63 ish can anyone recommend either MAPdot ot TPSdot for AE and some values to use as start points.

The TPS values seem OK it's the TPSacc that jumps arround and they don't seem to match eg:

If I stand on the throttle TP goes form 0 to 98 and stays there TPSacc goes from 100 to -12, -17, 187, 158.

I have attached a sample log

Thanks again

Neil

I'd reccomend using RPM based AE triggered by the tps. I found a massive improvement over normal AE. There are some great tuning tips posted in a sticky at the top of the MSnS-extra forum under 'help for AE tuning'.

Thanks for that, I am still a little unsure what the TPSacc values are, how they effect the Gammae and why they seem to go against the TP value

The accel enrich and decel (usualy enlean) are implimented in two different ways... But the numbers are usually combined into one data-log reading for TPSaccell. It can get confusing and it seems diferent -extra codes give slightly different readings. At least when I used -extra that was the case.

But basically the Accell is done as a pulse width that is added to the basic fuel pulse.
This can be decayed over time (or number of ignition events... thus RPM dependent) depending on settings. I like the RPM based because it naturally shortens the time AE is on at high rpm where it is needed less.

The deceleration is implimented like any other Gamma... warmup, ego, etc. and CANNOT be used with MAPdot. Because MAPdot often goes negative while accelerating!

This is how the MSII code works and as I recall the +extra code... but with more options.

I personaly like TPS more than MAP but some prefer MAPdot. TPSdot seems more predictable and much less subject to noise.