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

mc_att_control_main: do not apply the yaw weight for the feedforward term #9360

Merged
merged 2 commits into from
Apr 25, 2018

Conversation

bkueng
Copy link
Member

@bkueng bkueng commented Apr 23, 2018

The meaning of the yaw weight changed with #8003:

  • before, the yaw weight decreased with increasing tilt angle error, so it was mostly 1
  • now, it is constant and depends on the tuning gains (around 0.4 by default)

It means that #8003 reduced the feedforward term, and we get the closer behavior as before with this change.
It also reduces coupling between different parameters.

This PR fixes a mixer initialization as well.

memset (http://www.cplusplus.com/reference/cstring/memset/) interprets
the value argument as unsigned char, so passing a float will not work.
…term

The meaning of the yaw weight changed with #8003:
- before, the yaw weight decreased with increasing tilt angle error, so
  it was mostly 1
- now, it is constant and depends on the tuning gains (around 0.4 by default)

It means that #8003 reduced the feedforward term, and we get the closer
behavior as before with this change.
It also reduces coupling between different parameters.
@bkueng bkueng requested a review from MaEtUgR April 23, 2018 14:02
@LorenzMeier LorenzMeier merged commit 332a612 into master Apr 25, 2018
@mhkabir mhkabir deleted the att_controller_fixes branch April 25, 2018 19:13
@MaEtUgR
Copy link
Member

MaEtUgR commented May 2, 2018

Makes sense, that weight was only kept because it was there before but your resoning is correct and we're better off without.

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

Successfully merging this pull request may close these issues.

3 participants