Engine-management systems need a way to relate the engine's operating conditions to the fuel and ignition calibration. Manifold pressure, throttle position and measured air mass are different inputs to that process. The choice of table axis is not necessarily the same as the complete air-charge calculation: individual ECUs combine inputs and corrections in different ways.
Pressure-based load and speed density
A pressure-based table commonly uses manifold absolute pressure (MAP) and engine speed. In a speed-density fuel model, pressure and intake temperature help estimate air density; a calibrated efficiency value relates the available volume to the air entering the cylinders. For example, MoTeC describes an engine-load calculation using engine efficiency, displacement, cylinder count, manifold pressure and manifold temperature. MoTeC: engine efficiency and load model
MAP is absolute pressure: an engine stopped with the ignition on should normally read approximately local atmospheric pressure, not zero. Compare like units and pressure references when diagnosing a sensor. Sensor plumbing, calibration and the ECU's temperature measurement affect the model.
Throttle-based load (Alpha-N)
Alpha-N uses throttle position and engine speed as primary table coordinates. It can provide useful resolution when manifold pressure is highly pulsating or changes little over much of the useful throttle range. Throttle angle by itself does not directly measure the mass of air entering the engine. Changes in atmospheric pressure, temperature or boost may require additional measurements and corrections, depending on the ECU and installation.
The same controller can still use a MAP sensor for other functions even when the primary table is throttle based. MoTeC's M84 documentation gives specific MAP and throttle arrangements for its own system; these should not be assumed to apply to every ECU. MoTeC M84 user manual: load sensing
MAF and combined strategies
A mass-airflow sensor measures air passing the sensor, rather than using throttle angle as a proxy. Its signal still needs the correct sensor transfer calibration, and measured intake flow does not necessarily equal cylinder flow instantaneously during rapid transients. Some systems use more than one air-charge model, sensor or efficiency table; their blending, backup and fault behaviour are firmware-specific. MoTeC documents an example with both throttle- and manifold-pressure-based efficiency tables. MoTeC GPR Motorcycle: engine efficiency tables
Choosing and checking a strategy
- Identify the ECU, firmware and supported fuel models; read the instructions for how each table axis, compensation and sensor input is used.
- Inspect the intake arrangement and log stable MAP and throttle readings over the usable range. Choose a strategy that gives useful resolution with the actual sensors and installation.
- Verify sensor calibration and plausibility, injector data, ignition timing and fuel pressure before adjusting the fuel model. Do not treat a change in load strategy as a conversion of an existing tune; its values and corrections may no longer have the same meaning.
- Validate the new calibration progressively with a suitable wideband and controlled load. Monitor engine temperature, fuel pressure and abnormal combustion, and reduce load if conditions become unsafe. Haltech: applying load to the engine
See also Standalone ECU fuel tuning guide, Airflow sensors and Individual throttle bodies.