Calculation error about arduino-pid-library HOT 7 CLOSED

yes, the variables are possibly not named correctly, but the algo is OK. Every now and then someone stumbles upon this. have a look at #28 (and maybe #23).

from arduino-pid-library.

Please see here: http://brettbeauregard.com/blog/2011/04/improving-the-beginner%e2%80%99s-pid-derivative-kick/

from arduino-pid-library.

@split it's named dInput, not dEer. How would you suggest the variable be named?

from arduino-pid-library.

@split=>@isplitt (on my phone)

from arduino-pid-library.

maybe just call it "dNOTErr" :-)
I think it's ok how it is, but it still confuses some people from time to time.
Another solution could be to spend this one OP and tranform it to dErr (like mentioned in #23)

from arduino-pid-library.

Hi,

Thanks for quick reply. You are right, dError and dInput aren't same. As I understood, this optimisation cause that the derivative component responds only to a distortion of the controlled object but does not responds when the setpoint change. Sometimes it could be useful, I have to test it in my project. It is good to know how the controller works. Have you thought about add an option to customize this behaviour?

Cheers.

from arduino-pid-library.

It would be very easy to customize it's true, but I have yet to find a
situation where the kick is beneficial. This isn't to say there isn't one,
just that I have never seen it. (And I've seen a LOT of loops)
On Oct 20, 2015 7:05 AM, "rtlopez" [email protected] wrote:

Hi,

Thanks for quick reply. You are right, dError and dInput aren't same. As I
understood, this optimisation cause that the derivative component responds
only to a distortion of the controlled object but does not responds when
the setpoint change. Sometimes it could be useful, I have to test it in my
project. It is good to know how the controller works. Have you thought
about add an option to customize this behaviour?

Cheers.

—
Reply to this email directly or view it on GitHub
#31 (comment)
.

from arduino-pid-library.