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.