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
Integrator Windup #34
Comments
Are you thinking of this as an opt-in behavior, or as an always-in addition?. |
Opt-in |
OK, if you can prepare a pull-request we can review it. So there would be a boolean parameter for toggling the anti-windup behavior?. |
I think that would make sense, yes. |
Seeing that #52 has been merged, should this be closed? Did you change the API of (Yeah, I know I'm about six weeks late ;-) ) |
Thanks @ipa-mig, it would have made perfect sense to modify initPid the same way. |
@paulbovbel will this be done for others not stumbling upon the same? (Even though I actually appreciate having a proper antiwindup and would have probably not found this change without the build error :-) ) |
I'm totally open to it, although @bmagyar would be the one to ask. Would you be able to put up a PR? |
Even though
i_term
is clamped toi_max
,i_error
will continue to windup as long as there's an error. I've found this troublesome in an application with quadrotor control, where I'm trying to migrate the bespoke PID methods to the control_toolbox ones.Would you be open to a pull adding a "antiwindup" parameter to enable clamping
i_error
byi_max/i_gain_
?The text was updated successfully, but these errors were encountered: