PX4 Dev Call: June 4, 2025 (Team sync, and Community Q&A)

Coordination Calls PX4 Autopilot
1

PX4 Sync / Q&A - 2025-06-04T15:00:00Z

:tear_off_calendar: List of all Dronecode events

Agenda

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

Announcements

:rocket: PX4 Release Testing
PX4 v1.16.0-rc1 is out, and we need your help with testing!

:warning: QGC v5.0.0-rc2 Alert
The QGC team expects a stable release next week! Please test and report issues now.

Next Dronecode Meetup

Nothing scheduled yet. If anyone is interested to host a Meetup please reach us out. Always happy to have it organized.

Future Events

  • ?

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:

Comments / Discussion:

  • The flight testing team is building the VTOL

Release Discussion / Updates

v1.16 Release Discussion

:police_car_light: Release Candidate v1.16.0-rc1

The first release candidate for the upcoming release is finally available through github and QGC.

@rroche has prepared the draft of release notes which will be completed as the next RC is cut:

We need help with flight testing, especially for early adopters and users with free time who can provide logs from flights with their drones.

:test_tube: Release Testing

Testing Tracker

Issues Tracker

Community Q&A / PRs for Review

Q1: @stevejohn163 While flying the drone in Position mode using MANUAL_CONTROL joystick inputs, I want to temporarily override the yaw axis — for example, to automatically yaw the drone 90 degrees when a button is pressed. Is it possible to override the yaw input using a MAVLink message while still receiving manual joystick input via MANUAL_CONTROL? If so, which MAVLink message allows overriding specifically the yaw axis in Position mode?

Q2: @alexcekay What would be the possible way to save flash size for specific frames or board variant?

Discussed PRs:

  1. Fix reporting of connected battery by DonLakeFlyer · Pull Request #24800 · PX4/PX4-Autopilot · GitHub
    CC: @dagar ready to merge maybe?

  2. feat: configurable board pwm freq from Kconfig by Pedro-Roque · Pull Request #24787 · PX4/PX4-Autopilot · GitHub

  3. feat: spacecraft tooling for commander and VehicleStatus by Pedro-Roque · Pull Request #24716 · PX4/PX4-Autopilot · GitHub

  4. 3dr_ctrl-zero-h7-oem-revg: Adding missing module which prevented the USB interface to start by TOTON95 · Pull Request #24938 · PX4/PX4-Autopilot · GitHub

Discussed Issues:

2

Question: While flying the drone in Position mode using MANUAL_CONTROL joystick inputs, I want to temporarily override the yaw axis — for example, to automatically yaw the drone 90 degrees when a button is pressed. Is it possible to override the yaw input using a MAVLink message while still receiving manual joystick input via MANUAL_CONTROL? If so, which MAVLink message allows overriding specifically the yaw axis in Position mode?