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

ecl: attitude_fw update #9023

Merged
merged 2 commits into from
Mar 9, 2018
Merged

ecl: attitude_fw update #9023

merged 2 commits into from
Mar 9, 2018

Conversation

tstastny
Copy link

@tstastny tstastny commented Mar 5, 2018

  • move angular rate limits to body angular rates
  • handle rattitude/acro vs attitude mode rate limits

updates ecl submodule, see PX4/PX4-ECL#404.
see also PX4/PX4-ECL#402 for details.

(follow-up from #9017)

@tstastny
Copy link
Author

tstastny commented Mar 5, 2018

@dagar I initialized the _flag_control_attitude_enabled_last to false, and removed the setters from the param update function. however - i also added the params_updated bool to the reset limits condition, to make sure we catch scenarios where the mode does not change, but perhaps someone sets a new limit with a param update.

let me know if I've missed any other corner cases.

@dagar
Copy link
Member

dagar commented Mar 5, 2018

Did you update the submodule to point at the new branch in PX4/ecl?

@tstastny
Copy link
Author

tstastny commented Mar 5, 2018

Did you update the submodule to point at the new branch in PX4/ecl?

I believe so. I checked out PX4/ecl/pr-fw_att_lim_body_rates before amending the commit. The hash matches. I can try again though after rebase, unless you can think of something else I could have possibly done wrong.

- move angular rate limits to body angular rates
- handle rattitude/acro vs attitude mode rate limits
@dagar
Copy link
Member

dagar commented Mar 6, 2018

This looks good. Let's do a bit of testing (SITL is fine) that both exercises the full ecl/attitude_fw controllers and jumps back and forth between acro, rattitude, etc a few times.

@LorenzMeier
Copy link
Member

@tstastny Could you do the SITL testing and share a log here?

@tstastny
Copy link
Author

tstastny commented Mar 7, 2018

@tstastny Could you do the SITL testing and share a log here?

on my list for today - will upload this afternoon

@tstastny
Copy link
Author

tstastny commented Mar 7, 2018

See SITL logs with various modes switching back and forth and giving full rates.

https://review.px4.io/plot_app?log=5b1b0e2a-64b2-4220-87f9-fc5fbee91392

Rattitude and Acro modes allow the acro max rates, while Stabilized and Altitude modes allows only the stabilized max rates. A little harder to see the Rattitude threshold effects (I was not so good at flying this blind.. hard to see the plane in Gazebo). But I definitely saw the difference when passing the 80% threshold that was set.

@dagar
Copy link
Member

dagar commented Mar 9, 2018

Colourful testflight!

image

dagar
dagar previously approved these changes Mar 9, 2018
@dagar
Copy link
Member

dagar commented Mar 9, 2018

ECL side merged, I'm going to add a commit to this PR that updates ECL, then squash them together on merge.

@dagar dagar merged commit 7473027 into master Mar 9, 2018
@dagar dagar deleted the pr-fw_att_lim_body_rates branch March 9, 2018 03:55
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants