mirror of
https://gitee.com/mirrors_PX4/PX4-Autopilot.git
synced 2026-04-14 10:07:39 +08:00
3fd7e3f89c
If the second bit of COM_ARM_MIS_EXT_REQ is set the vehicle will only arm after receive an authorization. The authorization flow: vehicle/external -> command: arm authorization request -> arm authorizer vehicle <- command ack with result in progress <- arm authorizer vehicle <- any data request <- arm authorizer vehicle -> data response -> arm authorizer vehicle <- command ack authorizing or denying <- arm authorizer Right now there is 2 ways to start the arm authorization request, that can be configured by COM_ARM_AUTH parameter. - One arm: When pilot request the vehicle to arm, it will request authorization blocking the arm process up to the timeout defined in COM_ARM_AUTH parameter. - Two arms request: The first arm request will request the authorization and will deny the first arm request, if authorizer approved the request, pilot can arm again within the authorized time and arm without any block. The arm authorizer can be running anywhere(compute board or PX4 itself) and it is responsible to request the mission list or any other information to vehicle before send a final response, it should send to vehicle a COMMAND_ACK with result = MAV_RESULT_IN_PROGRESS as soon as it receive the arm authorization request and the final result as after it got all the data that it needs authorize or deny the request.
PX4 Pro Drone Autopilot
This repository holds the PX4 Pro 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.
- Official Website: http://px4.io (License: BSD 3-clause, LICENSE.md)
- Supported airframes:
- Multicopters
- Fixed wing
- VTOL
- many more experimental types (Rovers, Blimps, Boats, Submarines, etc)
- Releases: Downloads
Please refer to the user documentation and user forum for flying drones with the PX4 flight stack.
Weekly Dev Call
The PX4 Dev Team syncs up on a weekly dev call.
- Wednesday 17:00 Central European Time, 11:00 Eastern Time, 08:00 Pacific Standard Time
- Uber conference (dial-in or web client)
- The agenda is announced in advance on the PX4 Discuss
- Issues and PRs may be labelled devcall to flag them for discussion
Developers
Maintenance Team
- Project / Founder - Lorenz Meier
- Communication Architecture
- UI / UX
- Multicopter Flight Control
- VTOL Flight Control
- Fixed Wing Flight Control
- Racers - Matthias Grob
- OS / drivers - David Sidrane
- UAVCAN / Industrial - Pavel Kirienko
- State Estimation - James Goppert, Paul Riseborough
- Vision based navigation
- Obstacle Avoidance - Vilhjalmur Vilhjalmsson
- Snapdragon
- Intel Aero
- Raspberry Pi / Navio - Beat Kueng
- Parrot Bebop - Michael Schaeuble
- Airmind MindPX / MindRacer - Henry Zhang
- RTPS/ROS2 Interface - Vicente Monge
Supported Hardware
This repository contains code supporting these boards:
- Snapdragon Flight
- Intel Aero
- Raspberry PI with Navio 2
- Parrot Bebop 2
- FMUv1.x
- FMUv2.x
- FMUv3.x Pixhawk 2
- FMUv4.x
- Pixracer
- Pixhawk 3 Pro
- FMUv5.x (ARM Cortex M7, future Pixhawk)
- STM32F4Discovery (basic support) Tutorial
- Gumstix AeroCore (v1 and v2)
- Airmind MindPX V2.8
- Airmind MindRacer V1.2
- Bitcraze Crazyflie 2.0
Project Milestones
The PX4 software and Pixhawk hardware (which has been designed for it) has been created in 2011 by Lorenz Meier.