May 25, 2026 PX4 Weekly Dev Update: v1.17 Stabilization and Core Infrastructure & Safety Feature Enhancements

Dear PX4 Developers and Researchers,

Here is your weekly PX4 development trend briefing for May 25, 2026. Over the past seven days, the PX4 Autopilot project has shown vibrant activity across a wide range of areas, spearheaded by the stabilized v1.17 release, core infrastructure updates, introduction of enhanced safety features, and improvements to the simulation environment. Notably, the v1.17 stable release sets important milestones, including new flight modes, strengthened ROS 2 integration, and improved maturity of the Zenoh middleware, reaffirming the robustness and extensibility of the PX4 ecosystem.

This week’s activities clearly demonstrate a continued investment in future-oriented features (e.g., neural network control, advanced collision avoidance) and developer productivity enhancements (e.g., Windows SITL, reproducible builds), all while prioritizing the stability and reliability of drone systems. The community is also contributing to broadening PX4’s applicability by continuing discussions on MAVLink standards and QGroundControl improvement requirements.

PX4 Weekly Integrated Briefing

Over the past week, the PX4 Autopilot project has made significant progress on several fronts. The biggest news is the PX4 v1.17 stable release, announced on May 13th. This release significantly enhances PX4’s flight performance and external system integration capabilities by incorporating various core features, including the introduction of the ‘Altitude Cruise’ flight mode, improved fixed-wing takeoff mode, expanded control interfaces for ROS 2 workflows, and the maturation of Zenoh middleware’s rmw_zenoh compatibility.

In the GitHub repository, significant PRs related to safety and stability bug fixes, addition of new hardware (board) support, enhancement of MAVLink and UAVCAN driver functionalities, and improvements to the simulation environment were actively discussed or merged. Of particular note are long-term safety and core infrastructure improvements such as NuttX OS version upgrades, shared memory-based uORB refactoring, geofence-aware RTL, and the expansion of the Detect and Avoid module to comply with the ASTM F3442 standard.

The Discourse forum continued communication through the Weekly Dev Call, sharing progress from the core development team and answering community questions. Discussions within the MAVLink subsystem on China’s Remote ID standard highlighted PX4’s interest in international regulatory compliance, and QGroundControl-related questions suggested the need for continuous feature improvements and multi-platform support for the ground station software.

PX4 Releases and Major Changes per Version

Based on activities from the past seven days, the following release information is confirmed:

• v1.17.0 – Stable Release (Published 2026-05-13)
  • New Flight Mode: The Altitude Cruise mode for multicopters has been added, allowing for stable cruising at a consistent speed when sticks are released.
  • Fixed-Wing Takeoff Improvements: Maintains climb in horizontal flight upon navigation loss and allows defining loiter position using takeoff waypoint latitude/longitude.
  • ROS 2 Control Interface Expansion: New FwLateralLongitudinalSetpointType and RoverSetpointTypes have been added for fixed-wing and rover vehicles, strengthening integration with ROS 2 workflows.
  • Zenoh Middleware Maturity: The in-tree Zenoh middleware has achieved rmw_zenoh compatibility and stabilization (including CDRv1 serialization, ROS 2 graph liveness, auto-generated configs, etc.).
  • Neural Network Control (MC Neural Network Control) Test Path: A research and bench test path has been added to integrate TensorFlow Lite Micro on-device, allowing externally trained neural network models to replace multicopter controllers.
  • New INS Drivers: MicroStrain, sbgECom, and EULER-NAV drivers have been added, and Septentrio GNSS resilience reporting and GNSS altitude-based barometer auto-calibration have been implemented.
  • General Improvements: Various improvements related to MAVLink, RC, logging, failsafe, and rovers are included.
• v1.18.0-alpha1 (Published 2026-05-13)
  • This is a pre-release for flight testing. Official release notes will be published later.

The stabilization of v1.17 demonstrates PX4’s increased focus on providing sophisticated and reliable control solutions required in industrial and research fields. Particularly, the advancements in ROS 2 integration and Zenoh middleware are expected to significantly enhance the flexibility and performance for building complex drone systems.

Core GitHub Updates (PX4-Autopilot)

Over the past seven days, more than 60 PRs were actively discussed in the PX4-Autopilot GitHub repository, with over 13 of them being merged (closed). Key activities are as follows:

Key Merged PRs

Recently merged PRs primarily focus on stability improvements, driver fixes, and documentation enhancements:

• fix(boards/gearup): use 0x26ac VID: Fixed a vendor ID bug for Gearup boards, enhancing hardware recognition stability.
• fix(osd/atxxxx): show battery symbol based on remaining charge: Corrected the OSD battery icon to accurately display based on remaining charge, ensuring accuracy of critical flight information for the user.
• fix(uavcan/SIH): disable local sensors when UAVCAN is enabled: Disabled local sensors when UAVCAN is enabled in SIH (Software-In-the-Loop) environments, improving simulation consistency.
• fix(mavlink): guard mission download completion: Strengthened the robustness of MAVLink mission download completion handling, improving mission transfer reliability.
• fix(vtol): prevent divide-by-zero in tiltrotor transition weight: Prevented a potential divide-by-zero error during VTOL tiltrotor transitions, significantly enhancing flight safety (risk:safety-critical).
• fix(drivers): PCA9685 use correct internal OSC frequency: Corrected the internal OSC frequency setting for the PCA9685 driver, ensuring accurate control signal output.
• fix(commander): refuse stale config_control_setpoints cache on activation: Prevented stale control setpoint caches from being activated in the Commander module, strengthening safety (risk:safety-critical).
• fix(tools/uploader): handle USB CDC reconnect race during reboot: Fixed a race condition during USB CDC reconnection in the uploader tool, improving firmware upload stability.
• feat(mavlink): reassemble GPS_RTCM_DATA before GPS injection: An important feature was merged to add data reassembly logic before GPS RTCM data injection via MAVLink, enhancing RTK/PPK accuracy.
• feat(sensors/gps): map PVT UTC to HRT for EKF time alignment: A safety-related feature (risk:safety-critical) was added to map GPS PVT UTC time to HRT (High Resolution Timer) for improved EKF (Extended Kalman Filter) time alignment accuracy.

Notable Open PRs and Issues

This week, important feature development and infrastructure improvement PRs, indicating PX4’s future direction, are under active discussion:

• feat(platforms): upgrade NuttX to 12.12.0: A major PR to upgrade NuttX, PX4’s core RTOS, to 12.12.0. This is a risk:safety-critical change that will have widespread implications for PX4’s subsystem stability and support for new features, and it is currently under active discussion with 31 comments.
• feat(uorb): (WIP) Rebase TII's SHM-based uORB on pr-nuttx-nuttx-12-12-0: This task involves rebasing TII’s shared memory (SHM)-based uORB onto the NuttX 12.12.0 branch. This is a highly significant risk:safety-critical PR that, along with the NuttX upgrade, can fundamentally improve the performance and scalability of the uORB middleware.
• feat(navigator): Geofence Aware RTL: Adds a geofence-aware RTL (Return to Launch) feature to enhance flight safety (risk:safety-critical). Active review is ongoing with 16 comments.
• feat(navigator): extend detect and avoid module to follow regulatory standards such as ASTM F3442: A significant risk:safety-critical feature that extends the detect and avoid module to comply with regulatory standards such as ASTM F3442. This is an essential component for commercial drone operations, with 8 comments.
• feat(simulation): native Windows SITL with lockstep timing: Supports native SITL (Software-In-the-Loop) simulation with lockstep timing on Windows. This will greatly enhance accessibility to the PX4 simulation environment for Windows developers.
• feat(oot): support external MAVLink handler, stream, and dialect with opt in custom init scripts in Out of Tree modules: Enhances MAVLink customization and extensibility by supporting external MAVLink handlers, streams, and dialects with opt-in custom init scripts in Out-of-Tree modules.
• feat(gimbal): support mount gimbal manager: Adds support for a gimbal mount manager, providing advanced gimbal control capabilities. This is an important advancement for applications such as aerial photography and inspection.
• feat(new_module): Static and moving vision-based target esitmator (Kalman Filter): The addition of a vision-based static and moving target estimator (Kalman Filter) module is under discussion. This is a risk:safety-critical feature with the potential to significantly enhance autonomous flight and specific mission capabilities.
• Px4-xplane sitl airframe for Fixed Wing and Multicopter and VTOL: A PR for X-Plane SITL airframe support, with 25 comments, showing high interest in simulation expansion.
• uavcannode does not consistently support multiple uORB instances for sensor publishers: An issue has been raised that the UAVCAN node does not consistently support multiple uORB sensor publisher instances. This is a significant kind:improvement matter for enhancing the performance and robustness of UAVCAN-based sensor integration.
• [Bug] uxrce_dds_client stops publishing data after random uptime, requires flight controller reboot to recover: A bug has been reported where uxrce_dds_client stops publishing data after random uptime, requiring a flight controller reboot to recover. This is a kind:bug affecting the stability of the DDS middleware, and solutions are being sought with 6 comments.
• NXP Secure Element PX4 driver support as a green path for hardware based Root of Trust and PX4 security best practices: An issue regarding NXP Secure Element driver support. This is an important discussion for strengthening PX4’s security through hardware-based Root of Trust, an essential element for industrial and commercial drones.

Weekly Dev Call & Community Trends

The PX4 Dev Call held on May 20, 2026, consisted of a team sync and community Q&A session. This serves as an important channel for sharing development progress, answering technical questions from the community, and fostering transparency and participation within the PX4 ecosystem.

In the ‘PX4 Autopilot’ section of Discourse, questions of various difficulties were exchanged. Basic configuration and control questions such as serial 5 usage, armed status and warning messages via CRSF/ELRS, and Rate PID tuning were consistently raised, indicating that many new users and developers struggle with specific feature implementations. Meanwhile, in-depth discussions on advanced research and special-purpose drone development using PX4, such as Amphibious Drone / Aerial-Underwater Vehicle Architecture Guidance and B4DGM Recursive Telemetry Platform for PX4 Research, also took place, demonstrating that PX4 serves as the foundation for various innovative projects. The question PX4 Hardware-in-the-Loop (HITL) with X-Plane series? is linked to the X-Plane SITL airframe PR on GitHub, reflecting the community’s high interest and practical application demands for expanding the simulation environment.

Subsystem Trends (MAVLink, MAVSDK, QGC)

• MAVLink:
  Discourse saw the start of a discussion on “China GB 46750 Remote ID: field mapping gaps in MAVLink OpenDroneID”. This concerns potential gaps in mapping specific fields of China’s GB 46750 Remote ID standard within MAVLink OpenDroneID messages. As international drone regulatory compliance becomes crucial, continuous updates to the MAVLink standard and ensuring alignment with local regulations are essential tasks for PX4’s global market entry. This also connects to the recent fix(dronecan): forward MAVLink OpenDroneID Basic ID to Remote ID PR, showcasing ongoing efforts for Remote ID standard compliance.
• MAVSDK:
  No new discussions were observed in the Discourse MAVSDK section this week. This suggests that MAVSDK is currently in a relatively stable state, or that major discussions are taking place on other channels.
• QGroundControl:
  In QGroundControl Discourse, requests for specific platform support, such as “QGroundControl for Linux aarch64 (2)”, continue. This reflects the requirement for QGC to operate in diverse hardware environments and shows the community’s desire to utilize QGC on a wider range of platforms. Furthermore, the error report “Rally Point transfer failed” indicates that improvements in the stability of mission planning and transfer are still needed areas.

This week’s PX4 development trends clearly demonstrate the PX4 team’s efforts to solidify its current robustness through the stabilization of v1.17, while actively exploring future-oriented technologies such as NuttX upgrades, SHM-based uORB, Windows SITL, and advanced detect and avoid features, thereby maintaining leadership at the forefront of drone technology. We will bring you more exciting news from the PX4 project next week.

Thank you.