Skip to content

Commit

Permalink
Modify figure path
Browse files Browse the repository at this point in the history
  • Loading branch information
JcZou committed Jul 25, 2023
1 parent 1161b3b commit 0d1cbd0
Show file tree
Hide file tree
Showing 2 changed files with 13 additions and 5 deletions.
10 changes: 7 additions & 3 deletions docs/introduction/download.md
Original file line number Diff line number Diff line change
Expand Up @@ -25,7 +25,9 @@ After installing the compiler, the next step is to create a new environment vari

- **Windows**: Open the Control Panel, go to System and Security > System > Advanced system settings > Environment Variables. Click on "New" under "User variables" and enter the variable name as `RTT_EXEC_PATH` and the variable value as the full path to the compiler's bin directory.

<img src="../figures/win_exec_path.png" width="30%">
<p align="center">
<img src="./figures/win_exec_path.png" width="30%">
</p>

- **Linux/Mac**: Open a terminal and edit the shell configuration file (e.g., `~/.bashrc`, `~/.bash_profile`, or `~/.zshrc`, depending on your shell). Add the following line to the file:

Expand Down Expand Up @@ -83,8 +85,9 @@ To begin coding for the FMT-Firmware project in Visual Studio Code, follow these

Now, you have the FMT-Firmware project opened in Visual Studio Code, and you can start coding, modifying, and managing the project using the various features and extensions provided by the IDE. Happy coding!

<img src="../figures/vscode.png" width="50%">

<p align="center">
<img src="./figures/vscode.png" width="50%">
</p>

Absolutely, installing useful Visual Studio Code (VS Code) plugins can significantly enhance your development experience when working with the FMT-Firmware project. Two essential plugins for the FMT-Firmware project are:

Expand All @@ -100,3 +103,4 @@ To install these plugins, follow these steps:
5. After installation, you may need to restart Visual Studio Code to activate the plugins.

With these plugins installed, your development environment will be better equipped to handle the intricacies of the FMT-Firmware project, making coding and formatting tasks more efficient and convenient.

8 changes: 6 additions & 2 deletions docs/introduction/gcs.md
Original file line number Diff line number Diff line change
Expand Up @@ -6,7 +6,9 @@ QGroundControl (QGC) 3.5.6 is the preferred GCS for FMT usage, which ensures a s

It is important to note that FMT does not have a custom-tailored version of QGC. Instead, it utilizes the QGC PX4 version. As a result, you may encounter some errors, such as missing parameters, when using QGC PX4 with FMT. This is normal since QGC PX4 is primarily designed for PX4 and may not be fully optimized for FMT. Despite these errors, FMT can still function correctly, and developers are continuously working to improve the integration between FMT and QGC for a smoother experience.

<img src="../figures/qgc.png" width="60%">
<p align="center">
<img src="./figures/qgc.png" width="60%">
</p>

## Connect to GCS
To establish a connection between the Flight Controller and the GCS, you can either use a USB cable or telemetry.
Expand All @@ -15,4 +17,6 @@ For standard Pixhawk hardware, the QGC can automatically detect and connect to t

However, for other hardware configurations like ICF5, you may need to create the communication link manually. This involves configuring the communication parameters, such as baud rates and port, to establish a successful connection between the Flight Controller and the GCS.

<img src="../figures/qgc_connect.png" width="60%">
<p align="center">
<img src="./figures/qgc_connect.png" width="60%">
</p>

0 comments on commit 0d1cbd0

Please sign in to comment.