claudeDroneteam-docs
documentation · reference
Docs reference

Structured knowledge from collected_doc_media/claudedrone_docs/. Browse the tree on the left; the source of truth is markdown in the repo.

Installation

From host PC setup to physical drone assembly — the recipes that get the stack running.

draftdoc-seoupdated 2026-05-11T00:00:00.000ZClaudeDrone

This section is the how to actually do it side of claudeDrone. The other sections describe what the system is and how it’s designed; these pages describe the specific sequence of commands and configuration steps that take you from a fresh Ubuntu install to a working simulation, and (eventually) from a pile of parts to a flying drone.

Three subsections cover the three install layers. Host PC setup is the foundation: Ubuntu 24.04, ROS 2 Jazzy, Gazebo Harmonic, ArduPilot SITL, plus the supporting tooling we use day to day. Docker containers is the alternative path for users who’d rather isolate the whole stack in containers — slower iteration cycles, easier reproducibility. Drone assembly is the hardware-build guide (currently in design — the physical drone is on the H2 2026 roadmap).

There’s also a short, informal walkthrough by Aleks — ROS 2 Jazzy workspace bootstrap — that captures the first-time experience of setting up a ROS 2 workspace from scratch. If you’ve never used colcon or ros2 pkg create before, that’s a gentler introduction than the formal docs.

A note on the order: if you’re new to the project, the right sequence is host PC setup → ROS 2 workspace bootstrap → a smoke test from the simulation section → only then worry about Docker or hardware. Trying to do hardware first is a recipe for spending weeks debugging things that the simulation setup would have made obvious.

Contents

Auto-generated from child entries during build (update-indexes.mjs).

© 2026 claudeDrone Team · auto-pipeline · Nuxt 3 SSR