PX4 Sync / Q&A: Mar 05, 2025

PX4 Sync / Q&A: Mar 05, 2025
Dronecode Calendar

Agenda

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

Announcements

Maintainers Meeting

  • We need to discuss a few Quality and Functional Safety improvements
  • Including release cadence, and testing updates
  • All maintainers should join, an agenda will be distributed shortly
  • Ramon will be contacting everyone directly via email to coordinate a date/time

Next Dronecode Meetup

Philadelphia, Pennsylvania, USA

Future Events

Flight Testing Update

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:

  • Are we testing Fixed Wing / VTOL: not yet, but platforms are available for bringup
  • Are we using QGC Daily or Stable: Stable for now, we want to switch to Daily, but once video streaming is fixed in daily.

Release Discussion / Updates

v1.16 Release Discussion

  • Fixed Wing known blockers: @sfuhrer none on top of mind
  • Multi Copter known blockers: @MaEtUgR none on top of mind
  • Optical Flow: @AlexKlimaj we should likely get height estimate fixed in main
    • @dagar Let’s check the logs to make how to controllers are configured
    • TODO Let’s make a Test Case for the flight test team so we can validate
  • Simulation known blockers:

Resources

Bug report / Q&A

[Bug] PX4 Min PWM & Disarm PWM set to same values

Self assigned to @farhang :

PRs needing review

Remove random walk from gazebo-classic models. Currently causing CI SITL tests to fail frequently. See comments in PR:

Discussion:
Let’s have a quick sync between @dakejahl and @Jaeyoung-Lim @dagar so we can address his isssue and fix the overall problems

PR further improves the build system and adds a template as an example. Docs and gstreamer plugin to be coming:

An opportunity to add an ocean world with waves. A barge with an aruco tag would be sweet for testing ship takeoff and landings. This has been a feature people ask about for years. Any other interest? (Relevant plugin repo: GitHub - srmainwaring/asv_wave_sim: This package contains plugins that support the simulation of waves and surface vessels in Gazebo.)

Want to talk about this as there is some weird behavior when selecting x500 v2 (which is a pretty common airframe)

2 Likes

Also want to talk about this

as I can see people getting stuck when updating firmware versions and wondering why their VIO is no longer working

2 Likes

I won’t be on the call tomorrow but there are just a couple of things I wanted to bring up for comment from others.

Remove random walk from gazebo-classic models. Currently causing CI SITL tests to fail frequently. See my comments in PR.

I’ve been doing a large scale refactor and improving gz sim integration. Recently I added custom plugin support (optical flow), this PR further improves the build system and adds a template as an example. I just wanted to share this, I will work on docs once it’s a little further along. Stay tuned for a gstreamer plugin.

I think we should use the opportunity in this PR to add an ocean world with waves. A barge with an aruco tag would be sweet for testing ship takeoff and landings. This has been a feature I’ve seen people ask about for years. Any other interest?

Plugin repo for the above, for adding waves and surface vessels

2 Likes

Test Card process updates

Updated px4-dev container

  • native multi-arch support for x86 & arm64
  • based on ubuntu 24.04, using new ubuntu.sh
  • installs gcc 13 via apt
  • replaces older containers in our CI infrastructure:
    • Builds the board matrix with them
1 Like