4 Sensor Classifications
4.1 Start With the Measurement Story
A team choosing between optical, mechanical, chemical, and inertial sensing needs a sorting rule before it needs a shopping list. Classification helps match the measurement principle to the physical signal, environment, and failure mode.
Phoebe’s Why
This chapter lists capacitance change beside reflected light and sound travel time as one of the physical effects a proximity sensor can use, but a capacitance by itself is not a signal a microcontroller can read – there is no GPIO pin that measures farads. Every capacitive sensor needs a second physics step that turns a capacitance into a time, a frequency, or a voltage, and that second step is ordinary circuit physics: charge a capacitor through a resistor and time how long it takes to cross a threshold. The measured quantity (how close an object is) changes an electrical property (capacitance, through the gap between two conductors) via a governing equation from electrostatics; the reading then inverts a second governing equation, this time from circuit theory, to recover a number the firmware can count. Neither half of that chain is optional, and naming both halves is exactly what the “operating principle” and “output path” axes in this chapter’s own selection ledger are asking a reviewer to do.
The Derivation
Parallel-plate capacitance, the idealized model behind a capacitive proximity or level sensor:
\[C = \frac{\varepsilon_0 \varepsilon_r A}{d}\]
An RC relaxation timer charging toward \(V_{DD}\) crosses a comparator threshold at half-supply after:
\[t = RC\ln 2\]
Inverting the circuit-physics equation recovers capacitance from a measured time; inverting the electrostatics equation then recovers the physical gap the reading actually reports:
\[C = \frac{t}{R\ln 2} \qquad\Rightarrow\qquad d = \frac{\varepsilon_0\varepsilon_r A}{C}\]
Worked Numbers: A Capacitive Proximity Electrode
- Catalog-typical sensing electrode: \(A=1\ \text{cm}^2=1\times10^{-4}\ \text{m}^2\), air gap (\(\varepsilon_r=1\)).
- At \(d=5\) mm (object approaching): \(C=\varepsilon_0 A/d=0.177\) pF.
- At \(d=1\) mm (object close): \(C=\varepsilon_0 A/d=0.885\) pF – five times the capacitance, because \(C\propto1/d\).
- With a catalog-typical \(R=100\ \text{k}\Omega\) relaxation timer: \(t=RC\ln2\) gives \(t=12.3\) ns at 5 mm and \(t=61.4\) ns at 1 mm – the same \(5.00\times\) ratio carried straight through into a timing measurement a firmware timer/counter can resolve.
- This is the same two-equation pattern as the resistive labs elsewhere in this module (temperature-to-resistance, light-to-current); the classification axis this chapter asks a reviewer to name is which pair of governing equations – here electrostatics, then RC timing – actually sits behind a “digital” reading, because a comparator output alone hides both steps.
4.2 Classification Narrows the Search
Sensor classification is a practical map for choosing measurement evidence. A sensor can be grouped by what it measures, how it converts that condition into a signal, how the signal reaches a controller, how much energy it uses, and what limits its field evidence. The goal is not to memorize every part family. The goal is to rule out weak candidates before the design depends on them.
A good classification starts with the measurement decision. Temperature, pressure, motion, light, gas concentration, distance, position, touch, current, and vibration each place different demands on range, accuracy, response time, calibration, mounting, and interface. A sensor category only becomes useful when those demands are tied to an application claim.
Those axes often overlap in one part. A temperature probe might be classified by measured quantity as temperature, by operating principle as resistive or thermoelectric, by output as analog voltage or a digital bus value, and by evidence limits as calibrated for a specific enclosure and airflow. Each label answers a different review question, so dropping one can hide a design risk.
Use classification as an elimination tool before comparing part numbers. If the target must detect motion through a sealed case, contact-only choices fall away. If a sleeping battery node cannot spare heater current, some gas sensors fall away. If firmware has no spare ADC channel, an analog output may be a system cost rather than a simple option.
If you only need the intuition, use this rule: classify a sensor by the evidence path from physical condition to decision, not only by the part name printed on the module.
The First Classification Axes
Measured Quantity
Names the physical or contextual condition: temperature, humidity, pressure, light, motion, distance, gas, force, current, or position.
Signal Form
Describes whether the output is analog, digital, pulse timing, frequency, resistance, capacitance, or a structured bus message.
Energy Behavior
Separates sensors that observe existing energy from sensors that emit energy, heat an element, illuminate a target, or keep processing awake.
Evidence Limits
Records the conditions where the category is believable: calibration, placement, interference, range, drift, maintenance, and failure modes.
A second pass should name the shape of the output, not only the interface. A scalar sensor reports one magnitude such as temperature, pressure, humidity, illuminance, or gas concentration. A vector sensor reports magnitude plus direction or multiple components, such as a three-axis accelerometer, gyroscope, magnetometer, image, or audio feature stream. A one-bit threshold output, an ADC voltage, and an I2C register can all be "digital" somewhere in the chain, but they do not carry the same evidence. The review should say whether the application needs a single value, a direction-aware vector, a time series, or multimedia data before it accepts the signal path.
Two Pairs Worth Naming
Two classification pairs prevent common review mistakes. An absolute sensor claim reports a value against a reference, such as atmospheric pressure or a calibrated temperature. A relative sensor claim reports a change, offset, or difference, such as differential pressure between two ports or a barometer used only to detect floor-to-floor pressure change. The selection record should say which claim is needed; an application that only needs a difference may not need true absolute accuracy, while an application that reports a calibrated environmental value does.
Active and passive sensing are a separate axis. Passive sensors observe energy already present in the scene, such as ambient light, room temperature, or a changing infrared pattern. Active sensors inject energy and then read the response: an ultrasonic distance sensor sends a ping, a SoundWave-style interface emits an 18-22 kHz tone and tracks reflected frequency shifts, and an IR or structured-light depth camera projects light before reading the return. Active sensing records must preserve the emitter, receiver, duty cycle, interference limits, safety or privacy boundary, and recovery behavior after sleep.
Direct and proxy measurements are another useful pair. A direct measurement senses the target quantity itself, such as temperature with a calibrated temperature probe. A proxy measurement estimates the target from a related physical effect, such as dissolved salt inferred from water conductivity, traffic inferred from loop-inductance change, or occupancy inferred from changing infrared patterns. Proxy measurements are valid only when the record includes the calibration curve, confounders, operating range, and retest trigger. For salinity-by-conductivity, for example, temperature, electrode fouling, water chemistry, and reference-solution checks belong in the evidence record.
Beginner Examples
- A thermistor and a digital temperature sensor both measure temperature, but they have different signal paths and calibration burdens.
- A proximity sensor may detect reflected light, sound travel time, capacitance change, or magnetic field; the same user goal can use different principles.
- An accelerometer is a motion sensor, but the design still must decide whether it needs tilt, shock, vibration, step counting, or orientation evidence.
- A digital bus does not make the physical measurement trustworthy by itself; it only changes the communication and parsing problem.
Overview Knowledge Check
4.3 Classification Selection Records
In a project review, classification should become a short selection record. The record lists the measurement goal, candidate classes, output form, interface constraints, power behavior, expected environment, and rejection reasons. It gives the team a way to explain why a sensor category was chosen and why adjacent categories were not.
The strongest records include negative evidence. They state which classes were considered but rejected because of range, response time, mounting, interference, power budget, calibration burden, enclosure limits, or maintenance cost. That prevents the design from drifting back to an attractive but unsuitable sensor later.
How to Classify a Sensor Candidate
- Name the decision. Identify the alarm, display, model input, control action, trend, or diagnosis that will use the measurement.
- Classify the measured quantity. Record the physical condition, units, range, expected dynamics, and location of the measurement.
- Classify the transduction principle. State whether the sensor relies on resistance, capacitance, optical reflection, magnetic field, pressure, heat, acoustic timing, chemical reaction, or another principle.
- Classify the output path. Record analog voltage or current, digital threshold, pulse width, frequency, I2C, SPI, UART, 1-Wire, or another interface used by the controller.
- Classify the evidence constraints. Capture calibration need, placement sensitivity, drift, interference, power state, enclosure, and retest trigger.
Selection Ledger
Practitioner Knowledge Check
4.4 Classification as Boundary Contract
Under the hood, a classification is a contract between physics, electronics, firmware, and operations. The measured condition affects a transducer. The transducer produces a signal. The circuit conditions that signal. The controller samples or receives it. Firmware turns it into data. Operations decide when the evidence has expired. Each classification axis marks a boundary where assumptions can fail.
This is why two sensors in the same broad class can behave differently in a deployed IoT system. They may share the same measurement label but differ in response time, drift, hysteresis, warm-up behavior, cross-sensitivity, mounting sensitivity, bus timing, supply sensitivity, or calibration method. The design review should preserve those differences instead of collapsing them into a single category name.
The physics boundary asks whether the measured phenomenon reaches the sensing element in the same form expected by the datasheet. A light sensor behind smoked plastic, a pressure sensor connected through a narrow tube, and a humidity sensor inside a sealed box may all be classified correctly by type while still seeing a distorted version of the condition. Classification should therefore record placement and coupling assumptions, not only the phenomenon name.
The electrical and firmware boundaries ask whether the signal can be read without changing its meaning. A resistive sensor needs excitation and ADC reference discipline. A pulse-output sensor needs timer resolution and edge handling. A bus sensor needs address, timing, stale-data, and error-code rules. Treating all of those as just digital or analog loses the details that decide whether the field evidence remains trustworthy. For mixed-signal sensors, record the exact crossing point where physical behavior becomes a code, because that is where calibration constants, filtering, and stale reads can quietly replace measurement evidence with software assumptions.
Boundary Checks by Classification Axis
Physics Boundary
Check whether the sensor principle actually observes the target condition under the real material, airflow, enclosure, lighting, vibration, or chemical environment.
Electrical Boundary
Check impedance, biasing, reference voltage, ADC range, pull-ups, cable length, shielding, bus loading, and electromagnetic noise.
Firmware Boundary
Check sample timing, averaging, unit conversion, error codes, address collisions, retries, stale data, and invalid-state handling.
Operations Boundary
Check calibration interval, replacement rule, cleaning, retest trigger, field comparison, and what the system does when evidence weakens.
Failure Patterns
- Category collapse: treating all environmental sensors as equivalent even when one measures air temperature, another board temperature, and another surface temperature.
- Interface blindness: selecting a bus sensor without checking addressing, pull-ups, voltage levels, sample latency, or driver error handling.
- Power-state drift: duty-cycling a sensor to save energy, then reading before warm-up or stabilization has completed.
- Evidence leakage: using a laboratory classification decision after the enclosure, mounting, cable, calibration interval, or environment has changed.
Under-the-Hood Knowledge Check
4.5 Summary
Sensor classification turns a large parts space into a reviewable evidence path. Start with the measured condition and decision, then classify the transduction principle, signal output, interface, power behavior, calibration need, and operational limits. A useful classification does not stop at labels such as motion, environmental, analog, or digital. It explains what the sensor can prove in the real installation and what would require retesting or a different class of sensor.
4.6 Key Takeaway
Classify sensors by the full path from physical condition to decision. The best class is the one whose measurement principle, signal path, power behavior, and evidence limits match the IoT claim you need to make.
4.7 See Also
Sensor Introduction and Fundamentals
Review the measurement evidence boundary that classification supports.
Sensor Specifications
Connect classification choices to range, resolution, accuracy, precision, drift, and response time.
Common Sensors and MEMS
Apply the classification map to common sensor families and module choices.
Sensor Selection Guide
Use classification evidence in a step-by-step sensor selection process.