-
Notifications
You must be signed in to change notification settings - Fork 13.6k
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
Mixer: FunctionMotors: leave NAN control values at NAN with non-zero THR_MDL_FAC #24108
Conversation
…THR_MDL_FAC Signed-off-by: Silvan Fuhrer <[email protected]>
Signed-off-by: Silvan Fuhrer <[email protected]>
🔎 FLASH Analysispx4_fmu-v5x [Total VM Diff: 88 byte (0 %)]
px4_fmu-v6x [Total VM Diff: 72 byte (0 %)]
Updated: 2024-12-13T15:45:26 |
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.
Good find
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.
Thank you for fixing this so quickly 👍
We should add unit tests for this and cover the cases that are part of the interface 👀
Solved Problem
Fixes #24083.
Solution
Leave NAN untouched, even if THR_MOD_FAC is set.
Changelog Entry
For release notes: Mixer: leave NAN control values at NAN with non-zero THR_MDL_FAC to fix VTOL motors not turning off correctly.
Alternatives
Should the whole THR_MOD_FAC logic not live in the control allocation? Why is it handled by the mixer?
Test coverage
SITL tested.