How to check mass airflow sensor readings via OBD
LLCAR Editorial Team · published
Record the airflow in g/s along with engine speed, load and temperature. Repeat the measurement on the same car under the same operating conditions. The MAF, or mass air flow sensor, shows how much air passes through the intake per second. Comparable records help you understand what to check next.
Start with the codes and any available freeze frame. If Check Engine flashes while the engine is running, the engine shakes severely or power suddenly drops, stop somewhere safe and get help. Open the readings after stopping.
Signs of a problem and code P0101
Is the idle rough, are there hesitations under acceleration, or has Check Engine come on? With P0101, the control unit has found that the airflow data falls outside the expected range or does not agree with the operating conditions. Save the exact code and note when the sign appeared. Depending on the vehicle, check the intake connections, filter seating, connector and wiring, and then the sensor itself following the manufacturer procedure. How to save codes with your phone.
How to make a comparable measurement?
1. Record warm idle
With the car parked outdoors, wait for the engine speed to stabilize. Save the MAF, engine speed, coolant temperature and calculated load. On a repeat run, leave the air conditioning and other electrical accessories in the same state. If you do not have your own history yet, save several such records with the conditions noted. They will give a starting point for comparing future changes.
2. Select segments under load separately
If the car behaves normally and the manual allows driving, use recordings from a regular route. Review them after stopping. Compare segments with similar engine speed, load, temperature and the same fuel-control loop state, if available. In some ECUs the load is calculated using airflow, so a matching load helps select recordings but does not by itself confirm the mass airflow sensor is working correctly.
For comparable records, the raw g/s is usually enough. If you want to compare normalized values, use the formula MAF ÷ RPM × 1 000. For example, 4 g/s at 800 rpm gives 5 g/s normalized per 1 000 rpm. This is a calculated figure. It does not mean the sensor produced 5 g/s at 1 000 rpm, and it does not equalize temperature or load.
3. Check fuel trims and pick a separate test
Save LTFT and STFT for each available bank, plus the codes. If the airflow data, trims and codes disagree, first check the mode and repeatability. If they agree, use the match to choose a test of the intake, power supply, wiring or the sensor signal. Cleaning or replacing the mass airflow sensor should follow the results of such a test and the manufacturer procedure. If the MAF field is empty, check whether the ECU responds and whether it transmits this parameter. How to check communication with the ECU · How to read fuel trims.
| What to record | What the record shows |
|---|---|
| MAF in g/s, engine speed, load, temperature | Helps compare similar segments. A difference between incomparable modes is to be expected. |
| LTFT and STFT of one bank, loop state | Shows how the ECU adjusts fuel delivery. Testing a specific part requires a separate measurement. |
| Code and freeze frame, if available | Helps reconstruct the fault conditions. For P0101, check the intake, electrical circuit and sensor per the manual. |
What the Highlander recordings showed
On 6 November the dirty mass airflow sensor was replaced with a new one. The next day the oil and air filter were changed. The overall average airflow increased after the filter replacement. The difference almost disappeared when the warm-idle recordings were compared at engine speeds from 650 to 700 rpm, coolant temperature from 80 to 85 °C and calculated load from 30 to 35%. The upper boundaries were not included in the sample.
Normalized per 1 000 rpm, the values came to about 5,35 and 5,31 g/s. In the same case, the "−46%" hint compared the normalized airflow against the app's accumulated baseline. The two sets of measurements shown above were selected under the same operating conditions. The Highlander case and its historical baseline.
How LLCAR evaluates airflow
In Android LLCAR AI0.19, open Control → Diagnostic rules. When history is available, separate rules compare the airflow against accumulated recordings at similar engine speed and load. For an unstable baseline, the rules take into account whether the airflow change is consistent with mixture- or code-related signs. There is a separate check for persistently high airflow at warm idle without an accumulated history of normal readings. It needs fresh measurements, a suitable fuel-control mode and an additional sign of enrichment from mixture data or an engine code.
If a hint keeps appearing, save the recording and the conditions when it appeared. With these, a technician can choose a test and reproduce the required mode. What LLCAR shows (in Russian).
Before working on the sensor, save one comparable pair of recordings and the list of codes. That is enough to discuss with a technician, in concrete terms, what to measure next.