2025-07-09T15:00:00Z List of all Dronecode events
Announcements
Future Events
Flight Testing Update
Release Discussion
Bug Report / Q&A
Upcoming meetup in Korea
PX4 Release Testing PX4 v1.16.0-rc2 is out, and we need your help with testing!
QGC v5.0.0-rc3 Alert
Nothing scheduled yet. If anyone is interested to host a Meetup please reach us out. Always happy to have it organized.
Open Source Summit EU 2025
ROSCon 2025 Singapore
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:
One blocker for collision prevention with forward facing sensor. Tried in SITL but waiting for hardware.
v1.16 Release Discussion
Release Candidate v1.16.0-rc2
Release Testing
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) |
Project Board
Q1:
Discussed PRs:
SF45 revert missing bin logic by dirksavage88 · Pull Request #25173 · PX4/PX4-Autopilot · GitHub @MaEtUgR might want to take a look.Septentrio resillience reporting by Louis-max-H · Pull Request #25012 · PX4/PX4-Autopilot · GitHub
main ← pr-rmw-zenoh-cpp
opened 11:42AM - 09 Mar 25 UTC
This PR allows Zenoh to directly interface with ROS2 running rmw_zenoh_cpp
http… s://github.com/ros2/rmw_zenoh
rmw_zenoh_cpp isn't stable of as of yet, so compatibility might break again.
- Updates zenoh-pico library to 1.3.4
- Adds rosidl RIHS01 CRC32 hashes for each uORB message, providing type safety and ROS2 can compare it's own px4_msgs with that.
- Introduce ZENOH_DOMAIN_ID for set matching ROS_DOMAIN_ID on PX4
- Allow to map uORB instance topic to a custom ROS2 topic thanks to @BenChung
To reproduce
Have a Ubuntu 24.04 machine with ros2 kilted (now also works with jazzy as long you're running `0.2.5-1noble.20250620.205111` or newer)
Install rmw_zenoh_cpp
```
sudo apt update && sudo apt install ros-kilted-rmw-zenoh-cpp
```
Set RMW to rmw_zenoh_cpp
```
export RMW_IMPLEMENTATION=rmw_zenoh_cpp
```
Start zenohd using
```
ros2 run rmw_zenoh_cpp rmw_zenohd
```
You'll see something like this
```
2025-03-09T11:27:10.020634Z INFO ThreadId(02) zenoh::net::runtime::orchestrator: Zenoh can be reached at: tcp/192.168.1.104:7447
```
On your PX4 build with Zenoh compiled enable zenoh on startup
```
param set ZENOH_ENABLE 3
```
Configure network to connect to the machine running zenohd, 192.168.1.104 in this example.
Note `px4_sitl_zenoh` defaults to localhost so no need to change it.
```
zenoh config net client tcp/192.168.1.104:7447#iface=eth0
```
Create a custom publisher mapping for example cpuload to the ROS2 /fmu/out/cpuload topic
```
zenoh config add publisher /fmu/out/cpuload cpuload
```
To verify your config type `zenoh config` it should look similar to this
```
nsh> zenoh config
Network config:
Mode: client
Locator: tcp/192.168.1.104:7447#iface=eth0
Publisher config:
Topic: /fmu/out/cpuload
Type: cpuload
```
Reboot PX4
Now on your Linux get topic info using
```
peter@desktop-peter:~/ros2_ws_kilted$ ros2 topic info /fmu/out/cpuload -v
Type: px4_msgs/msg/Cpuload
Publisher count: 1
Node name: px4_aabbcc00000000000000000000000000
Node namespace: /
Topic type: px4_msgs/msg/Cpuload
Topic type hash: RIHS01_f41315fb98baf77228df67b159df4fdd978620d38cd5f38dd883d6fa3817a7af
Endpoint type: PUBLISHER
GID: 52.57.f3.91.ca.da.7e.c3.c9.dd.d7.78.94.b1.25.67
QoS profile:
Reliability: RELIABLE
History (Depth): KEEP_LAST (7)
Durability: VOLATILE
Lifespan: Infinite
Deadline: Infinite
Liveliness: AUTOMATIC
Liveliness lease duration: Infinite
Subscription count: 0
```
Subscribe to a topic
```
ros2 topic echo /fmu/out/cpuload
```
Ready for review, ci is all green now. And works with ros2 jazzy and kilted.
2 Likes
Need some input on this PR:SF45 revert missing bin logic by dirksavage88 · Pull Request #25173 · PX4/PX4-Autopilot · GitHub
We need to figure out where the new logic didn’t capture the correct distance data in the obstacle distance bins (long term fix), however in this PR I have a short term fix to revert changes made by @Mahima_Yoga to the handling missing bins logic.
1 Like
Hi !
main ← Louis-max-H:pr-resillience2
opened 02:46PM - 11 Jun 25 UTC
### Solved Problem
When errors occur in attached GNSS receivers, there is no … way to report them to the user so they know what is going wrong.
This PR is needed by QGC : https://github.com/mavlink/qgroundcontrol/pull/13009
This is an update of PR made by @flyingthingsintothings https://github.com/PX4/PX4-Autopilot/pull/23096
### Solution
- Add automatic configuration for Septentrio receivers to report resilience information every second
- Add to Septentrio parser so it can parse the new message
- Change the uORB message for GNSS information to support this new
- MAVLink message is in development.xml, you need to pass `CONFIG_MAVLINK_DIALECT="development"` to your `default.px4board`
Changelog Entry
For release notes:
```
Feature: Report resilience information from GNSS receivers
Documentation: Need to clarify page ...
```
### Test coverage
- I have tested this PR using a Septentrio receiver to emulate jamming, there was just a typo that has now been fixed.
### Context
- Link to old PR : https://github.com/PX4/PX4-Autopilot/pull/23096
- Link to QGC PR : https://github.com/mavlink/qgroundcontrol/pull/13009
1 Like
PX4 Release Testing
QGC v5.0.0-rc3 Alert
Release Candidate v1.16.0-rc2
Release Testing