Repository navigation
docs(update): Clarify that the Nan/INT32_MAX values should be used on new params - #786
Merged
hamishwillee merged 3 commits intoOct 1, 2026
Merged
Conversation
hamishwillee
commented
Oct 1, 2026
hamishwillee
commented
Oct 1, 2026
Co-authored-by: Hamish Willee <hamishwillee@gmail.com>
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.
This updates the dev guide to make it clear that
NaNfor float params andINT32_MAXfor INT32 params.@peterbarker I've put in weasel words to not that existing implementations may use 0 for historical reasons and explicitly mentioned ArduPilot. I.e. it is not a bug.
I'd like to make corresponding updates to pymavlink.