Pixhawk autonomy

Drone Mission Replay

A flight-test workspace for mission planning, sensor health, replay evidence, and controlled abort decisions.

A quadcopter mission diagram with waypoint timeline and sensor health markers.
Debugging optical-flow health

Primary goal

Prove a reliable autonomous mission path before extending flight complexity.

Evidence

Flight logs, Mission Planner screenshots, parameter notes, and incident links.

Limit

Live outdoor flight media still needs to replace placeholder evidence frames.

What this mission proves

This page is built around the part of drone work that is hardest to fake: the chain from hardware assumptions to replay evidence to the next controlled test. The goal is not to claim a perfect flight. The goal is to show that the system is being debugged like an engineering platform.

Evidence model

Each flight attempt should leave behind a small packet of proof: the Mission Planner screenshot, the relevant log slice, the parameter state, the sensor placement photo, and the incident note if anything degraded. Those artifacts make the project inspectable without forcing the homepage to carry the whole story.

Current limit

The present risk is optical-flow health. The next test should constrain variables tightly enough that each result can move the system forward instead of creating another ambiguous run.

Mission Timeline

Trace The Work

Each entry keeps the project inspectable by linking a system state to an evidence expectation.

  1. 00:00

    Bench validation

    Document wiring, sensor placement assumptions, and firmware state before field testing.

  2. 03:20

    Mission Planner replay

    Review mode transitions, EKF behavior, optical-flow health, and abort markers.

  3. 07:45

    Failure capture

    Record BAD OPTFLOW HEALTH as a test artifact rather than hiding it from the project.

  4. Next

    Constrained retest

    Change one variable at a time: placement, surface texture, calibration, then parameter tuning.

Evidence

Proof Slots

These cards are intentionally concrete. Replace placeholder frames with real logs, screenshots, photos, CAD exports, and code traces as they are available.

Build Stack

Tools And Surfaces

PixhawkMission PlannerArduPilotOptical flowFlight logs
FAIL-000 Tried to be a normal portfolio critical
Symptom
Visitors scrolled, shrugged, and closed the tab. Nothing stuck.
Root cause
The operator hid behind generic panels. Zero risk taken, zero easter eggs shipped.
Fix
Rebuilt as a living lab: boot sequence, command palette, and a public failure log.
Lesson
If you dug deep enough to find this, we should probably talk. Report this finding →
incident unlocked · konami / sudo