rroche
March 28, 2023, 4:02pm
1
April 04, 2023
The maintainers meeting is a meeting for the developer team to coordinate on pressing issues and to plan the development of the PX4 Autopilot project, the community is welcome to join and listen, but won’t be able to speak unless specific access is granted ahead of time.
Meeting Link
Agenda
PX4 v1.14 release
Discuss forum utilization
Meeting Notes
General
Dockerhub is not abandoning open source projects!
PX4 v1.14 release progress
Added issues for further discussion:
User Testing
opened 04:22PM - 22 Mar 23 UTC
closed 05:47PM - 03 Nov 23 UTC
Documentation 📑
discussion
## :exclamation: About
💡 For the upcoming v1.14 release, we are asking the Comm… unity 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.14 is right for you.
- [v1.14 Release Notes](https://docs.px4.io/main/en/releases/1.14.html)
## Pending Issues
- [x ] Cube Orange Plus target for beta not available in S3 bucket: https://github.com/PX4/PX4-Autopilot/issues/21358#issuecomment-1629618613
## ❓ 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 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!
### :bookmark_tabs: Flight testing matrix
📖 **Here are the table of things we need tests for.**
This will constantly get updated, and your contribution to testing the missing slots (tests needed) will be greatly appreciated!
| Title | Description | Vehicle/Hardware requirements | Testing procedure | Test logs | Related issue/posts |
|---|---|---|---|---|---|
| General | By testing your usual setup, we want to capture any regression / weird behaviors you may notice | Any | Test what you usually use for your personal usage, and report it to the comment below | | |
| Optical Flow | With optical flow fusion enabled, the preflight failures has been observed. | Any Optical Flow / Capable of either Altitude or Position mode | With Optical Flow enabled, try to arm in altitude or position mode | | https://github.com/PX4/PX4-Autopilot/issues/20929 |
| ~~Random 100% Thrust~~ | Due to edge case conditions by land detector & hover thrust estimator, multirotors showed occasional 100% thrust. https://github.com/hendjoshsr71 can reproduce it for now. | Multirotor (with low hover thrust input: e.g. 30%) | Takeoff, land and keep the throttle at low position. Occasionally vehicle will exhibit 100% thrust suddenly and shoot to the sky. | | https://github.com/PX4/PX4-Autopilot/issues/20275 |
### How to flash v1.14 beta firmware
![beta_flashing](https://user-images.githubusercontent.com/23277211/230138126-c7b02c00-f07b-4a4f-b6b7-866d69db6520.png)
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.14 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.
![log_uploading](https://user-images.githubusercontent.com/23277211/230143915-4dad89ec-ab6d-43f3-9e5f-7a4624faa56e.png)
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)!
TODO: Guide on how to do flight report - Junwoo
Release Notes
opened 03:50PM - 28 Mar 23 UTC
closed 05:27PM - 02 Aug 23 UTC
Documentation 📑
Work in Progress Release notes for v1.14
## Excel Sheet
We are drafting the … Relase Note in this excel sheet: https://docs.google.com/spreadsheets/d/14F6lDI5s3KbDqstinBxwU1Ovtq3X9bE_NcvXGPlDGG4/edit#gid=939619685
### Related PRs panel
![image](https://user-images.githubusercontent.com/23277211/233824750-40972b1e-bd07-47d1-b710-eaff82180b61.png)
For remembering the changes since v1.13 release, in the "Related PRs by Maintainer" panel of the excel sheet: Maintainers & Members who contributed to development can find the PRs they were involved with, and browse them in the Github UI.
**Note: Find all the PRs that got introduced between v1.13 release and current main**: [here](https://github.com/PX4/PX4-Autopilot/pulls?q=is%3Apr+merged%3A%3E%3D2022-04-27+base%3Amaster+base%3Amain)
### Draft panel
![image](https://user-images.githubusercontent.com/23277211/233825724-98b177c6-9d6f-426f-809c-17d7bb832ebc.png)
After going through them, please add the relevant PR / Features in the 'Release Note Draft' panel in the sheet!
<!--
> ⏰ Notes below will be updated based on the draft in the Excel sheet!
## Highlights
- New actuator configuration
https://docs.px4.io/main/en/config/actuators.html
- New mixing system: Control allocation
https://docs.px4.io/main/en/concept/control_allocation.html
- New failsafe handling
https://docs.px4.io/main/en/config/safety.html
- Simultaneous multi-height sources fusion:
https://docs.px4.io/main/en/advanced_config/tuning_the_ecl_ekf.html#height
- Native ROS support thanks to XRCE-DDS
## New hardware support
-
Pre existing
- VOXL2 better support: https://github.com/PX4/PX4-Autopilot/pull/21426
## Upgrade Notice
- User's upgrading from prior releases should follow the updated Actuaor guide before flight
https://docs.px4.io/main/en/config/actuators.html
## Other
- Snapdragon Spektrum RC refactor: https://github.com/PX4/PX4-Autopilot/pull/21427
-->
TODO: Junwoo and Ramon will work on this. Ask through group for feedback.
Control allocation & Failsafe state machine would be 2 major ones for sure
Method: Go through all the PRs that went in since v1.13 release, and group them
Documentation Sync
Discord is the easiest way to communicate over voice, video, and text. Chat, hang out, and stay close with your friends and communities.
Discussion between Daniel and Hamish would be sufficient. The release note preparation will be done & pinged in the thread.
opened 07:13PM - 21 Mar 23 UTC
closed 11:55PM - 23 May 23 UTC
As discussed in [today's Maintainers Call](https://discuss.px4.io/t/31237) some … parts of the documentation are out of sync with the PX4 `main` branch. This issue aims to capture the main points that should be fixed in view of the release of `v1.14.0`
- [x] #2345
- [x] #2265
- [x] [EKF2_AID_MASK](https://docs.px4.io/main/en/advanced_config/parameter_reference.html#EKF2_AID_MASK) refactoring and [ECL/EKF Overview & Tuning](https://docs.px4.io/main/en/advanced_config/tuning_the_ecl_ekf.html) update.
Associated PX4-Autopilot PRs:
- PX4/PX4-Autopilot#20497
- PX4/PX4-Autopilot#20501
- PX4/PX4-Autopilot#21032
Documentation PR: #2459
- [x] #2364
- [x] NAV_TRAFF_A_RADM and NAV_TRAFF_A_RAD - Docs PR is needed (https://github.com/PX4/PX4-Autopilot/pull/21283)
- [ ]
If anyone is aware of other major points, please add them in the comments.
Note: ROS1 - ROS 2 bridge would be removed, as use cases don’t really exist.
v1.14 release candidate blockers
Critical bugs that need to be fixed (below), before cutting a release candidate:
Optical flow preflight failure
opened 12:40AM - 14 Jan 23 UTC
closed 08:55AM - 20 Jul 23 UTC
bug-report
release blocker ❗️
In current main, with optical flow fusion enabled, I am unable to arm in altitud… e or position mode. If I take off in manual I am able to switch to altitude and position no problem.
On a larger quad with long landing gear, this issue doesn't present itself. It appears to be a problem with the optical flow close to the ground.
https://github.com/PX4/PX4-Autopilot/blob/main/src/modules/ekf2/Utility/PreFlightChecker.cpp#L85-L91
![image](https://user-images.githubusercontent.com/2019539/212567820-97ff03be-82c1-476e-9c9b-ed8024a8bff5.png)
Idea on fixing (Daniel):
on init
, take care of test ratio? (infinity)
Random 100% Thrust
opened 05:03PM - 21 Sep 22 UTC
closed 08:44AM - 09 May 23 UTC
Multirotor 🛸
priority-critical
bug-report
release blocker ❗️
On recent main, occasionally I will get 100% thrust from the position controller… .
This is with multiple baros and a rangefinder.
Took off in position mode, then it went full thrust.
https://review.px4.io/plot_app?log=f0acb7d2-7d1e-4ec9-92ca-0a816fd131f8
I was trying to land, sitting on the ground waiting for it to disarm. It wouldn't disarm so I throttled back up a bit to try again and it went 100% thrust.
https://review.px4.io/plot_app?log=10ece277-09e1-4e67-be8e-ca7b87b7555e
In the current beta, it is likely solved already. But Josh can help replicate this issue.
The PR itself *reduces the likelihood of hitting the edge case (100% thrust)
Daniel can follow up in the PR itself
Land detector has been improved (fact) & hover thrust estimator improvement
Discuss forum utilization
About
Recently concern was raised in Discord regarding the index-ability of the questions & answers in discord server.
The problem is that since the discussion in discord server is not indexed by a search engine, users can’t find the discussion easily and they get lost after a while.
The obvious solution is to encourage this discuss forum more (since it is indexed, and is more efficient at preserving knowledge from the past), but the question is how we get there.
I’m opening this thread this …
We could perhaps group FAQs manually and add it to user guide, to allow it to be search-engine indexable
Question: Is there a nice program to integrate discuss forum & discord?
Documentation problem
Mixer related functionality wasn’t appropriately removed from the doc (One more support for atomic documentation inside the codebase)
Tier support
Next release
Optical flow improvement can be done - Daniel
Are there release notes ready? If so, can you point me to them?
We decided that we will be breaking down the PR lists to have each maintainer review them and select notable PRs.
However, there are 4 main PRs already selected in the release notes issue linked above
Thanks, I think those 4 PRs have all got reasonable documentation in place.