PX4 Sync / Q&A - 2026-04-29T15:00:00Z
Announcements
Events
Release
Current tag: v1.17.0-rc2
Target date: June 2026
Flight Tracker: v1.17 Release Testing
Updates:
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.
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:
Decisions:
PRs for Review
Closed-loop RPM control through DSHOT to have more accurate robotic model.
https://github.com/PX4/PX4-Autopilot/pull/27126
Discussion about latency issues with RPM control, these are worked around by having a scaled feed-forward without any latency coming from feedback and its processing. The P and mostly I action of the controller then just makes sure the rpm is tracked more accurately longer term e.g. when the battery voltage drops. Next steps: move out of DSHOT driver into a class used in allocation, if possible use the existing unit-tested PID class for calculations (it can be improved if desired), remove D-term (never used), reduce parameter number (remove D-term, enable based on positive gain). after another review round conduct testing with the latest version.
Q&A
Do we plan to support allocation with SI units?
- Yes, control allocation made it easier. No one pushed through and is using it but the goal would still be to optionally support it, it’s currently not a priority contributions certainly welcome.
There will be an architectural proposal in an upcoming dev call