June 01, 2026 PX4 Weekly Dev Update: Safety Enhancements and Expanding Hardware/Simulation Ecosystem

Hello PX4 Developer Community, this is your weekly report providing an in-depth analysis of the main activities and technical trends of the PX4 Autopilot project as of June 01, 2026.

PX4 Weekly Integration Briefing

Over the past week, PX4 Autopilot project development has actively focused on two core pillars: enhancing flight safety and expanding system capabilities. Numerous critical bug fixes and improvement PRs related to safety-critical components such as EKF2, VTOL control, and the Commander module have been merged or are under discussion, reflecting continuous efforts to maintain a stable flight control system. Specifically, PRs like EKF-GSF emergency Yaw reset, prevent divide-by-zero during VTOL tiltrotor transition, and reject old configuration overrides emphasize proactively eliminating potential in-flight hazards.

Meanwhile, new hardware board support (DAKEFPV series, ZeroOneX6 V2), diverse sensor integration (LSM6DSV32X, dfrobot gas sensor, UAVCAN GNSS timestamping), and simulation environment improvements (X-Plane SITL backend addition, Gazebo gravity issue fix) continue to bolster the PX4 ecosystem’s scalability and flexibility. Notably, a PR extending the Detect and Avoid module to comply with regulatory standards such as ASTM F3442 indicates significant progress towards industrial application of autonomous flight systems, while the development of advanced navigation features like Geofence Aware RTL is also noteworthy.

At the community level, stability issues related to the recently released v1.17.0, such as Pitch/Roll control problems on Pixhawk 6X, are being actively discussed on the Discourse forum. This highlights the critical importance of real-world user feedback in the development cycle. Furthermore, ongoing bug reports concerning MAVLink communication and integration with QGroundControl indicate that seamless interaction with ground control systems remains a crucial development challenge.

PX4 Release and Version-Specific Key Changes

While no new PX4 Autopilot stable release was announced last week, the impact of major changes in the currently developing v1.18.0-alpha1 and the recent stable version v1.17.0 continues to be highly significant for the community.

v1.18.0-alpha1

• Release Date: May 13, 2026
• This is a pre-release version for flight testing, with official release notes to be published later. Developers can experience the latest features and improvements through this alpha version and contribute to the next stable release by providing feedback.

v1.17.0 – Stable Release

• Release Date: May 13, 2026
• This stable release, based on PX4 v1.16, includes the following key changes:
  • New Flight Mode: Addition of Altitude Cruise mode for multicopters (maintaining stable speed cruise while holding tilt and heading).
  • Fixed-wing Takeoff Improvements: Ascending to maintain horizontal flight upon navigation loss, and ability to define loiter position with takeoff waypoint latitude/longitude.
  • Extended ROS 2 Control Interfaces: Enhanced ROS 2 workflow support for fixed-wing and rover through FwLateralLongitudinalSetpointType and RoverSetpointTypes.
  • Zenoh Middleware Maturation: Strengthened features including rmw_zenoh compatibility, CDRv1 serialization, ROS 2 graph activation, and auto-generated config.
  • Initial MC Neural Network Control Test Path: Integration of TensorFlow Lite Micro allowing replacement of multicopter controllers with externally trained networks for research and bench testing.
  • New INS Drivers: Added MicroStrain, sbgECom, EULER-NAV, along with Septentrio GNSS resilience reporting and automatic barometer GNSS height-based calibration.
  • Various improvements related to MAVLink, RC, logging, failsafe, and rover operations, enhancing overall system stability and functionality.

v1.17.0 is a significant release that substantially advances PX4’s autonomous flight capabilities and ROS 2 integration. The Altitude Cruise mode, in particular, offers users a more flexible flight experience, and the expanded ROS 2 interfaces greatly improve the flexibility for developers building complex robotic applications based on PX4. Alongside these feature enhancements, community feedback on stability and bugs in real-world environments is crucial for the successful adoption of v1.17.0.

Core GitHub Updates (PX4-Autopilot)

Over the past 7 days, there has been active development in the PX4-Autopilot GitHub repository. PRs focusing on safety, new hardware support, and simulation improvements are particularly notable.

Merged Important PRs

• fix(fw_latlon): align airspeed load factor (risk:safety-critical): A critical fix improving flight safety by aligning the airspeed load factor for fixed-wing aircraft.
• refactor(uORB): hoist Publication advertise/publish to base (scope:uorb): Abstracted uORB message publication logic to a base class, increasing code reusability and maintainability. This contributes to the improvement of PX4’s core middleware architecture.
• feat(navigator): add course hold mode (kind:feature, risk:safety-critical): A course hold mode has been added for fixed-wing aircraft. This is a key feature that can enhance operational convenience and safety in long-duration flights or missions requiring specific path maintenance.
• feat(boards/dakefpv): add DAKEFPV H743 Pro board support, feat(boards/dakefpv): add DAKEFPV H743 board support, feat(boards/dakefpv): add DAKEFPV H743 Slim board support (kind:feature, scope:boards): Official support for the DAKEFPV H743 series flight controllers has been added, further expanding the range of hardware platforms supported by PX4.
• fix(mavlink): Hardcode PX4_MAX_FILEPATH for log handler (scope:mavlink): Hardcoded the file path length for the MAVLink log handler to improve stability.
• fix(septentrio): added periodic health checks to septentrio driver (scope:drivers, scope:sensors): Added periodic health check functionality to the Septentrio driver to strengthen the reliability of GNSS sensors.
• fix(failsafe): Inform user about every failsafe triggered (risk:safety-critical): Provides notifications to the user for every failsafe trigger, increasing situational awareness for operators.
• feat(logger): append topics defined in logger_topics.txt instead of replacing all (kind:feature, scope:logging): The logger topic configuration method has been improved to append new topics instead of overwriting existing ones, enhancing flexibility.

Open Critical Issues and PRs

• feat(navigator): extend detect and avoid module to follow regulatory standards such as ASTM F3442 (kind:feature, risk:safety-critical, scope:navigation): A major feature PR extending the Detect and Avoid module to comply with regulatory standards such as ASTM F3442. This represents a crucial development direction for PX4-based drones in terms of commercial and regulatory compliance.
• External modes: setpoints are applied for up to ~900 ms after the external process dies (risk:safety-critical, scope:offboard, scope:commander): A severe safety issue has been reported where setpoints are applied for up to ~900ms even after the external control process terminates. This is a critical point requiring attention from developers using offboard control systems.
• fix(ekf2): guard EKF-GSF emergency yaw reset (risk:safety-critical, scope:estimation): A corrective PR adding a safety guard for EKF-GSF emergency Yaw reset. This is essential for protecting the vehicle from unexpected attitude control issues.
• fix(vtol): prevent divide-by-zero in tiltrotor transition weight (risk:safety-critical, vehicle:vtol): A PR preventing a divide-by-zero error in tiltrotor transition weight calculations for VTOL aircraft. This directly impacts the stability of VTOL flight.
• feat(navigator): Geofence Aware RTL (kind:feature, risk:safety-critical, scope:navigation): A PR implementing Geofence Aware RTL (Return To Launch) functionality. This contributes to compliance with flight restricted areas and enhances autonomous flight safety.
• feat(platforms): upgrade NuttX to 12.12.0 (kind:feature, risk:safety-critical): A large-scale PR upgrading the NuttX RTOS to version 12.12.0. This is a significant change underpinning the entire PX4 system, potentially bringing new features, performance improvements, and enhanced stability, but requiring extensive testing.
• URML (substrate-neutral robot intent language) — RFC requesting feedback on PX4 capability-manifest mapping (kind:rfc, scope:mavlink, scope:middleware): An RFC (Request for Comments) has been posted regarding URML (substrate-neutral robot intent language). This initiates an important discussion on PX4’s future interfaces and interoperability strategies with other robotic systems.
• feat(simulator_xplane): add X-Plane SITL backend to avoid requirement for any X-Plane Plugin for simulation (kind:feature, scope:simulation): Adds an X-Plane SITL (Software-In-The-Loop) backend, enabling simulation without requiring any X-Plane plugin. This contributes to simplifying simulation environment setup and increasing accessibility.

Overall, the past week saw a balanced combination of safety-related bug fixes and foundational work for new features. In particular, PRs reflecting requirements for regulatory compliance and advanced autonomous flight capabilities are being actively discussed, indicating PX4’s evolution beyond a simple flight control system into a comprehensive drone solution platform.

Weekly Dev Call & Community Trends

The PX4 Dev Call held on May 27, 2026, consisted of team synchronization and community Q&A sessions. These weekly developer calls serve as a crucial platform for core developers and community members to communicate directly, share the latest development status, and seek solutions for important technical challenges. It is expected that numerous PRs and issues seen in GitHub activity were discussed in depth during this call. Especially, large-scale changes such as the NuttX 12.12.0 upgrade or the extension of the Detect and Avoid module undergo important processes of sharing roadmaps, implementation strategies, and gathering feedback during these sessions.

Discourse Forum Key Trends

Discourse forums saw active discussions surrounding the recently released v1.17.0 and new hardware.

• Pixhawk Section:
  • R-XSR transmitter -> pixhawk 6c mini doesn’t work (11 replies, 45 views): Discussions about communication issues between Pixhawk 6C Mini and R-XSR transmitter highlight potential driver or configuration difficulties that can arise with new hardware integration. This underscores the importance of community support.
  • Send Boat to Waypoint, it goes in circules backwards (0 replies, 20 views): Bug reports related to rover (boat) waypoint missions suggest the continuous need for improvements in the rover platform’s navigation stack.
• PX4 Autopilot Section:
  • Pitch/Roll control issues on X500 with Pixhawk 6X (PX4 v1.17) (15 replies, 55 views): Reports of Pitch/Roll control issues on X500 aircraft using Pixhawk 6X with v1.17 stable indicate the need for in-depth testing and debugging in real-world environments even after a release. This directly relates to several risk:safety-critical bug fix PRs currently in progress on GitHub.
  • Timestamp not syncing with PX4 simulation with gazebo /clock topic (0 replies, 16 views): Timestamp synchronization issues in the Gazebo SITL environment are critical as they affect the accuracy and reliability of simulations. This is also linked to simulation-related bug fix PRs on GitHub (fix(simulation): preserve gravity and step_size in px4-rc.gzsim set_physics), demonstrating efforts to ensure overall stability of the simulation environment.

Active community discussions play a vital role in surfacing practical application issues within PX4 and setting development priorities to address them. In particular, reports of control problems after a stable version release appear to be matters requiring urgent review by the development team.

Subsystem Trends (MAVLink, MAVSDK, QGC)

MAVLink Trends

MAVLink, as the core communication protocol between PX4 and ground control stations and external components, saw several important improvements and bug fixes last week.

• Bug Fixes:
  • fix(mavlink): preserve COMPONENT_ARM_DISARM param2 force flag on mission upload (open): Fixes to preserve the param2 force flag of the COMPONENT_ARM_DISARM message during mission upload, increasing mission reliability.
  • fix(mavlink): validate GPS UTC timestamps (open): Adds GPS UTC timestamp validation to ensure accuracy of time synchronization via MAVLink.
  • fix(mavlink): execute CONDITION_DELAY mission items as NAV_DELAY (open): Modifies CONDITION_DELAY mission items to execute like NAV_DELAY, improving consistency of mission flow.
  • fix(mavlink): leave LOITER_TO_ALT yaw unspecified (closed): Modifies LOITER_TO_ALT mission items to leave the Yaw value unspecified, increasing flexibility.
  • fix(mavlink): Hardcode PX4_MAX_FILEPATH for log handler (closed): Fixes a bug related to the file path in the MAVLink log handler, supporting stable logging.
• New Discussions:
  • URML (substrate-neutral robot intent language) — RFC requesting feedback on PX4 capability-manifest mapping (open): An RFC on URML has been initiated within the MAVLink and middleware scope. This is part of a crucial standardization effort for interoperability between robotic systems and will significantly impact PX4’s long-term architecture and integration strategy.
  • [Bug] PX4 doesn’t reject unsupported MAV_CMD params in commands or missions (open): A bug has been reported where unsupported MAV_CMD parameters are not rejected, indicating a need for improved robustness in MAVLink command processing.

MAVLink continues to be refined in its functionality, with many bug fixes especially in terms of safety and mission execution accuracy. Discussions around URML offer an interesting glimpse into MAVLink’s future direction.

MAVSDK Trends

No direct GitHub PRs, Issues, or Discourse discussions related to MAVSDK were specifically captured in the provided data for the past week. This could suggest that MAVSDK is currently maintaining a relatively stable state, or that major development activities are occurring through other channels. However, given the strengthening integration of ROS 2 in PX4, MAVSDK will continue to serve as an important interface for external application development.

QGroundControl (QGC) Trends

QGroundControl, as PX4’s standard ground control station, continues to see ongoing reports of user experience and feature integration issues.

• Bug Reports:
  • [Bug] “Go to location” in QGC doesn’t work as expected (open): A bug has been reported where the “Go to location” feature in QGC does not work as expected. This directly affects the accuracy of navigation commands and user convenience.
  • [Bug] Parameters request fail on QGC (open): A bug where parameter requests fail on QGC could indicate MAVLink communication issues or integration problems with PX4’s parameter system, which is essential for configuration and diagnostics.
• Discourse Discussions:
  • QGC shows extremely high MAVLink message rates (e.g., HEARTBEAT 46,000 Hz) even with USB-only connection – no companion computer attached (0 replies, 14 views): The phenomenon of QGC displaying abnormally high MAVLink message rates could indicate communication overhead or debugging-related issues. This suggests the need for further investigation into the implementation and efficiency of the communication protocol between QGC and PX4.

QGC-related issues provide important feedback on how end-users experience the PX4 system. Stable parameter configuration, accurate navigation command transmission, and efficient MAVLink communication are essential elements for enhancing the completeness of the PX4 ecosystem. These issues are challenges that need to be resolved through close collaboration between the QGC and PX4 development teams.