August 03, 2026 PX4 Weekly Dev Update: Core Platform Modernization, Enhanced Safety Features, and Broadened Hardware Support

PX4 Weekly Integrated Briefing

Over the past week, the PX4 Autopilot project has shown a strong focus on modernizing its core platform and strengthening system stability and safety. In particular, the long-term tasks of upgrading the NuttX OS to version 12.12.0 and rebasing uORB to a shared memory-based implementation are actively progressing. These efforts are laying crucial groundwork for future PX4 performance enhancements and the implementation of new functionalities. Such extensive platform changes necessitate comprehensive system-wide testing and validation, accompanied by concurrent bug fixes and optimization efforts.

Concurrently, significant bug fixes and safety feature improvements aimed at enhancing drone operational stability have been prominent. Numerous patches have been merged to prevent critical flight errors, including stronger validation for important parameters, prevention of NaN errors in fixed-wing flight control, and avoidance of path deviation during multicopter flights. Furthermore, the addition of a parachute command function for emergency landings, the development of a reversible motor failure recovery mechanism for hexarotors, and the expansion of ADS-B and battery-related failure injection capabilities demonstrate PX4’s evolution into a safer and more resilient system. Discussions around new board support and UUV (Unmanned Underwater Vehicle) DVL (Doppler Velocity Log) integration reflect the community’s continuous efforts to expand PX4’s application scope.

Meanwhile, the ground control system, QGroundControl, announced its v5.1 Release Candidate 1, accelerating improvements in user experience and stability. These overall movements clearly indicate that PX4 is evolving into a more powerful, safe, and versatile open-source flight control platform.

PX4 Releases and Key Changes by Version

There were no official PX4 Autopilot releases in the last seven days. The most recent major release was v1.18.0-beta1, announced on July 8, 2026. This version serves as a pre-test release for the PX4 1.18 stable release, incorporating many new features and improvements. Currently, changes subsequent to this beta version are being actively integrated into the development branch, with core platform enhancements like the NuttX 12.12.0 upgrade prominently underway.

Core GitHub Updates (PX4-Autopilot)

Key Merged Pull Requests

Over the past week, the PX4 Autopilot GitHub repository saw the merging of several notable updates, enhancing the system’s stability, functionality, and safety.

• feat(commander): add terminate options for critical battery and lost position failsafes: Adds failsafe termination options for critical battery and lost position scenarios, providing crucial functionality for safe drone handling during emergencies.
• feat(parachute): make the Parachute output function commandable via DO_PARACHUTE: Enables parachute output control via the MAVLink DO_PARACHUTE command, increasing flexibility in emergency system operations. This will play a vital role in emergency landing scenarios.
• feat(failure_injection): add ESC failure unit (off/wrong) with correct MAVLink semantics: Introduces an ESC failure injection capability, allowing for more realistic simulation of motor failure scenarios in simulation and testing environments. This is essential for evaluating system robustness.
• feat(mavlink): MAV_CMD_DO_SET_MISSION_CURRENT support: Adds support for the MAVLink MAV_CMD_DO_SET_MISSION_CURRENT command, enhancing the ability to set the current waypoint during a mission.
• fix(control_allocator): restore airship tail-thruster yaw: Fixes an issue with airship tail-thruster yaw control. This bug was labeled risk:safety-critical and is essential for stable airship control.
• fix(mc_pos_control): reject non-positive automatic vertical speed limits: Strengthens validation of control parameters in multicopter position control by rejecting non-positive automatic vertical speed limits. This helps prevent unintended flight behavior.
• [BACKPORT 1.18] fix(fw_latlon_control): prevent NaN eas2tas from zero-airspeed division and fix(fw_latlon_control): prevent NaN eas2tas from zero-airspeed division: Two fixes applied (including a backport to 1.18) prevent NaN (Not a Number) errors in fixed-wing flight control caused by zero-airspeed division, enhancing fixed-wing flight stability.

In-depth Analysis of Critical Open Issues

The following major issues are currently awaiting resolution:

• [Bug] fmu-v6xrt: hardfault in the MAVLink Onboard-stream / uORB Subscription::update path under load: A critical bug where the MAVLink Onboard-stream / uORB Subscription::update path causes a hardfault under load on PX4 FMU-v6xrt boards. This can severely impact MAVLink communication stability on specific hardware and requires high-priority resolution.
• [Bug] CAN-based RTK GNSS not working on NXP v6X-RT – inconsistent CAN frames, no RTK Fix: An issue where CAN-based RTK GNSS is not functioning correctly on NXP v6X-RT boards, preventing RTK Fix. This is a crucial hardware integration bug directly affecting applications requiring precise positioning.
• [Bug] Multicopter mission stalls and drifts away after overshooting a waypoint it can’t accept during a fast fly-through: A bug where a multicopter stalls and drifts after overshooting an unacceptable waypoint during a fast mission fly-through. This is a serious control and navigation issue that undermines the reliability of autonomous missions.
• [RFC] Enforce parameter constraints at param::get(): An RFC (Request For Comments) proposing to enforce parameter constraints at the param::get() call site. This will be an important discussion for ensuring parameter consistency and validity, thereby improving overall system robustness.
• Pixracer goes out of RAM with the latest main: A report of Pixracer boards running out of RAM with the latest main branch. This is a significant resource management issue that could affect users of older or resource-constrained boards.

Major Open Pull Requests (Pending Merge)

Notable open PRs include:

• feat(platforms): upgrade NuttX to 12.12.0: A large-scale PR to upgrade the NuttX OS to 12.12.0. This has significant potential to modernize PX4’s underlying OS and provide new features and stability, but requires extensive testing and validation, as indicated by its risk:safety-critical label. Active discussions are ongoing with 59 comments.
• feat(uorb): (WIP) Rebase TII’s SHM-based uORB on pr-nuttx-nuttx-12-12-0: A work-in-progress (WIP) to rebase TII’s shared memory (SHM)-based uORB on the NuttX 12.12.0 PR. Alongside the NuttX upgrade, this is a critical feature that could revolutionize PX4’s internal communication mechanism, expected to contribute to performance improvements. This is also labeled risk:safety-critical.
• feat(ekf2): support up to two optical flow sensors: A PR to improve EKF2 by supporting up to two optical flow sensors. This will enable more precise and robust position estimation in environments where GPS reception is challenging.
• feat(control_allocator): reversible-motor failure recovery for hexarotors: A PR adding reversible-motor failure recovery for hexarotors. This is a significant safety feature that can greatly enhance the drone’s fault-tolerance.
• docs(security): add threat model and Security documentation section: An important effort to enhance and document the security aspects of the PX4 system by adding a threat model and a dedicated security documentation section. This is crucial for industrial and high-reliability applications.
• feat(ekf2): Model-based 3D wind estimator for fixed-wing: A feature for a model-based 3D wind estimator for fixed-wing drones. This is an advanced EKF capability that will significantly contribute to improving fixed-wing flight performance and precision.
• feat(failure_injection): add ADS-B traffic failure injection and battery severity levels: A feature to add ADS-B traffic failure injection and battery severity levels. This will be utilized to test various emergency scenarios in complex simulation environments.

Weekly Dev Call & Community Trends

The PX4 Dev Call held on July 29, 2026, included a team sync and community Q&A session. While no additional discussions specific to this call were recorded on the forum itself, it consistently serves as an important channel for sharing development progress and communicating with the community.

In the PX4 Autopilot Discourse section, the following topics were discussed:

• Thrust consistency difference between cold and hot motors: A practical question was raised regarding the difference in thrust consistency between cold and hot motors. This is a critical engineering consideration directly impacting real-world flight performance.
• Quadrotor Three-Motor Emergency Landing: A PX4 Degraded-Landing Experiment: A post on a quadrotor’s three-motor emergency landing experiment was shared, demonstrating the community’s interest in PX4’s fault-tolerance research.
• PX4 Python Simulator: Discussions about a PX4 Python simulator reflect developers’ need to leverage PX4 within a Python environment.
• PX4 support for STM32N6?: Inquiries about supporting new hardware like the STM32N6 suggest the potential for PX4 to expand to various latest embedded platforms.
• DVL integration for underwater UUV px4 for underwater autonomous flight: Discussions regarding DVL (Doppler Velocity Log) integration for underwater UUVs (Unmanned Underwater Vehicles) indicate a significant move to extend PX4’s application scope beyond aerial drones to underwater robotic platforms.

Subsystem Trends (MAVLink, MAVSDK, QGC)

While there were no new posts in the MAVLink and MAVSDK Discourse sections over the past seven days, active bug fixes (Fix GPS_RAW_INT/GPS2_RAW instance selection, Improve GPS_RAW_INT yaw reporting) and new features (MAV_CMD_DO_SET_MISSION_CURRENT support) for MAVLink messaging were actively pursued in GitHub PRs. This indicates continuous improvement in the accuracy and utility of the MAVLink protocol.

In the Pixhawk section, an inquiry about Pixhawk 6X Pro integration with Jetson-based boards was raised. This reflects ongoing interest in combining high-performance computing modules with Pixhawk flight controllers, suggesting active development of integrated solutions for onboard AI/ML and complex missions.

QGroundControl (QGC) made significant progress this week by announcing QGroundControl v5.1 Release Candidate 1. This heralds the imminent release of a new stable version, promising an upgrade to the overall QGC experience, including user interface improvements, new feature additions, and enhanced stability. Additionally, bug reports for specific features, such as QGroundControl not showing 2nd battery, were also discussed, demonstrating continuous improvement efforts driven by user feedback.