A mission planner and ground control station for INAV and MultiWii flight controllers, supporting real-time telemetry, logging, and aviation monitoring.
mwptools is a mission planner and ground control station suite for model aircraft and UAS using INAV or MultiWii flight controllers. It provides tools for flight planning, real-time telemetry monitoring, log replay, and aviation traffic awareness. The project solves the need for a versatile, portable, and protocol-agnostic flight management system.
Drone and model aircraft enthusiasts, UAS operators, and developers working with INAV or MultiWii flight controllers who need comprehensive mission planning and monitoring capabilities.
Developers choose mwptools for its broad telemetry protocol support, cross-platform compatibility, and integrated aviation monitoring features, offering a free and open-source alternative to proprietary ground control software.
Migrated to codeberg.org https://codeberg.org/stronnag/mwptools
Open-Awesome is built by the community, for the community. Submit a project, suggest an awesome list, or help improve the catalog on GitHub.
Supports MSP, LTM, MAVLink, Smartport, Crossfire, Flysky AA, and BulletGCCS MQTT, enabling compatibility with a wide range of hardware and protocols for flexible connectivity.
Runs on Linux, FreeBSD, MacOS, and Windows using GTK4 and POSIX APIs, tested on aarch64, riscv64, and x86_64 architectures for versatile deployment.
Displays adjacent aircraft via INAV-radar, ADS-B, MAVLink Traffic Report, and internet providers, enhancing flight safety with real-time traffic awareness as documented in the README.
Replays mwp, Blackbox, OpenTX/EdgeTX CSV, BulletGCSS, and Ardupilot logs using tools from the flightlog2x project, aiding in detailed post-flight analysis and debugging.
Primarily focused on INAV and MultiWii, with no native mission planning support for other popular controllers like Betaflight, restricting its applicability to specific UAS setups.
Requires building from source on many systems using Meson and Ninja, with dependencies on GTK4 and POSIX APIs, which can be challenging for users unfamiliar with compilation or lacking pre-built packages.
Log replay functionality depends on the separate flightlog2x project, adding an extra installation step and potential integration hurdles for seamless use.