2025-05-28T15:00:00Z List of all Dronecode events
Announcements
Future Events
Flight Testing Update
Release Discussion
Bug Report / Q&A
PX4 Release Testing PX4 v1.16.0-rc1 is out, and we need your help with testing!
QGC v5.0.0-rc2 Alert
Nothing scheduled yet. If anyone is interested to host a Meetup please reach us out. Always happy to have it organized.
About the Test Team 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:
v1.16 Release Discussion
Release Candidate v1.16.0-rc1
The first release candidate for the upcoming release is finally available trough github and QGC.
We need help with flight testing, especially for early adopters and users with free time who can provide logs from flights with their drones.
Release Testing
Testing Tracker
opened 04:08PM - 08 Jan 25 UTC
bug-report
## :exclamation: About
💡 For the upcoming v1.16 release, we are asking the Commu… nity for flight tests. This issue will be used for keeping track of all the tests from the Community.
If you're unsure about upgrading, please read the preliminary release notes on the PX4 docs. Pay close attention to the Upgrade Guide before deciding if v1.16 is right for you.
- [v1.16 Release Notes](https://docs.px4.io/main/en/releases/1.16.html)
## ❓ Why we need flight testing
🌏 Thousands of people around the world depend on the stable release of PX4.
🖐️ Before every major release, as much testing as possible is needed to ensure that our release actually works!
😯 Simply said, **more testing = better release**
🤗 We would like to encourage every community member to join us in improving PX4!
## 🤷 How you can help with flight testing
😱 Even if you have never contributed a flight testing report, fear not! Please follow the steps below for the details of how you can contribute to flight testing.
1. **Select** a category from the "flight testing matrix" below
1. **Flash** the firmware (documented below)
1. **Test**
1. **Upload** the log (documented below)
1. **Report** the test in this issue thread!
## Test Procedures
https://docs.px4.io/main/en/test_and_ci/test_flights.html
### How to flash v1.16 pre-release firmware
1. Open QGC
3. Click the Q icon on upper right > Vehicle Setup > Firmware (Step 1 in picture)
4. Connect your flight controller to the computer
5. When the Firmware setup window pops up, click "Advanced settings" checkbox
6. Select "Beat Testing (beta)" from the drop down (Step 2 in picture)
7. Click "Ok"
This should automatically flash & reboot your flight controller with the latest v1.16 beta release!
### How to share your log
First, retreive the log from the flight controller in QGC Q icon > Analyze Tools > Log Download, and find the log you want to download.
Then:
1. Go to https://logs.px4.io/
2. Click on "Flight Report" tab (this allows public viewing of the log in the [browse page](https://logs.px4.io/browse))
3. Add the ULog file
5. Fill in the description, feedback, and video URL (if available)
6. Click "Upload"
7. Copy and paste the link of the log, and share it to this thread
When posting on this thread, please mention what kind of test it was (especially if it is one of the testing matrix options) & general info behind it!
## Questions?
Feel free to ask any questions regarding flight testing in the #dev-team channel in the [discord server](https://discord.gg/dronecode)!
## Results (05/12/25)
💪 **Release Testing**
| Date | Status | Submitter | Release | Platform | Flight Controller | Flights / Logs | Notes | Link |
| --------- | ------ | ------------ | -------------- | ---------- | ----------------- | -------------- | ------------------------------------------------------------------------- | --------------------------------------------------------------------------------- |
| 1/16/2025 | ❌ | afwilkin | v1.16.0-alpha1 | Quadcopter | Pixhawk 4 | 2 | | [Link](https://github.com/PX4/PX4-Autopilot/issues/24188#issuecomment-2596594336) |
| 1/23/2025 | ✅ | afwilkin | v1.16.0-alpha1 | Quadcopter | Pixhawk 4 | 2 | | [Link](https://github.com/PX4/PX4-Autopilot/issues/24188#issuecomment-2611482935) |
| 1/29/2025 | ✅ | afwilkin | v1.16.0-alpha1 | Quadcopter | Pixhawk 4 | 6 | | [Link](https://github.com/PX4/PX4-Autopilot/issues/24188#issuecomment-2622581014) |
| 1/29/2025 | ✅ | afwilkin | v1.16.0-alpha1 | Quadcopter | Pixhawk 4 | 2 | | [Link](https://github.com/PX4/PX4-Autopilot/issues/24188#issuecomment-2622581014) |
| 2/10/2025 | ✅ | afwilkin | v1.16.0-alpha1 | Quadcopter | Pixhawk 4 | 5 | | [Link](https://github.com/PX4/PX4-Autopilot/issues/24188#issuecomment-2649177017) |
| 3/5/2025 | ✅ | DroneWuKong | v1.16.0-rc1 | Quadcopter | Pixhawk 6X-RT | 11 | | [Link](https://github.com/PX4/PX4-Autopilot/issues/24188#issuecomment-2851994468) |
| 5/9/2025 | ✅ | afwilkin | v1.16.0-rc1 | Quadcopter | Pixhawk 6C | 2 | | [Link](https://github.com/PX4/PX4-Autopilot/issues/24188#issuecomment-2867864092) |
| 5/13/2025 | ✅ | TeddyZaremba | v1.16.0-rc1 | Quadcopter | VOXL 2 | 8 | [Precision land issue](https://github.com/PX4/PX4-Autopilot/issues/24850) | [Link](https://github.com/PX4/PX4-Autopilot/issues/24188#issuecomment-2880662926) |
| 5/19/2025 | ⚠️ | dk7xe | v1.16.0-rc1 | Quadcopter | Pixhawk 6X-RT | 9 | Various inconsistencies | [Link](https://github.com/PX4/PX4-Autopilot/issues/24188#issuecomment-2895445954) |
| 5/20/2025 | ✅ | dirksavage88 | v1.16.0-rc1 | Quadcopter | Pixhawk 6X | 8 | QGC v5 Crash | [Link](https://github.com/PX4/PX4-Autopilot/issues/24188#issuecomment-2898223625) |
| 5/21/2025 | ⚠️ | DroneWuKong | v1.16.0-rc1 | Quadcopter | Cube Orange+ | 1 | No GPS | [Link](https://github.com/PX4/PX4-Autopilot/issues/24188#issuecomment-2899811372) |
| 5/21/2025 | ⚠️ | JulianOes | v1.16.0-rc1 | Quadcopter | Cube Orange+ | 1 | Tuning required | [Link](https://github.com/PX4/PX4-Autopilot/issues/24188#issuecomment-2901915380) |
Testing Matrix
Date
Status
Submitter
Release
Platform
Flight Controller
Flights / Logs
Notes
Link
1/16/2025
afwilkin
v1.16.0-alpha1
Quadcopter
Pixhawk 4
2
Link
1/23/2025
afwilkin
v1.16.0-alpha1
Quadcopter
Pixhawk 4
2
Link
1/29/2025
afwilkin
v1.16.0-alpha1
Quadcopter
Pixhawk 4
6
Link
1/29/2025
afwilkin
v1.16.0-alpha1
Quadcopter
Pixhawk 4
2
Link
2/10/2025
afwilkin
v1.16.0-alpha1
Quadcopter
Pixhawk 4
5
Link
3/5/2025
DroneWuKong
v1.16.0-rc1
Quadcopter
Pixhawk 6X-RT
11
Link
5/9/2025
afwilkin
v1.16.0-rc1
Quadcopter
Pixhawk 6C
2
Link
5/13/2025
TeddyZaremba
v1.16.0-rc1
Quadcopter
VOXL 2
8
Precision land issue Link
5/19/2025
dk7xe
v1.16.0-rc1
Quadcopter
Pixhawk 6X-RT
9
Various inconsistencies
Link
5/20/2025
dirksavage88
v1.16.0-rc1
Quadcopter
Pixhawk 6X
8
QGC v5 Crash
Link
Issue Reporting, and Flight Log sharing
Release Blockers Discussion
ESC Calibration Issues (PX4-Autopilot #24635 ):
@AWilkins_Ascend will follow up with testing on this PR
VTOL DSHOT Issues @dk7xe
TODO : @rroche check this was fixed by PR
main ← pr-vtol-schedule-freq
opened 02:16PM - 15 Apr 25 UTC
### Solved Problem
Specific ADP ESCs lost communication when switching from MC … -> FW in case of using DSHOT150. When switching back from FW -> MC the motors would still not spin.
The communication loss is due to incorrect DSHOT messages on the wire. As can be seen multiple DSHOT frames got packed into one large stream:
The cause of this is that a DSHOT transmission is started while an old one was still in progress. This occured only on DSHOT150 as the other ones are quick enough for this to not happen. The reason for this is a extremly fast scheduling of the DSHOT driver:
All this could be traced back to `vtol_att_control` being called too often due to it having configured 4 topic callbacks which are triggered by `MulticopterRateControl` and `FixedwingRateControl` which are triggered by an update of `vehicle_angular_velocity`. So one update of `vehicle_angular_velocity` causes a burst of 4 schedules of `vtol_att_control`.
### Solution
Depending on the VTOL mode only the relevant callbacks are registered. In addition only the `torque` topics are subscribed as they are published after the `thrust` topics.
### Changelog Entry
For release notes:
```
Bugfix: Reduce vtol schedule frequency to avoid DSHOT150 problems
```
### Test coverage
- On the bench with an ADP F3 80 and DSHOT
- Flight tested on a Loong VTOL with PWM output
opened 12:55PM - 20 Jan 25 UTC
bug-report
### Describe the bug
When configuring the autopilot to be in Generic Standard P… lane the actuator outputs seemed to be glitchy. When putting the scope on the signal I noticed this.
As you can see shortly after `DShot::Run()` is called it get called a second time and then it operates @ 400Hz.
When using multicopter (MC) I don't see this behaviour
### To Reproduce
Reset FMU, select "Generic Standard Plane" airframe.
In actuators select dshot, and set MAIN1 to Motor 1.
Then connect scope on the Pin and you see the double output
### Expected behavior
A periodic pulse of the Dshot output without bursts
### Screenshot / Media
_No response_
### Flight Log
_No response_
### Software Version
Main
### Flight controller
V6X-RT
### Vehicle type
Fixed Wing
### How are the different components wired up (including port information)
_No response_
### Additional context
_No response_
Q1:
Discussed PRs:
Discussed Issues:
1 Like
Would love to discuss what the best way to fix the problematic header files is.
main ← SindreMHegre:neural_control_with_tflm
opened 12:23PM - 19 Feb 25 UTC
### Solved Problem
Using neural networks for various tasks on UAVs in research … is becoming more and more commonplace. My aim is to provide a module that can be used to replace the MC controller with NN to lower the barrier for using RL and NN on UAVs in general, and give researchers and hobbyist a place to start for NN use.
### Solution
- Add TensorFlow Lite Micro as an inference lib into PX4
- Make custom board configs with neural controllers
- Make a module for NN control
### Changelog Entry
For release notes:
```
Feature: Neural control mode for PX4, with possibility to use your own neural networks.
New parameters: MC_NN_EN, MIN_RPM, MAX_RPM, THRUST_COEFF
Documentation: read docs.px4.io/advanced/neural_networks, tflm and nn_module_utilities
```
### Alternatives
We could also look into using Eigen or executorch
### Test coverage
- Built and tested SITL with the x500
https://review.px4.io/plot_app?log=52502d02-009e-4d1f-baac-a49dd51cfdef (check neural_control topic)
- Built and tested HITL with pixracerpro and jMAVSim Hitl, note that the sim itself seemed a bit unstable and the network is not optimized for this model.
https://review.px4.io/plot_app?log=43d2ba6c-3d05-4d7f-a31b-490a57b3e647
- Tested live on ARL LMF model:
https://review.px4.io/plot_app?log=d101189d-672e-42a3-9d39-828c675dde57
https://www.youtube.com/watch?v=lY1OKz_UOqM&t=1s
https://arxiv.org/abs/2505.00432
### Context
Other feature requests:
- Put in different controller parameters with possibilities to replace different parts: Full e2e, only control, only allocation, Allocation and control as two separate networks.
- Script to give thrust and delay parameters from a flight log
2 Likes
I would appreciate help on this topic very much, if there is time!
1 Like
If I’m a bad coder and accidentally access a nullptr in module-X , is there a way to contain the resulting segfault, i.e. only module-X stops functioning? Or (on the VOXL2) since PX4 is a single process is it an inherent risk that a segfault occurring in any module will bring down the entire PX4 process?
1 Like
PX4 Release Testing
QGC v5.0.0-rc2 Alert
Release Candidate v1.16.0-rc1
Release Testing
Issue Reporting, and Flight Log sharing
Release Blockers Discussion