15  How to Read Sensor Datasheets

In 60 Seconds

Sensor datasheets are essential reading – they contain operating voltage (check 3.3V vs 5V compatibility!), current consumption (for battery life), accuracy and resolution (remember: resolution is NOT accuracy), operating range (sensor may report garbage outside it), response time, and interface requirements. Design for “maximum” specs, not “typical.” Always check footnotes – accuracy specs often apply only under ideal lab conditions.

Key Concepts
  • Absolute Maximum Ratings: The limits beyond which permanent device damage occurs; these are NOT operating conditions — they define destruction thresholds and must never be exceeded, even momentarily
  • Recommended Operating Conditions: The voltage, temperature, and load ranges within which the device is guaranteed to meet its specified performance; always design within these limits with additional margin
  • Typical vs. Guaranteed Specifications: Typical values represent average behavior but are NOT guaranteed; maximum and minimum values define the specification limits all devices are tested against — always design for worst-case min/max, not typical
  • Electrical Characteristics Table: The core performance specifications — output voltage, supply current, response time, accuracy, noise; always check the measurement conditions (temperature, supply voltage) listed for each specification
  • Pin Configuration / Pinout Diagram: Maps physical package pins to electrical functions; critical to verify before soldering — pinouts differ between packages (SOT-23, DIP, QFN) and sometimes between variants of the same sensor family
  • Application Circuit / Reference Design: A validated example circuit showing recommended external components (decoupling capacitors, pull-up resistors, filters); following the reference design avoids most common interfacing mistakes
  • Timing Diagram: Waveform illustrations showing required signal timing for digital protocols; defines setup time, hold time, minimum clock period, and startup sequences that firmware must respect
  • Revision History: Documents specification changes between datasheet versions; critical to check when switching between revision levels — accuracy specifications and pin configurations sometimes change between revisions

Learning Objectives

After completing this chapter, you will be able to:

  • Navigate sensor datasheets to locate critical specifications such as voltage, current, and accuracy
  • Interpret electrical characteristics, performance tables, and footnote conditions in real datasheets
  • Detect specification traps (typical vs. maximum, conditional footnotes, floating pins) that cause project failures
  • Calculate power budgets and ADC resolution requirements from datasheet parameters
  • Compare competing sensors using a weighted decision matrix derived from datasheet data

A datasheet is like an instruction manual and safety guide for an electronic component, all rolled into one document. It tells you exactly what voltage to use (getting this wrong can instantly destroy the part), how to wire it up, and what kind of readings to expect. Learning to read datasheets is one of the most practical skills in electronics – once you can do it, you can work with almost any sensor or component.

15.1 Prerequisites

15.2 Why Datasheets Matter

The datasheet is your sensor’s user manual, specification sheet, and warning label all in one. Skipping the datasheet leads to: - Damaged components (wrong voltage) - Unreliable readings (wrong interface) - Wasted time (missing features) - Project failure (impossible requirements)

15.3 Anatomy of a Sensor Datasheet

Most sensor datasheets follow a similar structure:

Section What You’ll Find Priority
Front Page Part number, key specs, package Read first
Features Bullet points of capabilities Skim
Applications Suggested use cases Helpful for context
Block Diagram Internal architecture Understand operation
Pin Configuration Pinout and connections Critical for wiring
Electrical Characteristics Voltage, current, timing Critical
Performance Specifications Accuracy, range, resolution Match to requirements
Application Circuit Recommended schematic Use this!
Package Information Physical dimensions For PCB design
Ordering Information Part number variants For purchasing

15.4 Critical Specifications to Check

15.4.1 1. Operating Voltage (Vcc/Vdd)

What it tells you: The voltage range the sensor can handle.

Example: BMP280 - Operating voltage: 1.71V to 3.6V - Interface voltage: 1.2V to 3.6V

Trap: ESP32 is 3.3V, Arduino Uno is 5V. Using BMP280 with 5V Arduino requires level shifting!

15.4.2 2. Operating Current

What it tells you: Power consumption for battery life calculations.

Example: BME280 - Sleep mode: 0.1 uA - Normal mode: 3.6 uA - Forced mode (during measurement): 340 uA

Quick estimate: On a 2000 mAh battery taking 1 reading/min in forced mode, the BME280 alone would last centuries theoretically. The microcontroller and radio dominate real power budgets. See the detailed BME280 walkthrough below for full calculation.

15.4.3 3. Accuracy and Resolution

What it tells you: How good the measurements are.

Example: DHT22 - Temperature accuracy: ±0.5°C - Temperature resolution: 0.1°C - Humidity accuracy: ±2% RH - Humidity resolution: 0.1% RH

Trap: Resolution of 0.1°C does not mean accuracy is 0.1°C! The sensor displays 25.3°C but the true value could be 24.8°C to 25.8°C.

15.4.4 4. Operating Range

What it tells you: Where the sensor works correctly.

Example: DHT22 - Temperature range: -40°C to 80°C - Humidity range: 0-100% RH (20-80% RH for best accuracy)

Trap: “Humidity range 0-100% RH” with note “Accuracy ±2% at 20-80% RH” means accuracy degrades outside 20-80%.

15.4.5 5. Response Time

What it tells you: How fast the sensor reacts.

Example: DHT22 - Sampling period: 2 seconds minimum - Response time (temperature): 6-10 seconds to 63% of step change

Trap: “Sampling period 2 seconds” means you CANNOT read faster than every 2 seconds. Doing so gives stale data.

15.4.6 6. Interface Type

What it tells you: How to connect to your microcontroller.

Common interfaces:

  • I2C: 2 wires (SDA, SCL), multiple devices on same bus
  • SPI: 4 wires (MOSI, MISO, SCLK, CS), faster, one device per CS
  • Analog: 1 wire + ground, needs ADC
  • UART: 2 wires (TX, RX), serial communication
  • 1-Wire: 1 wire + ground (like DS18B20)

15.5 Datasheet Traps That Catch Beginners

Trap 1: Accuracy “Typical” vs “Maximum”

What datasheet says: “Accuracy: ±0.3°C typical, ±0.5°C maximum”

What it means: Most sensors are ±0.3°C, but yours could be ±0.5°C. Design for maximum, not typical!

Trap 2: Conditions in Footnotes

What datasheet says: “Accuracy: ±0.1°C” Footnote: ”At 25°C ambient, Vcc = 3.3V ±1%, after 30 min warm-up”

What it means: That accuracy only applies under ideal lab conditions. In the field, expect worse.

Trap 3: Multiple I2C Addresses

What datasheet says: “I2C Address: 0x76 or 0x77 (selectable via SDO pin)”

What it means: Address depends on how you wire SDO. If SDO is not connected (floating), behavior is undefined. Always tie to VCC or GND.

Trap 4: Pull-Up Resistor Requirements

What datasheet says: “I2C interface requires external pull-up resistors”

What it means: Without pull-ups, I2C won’t work. Some breakout boards include them, some don’t. Check the schematic!

15.6 Where to Find Datasheets

Official Sources (Always Use These First): - Manufacturer Website: Bosch, TE Connectivity, Texas Instruments, STMicroelectronics - Distributor Sites: DigiKey, Mouser, Arrow have verified datasheets - Adafruit / SparkFun breakout board documentation (often includes tutorials + datasheet links)

Search Tips:

  • Google: “[Sensor Part Number] datasheet filetype:pdf”
  • Example: “DHT22 datasheet filetype:pdf”
  • Verify the sensor part number on your physical component (printed on chip)

Red Flags (Avoid These Datasheets): - No manufacturer logo or company name - Poor English translation with technical errors - Missing electrical specifications - Different part numbers on each page (copy-paste errors)

15.7 Worked Example: Reading the BME280 Datasheet

Let us walk through reading a real datasheet – the Bosch BME280, a popular combined temperature, humidity, and pressure sensor used in weather stations, indoor air quality monitors, and IoT environmental sensing.

Step 1: Front page – identify the key specifications

Specification Value from Datasheet What It Means for Your Project
Supply voltage 1.71V to 3.6V Works directly with ESP32 (3.3V) and nRF52 (1.8V). Do NOT use with 5V Arduino without level shifter.
Interface I2C (up to 3.4 MHz) or SPI (up to 10 MHz) Use I2C for simplicity (2 wires); SPI for speed (4 wires). I2C address: 0x76 or 0x77.
Pressure range 300 to 1100 hPa Covers all terrestrial altitudes from Dead Sea (-430m) to Everest Base Camp (5364m).
Temperature range -40 to +85°C Full industrial range. Accuracy degrades below -20°C per footnote.
Humidity range 0 to 100% RH Full range. Best accuracy at 20-80% RH.

Step 2: Electrical characteristics – calculate power budget

Mode Current Duration Use Case
Sleep 0.1 uA Between measurements Battery-optimized IoT
Forced 340 uA ~10 ms per measurement Periodic readings
Normal 3.6 uA Continuous Always-on weather station

Battery life calculation (CR2032 coin cell, 220 mAh):

Scenario: 1 reading per minute in forced mode
- Active: 340 uA x 10ms = 3.4 uAs per reading = 0.00094 uAh
- Sleep: 0.1 uA x 59.99s = 5.999 uAs = 0.00167 uAh
- Per minute total: 0.00261 uAh
- Per day: 0.00261 x 1440 = 3.76 uAh = 0.00376 mAh
- Battery life: 220 mAh / 0.00376 mAh/day = 58,500 days (160 years!)

Reality check: The BME280 itself lasts effectively forever on a coin cell. Your microcontroller and radio will be the actual power bottleneck. An ESP32 in deep sleep draws 10 uA – 100x more than the BME280 in sleep mode.

15.7.1 Sensor Battery Life Calculator

Use this calculator to estimate battery life for any sensor based on datasheet specifications. Enter the values from your sensor’s electrical characteristics table.

Step 3: Performance specifications – accuracy under real conditions

Parameter Typical Accuracy Maximum Error (Worst Case) Condition Footnote
Temperature ±0.5°C ±1.0°C At 0-65°C range. Wider range = worse accuracy.
Humidity ±3% RH ±5% RH At 25°C, 20-80% RH. Outside this range, accuracy degrades.
Pressure ±0.12 hPa ±1.0 hPa At 25°C, 900-1100 hPa. After 1 ms measurement time.

Critical insight from footnotes: The BME280 humidity sensor has hysteresis of ±1% RH. If the sensor experiences 100% RH (condensation), the humidity reading will be offset by up to 1% even after the sensor dries. Prolonged exposure to >80% RH accelerates accuracy degradation. For outdoor weather stations, consider adding a sensor cap with hydrophobic membrane.

Step 4: Application circuit – wiring it up

BME280 I2C Wiring to ESP32:
  BME280    ESP32
  ------    -----
  VCC   --> 3.3V
  GND   --> GND
  SDA   --> GPIO 21 (with 4.7 kOhm pull-up to 3.3V)
  SCL   --> GPIO 22 (with 4.7 kOhm pull-up to 3.3V)
  SDO   --> GND (sets address to 0x76)
  CSB   --> VCC (disables SPI, enables I2C)

Common wiring mistakes with BME280:

  1. Forgetting pull-up resistors: Some breakout boards (Adafruit, SparkFun) include them; generic modules often do not. Without pull-ups, I2C communication fails silently – no error, just no response.
  2. Leaving CSB floating: If CSB is not tied to VCC, the sensor may randomly switch between I2C and SPI modes.
  3. Wrong I2C address: SDO to GND = 0x76, SDO to VCC = 0x77. If your code uses 0x76 but SDO is floating, the sensor appears intermittently.

15.8 ADC Resolution: Matching Datasheet Specs to Your Hardware

Many sensor datasheets specify an analog output voltage (e.g., “10 mV/°C”). To use these sensors, you must verify that your microcontroller’s ADC resolution is fine enough to achieve the measurement granularity your application needs. Here is how to calculate it:

ADC Resolution = V_ref / 2^n

Where:
  V_ref = Reference voltage (3.3V for ESP32, 5V for Arduino)
  n     = Number of ADC bits

Examples:
  Arduino Uno (10-bit, 5V ref):
    Resolution = 5V / 1024 = 4.88 mV per step

  ESP32 (12-bit, 3.3V ref):
    Resolution = 3.3V / 4096 = 0.806 mV per step

LM35 temperature sensor example:

The LM35 outputs 10 mV per degree Celsius. On a 12-bit ESP32 (0.806 mV per step):

Temperature resolution = ADC step / Sensitivity
                       = 0.806 mV / 10 mV/°C
                       = 0.0806°C per ADC step

For a reading of ADC value 310:
  Voltage = 310 × 0.806 mV = 249.86 mV
  Temperature = 249.86 mV / 10 mV/°C = 24.99°C

ADC resolution determines measurement granularity. For ESP32’s 12-bit ADC at 3.3V:

\[\text{Resolution} = \frac{V_{ref}}{2^n} = \frac{3.3}{4096} = 0.806 \text{ mV/step}\]

The LM35 has 10 mV/°C sensitivity, so temperature resolution is:

\[\Delta T = \frac{0.806 \text{ mV}}{10 \text{ mV/°C}} = 0.081 \text{ °C per ADC step}\]

But the LM35’s ±0.5°C accuracy is 6× worse than ADC resolution. Using a 10-bit Arduino (4.88 mV/step → 0.488°C resolution) wouldn’t meaningfully degrade system accuracy — it’s sensor accuracy, not ADC resolution, that limits precision here.

15.8.1 ADC Resolution Calculator

Enter your microcontroller’s ADC specifications and sensor sensitivity from the datasheet to calculate measurement resolution.

15.9 Worked Example: Selecting Between Two Temperature Sensors Using Datasheets

Scenario: You are designing a cold-chain monitoring system for vaccine transport. Vaccines must be stored between 2-8°C, and you need to detect excursions within ±0.5°C. Battery life must exceed 2 years with readings every 60 seconds. Compare two candidate sensors using their datasheets.

Candidate A: Texas Instruments TMP117

Specification Value Source (Datasheet Section)
Accuracy ±0.1°C (typical), ±0.2°C (max) at -20 to +50°C Table 6.5, “Accuracy vs Temperature”
Resolution 0.0078°C (16-bit) Section 7.3
Supply current (active) 3.5 uA (one-shot mode) Table 6.3
Supply current (shutdown) 250 nA Table 6.3
Conversion time 15.5 ms (default) Table 6.4
Interface I2C, up to 4 addresses Section 7.5
Price $1.68 (qty 1000) Distributor pricing

Candidate B: Sensirion STS40

Specification Value Source (Datasheet Section)
Accuracy ±0.2°C (typical), ±0.4°C (max) at 0 to +65°C Table 1
Resolution 0.01°C Section 3.2
Supply current (active) 60 uA (single-shot, high precision) Table 3
Supply current (idle) 0.3 uA Table 3
Conversion time 6.9 ms (high precision) Table 5
Interface I2C, 2 addresses Section 5
Price $0.89 (qty 1000) Distributor pricing

Step 1: Accuracy requirement check

Your application needs ±0.5°C. Design for maximum specification:

  • TMP117: ±0.2°C max – passes with 0.3°C margin
  • STS40: ±0.4°C max – passes with 0.1°C margin

Both pass, but TMP117 provides more margin for calibration drift over the 2-year deployment.

Step 2: Battery life calculation (CR2477 coin cell, 1000 mAh)

TMP117: One reading per minute

Active: 3.5 uA x 15.5 ms = 0.0543 uAs = 0.0000151 uAh per reading
Shutdown: 0.25 uA x 59.98 s = 14.995 uAs = 0.00416 uAh per cycle
Per minute: 0.00418 uAh
Per day: 6.02 uAh = 0.00602 mAh
Battery life: 1000 / 0.00602 = 166,000 days (455 years theoretical)

STS40: One reading per minute

Active: 60 uA x 6.9 ms = 0.414 uAs = 0.000115 uAh per reading
Idle: 0.3 uA x 59.99 s = 17.997 uAs = 0.005 uAh per cycle
Per minute: 0.00512 uAh
Per day: 7.37 uAh = 0.00737 mAh
Battery life: 1000 / 0.00737 = 135,700 days (371 years theoretical)

Both far exceed the 2-year requirement. The microcontroller and radio (BLE or LoRaWAN) will dominate power consumption, not the sensor.

Step 3: Decision matrix

Criterion Weight TMP117 Score STS40 Score
Accuracy margin 30% 9/10 6/10
Power consumption 10% 9/10 8/10
Price (x1000 units) 25% 6/10 ($1,680) 9/10 ($890)
Calibration stability 20% 9/10 (NIST traceable) 7/10
Ease of integration 15% 8/10 8/10
Weighted total 8.10 7.45

Decision: TMP117 wins for vaccine cold-chain despite costing $790 more per 1,000 units. The accuracy margin and NIST-traceable calibration justify the premium in a medical compliance context where a false excursion reading could trigger a $50,000 vaccine disposal event.

For a non-medical application (e.g., HVAC monitoring at ±1°C), the STS40 would be the clear winner – nearly half the cost with adequate accuracy.

15.10 Datasheet Checklist for Your Project

Before ordering sensors, check these off:

Key Takeaway

The datasheet is your sensor’s complete user manual. Always check voltage compatibility first (prevents hardware damage), design for maximum specs (not typical), read the footnotes (accuracy conditions), verify interface requirements (pull-ups, timing, addresses), and calculate power consumption for battery life estimates. Skipping the datasheet is the number one cause of sensor project failures.

Max the Microcontroller was reading a datasheet – a special instruction manual that comes with every sensor. “Think of it like the rules for a board game,” Max explained to the Squad.

“The first page tells you the sensor’s name and superpowers,” Max said. “Then there is a section on VOLTAGE – this is SUPER important! If I run on 3.3 volts and the sensor needs 5 volts, we need a special translator (level shifter) or we could damage each other!”

Sammy the Sensor pointed to the accuracy section: “See where it says ‘plus or minus 0.5 degrees typical, plus or minus 1.0 degrees maximum’? That means MOST of us are within half a degree, but some unlucky ones could be off by a whole degree. Always plan for the worst case!”

Lila the LED noticed tiny text at the bottom: “Look – a footnote! It says the accuracy is only guaranteed at room temperature after a 30-minute warm-up. In the freezing cold, accuracy could be worse!”

Bella the Battery loved the power section: “It tells me exactly how many microamps the sensor uses in sleep mode. I can calculate that on a 2000 milliamp-hour battery, this sensor could run for YEARS if we use deep sleep!”

“Bottom line,” said Max: “ALWAYS read the datasheet. It saves time, money, and broken parts!”

15.11 Concept Relationships

Concept Related To Connection Type
Accuracy Spec Calibration Interval Better accuracy sensors can go longer between calibrations
Operating Voltage Level Shifters Mismatch requires voltage translation circuits
Supply Current Battery Life Directly determines power budget and battery sizing
I2C Address SDO Pin Connection GND vs VCC sets sensor address (0x76 vs 0x77)
Response Time Control Loop Speed Slow sensors limit how fast you can react to changes

15.12 Summary

Key datasheet reading takeaways:

  1. Always read the datasheet - Don’t rely on tutorials alone
  2. Check voltage compatibility first - Prevents damage
  3. Design for maximum specs - Not typical
  4. Read the footnotes - Conditions matter
  5. Verify interface requirements - Pull-ups, addresses, timing

15.13 Try It Yourself

Challenge: Download the SHT31 datasheet and answer these questions:

  1. What is the maximum temperature accuracy spec at 25°C?
  2. What supply voltage range is acceptable?
  3. What are the two possible I2C addresses?
  4. How much current does the sensor draw during a measurement?
  5. What is the maximum I2C clock frequency supported?
Click for answers
  1. ±0.3°C (Table 1, maximum column at 0-90°C range; typical is ±0.2°C)
  2. 2.15V to 5.5V (Section 2.1, Electrical Specifications)
  3. 0x44 and 0x45 (depends on ADDR pin connection)
  4. 1500 µA (1.5 mA) during measurement (Table 1)
  5. 1000 kHz (1 MHz) (Table 2, I2C Characteristics)
Key insight: Notice the difference between “typical” (±0.2°C) and “maximum” (±0.3°C) accuracy. Always design for maximum.

Common Pitfalls

Typical values represent average behavior at 25 C under nominal conditions. Production parts vary across their min/max specification range. Always design for the worst-case min or max value to ensure reliable operation across all units and temperature conditions.

Accuracy and response time specifications are only valid under the specific conditions listed in the measurement conditions column. A sensor specified as +-0.5 C at 25 C may only achieve +-1.5 C at 0 C. Always read the footnotes and test conditions alongside the specification values.

Manufacturers update datasheets to correct specification errors, change pin assignments, and add errata notes. Always download the latest revision directly from the manufacturer’s official website, not a third-party reseller.

The same sensor in different packages (DIP, SOIC, QFN) has different physical pin locations. Switching from a prototyping DIP to a production QFN without re-checking the QFN pinout is a common cause of production PCB failures. Verify the pinout for your specific package variant.

15.14 What’s Next

Now that you can read datasheets, explore these related topics:

Chapter Description
Common IoT Sensors Apply your datasheet skills to popular sensors (DHT22, BMP280, MPU6050)
Hands-On Labs Practice reading datasheets with physical sensors and wiring exercises
Selection Guide Compare datasheet specs systematically using weighted decision matrices
Common Mistakes Diagnose voltage mismatch, I2C address conflicts, and pull-up issues
Signal Processing Connect sampling rate specs from datasheets to signal quality requirements

Continue to Common IoT Sensors ->