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

VTOL standard: introduce scale for FW control surfaces in hover #12946

Closed
wants to merge 1 commit into from

Conversation

sfuhrer
Copy link
Contributor

@sfuhrer sfuhrer commented Sep 11, 2019

For VTOL in hover, if VT_ELEV_MC_LOCK is set to disabled, the FW control surfaces support the MC motors to control the rates/attitude. The FW control surfaces are controlled over the FW rate controller, which also runs in hover. The tuning of them is thus the same as in FW flight (except some scaling with airspeed, if available).

This PR introduces additional tuning scales for the control surfaces in hover. Both pitch and roll have an additional gain to tune the allocation of FW rate controller output to FW control surface deflection.

Note: other than first planned this PR does not change the subscription of the control surfaces from FW to MC rate controller. This mainly to make the control loops less entangled/ make the architecture simpler.

@sfuhrer sfuhrer requested a review from RomanBapst September 11, 2019 14:14
@sfuhrer sfuhrer changed the title VTOL standard: FW control surfaces listen to MC att C in hover VTOL standard: FW control surfaces subscribe to MC rate controller in hover Sep 11, 2019
…rfaces in hover

Signed-off-by: Silvan Fuhrer <silvan@auterion.com>
@sfuhrer sfuhrer force-pushed the VTOL_FW_actuators_control_allocation branch from a86992f to 595d1c4 Compare September 16, 2019 13:10
@sfuhrer sfuhrer changed the title VTOL standard: FW control surfaces subscribe to MC rate controller in hover VTOL standard: introduce scale for FW control surfaces in hover Sep 17, 2019
@stale
Copy link

stale bot commented Dec 16, 2019

This issue has been automatically marked as stale because it has not had recent activity. Thank you for your contributions.

@stale
Copy link

stale bot commented Mar 15, 2020

This issue has been automatically marked as stale because it has not had recent activity. Thank you for your contributions.

@stale stale bot added the stale label Mar 15, 2020
@sfuhrer
Copy link
Contributor Author

sfuhrer commented May 13, 2020

Close in favor of #14894

@sfuhrer sfuhrer closed this May 13, 2020
@LorenzMeier LorenzMeier deleted the VTOL_FW_actuators_control_allocation branch January 18, 2021 14:33
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant