What a MAF gives you
Instead of estimating airflow from manifold pressure and a volumetric efficiency table, a mass air flow sensor measures it directly. A Nexus ECU can take up to two MAF sensors, which is handy on engines with split intake tracts.
When the MAF is your fuel load type, set the tuning method to Mass Air Flow. With a good sensor calibration, the Fuel Base table gets filled with 1.000 across the board, and the mixture you want goes in the Lambda Target table. Fuel Base then only exists to correct spots where the calibration curve isn't quite right. Confirm everything against a wideband O2 sensor.
Grams per second is the raw flow through the sensor, and it climbs with RPM even at a steady load. Grams per cylinder spreads that flow across the intake events, so it reads like engine load. That's the one to build fuel maps against.
Setting it up in NSP, node by node
Wiring configuration
Turn on the MAF inputs you're using (enable Mass Air Flow 2 only if a second sensor is fitted), then choose the signal type for each:
- Analogue - Voltage for 0-5V sensors, which covers hot-wire MAFs and older flap-type meters.
- Digital - Frequency for sensors whose output frequency rises with airflow, as used by Mitsubishi and some GM vehicles.
Mass Air Flow Sensor 1/2
This is where the calibration curve lives. Haltech supplies curves for common sensors, and you bring one in with Load from File. If your sensor isn't covered, build the curve from the manufacturer's flow data. Remember that a calibration only holds true for the housing diameter it was made in.
Display
Sets the top of the MAF scale used across the user interface. It changes how gauges read, not how the ECU fuels.
Diagnostics
You can enable high and low voltage (or frequency) DTCs for each sensor, which catch wiring faults like a short or an open circuit. There's also an out-of-range check that watches the combined airflow and flags a DTC if it stays above or below your thresholds for a set time. That's how you catch excess flow through the sensors, or a lack of flow. Each check can have a DTC severity so Engine Protection can step in.
The two tables people skip
Filter
The filter smooths the MAF signal before the ECU uses it. The value is a time constant: the time it takes the filtered reading to move 63% of the way from the old value to a new one.
- More filtering: a steadier number, but it lags behind real airflow changes.
- Less filtering: quicker response, but noise gets through to the fuel calculation.
Our advice matches the general rule: leave it alone unless the MAF reading is genuinely erratic in normal driving. And before adding filtering, check for the usual causes of a noisy signal, like turbulence near a bend or a poor ground.
MAF Limit
This table puts a ceiling on the airflow value, usually against engine RPM. The classic use is low-RPM throttle snaps: slam the throttle at 1500 RPM and a MAF can briefly report far more air than the engine could actually ingest at that speed. Clipping that spike keeps the ECU from fueling for air that isn't really there. Set the limit a comfortable margin above what you log in real full-load running, so it only trims the spikes.
Troubleshooting
| Symptom | Usually |
|---|---|
| Mixture hiccup on sudden throttle at low RPM | Airflow spike that the MAF Limit table should clip |
| Airflow reading jumps around at steady load | Turbulent mounting position or grounding. Adjust the filter only after ruling those out |
| Fueling lags on throttle changes | Filter set higher than it needs to be |
| Consistently rich or lean | Calibration doesn't match the sensor or its housing |
On an Elite ECU instead? The ESP version is covered in our Elite mass airflow sensor guide. For deciding between MAF and speed density on your build, book a free consultation.
