Good video bro. I used these equations on a Arduino last year, made several PIDs to control the illumination of desks in a Lab. Controlled light dimming, fans of the lights, distance sensors(to check if there is someone in the desk). Really nice video man.
If the P gain is to high (~2:40), it will oscillate, but it will be above and below the set point, not under it. At 7:45 your two bottom tables are not correct, the reset register would not be that high when the error is small and the P is way to high when there is little or no error left. Thanks for the video. Watch the Motec PID videos, they are pretty good, but long.
Thanks the pseudo code really helps to clarify it in my (4 function) mind :-) Pity about the sound quality - as an ex-sound engineer, I suggest you use a pop-shield between you and the mic (this could be as simple a a piece of ladies stocking stretched over a wire loop ) it'll stop the popping sound as you pronounce the 'P's and 'B's and allow the recording level to be higher.
Well done! However, I quibble with this idea that gain is "unitless." I disagree. For instance, if the input is measured in miles per hour, and the output is measured in degrees, then change in output over change in input is measured in degrees per mph, or equivalently, degree-hours per mile, so the gain would be measured in degree-hours per mile. You could say that degree is not a physical unit, which is fine, but then you're still left with hours per mile.
Great video; good refresher for me. You confused me a little at the end there when you drew projections of the speed's slope and called it the error slope. Might be helpful to include an error plot to show how the error derivative imparts a negative effect on the controller output. Thanks for the lesson Scott!
Im still not understanding tau i when applied to code. Is it the change in time bewtween each cycle? or is it a cycle that adds up time until it equals 5 seconds or something?
Great Video. I'm a VEX Robotics Programmer so this has been really useful to me! Thanks - if you could do one that shows me how to implement PID Control into RobotC or EasyC it would be fantastic.
Very helpful, but still seems like rocket science to me. More time to play around will help cement this in my aged brain, and control this F****** stabilized camera head
People like you are awesome, thanks for taking the time to explain such a difficult concept in a simple way!
Good video bro. I used these equations on a Arduino last year, made several PIDs to control the illumination of desks in a Lab. Controlled light dimming, fans of the lights, distance sensors(to check if there is someone in the desk).
Really nice video man.
Great video, wish there was a visual representation of PID together
If the P gain is to high (~2:40), it will oscillate, but it will be above and below the set point, not under it. At 7:45 your two bottom tables are not correct, the reset register would not be that high when the error is small and the P is way to high when there is little or no error left. Thanks for the video. Watch the Motec PID videos, they are pretty good, but long.
Well done! Thank you for describing PID parameters in a way we can understand intuitively.
Thanks the pseudo code really helps to clarify it in my (4 function) mind :-)
Pity about the sound quality - as an ex-sound engineer, I suggest you use a pop-shield between you and the mic (this could be as simple a a piece of ladies stocking stretched over a wire loop ) it'll stop the popping sound as you pronounce the 'P's and 'B's and allow the recording level to be higher.
Great video!
Some people will complain about anything; I don't understand how anyone could dislike this...
Much better explanation than I got from the head of mech eng department at uni. :P
I struggled so hard with the integral part. You made it look so simple! Thanks mate! :)
Well done! However, I quibble with this idea that gain is "unitless." I disagree. For instance, if the input is measured in miles per hour, and the output is measured in degrees, then change in output over change in input is measured in degrees per mph, or equivalently, degree-hours per mile, so the gain would be measured in degree-hours per mile. You could say that degree is not a physical unit, which is fine, but then you're still left with hours per mile.
Really quite excellent. Not for a total beginner, but good for someone who is relatively new to PID loops.
Great video; good refresher for me. You confused me a little at the end there when you drew projections of the speed's slope and called it the error slope. Might be helpful to include an error plot to show how the error derivative imparts a negative effect on the controller output. Thanks for the lesson Scott!
Nice Video! I appreciate it. This makes the theory much more clear.
Im still not understanding tau i when applied to code. Is it the change in time bewtween each cycle? or is it a cycle that adds up time until it equals 5 seconds or something?
Thank you so much, this is superb....
awesomeness for the beginner... really im so thankful to you
Is simple but I think is a good explanation! I hope you keep doing videos about it.
Amazing!! Great graphical interpretation....
Excellent video! Thanks for it.
Fantastic explanation and video -- this helped so much -- thank you!!
Terrific video, thanks very much for making it!
mind blown ! thank you for the excellent video
Such a good explanation thank you so much
I've been struggling in understanding such conccept but after this videooo I really would love to thank you a lottt :D
Great video. Easy to understand! Thanks!
This is awesome thank you so much!
Great Video.
I'm a VEX Robotics Programmer so this has been really useful to me!
Thanks - if you could do one that shows me how to implement PID Control into RobotC or EasyC it would be fantastic.
Thank you for sharing you knowledge!
Thank you !
I love you !
good stuff...the units for the I and D can still be slower and clearer
Great job, this really helped thanks!!
great explaining thank you
Very nice explanation.
great explanation, thanks.
Excellente!
For the PD control you start out using tau_d but change to tau_i. Is this a typo?
very well explained
Did you say demystified?
helps me a lot
Superb!
Thank you so much !!!
nice one mate thanks
Thanks a bunch!
good job !!
Man Ur amazing :)
love it
very good
nice presentation :) thank you.. :) i thing u made ur voice lesser, next time pls pls use your own voice... its sometime irritating..
Very helpful, but still seems like rocket science to me. More time to play around will help cement this in my aged brain, and control this F****** stabilized camera head
Thanks
very usefull
THNX
Thnx to whom?
THNX to myself for watching this video. ;)
Too fast
Thanks