What the Car Can Sense
A module is only as good as what it can measure. Every decision the car makes begins with a sensor turning something physical into a signal.
In plain language
Sensors are the car's senses. They convert something physical — rotation, temperature, pressure, position, light, sound — into an electrical signal a module can read. There are only a handful of families, and once you know which family a sensor belongs to, you know what its signal should look like and how it tends to fail.
The most useful thing to understand is that a sensor rarely lies on purpose. When a module reports an implausible reading, the sensor, its wiring, its supply, its ground and the thing it is measuring are all candidates — and quite often the sensor is reporting a real condition that nobody wants to hear.
What the customer sees
A warning light, a gauge reading that does not match reality, a function that behaves as though the car thinks it is somewhere it is not, or a fault that only appears when hot, cold or wet.
What the module is doing
Supplying a reference voltage, reading the return, and comparing it against what it expects. Where two sources should agree — commanded position against measured position, one wheel speed against the others — it checks them against each other and reports a plausibility fault when they diverge.
What a technician tests
The signal itself, in the condition where the complaint happens, and preferably with an oscilloscope where the signal is a waveform rather than a steady value. Supply and ground at the sensor are checked first, because a sensor with a poor ground produces a wrong reading while being perfectly healthy.
The technical detail
A sensor needs its circuit as much as its own health. Most sensors are supplied with a reference from the module and return their signal on a third wire. Any of those three can change what the module sees. This is why "the sensor reads wrong" and "the sensor is faulty" are not the same statement.
Plausibility is the module's cross-check. Modern modules compare what they command with what they measure and compare related signals with each other. A plausibility fault means the picture does not add up — which is a very different claim from a circuit fault.
Waveforms hide faults that averages do not show. A signal can be present, average out correctly and still contain the momentary drop-out that causes the complaint. That is what scope testing is for, and it is why a sensor that measures correctly on a meter can still be the cause.
Some sensors are network devices now. Rain, light and solar sensing typically arrives as a message on a local link rather than as a raw voltage. Their faults therefore read as communication findings, and they are diagnosed the way network faults are diagnosed.
Sensor families and what their signals look like
| Family | Signal | What it measures | Where you meet it | What it needs | How failure presents |
|---|---|---|---|---|---|
| Hall-effect sensors | Digital switching signal | Position and speed of a rotating part | Crankshaft and camshaft position on many engines, wheel speed on modern systems, start-button detection on later cars | A supply, a ground and a signal line back to the module | Signal that drops out, becomes erratic or disappears at temperature; the module reports position as implausible or missing |
| Inductive sensors | Alternating voltage generated by a passing target | Speed and position | Crankshaft position on earlier systems, wheel speed on older ABS | Only the two signal wires, with the correct air gap to its target | Weak or distorted signal, often because of an air gap, damaged target wheel or debris rather than the sensor itself |
| Temperature sensors | Varying resistance read as a varying voltage | Coolant, oil, intake air and cabin temperatures | Coolant temperature, intake air temperature, exterior temperature | A reference supply from the module and a return path | A reading stuck at one extreme, which usually indicates an open or shorted circuit rather than a genuine temperature |
| Position sensors | Varying voltage across the sensor's travel | Angle or linear position | Throttle and pedal position, valve-lift position, some flap positions | A reference supply, a ground and a signal line | Dead spots or values that do not track the commanded position, reported by the module as a plausibility fault |
| Pressure sensors | Voltage or a digital message proportional to pressure | Manifold, fuel, oil, refrigerant and tyre pressure | Manifold absolute pressure, fuel rail pressure, refrigerant pressure | A reference supply and ground, plus a correct mechanical connection | A value the module cannot reconcile with the pressure it commanded, which may be the sensor, the circuit or the actual pressure |
| Mass air-flow sensors | Voltage or frequency proportional to air mass | The mass of air entering the engine | Hot-film air-mass meter | Supply, ground, signal, and undisturbed airflow through the intake | A reading that no longer agrees with load and throttle position; unmetered air after the sensor produces the same complaint with a healthy sensor |
| Oxygen and air-fuel sensors | Generated voltage or a controlled current, plus a heater circuit | Exhaust oxygen content, used to correct fuelling | Pre-catalyst and post-catalyst sensors | Heater supply and control, plus its own signal and ground | Slow response, a stuck reading, or a heater-circuit fault; the fuel corrections that result are a symptom, not the root cause |
| Knock sensors | Small voltage produced by vibration | Combustion noise used to protect the engine | Engine-block knock sensor | A screened signal path and correct mounting torque | Signal masked by mechanical noise or a loose mounting, which the module reports as an implausible signal |
| Switches | Simple open or closed circuit | A driver action or a state | Brake and clutch switches, door contacts, selector positions | Very little — which is why they are so often the cause | A state that never changes, or one that changes only intermittently; enough on its own to prevent a car from cranking |
| Ultrasonic sensors | Reflected sound converted to a distance value | Distance to nearby objects | Parking-distance and parking-assistance sensors | Supply, ground and a signal line to the assistance module | One sensor reported as short-circuited or open by the module that drives it, as in the F56 example on this site |
| Rain, light and solar sensors | Usually a message on a local network rather than a raw voltage | Rainfall, ambient brightness and solar load | Rain-light-solar-condensation sensor at the windscreen | Supply, ground and its local network connection to the controlling module | Reported as a missing network device or an implausible signal, which is a communication finding as much as a sensor one |
Why this matters when something goes wrong
The sensor family tells you the test. A digital switching sensor is judged on whether its edges are clean and present; a resistance-based sensor on whether its value tracks the real condition; a network sensor on whether it is present on its link at all.
It also tells you the trap. Sensor-named codes are among the most frequently replaced parts in the trade and among the most frequently unnecessary, because the code names the signal that was wrong and not the reason it was wrong. Testing the circuit and the condition before the component is what avoids that.