QYS-IGN-02 A Correct Dwell Command Is Not Proof the Coil Stored Enough Energy

Why correct commanded dwell can coexist with weak coil charging, low stored energy, and a spark that fails only under real cylinder pressure.

QYS IDQYS-IGN-02
Build LaneIgnition Diagnostics / Dwell Command, Primary Current Rise, and Stored-Energy Verification
System AreaIGN / Ignition / Dwell Commands, Coil Drivers, Primary Current, Coil Saturation, Stored Energy, and Secondary Spark Delivery
What It Seems To Prove

The controller commanded the expected dwell time, so the coil fully charged and can produce the required spark.

What It Actually Proves

The controller requested or reported a charging interval. It does not prove usable voltage reached the coil, required current flowed, stored energy was achieved, or the spark survived cylinder-pressure demand.

Purpose

This QYS separates commanded dwell from the charging result that actually matters. The dwell value is a time request. The coil still has to receive voltage, pull current through the full primary path, build magnetic energy, release cleanly, and deliver that energy through the secondary path.

The purpose is to stop a correct scan value, visible spark, or acceptable idle from being treated as proof of ignition capacity. The proof has to come from what the circuit achieved during the failure condition.

Core Idea

Dwell controls how long the primary circuit is allowed to charge before the ignition driver opens the circuit. Charge time matters, but time alone does not establish current rise or stored magnetic energy.

What the symptom seems to prove: The dwell number is correct, so the controller, driver, coil, and spark output must all be correct.

What it actually proves: A charging interval was requested or reported. The value does not confirm the voltage across the primary winding, the shape of the current ramp, the achieved peak current, or the energy delivered across the plug gap.

A strong diagnosis therefore separates requested dwell from achieved coil charge. That distinction is the difference between reading a command and proving ignition performance.

Why This Matters In The Real World

Ignition systems often pass easy checks because the demand is low. A coil may fire a plug in open air, idle smoothly, and show normal reported dwell while feed resistance, ground loss, a weak driver, heat, or winding damage limits primary current.

The failure appears when the required firing voltage rises or the available charge time falls. That is why the same vehicle can start cold, idle cleanly, and then misfire during cranking voltage loss, high RPM, boost, heavy throttle, or hot operation.

What Is Actually Failing

The failure is not always the dwell command. The charging process can break anywhere between the battery and the magnetic field stored inside the coil. Feed-side voltage drop, ground-side voltage drop, increased primary resistance, weak driver current, internal smart-coil electronics, or a damaged primary winding can flatten or slow the current ramp.

The release and secondary sides can fail too. A correct primary current event still does not guarantee that the field collapses correctly or that the resulting voltage reaches the plug gap without leaking through a boot, wire, spring, coil tower, or damaged insulation. The fault must be assigned to command, supply, ground, driver, coil, release, or secondary delivery instead of being dumped on the coil by assumption.

The Big Diagnostic Trap

The trap is treating dwell as if it were a direct measurement of stored energy. Scan data usually shows what the controller calculated, commanded, or believes occurred. It may not show actual current flow through the primary winding.

A second trap is assuming that more dwell always creates more spark energy. Once the coil reaches its intended current limit or saturation region, extra on-time may add heat instead of useful energy. Failed current limiting or excessive dwell can overheat coils and drivers, while unintended resistance can prevent the current target from being reached at all.

The System Chain You Have To Think Through

Think through the complete ignition-energy chain instead of stopping at the dwell PID:

  • Supply: battery and charging voltage, fuse and power distribution, ignition feed, connectors, terminals, and voltage delivered while primary current is flowing.
  • Primary path: coil primary winding, winding resistance and inductance, ignition driver or internal smart-coil electronics, driver ground, and module ground.
  • Charge event: dwell command, primary current rise rate, achieved peak current, intended current limiting, and coil saturation behavior.
  • Release event: driver turn-off timing, magnetic-field collapse, induced secondary voltage, and the energy available for the spark event.
  • Delivery: coil tower, boot, wire, spring, plug terminal, plug gap, insulation integrity, mixture condition, and cylinder pressure.

Every link can reduce delivered ignition energy while commanded dwell still looks normal. The diagnosis is not complete until the failed link is identified under the condition that produces the symptom.

Why This Gets Worse Under Real Conditions

Low cranking voltage reduces the electrical push available to build primary current. High engine speed reduces the time between firing events. Heat can increase resistance, weaken electronics, and expose insulation leakage. Feed-side or ground-side loss steals voltage exactly when the coil is demanding current.

High load, boost, lean mixtures, wide plug gaps, and high cylinder pressure increase the voltage required to start and maintain the spark. A marginal coil-charge event may look acceptable outside the cylinder but fail when the secondary path has to overcome real firing pressure. That is why condition matching matters.

What This Failure Looks Like On The Vehicle

Common patterns include:

  • Hard starting or weak ignition during low cranking voltage, especially with a marginal battery, cable, feed, or ground path.
  • A clean idle with a misfire under load, during boost, or at heavy throttle when cylinder-pressure demand rises.
  • High-RPM breakup because available charging time shrinks and the primary current target is no longer reached.
  • A heat-related intermittent misfire, normal reported dwell, or a visible open-air spark that still fails under compression.
  • Coil or driver overheating, repeated ignition-component failure, or damaged electronics caused by excessive dwell, failed current limiting, or an unresolved circuit problem.

None of these patterns prove the coil itself failed. They prove that ignition energy was not delivered reliably under the operating condition.

What A Good Tech Should Prove Instead

A good technician proves the charging result and then follows the energy into the secondary path:

  • Measure voltage at the coil while the primary circuit is loaded, then separate feed-side loss from ground-side loss.
  • Verify the dwell command and driver release timing, but do not stop there. Confirm that the driver can carry and interrupt the required current.
  • Use a primary-current ramp where appropriate to evaluate current rise rate, achieved peak current, current limiting, and saturation behavior.
  • Reproduce low voltage, heat, RPM, load, boost, plug-gap, and cylinder-pressure conditions closely enough to make the failure show itself.
  • Separate a primary charging fault from a secondary delivery fault, then assign ownership to the command, feed, ground, driver, coil, or secondary path before replacing parts.

The strongest evidence is captured during the actual failure. A normal result under easier conditions does not clear the system.

The Field Rule

A correct dwell command proves requested charge time. It does not prove achieved primary current, stored coil energy, or delivered spark under cylinder pressure.

Command is not delivery. Time is not current. Visible spark is not proof of loaded ignition capacity.

Things Learned From This Asset To Stop Doing

  • Stop treating scan-tool dwell as proof that the coil charged correctly.
  • Stop assuming more dwell always means more useful spark energy, or confusing dwell with ignition timing or spark duration.
  • Stop using visible open-air spark, clean idle, or light-load operation as final proof of ignition performance.
  • Stop condemning the coil before testing voltage delivery, ground integrity, driver performance, and the secondary path.
  • Stop replacing coils or drivers without proving why the charging or delivery process failed.

Things Learned From This Asset To Start Doing

  • Start separating requested dwell from achieved primary current and stored magnetic energy.
  • Start checking coil feed voltage and ground-side integrity while the primary circuit is charging.
  • Start using primary-current ramp evidence to judge rise rate, peak current, current limiting, and saturation when the test is appropriate.
  • Start reproducing the heat, RPM, load, voltage, boost, and cylinder-pressure conditions that expose marginal ignition energy.
  • Start separating primary charging faults from secondary delivery faults and proving the failed link before replacing parts.

Summary

Dwell is a command-side time value. It tells the ignition system how long to charge the coil, but it does not measure the charging result.

The coil only stores useful energy when adequate voltage drives the required current through the complete primary path. That energy still has to survive driver release and the entire secondary path under real firing pressure.

The diagnostic move is simple: stop treating commanded dwell as proof. Prove loaded voltage, primary current, current limiting, field release, and secondary delivery under the condition that produces the symptom.