Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

MissionItemProtocol_Rally: Use *_INT frames for Rally mission items #26400

Closed
wants to merge 1 commit into from

Conversation

nexton-winjeel
Copy link
Contributor

get_item_as_mission_item() returns a mavlink_mission_item_int_t and as such should be using the *_INT versions of the MAV_FRAMEs.

Follows from changes in #25380.

FYI: @IamPete1

@@ -117,24 +117,24 @@ bool MissionItemProtocol_Rally::get_item_as_mission_item(uint16_t seq,
}

// Default to relative to home
ret_packet.frame = MAV_FRAME_GLOBAL_RELATIVE_ALT;
ret_packet.frame = MAV_FRAME_GLOBAL_RELATIVE_ALT_INT;
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

We do not distinguish these frames.

i.e. An altitude frame doesn't care whether you're transporting things via integer or float.

The creation of these frames is acknowledged as a mistake.

@IamPete1
Copy link
Member

IamPete1 commented Mar 5, 2024

The current behavior is inline with what we do for the mission and fence.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants