Loading 3D model… large boards can take a moment.
A learning project: build a quadcopter from scratch — own hardware, own firmware, no existing flight stack.
The drone is the artefact; understanding the whole stack end-to-end is the deliverable.
no_std, embassy-nrf) on the firmware; Rust on the PC-side ground-station application too.See doc/00-vision.md for the full vision and the phased milestone plan.
Phase 2 (advanced prototyping) in progress. The whole stack runs on hardware. The drone has made first free flights — brief untethered, self-levelling hops on its own battery under closed-loop control — with telemetry over a two-hop radio link and PID gains tuned live from the ground station and now persisted to flash (ADR 0025): tune, save, power-cycle, and the gains survive.
groundstation app sends four-axis pilot commands (sliders or a gamepad) over USB-CDC to a remote micro:bit, which relays to the drone over IEEE 802.15.4 (ADR 0014). Telemetry returns the same path as a high/low-rate split frame (ADR 0027), postcard + COBS framed, every buffer sized at compile time from the shared types.firmware-drone-core.The ground station plots and logs every signal live, times the round trip, pushes and saves PID gains, shows a live 3D view of the drone's attitude, and pairs with an offline analyze tool that turns a telemetry log into a legible flight report.
Recent tuning work — validating the integral term as a centre-of-mass trim corrector, balancing the airframe by the per-motor effort split, and re-zeroing out a one-directional drift — is consolidated into a new control-troubleshooting field guide (doc/06-control-troubleshooting.md).
Next (to finish Phase 2): rebuild on the lighter next-generation frame — the previous flight frame was retired in a lost-control crash — with the IMU mounted near the centre of mass (which should cut the estimator lag at its source) and a fresh, softer re-tune; plus a firmware power-limit mode and the netted test enclosure (doc/07-safety.md). In parallel, Phase 4 is well underway — the custom nRF5340 flight controller (drone_fc v2, ADR 0026, ADR 0028) is fully routed with turnkey PCBA fab exports out to PCBWay; the micro:bit stays the tuning platform meanwhile.
See doc/progress.md for the dated milestone history, doc/dev-environment.md for the toolchain, and doc/decisions/ for the full decision history.
AGENTS.md — shared context file for AI coding assistants (Copilot, Claude, etc.). Read first.crates/ — Cargo workspace. firmware-drone-microbit (on-target binary), firmware-drone-shared (board-agnostic tasks/signals), firmware-drone-core (host-testable logic).doc/ — design notes, vision, architecture, hardware/software/control docs.doc/02-architecture.md — system architecture overview (two micro:bits, RF link, ground-station evolution).doc/decisions/ — Architecture Decision Records (ADRs).hardware/ — mechanical (Fusion 360) and electrical (KiCad).Host-testable logic (wire types, the supervisor state machine, the ground-station helpers) is unit-tested and run with cargo-nextest:
cargo nextest run # workspace host crates
cargo nextest run --manifest-path crates/groundstation/Cargo.toml # the GUI crate
A tracked pre-push git hook runs the suite before every push, and GitHub Actions runs fmt + clippy + tests on every push and pull request (the badge above). On-target firmware is exercised on hardware, not in CI. See doc/ci-and-testing.md for the details and the one-time hook setup.
proto crate for the wire protocol..f3d source + .stl mesh (STEP dropped, amended 2026-07-09).core/task split, HIL deferred.crates/, doc/, hardware/{mechanical,electrical}/, all lowercase.firmware-<role> naming; core/task split realised as sibling crates.board module inside firmware-drone, Cargo-feature-selected, tasks take erased types.main stays rustfmt-clean and clippy-clean; suppressions require justification.Channel / Watch / Signal / PubSubChannel.no_std crates: cfg_attr(not(test), no_std), inline mod tests, cargo test honours default-members.PercentageValue base.firmware-drone-core, supervisor is the sole publisher of motor commands.TelemetryState, tick-sampling per-source Watches at 100 Hz and owning frame-level fields.firmware-drone-core (Proposed).Dual-licensed under either of:
at your option.
Unless you explicitly state otherwise, any contribution intentionally submitted for inclusion in this work, as defined in the Apache-2.0 license, shall be dual-licensed as above, without any additional terms or conditions.
No comments yet. Be the first to ask about this board.