- Thu Aug 04, 2022 7:16 am
#57998
I was looking through my logs last evening, trying to collect data to better tune my TPSdot based AE, but I noticed some inconsistencies in its behaviour.
TS logs data at around 15Hz (one sample every 0,066s), and I was checking how much my throttle can move in one single sample.
Note that my TPS has ZERO noise, I have my AE threshold set to 0 and have absolutely NO false triggering, but my engine (1.6 Mx-5 NA) is really sensitive to small, low-throttle transients, spiking lean if AE does not come into play to keep AFRs in range.
I could see in the logs TPS moving from 0 to 3% from one sample to another (3% / 0,066s = 45%/s TPSdot) and triggering AE, and then later moving from 2 to 5% again in one sample: this should give the same TPSdot, but AE is not triggered.
Maybe I'm not grasping how AE and TPSdot work, but I can't understand the point of coverting TPS movement to %/s instead of just using "deltaTPS" between one ADC sample and the previous value.
This would give the same resolution, but be sensitive to every small movement of the throttle (that one can filter out with the threshold if not needed) and have a defined range (0-100%/sample).
Would it be possible to add a "Delta TPS" AE mode to the existing TPSdot and MAPdot ones?
It would retain the same options (threshold, RPM taper, cold enrichment and taper...) but save some calculations since converting to %/s would not be needed.
I don't know if TPSdot calculations and %/s based AE are used for some sort of compatibility among different hardware/boards, but since AE must be individually tuned on each car anyway, I find some simpler approach would be helpful.
Another nice feature would be "Tip-in AE", that adds a little more enrichment when moving from 0% TPS, since some engines are prone to swinging lean in this situation.
Thanks!
TS logs data at around 15Hz (one sample every 0,066s), and I was checking how much my throttle can move in one single sample.
Note that my TPS has ZERO noise, I have my AE threshold set to 0 and have absolutely NO false triggering, but my engine (1.6 Mx-5 NA) is really sensitive to small, low-throttle transients, spiking lean if AE does not come into play to keep AFRs in range.
I could see in the logs TPS moving from 0 to 3% from one sample to another (3% / 0,066s = 45%/s TPSdot) and triggering AE, and then later moving from 2 to 5% again in one sample: this should give the same TPSdot, but AE is not triggered.
Maybe I'm not grasping how AE and TPSdot work, but I can't understand the point of coverting TPS movement to %/s instead of just using "deltaTPS" between one ADC sample and the previous value.
This would give the same resolution, but be sensitive to every small movement of the throttle (that one can filter out with the threshold if not needed) and have a defined range (0-100%/sample).
Would it be possible to add a "Delta TPS" AE mode to the existing TPSdot and MAPdot ones?
It would retain the same options (threshold, RPM taper, cold enrichment and taper...) but save some calculations since converting to %/s would not be needed.
I don't know if TPSdot calculations and %/s based AE are used for some sort of compatibility among different hardware/boards, but since AE must be individually tuned on each car anyway, I find some simpler approach would be helpful.
Another nice feature would be "Tip-in AE", that adds a little more enrichment when moving from 0% TPS, since some engines are prone to swinging lean in this situation.
Thanks!
1997 BRG EU-Spec 1.6L MX-5 from Italy