PX4 Dev Call: Aug 19, 2026 (Team sync, and Community Q&A)

Coordination Calls PX4 Autopilot
1

PX4 Sync / Q&A - 2026-08-19T15:00:00Z

This week: 36 PRs merged | 115 awaiting review | 0 new bugs

Announcements

QGC 5.1 RC2 is released: QGroundControl v5.1 Release Candidate 2 is available : Tests are welcomed.

Events

PX4 Developer Summit at Open Source Summit Europe, Prague, Czechia, 7–9 October 2026. Speakers announced; full schedule and PX4 track filter here:

Dev Call Items

  • Annoucements/Events
  • Flight test team update
  • Release discussion
  • PRs/Issues/Q&As

Release

Updates:

Issues:

Decisions:

  • There might be good to add docs for flying indoors using OpticalFlow. Terrain has to be fused in the case of indoor flying using OpticalFlow.

PRs Merged This Week

36 PRs merged this week →

PRs Awaiting Review

115 PRs awaiting review →

New Bug Reports

  • No new bugs

Other New Issues

5 new issues →

Q&A:

  1. feat(avoidance): fuse external avoidance setpoints in Position/Mission by ZacharyLowell · Pull Request #28187 · PX4/PX4-Autopilot · GitHub
  2. Relevant to Romain’s PR:
  3. Is there a dedicated call between PX4 and QGC? There is an issue addressed which might need QGC team’s attention: fix(PlanManager): resend last mission waypoint in case of final ack timeout by MaEtUgR · Pull Request #14895 · mavlink/qgroundcontrol · GitHub
    • No dedicated call but teams are actively in touch.

Action Items

2

Hi dev team,

I created a commercial web app for multicopter PID tuning. I’d like to reference it in the PX4 documentation: PR28272
Do you have a policy regarding third party commercial software ?

I’ll join the call tomorrow to have your opinion on it.

3

Definitely join the call.

FWIW I am not opposed to 3rd party commercial software being included in the documentation provided it is clear that it

  • isn’t part of the open source offering,
  • Who it is supported by (where you go for help) and that it is not supported by PX4
  • is honest and open about what it provides
  • isn’t promoted over/instead of tools provided by the team.

This is why we have disclaimers at the top of [manufacturer boards].

I’ll look at your PR. Please cross link the discussion from the dev call to your PR once it has been made.

4

@rroche @dirksavage88 We need more eys on feat(avoidance): fuse external avoidance setpoints in Position/Mission by ZacharyLowell · Pull Request #28187 · PX4/PX4-Autopilot · GitHub. Its a “simplified headless generalization of the obstacle avoidance/collision detection integration interface” :slight_smile: .

It allows a system to provide an external setpoint while in missions/position mode. More or less what obstacle avoidance did, but without committing to the unsupported reference implementation, and instead providing a lot of hard tests.

We dropped the old interface for good reasons around support and testing. We haven’t replaced it with anything that can do the job (and no PX4 ROS 2 Waypoint Missions | PX4 Guide (main) is not an adequate subsitute). But that doesn’t mean this is adequate.

So can we get more eyes on it?

5

Commercial software is welcome, we just gotta make sure its in the right spot and being careful of endorsements, I’ll provide feedback on the PR.

6

@hamishwillee Please see the updated call notes from today.

7

Thanks @farhang

I see that you discussed the setpoint issue - but no comment on the resolution?

8

Commented on the PR @hamishwillee