DIAGNOSTIC THEORY
Back to Explainers

Where the crank signal comes from: VR vs Hall sensors, trigger wheels, and air gap

Every fuel and spark decision the computer makes starts with the crank signal. Learn how the sensor makes it - variable reluctance or Hall - what the trigger wheel and air gap do, and why only a capture can prove the wire.

What the crank signal actually is

The crankshaft position sensor tells the computer two things: how fast the engine is turning and where the crankshaft is in its rotation. Everything the computer does with fuel and spark starts from that input. No crank signal, no strategy - the computer will not fire injectors or coils on a schedule it cannot see.

Two designs make the signal: variable reluctance and Hall effect

Crank sensors come in two electrical designs, and the test you run depends entirely on which one you are facing. Identify the design from service information before touching a lead - the wrong test on the wrong design produces readings that mean nothing.

The trigger wheel: teeth, gaps, and the position landmark

The sensor does not watch the crankshaft directly - it watches a trigger wheel (reluctor) bolted to it. Each tooth passing the sensor makes one pulse, and the tooth count sets how many pulses the computer sees per revolution.

Most wheels leave one spot deliberately blank - the missing-tooth gap. That gap is the landmark: it happens once per revolution and tells the computer exactly where the crank is, not just how fast it is turning. A damaged or bent tooth makes a liar out of an otherwise healthy sensor.

Air gap: what the sensor can see

The air gap is the distance between the sensor tip and the trigger wheel. It is the one mechanical setting that decides how strong the signal is at birth. Too wide and the sensor cannot see the teeth clearly - the signal goes weak or missing even though every wire is perfect. Rust, debris, a bent bracket, or a sensor not fully seated all open the gap. When the signal is weak at the source and the circuit tests clean, the gap is the next thing to look at.

Why a scope shows what it shows

Put a scope on a VR sensor and crank the engine and you will see a sine wave that grows taller as the engine turns faster. That is normal - the height is the speed information. Judge a VR capture by its amplitude at a known speed and its frequency against the tooth count.

Put a scope on a Hall sensor and you will see a square wave - two flat levels, on and off, at the same height whether the engine cranks or runs. Speed does not change the height. Judge a Hall capture by its switching: levels, duty, and the pattern of events per revolution.

Mixing up the two is the classic misread: calling a VR signal bad because its cranking amplitude is small, or calling a Hall signal bad because its levels do not change with RPM. Each design is judged against its own nature, never the other's.

The scan-tool RPM number is a clue, not proof

The RPM reading on the scan tool shows what the module thinks about crank speed - an interpreted number, sometimes substituted when the real signal is missing. It does not show the wire. A PID reading RPM proves only that the module is reporting RPM; it cannot prove the signal wire between the sensor and the module is intact.

The related explainer on scan-tool limits covers this boundary in detail (What your scan tool can and cannot prove about a crank request). The clue-versus-proof discipline is simple: the PID opens the question, a capture answers it - the actual signal, on a scope, at the sensor's test point and again at the controller's input.

How SpeedNeeds uses it

The crank signal is proved in the problem condition, against the vehicle's own requirements. The design comes first - variable reluctance or Hall, identified from service information - because the design decides what the capture must show. Then the source signal is captured and checked (amplitude and frequency for VR; levels and pattern for Hall), then the same signal is captured at the controller input and the two are compared. A signal that leaves the source strong and arrives weak is a wire-and-connector question, not a sensor question.

The crank signal's system role - what the computer does with it once it arrives - is covered in the companion explainer (Crank/RPM Signal as a Master Enable Clue). And the measurement itself must never disturb the circuit: backprobe the connector, never pierce the wire (Proper circuit testing methods (backprobe vs pierce vs inline)).

Caution and edge cases

Closing clarity

The crank signal is born at the trigger wheel - teeth and gaps turned into electricity by a VR or Hall sensor, across an air gap that has to be right. Prove it the way it travels: design identified, source captured, input captured, each judged on its own evidence. And never let a scan-tool number stand in for a capture - the PID is the clue, the wire is the truth.

Copyright 2026 SpeedNeeds.net. All rights reserved.