QualityMax · Embedded & Robotics

Testing drone firmware over MAVLink

The same QualityMax pattern as the web — only the transport changes. Real PX4 flight-control firmware runs in a simulator (no hardware); scenarios drive it over MAVLink and assert on live telemetry. Both scenarios pass.

1 · Discoverread vehicle health & capability surface
2 · ScenarioAI-generated flight + failsafe cases
3 · Asserton real telemetry, with time/distance budgets
4 · Reportnon-engineer-readable verdict

Nominal mission

PASS · 5/5
N ↑ top-down view waypoint · 60 m N reached ±5.5 m HOME climb to 9.0 m
  • ✓
    Vehicle accepted ARM
  • ✓
    Reached takeoff altitude9.0 m in 11.6 s
  • ✓
    Flew to 60 m waypointarrived within 5.5 m in 13.0 s
  • ✓
    Returned home & landed (RTL)0.0 m from home in 50.1 s
  • ✓
    Disarmed on the ground

Geofence · control + containment + real breach

PASS · 7/7
50 m geofence control: no fence → flew to 73 m fenced 80 m cmd → held 6.9 m same command, 73 m → 6.9 m = the fence
  • ✓
    Control (no fence): drone flies outreached 73.1 m of the 80 m target
  • ✓
    Geofence blocks the out-of-bounds commandheld 6.9 m vs 73.1 m unfenced — the fence is the difference
  • ✓
    Never breached the 50 m fencemax 6.9 m
  • ✓
    Real breach auto-triggers Returnfence armed around a drone 60 m out → RTL, unprompted
  • ✓
    Returned home after the breach11.7 m from home
contained (fenced) control (no fence) safety boundary
PX4 SITL MAVLink MAVSDK 3.15 Docker · arm64 No physical hardware — firmware-in-simulation. Runs in CI / cloud.