Hamish Willee 88d623bedb
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>
2025-03-13 16:08:27 +11:00

1.4 KiB

Cameras

Cameras are important for many payload use cases, including mapping and surveying, surveillance, search & rescue, crop health and pest detection, and so on. They are commonly mounted on a gimbal that can provide camera stabilisation, point tracking, and movement independent of the hosting vehicle.

Camera Types

PX4 integrates with three types of cameras:

MAVLink cameras are recommended because they provide the broadest access to camera features using a simple and consistent command/message set. If a camera does not support this prototol, a camera manager running on a companion computer can be used to interface between MAVLink and the camera's native protocol.

See Also