164e7e0356
Fixes: - False positive airspeed failures due to first principle check. This was caused by mixing different throttle units in the check: Some with battery scaling, some without. As the battery depletes, this difference can already trigger the quite sensitive check. Now it uses purely TECS setpoints again, which are without battery scaling. - Slightly wrong synthetic airspeed as battery depletes. Previously, the synthetic airspeed used thrust from vehicle_thrust_setpoint_0, which already includes battery scaling. Battery scaling is intended to offset the effects of a depleted battery, so we command a higher throttle when the battery is empty but we do not go faster. The TECS throttle setpoint more closely reflects the physical response of the vehicle and so it is preferrable to use that for synthetic airspeed. Small simplifications without changing functionality: - update throttle filter only on TECS update. This removes the need to check for data recency inside of it. Functionality is kept - in any case if synthetic airspeed is demanded outside of fixed wing we give trim airspeed. For this we add an explicit if - remove current time argument from update_throttle_filter, is already class variable
PX4 Drone Autopilot
This repository holds the PX4 flight control solution for drones, with the main applications located in the src/modules directory. It also contains the PX4 Drone Middleware Platform, which provides drivers and middleware to run drones.
PX4 is highly portable, OS-independent and supports Linux, NuttX and MacOS out of the box.
- Official Website: http://px4.io (License: BSD 3-clause, LICENSE)
- Supported airframes (portfolio):
- Multicopters
- Fixed wing
- VTOL
- Autogyro
- Rover
- many more experimental types (Blimps, Boats, Submarines, High Altitude Balloons, Spacecraft, etc)
- Releases: Downloads
Releases
Release notes and supporting information for PX4 releases can be found on the Developer Guide.
Building a PX4 based drone, rover, boat or robot
The PX4 User Guide explains how to assemble supported vehicles and fly drones with PX4. See the forum and chat if you need help!
Changing Code and Contributing
This Developer Guide is for software developers who want to modify the flight stack and middleware (e.g. to add new flight modes), hardware integrators who want to support new flight controller boards and peripherals, and anyone who wants to get PX4 working on a new (unsupported) airframe/vehicle.
Developers should read the Guide for Contributions. See the forum and chat if you need help!
Weekly Dev Call
The PX4 Dev Team syncs up on a weekly dev call.
Note
The dev call is open to all interested developers (not just the core dev team). This is a great opportunity to meet the team and contribute to the ongoing development of the platform. It includes a QA session for newcomers. All regular calls are listed in the Dronecode calendar.
Maintenance Team
See the latest list of maintainers on MAINTAINERS file at the root of the project.
For the latest stats on contributors please see the latest stats for the Dronecode ecosystem in our project dashboard under LFX Insights. For information on how to update your profile and affiliations please see the following support link on how to Complete Your LFX Profile. Dronecode publishes a yearly snapshot of contributions and achievements on its website under the Reports section.
Supported Hardware
For the most up to date information, please visit PX4 User Guide > Autopilot Hardware.
Project Governance
The PX4 Autopilot project including all of its trademarks is hosted under Dronecode, part of the Linux Foundation.
