A real life example is the stabilisation of quadcopters ("drones" eugh I hate that word). Where instead of attempting to reach a location the target is to maintain a specific angle relative to the ground.
As always wikipedia is your friend http://en.wikipedia.org/wiki/PID_controller.
If the goal is to teach about PID controllers, then the demo could use a graph showing the parameters through time.
- how far the ball is from the target (P, proportional)
- how far the ball has been from the target over time (I, integrator), so if you are very far even after a long time you try to push harder
- how quickly is the ball approaching the target (D, derivator), i.e. if you're approaching quickly then you decrease the force, if you're approaching too slow then you increase the force
- A program controls the ball only via two thrusters (x/y), force represented as orange bars
- Program's goal is to deliver the ball to a given point (last click position)
There is a link in the footer: https://en.wikipedia.org/wiki/PID_controller which explains what's a PID controller in this case.
There are limitations of PID and what it can and cant be used for. There are also other ways of controlling systems (like state feedback).
I might have made some errors in the above statements because I haven't done control theory in a long time, but any control theory course at a university would cover PID control.
In relation to what the post is about, it seems like they've tuned a PID control loop to perform PID error calculations based on where you click and where the circle currently is, then move the circle to that position with a force (/acceleration) determined by the controller.
I've got an intake valve at work that we're controlling with P-only control, It basically iterates based on incremental voltage being proportional to current error in valve position.
Just trying to brush up on my lingo.
State-space representation is a strictly time domain approach, where you break your model and controller into a bunch of 1st degree DEs. This method is really only tractable with computing support.
In general, state-space and frequency domain models can in theory accomplish the same goals. You could for many situations design a PID controller using classical methods, and then take the same situation and use a state space approach, and in the end result in the equivalent controller/behavior.
While that's true, it's surprisingly effective and as a result is very widely used.
Yes, absolutely. It's less common but so are the people who can implement them.
http://en.wikipedia.org/wiki/Control_theory
I was surprised not to see Kalman listed in the people section. His contribution:
http://en.wikipedia.org/wiki/Kalman_filter
Turns out to be important sometimes - like when your sensors don't quite give you what you want. But when things get to that level, I call in a specialist to make sure it's done right - got one on speed dial, he does controls full time all the time.