This is what my MAP, MAPDOT, Tps, and tpsDOT look like with the oversampling turned on, lag factors at 100%! Tested a prerelease version without the extra tpsDOT smoothing- as smooth as it may look now, it will get even smoother!
Adaptive PID reduction allows us to define a zone above and below target, within which a reduction factor is applies to the values of P, I, and D. This factor is set in a 2x5 curve. This allows the user to set aggressive PID values for a strong response far from target, but ramp it down as target is approached. Works very well in combination with AIA. The working theory is that when near target RPM, the idle valve response is too coarse and too slow, and tends to cause small oscillations. So it's better kept relatively quiet, letting Adaptive Idle Advance do the fine tuning.
For those clamoring for an absolute dead zone, you can do just that!
Another nice feature is you can set it up to have an asymmetric response, more aggressive below target.
This log shows the effect of running 0 reduction factor- valve is much quieter than without. Sorry, the small movements are from my voltage correction, it should be even flatter. I am also running a rather small window size, maybe it should be larger fore more transition/ramp.
Status 5 indicates the value of P (so we can log Adaptive PID Reduction)- for the 50%, you see that the value of P (40) is reduced to 20 (at the bottom of the V). For the reduction factor of zero, we actually end up with a P value of zero at target! The width of the V and the clustering of the dots at the valley show how closely the RPMs stick to target. The red line up top shows no PID reduction applied.
Another small but nice improvement is the separation of the battery v from the temperature sensor filters (MAT & CLT). This lets me use heavier smoothing on CLT and MAT, and less on the battery voltage (for less lag and marginally faster --every bit helps-- voltage correction response.)