Skip to content
terrytaylorbonn edited this page Nov 15, 2024 · 915 revisions

24.1114

image


This wiki is organized by epics. Tech details (lab notes) are on the gdrive.


New stuff:




Why a wiki with docx's on a gdrive?

I've never found a big-picture step-by-step overview of how to get started building and flying (autonomous AI) drones. The closest thing I found was the original Youtube playlist that was the starting point for SITL (simulation). It took me almost 2 months to get through that simulation and document all the details (the Youtube videos were almost 5 years old; there were a lot of problems). But it was a start.

After that I (and more importantly Youtube AI algorithms) scoured Youtube for any related demos that I could get working (determining what "related" was was not easy). I documented what I did in the docx's (Word files) and put them on the gdrive. I created this Wiki as a big-picture overview (of the core instructions in the docx's). Low-level hands-on experience was critical for understanding the big picture concepts. I reorganized this Wiki at least 20 times (I use wiki because I can easily reorganize the wiki site and its very easy to use).

This ecosystem (Youtube demos, docx's, Wiki, along with Youtube/Google AI search and sites like StackOverflow) made it possible for a lone wolf like myself to succeed in getting all of this running. As for building actual drones, Amazon with its one-day delivery, product rating system, and AI search algorithms was key. All-in-all it was a lot more of a challenge than you would think just by looking at this rough-draft wiki and the gdrive docx's (basically rough lab notes that provide very accurate and detailed instructions).

Note: Lab notes are not user docs. And transforming them into user docs takes time. After hacking away at some strange problem and documenting everything I did in docx lab notes (maybe for several days), separating the wheat (what fixed the problem) from the chaff (without losing a single grain of invaluable wheat) is not simple. This invariably involves replicating the original tests. I have replicated the core SITL doc (10.1) instructions on a clean Linux partition at least 5 times. The effort to replicate the build process for an autonomous AI drone is (at least for now) is currently not planned.


Wiki home


"GET A JOB" EPIC

The goal

Demo deployments

1 APIs / API docs

2 AWS

3 Code


AI DRONE EPICS

Getting into the air ASAP

(0) Reference


EPIC 1 - Build/fly FPV drone

(1) FPV simulators (inav notes 0608)

(2) SBeeF405/INAV (1a)

(3) SBeeF405/BF (1b)

(4) SBeeF405/AP (1c)


EPIC 2 - Build/fly Pixhawk drone

(5) Pix6c/PX4 (2a)

(6) Pix6c/AP (2b)


EPIC 3 - Add AI to Pixhawk drone

(7) AI cc + cam

(8) AI CC+FW

(9a) SIH (frame+world sim)


EPIC 4 – Basic Autonomy

(13) CC AI (+ Mavlink) (2)

(11) FC_Mavlink_API (via CC/GCS APIs) (5.3)

(13c) CC autonomy algorithms


EPIC 5 – Advanced Autonomy

(20) Kalman KK (+Python,vectornav)

(14) Firmware dev (5)

(22) AI


EPIC 7 – Mission platforms / special projects

(15) Mission platforms (6b)

(16) Special projects (5.6,5.5)


EPIC 8 – PITS (Pie in the sky)

(12) ROS (+ROSMAV)

(14b) Matlab

(9b) HITL (frame+world sim)

(10) (skip) SITL (total sim) (1)

Clone this wiki locally