This topic provides a basic introduction to drones and using PX4 (it is meant mostly for novice users but is also a good introduction for experienced users).
If you are already familiar with the basic concepts, you can move on to Basic Assembly to learn how to wire your specific autopilot hardware. To load firmware and set up the vehicle with QGroundControl, see Basic Configuration.
A drone is an unmanned "robotic" vehicle that can be remotely or autonomously controlled.
Drones are used for many consumer, industrial, government and military applications. These include (non exhaustively): aerial photography/video, carrying cargo, racing, search and surveying etc.
Different types of drones exist for use in air, ground, sea, and underwater. These are (more formally) referred to as Unmanned Aerial Vehicles (UAV), Unmanned Aerial Systems (UAS), Unmanned Ground Vehicles (UGV), Unmanned Surface Vehicles (USV), Unmanned Underwater Vehicles (UUV).
The "brain" of the drone is called an autopilot. It consists of flight stack software running on vehicle controller ("flight controller") hardware.
PX4 is powerful open source autopilot flight stack.
Some of PX4's key features are:
- Controls many different vehicle frames/types, including: aircraft (multicopters, fixed wing aircraft and VTOLs), ground vehicles and underwater vehicles.
- Great choice of hardware for vehicle controller, sensors and other peripherals.
- Flexible and powerful flight modes and safety features.
PX4 is a core part of a broader drone platform that includes the QGroundControl ground station, Pixhawk hardware, and MAVSDK for integration with companion computers, cameras and other hardware using the MAVLink protocol. PX4 is supported by the Dronecode Project.
The Dronecode ground control station is called QGroundControl. You can use QGroundControl to load (flash) PX4 onto the vehicle control hardware, you can setup the vehicle, change different parameters, get real-time flight information and create and execute fully autonomous missions.
QGroundControl runs on Windows, Android, MacOS or Linux. Download and install it from here.
PX4 was initially designed to run on Pixhawk Series controllers, but can now run on Linux computers and other hardware. You should select a board that suits the physical constraints of your vehicle, the activities you wish to perform, and of course cost.
For more information see: Flight Controller Selection.
PX4 uses sensors to determine vehicle state (needed for stabilization and to enable autonomous control). The system minimally requires a gyroscope, accelerometer, magnetometer (compass) and barometer. A GPS or other positioning system is needed to enable all automatic modes, and some assisted modes. Fixed wing and VTOL-vehicles should additionally include an airspeed sensor (very highly recommended).
For more information see:
PX4 uses outputs to control: motor speed (e.g. via ESC), flight surfaces like ailerons and flaps, camera triggers, parachutes, grippers, and many other types of payloads.
The outputs are divided into
AUX outputs, and individually numbered (i.e.
n is 1 to usually 6 or 8).
The specific purpose for each output is hard coded on a per-airframe basis. The output mapping for all airframes is given in the Airframe Reference.
A flight controller may only have
MAINoutputs (like the Pixhawk 4 Mini), or may have only 6 outputs on either
AUX. Ensure that you select a controller that has enough of the right types of ports/outputs for your airframe.
MAIN port is used for core flight controls while
AUX is used for non-critical actuators/payloads (though
AUX may be used for flight controls if there aren't enough
MAIN ports for the vehicle type- e.g. VTOL).
For example, in a Generic Quadcopter the
MAIN outputs 1-4 are used for corresponding motors, while the remaining
MAIN and some
AUX outputs are used for RC passthrough.
The actual ports/bus used for the outputs on the flight controller depends on the hardware and PX4 configuration.
Usually the ports are mapped to PWM outputs as shown above, which are commonly screen printed
MAIN OUT and
They might also be marked as
FMU PWM OUT or
IO PWM Out (or similar).
Pixhawk controllers have a "main" FMU board and may have a separate IO board.
If there is an IO board, the
AUX ports are connected directly to the FMU and the
MAIN ports are connected to the IO board.
MAIN ports are connected to the FMU, and there are no
The FMU output ports can use D-shot or One-shot protocols (as well as PWM), which provide much lower-latency behaviour.
This can be useful for racers and other airframes that require better performance.
The output ports may also be mapped to UAVCAN nodes (e.g. UAVCAN motor controllers). The (same) airframe mapping of outputs to nodes is used in this case.
- There are only 6-8 outputs in
AUXbecause most flight controllers only have this many PWM/Dshot/Oneshot outputs. In theory there can be many more outputs if the bus supports it (i.e. a UAVCAN bus is not limited to this few nodes).
Many PX4 drones use brushless motors that are driven by the flight controller via an Electronic Speed Controller (ESC) (the ESC converts a signal from the flight controller to an appropriate level of power delivered to the motor).
For information about what ESC/Motors are supported by PX4 see:
PX4 drones are mostly commonly powered from Lithium-Polymer (LiPo) batteries. The battery is typically connected to the system using a Power Module or Power Management Board, which provide separate power for the flight controller and to the ESCs (for the motors).
A Radio Control (RC) system is used to manually control the vehicle. It consists of a remote control unit that uses a transmitter to communicate stick/control positions with a receiver based on the vehicle. Some RC systems can additionally receive telemetry information back from the autopilot.
PX4 does not require a remote control system for autonomous flight modes.
RC System Selection explains how to choose an RC system. Other related topics include:
- Radio/Remote Control Setup - Remote control configuration in QGroundControl.
- Flying 101 - Learn how to fly with a remote control.
- FrSky Telemetry - Set up the RC transmitter to receive telemetry/status updates from PX4.
A computer joystick connected through QGroundControl can also be used to manually control PX4 (QGC converts joystick movements into MAVLink messages that are sent over the telemetry link). This approach is used by ground control units that have an integrated ground control station, like the UAVComponents MicroNav shown below. Joysticks are also commonly used to fly the vehicle in simulation.
It is common for vehicles to have a safety switch that must be engaged before the vehicle can be armed (when armed, motors are powered and propellers can turn). Commonly the safety switch is integrated into a GPS unit, but it may also be a separate physical component.
A vehicle that is armed is potentially dangerous. The safety switch is an additional mechanism that prevents arming from happening by accident.
Data/Telemetry Radios can provide a wireless MAVLink connection between a ground control station like QGroundControl and a vehicle running PX4. This makes it possible to tune parameters while a vehicle is in flight, inspect telemetry in real-time, change a mission on the fly, etc.
PX4 can be controlled from a separate on-vehicle companion computer via a serial cable or wifi. The companion computer will usually communicate using a MAVLink API like the MAVSDK or MAVROS.
Using a Robotics API requires software development skills, and is outside the scope of this guide.
- Off-board Mode - Flight mode for offboard control of PX4 from a GCS or companion computer.
- Robotics APIs (PX4 Developer Guide)
By default, if no SD card is present PX4 will play the format failed (2-beep) tune twice during boot (and none of the above features will be available).
The maximum supported SD card size on Pixhawk boards is 32GB. The SanDisk Extreme U3 32GB is highly recommended (Developer Guide).
SD cards are never-the-less optional. Flight controllers that do not include an SD Card slot may:
- Disable notification beeps are disabled using the parameter CBRK_BUZZER.
- Stream logs to another component (companion).
- Store missions in RAM/FLASH.
Vehicles may have moving parts, some of which are potentially dangerous when powered (in particular motors and propellers)!
To reduce the chance of accidents:
- PX4 vehicles are disarmed (unpowered) when not in use, and must be explicitly armed before taking off.
- Some vehicles additionally require a safety switch be disengaged before arming can succeed.
- Arming is prevented if the vehicle is not in a "healthy" state.
- A vehicle will also usually revert to the disarmed state after landing or if a pilot does not take off quickly enough.
Arming is triggered by default (Mode 2 transmitters) by holding the RC throttle/yaw stick on the bottom right for one second (to disarm, hold stick on bottom left). It is also possible to configure PX4 to arm using an RC button on the RC control (and arming commands can be sent from a ground station).
A detailed overview of arming and disarming configuration can be found here: Prearm, Arm, Disarm Configuration.
Flight modes provide different types/levels of vehicle automation and autopilot assistance to the user (pilot). Autonomous modes are fully controlled by the autopilot, and require no pilot/remote control input. These are used, for example, to automate common tasks like takeoff, returning to the home position, and landing. Other autonomous modes execute pre-programmed missions, follow a GPS beacon, or accept commands from an offboard computer or ground station.
Manual modes are controlled by the user (via the RC control sticks/joystick) with assistance from the autopilot. Different manual modes enable different flight characteristics - for example, some modes enable acrobatic tricks, while others are impossible to flip and will hold position/course against wind.
Not all flight modes are available on all vehicle types, and some modes can only be used when specific conditions have been met (e.g. many modes require a global position estimate).
PX4 has configurable failsafe systems to protect and recover your vehicle if something goes wrong! These allow you to specify areas and conditions under which you can safely fly, and the action that will be performed if a failsafe is triggered (for example, landing, holding position, or returning to a specified point).
You can only specify the action for the first failsafe event. Once a failsafe occurs the system will enter special handling code, such that subsequent failsafe triggers are managed by separate system level and vehicle specific code.
The main failsafe areas are listed below:
- Low Battery
- Remote Control (RC) Loss
- Position Loss (global position estimate quality is too low).
- Offboard Loss (e.g. lose connection to companion computer)
- Data Link Loss (e.g. lose telemetry connection to GCS).
- Geofence Breach (restrict vehicle to flight within a virtual cylinder).
- Mission Failsafe (prevent a previous mission being run at a new takeoff location).
- Traffic avoidance (triggered by transponder data from e.g. ADSB transponders).
For more information see: Safety (Basic Configuration).
All the vehicles, boats and aircraft have a heading direction or an orientation based on their forward motion.
It is important to know the vehicle heading direction in order to align the autopilot with the vehicle vector of movement. Multicopters have a heading even when they are symmetrical from all sides! Usually manufacturers use a colored props or colored arms to indicate the heading.
In our illustrations we will use red coloring for the front propellers of multicopter to show heading.
You can read in depth about heading in Flight Controller Orientation