Chapter 6: Embedded Peripheral Management

The microcontroller core is rarely the dominant power consumer in an embedded system. Sensors, radios, displays, and communication buses often draw far more. This chapter covers strategies for managing these peripherals to minimize power consumption without sacrificing functionality.

6.1 The Peripheral Power Budget

Before optimizing, audit what each component actually draws. A typical IoT sensor node might look like:

The OLED and GSM modem standby currents are significant even when not actively used. If the device spends most of its time sleeping, these standby currents can become the dominant power consumers.

6.2 Duty Cycling Sensors

Most sensors have a measurement cycle: power on, wait for stabilization, take reading, power off. The stabilization time (warm-up) is the key constraint.

Temperature/humidity sensors (DHT22, SHT31): DHT22 stabilizes in ~2 s after power-on. If sampling every 60 s, the sensor only needs power for 2 s out of 60 — a 3.3% duty cycle.

Gas sensors (MQ series): These require a 24–48 hour burn-in for calibration and a 20-second pre-heat before each reading. They draw 100–200 mA during preheat — making them unsuitable for battery operation without careful duty-cycle design.

Control via GPIO load switch:

# MicroPython: power-cycle a sensor on a GPIO-controlled switch
import machine, time

SENSOR_PWR = machine.Pin(14, machine.Pin.OUT)

def read_sensor():
    SENSOR_PWR.value(1)      # power on
    time.sleep_ms(100)       # stabilization
    # ... read I2C/SPI/UART data ...
    SENSOR_PWR.value(0)      # power off
    return reading

6.3 WiFi Power Management on ESP32

WiFi is the single largest power consumer in most ESP32 projects. Key strategies:

Use static IP instead of DHCP: DHCP negotiation adds 500–1000 ms to connection time, during which the radio draws ~100 mA. Configuring a static IP reduces connection time to ~300–500 ms.

Reduce transmit power: The ESP32 transmits at up to 20 dBm. For short-range applications (same room as the router), 10–13 dBm is sufficient and reduces TX current from ~260 mA to ~180 mA.

import network
sta = network.WLAN(network.STA_IF)
sta.active(True)
sta.config(txpower=13)  # dBm

Use MQTT instead of HTTP: An MQTT publish after connection is one round-trip packet. HTTP adds TLS handshake, headers, and acknowledgment overhead. For small payloads, MQTT reduces active time by 50–80%.

Always disconnect before sleep: Failing to call sta.disconnect() and sta.active(False) before deep sleep leaves the radio partially active during the sleep entry sequence.

6.4 Bluetooth Low Energy (BLE) vs WiFi

BLE (Bluetooth Low Energy) is designed for low-power operation. A BLE advertisement packet can be sent in ~1.5 ms at ~15 mA — compared to WiFi’s 300–500 ms connection + transmission cycle at 100–260 mA.

For applications where a phone or gateway acts as the receiver, BLE advertising is often more power-efficient than WiFi, especially for short payloads.

Trade-offs:

• BLE range is shorter (10–50 m vs 50–100 m for WiFi indoors)
• BLE requires a receiver within range (phone, gateway, BLE scanner)
• WiFi can reach the internet directly; BLE requires a bridge

For indoor sensor nodes near a phone or dedicated BLE gateway, BLE is typically 10–50× more power-efficient than WiFi.

6.5 Display Management

OLED and LCD displays are significant power consumers for battery devices. Strategies:

Turn off the display during sleep: Even in display-off mode, many OLEDs draw 1–5 mA through the charge pump. Use the display’s power-down command or cut power via a load switch.

Reduce brightness: OLED power consumption scales roughly linearly with the number of lit pixels and brightness level. A fully bright white screen draws ~30 mA; the same content at half brightness draws ~15 mA.

Display only when needed: Use a motion sensor, button press, or proximity sensor to wake the display only when a user is present. This can reduce average display power from 20 mA to 0.1 mA or less.

6.6 Communication Bus Management

SPI, I2C, and UART hold clock lines and pull resistors active even when not in use.

• I2C pull-up resistors (typically 4.7 kΩ to 3.3 V) draw current whenever SDA or SCL is held low. On a quiet bus this is negligible, but a stuck bus (sensor not releasing the line) can drain significant current.
• SPI chip-select lines left inactive-high with pull-up resistors add quiescent current. Drive CS high explicitly before sleep.
• UART transmitters left enabled draw slightly more than when disabled. Call uart.deinit() in MicroPython before sleeping.

For critical low-power designs, consider cutting the entire sensor power domain (VCC) via a load switch. This guarantees zero current from all sensors, pull resistors, and any leakage paths through the bus.