maffreq and mafflow are enough, but all the other usual suspects are always useful.
Printable View
maffreq and mafflow are enough, but all the other usual suspects are always useful.
Log file attached to this message. Some BENs in the MAF curve are a bit high or low -- but everything around them makes sense and is close. So I didn't tweak just one cell in the MAF table down before it was showing rich or lean. My assumption is if the MAF curve would get out of whack to dial in air/fuel then that means that there is something else wrong in my tune. I couldn't feel it so I just left it alone.
Any help you can offer is appreciated. I have to work to keep my car above 1K RPM because now that I have the MAF back on, the car wants to stall a lot more.
I had a similiar phase were I could not MAF dialing to make sense. I found that I had to go back and make sure all was closed up from the AutoVE mode then change ONLY this:
Step by step:
0. Assuming a calibrated VE using speed density mode and "AutoVE"...
1. Put the tune in closed loop and all normal PE, etc.
2. Disable LTFT {B3801} and STFT idle trims {B4108}.
<!--[if gte vml 1]><v:shapetype id="_x0000_t75" coordsize="21600,21600" o:spt="75" o:preferrelative="t" path="m@4@5l@4@11@9@11@9@5xe" filled="f" stroked="f"> <v:stroke joinstyle="miter"/> <v:formulas> <v:f eqn="if lineDrawn pixelLineWidth 0"/> <v:f eqn="sum @0 1 0"/> <v:f eqn="sum 0 0 @1"/> <v:f eqn="prod @2 1 2"/> <v:f eqn="prod @3 21600 pixelWidth"/> <v:f eqn="prod @3 21600 pixelHeight"/> <v:f eqn="sum @0 0 1"/> <v:f eqn="prod @6 1 2"/> <v:f eqn="prod @7 21600 pixelWidth"/> <v:f eqn="sum @8 21600 0"/> <v:f eqn="prod @7 21600 pixelHeight"/> <v:f eqn="sum @10 21600 0"/> </v:formulas> <v:path o:extrusionok="f" gradientshapeok="t" o:connecttype="rect"/> <o:lock v:ext="edit" aspectratio="t"/> </v:shapetype><v:shape id="Picture_x0020_1" o:spid="_x0000_i1025" type="#_x0000_t75" alt="http://efiforum.iqd.co.nz/images/smilies/icon_wink.gif" style='width:11.35pt; height:11.35pt;visibility:visible;mso-wrap-style:square'> <v:imagedata src="file:///C:\DOCUME~1\Bruce\LOCALS~1\Temp\msohtmlclip1\01\cl ip_image001.gif" o:title="icon_wink"/> </v:shape><![endif]--><!--[if !vml]--><!--[endif]--> 3. Log a bunch of data - normal driving, wide open (to hit the high Hz, do some bonzai 4th gear 100+ mph runs
4. Save the log file.
5. Filter the throttle transients out using the BEN filter.
6. Copy and paste the MAF map as a factor into your MAF table in the tune.
7. Repeat steps 3 through 6 and you'll have the MAF dialed.
My MAF is dialed in to within 1% from 2375 Hz to 11k+.
Then it all came together as it should. Make sure you have the right MAF table for your car.
If you want to tune the MAF rapidly without having to worry about any input from the VE table, set parameter B0120 = 0 or 200 or some very low RPM. Any rpm point above that parameter value will result in using the MAF exclusively for airflow. :cheers:Quote:
Originally Posted by Bruce Melton
Edit: Re-read your post. Closed loop with BEN's does not work, as the O2 sensors will adjust fueling to stoich. You need to remain in open loop and re-enable the MAF, then disable airflow calculations.
raw data, no filtering:
http://static.flickr.com/172/363548621_93f9af2ecf_d.jpg
Z-score based filtering, 2 sigma:
http://static.flickr.com/188/363548615_a0d4896828_d.jpg
Z-score based filtering, 1 sigma:
http://static.flickr.com/120/363548613_7a31161d6b_d.jpg
few things become apparent once you chart your dataset:
1. you need more data, especially in mid/upper range
2. even the simplest statistical filtering works, however, for it to work well, it needs lots of data--look at the topend where data is so scarce it doesn't know what to do with it.
3. you're using BEN's to adjust your MAF table right? that's one way to do this. i prefer to use dynair values mapped onto maffreq scale for this particular calibration. this way ve table and maf table are truly describing the same thing, just in two forms. if you do two tunes, one to adjust ve, and another to adjust maf, that's two separate tunes. they'll be close, but since they operate from two different datasets, they are describing two different tunes really. try my method sometime, maybe it will work better for you.
i'll try to port this method to calc pids, right now it's in excel, cause it's simple to prototype things this way. i can post the spreadsheet if you're interested, as this was actually much harder to do in excel than i originally thought, so there's some really useful tricks in there.
hope this helps,
Marcin
Marcin,
That's a good bit of research you have done... :cheers:
The raw data shows more scattering in the upper range...would I be right in saying that the MAF is not as consistent in the upper range, or is this due to something else...?
Yes, please post the spreadsheet, that would be great.
Cheers,
Joe
:cheers:
5.7 Hemi's run speed density only.
If its good enough for them .....
:muahaha: :DQuote:
Originally Posted by ringram
Yep, never have to worry about a failed MAF... :D
You'd think it must answer the question (as does the HSV GTS) about the effects of weather and altitude change. Australia, like the US can experience a wide range of extremes...