PX4 Dev Call: Oct 22, 2025 (Team sync, and Community Q&A)

PX4 Sync / Q&A - 2025-10-22T15:00:00Z

Agenda

  • Announcements
  • Future Events
  • Flight Testing Update
  • Release Discussion
  • Bug Report / Q&A

Announcements

Your contribution to this survey matters a lot to us:

The PX4 DevSummit you all were waiting for

Future Events

ROSCon 2025 Singapore

Flight Testing Update

About the Test TeamThe team at Ascend Engineering (Chicago). are running flight testing for the community.

How to reach out to the team

GitHub: Tag user @PX4PX4PX4PX4**/testflights**

Discord: Flight Testing & Log Analysis

Weekly on the PX4 Dev Call

How to Request Testing (GitHub)

Write down the steps to te@PX4PX4t your issue/pull request

Make sure to note the risk involved in flying

Write down things to look out for / anticipate - eg: “we are looking for no yaw jumps”

Add issue/pull request to the Flight Testing project board

Make sure to specify any hardware/software requirements as much as possible

Updates:

  • NXP Pixhawk 6XRT with v16.1rc tests done smoothly. Tests card to indoor flight tests.
    (Tests Flights | PX4 Guide (main))

  • Once this part is settled we could aim for 1.17 alpha release.

Flight Review has updates

Please report any issues.

Release Discussion

v1.16.1

New release tag is cut: Release v1.16.1-rc1 · PX4/PX4-Autopilot · GitHub

v1.17.0-alpha1

Community Q&A / PRs for Review

PX4 documentation is now served by S3 and CloudFront instead of GitHub Pages.

Discussion:

  • Moving from 1.13 to 1.16 how to implement custom airframe? → Everything is basically being set by parameters after removing mixer files.

PRs:

I won’t be able to make the call today, but not sure if it makes sense to try to get Fix position setpoint update logic in Mission RTL by msberk · Pull Request #25600 · PX4/PX4-Autopilot · GitHub into the next release cut? I know @dagar mentioned he may do a refactor to push the setpoint modifications up into handleLanding() but I haven’t seen anything about that happening.