Drone Sensor Node

flux

Design it as two separate electronic systems: a safety-critical flight stack and a non-critical sensor payload.
Recommended schematic architecture 
Text
4S/6S LiPo
  |
  +-- Fuse / anti-spark / TVS
  |
  +-- 4-in-1 ESC --> Motors
  |
  +-- 5.2 V, >=5 A buck --> Autopilot + RC receiver + GNSS
  |
  +-- 5 V, 2 A filtered buck --> Companion computer / payload
  |
  +-- 3.3 V low-noise rail --> Environmental sensors

Autopilot
  +-- DShot/PWM --> ESC
  +-- UART --> GNSS + compass
  +-- UART --> telemetry radio
  +-- UART/CAN --> sensor controller
  +-- I2C/SPI --> rangefinder / optical flow
  +-- ADC <-- battery voltage/current monitor
  +-- GPIO --> buzzer, safety switch, status LEDs

Sensor controller
  +-- I2C --> temperature/humidity and other sensors
  +-- SPI --> local flash or microSD
  +-- UART/CAN --> autopilot
  +-- Wi-Fi/BLE --> setup and post-flight data download
1. Use a proven autopilot
Base the aircraft around a Pixhawk-compatible flight controller running ArduPilot or PX4. Designing the IMU flight controller from scratch requires careful sensor redundancy, vibration control, controlled-impedance interfaces, real-time firmware, and extensive validation.
Your custom schematic should initially cover:
  • Power distribution and monitoring
  • Sensor payload
  • Autopilot interfaces
  • Payload isolation and protection
  • Connectors and service/debug access
2. Power input and distribution
For a 4S LiPo, design for approximately 12–17 V; a 6S system needs approximately 18–25.2 V.
Include:
  • Input fuse sized from measured maximum load
  • Reverse-polarity protection
  • TVS diode selected for the battery voltage and transients
  • Bulk low-ESR capacitance near the ESC
  • Battery voltage divider into the autopilot ADC
  • Bidirectional current/power monitor
  • Separate buck regulators for flight electronics and noisy payloads
  • LC or ferrite filtering for GNSS, sensors, and radios
  • Regulator enable controls and test points
Do not route motor current through the sensor PCB. Keep the high-current battery-to-ESC path short and physically separate.
3. Autopilot interfaces
Expose keyed, locking connectors for:
  • ESC signals and telemetry
  • Dual power input where supported
  • GNSS/compass
  • RC receiver
  • Telemetry radio
  • CAN peripherals
  • Payload UART/CAN
  • SWD/JTAG and console UART
Use 3.3 V logic unless the selected autopilot explicitly specifies otherwise. Add ESD protection on external connectors and series damping resistors on fast clock/data lines.
4. Sensor payload
The existing SiWG917/SHT41 concept can become the payload controller, but it should be revised for drone power and measurement integrity:
  • Add a battery-compatible buck input or accept a regulated 5 V payload supply.
  • Connect to the autopilot through UART or CAN.
  • Add local flash or microSD so measurements survive radio loss.
  • Timestamp each reading and associate it with autopilot position.
  • Add a hardware watchdog and brownout-safe storage behavior.
  • Keep Wi-Fi/BLE for configuration and data retrieval—not flight safety.
  • Mount the SHT41 away from regulators, MCU heat, sunlight, battery airflow, and motor/propeller turbulence.
For accurate ambient readings, consider a remote cabled sensor in a ventilated radiation shield rather than placing it directly on the main PCB.
5. Essential safety behavior
Implement these independently of Wi-Fi/BLE:
  • RC/manual takeover
  • Geofence
  • Return-to-home on lost control link
  • Low-battery warning and landing
  • GNSS-loss behavior
  • Payload failure that cannot reset or power-cycle the autopilot
  • Default-off payload outputs after reset
  • Buzzer and high-visibility status indication
Design process
  1. Freeze battery voltage, aircraft size, payload mass, peak current, sensors, autopilot, and required flight time.
  2. Produce a power budget covering continuous, peak, startup, and stalled loads.
  3. Draw the block diagram and define every connector/pinout.
  4. Capture power protection and regulators first.
  5. Add autopilot interfaces and power monitoring.
  6. Add the sensor controller, storage, and sensors.
  7. Run ERC and review every power domain and failure path.
  8. Lay out high-current power first, then regulators, interfaces, and sensors.
  9. Validate power rails with motors disconnected before installing propellers.
A concrete schematic cannot be safely selected until the battery (4S or 6S), autopilot model, motor/ESC current, sensor list, and required flight time are fixed. No project changes were made. Execution stopped because your ACUs ran out.
Sign up to send

Files

Schematic

Layout

3D View

U1

USB-C WiFi BLE TH Sensor

USB-C WiFi BLE TH Sensor thumbnail