Bruce Abbott (2014.12.19.1330)
Warren Mansell –
WM: Thanks Bruce! That starts to make a lot of sense, and also explains why things can get messy when I have talked to control engineers before, and also maybe explain why control theory applications to living systems got off to a difficult start with cybernetics? I will certainly watch further - sorry for my false start - as I do want to be able to communicate with real control system engineers - there are many here at the university I could be collaborating with. I am wondering though whether the human controller in the example you mention actually has a hierarchical relationship with the rheostat in controlling its reference value rather than making it open loop?
Warren
You’re welcome! As for your question, the “open-loop” controller (the rheostat) is not a negative feedback control system, so you wouldn’t really have a two-level hierarchical control system, since the bottom-level “controller” doesn’t have a comparator or feedback loop of its own. You can think of the rheostat as establishing the environmental feedback function between the operator’s output (rheostat dial setting) and the torque being generated by the motor. The torque and disturbance (load on the motor) together determine the value of the operator’s controlled variable, the motor speed.
The operator’s output function could be unpacked further as a lower-level control system whose reference is the torque to be generated by the operator’s hand on the rheostat’s knob. The reference level would be proportional to the error in perceived motor speed. The torque generated by this system would move the rheostat knob until the operator’s perceived speed of the motor matched the operator’s reference for motor speed. This more complete model of the human operator is a two-level hierarchical control system, but the rheostat is still just a device out in the operator’s environment that determines (in open-loop fashion) the relationship between rheostat dial setting and motor torque.
Bruce
p.s. The “hand-torque” lower-level system can itself be elaborated to include a yet lower-level system that sets the references for the force being generated by the muscles of the hand and arm which together produce the torque exerted on the rheostat knob. Now we’re up to a three-level hierarchy! But for most purposes we don’t need to model every level. If we assume that the lower-level control systems are doing their jobs well, we can just hide them in the person’s output function, since whatever actions the higher-level system calls far will be produced with a reasonable degree of accuracy by the lower systems. In our example, the rheostat knob will get turned (the operator’s output action) as needed to bring the motor speed to the operator’s reference motor speed.
Bruce Abbott (2014.12.19 1020 EST)
Warren Mansell –
WM: Hi Bruce, I switched off after the first minute. Surely, from a PCT perspective, stability cannot be defined as the capacity to restore to an output of zero? Stability within PCT relies of a flexibly changing output to ensure that the INPUT remains as close as possible to the reference value for that input? My mood is stable not because I do nothing to change it but because it remains around a range I want it to be because of, and/or despite of, my behaviour?
Warren
I agree that Douglas’ way of defining stability is unfortunate. The problem you note arises partly because he is thinking of zero as the initial value (before the system is disturbed), but doesn’t mention that explicitly. A stable system will settle to (that same) zero after being disturbed. Also contributing to the problem is that Douglas is an control systems engineer and is using an engineer’s definitions of the various quantities. The output in a standard engineering diagram of a control system is what we would label the input. For example, the output of a voltage regulator is the regulated voltage. If the reference for the voltage is +5 Volts, then the regulated output should be as close as possible to + 5 Volts.
So when Douglas asserts that in a stable system, the output goes to zero, he is not saying that the actions go to zero, but that the variable is returning to its initial state.
So, what Douglas actually is asserting is that, in a stable system, after being disturbed the variable in question will settle back to its initial value.
If you continue watching the video, you will see an illustration in the form of a ball in a valley. Its “zero” is at the bottom center of the valley. If you disturb the ball (push it uphill and release) it will eventually come to rest back at zero (assuming there’s some energy loss due to friction of viscous damping). One could define the ball’s initial position as “3 inches from the left edge of the bowl.” In that case stability would be present if the ball eventually settled at 3 inches.
It’s important to note that Douglas does recognize that what is controlled in a control system is the system’s perception of the controlled variable. In the video, Robotic Car, Closed Loop Control Example, Douglas uses a simple tracked vehicle to illustrate the difference between open-loop and closed-loop control. The open-loop version can be aimed at a particular target location and will drive there so long as there are no disturbances. But when disturbances act to turn the car, the car does not reach the target. The closed-loop version has an accelerometer that senses the angular acceleration of the car in the horizontal plane. Beginning at 8:00 minutes into the video, Douglas diagrams the system. The output on his diagram is the actual angular acceleration of the car, but Douglas notes that the only thing the control system knows about the car’s angular acceleration is the sensed value provided by the accelerometer.
In engineering, the term “control” is used in a looser sense than we use the term in PCT. A motor “controller,” for example, may consist of a simple rheostat that varies the current flow to the motor. The rheostat is said to “control” the motor speed (in the sense of being an important factor determining that speed). In the absence of any disturbances to the motor’s speed, one could make up a table or formula giving the motor’s speed for any given position of the rheostat’s dial. Such a system may be described as employing “open-loop control.” It has no ability to counteract disturbances, so a load on the motor will slow it down below the rpm given in the table.
In the diagram of this system, there’s a reference (dial setting) the inputs to the “controller” and an output, the motor’s actual speed. To convert this system to closed-loop control, you read this output with a sensor and feed the sensor’s reading (after a change in sign to negative) into a comparator. The reference moves to the comparator and the output of the comparator, the error signal, now becomes the input to the “controller.”
So-called open-loop controllers are used by human beings, who may observe the actual output and adjust the reference (e.g., the rheostat’s dial setting) to compensate for any error between what the operator wanted and that the system is actually delivering. In so doing, the operator closes the loop. The term open-loop “controller” is called a controller because it allows the human operator the means to control the variable in question (e.g., motor speed). I think it makes sense in that context. In PCT, of course, we prefer to restrict the term “control” to systems that compare the actual state of affairs to the desired one and take action to reduce or eliminate any difference between them.
It’s important to understand these differences in terminology (and worth the effort to learn them) so that we are not led into believing that engineers are talking nonsense about control systems when in fact they are just using somewhat different terminology and diagrams than we use in PCT when saying the same thing.
Bruce
Bruce Abbott (2014.12.18 1940 EST)
BA: For those of you who would like to learn more about the classical approach to control systems, I highly recommend a series of YouTube videos presented by control systems engineer Brian Douglas (http://www.youtube.com/user/ControlLectures/videos ). The lectures range from basic concepts to sophisticated techniques used in control system design, analysis, and tuning, so whether you are a control systems neophyte or an engineer who needs a bit of brushing up on these techniques, you will find something worthwhile to view.
BA: Douglas is an engaging and talented teacher who is able to communicate complex ideas clearly. A nice place to start is with Douglas’ lecture, “introduction to system stability and control” (http://www.youtube.com/watch?v=uqjKG32AkC4). Another is the lecture ”examples of PID control (http://www.youtube.com/watch?v=XfAt6hNV8XM). Once you have watched