You're lucky I'm not a mod. I'd totally delete this thread it's so far off topic. It's supposed to be a discussion on the importance of maping the curve accuratley, and when to read it. This 'developing a windows GUI for calibrating sensors' stuff belongs in it's own thread, Mr.Fred wrote:Boy, hasn't this thread gone Off Topic! For the best. Now we have code to generate thermistor tables, a gui to make it easy, and a plan with regards doing the sampling and lookups. Sweet.
(MAP sorta doesn't belong here either, but it's the trickeist. Some averaging is good even on it, but I would almost recommend asynchonos sampling for it, plus averaging. There are standing pressure waves all through the manifold. Where you take your signal, you're going to get (relative to a particular engine rotation/position) an over or under error in the pressure, and this modification will vary with RPM.
You can do this averaging mechanically, with a pressure resivoir, but I think it'd be better to read the map very often, purposefully irregularly, (or at least many times per piston stroke) and average to make something meaningful of it. My father once worked on a project for the dept of defense, and it was all centered around taking samples in a way that was random on the timescale of the events in question so as not to miss resonances or read incorrect data.