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

Rate setpoint dropout during transition #12359

Closed
RomanBapst opened this issue Jun 28, 2019 · 5 comments
Closed

Rate setpoint dropout during transition #12359

RomanBapst opened this issue Jun 28, 2019 · 5 comments
Assignees
Labels
bug Hybrid VTOL 🛩️🚁 Multirotor + Fixedwing!

Comments

@RomanBapst
Copy link
Contributor

While flying a quadplane one v1.9 I noticed that there is always a 1 second gap in the vehicle_rates_setpoint topic at the beginning of the transition. Normally the fixed wing attitude controller should be publishing values. The rate controllers still seem to run.

image

In the figure above you can see the gap in the rate setpoint topic (top right).
At the beginning of the transition we switch from multicopter attitude controller to fixed wing attitude controller to produce the rate setpoint. However, i don't see the reason yet why it takes the fixed wing attitude controller 1 second to publish to the rates setpoint topic.

@dagar Any ideas?

Log: https://logs.px4.io/plot_app?log=5bca4650-96a8-4f92-8619-b9b1cadccf4a

@dagar
Copy link
Member

dagar commented Jul 1, 2019

I'm not sure, but I guess I'm not surprised given the complexity of the independent logic in each separate controller for coordinating which portion is running wrt vtol state and type.

I'm sure there's a whack-a-mole solution to the bug here if someone wants to temporarily get their head around all the current code and timing long enough to see the problem, but how about something architecturally simpler?

Currently we have fw_att_control and mc_att_control both containing attitude + rate controllers. What if we split these both into separate modules, and then turned vehicle_control_mode into an MC/FW virtual topic that the VTOL code could manipulate independently to control the transition behavior?

@dagar dagar added this to the Release v1.10.0 milestone Jul 1, 2019
@dagar
Copy link
Member

dagar commented Jul 1, 2019

Independent of the VTOL architecture I've already starting splitting mc_att_control. #12225

@RomanBapst
Copy link
Contributor Author

@sfuhrer I believe you fixed this lately. Can you confirm and close?

@sfuhrer
Copy link
Contributor

sfuhrer commented Sep 27, 2019

@sfuhrer I believe you fixed this lately. Can you confirm and close?

yes fixed

@sfuhrer sfuhrer closed this as completed Sep 27, 2019
@RomanBapst
Copy link
Contributor Author

@sfuhrer You the man! Thanks.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Hybrid VTOL 🛩️🚁 Multirotor + Fixedwing!
Projects
None yet
Development

No branches or pull requests

3 participants