FlightGear wiki - User contributions [en]

User:Kwikius/Using FlightGear for software in the loop simulation

2021-07-05T09:52:37Z

Kwikius: /* Using FlightGear for software in the loop simulation */

== Using FlightGear for software in the loop simulation ==
=== Introduction ===
FlightGear is popular as both a viewer and a flight dynamics engine (FDE) for software in the loop (SITL) simulation. This article describes a project that uses FlightGear to provide a viewer and an FDE for simulating flying an RC aeroplane autonomously using a flight controller (FC). <ref>
The source code for the examples is available on github at https://github.com/kwikius/fg_ext_fdm.
The source code is written in reasonably modern C++ and makes use of a C++ library for representing physical quantities called quan, also available on github at https://github.com/kwikius/quan-trunk.</ref>

<youtube>KcoqxdLbXuo</youtube>

=== The main requirements for a SITL simulation ===

==== Interfacing to FlightGear ====
There are many options to choose from {{ main article|Interfacing FlightGear}}

===== Sending data to the FDE =====
I chose to use [[Telnet_usage|telnet interface]]. There is a [https://sourceforge.net/p/flightgear/flightgear/ci/next/tree/scripts/example/fgfsclient.cxx C++ example in the FlightGear source code] , that shows basic useage. Telnet is relatively slow since it sends data as text, but you need to send a surprisingly small amount of information to control the aircraft. Usually you are merely sending information to modify pitch, roll and yaw. Less frequently you are changing throttle ,flaps and so on. By caching data in your app and only sending information if it actually changed, the overhead is quite low. When bandwidth becomes an issue, then there are other protocols available.

===== Receiving data from the FDE =====
I chose to use [[Property Tree/Sockets|socket interface]]. Again there is a [https://sourceforge.net/p/flightgear/flightgear/ci/next/tree/examples/netfdm C++example in the FlightGear source code]. Note that the example sends data to FlightGear, but the socket can also be used to read the [https://sourceforge.net/p/flightgear/flightgear/ci/next/tree/src/Network/net_fdm.hxx FGNetFDM] structure from FlightGear via a socket, which is what I chose to do. The FGNetFDM structure contains most, if not all the information that is need at a fast rate. Socket UDP interface sends the FGNetFDM structure as a binary chunk, so is fast.<ref>Lurking in FlightGear, there is a pipe interface which would promise to be very fast, but there is not much information about it. [https://sourceforge.net/p/flightgear/flightgear/ci/next/tree/src/FDM/ExternalPipe/ ExternalPipe] [https://sourceforge.net/p/flightgear/mailman/message/34559783/] </ref> Other data can be read back using the telnet interface.

===== Frame rate =====
Ideally we would like to receive the FDE data from FlightGear at arbitrarily high rates, but unfortunately this is one area where FlightGear isnt great. I can only get an update rate of 10 Hz. In practise this limitation can be worked with by simulating aircraft where things happen more slowly.<ref>The video above uses an update rate of 10Hz. The EasyStar has modified parameters.</ref> The only alternative is to use an external FDE and just use FlightGear as a viewer. <ref>This is the approach taken by Ardupilot, by using JSBSim directly.</ref>

=== Visualising the simulation ===
*The ability to view the simulation graphically. Though not entirely necessary, in practise this is most useful, since visualisation can show up issues that are hidden in data, therfore the examples use 3D graphical simulation where possible using FlightGear as the viewer in most cases.

==Footnotes==

<references />
L

User:Kwikius/Using FlightGear for software in the loop simulation

2021-07-05T09:49:51Z

Kwikius: Add framerate info

== Using FlightGear for software in the loop simulation ==
=== Introduction ===
FlightGear is popular as both a viewer and a flight dynamics engine (FDE) for software in the loop (SITL) simulation. This article describes a project that uses FlightGear to provide a viewer and an FDE for simulating flying an RC aeroplane autonomously using a flight controller (FC). <ref>
The source code for the examples is available on github at https://github.com/kwikius/fg_ext_fdm.
The source code is written in reasonably modern C++ and makes use of a C++ library for representing physical quantities called quan, also available on github at https://github.com/kwikius/quan-trunk.</ref>

<youtube>KcoqxdLbXuo</youtube>

=== The main requirements for a SITL simulation ===

==== Interfacing to FlightGear ====
There are many options to choose from {{ main article|Interfacing FlightGear}}

===== Sending data to the FDE =====
I chose to use [[Telnet_usage|telnet interface]]. There is a [https://sourceforge.net/p/flightgear/flightgear/ci/next/tree/scripts/example/fgfsclient.cxx C++ example in the FlightGear source code] , that shows basic useage. Telnet is relatively slow since it sends data as text, but you need to send a surprisingly small amount of information to control the aircraft. Usually you are merely sending information to modify pitch, roll and yaw. Less frequently you are changing throttle ,flaps and so on. By caching data in your app and only sending information if it actually changed, the overhead is quite low. When bandwidth becomes an issue, then there are other protocols available.

===== Receiving data from the FDE =====
I chose to use [[Property Tree/Sockets|socket interface]]. Again there is a [https://sourceforge.net/p/flightgear/flightgear/ci/next/tree/examples/netfdm C++example in the FlightGear source code]. Note that the example sends data to FlightGear, but the socket can also be used to read the [https://sourceforge.net/p/flightgear/flightgear/ci/next/tree/src/Network/net_fdm.hxx FGNetFDM] structure from FlightGear via a socket, which is what I chose to do. The FGNetFDM structure contains most, if not all the information that is need at a fast rate. Socket UDP interface sends the FGNetFDM structure as a binary chunk, so is fast.<ref>Lurking in FlightGear, there is a pipe interface which would promise to be very fast, but there is not much information about it. [https://sourceforge.net/p/flightgear/flightgear/ci/next/tree/src/FDM/ExternalPipe/ ExternalPipe] [https://sourceforge.net/p/flightgear/mailman/message/34559783/] </ref> Other data can be read back using the telnet interface.

=== Frame rate ===
Ideally we would like to receive the FDE data from FlightGear at arbitrarily high rates, but unfortunately this is one area where FlightGear isnt great. I can only get an update rate of 10 Hz. In practise this limitation can be worked with by simulating aircraft where things happen more slowly.<ref>The video above uses an update rate of 10Hz. The EasyStar has modified parameters.</ref> The only alternative is to use an external FDE and just use FlightGear as a viewer. <ref>This is the approach taken by Ardupilot, by using JSBSim directly.</ref>

=== Visualising the simulation ===
*The ability to view the simulation graphically. Though not entirely necessary, in practise this is most useful, since visualisation can show up issues that are hidden in data, therfore the examples use 3D graphical simulation where possible using FlightGear as the viewer in most cases.

==Footnotes==

<references />
L

User:Kwikius/Using FlightGear for software in the loop simulation

2021-07-05T09:09:52Z

Kwikius: /* Introduction */

== Using FlightGear for software in the loop simulation ==
=== Introduction ===
FlightGear is popular as both a viewer and a flight dynamics engine (FDE) for software in the loop (SITL) simulation. This article describes a project that uses FlightGear to provide a viewer and an FDE for simulating flying an RC aeroplane autonomously using a flight controller (FC). <ref>
The source code for the examples is available on github at https://github.com/kwikius/fg_ext_fdm.
The source code is written in reasonably modern C++ and makes use of a C++ library for representing physical quantities called quan, also available on github at https://github.com/kwikius/quan-trunk.</ref>

<youtube>KcoqxdLbXuo</youtube>

=== The main requirements for a SITL simulation ===

==== Interfacing to FlightGear ====
There are many options to choose from {{ main article|Interfacing FlightGear}}

===== Sending data to the FDE =====
I chose to use [[Telnet_usage|telnet interface]]. There is a [https://sourceforge.net/p/flightgear/flightgear/ci/next/tree/scripts/example/fgfsclient.cxx C++ example in the FlightGear source code] , that shows basic useage. Telnet is relatively slow since it sends data as text, but you need to send a surprisingly small amount of information to control the aircraft. Usually you are merely sending information to modify pitch, roll and yaw. Less frequently you are changing throttle ,flaps and so on. By caching data in your app and only sending information if it actually changed, the overhead is quite low. When bandwidth becomes an issue, then there are other protocols available.

===== Receiving data from the FDE =====
I chose to use [[Property Tree/Sockets|socket interface]]. Again there is a [https://sourceforge.net/p/flightgear/flightgear/ci/next/tree/examples/netfdm C++example in the FlightGear source code]. Note that the example sends data to FlightGear, but the socket can also be used to read the [https://sourceforge.net/p/flightgear/flightgear/ci/next/tree/src/Network/net_fdm.hxx FGNetFDM] structure from FlightGear via a socket, which is what I chose to do. The FGNetFDM structure contains most, if not all the information that is need at a fast rate. Socket UDP interface sends the FGNetFDM structure as a binary chunk, so is fast.<ref>Lurking in FlightGear, there is a pipe interface which would promise to be very fast, but there is not much information about it. [https://sourceforge.net/p/flightgear/flightgear/ci/next/tree/src/FDM/ExternalPipe/ ExternalPipe] [https://sourceforge.net/p/flightgear/mailman/message/34559783/] </ref> Other data can be read back using the telnet interface.

=== Visualising the simulation ===
*The ability to view the simulation graphically. Though not entirely necessary, in practise this is most useful, since visualisation can show up issues that are hidden in data, therfore the examples use 3D graphical simulation where possible using FlightGear as the viewer in most cases.

==Footnotes==

<references />
L

File:Slope soaring at Rhossilli.jpg

2021-06-18T17:23:11Z

Kwikius: Uploaded own work with UploadWizard

=={{int:filedesc}}==
{{Information
|description={{en|1=Slope soaring with EasyStar RC glider at Rhossilli U.K.}}
|date=2021-06-18
|source={{own}}
|author=[[User:Kwikius|Kwikius]]
|permission=
|other versions=
}}

=={{int:license-header}}==
{{self|cc-by-sa-4.0}}

User:Kwikius/Using FlightGear for software in the loop simulation

2021-06-16T11:18:43Z

Kwikius: /* Receiving data from the FDE */

== Using FlightGear for software in the loop simulation ==
=== Introduction ===
FlightGear is popular as both a viewer and a flight dynamics engine (FDE) for software in the loop (SITL) simulation. This article describes a project that uses FlightGear to provide a viewer and an FDE for simulating flying an RC aeroplane autonomously using a flight controller (FC). <ref>
The source code for the examples is available on github at https://github.com/kwikius/fg_ext_fdm.
The source code is written in reasonably modern C++ and makes use of a C++ library for representing physical quantities called quan, also available on github at https://github.com/kwikius/quan-trunk.</ref>

<youtube>27LC2WRK0Rk</youtube>

=== The main requirements for a SITL simulation ===

==== Interfacing to FlightGear ====
There are many options to choose from {{ main article|Interfacing FlightGear}}

===== Sending data to the FDE =====
I chose to use [[Telnet_usage|telnet interface]]. There is a [https://sourceforge.net/p/flightgear/flightgear/ci/next/tree/scripts/example/fgfsclient.cxx C++ example in the FlightGear source code] , that shows basic useage. Telnet is relatively slow since it sends data as text, but you need to send a surprisingly small amount of information to control the aircraft. Usually you are merely sending information to modify pitch, roll and yaw. Less frequently you are changing throttle ,flaps and so on. By caching data in your app and only sending information if it actually changed, the overhead is quite low. When bandwidth becomes an issue, then there are other protocols available.

===== Receiving data from the FDE =====
I chose to use [[Property Tree/Sockets|socket interface]]. Again there is a [https://sourceforge.net/p/flightgear/flightgear/ci/next/tree/examples/netfdm C++example in the FlightGear source code]. Note that the example sends data to FlightGear, but the socket can also be used to read the [https://sourceforge.net/p/flightgear/flightgear/ci/next/tree/src/Network/net_fdm.hxx FGNetFDM] structure from FlightGear via a socket, which is what I chose to do. The FGNetFDM structure contains most, if not all the information that is need at a fast rate. Socket UDP interface sends the FGNetFDM structure as a binary chunk, so is fast.<ref>Lurking in FlightGear, there is a pipe interface which would promise to be very fast, but there is not much information about it. [https://sourceforge.net/p/flightgear/flightgear/ci/next/tree/src/FDM/ExternalPipe/ ExternalPipe] [https://sourceforge.net/p/flightgear/mailman/message/34559783/] </ref> Other data can be read back using the telnet interface.

=== Visualising the simulation ===
*The ability to view the simulation graphically. Though not entirely necessary, in practise this is most useful, since visualisation can show up issues that are hidden in data, therfore the examples use 3D graphical simulation where possible using FlightGear as the viewer in most cases.

==Footnotes==

<references />
L

User:Kwikius/Using FlightGear for software in the loop simulation

2021-06-16T11:12:32Z

Kwikius:

== Using FlightGear for software in the loop simulation ==
=== Introduction ===
FlightGear is popular as both a viewer and a flight dynamics engine (FDE) for software in the loop (SITL) simulation. This article describes a project that uses FlightGear to provide a viewer and an FDE for simulating flying an RC aeroplane autonomously using a flight controller (FC). <ref>
The source code for the examples is available on github at https://github.com/kwikius/fg_ext_fdm.
The source code is written in reasonably modern C++ and makes use of a C++ library for representing physical quantities called quan, also available on github at https://github.com/kwikius/quan-trunk.</ref>

<youtube>27LC2WRK0Rk</youtube>

=== The main requirements for a SITL simulation ===

==== Interfacing to FlightGear ====
There are many options to choose from {{ main article|Interfacing FlightGear}}

===== Sending data to the FDE =====
I chose to use [[Telnet_usage|telnet interface]]. There is a [https://sourceforge.net/p/flightgear/flightgear/ci/next/tree/scripts/example/fgfsclient.cxx C++ example in the FlightGear source code] , that shows basic useage. Telnet is relatively slow since it sends data as text, but you need to send a surprisingly small amount of information to control the aircraft. Usually you are merely sending information to modify pitch, roll and yaw. Less frequently you are changing throttle ,flaps and so on. By caching data in your app and only sending information if it actually changed, the overhead is quite low. When bandwidth becomes an issue, then there are other protocols available.

===== Receiving data from the FDE =====
I chose to use [[Property Tree/Sockets|socket interface]]. Again there is a [https://sourceforge.net/p/flightgear/flightgear/ci/next/tree/examples/netfdm C++example in the FlightGear source code]. Note that the example sends data to FlightGear, but the socket can also be used to read the [https://sourceforge.net/p/flightgear/flightgear/ci/next/tree/src/Network/net_fdm.hxx FGNetFDM] structure from FlightGear via a socket, which is what I chose to do. The FGNetFDM structure contains most, if not all the information that is need at a fast rate. Socket UDP interface sends the FGNetFDM structure as a binary chunk, so is fast. Other data can be read back using the telnet interface. Somehwre lurking in FlighGear, there is a pipe inteface, but

=== Visualising the simulation ===
*The ability to view the simulation graphically. Though not entirely necessary, in practise this is most useful, since visualisation can show up issues that are hidden in data, therfore the examples use 3D graphical simulation where possible using FlightGear as the viewer in most cases.

==Footnotes==

<references />

User:Kwikius/Using FlightGear for software in the loop simulation

2021-06-16T10:27:40Z

Kwikius:

== Using FlightGear for software in the loop simulation ==
=== Introduction ===
FlightGear is popular as both a viewer and a flight dynamics engine (FDE) for software in the loop (SITL) simulation. This article describes a project that uses FlightGear to provide a viewer and an FDE for simulating flying an RC aeroplane autonomously using a flight controller (FC). <ref>
The source code for the examples is available on github at https://github.com/kwikius/fg_ext_fdm.
The source code is written in reasonably modern C++ and makes use of a C++ library for representing physical quantities called quan, also available on github at https://github.com/kwikius/quan-trunk.</ref>

<youtube>27LC2WRK0Rk</youtube>

=== The main requirements for a SITL simulation ===

==== Interfacing to FlightGear ====
There are many options to choose from {{ main article|Interfacing FlightGear}}

===== Sending data to the FDE =====
I chose to use [[Telnet_usage|telnet interface]]. There is a [https://sourceforge.net/p/flightgear/flightgear/ci/next/tree/scripts/example/fgfsclient.cxx C++ example in the FlightGear source code] , that shows basic useage. Telnet is relatively slow since it sends data as text, but you need to send a surprisingly small amount of information to control the aircraft. Usually you are merely sending information to modify pitch, roll and yaw. Less frequently you are changing throttle ,flaps and so on. By caching data in your app and only sending information, if it actually changed, the overhead is quite low. When bandwidth becomes an issue, then there are other protocols available.

===== Receiving data from the FDE =====
I chose to use [[Property Tree/Sockets|socket interface]]. Again there is a [https://sourceforge.net/p/flightgear/flightgear/ci/next/tree/examples/netfdm C++example in the FlightGear source code]. Note that the example sends data to FlightGear, but the socket can also be used to read the [https://sourceforge.net/p/flightgear/flightgear/ci/next/tree/src/Network/net_fdm.hxx FGNetFDM] structure from FlightGear via a socket, which is what I chose to do. The FGNetFDM structure contains most, if not all the information that is need at a fast rate. Socket UDP interface sends the FGNetFDM structure as a binary chunk, so is fast. Other data can be read back using the telnet interface. Somehwre lurking in FlighGear, there is a pipe inteface, but

=== Visualising the simulation ===
*The ability to view the simulation graphically. Though not entirely necessary, in practise this is most useful, since visualisation can show up issues that are hidden in data, therfore the examples use 3D graphical simulation where possible using FlightGear as the viewer in most cases.

==Footnotes==

<references />

User:Kwikius/Using FlightGear for software in the loop simulation

2021-06-16T10:21:26Z

Kwikius:

== Using FlightGear for software in the loop simulation ==
=== Introduction ===
FlightGear is popular as both a viewer and a flight dynamics engine (FDE) for software in the loop (SITL) simulation. This article describes a project that uses FlightGear to provide a viewer and an FDE for simulating flying an RC aeroplane autonomously using a flight controller (FC). <ref>
The source code for the examples is available on github at https://github.com/kwikius/fg_ext_fdm.
The source code is written in reasonably modern C++ and makes use of a C++ library for representing physical quantities called quan, also available on github at https://github.com/kwikius/quan-trunk.</ref>

<youtube>27LC2WRK0Rk</youtube>

=== The main requirements for a SITL simulation ===

==== Interfacing to FlightGear ====
There are many options to choose from {{ main article|Interfacing FlightGear}}

===== Sending data to the FDE =====
I chose to use [[Telnet_usage|telnet interface]]. There is a [https://sourceforge.net/p/flightgear/flightgear/ci/next/tree/scripts/example/fgfsclient.cxx C++ example in the FlightGear source code] , that shows basic useage. Telnet is relatively slow, but you need to send a surprisingly small amount of information to control the aircraft. Usually you are merely sending information to modify pitch, roll and yaw. Less frequently you are changing throttle ,flaps and so on. By caching data in your app and only sending information, if it actually changed, the overhead is quite low. When bandwidth becomes an issue, then there are other protocols available.

===== Receiving data from the FDE =====
I chose to use [[Property Tree/Sockets|socket interface]]. Again there is a [https://sourceforge.net/p/flightgear/flightgear/ci/next/tree/examples/netfdm C++example in the FlightGear source code]. Note that the example sends data to FlightGear, but the socket can also be used to read the [https://sourceforge.net/p/flightgear/flightgear/ci/next/tree/src/Network/net_fdm.hxx FGNetFDM] structure from FlightGear via a socket, which is what I chose to do. The FGNetFDM structure contains most, if not all the information that is need at a fast rate. Other data can be read back using the telnet interface.

=== Visualising the simulation ===
*The ability to view the simulation graphically. Though not entirely necessary, in practise this is most useful, since visualisation can show up issues that are hidden in data, therfore the examples use 3D graphical simulation where possible using FlightGear as the viewer in most cases.

==Footnotes==

<references />

User:Kwikius/Using FlightGear for software in the loop simulation

2021-06-16T10:10:15Z

Kwikius:

User:Kwikius/Using FlightGear for software in the loop simulation

2021-06-16T10:03:47Z

Kwikius: fix up links

User:Kwikius/Using FlightGear for software in the loop simulation

2021-06-16T09:59:39Z

Kwikius:

User:Kwikius/Using FlightGear for software in the loop simulation

2021-06-16T09:57:09Z

Kwikius: Add some detail and links about interfacing

User:Kwikius/Using FlightGear for software in the loop simulation

2021-06-16T08:56:18Z

Kwikius:

User:Kwikius/Using FlightGear for software in the loop simulation

2021-06-16T08:53:12Z

Kwikius: Use headings intro etc

User:Kwikius/Using FlightGear for software in the loop simulation

2021-06-16T08:43:39Z

Kwikius:

FlightGear is popular as both a viewer and a flight dynamics engine (FDE) for software in the loop (SITL) simulation. This article describes a project that uses FlightGear to provide a viewer and an FDE for simulating flying an RC aeroplane autonomously using a flight controller (FC). <ref>
The source code for the examples is available on github at https://github.com/kwikius/fg_ext_fdm.
The source code is written in reasonably modern C++ and makes use of a C++ library for representing physical quantities called quan, also available on github at https://github.com/kwikius/quan-trunk.</ref>

<youtube>27LC2WRK0Rk</youtube>

The main requirements for a SITL simulation are :

* To be able to send control commands to the FDE
* To receive back information from the FDE that can be used to simulate the FC sensors.
* The ability to view the simulation graphically. Though not entirely necessary, in practise this is most useful, since visualisation can show up issues that are hidden in data, therfore the examples use 3D graphical simulation where possible using FlightGear as the viewer in most cases.

==Footnotes==

User:Kwikius/Using FlightGear for software in the loop simulation

2021-06-16T08:39:03Z

Kwikius:

FlightGear is popular as both a viewer and a flight dynamics engine (FDE) for software in the loop (SITL) simulation. This article describes a project that uses FlightGear to provide a viewer and an FDE for simulating flying an RC aeroplane autonomously using a flight controller (FC). <ref>
The source code for the examples is available on github at https://github.com/kwikius/fg_ext_fdm.
The source code is written in reasonably modern C++ and makes use of a C++ library for representing physical quantities called quan, also available on github at https://github.com/kwikius/quan-trunk.</ref>

<youtube>27LC2WRK0Rk</youtube>

The main requirements for a SITL simulation are to be able to send control commands to the FDE and to receive back information from the FDE that can be used to simulate the FC sensors. The ability to view the simulation graphically is not entirely necessary, but the examples will all use 3D graphical simulation where possible using FlightGear as the viewer as well.

==Footnotes==

User:Kwikius/Using FlightGear for software in the loop simulation

2021-06-16T08:36:52Z

Kwikius: test footnotes

FlightGear is popular as both a viewer and a flight dynamics engine (FDE) for software in the loop (SITL) simulation. This article describes a project that uses FlightGear to provide a viewer and an FDE for simulating flying an RC aeroplane autonomously using a flight controller (FC). <ref>The implementation is firmly based on reasonably modern C++ and makes use of a C++ library for representing physical quantities called quan, also available on github at https://github.com/kwikius/quan-trunk.</ref>

<youtube>27LC2WRK0Rk</youtube>

The source code for the examples is available on github at https://github.com/kwikius/fg_ext_fdm.

The main requirements for a SITL simulation are to be able to send control commands to the FDE and to receive back information from the FDE that can be used to simulate the FC sensors. The ability to view the simulation graphically is not entirely necessary, but the examples will all use 3D graphical simulation where possible using FlightGear as the viewer as well.

User:Kwikius/Using FlightGear for software in the loop simulation

2021-06-16T08:24:18Z

Kwikius: Move some parts to footnotes

FlightGear is popular as both a viewer and a flight dynamics engine (FDE) for software in the loop (SITL) simulation. This article describes a project that uses FlightGear to provide a viewer and an FDE for simulating flying an RC aeroplane autonomously using a flight controller (FC). [1]

<youtube>27LC2WRK0Rk</youtube>

The source code for the examples is available on github at https://github.com/kwikius/fg_ext_fdm.

The main requirements for a SITL simulation are to be able to send control commands to the FDE and to receive back information from the FDE that can be used to simulate the FC sensors. The ability to view the simulation graphically is not entirely necessary, but the examples will all use 3D graphical simulation where possible using FlightGear as the viewer as well.

=== Footnotes ===

# The implementation is firmly based on reasonably modern C++ and makes use of a C++ library for representing physical quantities called quan, also available on github at https://github.com/kwikius/quan-trunk.

User:Kwikius/Using FlightGear for software in the loop simulation

2021-06-15T22:55:19Z

Kwikius:

FlightGear is popular as both a viewer and a flight dynamics engine (FDE) for software in the loop (SITL) simulation.
This article intends to describe a project that uses FlightGear to provide a viewer and an FDE for simulating flying an RC aeroplane autonomously using a flight controller (FC).

<youtube>27LC2WRK0Rk</youtube>

The source code for the examples is available on github at https://github.com/kwikius/fg_ext_fdm.

The implementation is firmly based on reasonably modern C++ and makes use of a C++ library for representing physical quantities called quan, also available on github at https://github.com/kwikius/quan-trunk.

The main requirements for a SITL simulation are to be able to send control commands to the FDE and to receive back information from the FDE that can be used to simulate the FC sensors. The ability to view the simulation graphically is not entirely necessary, but the examples will all use 3D graphical simulation where possible using FlightGear as the viewer as well.

User:Kwikius

2021-06-15T22:51:25Z

Kwikius: add link to first article

Veteran C++ programmer.

[[User:Kwikius/Using FlightGear for software in the loop simulation]]

User:Kwikius/Using FlightGear for software in the loop simulation

2021-06-15T22:40:04Z

Kwikius: A little more about the main simulation requirements

FlightGear is popular as both a viewer and a flight dynamics engine (FDE) for software in the loop (SITL) simulation.
This article intends to describe a project that uses FlightGear to provide a viewer and an FDE for simulating flying an RC aeroplane autonomously using a flight controller (FC).

The source code for the examples is available on github at https://github.com/kwikius/fg_ext_fdm.

The implementation is firmly based on reasonably modern C++ and makes use of a C++ library for representing physical quantities called quan, also available on github at https://github.com/kwikius/quan-trunk.

The main requirements for a SITL simulation are to be able to send control commands to the FDE and to receive back information from the FDE that can be used to simulate the FC sensors. The ability to view the simulation graphically is not entirely necessary, but the examples will all use 3D graphical simulation where possible using FlightGear as the viewer as well.

User:Kwikius/Using FlightGear for software in the loop simulation

2021-06-15T22:35:33Z

Kwikius: Created page with "FlightGear is popular as both a viewer and a flight dynamics engine (FDE) for software in the loop (SITL) simulation. This article intends to describe a project that uses Flig..."

FlightGear is popular as both a viewer and a flight dynamics engine (FDE) for software in the loop (SITL) simulation.
This article intends to describe a project that uses FlightGear to provide a viewer and an FDE for simulating flying an RC aeroplane autonomously using a flight controller (FC).

The source code for the examples is available on github at https://github.com/kwikius/fg_ext_fdm.

The implementation is firmly based on reasonably modern C++ and makes use of a C++ library for representing physical quantities called quan,
also available on github at https://github.com/kwikius/quan-trunk.

The main requirements for a SITL simulation are to be able to send control commands to the FDE and to receive back information from the FDE that can be used
to simulate the FC sensors. The ability to view the simulation Graphically is not entirely necessary, butthe examples ALL use 3D graphical simulation, since this is the main benefir of using FlighGear.

User:Kwikius

2021-06-15T22:01:30Z

Kwikius: Initial creation of page

Veteran C++ programmer.