July 27, 2026 PX4 Weekly Dev Update: Accelerating Autonomous Flight Safety and Hardware Expansion

PX4 Weekly Integrated Briefing

Over the past seven days, the PX4 Autopilot project has demonstrated vigorous development activity, primarily focusing on enhancing the safety, reliability, and hardware expandability of autonomous flight systems. Key highlights include advanced control and safety features for fixed-wing aircraft, improved fault detection and recovery mechanisms for multirotor platforms, and expanded support for a diverse range of new flight controller boards.

Concurrently, significant strides have been made in refining the accuracy and stability of simulation environments, alongside active performance optimization for EKF2 (Extended Kalman Filter 2). Critical bug reports from the community, including in-flight software crashes and unexpected setpoint deviations during landing, have further underscored the paramount importance of stability enhancements. Ongoing documentation and internationalization initiatives continue to bolster the overall user and developer experience.

The activities this week reflect PX4’s continuous commitment to evolving into a safer and more versatile drone platform. Notably, the introduction of advanced features like Failure Injection and sophisticated control algorithms demonstrates immense potential for elevating drone operational capabilities in complex mission environments.

PX4 Releases and Key Version Changes

Last week saw the announcement of the new PX4 Autopilot pre-release, v1.18.0-beta1. This beta version is designed for extensive flight testing, serving as a crucial step before the official 1.18 stable release. Developers are encouraged to utilize this version to validate new features and changes, facilitating early detection of potential issues. Comprehensive details for v1.18.0-beta1 are available on its dedicated GitHub Release page. The complete changelog will be thoroughly documented in the official release notes once 1.18 is stable.

Core GitHub Updates (PX4-Autopilot)

Key Merged Pull Requests

This week, a significant number of Pull Requests (PRs) focusing on enhancing the stability and functionality of PX4 Autopilot have been merged:

• fix(mavlink): accept INT32_MIN as “param not used” in mission item validation: Improved MAVLink mission planning robustness by accepting INT32_MIN as a “param not used” value in mission item validation.
• fix(iis2mdc): data-ready flag, sensitivity, and sample rate: Resolved bugs related to the IIS2MDC driver’s data-ready flag, sensitivity, and sample rate, improving sensor data accuracy.
• fix(nuttx): update submodule for SDMMC RX DMA cache coherency: Addressed SDMMC RX DMA cache coherency issues by updating the NuttX submodule, contributing to system stability.
• feat(commander): add failsafe for traffic avoidance system: Introduced a failsafe feature for the traffic avoidance system, significantly enhancing flight safety.
• feat(device_information): expand enum with aditional types: Expanded the device information enum to support a broader range of device types.
• docs(contribute): add AI coding assistant policy: Added a policy document regarding the use of AI coding assistants, clarifying contributor guidelines.
• docs(security): treat AI-assisted bug discovery as public: Clarified the security policy to treat AI-assisted bug discovery as public.
• [BACKPORT 1.17]fix(crsf_rc): guard against packet_size underflow in CRSF parse: Backported a patch to version 1.17 for the CRSF RC receiver driver, preventing packet_size underflow and increasing stability.
• test(matrix): register and cover Vector4 unit suite, test(system_identification): cover linear and log sine sweeps, test(mathlib): cover LowPassFilter2p invalid cutoff edges: Extended test coverage to bolster code quality and robustness.
• fix(uavcan/rangefinder): rangefinder does track init-variables now for all instances: Fixed a bug in the UAVCAN rangefinder driver where initialization variables were not tracked for all instances.
• feat(fw_mode_manager): Do first-order-hold also for go-to: Added a first-order-hold for the ‘go-to’ function in the fixed-wing mode manager, enabling smoother transitions.
• fix(boards): enable CONFIG_FS_LARGEFILE for NuttX boards with MMC/SD: Enabled CONFIG_FS_LARGEFILE for NuttX boards with MMC/SD, supporting large file systems.
• fix(boards/modalai/voxl2): Add directory for keepalive failure file: Resolved an issue with the Keepalive failure file directory for ModalAI VOXL2 boards.
• fix(px4_daemon): fix startup stdout TLS race: Fixed a stdout TLS race condition bug during PX4 daemon startup, improving simulation stability.
• feat(commander): add warning-only mode to COM_PARACHUTE: Introduced a warning-only mode for the COM_PARACHUTE function, allowing flexible control over parachute deployment.
• fix(mathlib): avoid Hexagon NaN comparison issues: Corrected a math library bug related to NaN comparison issues on Hexagon architecture (resolved redundantly across multiple PRs).
• docs(update): Logger max file size from 2 to 4 GB: Updated documentation to reflect the logger’s maximum file size expansion from 2GB to 4GB.
• fix(matrix): clamp asin domain in Euler(Dcm) near gimbal lock: Enhanced mathematical stability by addressing the asin domain clamping issue during Euler(Dcm) transformation near gimbal lock.
• fix(drivers/bmi270): correct FIFO watermark byte calculation (salvage #27875): Corrected a FIFO watermark byte calculation error in the BMI270 driver.
• fix(simulation): wind_info topic takes precedence over the wind entity: Adjusted simulation behavior so the wind_info topic takes precedence over the wind entity.
• fix(simulation): clamp simulated FIFO accel/gyro samples to int16: Improved realism by clamping simulated FIFO accelerometer/gyro samples to int16.

In-depth Analysis of Critical Open Issues

Several critical issues are currently under active discussion or awaiting resolution:

• [Bug] Setpoint got set to origin on AUTO.LAND: A severe bug reported where the setpoint resets to the origin in AUTO.LAND mode. This could critically impact aircraft control during landing and requires priority investigation.
• [Bug] Software Crash during flight – lead to UAV loss – CubePilot Orange+, 1.17.0 stable: A highly critical bug report detailing a software crash during flight on a CubePilot Orange+ using 1.17.0 stable, leading to UAV loss. Immediate investigation and resolution are essential due to direct impact on stability and safety.
• [Bug] Memory leak in the gz_x500_depth simulation.: A memory leak has been reported in the gz_x500_depth simulation, which could undermine the stability of long-duration simulation tests.
• [Bug] LockstepScheduler can broadcast to expired stack condition variables and crash POSIX SITL: A bug where the LockstepScheduler can broadcast to expired stack condition variables, leading to a POSIX SITL crash. This impacts the reliability of debugging and testing in SITL environments.
• [Bug] SPI DMA transfer is not locked with multiple devices: An long-standing bug remains open where SPI DMA transfers are not locked when multiple SPI devices are used, potentially causing data corruption. This concurrency issue at the hardware driver level is crucial for stable sensor and peripheral operation.
• docs(bug): GHSA-mqgj-hh4g-fg5p patch version. May be dangerous!: A documentation bug related to security, warning that a specific patch version might be dangerous. This is critical as it could directly correlate with security vulnerabilities.

Key Open Pull Requests (Future Development)

This week, a variety of feature development Pull Requests (PRs) continue to be actively discussed, shaping the future direction of PX4:

• feat(fw_mode_manager): add ETA-based height-rate modulation: Introduced ETA (Estimated Time of Arrival)-based height-rate modulation to the fixed-wing mode manager, enabling more precise flight control.
• feat(dshot): enable concurrent BDShot capture per timer: The DShot driver will support concurrent BDShot capture per timer, enhancing motor control performance.
• feat(boards): add Droneer X6 flight controller, feat(boards): add Lectron Pi5 Autopilot board, feat(boards): add siyi_unifc-6-pico flight controller, feat(boards): Add support for the NewBeeDrone PixNova: The addition of support for various new flight controller boards continuously expands hardware compatibility within the PX4 ecosystem.
• feat(control_allocator): add tilting multirotor actuator effectiveness: Added an actuator effectiveness model for tilting multirotors, which will improve control precision for VTOL and specialized multirotor configurations.
• feat(failure_injection): add ADS-B traffic failure injection and battery severity levels: The addition of ADS-B traffic failure injection and battery severity levels is crucial for testing failsafe systems and emergency scenarios.
• perf(fw_att_control): fused sincosf for the legacy ecl attitude controller, perf(mixer): fuse the two post-clamp passes in the legacy multirotor …, perf(ekf2): build the four hottest EKF fusion/covariance files at -O3: Performance optimizations for EKF2 and control loops maximize PX4’s efficiency in resource-constrained environments.
• feat(control_allocator): reversible-motor failure recovery for hexarotors: Added a reversible-motor failure recovery feature for hexarotors, a critical safety function to reduce the risk of aircraft loss.
• feat(fw_mode_manager): parachute landing on mission landing approach: Parachute landing capability for fixed-wing aircraft during mission landing approach provides a safe landing option in emergency situations.
• feat(ekf2): support up to two optical flow sensors: Supporting up to two optical flow sensors enhances the accuracy and robustness of EKF2’s position estimation.
• feat(parachute): make the Parachute output function commandable via DO_PARACHUTE: The Parachute output function can now be commanded via DO_PARACHUTE MAVLink command, facilitating integration into autonomous missions.
• feat(commander): add terminate options for critical battery and lost position failsafes: Added termination options for critical battery and lost position failsafes, enhancing flexibility in emergency response.
• docs(tools): Mode Requirements detailed docs: Added detailed documentation for mode requirements, aiding understanding of PX4 mode behavior.
• docs(security): add threat model and Security documentation section: Added a threat model and Security documentation section, demonstrating the project’s commitment to enhancing security.
• feat(simulation): add parachute plugin for gz: Added a parachute plugin for Gazebo (gz) simulation, enabling realistic emergency scenario testing.
• feat(ekf2): Model-based 3D wind estimator for fixed-wing: The introduction of a model-based 3D wind estimator for fixed-wing aircraft into EKF2 is expected to significantly improve flight prediction and control accuracy.
• feat(motor_failure_detector): add current-residual detection library and feat(commander): wire current-residual motor-failure detector + offline replay tool: The introduction of a current-residual based motor failure detection library and an offline replay tool significantly enhances motor failure diagnosis and post-analysis capabilities.
• feat(gimbal): support forwarding to an external gimbal manager: Support for forwarding to an external gimbal manager increases the flexibility and expandability of gimbal systems.
• feat(fw_mode_manager): Support path interface with separate Fixedwing Guidance Control Module: Support for a path interface with a separate Fixed-wing Guidance Control Module suggests modularization and advanced flight path management possibilities for fixed-wing systems.
• feat(uavcan): add bidirectional ESC support for uavcan: UAVCAN-based bidirectional ESC support enables advanced motor control and braking capabilities.

Weekly Dev Call & Community Trends

The weekly developer call, held on July 22, 2026 (PX4 Dev Call: Jul 22, 2026 (Team sync, and Community Q&A)), focused on team synchronization and community Q&A. While specific discussion details are yet to be published in the forum post, these regular sync-ups are vital for sharing project progress and integrating community feedback.

On the PX4 Autopilot Discourse forum, several key topics were actively discussed:

• Flight Termination Failsafe, EKF2 divergence, simulation lagging: Discussions surrounding EKF2 divergence and flight termination failsafe activation due to simulation engine lagging highlight the need for improved realism and stability in simulation environments, as well as fine-tuning of failsafe logic. This aligns with related simulation bug reports on GitHub.
• Speed Controller Parameter Tuning: Questions about speed controller parameter tuning indicate significant user interest in optimizing practical flight performance.
• Setpoint jumped to origin in LAND: The issue of the setpoint jumping to the origin in LAND mode mirrors the GitHub issue [Bug] Setpoint got set to origin on AUTO.LAND, recognized as a highly critical bug for flight safety.
• Sharing PX4-FlightAxis-Bridge — RealFlight Evolution as a PX4 simulator: The sharing of a new simulation bridge reflects developers’ efforts to test and utilize PX4 in diverse environments.
• What kind of results can be achieved with an EKF2 replay?: Questions about the utility of EKF2 replay demonstrate high community interest in data analysis and debugging tools.

Subsystem Trends (MAVLink, MAVSDK, QGroundControl)

MAVLink

Concerning MAVLink, a critical bug fix PR (fix(mavlink): accept INT32_MIN as “param not used” in mission item validation) was merged on GitHub. This change directly enhances the stability of MAVLink-based mission planning by allowing INT32_MIN to signify an ‘unused parameter’ during mission item validation. Furthermore, a PR (feat(gimbal): support forwarding to an external gimbal manager) to enable gimbal systems to forward MAVLink messages to an external gimbal manager is currently under discussion, underscoring the increasing flexibility in peripheral device integration through MAVLink.

MAVSDK

Direct GitHub activity or Discourse discussions specifically centered on MAVSDK were not prominent this week. Nevertheless, the merging of PX4 Autopilot documentation PRs (docs(ko): point MAVSDK SITL tests at sih-sitl.json, docs(uk): point MAVSDK SITL tests at sih-sitl.json) underscores ongoing internationalization efforts for MAVSDK-driven SITL testing guidelines. This highlights MAVSDK’s persistent and vital role within the PX4 testing and development ecosystem.

QGroundControl

On the QGroundControl (QGC) Discourse forum, the topic “Unable to control Sony ILX on Pixy LR with QGC” generated discussion. This user experience issue, arising from QGC’s integration with specific hardware (Sony ILX camera and Pixy LR), highlights a strong community interest in QGC’s peripheral control capabilities and compatibility. On GitHub, an issue concerning the addition of VIO health indicators (Create QGC indicators for VIO health) was marked as stale and subsequently closed. This suggests that while there’s a recognized need for QGC interface enhancements, this particular feature might currently be deprioritized or slated for resolution via alternative approaches.