<TABLE BORDER=0 ALIGN=CENTER WIDTH=85%><TR><TD><font size=-1>Quote:</font><HR></TD></TR><TR><TD><FONT SIZE=-1><BLOCKQUOTE>
I don't understand the big picture of how all the elements work together, so I can't say if you have a big enough lookup table or enough bits of resolution in the table. If what you are doing gives optimal output as measured on a dyno with wideband 02, etc., then you're good enough :wink: .
</BLOCKQUOTE></FONT></TD></TR><TR><TD><HR></TD></TR></TABLE>
Yes, the dyno results that we're getting are totally awesome. Very precise control of air-fuel over the entire rpm range (on many different vehicles). Feedback from a wide-band and a scan-tool on both a chassis dyno and the open road verify our results.
<TABLE BORDER=0 ALIGN=CENTER WIDTH=85%><TR><TD><font size=-1>Quote:</font><HR></TD></TR><TR><TD><FONT SIZE=-1><BLOCKQUOTE>
As for GUI editing with curves, if you have say 50 sliders, and the end result always looks fairly smooth (slider positions don't have discontinuities), then you could use far less controls, and allow moving of curve control points with tangent handles. This would also allow you to abstract (hide) the internal rep of you algorithm(s). Also, it would allow you to change table length and never have to change the UI (it will then be table resolution independent). Thus, you start out with a straight line, then as you click on the line, a new control point is created. You move it up and down, adjust the tangent curve, and click again precisely where you need to make a change, and edit again. Should be very fast and easy to use...
</BLOCKQUOTE></FONT></TD></TR><TR><TD><HR></TD></TR></TABLE>
OK, I understand now. Sounds like interesting concepts.
<TABLE BORDER=0 ALIGN=CENTER WIDTH=85%><TR><TD><font size=-1>Quote:</font><HR></TD></TR><TR><TD><FONT SIZE=-1><BLOCKQUOTE>
Are you saying that your system effectively increases the resolution of the adaptability of the MAF sensor to flow conditions? It seems to me the optimal solution is to get the Ford computer's tables optimized as much as possible, or chuck the Ford computer for a programmable aftermarket control system (if they exist). Maybe something off an F1 car :wink: .
</BLOCKQUOTE></FONT></TD></TR><TR><TD><HR></TD></TR></TABLE>
You can't really do better resolution-wise with the Ford tables in the picture. They act as sort of a crude filter. Very few bins.
<TABLE BORDER=0 ALIGN=CENTER WIDTH=85%><TR><TD><font size=-1>Quote:</font><HR></TD></TR><TR><TD><FONT SIZE=-1><BLOCKQUOTE>
Fourth order transfer function (quartic): Why?
</BLOCKQUOTE></FONT></TD></TR><TR><TD><HR></TD></TR></TABLE>
Physical properties of the sensor itself. In a nutshell, a platinum resistor is heated and the rate of cooling is measured and compared with another (unheated) platinum resistor. There is effectively a square-law relationship between voltage and power and another square-law relationship between electrical power put into the resistor and mass-air flow that it takes to cool it. Hence the fourth order relationship. For more information, check out
www.pro-flow.com and read their tech section. It's pretty comprehensive.
<TABLE BORDER=0 ALIGN=CENTER WIDTH=85%><TR><TD><font size=-1>Quote:</font><HR></TD></TR><TR><TD><FONT SIZE=-1><BLOCKQUOTE>
Perhaps I'm misunderstaning something, but if they are using a small lerp'd table, why would they bother with a quartic elsewhere? Seems like you could get way better results with an interpolating cubic and a lookup table (define just about any smooth function you want, without the wiggle problems of a quartic). Memory is cheap... Am I missing something?
</BLOCKQUOTE></FONT></TD></TR><TR><TD><HR></TD></TR></TABLE>
See above. Thanks for the interesting conversation!
Mark Chiappetta
Zone-5 Performance Products