PX4 Dev Call: Sep 3, 2025 (Team sync, and Community Q&A)

[farhang]

PX4 Sync / Q&A - 2025-09-03T15:00:00Z

List of all Dronecode events

Agenda

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

Announcements

The PX4 DevSummit you all were waiting for

• CFPs are closed!!! Reviews in progress!!!
• Early Bird Tickets are still around, so use your chance to get them!!!

Don’t Call it a Comeback! The PX4 Developer Summit Returns for 2025 —...

Future Events

ROSCon 2025 Singapore

ROSCon 2025

Next Dronecode Meetup

Upcoming meetup in Korea

ELISA Project + Dronecode Foundation Meetup – ELISA

Flight Testing Update

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

How to reach out to the team

• GitHub: Tag user @PX4**/testflights**
• Discord: #flight-testing
• Weekly on the PX4 Dev Call

How to Request Testing (GitHub)

• Write down the steps to test 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

Resources:

• Flight Testing Project Board
• Tests Cards

Discussion

• Testing team is reviewing their flight logs on v1.16 for debugging possibility of issues.

Release Discussion / Updates

We are going to be promoting the release branch to stable, and push a stable release ASAP.

v1.16 Release Discussion

New Release

PX4-Autopilot v1.16.0 Release Notes | PX4 Guide (main)

Release notes here as well → Releases · PX4/PX4-Autopilot · GitHub

Project Board

PX4 v1.16 Release • PX4

Community Q&A / PRs for Review

PRs:

1. Concept: Separate GNSS position and heading topics by oystub · Pull Request #25516 · PX4/PX4-Autopilot · GitHub
2. https://github.com/PX4/PX4-Autopilot/pull/25012

Issues:

1. FLASH savings feature tracker · Issue #25491 · PX4/PX4-Autopilot · GitHub
2. [Bug] Takeoff/Land without GPS does not hold position · Issue #22250 · PX4/PX4-Autopilot · GitHub (tests in SITL to reproduce)
   → We might need to update SITL tests to be based on new Gazebo

[oystub]

Hey folks!

We’re developed and are flying with a setup in our 1.13 fork where GNSS heading is handled separately from position instead of being tied into GPS blending. Right now, blending mixes concepts that don’t really belong together, so we added a sensor bridge that publishes vehicle_gnss_heading from sensor_gnss_relative. This makes heading cleaner, easier to debug, and independent of position logic.

I’ve created a draft PR with the relevant changes from what we currently fly with, with an extensive description of the background and reasoning behind. Concept: Separate GNSS position and heading topics by oystub · Pull Request #25516 · PX4/PX4-Autopilot · GitHub

It’s based on 1.13, but most of the logic only needs minor adjustments up to 1.15 (I don’t have the full overview of 1.16 yet). We would be happy to do the required modifications, and refinements for getting this upstream. We’re also (finally) moving away from 1.13 to 1.15 or 16 for our production drones.

However, before pushing further, we’d really like to hear what you other developers and community members think about the way forward for the GNSS logic in PX4. Hopefully we can have a quick chat about it at the call today