Files
PX4-Autopilot/docs/en/modules/modules_driver_camera.md
T
Alex E 59fa7a4a7d docs(modules): add auto-generated disclaimer to every module reference page (#29673)
Only modules_main.md told readers that the module reference is generated
from source. The per-category pages (modules_driver.md, modules_system.md,
...) and the per-subcategory pages (modules_driver_imu.md, ...) had no such
note, so contributors kept fixing typos directly in docs/en/modules/ and
the next metadata sync silently reverted them (see #29614).

Emit a `::: info` block right under the H1 of every category and
subcategory page. The wording follows the existing disclaimers on the
airframe reference and the uORB message index: it links to the generator
script and names the `make module_documentation` target.

docs/en/modules/*.md are regenerated with the updated generator and run
through Prettier, mirroring what the docs-orchestrator metadata sync does
on main, so the diff is only the new note.

Fixes #29624

Assisted-by: Claude:claude-fable-5-1

Signed-off-by: Alex E <aelejandro9@gmail.com>
2026-11-10 08:51:33 +11:00

2.1 KiB

Modules Reference: Camera (Driver)

::: info This page is auto-generated from the source code using the build command: make module_documentation. Do not edit it directly; fix the module documentation in the PX4-Autopilot source instead. :::

camera_trigger

Source: drivers/camera_trigger

Description

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 received 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. In particular:

  • 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.

Usage

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