-
Notifications
You must be signed in to change notification settings - Fork 17.5k
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
Param Metadata - Mark more compass values as calibration and make the loop rate a range #28470
Conversation
Makes it easier for GUI applications to display this better and valudate the range
what functional impact does this have? |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
Marking this for DevCall to make sure people are OK with the concept of a "range" for the main loop rate. @Hwurzburg these obviously don't affect the flight code - but will be important for MethodicConfigurator and other places. It may affect the interface in MissionPlanner poorly for the range check - perhaps a slider rather than a dropdown for the main loop rate. @amilcarlucas have you checked that? |
I did not test MP, but it will improve the Methodic configurator GUI. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Seems like a sensible change.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
we could increase the LOOP_RATE range to 800 but this is fine, txs!
No description provided.