mirror of
https://github.com/mavlink/mavlink.git
synced 2026-06-19 07:35:34 +00:00
common: add camera_device_id to CAMERA_INFORMATION (#2121)
* common: add camera_device_id to CAMERA_INFORMATION By adding a camera_device_id to a CAMERA_INFORMATION message, we allow an autopilot to be a proxy for a MAVLink or non-MAVLink camera. The idea is similar to a gimbal manager implemented by an autopilot. * Update message_definitions/v1.0/common.xml --------- Co-authored-by: Hamish Willee <hamishwillee@gmail.com>
This commit is contained in:
@@ -6909,6 +6909,7 @@
|
||||
<field type="char[140]" name="cam_definition_uri">Camera definition URI (if any, otherwise only basic functions will be available). HTTP- (http://) and MAVLink FTP- (mavlinkftp://) formatted URIs are allowed (and both must be supported by any GCS that implements the Camera Protocol). The definition file may be xz compressed, which will be indicated by the file extension .xml.xz (a GCS that implements the protocol must support decompressing the file). The string needs to be zero terminated. Use a zero-length string if not known.</field>
|
||||
<extensions/>
|
||||
<field type="uint8_t" name="gimbal_device_id" invalid="0">Gimbal id of a gimbal associated with this camera. This is the component id of the gimbal device, or 1-6 for non mavlink gimbals. Use 0 if no gimbal is associated with the camera.</field>
|
||||
<field type="uint8_t" name="camera_device_id" invalid="0">Camera id of a camera associated with this component. This is the component id of a proxied MAVLink camera, or 1-6 for a non-MAVLink camera attached to the component. Use 0 if the component is a camera (not something else providing access to a camera).</field>
|
||||
</message>
|
||||
<message id="260" name="CAMERA_SETTINGS">
|
||||
<description>Settings of a camera. Can be requested with a MAV_CMD_REQUEST_MESSAGE command.</description>
|
||||
|
||||
Reference in New Issue
Block a user