System Architecture
Separate responsibilities so hardware, firmware, networking, and user interface can be tested independently.
ESPFlight Docs · v1 • Validated v1 documentation path
# Layer responsibilities
System layers Each layer has a clear responsibility
Application Control, configuration, tuning and status
Network / Protocol Discovery and real-time data exchange
Firmware Control loop, stabilization, safety and telemetry
Hardware Power, sensors, motors and mechanics
| Layer | Primary responsibility |
|---|---|
| Hardware | Power, sensing, physical motor outputs, mechanical system. |
| Firmware | 250 Hz control loop, stabilization, safety state, communication and telemetry. |
| Network / Protocol | Discovery and real-time exchange between controller and application. |
| Application | User control, configuration, tuning, connection and status presentation. |
# Why separation matters
When a test fails, identify which layer failed before changing unrelated parts. A wrong IMU axis is a hardware/configuration problem; a discovery failure is a network problem; a UI display issue is not fixed by changing motor PID.