Key takeaways
- Closed loop chases a target with feedback; open loop commands values blind from maps.
- At WOT petrol ECUs deliberately go open loop for component-protection enrichment.
- In closed-loop regions calibrate the target, not the output — the controller always gets the last word.
ECU control strategies are either open-loop (map-based only) or closed-loop (using sensor feedback). Understanding when each is active is crucial for effective calibration.
Overview
Open-loop control uses pre-programmed maps without sensor feedback — “set and forget.” Closed-loop control continuously adjusts based on sensor readings to maintain a target. Most systems use both modes depending on operating conditions.
Open-Loop Operation
Maps/Tables → Actuator Commands (No feedback correction)
- Faster response (no feedback delay)
- Requires accurate calibration
- Used when feedback is unavailable or unreliable
Closed-Loop Operation
Target Value → Compare to Sensor
↓
Error → PID Controller
↓
Correction → Actuator
↓
Sensor → (loop back to compare)
- Self-correcting for wear and variation
- Can compensate for altitude, temperature, aging
- Slower response due to feedback delay
Lambda/AFR Control
- Closed-loop — cruise, part throttle, idle (targeting stoichiometric)
- Open-loop — wide-open throttle, cold start, high load
- Transition — ECU switches based on load, temperature, catalyst temp
During open-loop, the ECU relies entirely on fuel maps — errors aren’t corrected.
Boost Control
- Closed-loop — PID control maintains target boost vs actual
- Open-loop — fallback if boost sensor fails
- Feedforward — base duty cycle from maps, PID corrects error
Knock Control
- Closed-loop — retards timing when knock detected, advances when clear
- Base timing — open-loop starting point from maps
- Learning — long-term adaptation stored in EEPROM
EGR Control
- Closed-loop — using MAF sensor to verify EGR flow
- Open-loop — using position sensor feedback only
- Model-based — calculated flow vs target
When Closed-Loop Disables
- Cold engine — sensors not yet accurate
- Wide-open throttle — response time critical
- Sensor fault — fallback to open-loop
- Regeneration — DPF regen uses open-loop enrichment
Fuel Trims
Fuel trims are closed-loop corrections stored by the ECU:
- Short-term fuel trim (STFT) — immediate corrections
- Long-term fuel trim (LTFT) — learned corrections over time
- Normal range — ±10% indicates proper calibration
- Large trims — indicate air/fuel system issues
Calibration Implications
- Open-loop regions require precise map calibration
- Closed-loop compensates for small errors automatically
- Fuel trims reveal calibration quality in closed-loop regions
- WOT tuning is open-loop — no safety net from sensors
Best Practices
- Verify closed-loop operation with scan tool data
- Monitor fuel trims after tuning changes
- Open-loop WOT requires careful wideband verification
- Understand when the ECU will and won’t self-correct
Where Each Strategy Lives in a Modern ECU
Closed loop is everywhere the ECU has a trustworthy sensor and time to react: lambda control at part load on petrol, boost pressure, rail pressure, idle speed. Open loop takes over where reaction time or sensor validity runs out — full-load enrichment, cold start, component-protection enrichment at high EGT. Tuning implication: in closed-loop regions the controller will fight direct output edits, so the correct lever is the target or the model feeding it; trims drifting away from zero afterward are your feedback that the model no longer matches reality.
Where Tuners Meet Each Strategy
Calibration work constantly crosses the boundary between the two worlds. Lambda control is the classic example: at part load the petrol engine sits in closed loop around stoichiometry, and fuelling changes there are corrected away by the trims — the place to work is the base map so that the trims stay near zero. At wide-open throttle the ECU deliberately drops to open loop and commands component-protection enrichment; the target lambda tables for that region are a direct tuning surface, within EGT limits.
Boost control shows the other trap. The closed-loop controller will chase the target it is given, so raising boost by inflating the feed-forward duty alone leads to overshoot and oscillation; raising the target without enough duty-cycle authority leads to permanent deviation — and on many platforms a stored overboost or underboost fault with limp mode. Target, feed-forward and PID authority have to move together.
The general rule: in closed-loop regions, calibrate the target and the model so the controller has an achievable goal; in open-loop regions, calibrate the commanded value itself and verify with logs. Fighting a closed loop with brute-force map changes is the signature of a poor tune — the controller always gets the last word.
Why do my fuel map changes disappear at part load?
What happens if boost is raised without touching the closed-loop controller?
Is open loop dangerous?
Related: these maps and strategies are the daily work of our ECU remapping service. See also ECU Map Types Glossary in the knowledge base.
