@wolke This is great to hear (for me not you). I’m glad it isn’t just me having this issue. FYI: Today I did a test where I did back to back fligths with PX4 and then Arducopter. The vibe levels all looked good for Arducopter but were dangerously high for PX4. I posted about that here:
opened 04:22PM - 22 Mar 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.
## ❓ 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)!
Given your test and mine, this seems to definitely be a firmware bug of some sort. I am glad to see that you’ve tested V1.12 and V1.13 to show where the issue arose. I am running 1.14 beta. Looping in @JulianOes on this, as I mentioned this issue in another post , but wanted him to see your testing results as well.
Not sure what to do here except wait for the dev team to try to resolve this.