Move PX4 Guide source into /docs (#24490)

* 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>
This commit is contained in:
Hamish Willee
2025-03-13 16:08:27 +11:00
committed by GitHub
co-authored by Ramon Roche
parent 8e6d2ebe4a
commit 88d623bedb
5176 changed files with 558771 additions and 2 deletions
+32
View File
@@ -0,0 +1,32 @@
# Failsafe State Machine Simulation
<Badge type="tip" text="PX4 v1.14" />
This page can be used to simulate the actions of the PX4 failsafe state machine under all possible configurations and conditions.
The simulation runs the same code in the browser as is executed on the vehicle, in real-time (the simulation is automatically kept in sync with the latest version of the code).
Note that any delayed action (`COM_FAIL_ACT_T`) will also be delayed in the simulation.
To use it:
1. First configure the parameters on the left.
The initial values correspond to the PX4 defaults.
2. Set the vehicle type
3. Set the other values in the **State** or any of the flags under **Conditions**
- The **Intended Mode** corresponds to the commanded mode via RC or GCS (or external script).
The failsafe state machine can override this in case of a failsafe.
4. Check the action under **Output**
5. Check what happens when changing mode or **Move the RC sticks**
6. Play with different settings and conditions!
The simulation can also be executed locally in order to test a specific version or set of changes:
```sh
make run_failsafe_web_server
```
<iframe :src="withBase('/config/failsafe/index.html')" frameborder="0" height="1400px" style="text-align: center; margin-left: -20px; margin-right: -230px;" width="1200"></iframe>
<script setup>
import { withBase } from 'vitepress';
</script>