2025-12-03T16:00:00Z Agenda
Announcements
Future Events
Flight Testing Update
Release Discussion
Bug Report / Q&A
Announcements
Future Events
Flight Testing Update
About the Test TeamThe team at Ascend Engineering (Chicago). are running flight testing for the community.
How to reach out to the team
GitHub: Tag user @PX4PX4PX4PX4 **/testflights**
Discord: Flight Testing & Log Analysis
Weekly on the PX4 Dev Call
How to Request Testing (GitHub)
Write down the steps to te@PX4PX4t 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
Updates :
v1.16.1
New release tag is cut
v1.17.0-alpha1
Q&A:
How to implement Path Following interface for ROS 2 coherent with the fixedwing_mode_manager?
PRs:
1 Like
Please consider discussing adding MAVLink messages for controlling LED strips.
master ← DanielAdelodun:lights-plugin
opened 07:57PM - 19 Nov 25 UTC
### This is a new **set of messages for controlling LED strips**.
It supports… up to **255 LED strips per system and any number of LEDs per strip**.
**Each message can set up to 8 RGB LEDs** on a single strip. Which strip, and which 8 LEDs along the strip are to be set by that particular message are configured using the appropriate fields.
RGB colour values are given as a 24bit hex value 0xRRGGBB (right-aligned in a uint32_t). Each colour channel ranges from 00 -> 255 (0xFF). 8 can be set at a time using the `colors` array of the `LED_STRIP_CONFIG` message.
You can set up to 8 consecutive LEDs along a strip at a time. `length` is used to specify how many (up to 8). Use `index` to indicate where along the strip to start.
**You can also set all LEDs on a strip to the same color, turn all the LEDs off, or have all LEDs on the strip change colours according to the current flightmode by setting the `fill_mode` field appropriately.**
The `strip_id` field is used to set which LED strip to target. How these indices map to hardware would be user defined. setting `strip_id = 255` targets all strips at once.
I've tested adding support for these messages into [MAVSDK](https://github.com/DanielAdelodun/MAVSDK/tree/lights-plugin), [MAVSDK-Proto](https://github.com/DanielAdelodun/MAVSDK-Proto/tree/lights-plugin), and [MAVSDK-Python](https://github.com/DanielAdelodun/MAVSDK-Python/tree/lights-plugin).
And an RP2xxx (Raspberry Pi Pico) based [LED controller]() that reads the messages and configures the attached LEDs.
My intention is to keep maintaining this and to potentially sell [opensource hardware](https://github.com/DanielAdelodun/MAVLink-Lights-Hardware) that can easily plug into a MAVLink flight controller and work as an LED controller.
**Demos:
[Red Heart Using MAVSDK-Python Offboard Example](https://youtu.be/aNKbazAUzbI)
[Waypoints](https://youtu.be/iBu-zbaUTHk?si=AqnKdKJmvez6inXw)**
1 Like
@farhang The discussion to have here is whether PX4 is interested in integrating support for controlling LED strips at all, and if so how and what - do we want them in missions, do we want them via mavlink like a camera rather than direct attached, or both? All integrations have a cost.
If there is strong interest then the proposed dialect could move into development.xml. If not, then the author will have to fork PX4. I don’t want to look closely at the design of these messages unless there is interest in a PX4 integration and support for standardization.
1 Like
