esc_report: change esc_temperature field to allow negative values [needs mavlink submodule update] #18108
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.
Title is self explanatory. This PR needs to go in after the relative mavlink message is updated, mavlink/mavlink#1663.
@dagar i've also noticed that the UAVCAN spec defines the temperature in Kelvin for
uavcan.equipment.esc.Status
(https://legacy.uavcan.org/Specification/7._List_of_standard_data_types/), looking at the code we've always filled the esc_temperature directly from the UAVCAN message.. not sure who to trust there :|