Sized for the mission, not the spec sheet.
A reference airframe, a companion computer that runs the perception, a payload that earns its mass, and positioning you can trust. Scale the airframe class to the payload — not the other way around.
A working configuration.
| Subsystem | Reference | Note |
|---|---|---|
| Airframe | Holybro X500 v2 | X650 when payload + endurance demand it |
| Companion compute | NVIDIA Jetson Orin Nano | Runs perception / Re-ID at the edge |
| Payload | Zoom + thermal gimbal | Dual-band for dawn/dusk coverage |
| Positioning | RTK GNSS | Centimetre-class for repeatable survey |
| Flight controller | Pixhawk 6X | Pairs with ArduPilot or PX4 |
The payload sets the airframe.
The most common build mistake is choosing an airframe first and then discovering the gimbal, compute, and battery don’t fit the thrust budget. Start from the payload mass and the endurance target; the airframe class falls out of that.
The X500 is a clean default for a single-gimbal perception build. When the mission adds mass — a heavier sensor, a second payload, longer endurance — the X650 is the next step up rather than overloading the smaller frame.
Figures and configurations on this page are illustrative, drawn from public open-source documentation (subject to verification). Operation in the Republic of Korea requires national airworthiness rules, KC radio-frequency certification, and expert validation. All build content is published only after export-control and dual-use review. Open-source components are governed by their own licenses (ArduPilot: GPLv3, PX4: BSD-3-Clause). This page is not legal or export-control advice.