June 15, 2026 PX4 Weekly Dev Update: Hardware Expansion, Safety Enhancement, and Accelerated Regulatory Compliance

Bymaponarooo

Greetings, PX4 and Dronecode infrastructure development community. This is the PX4 Weekly Dev Update briefing for June 15, 2026.
Analysis of data collected from the PX4 GitHub repository and Discourse forum over the past seven days reveals that the project is actively expanding support for a wide range of hardware platforms, strengthening the robustness of core systems, and deepening efforts towards drone operational safety and regulatory compliance. Notably, the addition of multiple new board supports, a NuttX OS upgrade, and the expansion of the ‘Detect and Avoid’ module targeting regulatory standards such as ASTM F3442 are significant.

This week’s activities clearly demonstrate PX4’s evolution beyond a mere flight control system into a comprehensive drone platform that meets the requirements of diverse industrial and research sectors. Bug fixes and safety-related improvements enhance system reliability, while the strengthening of simulation and testing infrastructure provides a foundation for stably integrating these improvements. Active community participation serves as a key driver for the healthy development of the project.

PX4 Release and Major Version-Specific Changes

The latest officially announced pre-release version is v1.18.0-alpha1.

  • v1.18.0-alpha1 (Released May 13, 2026)

    • Status: Pre-release for flight testing
    • Key Highlights: This alpha version is a flight testing phase for the next stable release and is expected to include numerous new features, improvements, and bug fixes merged to date. While the full release notes will be provided with the official release, recent GitHub activity suggests active updates across middleware, drivers, and board support areas form the basis of this version.
      Specifically, the NuttX 12.12.0 upgrade, Zenoh-pico library update, various new board supports, and safety-related fixes are anticipated to be core to this release.
    • Detailed Link: https://github.com/PX4/PX4-Autopilot/releases/tag/v1.18.0-alpha1

Developers can contribute to the next stable version by testing the latest features in this alpha release and providing feedback.

Core GitHub Updates (PX4-Autopilot)

Over the past 7 days, a total of 60 Pull Requests (PRs) were updated in the PX4-Autopilot repository, with 16 of them being Merged (Closed). Additionally, 15 new or active Issues were discussed. This reflects a vibrant development cycle and continuous efforts to improve the system.

Key Merged PRs

Key Open PRs and Issues

Weekly Dev Call & Community Trends

The Weekly Dev Call on June 10 featured a “Team sync, and Community Q&A” session. This serves as a regular platform for sharing internal development progress and addressing direct questions from the community. In the ‘PX4 Autopilot’ section of the official Discourse forum, the following key discussions took place:

  • Swarm Drone Challenge 2026 — our PX4 swarm solution, open-sourced: The news that the PX4-based swarm solution used in the 2026 Swarm Drone Challenge has been open-sourced is a significant example demonstrating PX4’s swarm flight capabilities and scalability. This will enhance PX4’s value in research and commercial applications.
  • Volunteering to help harden PX4 security: The call for volunteers to help harden PX4 security is a very positive sign for the project’s long-term stability and reliability. Drone system security is an increasingly crucial factor, and such voluntary efforts from the community are essential for PX4’s continued growth.
  • Motors cut out mid-flight: A critical issue regarding motors cutting out unexpectedly mid-flight has been reported. This is a Critical Issue directly related to flight safety, requiring active discussion and analysis.
  • EKF2 using range finder data incorrectly: Issues such as EKF2 (Extended Kalman Filter) using range finder data incorrectly and Battery State Estimation Not Working: were reported. These are core flight control and state estimation-related bugs. Given their importance for accurate position estimation and stable power management, a prompt resolution is crucial.
  • BRGF Core Box Prototype for PX4 Integration: Discussions regarding the PX4 integration of a new hardware prototype show that PX4 continuously explores interoperability with various hardware solutions.

Subsystem Trends (MAVLink, MAVSDK, QGC)

Key subsystems within the PX4 ecosystem are also continuously evolving through ongoing improvements and user feedback.

  • MAVLink:

    In GitHub PRs, items such as fix(mavlink): reject unsupported CONDITION_DISTANCE missions and fix(mavlink): reject unsupported params in commands and missions stand out. These focus on strengthening the robustness of MAVLink mission and command processing logic and reducing the potential for malfunction due to unsupported commands. Furthermore, performance improvements like perf(mavlink): replace forward_message mutex with atomic reader counter are underway, demonstrating efforts to enhance MAVLink communication efficiency and ensure stable data exchange. These improvements will enhance the reliability of integration with external systems.

  • MAVSDK:

    The GitHub PR feat(tests): add SIH as a selectable MAVSDK test backend represents a significant step in strengthening MAVSDK’s testing infrastructure. By adding a SIH (Software-In-the-Loop Hardware) backend for MAVSDK testing, the reliability of MAVSDK-based applications can be validated in an environment closer to real hardware. This is a crucial development that supports MAVSDK developers in creating more robust drone applications.

  • QGroundControl:

    On the Discourse forum, user issues related to QGroundControl (QGC) for specific hardware and input methods were discussed. QGC Camera Trigger Issue with SIYI A8 Mini and PX4 1.17 highlights integration problems with a specific camera system, while Trying to use HID joystick input on android indicates a request for support regarding HID joystick input in an Android environment. This feedback suggests the continuous need for QGC improvements to provide a better user experience across diverse user environments and hardware.

This week’s PX4 development trends clearly showcase the project’s deep commitment to strengthening core firmware stability and safety, expanding support for diverse hardware platforms, and developing regulatory compliance and advanced autonomous features—all critical for future drone operations. The vibrant participation and contributions from the community are vital drivers of this progress. We look forward to bringing you more comprehensive news next week.

Similar Posts

답글 남기기