Right, I don't understand this, so if anyone could help it would be great.

My understanding is TPSacc in MLV shows me the AE pulses, why is AE kicking in here when my TPSdot is 0.0 and doesn't change? Doing my head in, look how it messes with my AFRs! Even the bigger first spike after the little hiccup on TPSdot shouldn't be there because my TPSdot threshold is 40.0 and that little lump is under 30.0.

Confused.

 

It is possible that there was an acceleration event between the two datalogging samples.

 

But surely that would show up where the longer AE pulse is? It spans more than a single log event and at no point is the TPSDOT value higher than the threshold?

 

It's kicking in and you're not seeing why as you're getting noise spikes in the TPS signal which the slow logging rate of the MS isn't picking up.

Robs on MSExtra and Jason on here are both helping to develop improved code which cuts out the noise without introducing lag into the input (which is what the already there code does - called LAG factors)

 

Roger roger.

So, what you're telling me is my threshold is too low, if I increase it the noise will no longer trigger the AE.

That correct?

 

Yes, BUT that'll mean AE won't trigger when you want it to!

 

mapdot?

 

Are you suggesting trying it, or suggesting it as a cause? Currently disabled.

 

disabled, but what is the threshold set to?

 

1000kpa/s

 

weird. mine only spins to 999 on the ms3.

as reverent said, it could definitely be a bump between datapoints. the MS has an issue where it uses even the smallest tps change due to voltage fluctuations to calculate tpsdot (say a TPS value is on the verge of two bit values and flips back and forth) and it can lead to very high tpsdot values over a very short period. like 10ms.

some recent firmware changes have introduced a filter for tpsdot and mapdot that eliminate those spikes. not sure if it was put into ms2 as well as ms3.

anyway, it may be related.