* 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>
1.4 KiB
Path Planning Interface
:::warning The Path Planning Interface, along with the features Obstacle avoidance in Missions and Safe Landing are no longer supported or maintained, and should not be used in any PX4 version.
This code was abandoned due to architectural constraints of the implementation making it hard to maintain, extend, and adopt. Support has been withdrawn make it clear that this interface is untested. :::
:::tip PX4 is now adopting more generic and scalable approaches for integrating these kinds of features. For example the PX4 ROS 2 Interface Library allows complete replacement of PX4 flight modes with enhanced versions written using ROS 2. :::
This interface allows PX4 to stream a proposed path to a companion computer, and receive back a stream of setpoints that more safely achieves the emitted path, or a mirror of the same stream if the path planning software does not support planning for the current PX4 mode. This enables features such obstacle avoidance in missions and safer landing to be provided by a planner on a companion computer.
This actual code is still present in code at time of writing (PX4 v1.15). Information about the API and associated features can be found in the PX4 v1.14 docs.