PX4 Dev Call: Apr 22, 2026 (Team sync, and Community Q&A)

Coordination Calls PX4 Autopilot
1

PX4 Sync / Q&A - 2026-04-22T15:00:00Z

Announcements

PX4 Dev Summit Schedue is live :backhand_index_pointing_down::backhand_index_pointing_down::backhand_index_pointing_down::

Events

PX4 & Foxglove Meetup @ ModalAI San Diego

Release

Current tag: v1.17.0-rc2
Target date: June 2026
Flight Tracker: v1.17 Release Testing

Updates:

Issues:

Decisions:

TODO:

PRs for Review

Q&A

Action Items

2

Hi, I’m working on a student project involving PX4 with a Pixhawk flight controller, a companion computer (Raspberry Pi with ROS2), and a custom control/monitoring application written in C++ (using MAVSDK and Qt).

The goal of the project is to create drone light painting, where the drone flies a 2D path and generates a visible image (e.g. text) using LEDs and long-exposure photography.

I would like to better understand the full communication flow in such a setup:

  1. Could you briefly explain how the data flow should ideally work end-to-end?
    Starting from a mission path (waypoints with coordinates and LED color data) provided via a CSV file in our application, then sending it via MAVLink to PX4, and in parallel forwarding LED-related data via ROS2 topics to a Raspberry Pi companion computer so that the LEDs are triggered at the correct positions.

  2. Is it best practice to upload the full mission to PX4 before flight, or stream waypoints during execution?

Thanks a lot!

1 Like
3

Here’s some examples on how to run missions with ROS 2 and PX4 px4-ros2-interface-lib/examples/cpp/modes/mission at main · Auterion/px4-ros2-interface-lib · GitHub

1 Like