QYS-EFI-02 Immediate Run-Enable Loss Is Not a Proven No-Start
A start-and-die event proves the engine caught. It does not prove the run-enable chain stayed alive after the catch.
The engine started, so the run-enable path must be good.
The engine achieved combustion briefly. It does not prove authorization, fuel command, injector enable, ignition feed, RPM signal, relay output, idle air, or PCM power stayed alive in RUN.
Purpose
This asset exists to keep a start-and-die complaint from getting misfiled as a proven no-start, a proven fuel problem, or a proven ignition problem just because the engine fired once.
The job is to separate crank-state evidence from post-catch evidence. The catch matters, but the dropout after the catch is where the proof lives.
Core Idea
Immediate run-enable loss is a state-change failure. The vehicle has enough air, spark, fuel, timing, compression, and authorization to light off briefly, but one required piece of the sustain chain disappears as the system transitions from START to RUN.
What the symptom seems to prove: The engine started, so the PCM, fuel pump, injectors, spark, and security path must all be good.
What it actually proves: The engine reached brief combustion. It does not prove the system stayed authorized, powered, commanded, synchronized, or mechanically supplied after the catch.
That difference is the whole diagnostic split. Starting is not the same as staying running.
Why This Matters In The Real World
This fault burns time because the first few seconds look convincing. The engine catches, maybe flares, maybe sounds clean, and then dies. That makes people assume the basics are already proven.
They are not. A brief start can be running on prime fuel, crank-only enable, stored idle air, temporary relay latch, or a signal that drops out as soon as RPM changes. Treating that short catch as proof closes the case too early.
What Is Actually Failing
The failure is not automatically fuel, spark, throttle body, PCM, security, or relay. The failure is the loss of a required run condition after initial combustion.
That loss may be command side, load side, logic side, signal side, or airflow side. The system may pass key-on prime and crank checks while failing the run-state handoff.
The Big Diagnostic Trap
The trap is testing the wrong time window. A tech verifies pump prime, sees crank spark, hears a relay click, catches one injector pulse, or sees the engine fire, then treats that as proof of sustained run control.
Those checks only prove the system did something before or during the catch. They do not prove what the system did one second later when the engine needed to stay alive.
The System Chain You Have To Think Through
Think through the run-enable chain as a sequence, not as a pile of parts:
- The crank signal must remain valid after the engine catches, not just during starter speed.
- The PCM must keep its main power, grounds, references, and internal logic stable as voltage and load change.
- The main, ASD, EFI, ignition, or fuel relay path must latch and carry load in RUN, not only click or energize during crank.
- Injector pulse, ignition command, and fuel pump command must continue after the initial start window closes.
- Idle air, throttle control, and minimum airflow must support the engine once starter airflow and flare are gone.
Any break in that chain can create the same symptom: starts, catches, then dies like somebody turned the key off.
Why This Gets Worse Under Real Conditions
Real conditions expose this because the transition is not gentle. Starter load comes off, RPM jumps, voltage recovers, relay logic changes, security logic may recheck, idle control takes over, and the PCM moves out of crank strategy.
A marginal relay contact, weak ignition switch RUN feed, dropping crank sensor signal, unstable PCM power feed, security timeout, or idle-air fault may only show itself inside that narrow post-catch window.
What This Failure Looks Like On The Vehicle
On the vehicle, immediate run-enable loss usually looks cleaner than the fault actually is:
- The engine starts and dies within about 1-3 seconds.
- The engine may run only while the key is held in START or during the initial flare.
- Fuel pump prime may sound normal, but pump command or relay output disappears after the catch.
- Spark or injector pulse may be present during crank and missing immediately after the engine starts.
- The tach, scan RPM, security lamp, main relay state, or PCM data stream may drop out right when the engine dies.
The symptom may feel like a bad pump, bad throttle body, bad PCM, or bad ignition part. The pattern only says the run state was not sustained.
What A Good Tech Should Prove Instead
A good tech does not ask, "Did it fire?" and stop. A good tech asks, "What disappeared after it fired?" Prove the loss during the actual event:
- Capture RPM signal during crank, catch, and stall. Do not accept crank-only RPM as run proof.
- Check fuel pump command and pump power output through the stall, not only during key-on prime.
- Verify injector pulse and ignition control after the engine catches, not only while cranking.
- Load-test the main, ASD, EFI, ignition, and PCM power feeds in RUN during the dropout window.
- Watch security state, idle-air command, throttle position, PCM power, and module communication as the symptom happens.
The proof standard is event-based. If the failure happens after the catch, the test has to watch after the catch.
The Field Rule
Do not let the first fire trick you. The system can pass the start window and still fail the run window.
Things Learned From This Asset To Stop Doing
- Stop calling it a proven no-start just because it starts and dies.
- Stop treating pump prime as proof of pump run command.
- Stop treating crank spark as proof of RUN ignition feed or sustained coil control.
- Stop treating one injector pulse as proof of continued injector enable.
- Stop replacing parts before identifying which signal, feed, command, or airflow path disappears after the catch.
Things Learned From This Asset To Start Doing
- Start separating START-state evidence from RUN-state evidence.
- Start testing through the exact catch-and-stall window instead of before it.
- Start proving RPM, fuel command, injector pulse, ignition power, relay output, and PCM power as live conditions.
- Start using loaded checks on feeds and grounds instead of trusting static voltage or relay sound.
- Start treating security state, idle-air control, and module stability as part of the run-enable chain.
Summary
Immediate run-enable loss is not a simple no-start. It is a start-to-run sustain problem.
The engine firing briefly proves that combustion happened. It does not prove the PCM kept authorization, RPM, fuel command, injector enable, ignition power, relay output, idle air, or module power alive in RUN.
The clean diagnostic move is to stop proving the start and start proving the loss. Find what disappears after the catch, and the failure path stops hiding.
Stay in the loop
Get new drops in your inbox
New QTS builds, tools, and garage stories — straight to your inbox. No spam. Unsubscribe anytime.
Read the Privacy Policy.