4.8:23092/DO_SET_ROI_WPNEXT_OFFSET - #7920
Open
Hwurzburg wants to merge 1 commit into
Open
Conversation
…OFFSET Add MAV_CMD_DO_SET_ROI_WPNEXT_OFFSET (points the gimbal at the next mission waypoint with an optional roll/pitch/yaw offset) to Copter's supported-commands list and a new detail section, per ardupilot PR 23092. Documented as Copter-only: AP_Vehicle::get_wp_location() is only overridden by ArduCopter, so Plane/Rover/Sub accept the mission item but the mount never receives a target. Also notes the >2MB flash requirement (AP_MOUNT_ROI_WPNEXT_OFFSET_ENABLED). Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
Hwurzburg
added a commit
to Hwurzburg/ardupilot_wiki
that referenced
this pull request
Aug 2, 2026
…ROI_WPNEXT_OFFSET Reference the new-board and new-feature wiki PRs added in this batch: - SimpliFly H7: ArduPilot#7915 - AET-H743-Air: ArduPilot#7918 - MAV_CMD_DO_SET_ROI_WPNEXT_OFFSET (Copter): ArduPilot#7920 Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
Hwurzburg
added a commit
to Hwurzburg/ardupilot_wiki
that referenced
this pull request
Aug 2, 2026
…ROI_WPNEXT_OFFSET, accel/gyro check timing Reference the new-board and new-feature wiki PRs added in this batch: - SimpliFly H7: ArduPilot#7915 - AET-H743-Air: ArduPilot#7918 - MAV_CMD_DO_SET_ROI_WPNEXT_OFFSET (Copter): ArduPilot#7920 - Accel/gyro consistency check timing (all vehicles): ArduPilot#7921 Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
Hwurzburg
added a commit
that referenced
this pull request
Aug 2, 2026
…ROI_WPNEXT_OFFSET, accel/gyro check timing Reference the new-board and new-feature wiki PRs added in this batch: - SimpliFly H7: #7915 - AET-H743-Air: #7918 - MAV_CMD_DO_SET_ROI_WPNEXT_OFFSET (Copter): #7920 - Accel/gyro consistency check timing (all vehicles): #7921 Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
rmackay9
approved these changes
Aug 2, 2026
rmackay9
left a comment
rmackay9
left a comment
Contributor
There was a problem hiding this comment.
Looks OK to me. This is @peterbarker's work I think
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Documents MAV_CMD_DO_SET_ROI_WPNEXT_OFFSET (point gimbal at next waypoint with an offset), per ardupilot PR ArduPilot/ardupilot#23092.
Documented as Copter-only since AP_Vehicle::get_wp_location() is currently only overridden by ArduCopter; Plane/Rover/Sub accept the mission item but the mount never receives a target. Also notes the >2MB flash requirement.