mirror of
https://github.com/PX4/PX4-Autopilot.git
synced 2026-07-26 16:28:06 +08:00
Fix all possible HTTP to HTTPS docs links (#25153)
This commit is contained in:
@@ -7,8 +7,8 @@ It may or may not work with current versions of PX4.
|
||||
See [Toolchain Installation](../dev_setup/dev_env.md) for information about the environments and tools supported by the core development team.
|
||||
:::
|
||||
|
||||
[FlightGear](https://www.flightgear.org/) is a flight simulator with powerful [FDM engines](http://wiki.flightgear.org/Flight_Dynamics_Model).
|
||||
This allows FlightGear to simulate rotorcrafts under various meteorological conditions (which is why the bridge was originally developed by [ThunderFly s.r.o.](https://www.thunderfly.cz/)).
|
||||
[FlightGear](https://wiki.flightgear.org/Flight_Dynamics_Model) is a flight simulator with powerful [FDM engines](https://wiki.flightgear.org/Flight_Dynamics_Model).
|
||||
This allows FlightGear to simulate rotorcraft under various meteorological conditions (which is why the bridge was originally developed by [ThunderFly s.r.o.](https://www.thunderfly.cz/)).
|
||||
|
||||
This page describes FlightGear's single-vehicle use in SITL.
|
||||
For information about multi-vehicle use see: [Multi-Vehicle Simulation with FlightGear](../sim_flightgear/multi_vehicle.md).
|
||||
@@ -189,7 +189,7 @@ 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: `--airport`, `--runway`, and `--offset-distance`.
|
||||
Other options can be found on [FlightGear wiki](http://wiki.flightgear.org/Command_line_options#Initial_Position_and_Orientation)
|
||||
Other options can be found on [FlightGear wiki](https://wiki.flightgear.org/Command_line_options#Initial_Position_and_Orientation)
|
||||
|
||||
For example:
|
||||
|
||||
@@ -197,7 +197,7 @@ For example:
|
||||
FG_ARGS_EX="--airport=PHNL" make px4_sitl_nolockstep flightgear_rascal
|
||||
```
|
||||
|
||||
The example above starts the simulation on the [Honolulu international airport](http://wiki.flightgear.org/Suggested_airports)
|
||||
The example above starts the simulation on the [Honolulu international airport](https://wiki.flightgear.org/Suggested_airports)
|
||||
|
||||
### Using a Joystick
|
||||
|
||||
|
||||
@@ -25,7 +25,7 @@ The most suitable one for UAV development is currently the [Rascal RC plane](htt
|
||||
|
||||

|
||||
|
||||
The variants differ mainly by the [FDM](http://wiki.flightgear.org/Flight_Dynamics_Model) model.
|
||||
The variants differ mainly by the [FDM](https://wiki.flightgear.org/Flight_Dynamics_Model) model.
|
||||
All variants have a common feature selection table that can be activated by pressing the `=` key on the computer keyboard.
|
||||
|
||||
There is a pop-up table that could be used for advanced features activation.
|
||||
@@ -119,7 +119,7 @@ The file content meaning is as follows:
|
||||
|
||||
- `FgModel` - a precise case sensitive name of the FlightGear model corresponding to "XXXX-set.xml" in the model directory (where XXXX is the model name).
|
||||
- `Url` is optional and it is not currently used. It is intended for future use to auto-download the models from web
|
||||
- `Controls` - the most important part of the process of adding a vehicle. This section contains the mapping between the PX4 mixer file and [FlightGear property tree](http://wiki.flightgear.org/Property_tree).
|
||||
- `Controls` - the most important part of the process of adding a vehicle. This section contains the mapping between the PX4 mixer file and [FlightGear property tree](https://wiki.flightgear.org/Property_tree).
|
||||
- The first number in a list selects a PX4 mixer output.
|
||||
- Path string is a FlightGear variable location in the property tree.
|
||||
- The last number in a list is a multiplier, allowing inversion or scaling of mixer input.
|
||||
|
||||
Reference in New Issue
Block a user