Dokumentationsindex
Jedes Dokument des Repositories, nach Aufgabe gruppiert.
Originaltitel im Repository: Documentation map
Start with the project overview. Maintained guides describe interfaces, procedures and limits; dated captures describe what was actually observed. Check the current aircraft before acting on either.
Operation
| Guide | Scope |
|---|---|
| Sensor inspection and recording | Disarmed camera/MAVLink recording, outputs and component health |
| FC checks | Read-only firmware, configuration and live sensor checks |
| GPS-free hover | Guarded takeoff, optical-flow Loiter, landing and required validation |
| Bench motor test | Explicit propeller-off motor/ESC checks |
| Armed tag/servo recording | Separate actuator workflow and mechanism calibration |
| AprilTag mission design | Planned tag approach/release and navigation limitations |
Run uv run <command> --help for current options. A documented workflow does
not mean its live hardware prerequisites or flight validation are complete.
Connections and Raspberry Pi
| Guide | Scope |
|---|---|
| Pi networking | Client networks, fallback hotspot, boot selection and dual interfaces |
| Pi USB Ethernet/SSH | Developer-host gadget networking on Linux, Windows and macOS |
| Direct FC USB | Controller serial access and passive inspection without the Pi |
| Pi power resilience | Controlled upgrades, recording durability and boot-service checks |
| Connection and shutdown status | Check connections and prepare battery or USB removal |
Deployment commands are introduced in the root overview. Pi USB Ethernet and flight-controller USB are different devices and protocols.
Hardware, configuration and firmware
| Guide | Scope |
|---|---|
| Hardware inventory | Project components and intended roles |
| FC configuration | Canonical UART/wiring rules, MAVLink allocation, arming checks and capture |
| Hardware assets | Original 3MF projects and STL print exports |
| Frame and print guide | Frame construction and source files |
| Payload mechanism | BCM12 servo, power and physical verification |
| Firmware artifacts | Reviewed overlays, manifest and post-flash gates |
| ArduCopter 4.7 no-GPS review | EKF rationale, exact build and SITL acceptance procedure |
Dated evidence and history
- 9 September firmware and power update: installed custom ArduCopter 4.7.1, matched simulation and connection/shutdown checks.
- 9 September startup melody: WAV 34 adapted and verified on all four AM32 ESCs.
- 9 September MT-15 integration: verified forward range through FC and Pi after UART3 pin swapping, with parameters captured at integration.
- 7 September 2026 repair result: completed software/FC repairs, verification and remaining physical work.
- 7 September initial analysis: earlier findings and attempts, retained with their original chronology.
- MT-15 direct-USB configuration: verified sensor output and its ID quirk, separate from FC reception.
- 7 September FC parameters and capture metadata.
- 25 August firmware/flow verification, 19 August capture, and 18 August capture.
- Branch archive, with original commit provenance and incident evidence.
- Historical poster and project site.
- Historical notes, including the archived August 25
handoff formerly named
CURRENT.MD. - Retired implementation archive, excluded from runtime deployment and active checks.
Older failures remain evidence of what happened then; the later repair report records the resulting state. Raw artifact links may require the local workspace. Other-aircraft reference data is not a configuration source for this drone.
Development
README lists repository checks. Software architecture explains runtime responsibilities. CLAUDE.md describes architecture, dependencies and contributor conventions; AGENTS.md records access and hardware-safety rules.