mirror of
https://gitee.com/mirrors_PX4/PX4-Autopilot.git
synced 2026-04-14 10:07:39 +08:00
88d623bedb
* 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>
54 lines
1.8 KiB
Markdown
54 lines
1.8 KiB
Markdown
# Modules Reference: Camera (Driver)
|
|
|
|
## camera_trigger
|
|
|
|
Source: [drivers/camera_trigger](https://github.com/PX4/PX4-Autopilot/tree/main/src/drivers/camera_trigger)
|
|
|
|
### Опис
|
|
|
|
Camera trigger driver.
|
|
|
|
This module triggers cameras that are connected to the flight-controller outputs,
|
|
or simple MAVLink cameras that implement the MAVLink trigger protocol.
|
|
|
|
The driver responds to the following MAVLink trigger commands being found in missions or recieved over MAVLink:
|
|
|
|
- `MAV_CMD_DO_TRIGGER_CONTROL`
|
|
- `MAV_CMD_DO_DIGICAM_CONTROL`
|
|
- `MAV_CMD_DO_SET_CAM_TRIGG_DIST`
|
|
- `MAV_CMD_OBLIQUE_SURVEY`
|
|
|
|
The commands cause the driver to trigger camera image capture based on time or distance.
|
|
Each time an image capture is triggered, the `CAMERA_TRIGGER` MAVLink message is emitted.
|
|
|
|
A "simple MAVLink camera" is one that supports the above command set.
|
|
When configured for this kind of camera, all the driver does is emit the `CAMERA_TRIGGER` MAVLink message as expected.
|
|
The incoming commands must be forwarded to the MAVLink camera, and are automatically emitted to MAVLink channels
|
|
when found in missions.
|
|
|
|
The driver is configured using [Camera Trigger parameters](../advanced_config/parameter_reference.md#camera-trigger).
|
|
Зокрема:
|
|
|
|
- `TRIG_INTERFACE` - How the camera is connected to flight controller (PWM, GPIO, Seagull, MAVLink)
|
|
- `TRIG_MODE` - Distance or time based triggering, with values set by `TRIG_DISTANCE` and `TRIG_INTERVAL`.
|
|
|
|
[Setup/usage information](../camera/index.md).
|
|
|
|
<a id="camera_trigger_usage"></a>
|
|
|
|
### Використання
|
|
|
|
```
|
|
camera_trigger <command> [arguments...]
|
|
Commands:
|
|
start
|
|
|
|
stop Stop driver
|
|
|
|
status Print driver status information
|
|
|
|
test Trigger one image (not logged or forwarded to GCS)
|
|
|
|
test_power Toggle power
|
|
```
|