mirror of
https://gitee.com/mirrors_PX4/PX4-Autopilot.git
synced 2026-04-14 10:07:39 +08:00
* Add vitepress tree * Update existing workflows so they dont trigger on changes in the docs path * Add nojekyll, package.json, LICENCE etc * Add crowdin docs upload/download scripts * Add docs flaw checker workflows * Used docs prefix for docs workflows * Crowdin obvious fixes * ci: docs move to self hosted runner runs on a beefy server for faster builds Signed-off-by: Ramon Roche <mrpollo@gmail.com> * ci: don't run build action for docs or ci changes Signed-off-by: Ramon Roche <mrpollo@gmail.com> * ci: update runners Signed-off-by: Ramon Roche <mrpollo@gmail.com> * Add docs/en * Add docs assets and scripts * Fix up editlinks to point to PX4 sources * Download just the translations that are supported * Add translation sources for zh, uk, ko * Update latest tranlsation and uorb graphs * update vitepress to latest --------- Signed-off-by: Ramon Roche <mrpollo@gmail.com> Co-authored-by: Ramon Roche <mrpollo@gmail.com>
49 lines
1.7 KiB
Markdown
49 lines
1.7 KiB
Markdown
# MAVLink Shell
|
|
|
|
The MAVLink Shell is an _NSH console_ that can be accessed via MAVLink over serial (USB/Telemetry) or WiFi (UDP/TCP) links (in particular, on NuttX-based systems like: Pixhawk, Pixracer, etc.).
|
|
|
|
The shell can be used for running commands and modules, and displaying their output.
|
|
While the shell cannot _directly_ display the output of modules that it does not start, it can do so indirectly using the `dmesg` command (`dmesg -f &` can be used to display the output of other modules and tasks running on the work queue).
|
|
|
|
:::tip
|
|
The [QGroundControl MAVLink Console](#qgroundcontrol) is the easiest way to access the console.
|
|
If the system does not start properly you should instead use the [System Console](../debug/system_console.md).
|
|
:::
|
|
|
|
## Opening the Shell
|
|
|
|
<a id="qgroundcontrol"></a>
|
|
|
|
### QGroundControl MAVLink Console
|
|
|
|
The easiest way to access shell is to use the [QGroundControl MAVLink Console](https://docs.qgroundcontrol.com/master/en/qgc-user-guide/analyze_view/mavlink_console.html) (see **Analyze View > Mavlink Console**).
|
|
|
|
### mavlink_shell.py
|
|
|
|
You can also access the shell in a terminal using the **mavlink_shell.py** script:
|
|
|
|
1. Shut down _QGroundControl_.
|
|
1. Install dependencies:
|
|
|
|
```sh
|
|
pip3 install --user pymavlink pyserial
|
|
```
|
|
|
|
1. Open terminal (in PX4-Autopilot directory) and start the shell:
|
|
|
|
```sh
|
|
# For serial port
|
|
./Tools/mavlink_shell.py /dev/ttyACM0
|
|
```
|
|
|
|
```sh
|
|
# For Wifi connection
|
|
./Tools/mavlink_shell.py 0.0.0.0:14550
|
|
```
|
|
|
|
Use `mavlink_shell.py -h` to get a description of all available arguments.
|
|
|
|
## Using the MAVLink Shell
|
|
|
|
For information see: [PX4 Consoles/Shells > Using Consoles/Shells](../debug/consoles.md#using_the_console).
|