I can’t start executing the PCB design because the session has no remaining credits for project edits or tool-based verification.
Current project state:
- Project is still empty: 0 components, 0 nets.
- No schematic, layout, or documentation has been created yet.
- The project still has its draft placeholder name and default description.
To design a complete ultra-miniature ESP32 drone controller PCB, I’ll need the missing requirements after credits are available, especially:
- Target board size and shape constraints
- ESP32 variant/module preference, e.g. ESP32-C3, ESP32-S3, ESP32-WROOM, bare chip/module
- Battery type and voltage, likely 1S LiPo
- Motor type: brushed coreless motors or brushless ESC outputs
- Number of motors: likely 4
- IMU preference or acceptable default
- Receiver/control method: WiFi, BLE, ESP-NOW, SBUS/CRSF, etc.
- Charging requirement: USB-C LiPo charging on-board or external charging
- Sensors: barometer, magnetometer, optical flow, ToF, etc.
- Programming/debug connector preference
- Assembly preference: hand-solderable vs ultra-miniature SMT only
Recommended default architecture once work can continue:
- ESP32-C3 or ESP32-S3 module for WiFi/BLE control
- 6-axis IMU close to board center
- 1S LiPo input with protection and battery monitoring
- USB-C for power/programming if size allows
- 4 motor driver outputs for brushed motors, or 4 PWM/DSHOT outputs for external brushless ESCs
- 3.3 V regulator sized from a full power budget
- Decoupling on every IC power pin
- Boot/programming circuitry, reset button, status LEDs, and test pads
- Compact 2-layer or 4-layer PCB depending on RF/size constraints
When credits are available, the next step is to complete the requirement list, then I can build the schematic, verify it against datasheets, run review checks, create bring-up/firmware documentation, and only then move to PCB layout with your confirmation.