-
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
AutoMapper1/2: set thrust to NAN at idle #11229
Conversation
This fixes a bug where a multicopter tries to control attitude and therefore takes off when in HOLD mode and landed.
One catch is that this only works once, and not again after a takeoff and landing. |
Can we reset the whole state after landing? This applies to other states as well. |
I think I don't understand what's going on, especially not this: |
@bresch Could you please chime in here? @julianoes Maybe catch up quickly in person.. |
@julianoes as I explained in #11197, the issue only occurs with with MPC_AUTO_MODE is set to jerk-limited. So if you need a quick fix, then we should change the default back to 0 (https://github.com/PX4/Firmware/blob/master/src/modules/mc_pos_control/mc_pos_control_params.c#L684) |
We can have a call, but I fear that all the "hot-fixes" are going in the complete wrong direction and you just add new issues. |
I don't need a quick fix but I think the fact that controls are running when the drone is supposed to be idling on ground is a potential safety issue and therefore should get resolved as soon as possible. The regression happened with #11056, so that's why I'm suggesting to just revert that. |
This seems not to work properly, so closing. |
@julianoes If it's blocking you from work on master just checkout this hotfix #11207 but I'd suggest we don't merge it but rather fix the AutoMapper2 to not produce any unexpected setpoints.
Not really. The bug was introduced with #10746 and #11056 just unveils it. |
I don't understand all the things that you guys are talking about but I would like to have the regression fixed and this change seems to do it.
Fixes #11197.
If we can't fix this quickly, then I'd suggest to revert #11056 for now.