PX4 v1.11 Release Candidates are finally here!
Let’s help the project maintainers to get the release to the finish line by getting involved with testing
Flash via QGC with “PX4 v1.11-rc1”
If the test is successful, please follow this thread. What would be awesome in the reporting:
Your test case and procedure (bench test, autopilot make and model, vehicle type etc. )
If you discovered a bug, please report on Github issue , so the maintainers can quickly triage:
Funnel any necessary conversations in the #release channel on PX4 Slack
Let us know below if you have questions, feedback, or comments.
Hopefully I’m in the right spot at the right time and replying to the right thread in the right way
I ran a preliminary outdoor test on v1.11 RC, but looks like there was Navigation failure due to altitude sensor issues. I’m still trying to pinpoint the issue and unsure if it’s a bug or not (as well as figuring out how to properly report here and find help).
Outdoor Test - Position Hold / RTL test, Modal-AI Flight Core, s500
Question, how can a user without a build system equipped flash the v1.11-rc1?
In the doc :
https://docs.px4.io/master/en/config/firmware.html#custom, there’s no mention for flashing release candidates.
Do you have
Beta Testing (beta): A beta/candidate release. (like mentioned in the documentation) in your QGC setting? Are you updated to QGC daily build?
Yes there’s beta testing option, but isn’t that different from the release candidate 3?
https://github.com/PX4/Firmware/issues/15668 it seems that fixed-wing auto landing is broken in 1.11 and later
PX4 v1.11 has been released.
Thanks to everyone who contributed to flight testing, we couldn’t have done this without you.
[Announcing PX4 v1.11.0]
Community, it’s hard to think its been 8-months since our last release last December, we have all gone through a lot to get here, and it’s time we celebrate, together, as a community.
I want to thank everyone involved with this release for helping us reach a major milestone in our small and humble open-source project. In particular, there are a few individuals that need to be thanked, for their outstanding contributions (in no order):
Jinger Zeng @jinger26