ArduPilot/ardupilot

DO_SET_ROI_LOCATION and DO_SET_ROI_NONE "gimbal device id" fields should be supported

Open

#29,566 创建于 2025年3月19日

在 GitHub 查看
 (6 评论) (0 反应) (0 负责人)C++ (9,336 star) (15,603 fork)batch import
good first issue

描述

AP supports the DO_SET_ROI_LOCATION and DO_SET_ROI_NONE as "immediate" and mission commands but we do not correctly consume "param1" ("Gimbal device ID"). Instead it is always the first camera gimbal that is controlled. We should consume this field and control the gimbal device specified

PR https://github.com/ArduPilot/ardupilot/pull/29567 added mission support for these commands

贡献者指南

技术栈
cpp
领域
api
议题类型
feature
难度面向新贡献者的预计实现难度，1 表示很小改动，5 表示专家级工作。
3
预计时间有经验贡献者完成调查、实现、测试并准备 pull request 的粗略时间范围。
half day
活动状态议题当前的可参与程度：新鲜、活跃、陈旧、阻塞或等待维护者输入。
active
清晰度议题是否清楚说明期望改动、验收标准和下一步。
mostly clear
前置要求
Basic C++MAVLink protocolArduPilot build system
新手友好度1-100 的估计分数，表示该议题对首次贡献者的友好程度。
35
研究方向
Examine the handling of DO SET ROI commands (likely in GCS Mavlink.cpp or similar). Identify where param1 is currently ignored. Implement logic to read gimbal device ID from param1 and control the specified gimbal. Use PR #29567 as a reference for mission support implementation. Consult MAVLink documentation for param1 usage.
DO_SET_ROI_LOCATION and DO_SET_ROI_NONE "gimbal device id" fields should be supported · ArduPilot/ardupilot#29566 | Good First Issue