PX4 Sync / Q&A - 2026-05-06T15:00:00Z
Announcements
Events
- PX4 Dev Summit Schedule:
Open Source Summit + Embedded Linux Conference North America 2026: Schedule For PX4 Dev Summit Events @ Minneapolis, MN, USA
- There will be a ROS2 Workshop which recently is added.
Release
Current tag: v1.17.0-rc2
Target date: June 2026
Flight Tracker: v1.17 Release Testing
Updates:
From the last week:
Release 1.17 is close to being released. The problems that were found so far were identified to not be regressions and not blocking the release. We’ll fix them in 1.18 and move ahead with 1.17. Next announcement planned for this Friday.
We should give a chance to everyone to review the PRs and check what should be merged. We should go once more round thru the main branch for the release. In a week we should be able to have stable release unless there are issues or PRs still needs to be reviewed by the maintainers. Anyone wants to have their PRs reviewed before they might tag @rroche or addit to the project board.
Note: The merge window for 1.18 release is now. As soon as 1.17 is out 1.18 will be branched off and only bugfixes will be merged, new things then go to 1.19.
Issues:
- [Bug] `MAV_CMD_CONDITION_DELAY` mission items are accepted but the delay duration parameter is ignored · Issue #27289 · PX4/PX4-Autopilot · GitHub ( There should be an open PR to fix this)
- [Bug] MAV_CMD_COMPONENT_ARM_DISARM drops `param2`, preventing forced disarm · Issue #27288 · PX4/PX4-Autopilot · GitHub (This should be verified by SITL)
- Rangefinder step-changes cause altitude jumps in Terrain Hold with optical flow · Issue #27110 · PX4/PX4-Autopilot · GitHub (@dakejahl we should discuss the priority on this issue)
- [Bug] "Heading estimate invalid" when flying with VIO Only · Issue #27031 · PX4/PX4-Autopilot · GitHub (Still with VIO there is the issue maybe what implemented for OpticalFlow could work here)
Decisions:
PRs for Review
Q&A
1- I’m new to PX4 and currently exploring it for autonomous drone monitoring applications. I’ve noticed there are many interconnected technologies involved (SITL, QGroundControl, MAVLink, MAVSDK etc.) also for simulation with ROS2 & Gazebo , and it feels a bit overwhelming to structure the learning process. Is there a recommended roadmap or guide to follow that helps build a solid foundation step by step? For example: What should I learn first (PX4 basics, SITL, or simulation)? When should I integrate ROS 2? Any best practices for moving from simulation to real hardware? I’d really appreciate any guidance or resources from your experience.
Ans: You should go thru the PX4 Docs first and have a hands on experience. Start flying in SITL first and then have your hands on hardware.
2- @Vilius How does multiple sensor fusion work on UAVCAN and is it possible to move MAVLINK message conventions from Development to Common for GNSS integrity. There are missing messages fields for GPS jamming inside common MAVLINK messages convention.