fly316/PX4-Autopilot
7
0
Fork 0
mirror of https://gitee.com/mirrors_PX4/PX4-Autopilot.git synced 2026-10-03 16:08:53 +08:00
Code Issues Packages Projects Releases Wiki Activity

docs: Numerous spelling and grammer fixes in flight controller section (#26582)

Browse Source
This commit is contained in:
Hamish Willee
2026-02-26 11:53:44 +11:00
committed by GitHub
parent 3c961de3fe
commit 539b1def78
85 changed files with 391 additions and 396 deletions
Download Patch File Download Diff File Expand all files Collapse all files
docs/en/sim_gazebo_classic/index.md
+2 -2
View File
@@ -345,7 +345,7 @@ The video below shows that the location of the environment is aligned with the w
For extended development sessions it might be more convenient to start Gazebo Classic and PX4 separately or even from within an IDE.
In addition to the existing cmake targets that run `sitl_run.sh` with parameters for px4 to load the correct model it creates a launcher targets named `px4_<mode>` that is a thin wrapper around original sitl px4 app.
In addition to the existing cmake targets that run `sitl_run.sh` with parameters for PX4 to load the correct model it creates a launcher targets named `px4_<mode>` that is a thin wrapper around original sitl PX4 app.
This thin wrapper simply embeds app arguments like current working directories and the path to the model file.
To start Gazebo Classic and PX4 separately:
@@ -365,7 +365,7 @@ To start Gazebo Classic and PX4 separately:
- In your IDE select `px4_<mode>` target you want to debug (e.g. `px4_iris`)
- Start the debug session directly from IDE
This approach significantly reduces the debug cycle time because simulator is always running in background and you only re-run the px4 process which is very light.
This approach significantly reduces the debug cycle time because simulator is always running in background and you only re-run the PX4 process which is very light.
## Simulated Survey Camera