MAP averaging
#17
EvoM Guru
iTrader: (50)
This might go back to how you thinking of doing averaging. Were you thinking of averaging the MAP sensor reading from each cycle through the ADC routine, or were you perhaps thinking of measuring the MAP sensor several times each time the CPU traverses the ADC routine? Maybe keep the original ADC read, and then add another ADC read in your add-on code. Then for each time through the code, you'd have two reads of the MAP sensor.
#21
You'll certainly need a slower response time and can get away with much more filtering if you use it to control boost rather than for fuelling/timing for transients.
Imagine a standard car at peak power running say 1500Hz on the MAF sensor. With an exponential averaging over 10 ticks then you still have a rate of 150Hz which is quicker than one engine revolution even at the RPM limiter.
For a boost controller I would suggest you want to update it every time the solenoid duty cycle is complete, otherwise you're wasting calculations. On most ECUs I've come across this is about 15Hz, so you do have ample filtering opportunities running it off the slow main loop.
Imagine a standard car at peak power running say 1500Hz on the MAF sensor. With an exponential averaging over 10 ticks then you still have a rate of 150Hz which is quicker than one engine revolution even at the RPM limiter.
For a boost controller I would suggest you want to update it every time the solenoid duty cycle is complete, otherwise you're wasting calculations. On most ECUs I've come across this is about 15Hz, so you do have ample filtering opportunities running it off the slow main loop.
#23
right back on this topic. I hope to include this in my next patch, which will be out soon and have a this, 2byte->1byte load mod, as well as some fixes and cleanups.
so I want to finalise the averaging algorithm so I can release it.
without posting graphs, weighted 5pt, weighted 3pt, and normal 3pt (SUM/3) basically give the same result within a few pt's of a psi.
so in keeping with KISS principle (yes I know MrFred you said it at the beginning lol!)
I think I will just go with a regular 3pt average, ie =(LAST, NOW, NEXT)/3
So we lose one "future" map reading, but at the rate we run the avg routine and get new ADC data I don't think it will matter to the boost routines.
anyone have an objections?
ps the 2nd graph I posted on pg1 was "laggy" because I screwed up the plotting points :P hehe
so I want to finalise the averaging algorithm so I can release it.
without posting graphs, weighted 5pt, weighted 3pt, and normal 3pt (SUM/3) basically give the same result within a few pt's of a psi.
so in keeping with KISS principle (yes I know MrFred you said it at the beginning lol!)
I think I will just go with a regular 3pt average, ie =(LAST, NOW, NEXT)/3
So we lose one "future" map reading, but at the rate we run the avg routine and get new ADC data I don't think it will matter to the boost routines.
anyone have an objections?
ps the 2nd graph I posted on pg1 was "laggy" because I screwed up the plotting points :P hehe
Last edited by tephra; May 24, 2008 at 05:47 AM.
#25
Account Disabled
iTrader: (3)
Join Date: Apr 2006
Location: USA
Posts: 1,029
Likes: 0
Received 0 Likes
on
0 Posts
I believe it is intake manifold harmonics and normal pulsations as well. The intake manifold is pretty much a musical instrument with respect to vibrations.
I for one would like to see the normal jittery map signal and log this. I don't want my boost spike that I'm trying to tune out being lessened by the math. It would also be nice to have the option to turn the map averaging on/off. I'm still unsure if it will help or hurt when tuning the boost but I'd like to have the option to turn it on/off as with the rest of the tephra mods.
Thanks for the great features guys, so far your doing a great job of implementing things people need and with no bugs as far as I can tell.
#26
yes option to enable/disable is in.
problem is that with the boost routines if you happen to run them on the spike (up or down) then the error correction goes haywire and starts changing WGDC needlessly..
also you will still be able to log both real and avg map signal, its just the avg will be used by the boost routines... (if enabled)
problem is that with the boost routines if you happen to run them on the spike (up or down) then the error correction goes haywire and starts changing WGDC needlessly..
also you will still be able to log both real and avg map signal, its just the avg will be used by the boost routines... (if enabled)
Thread
Thread Starter
Forum
Replies
Last Post
simonevo900
Project Cars / Build Threads
44
Jan 21, 2016 11:17 PM
DrivelineSales
Vendor Announcements
16
Jun 20, 2011 04:51 PM