# PX4 Dev Call: Sep 30, 2026 (Team sync, and Community Q&A) **URL:** \ **Category:** PX4 Autopilot\ **Created:** [September 28, 2026, 10:02am UTC](https://discuss.px4.io/t/px4-dev-call-sep-30-2026-team-sync-and-community-q-a/49549 "2026-09-28T10:02:04Z")\ **Posts on this page:** 2\ **Page:** 1
**Author:** ![system](https://discuss.px4.io/uploads/default/original/3X/7/3/73ce918bdcd64854de904f0c8d9ab70ca9723f2a.png) [@system](https://discuss.px4.io/u/system)\ **Post date:** [September 28, 2026, 10:02am UTC](https://discuss.px4.io/t/px4-dev-call-sep-30-2026-team-sync-and-community-q-a/49549/1 "2026-09-28T10:02:04Z")
# PX4 Sync / Q&A - 2026-09-30T15:00:00Z **This week:** 85 PRs merged | 162 awaiting review | 0 new bugs * * * ## Announcements MAVSDK v4 Release > **[Releases · mavlink/MAVSDK](https://github.com/mavlink/MAVSDK/releases)** > > API and library for MAVLink compatible systems written in C++ - mavlink/MAVSDK * * * ## Events > **[Open Source Summit Europe](https://events.linuxfoundation.org/open-source-summit-europe/)** > > The premier vendor-neutral conference for open source developers and technologists to collaborate, share information and learn about the latest technologies and innovations across open source. > **[PX4 Developer Summit After Party sponsored by Auterion · Luma](https://luma.com/l3vd0qth)** > > Come hang out with the open source robotics and embedded Linux crowd in Prague. The Dronecode Foundation and Auterion are taking over Bastion, a garden… > **[Dronecode Community Meetup @ Amsterdam, NL · Luma](https://luma.com/6k50nmro)** > > Dronecode Amsterdam Meetup > Join the Dronecode community in Amsterdam at our next meetup sponsored by DeltaQuad for an afternoon of talks, demos, and drinks… * * * ## Dev Call Items - None * * * ## Release > > > \## :exclamation: About > 💡 For the upcoming v1.18 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.17 is right for you. > > \- \[v1.18 Release Notes(Link TBD)\](https://docs.px4.io/main/en/releases/1.18.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.18 pre-release 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 "Beta 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.18 alpha 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)! > > > \## Results (Date TBA) > > \*\*Release Testing\*\* **Updates:** **Status** : Test Flights in progress for v1.18.0-rc1, pending flights are - NXP Tropic FMU - Fixed Wing Vehicle **Issues:** **Decisions:** We will be waiting for the test team to wrap up the rc1 test campaign before we cut a new rc2 and make focus testing, we think we can have a stable v1.18 release by early November * * * ## PRs Merged This Week [85 PRs merged this week →](https://github.com/PX4/PX4-Autopilot/pulls?q=is:pr+is:merged+merged:%3E=2026-09-21) ## PRs Awaiting Review [162 PRs awaiting review →](https://github.com/PX4/PX4-Autopilot/pulls?q=is:pr+is:open+draft:false+review:none) * * * ## New Bug Reports - No new bugs ## Other New Issues [9 new issues →](https://github.com/PX4/PX4-Autopilot/issues?q=is:issue+created:%3E=2026-09-21+-label:bug) * * * ## Q&A **Ibrahim** : Is there any simulation for PX4? > **[Simulation](https://docs.px4.io/main/en/simulation/)** > > Open-source flight stack for drones and autonomous vehicles. **Hououin Kyouma** : Where can I start contributing? Test Flights for v1.18 are a good place to start, beyond that search the issue list by labels. * * * ## Action Items ---
**Author:** ![yigitcan-ozturk](https://discuss.px4.io/user_avatar/discuss.px4.io/yigitcan-ozturk/32/22039_2.png) [@yigitcan-ozturk](https://discuss.px4.io/u/yigitcan-ozturk)\ **Post date:** [September 29, 2026, 12:24am UTC](https://discuss.px4.io/t/px4-dev-call-sep-30-2026-team-sync-and-community-q-a/49549/2 "2026-09-29T00:24:04Z")
**Q&A proposal: distinguishing first observable anomaly from first relevant divergence in PX4 ULog analysis** In recent log-analysis cases, an estimator or sensor consistency anomaly can appear well before the visible control loss or failsafe event. I’d be interested in discussing whether there is a recommended PX4-side methodology for separating: - earliest observable anomaly, - first relevant divergence in the incident sequence, - downstream failsafe detection, - and an actual causal conclusion. In particular, which estimator/control/status signals do PX4 developers consider most reliable for reconstructing this sequence without over-interpreting temporal precedence as causality?