SpeedNeeds
SpeedNeeds Tool

Ignition Command Logic Mapper

Tight scope: map who is allowed to create spark right now. This clarifies ECU enable, ignition power path, security inhibit, and RPM dependency so you do not start the wrong ignition test first.

This matters because many systems allow prime at KOEO, then require RPM once cranking/running.
Pick the spark architecture: ECU coil drive, ignition module control, or distributor-triggered.
Most systems do not fire coils at KOEO. If you expect spark only during crank/run, KOEO checks can mislead you.
If YES, KOEO coil checks can waste time. Validate spark enable during crank, with a real RPM signal.
If security can inhibit, the ECU may "want" ignition but never enable the spark.
These can block spark even when power and wiring look fine at the coil.
This does not change logic, it just prints into the map so you keep your head straight.
Primary spark commander
--
ECU enable expected?
--
Ignition control path
--
Most important gate
--
Copy this into your notes. It is the "who is allowed to create spark" snapshot.
Notes and logic
  • KOEO behavior: Most systems do not fire coils at KOEO. Spark enable is usually crank/run only and tied to a valid RPM/crank signal.
  • RPM dependency: If spark enable depends on RPM, do not judge "spark power" based only on KOEO checks. Test under crank/run.
  • Security inhibit: Security can block the enable even when the ECU has power and ground. Treat it as a gate until proven otherwise.
  • Spark inhibits: Security, interlocks, or ECU strategy can block spark even when power feed is present.
  • What this tool is NOT: It is not a diagnostic. It is an orientation map so you start on the right A-test.
Purpose of this tool

This tool exists to keep you oriented before you start chasing spark with a tester, light, or scope.

It helps prevent three common mistakes:

  • Proving the wrong thing - testing power, ground, or the spark itself when the system is not allowed to command it.
  • Testing in the wrong state - checking spark behavior at KOEO when the logic only applies during crank or run.
  • Testing with the wrong expectation - assuming the spark should be on continuously when prime windows, RPM dependency, security inhibits, or cut devices say otherwise.

This tool is here to prevent you from proving the wrong thing, in the wrong state, with the wrong expectation.

The output is an orientation snapshot. It tells you who can create spark and under what conditions - not what failed and not what to replace.

Get new drops in your inbox

Read the Privacy Policy.