Briefing
One background thread owns the MAVLink link and caches the latest message of each type, so state reads return at once; parameter values arrive through a separate store. An arm request returns the COMMAND_ACK result and, on refusal, the prearm STATUSTEXT, such as AHRS waiting for home. Modes are mapped by name per vehicle type, and a parameter write is confirmed by the echoed PARAM_VALUE. Write tools carry the MCP destructiveHint.
The README lists three kinds of validation: unit tests on Python 3.10 to 3.12, a MAVLink wire check and a live SITL run. ARMING_CHECK writes are refused on every link, even with both actuation flags set. Mission upload and guided takeoff, goto and land are deferred because of fly-away risk.
Written by the Boards & Bots curator
From the GitHub API
Repository facts
| Repository | rmeadomavic/ |
|---|---|
| Stars | 4 |
| License | MIT Permissive |
| Language | Python |
| Last push | 3 Aug 2026 2 mo ago |