Air/fuel ratio (AFR) tuning help
The single most expensive misunderstanding in DIY tuning is believing the number the PCM commands is the number the engine actually burns. Commanded AFR is a request; delivered AFR is reality — and only a wideband knows the difference. TuneVault reads your VCM Editor commanded-fuel tables and your VCM Scanner wideband trace and checks that the two actually agree.
What TuneVault checks
- ✓Commanded AFR/lambda table is verified against a logged wideband, not narrowband O2s
- ✓Target units (AFR vs lambda vs EQ ratio) are consistent with the actual fuel being run
- ✓N/A WOT targets land around λ 0.85–0.88; boosted targets are appropriately richer
- ✓No lean hole at the closed-loop-to-open-loop (PE enable) transition
- ✓Power-enrichment enable thresholds are set so enrichment arrives before load does
- ✓E85 targets, injector capacity, and fuel-system flow are mutually consistent
- ✓Delivered AFR tracks commanded across the whole pull, including the top end
Commanded vs delivered — they are not the same number
In HP Tuners VCM Editor you edit what the PCM commands: an open-loop or power-enrichment table that targets a specific equivalence ratio or AFR at high load. But what the cylinder actually burns depends on injector data, fuel pressure, MAF/VE accuracy, and fuel quality. You can command 12.5:1 and deliver 13.5:1 if your injector slopes are off or your MAF under-reads — and the engine doesn't care what you commanded, only what it burned.
This is why a wideband is non-negotiable. The narrowband O2 sensors the PCM uses for closed-loop are only accurate near stoich; they're useless for verifying a 12:1 WOT target. TuneVault's entire AFR workflow is built around comparing your commanded table to a logged wideband — if you don't have wideband data, we'll tell you we can't safely sign off on your WOT fueling, full stop.
Lambda is the platform-independent language
AFR numbers are fuel-specific: 14.7:1 is stoichiometric for pump gas, but only about 9.8:1 for E85. Switch fuels and every AFR target shifts. Lambda (λ) sidesteps that — λ 1.0 is always stoich regardless of fuel, λ 0.85 is always 15% richer than stoich. Thinking in lambda means a WOT target of λ 0.80–0.85 is portable across gasoline, E85, and blends.
Many HP Tuners OSes let you display and target in EQ ratio (the inverse of lambda) or AFR. The trap is mixing units mid-tune — entering a gasoline AFR into a table the engine is now burning E85 through. TuneVault checks that your commanded targets make sense for the fuel you say you're running, and translates between AFR, lambda, and EQ ratio so a unit mix-up doesn't run you dangerously lean.
WOT targets — N/A vs boosted
Naturally-aspirated engines typically make best power around λ 0.85–0.88 (roughly 12.5–12.9:1 on pump gas), rich enough for a safety and cooling margin without drowning power. Add boost and you deliberately go richer — often λ 0.78–0.80 or lower (high-11s to low-12s on gas) — because the extra fuel cools the charge and suppresses knock as cylinder pressure climbs. The more boost, the richer the safe target.
These are starting points, not guarantees — your knock data and wideband decide the final number. Running a boosted engine at an N/A AFR target is a classic way to make great dyno numbers right up until detonation. TuneVault flags WOT targets that look lean for your stated induction and reminds you it cannot promise the target that makes peak power on your specific combo; it keeps you on the rich, safe side and tells you to confirm with a wideband on every pull.
Closed loop vs open loop
At idle and cruise the PCM runs closed loop, trimming fuel against the narrowband O2s to hold stoich for emissions and economy — this is where fuel trims live and where your MAF/injector cal gets validated. Under heavy load the PCM switches to open loop and follows your commanded power-enrichment table directly, ignoring the narrowbands. That handoff is defined by tables you can edit (load/RPM thresholds for PE enable).
Understanding the boundary matters: a lean spot at the closed-to-open transition is a real and common drivability and safety issue, often from a poorly-set PE enable point or a commanded table that doesn't blend smoothly from stoich into enrichment. TuneVault checks that your PE transition is smooth and that open-loop targets pick up cleanly where closed loop hands off, so you don't get a momentary lean hole right as load comes on.
E85 and fuel-quality reality
E85 changes everything: stoich near 9.8:1, far more knock resistance, and roughly 30–40% more fuel volume needed — which is why injector and fuel-system capacity, not just a table edit, gate how much E85 you can run. "E85" at the pump also varies seasonally between roughly E70 and E85, so your true stoich and your trims move with the blend unless you have a flex-fuel sensor.
TuneVault sanity-checks that your commanded targets, injector capacity, and fuel choice are mutually consistent — there's no point commanding a rich E85 target through injectors that are already maxed. And as always: lambda tells you the truth across blends, but only a wideband tells you what you actually delivered.
Platforms & hardware
Covers commanded-fuel and power-enrichment tuning on GM LS/LT (LS1–LS7, L83/L86, LT1/LT4) and Ford Coyote, Modular 4.6/5.4, and EcoBoost in HP Tuners VCM Editor — naturally aspirated, nitrous, and forced-induction. Especially relevant to E85 and flex-fuel conversions, boosted blower/turbo builds setting richer WOT targets, and any car where injector capacity gates the achievable AFR.
Start free — see the audit before you pay.
Upload a VCM Editor screenshot and get the exact, safety-checked changes.
Open the CopilotFrequently asked questions
I commanded 12.5:1 but the wideband shows 13.5 — which do I trust?
The wideband, every time. Commanded is a request; delivered is what burned, and the gap usually means injector data or MAF/VE error. Fix the underlying cal so delivered tracks commanded — don't just richen the command to mask it. Never sign off WOT fueling on narrowband O2s.
Why do my AFR targets change when I switch to E85?
Because stoich for E85 is near 9.8:1 versus 14.7:1 for gasoline, so the same lambda is a very different AFR number. Think in lambda to stay sane across fuels. Also confirm your injectors and fuel system can flow the ~30–40% extra volume E85 demands.
What AFR should I target at wide-open throttle?
Roughly λ 0.85–0.88 (about 12.5–12.9:1 on gas) naturally aspirated, and richer under boost (often λ 0.78–0.80 or lower) to cool the charge and fight knock. These are conservative starting points — your knock and wideband data decide the final number. TuneVault won't promise the exact peak-power figure for your combo.
What's the difference between closed loop and open loop?
Closed loop runs at idle/cruise, trimming fuel against narrowband O2s to hold stoich — that's where fuel trims live. Open loop kicks in under heavy load and follows your commanded power-enrichment table directly. A lean spot at the transition between them is a common, fixable safety issue.
Can TuneVault tune my AFR without a wideband?
It can review your tables and catch unit mix-ups, lean transitions, and impossible targets, but it cannot validate WOT fueling without wideband data — the PCM's narrowband sensors simply can't measure a 12:1 target. We'll be explicit that we can't safely sign off WOT until you log a wideband.
- •TuneVault is a tuning copilot, not a replacement for a professional tuner. For high-boost, forced-induction, or unusual builds, a qualified human tuner is still valuable.
- •No tool can guarantee horsepower. Power depends on your hardware, fuel, altitude, and condition — anything promising a number is selling you something.
- •You are responsible for what you flash. You make the changes and write them to your ECU; the outcome is yours.
- •Commanded AFR is not delivered AFR. Always verify fueling with a wideband before boost, and keep timing conservative for pump gas.
- •Modifying emissions equipment may be restricted where you live. Know your local laws; off-road/competition use only where applicable.