Skip to content

Commit 0d4d4a3

Browse files
authored
Update README.md
Improve wording.
1 parent 5e98e4d commit 0d4d4a3

File tree

1 file changed

+8
-8
lines changed

1 file changed

+8
-8
lines changed

README.md

Lines changed: 8 additions & 8 deletions
Original file line numberDiff line numberDiff line change
@@ -10,11 +10,11 @@ This stand-alone application adds the possibility of the use of the FlightGear s
1010

1111
It connects to FG (over UDP generic protocol) and transforms the data to TCP MAVlink packets for the PX4 stack.
1212

13-
### How to use the FlightGear with PX4
13+
### How to use FlightGear with PX4
1414

1515
#### Install
1616

17-
1) Install FlightGear. In Ubuntu You can use install the last stable FG from the [PPA repository](https://launchpad.net/~saiarcot895/+archive/ubuntu/flightgear) by following commands: ```sudo add-apt-repository -y -u ppa:saiarcot895/flightgear``` and ```sudo DEBIAN_FRONTEND=noninteractive apt-get -y --quiet install flightgear```
17+
1) Install FlightGear. In Ubuntu, you can install the latest stable FG from the [PPA repository](https://launchpad.net/~saiarcot895/+archive/ubuntu/flightgear) by following commands: ```sudo add-apt-repository -y -u ppa:saiarcot895/flightgear``` and ```sudo DEBIAN_FRONTEND=noninteractive apt-get -y --quiet install flightgear```
1818
* Alternatively use the [TF modified FlightGear](https://github.com/ThunderFly-aerospace/FlightGear/wiki) for advanced features of the models.
1919
3) Set write permissions to the `Protocols` folder in the FlightGear installation directory. On Ubuntu run ```sudo chmod a+w /usr/share/games/flightgear/Protocol ```
2020

@@ -55,11 +55,11 @@ General usage consists following steps
5555

5656
#### Known issues
5757

58-
1) If you have FPS lower than 20 the bridge will not work correctly. Check your FPS. In FlightGear display frame rate by enabling it in View->View Options->Show frame rate.
58+
1) If you have FPS lower than 20, the bridge will not work correctly. Check your FPS. In FlightGear, display frame rate by enabling it in View->View Options->Show frame rate.
5959
2) You can probably use a wild set of FG versions - we tested installation with FG 2019.1.1 and 2020.3.8. But in the past, we achieved basic functionality on Debian 9 running FG 2016.1.1 from the distribution repository.
60-
3) Multiple models packaged with the bridge have an electric engine that needs up-to-date FlightGear.
60+
3) Multiple models packaged with the bridge have an electric engine that requires up-to-date FlightGear.
6161
5) PX4 internal starting script runs ```fgfs``` with a set of parameters to reduce graphic load.
62-
6) The starting script searches for the FG-Data folder. Run ```fgfs --version``` to check the paths. If your output of this command does not contain the FG_ROOT line, the script will not work. Check where are FG binaries in your system, by executing the command ``` which fgfs```. Then the Advanced Options section of this readme could help you.
62+
6) The starting script searches for the FG-Data folder. Run ```fgfs --version``` to check the paths. If your output of this command does not contain the FG_ROOT line, the script will not work. Check where are FG binaries are in your system, by executing the command ``` which fgfs```. Then the Advanced Options section of this readme could help you.
6363

6464
### Advanced Options
6565

@@ -69,7 +69,7 @@ You can tune your FG installation/settings by the following environment variable
6969
2) ```FG_MODELS_DIR``` - absolute path to the folder containing the manually downloaded aircraft models that should be used for simulation.
7070
3) ```FG_ARGS_EX``` - any additional FG parameters
7171

72-
FlightGear Bridge and starting script now support multiple instances of PX4. FG\_run script takes the second argument, which is PX4 ID (and automatically adjusts the port numbers according to the given number) and bridge binary takes this ID as the first argument before the output of get\_FGbridge\_params.py
72+
FlightGear Bridge and starting script now support multiple instances of PX4. FG\_run script takes the second argument, which is PX4 ID (and automatically adjusts the port numbers according to the given number), and bridge binary takes this ID as the first argument before the output of get\_FGbridge\_params.py
7373

7474
If you want to use a currently unsupported FlightGear aircraft with PX4, you need:
7575
1) Add the FlightGear aircraft to ```models``` subdirectory, or to another MODEL PATH searched by FG
@@ -83,8 +83,8 @@ If you want to test another plane model, you can switch the Rascal model to anot
8383

8484
The PX4 is connected to FlightGear through "[generic protocol](http://wiki.flightgear.org/Generic_protocol)", which is served synchronously to the simulator graphics engine frame rate. So the PX4 gets the sensor data in frequency, depending on graphics resources and the current scene. The source code implements the artificial upsampling of sensor data to ~100Hz to avoid stale sensor detection triggers in PX4. Random noise is added to the sensor data.
8585

86-
The possible better approach is to obtain the FlightGear using an [HLA](http://wiki.flightgear.org/High-Level_Architecture) interface.
86+
The possibly better approach is to connect FlightGear using an [HLA](http://wiki.flightgear.org/High-Level_Architecture) interface.
8787

8888
### Credits
8989

90-
FlightGear bridge was initially developed at [ThunderFly s.r.o.](https://www.thunderfly.cz/) by Vít Hanousek <info@thunderfly.cz>
90+
FlightGear bridge was initially developed at [ThunderFly s.r.o.](https://www.thunderfly.cz/) by @slimonslimon <support@thunderfly.cz>

0 commit comments

Comments
 (0)