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

Put the current mode of the plane into a string #50

Closed
wants to merge 3 commits into from
Closed

Conversation

vinaxue
Copy link
Contributor

@vinaxue vinaxue commented Apr 12, 2019

Added the mode of the plane as a string to the overview telemetry protobuf message.

@vinaxue vinaxue requested review from oldmud0 and bbridges April 12, 2019 01:21
@@ -24,6 +24,7 @@ message Overview {
Velocity vel = 5;
Speed speed = 6;
Battery battery = 7;
string mode = 8;
Copy link
Member

Choose a reason for hiding this comment

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

Hmm, I wonder if we should enumerate the mode. This works for now though, and enumerating has complications because the custom mode differs based on the firmware.

Copy link
Member

Choose a reason for hiding this comment

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

Can add an endpoint for returning the available modes for the autopilot in strings for the future?

Copy link
Member

Choose a reason for hiding this comment

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

Also the file mode on this file changed in the commit

Copy link
Member

@bbridges bbridges left a comment

Choose a reason for hiding this comment

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

You need to verify that the autopilot is not PX4 and that the mav_type is coming from a fixed wing plane before doing mode conversions. Need to add a test checking that the mode has been classified. I'd also break the logic out for classifying the mode into a separate mode.js file and keep in mind variable naming conventions on declaring the mode mapping constant.

@bbridges
Copy link
Member

bbridges commented May 6, 2019

Closing in favor of just including the functionality done here in #53.

@bbridges bbridges closed this May 6, 2019
@oldmud0
Copy link
Member

oldmud0 commented May 6, 2019

Wait what?

@oldmud0
Copy link
Member

oldmud0 commented Feb 14, 2020

It was true, set-mode was an outdated branch succeeded by plane-mode. Deleting branch.

@oldmud0 oldmud0 deleted the plane-mode branch February 14, 2020 01:53
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.

4 participants