Structure Scan - Gimbal Orientation #9405
Merged
Conversation
This file contains 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
|
I initially thought this was an ROI setting, but now I see it makes sense. Architecturally it would be better for navigator to be interpreting the ROI and sending gimbal commands (if appropriate), but this is good for now. |
dagar
approved these changes
May 3, 2018
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
I have tested the Structure Scan feature and the gimbal doesn't point perpendicularly to the heading.
The gimbal points to the next triplet with an offset of 90deg which is not the area of interest.
In order to have the gimbal pointing towards the structure when
MIS_MNT_YAW_CTL =1, the gimbal has to point to the current triplet with an offset of 90deg.