ESP-Drone

What the base configuration contains

The V1.2 parts list specifies an ESP32-S2-WROVER/MPU6050 main board, four 716 motors with rubber mounting rings, two A and two B 46 mm propellers, a 300 mAh 1S LiPo battery, a separate 1S charger and pin headers. It lists 720 motors, 55 mm propellers and a 350 mAh battery as alternatives. Selecting the 720 motor also requires changing the motor setting in menuconfig; these alternatives are not extra items to add to the base bill. A current delivered cost was not established. [S005]

The selected board integrates the airframe arrangement rather than using the separate frame required by the older ESPlane-FC-V1. The assembly guide includes motor soldering and a separate A/B propeller-direction diagram. Follow the diagram for the exact board rather than assuming all four propellers are interchangeable. No assembly or flight was performed for this review. [S005] [S006] [S011]

Assisted flight requires additional hardware

The main-board MPU6050 supports the basic flight configuration. The position-hold extension uses PMW3901 optical flow plus VL53L1X ranging and mounts underneath, facing the ground. A pressure-sensor route uses MS5611. The guide further distinguishes pressure-based altitude hold from ranging-based height hold, so the word “hold” alone is insufficient to identify the required sensors or operating conditions. [S005] [S006]

These documented modes are upstream capabilities, not catalog-tested performance. The guide includes level-surface startup, sensor orientation and battery-status checks. A successful Wi-Fi connection does not establish that the sensor stack, motor directions or control mapping are correct. [S006]

Keep the development and control software matched

The documented development environment is ESP-IDF release/v5.0. Upstream's preserved build workflow includes v4.4 and v5.0 containers, but that workflow configuration is not evidence that this review built either version successfully. Record the source revision, target chip and selected hardware settings together before flashing. [S007] [S009]

Control can use a mobile app, with a customized cfclient route for PC debugging and gamepad input. The README points to the leeebo cfclient fork while the detailed guide names qljz1993. That mismatch remains unresolved here; compatibility of either fork with the selected firmware was not tested. The guide also warns that online parameter changes are for debugging and do not survive power-down. Preserve final tuning in the appropriate persistent configuration rather than relying on a running session. [S001] [S006]

Source coverage and remaining gaps

The main repository carries GPL-3.0 and attributes its Crazyflie-derived code. Its third-party table leaves the DSP library's license field blank, so the root license is not presented as a complete audit of every dependency. External mobile applications and client forks require their own source and license checks. [S001] [S003] [S008]

The archive includes hardware schematics, PCB PDFs and BOM spreadsheets, including the S2 V1.2 board and flow deck. Their presence does not establish a complete editable manufacturing package or specific hardware reuse terms. BOM rows and circuit correctness were not validated. No firmware build, flashing, radio-control test or flight test was performed. [S005] [S010]