Temperature and Humidity Sensor Node Design

spacecadets

spacecadets

Make me a temperature and humidity sensor node with Wifi and Bluetooth, powered by USB-C (5V) for consumer use.
It should be a low-power environmental node with a digital T/RH sensor, ultra-low-power MCU with Wi-Fi + Bluetooth (dual-radio) — 2.4 GHz 802.11 b/g/n plus BLE 5.x powered by USB-C (5 V) — USB-C receptacle 5 V default; include reverse/OVP/UVLO/OCP protection and plan for 0.5–3 A sources.

flux

I've made a plan, and started work on it.
Add USB ESD
Choose ESP32-C6
Choose SHT4x sensor
Document requirements
Run design review
No schematic yet

Talk to Flux to get started.

Refine this doc
Ask about this doc
High-Level Execution Plan: USB-C WiFi/Bluetooth Temperature & Humidity Sensor Node
1. Project Definition
  • Build a low-power consumer environmental sensor node powered from USB-C 5 V.
  • Measure temperature and relative humidity using a digital sensor.
  • Use an ultra-low-power MCU/module or SoC with dual-radio support:
    • 2.4 GHz WiFi 802.11 b/g/n
    • Bluetooth Low Energy 5.x
  • Support operation from USB-C 5 V default sources, with practical behavior across approximately 0.5 A to 3 A source capability.
  • Include front-end protection suitable for consumer use: reverse-current/reverse-polarity protection as applicable, over-voltage protection, under-voltage lockout, and over-current protection.
2. System Architecture
Create the design around these functional blocks:
  1. USB-C power input
  2. Input protection and power-path control
  3. 5 V to system rail regulation
  4. MCU / WiFi / Bluetooth radio subsystem
  5. Digital temperature and humidity sensor subsystem
  6. Programming, debug, and manufacturing test access
  7. Status/user interface, if required
  8. Mechanical enclosure and RF/thermal/environmental exposure strategy
3. Requirements Capture and Design Constraints
  • Confirm target supply assumptions:
    • USB-C 5 V only; no USB Power Delivery requirement unless later added.
    • Device must remain safe on higher-current sources while limiting its own current draw.
    • Device should operate within a low-current budget compatible with 0.5 A sources.
  • Define power goals:
    • Active WiFi current budget
    • BLE active current budget
    • Sensor sampling duty cycle
    • Idle/light-sleep/deep-sleep current goals
  • Define product behavior:
    • WiFi provisioning method
    • BLE role during setup and/or operation
    • Sensor reporting interval
    • Firmware update path
    • Local indicators, button, reset behavior, and factory test mode
4. Schematic Execution Plan
4.1 USB-C Input
  • Add USB-C receptacle configured as a 5 V sink.
  • Include required CC termination for default USB-C sink operation.
  • Decide whether to detect advertised Type-C current capability or operate conservatively below the minimum expected source current.
  • Add ESD protection on exposed USB-C pins as appropriate.
4.2 Input Protection / Power Path
  • Add a protection stage covering:
    • Reverse-current / reverse-polarity protection as applicable to the selected architecture
    • Over-voltage protection
    • Under-voltage lockout
    • Over-current protection / current limiting
    • Inrush control if needed
  • Size protection and thermal limits for consumer USB-C sources from approximately 0.5 A to 3 A.
  • Ensure the system does not rely on the source current rating for safety.
4.3 Power Regulation
  • Generate the required logic/radio rail from protected 5 V, typically a regulated low-voltage rail for the MCU, radio, and sensor.
  • Choose a regulator approach that balances:
    • Low quiescent current
    • RF burst current capability
    • Efficiency during active radio transmit
    • Thermal margin
    • Output ripple/noise acceptable to sensor and RF subsystem
  • Partition rails if needed for sensor accuracy, noise control, or power gating.
4.4 MCU / Radio Subsystem
  • Add the ultra-low-power WiFi + BLE-capable MCU/module/SoC.
  • Ensure support for:
    • 2.4 GHz 802.11 b/g/n
    • BLE 5.x
    • Low-power sleep modes
    • Sufficient GPIO/I2C/SPI/UART resources
    • Secure boot / OTA capability if required
  • Provide required clocks, flash, strapping pins, boot-mode controls, reset, and programming/debug access.
  • Include RF matching/antenna strategy or module antenna keepout as required.
4.5 Temperature / Humidity Sensor
  • Add a digital temperature and relative humidity sensor interface.
  • Keep the sensor thermally and environmentally isolated from heat-generating components.
  • Provide pullups, filtering, and optional power gating as needed.
  • Plan mechanical exposure path to ambient air while protecting against contamination, ESD, and handling.
4.6 Test, Debug, and Manufacturing
  • Add test points for:
    • USB 5 V input after receptacle
    • Protected 5 V rail
    • Regulated system rail(s)
    • Reset/boot/programming signals
    • Digital sensor bus
    • Ground
  • Include firmware programming/debug interface appropriate for the selected MCU/module.
  • Define factory test procedure at a high level: power-on, rail check, sensor read, WiFi/BLE radio check, current consumption check.
5. PCB Layout Execution Plan
  • Place the USB-C receptacle at the board edge with robust mechanical anchoring.
  • Keep high-current/protection path short and appropriately wide.
  • Place input protection close to the USB-C connector.
  • Place regulator close to the MCU/radio supply pins; use tight decoupling loops.
  • Follow RF layout guidance from the selected MCU/module vendor.
  • Maintain antenna keepout and ground clearance exactly as required by the selected RF implementation.
  • Physically separate the temperature/humidity sensor from:
    • Regulator heat
    • MCU/radio heat
    • USB-C connector heat and metal mass
    • High-current copper paths
  • Add slots, cutouts, edge placement, or enclosure vents as needed to improve ambient sensing accuracy.
  • Maintain ESD/EMC practices for consumer handling and USB attachment.
6. Firmware / System Bring-Up Plan
  • Implement staged firmware bring-up:
    1. Boot and debug interface validation
    2. Power-mode validation
    3. Sensor communication and calibration handling
    4. BLE provisioning or setup flow
    5. WiFi connection and data reporting
    6. OTA/update path if required
    7. Low-power duty-cycled operation
  • Include fault handling for:
    • Brownout / UVLO events
    • WiFi connection loss
    • Sensor read failure
    • Over-current or power fault indication if available
7. Review and Verification Plan
  • Run schematic ERC and PCB DRC in Flux.
  • Review USB-C sink implementation.
  • Review protection chain behavior against expected USB-C 5 V source cases.
  • Review regulator current, transient response, and thermal margins.
  • Review RF antenna placement and keepout.
  • Review sensor thermal placement and airflow strategy.
  • Verify no unnecessary leakage paths conflict with low-power goals.
  • Verify all MPNs, footprints, symbols, and datasheets before release.
8. Prototype Validation Plan
  • Power validation:
    • Startup from 5 V USB-C
    • Operation from low-current and high-current USB-C sources
    • Inrush/current-limit behavior
    • OVP/UVLO/OCP response
    • Regulator ripple and transient response during RF bursts
  • Functional validation:
    • Temperature and humidity readings
    • WiFi connection and data transmission
    • BLE advertising/provisioning/connection
    • Sleep and wake behavior
  • Environmental/mechanical validation:
    • Sensor response time
    • Self-heating error
    • Enclosure airflow impact
    • ESD and handling robustness
  • Compliance-oriented pre-checks:
    • USB-C attachment behavior
    • RF layout/module certification constraints
    • EMC risk review
9. Key Risks / Decisions for Execution Agent
  • Whether to use a certified radio module or bare SoC.
  • Whether to detect USB-C advertised current or operate conservatively below the minimum supported current.
  • Protection IC/power-path topology selection and current-limit target.
  • Regulator topology optimized for low sleep current and high RF burst current.
  • Sensor placement and enclosure airflow strategy to minimize self-heating and lag.
  • Production test access versus board size and enclosure constraints.
10. Expected Deliverables
  • Block diagram and requirements notes.
  • Schematic with annotated power tree and protection chain.
  • PCB layout with RF, USB-C, thermal, and sensor-placement considerations addressed.
  • BOM with lifecycle/availability checked.
  • Bring-up checklist and prototype validation checklist.
  • Manufacturing/test notes for consumer-use production readiness.

  • 1. Project Definition

  • 2. System Architecture

  • 3. Requirements Capture and Design Constraints

  • 4. Schematic Execution Plan

  • 4.1 USB-C Input

  • 4.2 Input Protection / Power Path

  • 4.3 Power Regulation

  • 4.4 MCU / Radio Subsystem

  • 4.5 Temperature / Humidity Sensor

  • 4.6 Test, Debug, and Manufacturing

  • 5. PCB Layout Execution Plan

  • 6. Firmware / System Bring-Up Plan

  • 7. Review and Verification Plan

  • 8. Prototype Validation Plan

  • 9. Key Risks / Decisions for Execution Agent

  • 10. Expected Deliverables

Spatial Jade Teleporter

Spatial Jade Teleporter thumbnail
Welcome to your new project. Imagine what you can build here.

Properties

Properties describe core aspects of the project.

Pricing & Availability

See prices from popular manufacturers for your project.

Controls