Tuning Wiki

This is a historical revision. Read the current page or return to its history.

Page organisation in this revision
Page type
Technical article
Subject
Diagnostics
Parent
Section level
Applies to
No ECU-specific applicability
Tool groups
None
Manufacturers
None

See also testing a lambda sensor with propane enrichment for a controlled rich-response check, interpretation and workshop precautions.

Fuel trims show how much an engine control unit (ECU) is correcting its calculated fuel delivery in response to exhaust oxygen feedback. They are useful diagnostic clues even when no fault code is stored. This guide focuses on closed-loop petrol engines; diesel, lean-burn and some direct-injection strategies use different controls and displays.

How the feedback loop works

The ECU calculates a base fuel quantity from measured or estimated air and operating conditions. When the system enters closed loop, it compares exhaust sensor feedback with the commanded mixture and adjusts fuelling. For conventional petrol at stoichiometry, lambda is 1; the familiar approximately 14.7:1 air-to-fuel ratio is an approximation and changes with fuel composition. Other operating conditions may call for a different mixture.

Closed-loop fuel control: ECU calculates fuel, injectors supply the engine, the upstream lambda sensor measures exhaust oxygen, and feedback returns to the ECU.

Original illustration created for Tuning Wiki.

1. Calculate2. Deliver3. Measure4. Correct
Air, speed, temperature and load → base fuelInjectors deliver fuel → combustionUpstream lambda sensor measures exhaust oxygenECU compares feedback with target → adjusts fuel and repeats

Diagram: simplified closed-loop fuel control. The exact inputs and control strategy depend on the vehicle. US EPA: fuel system trim and feedback.

Short-term and long-term trim

  • Short-term fuel trim (STFT) is the faster feedback correction. It changes as the ECU responds to the sensor and operating conditions.
  • Long-term fuel trim (LTFT) is a learned correction that can take over a persistent adjustment, leaving STFT room to respond. Some ECUs learn separate corrections for idle, part load and other operating regions.
DisplayWhat the ECU is doingWhat it suggests
Positive percentageAdding fuel relative to its base calculationFeedback indicates a lean tendency, or feedback is misleading
Negative percentageRemoving fuel relative to its base calculationFeedback indicates a rich tendency, or feedback is misleading
Near zeroLittle indicated correction for that value at that momentCheck loop status and both trims; a zero or inactive STFT does not prove the system is healthy

Read fuel-system status alongside the trims. During open-loop operation, such as some cold-start, fault or high-load conditions, the displayed STFT may be inactive, fixed or otherwise not a live closed-loop correction. Some ECUs still apply learned corrections in open loop; behaviour varies. A recently reset LTFT near zero also does not establish that the underlying fault is fixed.

Some manufacturer-specific data uses a multiplier or a different name instead of a percentage: for example, 1.00 may mean no correction. Do not confuse that correction factor with lambda 1.00. Check the data definition for the vehicle. Manufacturer explanation of fuel corrections and learning.

On systems where the manufacturer specifies it, STFT and LTFT for the same bank can be added as a useful approximate indication of total correction. For example, +12% LTFT and −3% STFT suggest approximately +9% overall. It is a diagnostic approximation, not a universal formula for exact injector pulse width. A small STFT alone can hide a large learned LTFT. Compare with the manufacturer's method, limits and conditions.

Give each steady operating point time to settle and record STFT and LTFT together. An LTFT change between idle and part load may reflect a switch to another learned cell rather than an immediate change in the fault. Keep the vehicle, bank, temperature, loop status and PID definition consistent when comparing readings. Manufacturer explanation of idle and part-load adaptations.

Reading the pattern

Illustrative trim patterns: positive trim improving at raised rpm, positive trim persisting under load, and negative trim at two operating points.

Original illustration created for Tuning Wiki. The points are examples, not diagnostic limits; several faults can produce similar patterns.

Observed patternPossible direction for testing
Positive at warm idle, closer to zero at a steady raised speedInvestigate an intake or crankcase ventilation leak; airflow measurement and other faults can produce similar results.
Positive at idle and under load, or increasingly positive under loadCheck fuel delivery and pressure under the specified conditions, air measurement, injectors and exhaust leaks. A stationary raised-speed test is not a substitute for a load test.
Negative in several operating regionsInvestigate excess fuel, purge flow, fuel pressure, injector leakage or a biased sensor/input, according to the vehicle's test plan.
One bank differs from the otherCompare bank-specific intake and exhaust leaks, injectors and sensor circuits. A shared fault can still affect banks differently.
Large corrections but no codeRecord the evidence and investigate; a fault may not have met its monitor conditions or threshold.

These are hypotheses, not component verdicts. For example, a fixed air leak often has a greater proportionate effect at idle, but different airflow models and faults can change the pattern. A GM service procedure for specific vehicles compares idle and approximately 2,000 rpm and lists several possible causes when trim improves; it does not establish a universal limit. GM service information.

Worked example: positive trim at idle

Illustrative example: a warm, single-bank petrol engine with a mass-airflow sensor idles roughly. The scan tool reports closed-loop control, and the technician has recorded the fault codes and freeze-frame data without resetting adaptations. The figures below are invented to show the reasoning; they are not universal pass limits. For this example, the vehicle procedure permits STFT and LTFT from the same bank to be added as an approximate diagnostic correction.

  • Warm idle, bank 1: LTFT +12%, STFT approximately +10%; combined indication approximately +22%.
  • Steady 2,000 rpm in Park, bank 1: LTFT +3%, STFT approximately +2%; combined indication approximately +5%.

Interpretation: at idle the ECU is adding substantial fuel in response to its feedback. At raised speed the indicated correction is smaller. This pattern makes an intake or crankcase-ventilation air leak a reasonable test direction, because a leak can be a larger proportion of the total airflow at idle. It does not prove a leak: airflow measurement, a change of learned cell or other faults can also affect the comparison. The readings are taken at stable conditions with the engine still in closed loop; a raised-speed test in Park does not test fuel delivery under road load. GM service information: idle and raised-speed comparison on specified vehicles.

Test and repair: following the vehicle and smoke-machine procedures, the technician finds smoke escaping from a split intake vacuum hose downstream of the airflow sensor. The hose is replaced and a repeat leak test shows no smoke at the repair. The smoke test confirms a leak at that location; the fuel-trim pattern alone did not identify the hose.

Verify: after the appropriate relearn and with closed loop confirmed, the same bank is checked at the same operating points. In this example idle now reads LTFT +2% and STFT approximately +1%; at 2,000 rpm it reads LTFT +1% and STFT approximately +2%. The rough idle has gone and the fault does not return on a suitable test drive. These results support the repair; compare actual readings and readiness with the vehicle procedure, and do not treat an immediately reset LTFT as proof of success.

Worked example: negative fuel trim

Illustrative example: a single-bank petrol engine runs in closed loop at normal temperature and has a stored P0172. The technician records the codes, freeze-frame data and trims before clearing or resetting anything. The following values and test results are invented to demonstrate the method; they are not universal diagnostic limits. This example assumes the vehicle's procedure allows the two trims for the same bank to be added for an approximate combined indication.

  • Warm idle, bank 1: LTFT −16%, STFT approximately −5%; combined indication approximately −21%.
  • Steady 2,000 rpm in Park, bank 1: LTFT −12%, STFT approximately −3%; combined indication approximately −15%.

Interpretation: the ECU is removing fuel in both conditions in response to its feedback. This suggests a rich tendency, but the numbers alone do not prove that the fuel injectors or lambda sensor are faulty. Excess fuel vapour, high fuel pressure, injector leakage, inaccurate airflow or temperature inputs, and misleading sensor feedback are among the possibilities. Learned values can differ between operating cells, and the stationary raised-speed test does not establish what happens under load.

Narrowing it down: in this example, the technician checks the relevant service information, fuel specification, sensor data and fuel delivery using the manufacturer's procedures. No fault is found in those checks. The oil level is above its expected range and the oil smells strongly of fuel; the vehicle has repeatedly been driven on very short trips. Further investigation confirms fuel-diluted oil and finds no fuel-system fault responsible. Fuel vapour from the crankcase can contribute to a rich condition through the ventilation system. Fuel smell or oil level alone does not establish the cause: investigate and repair any fuel leak or other underlying fault. A GM bulletin describes fuel-diluted oil associated with short trips and negative LTFT on specified vehicles; its procedure and limits are vehicle-specific.

Repair and verify: in this example the confirmed contaminated oil and filter are replaced using the vehicle procedure. The technician clears the code as directed, allows the ECU to relearn, then repeats the warm closed-loop checks at the same operating points. Idle now shows LTFT −2% and STFT approximately −1%; at 2,000 rpm LTFT is −1% and STFT approximately −2%. Following an appropriate test drive, the code has not returned. Compare readings and monitor status with the vehicle's procedure: a zero LTFT immediately after a reset is not proof of repair, and a test drive alone may not complete every monitor.

Worked example: different readings between banks

Illustrative example: a warm V-engine with separate upstream sensors and bank-specific trims has a rough idle and a stored P0171. The technician records the codes and freeze-frame data before clearing anything, confirms closed-loop operation, and uses the vehicle information to identify bank 1 and its upstream sensor. The readings and test results below are invented; they are not universal limits. In this example the vehicle procedure permits STFT and LTFT on the same bank to be added for an approximate combined indication.

  • Bank 1 at stable idle: LTFT +14%, STFT approximately +6%; combined indication approximately +20%.
  • Bank 2 at the same idle: LTFT +2%, STFT approximately +1%; combined indication approximately +3%.
  • At a steady 2,000 rpm in Park: bank 1 is approximately +7% combined and bank 2 approximately +3%, with both banks still in closed loop.

Interpretation: bank 1 is adding considerably more fuel at idle, so investigate faults that can affect its cylinders or feedback more strongly. The lower bank 1 correction at raised speed makes an intake leak near that bank one possibility. A bank-specific exhaust leak ahead of the sensor, injector problem, or sensor or wiring fault can also produce a difference. A shared fault can affect the banks unequally, and a change of learned cell may influence the comparison. The trims are clues, not proof of a failed component. Subaru diagnostic guidance on intake and upstream exhaust leaks.

Test and repair: using the vehicle and equipment procedures, the technician performs a regulated intake smoke test and finds a leak at the intake manifold seal adjoining a bank 1 runner. In this invented case the seal is replaced, and a repeat leak test shows no smoke at the repair. The leak test identifies the location; the difference in trims alone could not establish it. If no leak were found, the next checks would follow the vehicle's diagnostic procedure for bank 1 fuel delivery, exhaust and sensor circuit.

Verify: after the appropriate relearn, the technician repeats the warm closed-loop idle and raised-speed checks on both banks. At idle, bank 1 now reads LTFT +2% and STFT approximately +1%, while bank 2 reads LTFT +2% and STFT approximately 0%. The rough idle has cleared, and the code does not return during an appropriate test drive. Compare readings and monitor status with the vehicle procedure; an immediately reset LTFT is not proof of repair. A stationary 2,000 rpm check does not test fuel delivery under road load.

Worked example: misleading lambda sensor feedback

Illustrative example: a warm petrol engine with a conventional upstream narrowband sensor idles roughly and uses more fuel than expected. Closed-loop control is active. The technician records the fault codes, freeze-frame data and trims before resetting anything. The figures and test results below are invented to demonstrate the diagnosis; they are not vehicle specifications. This example assumes the manufacturer permits the trims from the same bank to be added for an approximate combined indication.

  • Bank 1 at stable idle: LTFT +12%, STFT approximately +9%; combined indication approximately +21%.
  • Upstream sensor data: the scan tool reports a low, lean-indicating signal for much of the test.
  • Independent check: a correctly used exhaust gas analyser indicates a rich exhaust under the test conditions.

Interpretation: the ECU is adding fuel because of what its feedback indicates, yet the separate exhaust measurement suggests the actual exhaust is rich. This disagreement makes the feedback path worth investigating; it does not by itself prove that the sensor is defective. Confirm the analyser setup, sampling point and interpretation for the vehicle, and investigate intake and upstream exhaust leaks, misfire and fuelling faults. Scan-tool readings are processed data and may not show every signal fault. Bosch: comparing sensor data and exhaust gas readings.

Narrowing it down: in this invented case the specified leak, combustion and fuel-system checks do not identify a fault. The technician identifies the sensor type and uses the manufacturer's test procedure, correct connections and a suitable oscilloscope to compare the sensor signal and the ECU-side input. During the prescribed response checks, the sensor-side waveform responds as expected, but the ECU-side signal is intermittently low. Inspection and circuit testing then reveal a damaged connector and wiring fault between the sensor and ECU. The disagreement localises the problem to the feedback circuit; it does not justify replacing the sensor without further evidence. A GM bulletin illustrates that contaminated oxygen-sensor wiring can skew readings on specified vehicles; its remedy is specific to those vehicles and its particular fault.

Repair and verify: the damaged wiring and connector are repaired according to the vehicle procedure, and the sensor-side and ECU-side signals are checked again. After the appropriate relearn and with closed loop confirmed, the same idle condition now shows LTFT +2% and STFT approximately +1%; the gas-analyser result is consistent with the commanded operating condition and the rough idle has cleared. The code does not return on an appropriate test drive. Compare monitor status and readings against the vehicle procedure; a recently reset LTFT alone is not proof of repair.

This example is for a conventional narrowband sensor. Wideband sensors use different control circuits and signals; never apply a generic 0–1 V test or probe an unfamiliar circuit without the manufacturer's procedure. Bosch: sensor signal types and test conditions.

Worked example: positive fuel trim under load

Illustrative example: a single-bank, port-injected petrol engine drives normally at idle but hesitates during a steady uphill drive. The technician records the complaint, any codes and freeze-frame data before resetting adaptations. The figures and test results below are invented to show the reasoning; they are not universal limits. In this example the vehicle procedure allows STFT and LTFT for the same bank to be added as an approximate combined indication.

  • Warm idle, bank 1: LTFT +2%, STFT approximately +1%; combined indication approximately +3%.
  • Steady moderate load, bank 1: LTFT +8%, STFT approximately +10%; combined indication approximately +18%. Closed-loop control remains active at the recorded point.

Interpretation: the ECU is adding much more fuel at the loaded point. A fuel supply that cannot maintain the required delivery is one possibility; inaccurate airflow measurement, injector restriction, an exhaust leak or misleading sensor feedback can also produce positive correction. Different learned cells may contribute to the change. The trim pattern alone cannot identify the defective part, and free-revving in Park does not reproduce road load.

Narrowing it down: the technician checks the vehicle's service information and inspects the intake, airflow-sensor installation, exhaust and wiring. A suitable log is captured at the moderate-load condition on a safe road or dynamometer, with a second person operating the equipment. Fuel-system status, engine speed, load, both trims, commanded and measured lambda where supported, and the relevant fuel-pressure data are recorded. The test is stopped if the engine runs severely lean or misfires; higher load or full throttle is not required to prove the point. On systems that enter open loop at high load, STFT may stop being a live correction, so interpret it only with the control status and vehicle-specific data.

Test and repair: in this example, fuel pressure is within the manufacturer's specified range at idle but falls below the required pressure during the recorded moderate-load condition. The technician confirms the measurement with the approved equipment, then follows the vehicle's fuel pressure, delivery and electrical tests. A restriction is confirmed at a serviceable fuel filter; pump supply and control test correctly. The filter is replaced and the fuel system is rechecked for leaks. A pressure drop alone would not prove the filter or pump is faulty. Bosch: fuel supply and reduced delivery.

Verify: after the appropriate relearn, the technician repeats the same warm closed-loop idle and moderate-load checks. In this example idle reads LTFT +1% and STFT approximately +1%; under the same load LTFT is +2% and STFT approximately +2%. Fuel pressure remains within the vehicle's specification, the hesitation is gone, and no relevant fault returns during the prescribed test. Check monitor status as well: an immediately reset LTFT or a short test drive alone is not proof that every monitor has completed.

Use the manufacturer's approved connections, pressure-relief steps and test equipment. Petrol direct-injection systems can retain high pressure, and their low- and high-pressure circuits require their own procedures.

Worked example: a faulty mass airflow sensor

Illustrative example: a warm, single-bank petrol engine with a mass airflow (MAF) sensor hesitates at moderate load and has a stored P0171. The technician records the codes, freeze-frame data and trims before clearing anything. The numbers and test results below are invented to show the method; they are not specifications. For this example, the vehicle procedure permits same-bank STFT and LTFT to be added as an approximate combined indication.

  • Warm idle, bank 1: LTFT +3%, STFT approximately +2%; combined indication approximately +5%.
  • Steady moderate load, bank 1: LTFT +9%, STFT approximately +10%; combined indication approximately +19%. The fuel system remains in closed loop.

Interpretation: the ECU is adding more fuel at the loaded point. A MAF sensor that under-reports airflow can contribute to a lean tendency, but these trims do not prove the sensor is faulty. Fuel delivery, unmetered air, intake configuration, exhaust leaks, sensor feedback and changes in learned cells are also possible. Closed-loop status must be checked at each point; a free-rev test in Park does not reproduce road load.

Narrowing it down: the technician follows the vehicle's diagnostic procedure, inspects the air filter, MAF housing and ducting, and checks for air leaks downstream of the MAF. Intake and upstream exhaust leak checks, fuel-pressure and delivery tests, and checks of the MAF power, ground, wiring and connector reveal no fault in this example. A low reported airflow value by itself does not establish a bad MAF: an air leak or disturbed airflow can produce misleading readings. GM: low MAF readings and intake-system causes on specified vehicles.

At the same steady speed, load and operating temperature on a dynamometer, the suspect sensor reports approximately 14 g/s; a verified compatible known-good sensor temporarily fitted in the same housing reports approximately 19 g/s. With the known-good sensor installed, the short-term correction moves towards zero while the learned long-term value initially remains positive. Reinstalling the original sensor reproduces the low reading and positive correction. The comparison supports a biased sensor after the other checks; these airflow values are illustrative and must not be used as another engine's specification. Use the manufacturer's comparison method and account for normal test variation. Subaru: P0171 metering-device and leak checks.

Repair and verify: the confirmed faulty MAF is replaced with the correct part, and the intake is reassembled and checked. After the appropriate relearn, the technician repeats the warm closed-loop idle and moderate-load checks. In this example idle shows LTFT +2% and STFT approximately +1%; at the same load LTFT is +2% and STFT approximately +2%. The hesitation has gone, and no relevant code returns during the prescribed test. Check monitor status and the manufacturer's limits; an immediately reset LTFT alone is not proof of repair. A road test requires a driver and a second person to operate the diagnostic equipment.

Common fault codes

P0171 and P0172 generally identify a lean and a rich fuel-system condition on bank 1; P0174 and P0175 identify lean and rich conditions on bank 2 respectively. The code indicates the monitor result, not the failed component. Confirm the exact description and diagnostic procedure for the vehicle, including its bank identification. Monitor thresholds and enabling conditions vary. Toyota: fuel-trim code examples.

Workshop procedure

  1. Record the complaint, fuel type, modifications, stored and pending codes, freeze-frame data and readiness. Inspect intake ducting, hoses, PCV connections, wiring and exhaust for obvious faults. Do not clear codes or adaptations before recording the evidence.
  2. Bring the engine to the relevant temperature and verify fuel-control status. Log STFT and LTFT for each available bank, engine speed, load, coolant temperature, airflow or manifold pressure, commanded lambda and upstream sensor data where supported.
  3. Record a stable idle, then a stable raised speed in a safe stationary position, following the vehicle procedure. Compare the same bank and operating conditions. If the concern occurs under load, capture a suitable road or dynamometer log safely with a second person operating the scan tool.
  4. Use the pattern to select a test: a regulated smoke test for an intake leak, fuel pressure and delivery tests under the specified conditions, injector tests, or checks of airflow and sensor wiring. Follow vehicle and equipment procedures for pressure and test medium; do not apply unregulated shop air to the crankcase or fuel system. For fuel-vapour systems, use the specified inert gas and leak-test equipment. Petrol direct-injection systems can retain high pressure: follow the manufacturer’s depressurisation and connection procedure before opening a fuel circuit. Bosch: leak testing and inert gas.
  5. If sensor feedback and other evidence disagree, compare with an exhaust gas analyser and test the sensor and circuit using the correct procedure. Scan-tool values are processed and may be limited or filtered; a suitable oscilloscope can reveal a signal the displayed data does not show. Check the circuit, reference and heater as applicable before replacing parts.
  6. Repair the confirmed cause, then follow the manufacturer's instructions for clearing faults or resetting adaptations if appropriate. Recheck for leaks, repeat the original operating conditions and allow the ECU to relearn before judging the final result.

When feedback tells the wrong story

A positive trim means the ECU is adding fuel; it does not independently prove that the actual exhaust mixture is lean. An exhaust leak upstream of the sensor, misfire, wiring fault or a faulty sensor can distort the oxygen signal. If a gas analyser indicates a rich exhaust while the ECU is adding fuel, investigate the feedback and its circuit as well as the fuelling system. A newly fitted sensor or other part still needs to be tested. Bosch recommends comparing sensor data with exhaust-gas readings and, where necessary, checking the signal with an oscilloscope. Bosch: lambda and air-mass sensor diagnosis.

A conventional narrowband zirconia sensor and a wideband air–fuel sensor have different signals and test methods. Do not apply a 0–1 V switching test to every sensor; use the manufacturer's pinout, equipment and procedure. Exhaust oxygen can also be affected by misfire, so interpret the signal alongside combustion and gas-analysis evidence. Bosch: lambda sensor signal types.

Related reading