FlightGear is a flight simulator with powerful FDM engines. This allows FlightGear to simulate rotorcrafts under various meteorological conditions (which is why the bridge was originally developed by ThunderFly s.r.o.).
This page describes FlightGear's single-vehicle use in SITL. For information about multi-vehicle use see: Multi-Vehicle Simulation with FlightGear.
Supported Vehicles: Autogyro, Plane, Rover.
See Simulation for general information about simulators, the simulation environment, and simulation configuration (e.g. supported vehicles).
These instructions were tested on Ubuntu 18.04
- Install the usual Development Environment on Ubuntu LTS / Debian Linux.
sudo add-apt-repository ppa:saiarcot895/flightgear sudo apt update sudo apt install flightgear
This installs the latest stable FlightGear version from the PAA repository along with the the FGdata package.
For some models (e.g. those with electric engines) the daily build with the newest features may be necessary. Install this using the daily build PPA.
Check that you are able to run FlightGear:
- Set write permissions to the Protocols folder in the FlightGear installation directory:
Setting the permissions is required because the PX4-FlightGear-Bridge puts the communication definition file here.
sudo chmod a+w /usr/share/games/flightgear/Protocols
Additional installation instructions can be found on FlightGear wiki.
Run a simulation by starting PX4 SITL, specifying the airframe configuration of your choice.
The easiest way to do this is to open a terminal in the root directory of the PX4 Firmware repository and call
make for the desired target. For example, to start a plane simulation :
cd /path/to/Firmware make px4_sitl_nolockstep flightgear_rascal
The supported vehicles and
make commands are listed below (click on the links to see the vehicle images).
|Ackerman vehicle (UGV/Rover)||
The commands above launch a single vehicle with the full UI. QGroundControl should be able to automatically connect to the simulated vehicle.
For the full list of FlightGear build targets (highlighted) run:
make px4_sitl_nolockstep list_vmd_make_targets | grep flightgear_
For additional information see: FlightGear Vehicles (this includes information about "unsupported" vehicles, and adding new vehicles).
The Installing Files and Code guide is a useful reference if there are build errors.
make commands mentioned above first build PX4 and then run it along with the FlightGear simulator.
Once the PX4 has started it will launch the PX4 shell as shown below. You must select enter to get the command prompt.
______ __ __ ___ | ___ \ \ \ / / / | | |_/ / \ V / / /| | | __/ / \ / /_| | | | / /^\ \ \___ | \_| \/ \/ |_/ px4 starting. INFO [px4] Calling startup script: /bin/sh etc/init.d-posix/rcS 0 INFO [param] selected parameter default file eeprom/parameters_1034 I'm Mavlink to FlightGear Bridge Targed Bridge Freq: 200, send data every step: 1 4 5 -1 7 -1 2 1 4 1 [param] Loaded: eeprom/parameters_1034 INFO [dataman] Unknown restart, data manager file './dataman' size is 11798680 bytes INFO [simulator] Waiting for simulator to accept connection on TCP port 4560 INFO [simulator] Simulator connected on TCP port 4560. INFO [commander] LED: open /dev/led0 failed (22) INFO [commander] Mission #3 loaded, 9 WPs, curr: 8 INFO [init] Mixer: etc/mixers-sitl/plane_sitl.main.mix on /dev/pwm_output0 INFO [mavlink] mode: Normal, data rate: 4000000 B/s on udp port 18570 remote port 14550 INFO [airspeed_selector] No airspeed sensor detected. Switch to non-airspeed mode. INFO [mavlink] mode: Onboard, data rate: 4000000 B/s on udp port 14580 remote port 14540 INFO [mavlink] mode: Onboard, data rate: 4000 B/s on udp port 14280 remote port 14030 INFO [logger] logger started (mode=all) INFO [logger] Start file log (type: full) INFO [logger] Opened full log file: ./log/2020-04-28/22_03_36.ulg INFO [mavlink] MAVLink only on localhost (set param MAV_BROADCAST = 1 to enable network) INFO [px4] Startup script returned successfully pxh> StatsHandler::StatsHandler() Setting up GL2 compatible shaders Now checking for plug-in osgPlugins-3.4.1/osgdb_nvtt.so PX4 Communicator: PX4 Connected. pxh>
The console will print out status as PX4 loads the airframe-specific initialization and parameter files, wait for (and connect to) the simulator. Once there is an INFO print that [ecl/EKF] is
commencing GPS fusion the vehicle is ready to arm. At this point, you should see a FlightGear window with some view of aircraft.
You can change the view by pressing Ctrl+V.
You can bring it into the air by typing:
pxh> commander takeoff
You can tune your FG installation/settings by the following environment variables:
FG\_BINARY- absolute path to FG binary to run. (It can be an AppImage)
FG\_MODELS\_DIR- absolute path to the folder containing the manually-downloaded aircraft models which should be used for simulation.
FG\_ARGS\_EX- any additional FG parameters.
In FlightGear you can display the frame rate by enabling it in: View > View Options > Show frame rate.
Takeoff location in SITL FlightGear can be set using additional variables. Setting the variable will override the default takeoff location.
The variables which can be set are as follows:
--offset-distance. Other options can be found on FlightGear wiki
FG_ARGS_EX="--airport=PHNL" make px4_sitl_nolockstep flightgear_rascal
The example above starts the simulation on the Honolulu international airport
Joystick and thumb-joystick are supported through QGroundControl (setup instructions here).
The joystick input in FlightGear should be disabled in otherwise there will be a "race condition" between the FG joystick input and PX4 commands.
To extend or customize the simulation interface, edit the files in the *Tools/flightgear_bridge folder. The code is available in the PX4-FlightGear-Bridge repository on Github.