June 08, 2026 PX4 Weekly Dev Update: Accelerating Safety Enhancements and Core Infrastructure Upgrades

PX4 Weekly Integrated Briefing

As of June 08, 2026, the PX4 Autopilot project has seen a flurry of activity across various domains over the past week, accelerating development for the upcoming v1.18.0 release. Notably, there’s a prominent trend towards focused discussion and implementation of core functionalities crucial for safe drone operation and Regulatory Compliance. The expansion of the Detect and Avoid module to comply with ASTM F3442 standards, geo-fence aware RTL (Return-To-Land) capabilities, and updates related to Remote ID are expected to enhance the stability and fulfill legal requirements of autonomous drone operating environments.

Concurrently, fundamental infrastructure improvements are actively underway, including the upgrade of NuttX OS to version 12.12.0, refactoring of the uORB middleware, and a shift towards SIH (Software-in-the-Loop) as the primary simulation environment. These changes will play a crucial role in enhancing PX4 system stability, performance, and long-term development and testing efficiency. Furthermore, the addition of support for numerous new flight control boards, along with various bug fixes and optimizations, continuously contributes to PX4’s hardware extensibility and improved flight stability. In the community forums, developers actively discussed simulation environment configurations, hardware integration issues, and architectural direction.

PX4 Releases and Key Version-Specific Changes

There were no new official PX4 Autopilot releases over the past seven days. The PX4 development team is currently focused on testing and further developing the v1.18.0-alpha1 version, which will serve as the foundation for the upcoming v1.18.0 stable release. Developers and researchers are encouraged to test this alpha version in preparation for the next stable release.

The most recent stable release is v1.17.0, announced on May 13, 2026. This version includes various improvements since v1.16.2, with the following key changes:

• New Multicopter Flight Mode: Altitude Cruise – A mode that maintains the vehicle’s inclination and heading to cruise at a constant speed when sticks are released.
• Fixed-wing Takeoff Mode Improvements – Maintains ascent in level flight upon navigation loss and allows defining the loiter position using the latitude and longitude of the takeoff waypoint.
• ROS 2 Control Interface Expansion – New FwLateralLongitudinalSetpointType and RoverSetpointTypes have been added for fixed-wing and rovers, facilitating easier control through ROS 2 workflows.
• Zenoh Middleware Maturation – Zenoh middleware has been further stabilized, including rmw_zenoh compatibility, CDRv1 serialization, ROS 2 graph activity, and auto-generated configurations.
• MC Neural Network Control Early Test Path – Integration of TensorFlow Lite Micro adds research and bench testing capabilities, allowing externally trained neural networks to be used as multicopter controllers.
• New INS Driver Additions – INS drivers such as MicroStrain, sbgECom, and EULER-NAV have been integrated, and Septentrio GNSS resilience reporting and automatic barometer calibration features have also been improved.
• Overall system improvements and bug fixes have been made across MAVLink, RC, logging, failsafe, and more.

Core GitHub Updates (PX4-Autopilot)

Over the past seven days, the PX4-Autopilot GitHub repository saw a total of 70 Pull Requests (PRs) and 11 Issues. Among these, the following notable Merged PRs and currently active critical Issues are highlighted:

Key Merged PRs

• feat(uxrce_dds_client): add support for Micro-XRCE-DDS_Client v3: The Micro-XRCE-DDS client, a core component of offboard middleware, has been updated to support v3, expected to enhance communication stability and functionality.
• fix(mavlink): avoid reinitializing command sender semaphore: Solves the semaphore reinitialization issue occurring during MAVLink command transmission, improving communication stability.
• fix(fw_mode_manager/navigator): use the correct waypoint switching distance: Corrects a bug where waypoint switching distance was not correctly calculated in fixed-wing mode, improving navigation accuracy.
• fix(navigator): use int32_t lower bound for mission index: Fixes an integer range-related bug in mission index processing, increasing the robustness of mission planning.
• fix(drivers): update SPL06_SPI.cpp to fix the sensor data issue: Corrects a data issue in the SPL06 barometric sensor driver, ensuring sensor reliability.
• fix(commander): refuse stale config_overrides on activation: Reduces safety risks by refusing stale configuration overrides upon activation. This is a safety-critical change.
• fix(vtol): prevent divide-by-zero in tiltrotor transition weight: Prevents a divide-by-zero error in the tiltrotor transition weight calculation for VTOL aircraft, enhancing flight stability. This is a significant fix tagged with risk:safety-critical.
• fix(shutdownlock): prevent external_reset_lockout from been hold for longer than 60sec: Prevents external_reset_lockout from being held for longer than 60 seconds, improving system responsiveness.
• refactor(navigator): Removed geofence breach avoidance feature: The geofence breach avoidance feature has been refactored and removed. This suggests a redesign or a change in the integration strategy for related functionalities.
• feat(fw_latlon_control): limit bank angle to not exceed max airspeed: A feature has been added to limit the bank angle of fixed-wing aircraft to not exceed maximum airspeed, enhancing flight safety. This is a crucial feature tagged with risk:safety-critical.
• feat(ekf2-mag): limit max heading rate change due to mag fusion: A feature has been added to limit the maximum heading rate change due to magnetic fusion in EKF2, improving the robustness of attitude estimation during autonomous flight. This is also a change tagged with risk:safety-critical.
• fix(navigator): rtl compute wind angle to select best land approach based on rally point location instead of home location: During RTL, the calculation for the optimal landing approach direction has been modified to consider wind angle based on the rally point location instead of the home location, enhancing safety.
• fix(navigator): honor NAV_LAND mission item abort altitude (param1): A critical bug where the abort altitude (param1) of the NAV_LAND mission item was not correctly applied has been fixed. This is a highly significant fix tagged with risk:safety-critical.

In-depth Analysis of Open Critical Issues

• External modes: setpoints are applied for up to ~900 ms after the external process dies: A severe safety concern has been raised, stating that offboard control setpoints can still be applied for up to ~900 ms after the external process terminates. This could fatally impact systems utilizing external modes and is tagged with risk:safety-critical, requiring urgent resolution.
• [Bug] Rover Differential – Doesn’t turn in Mission Mode (v1.17 Stable): A bug has been reported in the latest stable version v1.17 where the rover differential drive does not turn in Mission Mode. This constitutes a critical functional disability for rover users and demands a swift resolution.
• [Bug] auto entry into HOLD mode during auto-takeoff testing.: A bug has been reported where the vehicle automatically enters HOLD mode during auto-takeoff testing. This is a significant issue that could affect the stability of flight mode management.
• Tracking issue for the current mavlink implementation: A tracking issue is open for the current MAVLink implementation. This signifies ongoing efforts to continuously improve MAVLink protocol performance, functionality, and refactoring, foreshadowing major MAVLink-related changes in the future.

Notable Open PRs

Several important PRs are currently under review, with the following items, in particular, indicating the future direction of PX4:

• feat(navigator): extend detect and avoid module to follow regulatory standards such as ASTM F3442: The extension of the Detect and Avoid module to comply with regulatory standards like ASTM F3442 is central to developing safe autonomous flight systems.
• feat(platforms): upgrade NuttX to 12.12.0: The major version upgrade of NuttX OS will significantly impact system stability, security, and support for new hardware.
• feat(uorb): (WIP) Rebase TII’s SHM-based uORB on pr-nuttx-nuttx-12-12-0: TII’s SHM-based uORB rebase, linked with the NuttX upgrade, has the potential to significantly affect internal communication performance and architecture.
• feat(navigator): Geofence Aware RTL: The ability to plan RTL paths with geofence awareness will further enhance flight safety.
• feat(tests): run integration tests with PX4 internal SIH simulation and ci(ros_integration_tests): migrate from Gazebo Classic to SIH: The transition of the testing environment from Gazebo Classic to PX4 internal SIH simulation is a significant change that will increase the efficiency and reliability of development and verification processes.
• feat(open_drone_id): add RID identity record verification with read-only mtd_id backend: The Remote ID (RID) identity record verification feature for Open Drone ID is an essential element for drone regulatory compliance.
• Numerous feat(boards): add … flight controller PRs demonstrate the continuous expansion of PX4’s supported hardware ecosystem.

Weekly Dev Call & Community Trends

The regular PX4 Dev Call took place on June 3rd. This meeting serves as a crucial platform for synchronization among development teams and community Q&A, where major development issues discussed on GitHub are likely addressed.

In the general PX4 Autopilot section of the Discourse forum, various user problems and development discussions were active. Specifically, simulation-related issues such as JSBSim hexarotor_x SITL spawns high / FlightGear-QGC mismatch / auto-disarm are recurring difficulties for multiple users, suggesting the complexity of simulation environment setup or the need for documentation improvements. Furthermore, the bug report DShot motors only initialize after re-assigning output functions (cold boot) — CUAV X7, AM32, v1.16 & v1.17 indicates a hardware initialization problem in the latest stable versions, requiring an urgent solution for CUAV X7 users.

Interestingly, the discussion titled Multi-device vs. separate driver module - community preference/standards? encapsulates a fundamental community question regarding driver architecture. This indicates a need for a standardized approach to driver management and modularization as PX4 evolves. Hardware-specific problems like Overheating STM32H743 Processor or compatibility issues with older versions, such as GPS UBlox F9P Version 1.51 with PX4 Version 1.12, are also continuously being raised.

Subsystem Trends (MAVLink, MAVSDK, QGC)

MAVLink

Several significant activities related to MAVLink have been observed on GitHub. The fix(mavlink): avoid reinitializing command sender semaphore PR has been merged, improving MAVLink communication stability. Additionally, battery status reporting functionality is being enhanced through the feat(mavlink): Battery_Status_V2 MAVLink stream PR, and the fix(dronecan): forward MAVLink OpenDroneID Basic ID to Remote ID PR improves OpenDroneID information transmission via MAVLink, contributing to regulatory compliance. The currently open Tracking issue for the current mavlink implementation indicates ongoing continuous improvement and refactoring across the entire MAVLink system.

MAVSDK

There was no particularly noteworthy significant activity observed in the MAVSDK Discourse forum. However, the continuous improvements in MAVLink, particularly new data streams (Battery_Status_V2) and OpenDroneID integration, hold the potential to provide new features and data accessibility for developers using MAVSDK. The safety issue with offboard control (External modes: setpoints are applied...) will be a critical consideration for developers implementing offboard control via MAVSDK.

QGroundControl (QGC)

Discussions in the QGroundControl forum primarily revolved around connectivity and communication issues. The issue QGroundControl Android Parameter Download Stalls Over Wireless Link but Works via USB Network Sharing points to a parameter download delay problem over wireless links in QGC for Android. This suggests the need for optimization in wireless communication stacks or large data transfer efficiency. Furthermore, PX4 not receiving QGroundControl replies through MOOS UDP bridge indicates a potential MAVLink communication problem between PX4 and QGC in specific setups using a MOOS UDP bridge. These issues directly impact the user experience when QGC interacts with PX4 systems, emphasizing the importance of MAVLink protocol robustness and compatibility across various network environments.