Why build a drone

Summary¶

Building a drone is one of the few projects where a single weekend of work produces a functional flying machine that touches physics, electronics, software, mechanical engineering, and regulation simultaneously. But "why build a drone" has a better answer than curiosity. A drone you built yourself is one you can repair, extend, and trust — because you understand every layer of it. A drone you bought is a black box that can be updated, restricted, or discontinued by someone else. This article is the entry point for workshop participants and new students: what the build teaches, what the platform enables, and why the open-source choice matters.

Concept¶

What the build teaches¶

Building a libdrone is not a drone project. It is a systems engineering project that uses a drone as the integrating artefact.

The skills touched in one complete build:

No other single student project delivers this breadth at this cost. The drone either flies correctly or it does not — feedback is immediate and unambiguous. There is no partial credit. A blinking LED is not the same as a stable hover.

The GX12 payload interface¶

libdrone has a documented payload connector standard (GX12-7) for anyone who wants to build a swappable sensor or camera interface — see gx12-connector-standard. The current builds don't use it yet (Cinematic's GoPro mounts directly), but it's planned for a future iteration. Once it exists on a real build, the same principle applies: you can carry any instrument you design and build to the standard, and the open firmware and hardware mean you can modify flight behaviour or frame geometry too.

The most important skill the build develops is not any of the specific techniques — it is the habit of working with systems where every component is understood and auditable. This habit transfers to every future engineering project.

Why open source specifically¶

Every component in libdrone's software stack is open source. This means:

• The firmware that controls the motors can be read, verified, and modified
• The radio protocol specification is public — no vendor can break your RC link by releasing an incompatible update
• The CAD files are parametric and open — you can change any dimension
• The documentation is free — no licence, no subscription, no DRM

A student who learns on open tools owns their skills. The tools will always be available to them. A student who learns on proprietary tools can only work where those tools are licensed. The career argument is direct: open-source contribution is a public portfolio that any employer can see and verify.

Why building beats buying¶

A bought drone is opaque. You cannot know what the firmware does to your data. You cannot fix it when it breaks beyond the vendor's supported repair window. You cannot extend it beyond what the vendor permits. You cannot audit it for a security-sensitive deployment.

A built drone is transparent. You know what every component does because you installed it. You can repair it in the field because you understand the failure hierarchy. You can adapt it because the design is open. You can audit it because every line of code and every CAD file is public.

The build is not the price of admission. The build is the point.

Reference¶

Workshop participant prerequisites¶

No prior experience is required to attend a libdrone workshop. Participants who will benefit most:

• Can use a computer at a basic level (file management, browser)
• Are comfortable with hand tools (screwdrivers, hex keys)
• Have some soldering experience (helpful but not required — taught in workshop)
• Are curious about how things work

The workshop follows the same build guide a solo builder would use — sk-cinematic-6in-ardupilot-gopro or sk-agile-3in-hdzero — with hands-on help at the points that actually trip people up. Participants who complete the workshop will have flown a drone they built themselves.

Procedure¶

Rationale¶

Why the workshop uses libdrone and not a commercial kit¶

Commercial drone kits abstract the engineering. You follow instructions to assemble pre-designed parts and configure pre-written firmware. The result is a drone you can fly but not understand. When it breaks, you are dependent on the manufacturer. When it is updated, you lose any customisations.

libdrone workshops expose every layer: why each component exists, what failure mode it protects against, what the physics behind each design decision is. The extra complexity is the curriculum. Understanding the system — not just operating it — is the learning outcome.

Connections¶

requires: [] related: - foss-principles - foss-stack-libdrone - legal-and-regulatory leads_to: - sk-cinematic-6in-ardupilot-gopro - sk-agile-3in-hdzero