Simulators allow PX4 flight code to control a computer modeled vehicle in a simulated "world". You can interact with this vehicle just as you might with a real vehicle, using QGroundControl, an offboard API, or a radio controller/gamepad.
Simulation is a quick, easy, and most importantly, safe way to test changes to PX4 code before attempting to fly in the real world. It is also a good way to start flying with PX4 when you haven't yet got a vehicle to experiment with.
PX4 supports both Software In the Loop (SITL) simulation, where the flight stack runs on computer (either the same computer or another computer on the same network) and Hardware In the Loop (HITL) simulation using a simulation firmware on a real flight controller board.
Information about available simulators and how to set them up are provided in the next section. The other sections provide general information about how the simulator works, and are not required to use the simulators.
The following simulators work with PX4 for HITL and/or SITL simulation.
This simulator is highly recommended.
A powerful 3D simulation environment that is particularly suitable for testing object-avoidance and computer vision. It can also be used for multi-vehicle simulation and is commonly used with ROS, a collection of tools for automating vehicle control.
|jMAVSim||A simple multirotor simulator that allows you to fly copter type vehicles around a simulated world.
It is easy to set up and can be used to test that your vehicle can take off, fly, land, and responds appropriately to various fail conditions (e.g. GPS failure). It can also be used for multi-vehicle simulation.
Supported Vehicles: Quad
|AirSim||A cross platform simulator that provides physically and visually realistic simulations. This simulator is resource intensive, and requires a very significantly more powerful computer than the other simulators described here.
Supported Vehicles: Iris (MultiRotor model and a configuration for PX4 QuadRotor in the X configuration).
|XPlane (HITL only)||A comprehensive and powerful fixed-wing flight simulator that offers very realistic flight models.
Supported Vehicles: Plane
Instructions for how to setup and use the simulators are in the topics linked above.
The remainder of this topic is a "somewhat generic" description of how the simulation infrastructure works. It is not required to use the simulators.
All simulators communicate with PX4 using the Simulator MAVLink API. This API defines a set of MAVLink messages that supply sensor data from the simulated world to PX4 and return motor and actuator values from the flight code that will be applied to the simulated vehicle. The image below shows the message flow.
A SITL build of PX4 uses simulator_mavlink.cpp to handle these messages while a hardware build in HIL mode uses mavlink_receiver.cpp. Sensor data from the simulator is written to PX4 uORB topics. All motors / actuators are blocked, but internal software is fully operational.
The messages are described below (see links for specific detail).
|MAV_MODE:MAV_MODE_FLAG_HIL_ENABLED||NA||Mode flag when using simulation. All motors/actuators are blocked, but internal software is fully operational.|
|HIL_ACTUATOR_CONTROLS||PX4 to Sim||PX4 control outputs (to motors, actuators).|
|HIL_SENSOR||Sim to PX4||Simulated IMU readings in SI units in NED body frame.|
|HIL_GPS||Sim to PX4||The simulated GPS RAW sensor value.|
|HIL_OPTICAL_FLOW||Sim to PX4||Simulated optical flow from a flow sensor (e.g. PX4FLOW or optical mouse sensor)|
|HIL_STATE_QUATERNION||Sim to PX4||Contains the actual "simulated" vehicle position, attitude, speed etc. This can be logged and compared to PX4's estimates for analysis and debugging (for example, checking how well an estimator works for noisy (simulated) sensor inputs).|
|HIL_RC_INPUTS_RAW||Sim to PX4||The RAW values of the RC channels received.|
By default, PX4 uses commonly established UDP ports for MAVLink communication with ground control stations (e.g. QGroundControl), Offboard APIs (e.g. Dronecode SDK, MAVROS) and simulator APIs (e.g. Gazebo). These ports are:
- UDP Port 14540 is used for communication with offboard APIs. Offboard APIs are expected to listen for connections on this port.
- UDP Port 14550 is used for communication with ground control stations. GCS are expected to listen for connections on this port. QGroundControl listens to this port by default.
- TCP Port 4560 is used for communication with simulators. PX4 listens to this port, and simulators are expected to initiate the communication by broadcasting data to this port.
The ports for the GCS and offboard APIs are set in configuration files, while the simulator broadcast port is hard-coded in the simulation MAVLink module.
The diagram below shows a typical SITL simulation environment for any of the supported simulators. The different parts of the system connect via UDP, and can be run on either the same computer or another computer on the same network.
- PX4 uses a simulation-specific module to listen on TCP port 4560. Simulators connect to this port, then exchange information using the Simulator MAVLink API described above. PX4 on SITL and the simulator can run on either the same computer or different computers on the same network.
- PX4 uses the normal MAVLink module to connect to GroundStations (which listen on port 14550) and external developer APIs like Dronecode SDK or ROS (which listen on port 14540).
- A serial connection is used to connect Joystick/Gamepad hardware via QGroundControl.
If you use the normal build system SITL
make configuration targets (see next section) then both SITL and the Simulator will be launched on the same computer and the ports above will automatically be configured. You can configure additional MAVLink UDP connections and otherwise modify the simulation environment in the build configuration and initialisation files.
The build system makes it very easy to build and start PX4 on SITL, launch a simulator, and connect them. The syntax (simplified) looks like this:
make px4_sitl simulator[_vehicle-model]
jmavsim or some other simulator, and vehicle-model is a particular vehicle type supported by that simulator (jMAVSim only supports multicopters, while Gazebo supports many different types).
A number of examples are shown below, and there are many more in the individual pages for each of the simulators:
# Start Gazebo with plane make px4_sitl gazebo_plane # Start Gazebo with iris and optical flow make px4_sitl gazebo_iris_opt_flow # Start JMavSim with iris (default vehicle model) make px4_sitl jmavsim
The simulation can be further configured via environment variables:
PX4_ESTIMATOR: This variable configures which estimator to use. Possible options are:
inav. It can be set via
export PX4_ESTIMATOR=lpebefore running the simulation.
The syntax described here is simplified, and there are many other options that you can configure via make - for example, to set that you wish to connect to an IDE or debugger. For more information see: Building the Code > PX4 Make Build Targets.
SITL can be run faster or slower than realtime when using jMAVSim or Gazebo.
The speed factor is set using the environment variable
For example, to run the jMAVSim simulation at 2 times the real time speed:
PX4_SIM_SPEED_FACTOR=2 make px4_sitl jmavsim
To run at half real-time:
PX4_SIM_SPEED_FACTOR=0.5 make px4_sitl jmavsim
You can apply the factor to all SITL runs in the current session using
export PX4_SIM_SPEED_FACTOR=2 make px4_sitl jmavsim
At some point IO or CPU will limit the speed that is possible on your machine and it will be slowed down "automatically". Powerful desktop machines can usually run the simulation at around 6-10x, for notebooks the achieved rates can be around 3-4x.
To avoid PX4 detecting data link timeouts, increase the value of param COM_DL_LOSS_T proportional to the simulation rate. For example, if
COM_DL_LOSS_Tis 10 in realtime, at 10x simulation rate increase to 100.
Scripts are used to control which parameter settings to use or which modules to start.
They are located in the ROMFS/px4fmu_common/init.d-posix directory, the
rcS file is the main entry point. See System Startup for more information.
With Hardware-in-the-Loop (HITL) simulation the normal PX4 firmware is run on real hardware. The HITL Simulation Environment in documented in: HITL Simulation.
QGroundControl desktop versions can connect to a USB Joystick/Gamepad and send its movement commands and button presses to PX4 over MAVLink. This works on both SITL and HITL simulations, and allows you to directly control the simulated vehicle. If you don't have a joystick you can alternatively control the vehicle using QGroundControl's onscreen virtual thumbsticks.
For setup information see the QGroundControl User Guide:
The simulated camera is a gazebo plugin that implements the MAVLink Camera Protocol. PX4 connects/integrates with this camera in exactly the same way as it would with any other MAVLink camera:
- TRIG_INTERFACE must be set to
3to configure the camera trigger driver for use with a MAVLink camera
- PX4 must forward all camera commands between the GCS and the (simulator) MAVLink Camera. You can do this by starting mavlink with the
-fflag as shown, specifying the UDP ports for the new connection.
mavlink start -u 14558 -o 14530 -r 4000 -f -m camera
More than just the camera MAVLink messages will be forwarded, but the camera will ignore those that it doesn't consider relevant.
The same approach can be used by other simulators to implement camera support.
It is possible to run the simulator on one computer, and access it from another computer on the same network (or on another network with appropriate routing). This might be useful, for example, if you want to test a drone application running on real companion computer hardware running against a simulated vehicle.
This does not work "out of the box" because PX4 does not route packets to external interfaces by default (in order to avoid spamming the network and different simulations interfering with each other). Instead it routes traffic internally - to "localhost".
There are a number of ways to make the UDP packets available on external interfaces, as outlined below.
Enable MAV_BROADCAST to broadcast heartbeats on the local network.
A remote computer can then connect to the simulator by listening to the appropriate port (i.e. 14550 for QGroundControl).
The mavlink-router can be used to route packets from localhost to an external interface.
The mavlink module routes to localhost by default, but you can specify an external IP address to broadcast to using its
This should be done in various configuration files where
mavlink start is called. For example: /ROMFS/px4fmu_common/init.d-posix/rcS.
SSH tunneling is a flexible option because the simulation computer and the system using it need not be on the same network.
You might similarly use VPN to provide a tunnel to an external interface (on the same network or another network).
One way to create the tunnel is to use SSH tunneling options.
The tunnel itself can be created by running the following command on localhost, where
remote.local is the name of a remote computer:
ssh -C -fR 14551:localhost:14551 remote.local
The UDP packets need to be translated to TCP packets so they can be routed over SSH. The netcat utility can be used on both sides of the tunnel - first to convert packets from UDP to TCP, and then back to UDP at the other end.
QGC must be running before executing netcat.
On the QGroundControl computer, UDP packet translation may be implemented by running following commands:
mkfifo /tmp/tcp2udp netcat -lvp 14551 < /tmp/tcp2udp | netcat -u localhost 14550 > /tmp/tcp2udp
On the simulator side of the SSH tunnel, the command is:
mkfifo /tmp/udp2tcp netcat -lvup 14550 < /tmp/udp2tcp | netcat localhost 14551 > /tmp/udp2tcp
The port number
14550 is valid for connecting to QGroundControl or another GCS, but should be adjusted for other endpoints (e.g. developer APIs etc.).
The tunnel may in theory run indefinitely, but netcat connections may need to be restarted if there is a problem.
The QGC_remote_connect.bash script can be run on the QGC computer to automatically setup/run the above instructions. The simulation must already be running on the remote server, and you must be able to SSH into that server.