Skip to content
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

Quad makes crazy jump after touched down #78

Open
kohlerj opened this issue Sep 12, 2018 · 3 comments
Open

Quad makes crazy jump after touched down #78

kohlerj opened this issue Sep 12, 2018 · 3 comments

Comments

@kohlerj
Copy link
Contributor

kohlerj commented Sep 12, 2018

@mfaessle Isn't it the source of this bounce back we discussed a few months ago

SOURCE

@mfaessle
Copy link
Contributor

I don't remember, can you elaborate a bit what symptoms we are dealing with here?

@kohlerj
Copy link
Contributor Author

kohlerj commented Sep 12, 2018

When you land with the snapdragon providing the state estimate, everything goes well until you touched down at which point the state estimate is lost. Here we see that whichever the states was, if the state estimate is regained then a "hover" control command is sent. If you're closed to the ground then it will jump up again. Is that more or less understandable ?

@mfaessle
Copy link
Contributor

I'm assuming that this is not necessarily related to touching the ground but what the state estimate is doing right after it was regained. It might be that the state estimate goes crazy for a bit after touching the ground and then being reinitialized, at least with the snapdragon. Since this is more of a conceptual thing on how one wants to treat this issue I'm proposing to following ideas:

  1. Introduce a flag whether we allow to autopilot to switch back to hover after the state estimate is lost and then regained. If it is not allowed, the quad would just finish the emergency landing and then switch off. (But I would not always impose this behavior since for e.g. a motion capture system it makes sense to go back to hover)
  2. Introduce a short timeout during which the quad is allowed to switch back to hover after the state estimate was lost and regained. This would allow to overcome short glitches as we might have with SVO which might be more desirable compared to the above solution.

Let me know what you think about those

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants