Scaling and parameterizing a controller

Abstract

Controller scaling and parameterization are described. Techniques that can be improved by employing the scaling and parameterization include, but are not limited to, controller design, tuning and optimization. The scaling and parameterization methods described here apply to transfer function based controllers, including PID controllers. The parameterization methods also applies to state feedback and state observer based controllers, as well as linear active disturbance rejection controllers.

Description

TECHNICAL FIELD

[0002] The systems, methods, application programming interfaces (API), graphical user interfaces (GUI), computer readable media, and so on described herein relate generally to controllers and more particularly to scaling and parameterizing controllers, which facilitates improving controller design, tuning, and optimizing.

BACKGROUND

[0003] A feedback (closed-loop) control system 100, as shown in Prior Art FIG. 1, is widely used to modify the behavior of a physical process, denoted as the plant 110, so it behaves in a specific desirable way over time. For example, it may be desirable to maintain the speed of a car on a highway as close as possible to 60 miles per hour in spite of possible hills or adverse wind; or it may be desirable to have an aircraft follow a desired altitude, heading and velocity profile independently of wind gusts; or it may be desirable to have the temperature and pressure in a reactor vessel in a chemical process plant maintained at desired levels. All these are being accomplished today by using feedback control, and the above are examples of what automatic control systems are designed to do, without human intervention.

[0004] The key component in a feedback control system is the controller 120, which determines the difference between the output of the plant 110, (e.g., the temperature) and its desired value and produces a corresponding control signal u (e.g., turning a heater on or off). The goal of controller design is usually to make this difference as small as possible as soon as possible. Today, controllers are employed in a large number of industrial control applications and in areas like robotics, aeronautics, astronautics, motors, motion control, thermal control, and so on.

[0005] Classic Controllers:

[0006] Classic Control Theory provides a number of techniques an engineer can use in controller design. Existing controllers for linear, time invariant, and single-input single output plants can be categorized into three forms: the proportional/integral/derivative (PID) controllers, transfer function based (TFB) controllers, and state feedback (SF) controllers. The PID controller is defined by the equation 1$\begin{array}{cc}u=K_{p}e+K_I\int e+K_D\stackrel{.}{e}& \left(1\right)\end{array}$

[0007] where u is the control signal and e is the error between the setpoint and the process output being controlled. This type of controller has been employed in engineering and other applications since the early 1920s. It is an error based controller that does not require an explicit mathematical model of the plant. The TFB controller is given in the form of 2$\begin{array}{cc}U\left(s\right)=G_c\left(s\right)E\left(s\right),G_c\left(s\right)=\frac{n\left(s\right)}{d\left(s\right)}& \left(2\right)\end{array}$

[0008] where U(s) and E(s) are Laplace Transforms of u and e defined above, and n(s) and d(s) are polynomials in s. The TFB controller can be designed using methods in control theory based on the transfer function model of the plant, Gp(s). A PID controller can be considered a special case of a TFB controller because it has an equivalent transfer function of 3$\begin{array}{cc}{G}_c\left(s\right)=k_p+\frac{k_i}{s}+k_{d}s& \left(3\right)\end{array}$

[0009] The State Feedback (SF) Controller

[0010] The SF controller can be defined by

u=r+K{circumflex over (x)}   (4)

[0011] and is based on the state space model of the plant:

{dot over (x)} (t)=Ax(t)+Bu(t), y(t)=Cx(t)+Du(t)  (5)

[0012] When the state x is not accessible, a state observer (SO):

{circumflex over ({dot over (x)})}=A{circumflex over (x)}+Bu+L (y−ŷ)  (6)

[0013] is often used to find its estimate, {circumflex over (x)}. Here r is the setpoint for the output to follow.

[0014] In addition to the above controllers, a more practical controller is the recently developed Active Disturbance Rejection Controller (ADRC). Its linear form (LADRC) for a second order plant is introduced below as an illustration. The unique distinction of ADRC is that it is largely independent of the mathematical model of the plant and is therefore better than most controllers in performance and robustness in practical applications.

[0015] Linear Activated Disturbance Rejection Controller (LADRC)

[0016] Consider an example of controlling a second order plant

ÿ=−a{dot over (y)}−by+w+bu   (7)

[0017] where y and u are output and input, respectively, and w is an input disturbance. Here both parameters, a and b, are unknown, although there is some knowledge of b, (e.g., b0≈b, derived from the initial acceleration of y in step response). Rewrite (7) as

ÿ=−a{dot over (y)}−by+w+ (b−b0)u+b0u=f+b0u  (8)

[0018] where f=−a{dot over (y)}−by+w+(b−b0)u. Here f is referred to as the generalized disturbance, or disturbance, because it represents both the unknown internal dynamics, −a{dot over (y)}−by+(b−b0)u and the external disturbance w(t).

[0019] If an estimate of f, {circumflex over (f)} can be obtained, then the control law 4$u=\frac{-\hat{f}+u_0}{b_0}$

[0020] reduces the plant to ÿ=(f−{circumflex over (f)})+u0 which is a unit-gain double integrator control problem with a disturbance (f−{circumflex over (f)}).

[0021] Thus, rewrite the plant in (8) in state space form as 5$\begin{array}{cc}\{\begin{array}{c}{\stackrel{.}{x}}_1=x_2\\ {\stackrel{.}{x}}_2=x_3+b_{0}u\\ {\stackrel{.}{x}}_3=h\\ y=x_1\end{array}& \left(9\right)\end{array}$

[0022] with x3=f added as an augmented state, and h={dot over (f)} is seen as an unknown disturbance. Now f can be estimated using a state observer based on the state space model 6$\begin{array}{cc}\stackrel{.}{x}=\mathrm{Ax}+\mathrm{Bu}+\mathrm{Eh}y=\mathrm{Cz}\mathrm{where}A=\left[\begin{array}{ccc}0& 1& 0\\ 0& 0& 1\\ 0& 0& 0\end{array}\right],B=\left[\begin{array}{c}0\\ b_0\\ 0\end{array}\right].C=\left[100\right],E=\left[\begin{array}{c}0\\ 0\\ 1\end{array}\right]& \left(10\right)\end{array}$

[0023] Now the state space observer, denoted as the linear extended state observer (LESO), of (10) can be constructed as

{dot over (z)}=Az+Bu+L (y−ŷ)

ŷ=Cz   (11)

[0024] which can be reconstructed in software, for example, and L is the observer gain vector, which can be obtained using various methods known in the art like pole placement,

L=[β 1 β2β3]T  (12)

[0025] where [ ]T denotes transpose. With the given state observer, the control law can be given as: 7$\begin{array}{cc}u=\frac{-z_3+u_0}{b_0}& \left(13\right)\end{array}$

[0026] Ignoring the inaccuracy of the observer,

ÿ =(f−z3)+u0≈u0  (14)

[0027] which is an unit gain double integrator that can be implemented with a PD controller

u 0 =k p (r−z1)−kdz2  (15)

[0028] Controller Tuning

[0029] Over the years, the advances in control theory provided a number of useful analysis and design tools. As a result, controller design moved from empirical methods (e.g., ad hoc tuning via Ziegler and Nichols tuning tables for PID) to analytical methods (e.g., pole placement). The frequency response method (Bode and Nyquist plots) also facilitated analytical control design.

[0030] Conventionally, controllers are individually designed according to design criteria and then individually tuned until they exhibit an acceptable performance. Practicing engineers may design controllers, (e.g., PID) using look-up tables and then tune the controllers using trial and error techniques. But each controller is typically individually designed, tuned, and tested.

[0031] Tuning controllers has perplexed engineers. Controllers that are developed based on a mathematical model of the plant usually need their parameters to be adjusted, or “tuned” as they are implemented in hardware and tested. This is because the mathematical model often does not accurately reflect the dynamics of the plant. Determining appropriate control parameters under such circumstances is often problematic, leading to control solutions that are functional but ill-tuned, yielding lost performance and wasted control energy. Additionally, and/or alternatively, engineers design using analytical (e.g., pole placement) techniques, but once again tune with trial and error techniques. Since many industrial machines and engineering applications are built to be inherently stable, acceptable controllers can be designed and tuned using these conventional techniques, however, acceptable performance may not approach optimal performance.

[0032] One example conventional technique for designing a PID controller included obtaining an open-loop response and determining what, if anything, needed to be improved. By way of illustration, the designer would build a candidate system with a feedback loop, guess the initial values of the three gains (e.g., kp, kd, ki) in PID and observe the performance in terms of rise time, steady state error and so on. Then, the designer might modify the proportional gain to improve rise time. Similarly, the designer might add or modify a derivative controller to improve overshoot and an integral controller to eliminate steady state error. Each component would have its own gain that would be individually tuned. Thus, conventional designers often faced choosing three components in a PID controller and individually tuning each component. Furthermore, there could be many more parameters that the design engineer must tune if a TFB or a state feedback state observer (SFSOB) controller is employed.

[0033] Another observation of control design is that it is not portable. That is, each control problem is solved individually and its solution cannot be easily modified for another control problem. This means that the tedious design and tuning process must be repeated for each control problem.

[0034] Thus, having reviewed controllers, the application now describes example systems and methods related to controllers.

SUMMARY

[0035] This section presents a simplified summary of methods, systems, computer readable media and so on for scaling and parameterizing controllers to facilitate providing a basic understanding of these items. This summary is not an extensive overview and is not intended to identify key or critical elements of the methods, systems, computer readable media, and so on or to delineate the scope of these items. This summary provides a conceptual introduction in a simplified form as a prelude to the more detailed description that is presented later.

[0036] The application describes scaling and parameterizing controllers. With these two techniques, controller designing, tuning, and optimizing can be improved. In one example, systems, methods, and so on described herein facilitate reusing a controller design by scaling a controller from one application to another. This scaling may be available, for example, for applications whose plant differences can be detailed through frequency scale and/or gain scale. While PID controllers are used as examples, it is to be appreciated that other controllers can benefit from scaling and parameterizing as described herein.

[0037] Those familiar with filter design understand that filters may be designed and then scaled for use in analogous applications. Filter designers are versed in the concept of the unit filter which facilitates scaling filters. In example controller scaling techniques, a plant transfer function is first reduced to a unit gain and unit bandwidth (UGUB) form. Then, a known controller for an appropriate UGUB plant is scaled for an analogous plant. Since certain plants share certain characteristics, classes of UGUB plants can be designed for which corresponding classes of scaleable, parameterizable controllers can be designed.

[0038] Since certain classes of plants have similar properties, it is possible to frequency scale controllers within classes. For example, an anti-lock brake plant for a passenger car that weighs 2000 pounds may share a number of characteristics with an anti-lock brake plant for a passenger car that weighs 2500 pounds. Thus, if a UGUB plant can be designed for this class of cars, then a frequency scaleable controller can also be designed for the class of plants. Then, once a controller has been selected and engineered for a member of the class (e.g., the 2000 pound car), it becomes a known controller from which other analogous controllers can be designed for other similar cars (e.g., the 2500 pound car) using frequency scaling.

[0039] This scaling method makes a controller “portable”. That is a single controller can be used as the “seed” to generate controllers for a large number of different plants that are similar in nature. The remaining question concerns how to account for differences in design requirements. Controller parameterization addresses this issue. The example parameterization techniques described herein make controller coefficients functions of a single design parameter, namely the crossover frequency (also known as the bandwidth). In doing so, the controller can be tuned for different design requirements, which is primarily reflected in the bandwidth requirement.

[0040] The combination of scaling and parameterization methods means that an existing controller (including PID, TFB, and SFSOB) can be scaled for different plants and then, through the adjustment of one parameter, changed to meet different performance requirements that are unique in different applications.

[0041] Certain illustrative example methods, systems, computer readable media and so on are described herein in connection with the following description and the annexed drawings. These examples are indicative, however, of but a few of the various ways in which the principles of the methods, systems, computer readable media and so on may be employed and thus are intended to be inclusive of equivalents. Other advantages and novel features may become apparent from the following detailed description when considered in conjunction with the drawings.

BRIEF DESCRIPTION OF THE DRAWINGS

[0042] Prior Art FIG. 1 illustrates the configuration of an output feedback control system.

[0043] FIG. 2 illustrates a feedback control configuration.

[0044] FIG. 3 illustrates an example controller production system.

[0045] FIG. 4 illustrates an example controller scaling method.

[0046] FIG. 5 illustrates an example controller scaling method.

[0047] FIG. 6 compares controller responses.

[0048] FIG. 7 illustrates loop shaping.

[0049] FIG. 8 illustrates a closed loop simulator setup.

[0050] FIG. 9 compares step responses.

[0051] FIG. 10 illustrates transient profile effects.

[0052] FIG. 11 compares PD and LADRC controllers.

[0053] FIG. 12 illustrates LESO performance.

[0054] FIG. 13 is a flowchart of an example design method.

[0055] FIG. 14 is a schematic block diagram of an example computing environment.

[0056] FIG. 15 illustrates a data packet.

[0057] FIG. 16 illustrates sub-fields within a data packet.

[0058] FIG. 17 illustrates an API.

[0059] FIG. 18 illustrates an example observer based system.

Lexicon

[0060] As used in this application, the term “computer component” refers to a computer-related entity, either hardware, firmware, software, a combination thereof, or software in execution. For example, a computer component can be, but is not limited to being, a process running on a processor, a processor, an object, an executable, a thread of execution, a program and a computer. By way of illustration, both an application running on a server and the server can be computer components. One or more computer components can reside within a process and/or thread of execution and a computer component can be localized on one computer and/or distributed between two or more computers.

[0061] “Computer communications”, as used herein, refers to a communication between two or more computers and can be, for example, a network transfer, a file transfer, an applet transfer, an email, a hypertext transfer protocol (HTTP) message, a datagram, an object transfer, a binary large object (BLOB) transfer, and so on. A computer communication can occur across, for example, a wireless system (e.g., IEEE 802.11), an Ethernet system (e.g., IEEE 802.3), a token ring system (e.g., IEEE 802.5), a local area network (LAN), a wide area network (WAN), a point-to-point system, a circuit switching system, a packet switching system, and so on.

[0062] “Logic”, as used herein, includes but is not limited to hardware, firmware, software and/or combinations of each to perform a function(s) or an action(s). For example, based on a desired application or needs, logic may include a software controlled microprocessor, discrete logic such as an application specific integrated circuit (ASIC), or other programmed logic device. Logic may also be fully embodied as software.

[0063] An “operable connection” is one in which signals and/or actual communication flow and/or logical communication flow may be sent and/or received. Usually, an operable connection includes a physical interface, an electrical interface, and/or a data interface, but it is to be noted that an operable connection may consist of differing combinations of these or other types of connections sufficient to allow operable control.

[0064] “Signal”, as used herein, includes but is not limited to one or more electrical or optical signals, analog or digital, one or more computer instructions, a bit or bit stream, or the like.

[0065] “Software”, as used herein, includes but is not limited to, one or more computer readable and/or executable instructions that cause a computer or other electronic device to perform functions, actions and/or behave in a desired manner. The instructions may be embodied in various forms like routines, algorithms, modules, methods, threads, and/or programs. Software may also be implemented in a variety of executable and/or loadable forms including, but not limited to, a stand-alone program, a function call (local and/or remote), a servelet, an applet, instructions stored in a memory, part of an operating system or browser, and the like. It is to be appreciated that the computer readable and/or executable instructions can be located in one computer component and/or distributed between two or more communicating, co-operating, and/or parallel processing computer components and thus can be loaded and/or executed in serial, parallel, massively parallel and other manners. It will be appreciated by-one of ordinary skill in the art that the form of software may be dependent on, for example, requirements of a desired application, the environment in which it runs, and/or the desires of a designer/programmer or the like.

[0066] “Data store”, as used herein, refers to a physical and/or logical entity that can store data. A data store may be, for example, a database, a table, a file, a list, a queue, a heap, and so on. A data store may reside in one logical and/or physical entity and/or may be distributed between two or more logical and/or physical entities.

[0067] To the extent that the term “includes” is employed in the detailed description or the claims, it is intended to be inclusive in a manner similar to the term “comprising” as that term is interpreted when employed as a transitional word in a claim.

[0068] To the extent that the term “or” is employed in the claims (e.g., A or B) it is intended to mean “A or B or both”. When the author intends to indicate “only A or B but not both”, then the author will employ the term “A or B but not both”. Thus, use of the term “or” in the claims is the inclusive, and not the exclusive, use. See BRYAN A. GARNER, A DICTIONARY OF MODERN LEGAL USAGE 624 (2d Ed. 1995).

DETAILED DESCRIPTION

[0069] Example methods, systems, computer media, and so on are now described with reference to the drawings, where like reference numerals are used to refer to like elements throughout. In the following description for purposes of explanation, numerous specific details are set forth in order to facilitate thoroughly understanding the methods, systems, computer readable media, and so on. It may be evident, however, that the methods, systems and so on can be practiced without these specific details. In other instances, well-known structures and devices are shown in block diagram form in order to simplify description.

[0070] Scaling:

[0071] Controllers typically are not scalable and thus are not portable between applications. However, controllers can be made portable via scaling as described in the example systems and methods provided herein. In general, a plant mathematically represented by a transfer function Gp(s), (where s is the Laplace Transform variable) can be scaled according to:

{overscore (G)}p(s)=kGp(s/ωp)  (16)

[0072] where ωp is the plant frequency scale and k is the gain scale, to represent a large number of plants that differ from the original plant by a frequency scale, ωp, and a gain scale, k.

[0073] Then, a corresponding controller Gc(s) for the plant Gp(s) can be scaled according to:

G c (s)=(1/k)Gc(s/ωp).  (17)

[0074] Consider a unit feedback control system 200 with the plant Gp(s) 210 and controller Gc(s) 220, as shown in FIG. 2. Assume that Gc(s) 220 was designed with desired command following, disturbance rejection, noise rejection, and stability robustness. Now, consider a similar class of plants kGp(s/ωp). For given ωp, using example systems and methods described herein, a suitable controller can be produced through frequency scaling. Thus define ωp as the frequency scale and k as the gain scale of the plant Gp(s/ωp) with respect to

Gp(s).  (18)

[0075] Then

G c (s)=(1/k)Gc(s/ωp).  (19)

[0076] Referring to FIG. 3, an example system 300 that employs frequency scaling is illustrated. The system 300 includes a controller identifier 310 that can identify a known controller associated with controlling a known plant. The controller may have one or more scaleable parameters (e.g., frequency, gains) that facilitate scaling the controller. The controller identifier 310 may access a controller information data store 330 and/or a plant information data store 340 to facilitate characterizing one or more properties of the known controller. By way of illustration, the controller identifier 310 may identify the frequency scale of the controller (ωc) and/or the frequency scale (ωp) and transfer function (s) of a plant controlled by the known controller.

[0077] The controller information data store 330 may store, for example, controller class information and/or information concerning scaleable controller parameters. Similarly, the plant data store 340 may store, for example, plant information like transfer function shape, frequency scale, and so on.

[0078] The system 300 may also include a controller scaler 320 that produces a scaled controller from the identified scaleable parameter. The scaler 320 may make scaling decisions based, for example, on information in the controller information data store 330 (e.g., controller class, scaleable parameters, frequency scale), information in the plant information data store 340 (e.g. plant class, plant transfer function, frequency scale), and so on.

[0079] While illustrated as two separate entities, it is to be appreciated that the identifier 310 and scaler 320 could be implemented in a single computer component and/or as two or more distributed, communicating, co-operating computer components. Thus, the entities illustrated in FIG. 3 may communicate through computer communications using signals, carrier waves, data packets, and so on. Similarly, while illustrated as two separate data stores, the controller information data store 330 and the plant information data store 340 may be implemented as a single data store and/or distributed between two or more communicating, co-operating data stores.

[0080] Aspects of controller scaling can be related to filter design. In filter design, with the bandwidth, the pass band, and stop band requirements given, filter design is straight forward. An example filter design method includes finding a unit bandwidth filter, such as an nth order Chebeshev filter H(s), that meets the pass band and stop band specifications and then frequency scaling the filter as H(s/ω0) to achieve a bandwidth of ω0.

[0081] Revisiting the system 200 in FIG. 2, to facilitate understanding frequency scaling and time scaling as related to controllers, denote ωp as the frequency scale of the plant Gp(s/ωp) with respect to Gp(s) 210, and τp=1/ωp, the corresponding time scale. Then denote k as the gain scale of the plant kGp(s) with respect to Gp(s) 210. With these definitions in hand, differences in example industrial control problems can be described in terms of the frequency and gain scales. For example, temperature processes with different time constants (in first order transfer functions), motion control problems with different inertias, motor sizes, frictions, and the like can be described in terms of the defined frequency and gain scales.

[0082] These scales facilitate paying less attention to differences between controllers and applications and more attention to a generic solution for a class of problems because using the scales facilitates reducing linear time invariant plants, proper and without a finite zero, to one of the following example forms: 8$\begin{array}{cc}\frac{1}{s+1},\frac{1}{s},\frac{1}{s^2+2\xi s+1},\frac{1}{s\left(s+1\right)},\frac{1}{s^2},\frac{1}{s^3+{\xi }_1{s}^2+{\xi }_{2}s+1},& \left(22\right)\end{array}$

[0083] through gain and frequency scaling. For example, the motion control plant of Gp(s)=23.2/s(s+1.41) is a variation of a generic motion control plant Gp(s)=1/s(s+1) with a gain factor of k=11.67 and ωp=1.41. 9$\begin{array}{cc}\frac{23.2}{s\left(s+1.41\right)}=\frac{11.67}{\frac{s}{1.41}\left(\frac{s}{1.41}+1\right)}& \left(23\right)\end{array}$

[0084] Equation (22) describes many example industrial control problems that can be approximated by a first order or a second order transfer function response. Additionally, equation (22) can be appended by terms like: 10$\begin{array}{cc}\frac{s+1}{s^2+2\xi s+1},\frac{s^2=2{\xi }_{z}s+1}{s^3+{\xi }_1{s}^2+{\xi }_{2}s+1},& \left(24\right)\end{array}$

[0085] to include systems with finite zeros. Thus, while a set of examples is provided in equations (22) and (24), it is to be appreciated that a greater and/or lesser number of forms can be employed in accordance with the systems and methods described herein. Furthermore, in some examples, scaling can be applied to reflect the unique characteristics of certain problems. For example, a motion control system with significant resonant problems can be modeled and scaled as 11$\begin{array}{cc}\frac{k}{\frac{s}{{\omega }_p}\left(\frac{s}{{\omega }_p}+1\right)}\frac{{\left(\frac{s}{{\omega }_{\mathrm{rz}}}\right)}^2+2{\xi }_z\frac{s}{{\omega }_{\mathrm{rz}}}+1}{{\left(\frac{s}{{\omega }_{\mathrm{rp}}}\right)}^2+2{\xi }_p\frac{s}{{\omega }_{\mathrm{rp}}}+1}\mathrm{scaling}\Downarrow & \\ \frac{1}{s\left(s+1\right)}\frac{{\left(\frac{s}{m}\right)}^2+2{\xi }_z\frac{s}{m}+1}{{\left(\frac{s}{n}\right)}^2+2{\xi }_p\frac{s}{n}+1}& \left(25\right)\end{array}$

[0086] where the resonant frequencies satisfy ωrp=nωp, ωrz=mωp. Problems with multiple frequency scales, ωp, nωp, and mωp, can be referred to as multi-scale problems. With these definitions in hand, an example controller scaling technique is now described.

[0087] Assume Gc(s) is a stabilizing controller for plant Gp(s), and the loop gain crossover frequency is ωc, then the controller

{overscore (G)} c (s)=Gc(s/ωp)/k  (26)

[0088] will stabilize the plant {overscore (G)}p(s)=kGp1(s/ωp). The new controller new loop gain

{overscore (L)} (s)={overscore (G)}p(s){overscore (G)}c(s)  (27)

[0089] will have a bandwidth of ωcωp, and substantially the same stability margins of

L (s)=Gp(s)Gc(s)

[0090] since

{overscore (L)} (s)=L(s/ωp).

[0091] Note that the new closed-loop system has substantially the same frequency response shape as the original system except that it is shifted by ωp. Thus, feedback control properties like bandwidth, disturbance and noise rejection are retained, as is the stability robustness, from the previous design, except that frequency ranges are shifted by ωp.

[0092] Now that controller scaling has been described, PID scaling can be addressed. According to the frequency scale principle discussed above, and assuming the original controller for Gp(s) is a PID, e.g., 12$\begin{array}{cc}{G}_c\left(s\right)=k_p+\frac{k_i}{s}+k_{d}s& \left(28\right)\end{array}$

[0093] then the new controller for the plant kGp(s/ωp) is obtained from (28) as 13$\begin{array}{cc}{G}_c\left(s\right)=\left(k_p+k_i\frac{{\omega }_p}{s}+k_d\frac{s}{{\omega }_p}\right)/k& \left(29\right)\end{array}$

[0094] That is, the new PID gains, {overscore (k)}p, {overscore (k)}i, and {overscore (k)}d are obtained from the original ones as 14$\begin{array}{cc}{\stackrel{\_}{k}}_p=\frac{k_p}{k},{\stackrel{\_}{k}}_i=\frac{k_i{\omega }_p}{k},{\stackrel{\_}{k}}_d=\frac{k_d}{k{\omega }_p}& \left(30\right)\end{array}$

[0095] To demonstrate the practical application and tangible results possible from the method described above, in the following example, consider a plant that has a transfer function of 15$G_p\left(s\right)=\frac{1}{s^2+s+1}$

[0096] and the PID control gains of kp=3, ki=1, and kd=2. Now, assume the plant has changed to 16$G_p\left(s\right)=\frac{1}{{\left(\frac{s}{10}\right)}^2+\frac{s}{10}+1}$

[0097] The new gains are calculated from equation (30) as {overscore (k)}p=3,{overscore (k)}i=10,{overscore (k)}d=0.2. Thus, rather than having to build, design, and tune the controller for the plant 17$G_p\left(s\right)=\frac{1}{{\left(\frac{s}{10}\right)}^2+\frac{s}{10}+1}$

[0098] from scratch, the PID designer was able to select an existing PID appropriate for the PID class and scale the PID. Thus, frequency scaling facilitates new systems and methods for controller design that take advantage of previously designed controllers and the relationships between controllers in related applications.

[0099] In one example, the controller is a PID controller. The PID controller may have a plant frequency scale ωp as a scaleable parameter. In another example, the method includes producing the scaled controller. For example, a computer component may be programmed to perform the frequency scaled controlling. Additionally, computer executable portions of the method may be stored on a computer readable medium and/or be transmitted between computer components by, for example, carrier waves encoding computer executable instructions.

[0100] In view of the exemplary systems shown and described below, example methodologies that are implemented will be better appreciated with reference to the flow diagrams of FIGS. 4, 5 and 13. While for purposes of simplicity of explanation, the illustrated methodologies are shown and described as a series of blocks, it is to be appreciated that the methodologies are not limited by the order of the blocks, as some blocks can occur in different orders and/or concurrently with other blocks from that shown and described. Moreover, less than all the illustrated blocks may be required to implement an example methodology. Furthermore, additional and/or alternative methodologies can employ additional, not illustrated blocks. In one example, methodologies are implemented as computer executable instructions and/or operations, stored on computer readable media including, but not limited to an application specific integrated circuit (ASIC), a compact disc (CD), a digital versatile disk (DVD), a random access memory (RAM), a read only memory (ROM), a programmable read only memory (PROM), an electronically erasable programmable read only memory (EEPROM), a disk, a carrier wave, and a memory stick.

[0101] In the flow diagrams, rectangular blocks denote “processing blocks” that may be implemented, for example, in software. Similarly, the diamond shaped blocks denote “decision blocks” or “flow control blocks” that may also be implemented, for example, in software. Alternatively, and/or additionally, the processing and decision blocks can be implemented in functionally equivalent circuits like a digital signal processor (DSP), an ASIC, and the like.

[0102] A flow diagram does not depict syntax for any particular programming language, methodology, or style (e.g., procedural, object-oriented). Rather, a flow diagram illustrates functional information one skilled in the art may employ to program software, design circuits, and so on. It is to be appreciated that in some examples, program elements like temporary variables, initialization of loops and variables, routine loops, and so on are not shown.

[0103] Turning to FIG. 5, a flowchart for an example method 500 for producing a controller is illustrated. The method 500 includes, at 510, identifying a controller Gc(s) that stabilizes a plant Gp(s) where the controller has a frequency ωc and, at 520, producing a controller {overscore (G)}c(s) by scaling the controller Gp(s) according to {overscore (G)}c(s)=Gc(s/ωp)/k, where the controller {overscore (G)}c(s) will stabilize the plant {overscore (G)}p(s)=kGp1(s/ωp), where ωp is the frequency scale of the plant Gp(s/ωp), and where k is the gain scale of the plant kGp(s). In one example, the controller is a PID controller of the form 18$G_c\left(s\right)=k_p+\frac{k_i}{s}+k_{d}s,$

[0104] where kp is a proportional gain, ki is an integral gain, and kd is a derivative gain. In another example, 19$G_c\left(s\right)=\left(k_p+k_i\frac{{\omega }_p}{s}+k_d\frac{s}{{\omega }_p}\right)/k.$

[0105] In yet another example, the PID gains {overscore (k)}p, {overscore (k)}i, and {overscore (k)}d are obtained from the kp, ki and kd according to 20${\stackrel{\_}{k}}_p=\frac{k_p}{k},{\stackrel{\_}{k}}_i=\frac{k_i{\omega }_p}{k},{\stackrel{\_}{k}}_d=\frac{k_d}{k{\omega }_p}$

[0106] It is to be appreciated that this example method can be employed with linear and/or non-linear PIDs.

[0107] Applying a unit step function as the set point, the responses of an original controller and a scaled controller are shown in FIG. 6, demonstrating that the response of the scaled controller is substantially the same as the response of the original controller, but scaled by τ=1/ω0. The gain margins of both systems are substantially infinite and the phase margins are both approximately 82.372 degrees. The 0 dB crossover frequency for both systems are 2.3935 and 23.935 r/s, respectively. Thus, the PID scaled by the example method is demonstrably appropriate for the application.

[0108] While the method described above concerned linear PIDs, it is to be appreciated that the method can also be applied to scaling nonlinear PIDs. For example, PID performance can be improved by using nonlinear gains in place of the linear ones. For example,

u=k p g p (e)+ki∫gi(e)dt+kdgd({dot over (e)})  (31)

[0109] where gp(e), gi(e), and gd(e) are nonlinear functions. The non-linear PIDs can be denoted NPID. Nonlinearities are selected so that the proportional control is more sensitive to small errors, the integral control is limited to the small error region—which leads to significant reduction in the associate phase lag—and the differential control is limited to a large error region, which reduces its sensitivity to the poor signal to noise ratio when the response reaches steady state and the error is small.

[0110] The NPID retains the simplicity of PID and the intuitive tuning. The same gain scaling formula (30) will also apply to the NPID controller when the plant changes from Gp(s) to kGp(s/ωp).

[0111] Scaling facilitates concentrating on normalized control problems like those defined in (22). This facilitates selecting an appropriate controller for an individual problem by using the scaling formula in (26) and the related systems and methods that produce tangible, results (e.g., scaled controller). This further facilitates focusing on the fundamentals of control, like basic assumptions, requirements, and limitations. Thus, the example systems, methods, and so on described herein concerning scaling and parameterization can be employed to facilitate optimizing individual solutions given the physical constraints of a problem.

[0112] Parameterization

[0113] Working with controllers can be simplified if they can be described in terms of a smaller set of parameters than is conventionally possible. Typically, a controller (and possibly an observer) may have many (e.g. 15) parameters. The systems and methods described herein concerning parameterization facilitate describing a controller in terms of a single parameter. In one example, controller parameterization concerns making controller parameters functions of a single variable, the controller bandwidth ωc.

[0114] Considering the normalized plants in (22) and assuming desired closed-loop transfer functions are: 21$\begin{array}{cc}\frac{{\omega }_c}{s+{\omega }_c},\frac{{\omega }_c^2}{{\left(s+{\omega }_c\right)}^2},\frac{{\omega }_c^3}{{\left(s+{\omega }_c\right)}^3},& \left(32\right)\end{array}$

[0115] then for second order plants, the damping ratio can be set to unity, resulting in two repeated poles at −ωc. The same technique can also be applied to higher order plants.

[0116] Applying pole-placement design to the first and second order plants in (22), a set of example ωc parameterized controllers are obtained and shown in Table I. Information concerning the plants and the related controllers can be stored, for example, in a data store.

TABLE I
Examples of ωc-parameterized controllers
Gp(s)	22$\frac{1}{s+1}$	23$\frac{1}{s}$	24$\frac{1}{s^2+2\mathrm{\xi s}+1}$	25$\frac{1}{s\left(s+1\right)}$	26$\frac{1}{s^2}$
Gc(s, ωc)	27$\frac{{\omega }_c\left(s+1\right)}{s}$	ωc	28${\omega }_c^2\frac{s^2+2\mathrm{\xi s}+1}{s\left(s+2{\omega }_c\right)}$	29$\frac{{\omega }_c^2\left(s+1\right)}{s+2{\omega }_c}$	30$\frac{{\omega }_c^{2}s}{s+2{\omega }_c}$

[0117] Loop shaping design can also be parameterized. Loop-shaping refers to manipulating the loop gain frequency response, L(jω)=Gp(jω)Gc(jω), as a control design tool. One example loop-shaping method includes converting design specifications to loop gain constraints, as shown in FIG. 7 and finding a controller Gc(jω) to meet the specifications.

[0118] As an example of loop shaping, considering the plants of the form Gp(s), in Table I, the desired loop gain can be characterized as 31$\begin{array}{cc}L\left(s\right)=G_p\left(s\right)G_c\left(s\right)={\left(\frac{s+{\omega }_1}{s}\right)}^m\frac{1}{\frac{s}{{\omega }_c}+1}\frac{1}{{\left(\frac{s}{{\omega }_2}+1\right)}^n}& \left(33\right)\end{array}$

[0119] where ωc is the bandwidth, and

ω1<ωc, ω2>ωc, m≧0, and n≧0  (34)

[0120] are selected to meet constrains shown in FIG. 7. In the example, both m and n are integers. In one example, default values for ω1 and ω2 are

ω1=ωc/10 and ω2=10ωc  (35)

[0121] which yield a phase margin greater than forty-five degrees.

[0122] Once appropriate loop gain constraints are derived and the corresponding lowest order L(s) in (33) is selected, the controller can be determined from 32$\begin{array}{cc}{G}_c\left(s\right)={\left(\frac{s+{\omega }_1}{s}\right)}^m\frac{1}{\frac{s}{{\omega }_c}+1}\frac{1}{{\left(\frac{s}{{\omega }_2}+1\right)}^n}{G}_p^{-1}\left(s\right)& \left(36\right)\end{array}$

[0123] An additional constraint on n is that 33$\begin{array}{cc}\frac{1}{\frac{s}{{\omega }_c}+1}\frac{1}{{\left(\frac{s}{{\omega }_2}+1\right)}^n}{G}_p^{-1}\left(s\right)\mathrm{is}\mathrm{proper}.& \left(37\right)\end{array}$

[0124] This design is valid for plants with a minimum phase. For a non-minimum phase plant, a minimum phase approximation of Gp−1(s) can be employed.

[0125] A compromise between ω1 and the phase margin can be made by adjusting ω1 upwards, which will improve the low frequency properties at the cost of reducing phase margin. A similar compromise can be made between phase margin and ω2.

[0126] Turning to FIG. 4, an example method 400 for scaling a controller is illustrated. The method 400 includes, at 410, identifying a known controller in a controller class where the known controller controls a first plant. The method 400 also includes, at 420, identifying a scaleable parameter for the known controller. At 430, the method 400 includes identifying a desired controller in the controller class, where the desired controller controls a second, frequency related plant and at 440, establishing the frequency relation between the known controller and the desired controller. At 450, the method 400 scales the known controller to the desired controller by scaling the scaleable parameter based, at least in part, on the relation between the known controller and the desired controller.

[0127] Practical Optimization Based on a Hybrid Scaling and Parameterization Method

[0128] Practical controller optimization concerns obtaining optimal performance out of existing hardware and software given physical constraints. Practical controller optimization is measured by performance measurements including, but not limited to, command following quickness (a.k.a. settling time), accuracy (transient and steady state errors), and disturbance rejection ability (e.g., attenuation magnitude and frequency range). Example physical constraints include, but are not limited to, sampling and loop update rate, sensor noise, plant dynamic uncertainties, saturation limit, and actuation signal smoothness requirements.

[0129] Conventional tuning relies, for example, on minimizing a cost function like H2 and H28 . However, conventional cost functions may not comprehensively reflect the realities of control engineering, and may, therefore, lead to suboptimal tuning. For example, one common cost function is mathematically attractive but can lead to suboptimal controller tuning. Thus, optimizing other criteria, like ωc are considered.

[0130] A typical industrial control application involves a stable single-input single-output (SISO) plant, where the output represents a measurable process variable to be regulated and the input represents the control actuation that has a certain dynamic relationship to the output. This relationship is usually nonlinear and unknown, although a linear approximation can be obtained at an operating point via the plant response to a particular input excitation, like a step change.

[0131] Evaluating performance measurements in light of physical limitations yields the fact that they benefit from maximum controller bandwidth ωc. If poles are placed in the same location, then ωc can become the single item to tune. Thus, practical PID optimization can be achieved with single parameter tuning. For example, in manufacturing, a design objective for an assembly line may be to make it run as fast as possible while minimizing the down time for maintenance and trouble shooting. Similarly, in servo design for a computer hard disk drive, a design objective may be to make the read/write head position follow the setpoint as fast as possible while maintaining extremely high accuracy. In automobile anti-lock brake control design, a design objective may be to have the wheel speed follow a desired speed as closely as possible to achieve minimum braking distance.

[0132] In the three examples, the design goal can be translated to maximizing controller bandwidth ωc. There are other industrial control examples that lead to the same conclusion. Thus, ωc maximization appears to be a useful criterion for practical optimality. Furthermore, unlike purely mathematical optimization techniques, ωc optimization has real world applicability because it is limited by physical constraints. For example, sending ωc to infinity may be impractical because it may cause a resulting signal to vary unacceptably.

[0133] As an example of how physical limitations may affect ωc optimization, consider digital control apparatus that have a maximum sampling rate and a maximum loop update rate. The maximum sampling rate is a hardware limit associated with the Analog to Digital Converter (ADC) and the maximum loop update rate is software limit related to central processing unit (CPU) speed and the control algorithm complexity. Typically, computation speeds outpace sampling rates and therefore only the sampling rate limitation is considered.

[0134] As another example, measurement noise may also be considered when examining the physical limitations of ωc optimization. For example, the ωc is limited to the frequency range where the accurate measurement of the process variable can be obtained. Outside of this range, the noise can be filtered using either analog or digital filters.

[0135] Plant dynamic uncertainty may also be considered when examining the physical limitations of ωc optimization. Conventional control design is based on a mathematical description of the plant, which may only be reliable in a low frequency range. Some physical plants exhibit erratic phase distortions and nonlinear behaviors at a relative high frequency range. The controller bandwidth is therefore limited to the low frequency range where the plant is well behaved and predictable. To safeguard the system from instability, the loop gain is reduced where the plant is uncertain. Thus, maximizing the bandwidth safely amounts to expanding the effective (high gain) control to the edge of frequency range where the behavior of the plant is well known.

[0136] Similarly, actuator saturation and smoothness may also affect design. Although using transient profile helps to decouple bandwidth design and the transient requirement, limitations in the actuator like saturation, nonlinearities like backlash and hysteresis, limits on rate of change, smoothness requirements based on wear and tear considerations, and so on may affect the design. For example, in a motion control application with a significant backlash problem in the gearbox, excessively high bandwidth will result in a chattering gearbox and, very likely, premature breakdown. Thus, ωc optimization, because it considers physical limitations like sampling rate, loop update rate, plant uncertainty, actuator saturation, and so on, may produce improved performance.

[0137] In one controller optimization example, assume that the plant is minimum phase, (e.g., its poles and zeros are in the left half plane), that the plant transfer function is given, that the ωc parameterized controllers are known and available in form of Table I, that a transient profile is defined according to the transient response specifications, and that a simulator 800 of closed-loop control system as shown in FIG. 8 is available. It is to be appreciated that the closed loop control system simulator 800 can be, for example, hardware, software or a combination of both. In one example, the simulator incorporates limiting factors including, but not limited to, sensor and quantization noises, sampling disturbances, actuator limits, and the like.

[0138] With these assumptions, one example design method then includes, determining frequency and gain scales, ωp and k from the given plant transfer function. The method also includes, based on the design specification, determining the type of controller required from, for example, Table I. The method also includes selecting the Gc(s, ωc) corresponding to the scaled plant in the form of Table I. The method also includes scaling the controller to 34$\frac{1}{k}{G}_c\left(\frac{s}{{\omega }_p},{\omega }_c\right),$

[0139] digitizing Gc(s/ωp, ωc)/k and implementing the controller in the simulator. The method may also include setting an initial value of ωc based on the bandwidth requirement from the transient response and increasing ωc while performing tests on the simulator, until either one of the following is observed:

[0140] a. Control signal becomes too noisy and/or too uneven, or

[0141] b. Indication of instability (oscillatory behavior)

[0142] Consider an example motion control test bed for which the mathematical model of the motion system is

ÿ =(−1.41{dot over (y)}+23.2Td)+23.2u  (38)

[0143] where y is the output position, u is the control voltage sent to the power amplifier that drives the motor, and Td is the torque disturbance. An example design objective for the example system could be rotating the load one revolution in one second with no overshoot. Thus, the physical characteristics of the example control problem are:

[0144] 1) |u|<3.5 volt,

[0145] 2) sampling rate=1 kHz,

[0146] 3) sensor noise is 0.1% white noise,

[0147] 4) torque disturbance up to 10% of the maximum torque,

[0148] 5) smooth control signal.

[0149] The plant transfer function is 35$G_p\left(s\right)=\frac{k}{\frac{s}{{\omega }_p}\left(\frac{s}{{\omega }_p}+1\right)},k=11.67\mathrm{and}{\omega }_p=1.41.$

[0150] Now consider the corresponding UGUB plant 36${\stackrel{\_}{G}}_p\left(s\right)=\frac{1}{s\left(s+1\right)}.$

[0151] A PD design of

u=k p (r−y)+kd(−{dot over (y)})

[0152] with

[0153] kp=ωc2 and kd=2ωc−1

[0154] makes the closed-loop transfer function 37$G_{\mathrm{c1}}\left(s\right)=\frac{{\omega }_c^2}{{\left(s+{\omega }_c\right)}^2}.$

[0155] Considering the plant gain scale of k and the frequency scale of ωp, the PD gains are then scaled as 38$k_p=\frac{{\omega }_c^2}{k}=\mathrm{.086}{\omega }_c^2\mathrm{and}{k}_d=\frac{2{\omega }_c-1}{k{\omega }_p}=\mathrm{.061}\left(2{\omega }_c-1\right).$

[0156] To avoid noise corruptions of the control signal, an approximate differentiator 39$\frac{s}{{\left(\frac{s}{10{\omega }_c}+1\right)}^2}$

[0157] is used where the corner frequency 10ωc is selected so that the differentiator approximation does not introduce problematic phase delays at the crossover frequency. Using a conventional root locus method, the one second settling time would require a closed-loop bandwidth of 4 rad/sec. The example single parameter design and tuning methods described herein facilitate determining that an ωc of 20 rad/sec yields optimal performance under the given conditions. A comparison of the two designs is shown in FIG. 9. Note that a step disturbance of 1 volt is added at t=3 seconds to test disturbance rejection. Finally, a trapezoidal transient profile is used in place of the step command. The results are shown in FIG. 10.

[0158] Parameterization of State Feedback and State Observer Gains

[0159] As described in the Background section, the State Feedback (SF) controller

u=r+K{circumflex over (x)}   (4)

[0160] is based on the state space model of the plant:

{dot over (x)} (t)=Ax(t)+Bu(t), y(t)=Cx(t)+Du(t)  (5)

[0161] When the state x is not accessible, a state observer (SO):

{circumflex over ({dot over (x)})}=A{circumflex over (x)}+Bu+L (y−ŷ)  (6)

[0162] is often used to find its estimate, {circumflex over (x)}. Here r is the setpoint for the output to follow. The state feedback gain K and the observer gain L are determined from the equations:

eig (A+BK)=λc(s) and eig(A+LC)=λo(s)

[0163] where λc(s) and λo(s) are polynomials of s that are chosen by the designer. Usually the K and L have many parameters and are hard to tune.

[0164] The parameterization of state feedback and state observer gains are achieved by making

[0165] λc(s)=(s+ωc)n and λo(s)=(s+ωo)n

[0166] where ωc and ωo are bandwidth of the state feedback system and the state observer, respectively, and n is the order of the system. This simplifies tuning since parameters in K and L are now functions of ωc and ωo, respectively.

[0167] Parameterization of Linear Active Disturbance Rejection Controller (LADRC) for a Second Order Plant

[0168] Some controllers are associated with observers. Conventionally, second order systems with controllers and observers may have a large number (e.g., 15) tunable features in each of the controller and observer. Thus, while a design method like the Hann method is conceptually viable, its practical implementation is difficult because of tuning issues. As a consequence of the scaling and parameterization described herein, observer based systems can be constructed and tuned using two parameters, observer bandwidth (ω0) and controller bandwidth (ωc).

[0169] State observers provide information on the internal states of plants. State observers also function as noise filters. A state observer design principle concerns how fast the observer should track the states, (e.g., what should its bandwidth be). The closed-loop observer, or the correction term L(y−ŷ) in particular, accommodates unknown initial states, uncertainties in parameters, and disturbances. Whether an observer can meet the control requirements is largely dependent on how fast the observer can track the states and, in case of ESO, the disturbance f(t,x1,x2,w). Generally speaking, faster observers are preferred. Common limiting factors in observer design include, but are not limited to dependency on the state space model of the plant, sensor noise, and fixed sampling rate.

[0170] Dependency on the state space model can limit an application to situations where a model is available. It also makes the observer sensitive to the inaccuracies of the model and the plant dynamic changes. The sensor noise level is hardware dependent, but it is reasonable to assume it is a white noise with the peak value 0.1% to 1% of the output. The observer bandwidth can be selected so that there is no significant oscillation in its states due to noises. A state observer is a closed-loop system by itself and the sampling rate has similar effects on the state observer performance as it does on feedback control. Thus, an example model independent state observer system is described.

[0171] Observers are typically based on mathematical models. Example systems and methods described herein can employ a “model independent” observer as illustrated in FIG. 18. For example a plant 1820 may have a controller 1810 and an observer 1830. The controller 1810 may be implemented as a computer component and thus may be programmatically tunable. Similarly, the observer 1830 may be implemented as a computer component and thus may have scaleable parameters that can be scaled programmatically. Furthermore, using analogous scaling and parameterizing as described herein, the parameters of the observer 1830 can be reduced to ωo. Therefore, overall optimizing of the system 1800 reduces to tuning ωc and ωo.

[0172] Consider a simple example for controlling a second order plant

ÿ=−a{dot over (y)}−by+w+bu   (39)

[0173] where y and u are output and input, respectively, and w is an input disturbance. Here both parameters, a and b, are unknown, although there is some knowledge of b, (e.g., b0≈b, derived from the initial acceleration of y in step response). Rewrite (39) as

ÿ=−a{dot over (y)}−by+w +(b−b0)u+bou=f+b0u  (40)

[0174] where f=−a{dot over (y)}−by+w+(b−bo)u. Here f is referred to as the generalized disturbance, or disturbance, because it represents both the unknown internal dynamics, −a{dot over (y)}−by+(b−bo)u and the external disturbance w(t).

[0175] If an estimate of f, {circumflex over (f)} can be obtained, then the control law 40$u=\frac{-\hat{f}+u_0}{b_0}$

[0176] reduces the plant to ÿ=(f−{circumflex over (f)})+uo which is a unit-gain double integrator control problem with a disturbance (f−{circumflex over (f)}).

[0177] Thus, rewrite the plant in (40) in state space form as 41$\begin{array}{cc}\{\begin{array}{c}{\stackrel{.}{x}}_1=x_2\\ {\stackrel{.}{x}}_2=x_3+b_{0}u\\ {\stackrel{.}{x}}_3=h\\ y=x_1\end{array}& \left(41\right)\end{array}$

[0178] with x3=f added as an augmented state, and h={dot over (f)} is seen as an unknown disturbance. Now f can be estimated using a state observer based on the state space model 42$\begin{array}{cc}\stackrel{.}{x}=Ax+Bu+Ehy=Cz\mathrm{where}\text{\&IndentingNewLine;}A=\left[\begin{array}{ccc}0& 1& 0\\ 0& 0& 1\\ 0& 0& 0\end{array}\right],B=\left[\begin{array}{c}0\\ b_0\\ 0\end{array}\right],C=\left[100\right],E=\left[\begin{array}{c}0\\ 0\\ 1\end{array}\right]& \left(42\right)\end{array}$

[0179] Now the state space observer, denoted as the linear extended state observer (LESO), of (42) can be constructed as

[0180] {dot over (z)}=Az+Bu+L (y−ŷ)

ŷ=Cz   (43)

[0181] which can be reconstructed in software, for example, and L is the observer gain vector, which can be obtained using various methods known in the art like pole placement,

L=[β 1 β2β3]T  (44)

[0182] where [ ]T denotes transpose. With the given state observer, the control law can be given as: 43$\begin{array}{cc}u=\frac{-z_3+u_0}{b_0}& \left(45\right)\end{array}$

[0183] Ignoring the inaccuracy of the observer,

ÿ =(f−z3)+u0≈uo  (46)

[0184] which is an unit gain double integrator that can be implemented with a PD controller

u 0 =k p (r−z1)−kdz2  (47)

[0185] where r is the setpoint. This results in a pure second order closed-loop transfer function of 44$\begin{array}{cc}{G}_{\mathrm{cl}}=\frac{1}{s^2+k_{d}s+k_p}& \left(48\right)\end{array}$

[0186] Thus, the gains can be selected as

k d =2ξωc and kp=ωc2  (49)

[0187] where ωc and ζ are the desired closed loop natural frequency and damping ratio. ζ can be chosen to avoid oscillations. Note that −kdz2, instead of kd({dot over (r)}−z2), is used to avoid differentiating the setpoint and to make the closed-loop transfer function a pure second order one without a zero.

[0188] This example illustrates that disturbance observer based PD control achieves zero steady state error without using the integral part of a PID controller. The example also illustrates that the design is model independent in that the design relies on the approximate value of b in (39). The example also illustrates that the combined effects of the unknown disturbance and the internal dynamics are treated as a generalized disturbance. By augmenting the observer to include an extra state, it is actively estimated and canceled out, thereby achieving active disturbance rejection. This LESO based control scheme is referred to as linear active disturbance rejection control (LADRC) because the disturbance, both internal and external, represented by f, is actively estimated and eliminated.

[0189] The stability of controllers can also be examined. Let ei=xi−zi, i=1, 2, 3. Combine equation (43) and (44) and subtract the combination from (42). Thus, the error equation can be written: 45$\begin{array}{cc}\stackrel{.}{e}=A_{e}e+\mathrm{Eh}\mathrm{where}{A}_e=A-\mathrm{LC}=\left[\begin{array}{ccc}-{\beta }_1& 1& 0\\ -{\beta }_2& 0& 1\\ -{\beta }_3& 0& 0\end{array}\right]& \left(50\right)\end{array}$

[0190] and E is defined in (42). The LESO is bounded input, bounded output (BIBO) stable if the roots of the characteristic polynomial of Ae

λ(s)=s3+β1s2+β2s+β3  (51)

[0191] are in the left half plane (LHP) and h is bounded. This separation principle also applies to LADRC.

[0192] The LADRC design from (43) to (46) yields a BIBO stable closed-loop system if the observer in (43) and (44) and the feedback control law (46) for the double integrator are stable, respectively. This is shown by combing equations (45) and (47) into a state feedback form of u=(1/b0)[−kp−kd−1]z=Fz, where F=(1/b0)[−kp−kd−1]. Thus, the closed-loop system can be represented by the state-space equation of: 46$\begin{array}{cc}\left[\begin{array}{c}\stackrel{.}{x}\\ \stackrel{.}{z}\end{array}\right]=\left[\begin{array}{cc}A& \stackrel{\_}{B}F\\ \mathrm{LC}& A-\mathrm{LC}+\stackrel{\_}{B}F\end{array}\right]\left[\begin{array}{c}x\\ z\end{array}\right]+\left[\begin{array}{cc}[\stackrel{\_}{B}& E]\\ \stackrel{\_}{[B}& 0]\end{array}\right]\left[\begin{array}{c}r\\ h\end{array}\right]& \left(52\right)\end{array}$

[0193] where {overscore (B)}=B/b0, and which is BIBO stable if its eigenvalues are in the LHP. By applying row and column operations, the closed-loop eigenvalues 47$\mathrm{eig}\left(\left[\begin{array}{cc}A& \stackrel{\_}{B}F\\ \mathrm{LC}& A-\mathrm{LC}+\stackrel{\_}{B}F\end{array}\right]\right)=\mathrm{eig}\left(\left[\begin{array}{cc}A+\stackrel{\_}{B}F& \stackrel{\_}{B}F\\ 0& A-\mathrm{LC}\end{array}\right]\right)$$\begin{array}{c}=\mathrm{eig}\left(A+\stackrel{\_}{B}F\right)⋓\mathrm{eig}\left(A-\mathrm{LC}\right)\\ =\left\{\mathrm{roots}\mathrm{of}{s}^2+k_{d}s+k_p\right\}⋓\{\mathrm{roots}\mathrm{of}{s}^3+{\beta }_1{s}^2+{\beta }_{2}s+{\beta }_3\}\end{array}$

[0194] Since r is the bounded reference signal, a nontrivial condition on the plant is that h={dot over (f)} is bounded. In other words, the disturbance f must be differentiable.

[0195] Observer Bandwidth Parameterization

[0196] ωo parameterization refers to parameterizing the ESO on observer bandwidth ωo. Consider a plant (42) that has three poles at the origin. The related observer will be less sensitive to noises if the observer gains in (44) are small for a given ωo. But observer gains are proportional to the distance for the plant poles to those of the observer. Thus the three observer poles should be placed at −ωo, or equivalently,

λ(s)=s3+β1s2+β2s+β3=(s+ωo)3  (53)

[0197] That is

β1=3ωo, β2=3ωo2, β3=ωo3  (54)

[0198] It is to be appreciated by one of ordinary skill in the art that equations (53) and (54) are extendable to nth order ESO. Similarly, the parameterization method can be extended to the Luenberger Observer for arbitrary A, B, and C matrices, by obtaining {{overscore (A)},{overscore (B)},{overscore (C)}} as observable canonical form of {A,B,C}, determining the observer gain, {overscore (L)}, so that the poles of the observer are at −ωo and using the inverse state transformation to obtain the observer gain, L, for {A,B,C}. The parameters in L are functions of ωo. One example procedure for ωo optimization based design is now described.

[0199] Given tolerable noise thresholds in the observer states, increase ωo until at least one of the thresholds is about to be reached or the observer states become oscillatory due to sampling delay. In general, the faster the ESO, the faster the disturbance is observed and cancelled by the control law.

[0200] A relationship between ωo and ωc can be examined. One example relationship is

ωo≈3␣5ωc  (55)

[0201] Equation (55) applies to a state feedback control system where ωc is determined based on transient response requirements like the settling time specification. Using a transient profile instead of a step command facilitates more aggressive control design. In this example there are two bandwidths to consider, the actual control loop bandwidth ωc and the equivalent bandwidth of the transient profile, {overscore (ω)}c. Part of the design procedure concerns selecting which of the two to use in (55). Since the observer is evaluated on how closely it tracks the states and {overscore (ω)}c is more indicative than ωc on how fast the plant states move, {overscore (ω)}c is the better choice although it is to be appreciated that either can be employed. Furthermore, taking other design issues like the sampling delay into consideration, a more appropriate minimum ωo is found through simulation and experimentation as

ωo≈5␣10{overscore (ω)}c  (56)

[0202] An example for optimizing LADRC is now presented. One example LADRC design and optimization method includes designing a parameterized LESO and feedback control law where ωo and ωc are the design parameters. The method also includes designing a transient profile with the equivalent bandwidth of {overscore (ω)}c and selecting an ωo from (56). The method then includes setting ωc=ωo and simulating and/or testing the LADRC in a simulator. The method also includes incrementally increasing ωc and ωo by the same amount until the noise levels and/or oscillations in the control signal and output exceed the tolerance. The method also includes incrementally increasing or decreasing ωc and ωo individually, if necessary, to make trade-offs between different design considerations like the maximum error during the transient period, the disturbance attenuation, and the magnitude and smoothness of the controller.

[0203] In one example, the simulation and/or testing may not yield satisfactory results if the transient design specification described by {overscore (ω)}c is untenable due to noise and/or sampling limitations. In this case, control goals can be lowered by reducing {overscore (ω)}c and therefore ωc and ωo. It will be appreciated by one skilled in the art that this approach can be extended to Luenberg state observer based state feedback design.

[0204] By way of illustration, reconsider the control problem example associated with equations (32), but apply the LADRC in (43) to (48). Note that b=23.2 for this problem, but to make the design realistic, assume the designer's estimate of b is b0=40. Now rewrite the plant differential equation (38) as

ÿ (−1.41{dot over (y)}+23.2Td)+(23.2−40)u+40u=f+40u

[0205] The LESO is 48$\stackrel{.}{z}=\left[\begin{array}{ccc}-3{\omega }_o& 1& 0\\ -3{\omega }_o^2& 0& 1\\ -{\omega }_o^3& 0& 0\end{array}\right]z+\left[\begin{array}{cc}0& 3{\omega }_o\\ 40& 3{\omega }_o^2\\ 0& {\omega }_o^3\end{array}\right]\left[\begin{array}{c}u\\ y\end{array}\right]$

[0206] and

[0207] z1→y,z2→{dot over (y)}, and

[0208] z3→f=−1.41{dot over (y)}+23.2Td+(23.2−40)u, as t→∞

[0209] The control law is defined as 49$u=\frac{u_0-z_3}{40}\mathrm{and}{u}_0=k_p\left(r-z_1\right)-k_d{z}_2$

[0210] with

[0211] kd=2ξωc, ξ=1, and kp=ωc2

[0212] where ωc is the sole design parameter to be tuned. A trapezoidal transient profile is used with a settling time of one second, or {overscore (ω)}c=4. From (56), ωo is selected to be 40 rad/sec. The LADRC facilitates design where a detailed mathematical model is not required, where zero steady state error is achieved without using the integrator term in PID, where there is better command following during the transient stage and where the controller is robust. This performance is achieved by using a disturbance observer. Example performance is illustrated in FIG. 12.

[0213] Parameterization of LADRC for nth Order Plant

[0214] It will be appreciated by one skilled in the art that observer based design and tuning techniques can be scaled to plants of arbitrary orders. For a general nth order plant with unknown dynamics and external disturbances,

y (n) =f (t,y,{dot over (y)}, . . . , y(n−1),u,{dot over (u)}, . . . u(n−1),w)+bu  (57)

[0215] the observer can be similarly derived, starting from the state space equation 50$\begin{array}{cc}\{\begin{array}{c}{\stackrel{.}{x}}_1=x_2\\ {\stackrel{.}{x}}_2=x_3\\ \cdots \\ {\stackrel{.}{x}}_n=x_{n+1}+b_{0}u\\ {\stackrel{.}{x}}_{n+1}=h\\ y=x_1\end{array}& \left(58\right)\end{array}$

[0216] with xn+1=f added as an augmented state, and h=f mostly unknown. The observer of (43) in its linear form with the observer gain

L=[β 1 β2 . . . βn+1]  (59)

[0217] has the form 51$\begin{array}{cc}\{\begin{array}{c}{\stackrel{.}{z}}_1=z_2-{\beta }_1\left(z_1-y\left(t\right)\right)\\ {\stackrel{.}{z}}_2=z_3-{\beta }_2\left(z_1-y\left(t\right)\right)\\ \cdots \\ {\stackrel{.}{z}}_n=z_{n+1}-{\beta }_n\left(z_1-y\left(t\right)\right)+b_{0}u\\ {\stackrel{.}{z}}_{n+1}=-{\beta }_{n+1}\left(z_1-y\left(t\right)\right)\end{array}& \left(60\right)\end{array}$

[0218] With the gains properly selected, the observer will track the states and yield

z 1 (t)→y(t),z2(t)→{dot over (y)}(t), . . . ,Zn(t)→y(n−1)(t)

z n+1 (t)→f(t,y,{dot over (y)}, . . . , y(n−1),u,{dot over (u)}, . . . u(n−1),w)  (61)

[0219] The control law can also be similarly designed as in (45) and (47), with 52$\begin{array}{cc}u=\frac{z_{n+1}+u_0}{b_0}& \left(62\right)\end{array}$

[0220] which reduces the plant to approximately a unit gain cascaded integrator plant

y (n) =(f−zn+1)+u0≈u0  (63)

[0221] and

u 0 =k p (r−z1)−kd1z2− . . . −kdn−1zn  (64)

[0222] where the gains are selected so that the closed-loop characteristic polynomial has n poles at −ωc,

s n +k d n−1 s n−1 + . . . +k d 1 s+k p =(s+ωc)n  (65)

[0223] ωc is the closed-loop bandwidth to be optimized in tuning. The ωo optimization can similarly be applied using

s n +β1sn−1+ . . . +βn−1s+βn=(s+ωo)n  (66)

[0224] The following example method can be employed to identify a plant order and b0. Given a “black box” plant with input u and output y, the order, n, and b0 can be estimated by allowing the plant to discharge energy stored internally so that it has a zero initial condition, (e.g., y(0)={dot over (y)}(0)= . . . y(n−1)(0)=0) and then assuming f(0)=0. The method includes applying a set of input signals and determining the initial slope of the response: {dot over (y)}(0+),ÿ(0+), . . . . The method also includes determining the slope y(i)(0+) that is proportional to u(0) under various tests, (e.g., y(i)(0+)=ku(0)). Then the method includes setting n=i+1 and b0=k.

[0225] Auto-Tuning Based on the New Scaling, Parameterization and Optimization Techniques

[0226] Auto-tuning concerns a “press button function” in digital control equipment that automatically selects control parameters. Auto-tuning is conventionally realized using an algorithm to calculate the PID parameters based on the step response characteristics like overshoot and settling time. Auto-tuning has application in, for example, the start up procedure of closed-loop control (e.g., commissioning an assembly line in a factory). Auto-tuning can benefit from scaling and parameterization.

[0227] In some applications, dynamic changes in the plant during operations are so severe that controller parameters are varied from one operating point to another. Conventionally, gain-scheduling is employed to handle these situations. In gain-scheduling, the controller gains are predetermined for different operating points and switched during operations. Additionally, and/or alternatively, self-tuning that actively adjusts control parameters based on real time data identifying dynamic plant changes is employed.

[0228] Common goals of these techniques are to make the controller parameter determination automatic, given the plant response to a certain input excitation, say a step function and to maintain a consistent controller performance over a wide range of operations, (e.g. making the controller robust).

[0229] Example systems, methods and so on described herein concerning scaling and parameterization facilitate auto-scaling model based controllers. When a transfer function model of a plant is available, the controller can be designed using either pole placement or loop shaping techniques. Thus, example scaling techniques described herein facilitate automating controller design and tuning for problems including, but not limited to, motion control, where plants are similar, differing only in de gain and the bandwidth, and adjusting controller parameters to maintain high control performance as the bandwidth and the gain of the plant change during the operation.

[0230] In the examples, the plant transfer functions can be represented as {overscore (G)}p(s)=kGp(s/ωp), where Gp(s) is given and known as the “mother” plant and k and ωp are obtained from the plant response or transfer function. Assuming the design criteria are similar in nature, differing only in terms of the loop gain bandwidth, ωc, the controller for similar plants can be automatically obtained by scaling the given controller, Gc(s,ωc), for Gp(s). This is achieved by combining the controller scaling, defined in equation (26), and ωc-parameterization to obtain the controller for {overscore (G)}p(s)=kGp(s/ωp) as

{overscore (G)} c (s,ωc)=Gc(s/ωp, ωc)/k  (67)

[0231] There are three parameters in (67) that are subject to tuning. The first two parameters, k and ωp, represent plant changes or variations that are determined. The third parameter, ωc, is tuned to maximize performance of the control system subject to practical constraints.

[0232] An example method for auto-tuning is now described. The auto-tuning method includes examining a plant Gp(s) and the nominal controller Gc(s,ωc). Given the plant Gp(s) and the nominal controller Gc(s,ωc), the method includes performing off-line tests to determine k and ωp for the plant. The method also includes using equation (67) to determine a new controller for the plant, {overscore (G)}p(s)=kGp(s/ωp), obtained in the previous act. The method also includes optimizing ωc for the new plant.

[0233] An example method for adaptive self-tuning is now described. The adaptive self-tuning procedure includes examining a plant {overscore (G)}p(s)=kGp(s/ωp), where k and ωp are subject to change during plant operation. Given the plant {overscore (G)}p(s)=kGp(s/ωp), the method includes performing real time parameter estimation to determine k and ωp as they change. The method also includes determining when the performance of the control system is degraded beyond a pre-determined, configurable threshold and updating the controller using (67). The method also includes selectively decreasing ωc if the plant dynamics deviate significantly from the model kGp(s/ωp), which causes performance and stability problems. The method also includes selectively increasing ωc subject to ωc-optimization constraints if the plant model can be updated to reflect the changes of the plant beyond k and ωp.

[0234] The LADRC technique does not require the mathematical model of the plant. Instead, it employs a rough estimate of the single parameter b in the differential equation of the plant (57). This estimation is denoted as b0 and is the sole plant parameter in LADRC. As the dynamics of the plant changes, so does b. Thus, b0 can be estimated by rewriting (57) as

y (n) =f (t)+bu  (69)

[0235] and assuming the zero initial condition, (e.g., y(i)(0)=0, i=1, 2, . . . n−1 and f(0)=0). Then b0≈b can be estimated by using

b o =y (n) (0+)/u(0)  (70)

[0236] where u(0) is the initial value of the input. It is to be appreciated that this method can be applied to both open loop and closed-loop configurations. For the auto-tuning purposes, the test can be performed off-line and a step input, u(t)=constant can be applied. The LADRC does not require b0 to be highly accurate because the difference, b−b0, is treated as one of the sources of the disturbance estimated by LESO and cancelled by control law.

[0237] The b0 obtained from the off-line estimation of b described above can be adapted for auto-tuning LADRC. An auto-tuning method includes, performing off-line tests to determine the order of the plant and b0, selecting the order and the b0 parameter of the LADRC using the results of the off-line tests, and performing a computerized auto-optimization.

[0238] Using the controller scaling, parameterization and optimization techniques presented herein, an example computer implemented method 1300 as shown in FIG. 13 can be employed to facilitate automatically designing and optimizing the automatic controls (ADOAC) for various applications. The applications include, but are not limited to, motion control, thermal control, pH control, aeronautics, avionics, astronautics, servo control, and so on.

[0239] The method 1300, at 1310, accepts inputs including, but not limited to, information concerning hardware and software limitations like the actuator saturation limit, noise tolerance, sampling rate limit, noise levels from sensors, quantization, finite word length, and the like. The method also accepts input design requirements like settling time, overshoot, accuracy, disturbance attenuation, and so on. Furthermore, the method also accepts as input the preferred control law form like, PID form, model based controller in a transfer function form, and model independent LADRC form. In one example, the method can indicate if the control law should be provided in a difference equation form. At 1320, a determination is made concerning whether a model is available. If a model is available, then at 1330 the model is accepted either in transfer function, differential equations, or state space form. If a model is not available, then the method may accept step response data at 1340. Information on significant dynamics that is not modeled, such as the resonant modes, can also be accepted.

[0240] Once the method has received information input, the method can check design feasibility by evaluating the specification against the limitations. For example, in order to see whether transient specifications are achievable given the limitations on the actuator, various transient profiles can be used to determine maximum values of the derivatives of the output base on which the maximum control signal can be estimated. Thus, at 1350, a determination is made concerning whether the design is feasible. In one example, if the design is not feasible, processing can conclude. Otherwise, processing can proceed to 1360.

[0241] If the input information passes the feasibility test, then at 1360, the method 1300 can determine an ωc parameterized solution in one or more formats. In one example, the ωc solution can then be simulated at 1370 to facilitate optimizing the solution.

[0242] In one example, to assist an engineer or other user, the ADOAC method provides parameterized solutions of different kind, order, and/or forms, as references. The references can then be ranked separately according to simplicity, command following quality, disturbance rejection, and so on to facilitate comparison.

[0243] FIG. 14 illustrates a computer 1400 that includes a processor 1402, a memory 1404, a disk 1406, input/output ports 1410, and a network interface 1412 operably connected by a bus 1408. Executable components of the systems described herein may be located on a computer like computer 1400. Similarly, computer executable methods described herein may be performed on a computer like computer 1400. It is to be appreciated that other computers may also be employed with the systems and methods described herein. The processor 1402 can be a variety of various processors including dual microprocessor and other multi-processor architectures. The memory 1404 can include volatile memory and/or non-volatile memory. The non-volatile memory can include, but is not limited to, read only memory (ROM), programmable read only memory (PROM), electrically programmable read only memory (EPROM), electrically erasable programmable read only memory (EEPROM), and the like. Volatile memory can include, for example, random access memory (RAM), synchronous RAM (SRAM), dynamic RAM (DRAM), synchronous DRAM (SDRAM), double data rate SDRAM (DDR SDRAM), and direct RAM bus RAM (DRRAM). The disk 1406 can include, but is not limited to, devices like a magnetic disk drive, a floppy disk drive, a tape drive, a Zip drive, a flash memory card, and/or a memory stick. Furthermore, the disk 1406 can include optical drives like, compact disk ROM (CD-ROM), a CD recordable drive (CD-R drive), a CD rewriteable drive (CD-RW drive) and/or a digital versatile ROM drive (DVD ROM). The memory 1404 can store processes 1414 and/or data 1416, for example. The disk 1406 and/or memory 1404 can store an operating system that controls and allocates resources of the computer 1400.

[0244] The bus 1408 can be a single internal bus interconnect architecture and/or other bus architectures. The bus 1408 can be of a variety of types including, but not limited to, a memory bus or memory controller, a peripheral bus or external bus, and/or a local bus. The local bus can be of varieties including, but not limited to, an industrial standard architecture (ISA) bus, a microchannel architecture (MSA) bus, an extended ISA (EISA) bus, a peripheral component interconnect (PCI) bus, a universal serial (USB) bus, and a small computer systems interface (SCSI) bus.

[0245] The computer 1400 interacts with input/output devices 1418 via input/output ports 1410. Input/output devices 1418 can include, but are not limited to, a keyboard, a microphone, a pointing and selection device, cameras, video cards, displays, and the like. The input/output ports 1410 can include but are not limited to, serial ports, parallel ports, and USB ports.

[0246] The computer 1400 can operate in a network environment and thus is connected to a network 1420 by a network interface 1412. Through the network 1420, the computer 1400 may be logically connected to a remote computer 1422. The network 1420 can include, but is not limited to, local area networks (LAN), wide area networks (WAN), and other networks. The network interface 1412 can connect to local area network technologies including, but not limited to, fiber distributed data interface (FDDI), copper distributed data interface (CDDI), ethernet/IEEE 802.3, token ring/IEEE 802.5, and the like. Similarly, the network interface 1412 can connect to wide area network technologies including, but not limited to, point to point links, and circuit switching networks like integrated services digital networks (ISDN), packet switching networks, and digital subscriber lines (DSL).

[0247] Referring now to FIG. 15, information can be transmitted between various computer components associated with controller scaling and parameterization described herein via a data packet 1500. An exemplary data packet 1500 is shown. The data packet 1500 includes a header field 1510 that includes information such as the length and type of packet. A source identifier 1520 follows the header field 1510 and includes, for example, an address of the computer component from which the packet 1500 originated. Following the source identifier 1520, the packet 1500 includes a destination identifier 1530 that holds, for example, an address of the computer component to which the packet 1500 is ultimately destined. Source and destination identifiers can be, for example, globally unique identifiers (guids), URLS (uniform resource locators), path names, and the like. The data field 1540 in the packet 1500 includes various information intended for the receiving computer component. The data packet 1500 ends with an error detecting and/or correcting field 1550 whereby a computer component can determine if it has properly received the packet 1500. While six fields are illustrated in the data packet 1500, it is to be appreciated that a greater and/or lesser number of fields can be present in data packets.

[0248] FIG. 16 is a schematic illustration of sub-fields 1600 within the data field 1540 (FIG. 15). The sub-fields 1600 discussed are merely exemplary and it is to be appreciated that a greater and/or lesser number of sub-fields could be employed with various types of data germane to controller scaling and parameterization. The sub-fields 1600 include a field 1610 that stores, for example, information concerning the frequency of a known controller and a second field 1620 that stores a desired frequency for a desired controller that will be scaled from the known controller. The sub-fields 1600 may also include a field 1630 that stores a frequency scaling data computed from the known frequency and the desired frequency.

[0249] Referring now to FIG. 17, an application programming interface (API) 1700 is illustrated providing access to a system 1710 for controller scaling and/or parameterization. The API 1700 can be employed, for example, by programmers 1720 and/or processes 1730 to gain access to processing performed by the system 1710. For example, a programmer 1720 can write a program to access the system 1710 (e.g., to invoke its operation, to monitor its operation, to access its functionality) where writing a program is facilitated by the presence of the API 1700. Thus, rather than the programmer 1720 having to understand the internals of the system 1710, the programmer's task is simplified by merely having to learn the interface to the system 1710. This facilitates encapsulating the functionality of the system 1710 while exposing that functionality. Similarly, the API 1700 can be employed to provide data values to the system 1710 and/or retrieve data values from the system 1710.

[0250] For example, a process 1730 that retrieves plant information from a data store can provide the plant information to the system 1710 and/or the programmers 1720 via the API 1700 by, for example, using a call provided in the API 1700. Thus, in one example of the API 1700, a set of application program interfaces can be stored on a computer-readable medium. The interfaces can be executed by a computer component to gain access to a system for controller scaling and parameterization. Interfaces can include, but are not limited to, a first interface 1740 that facilitates communicating controller information associated with PID production, a second interface 1750 that facilitates communicating plant information associated with PID production, and a third interface 1760 that facilitates communicating frequency scaling information generated from the plant information and the controller information.

[0251] The systems, methods, and objects described herein may be stored, for example, on a computer readable media. Media can include, but are not limited to, an ASIC, a CD, a DVD, a RAM, a ROM, a PROM, a disk, a carrier wave, a memory stick, and the like. Thus, an example computer readable medium can store computer executable instructions for one or more of the claimed methods.

[0252] What has been described above includes several examples. It is, of course, not possible to describe every conceivable combination of components or methodologies for purposes of describing the systems, methods, computer readable media and so on employed in scaling and parameterizing controllers. However, one of ordinary skill in the art may recognize that further combinations and permutations are possible. Accordingly, this application is intended to embrace alterations, modifications, and variations that fall within the scope of the appended claims. Furthermore, the preceding description is not meant to limit the scope of the invention. Rather, the scope of the invention is to be determined only by the appended claims and their equivalents.

[0253] While the systems, methods and so on herein have been illustrated by describing examples, and while the examples have been described in considerable detail, it is not the intention of the applicants to restrict or in any way limit the scope of the appended claims to such detail. Additional advantages and modifications will be readily apparent to those skilled in the art. Therefore, the invention, in its broader aspects, is not limited to the specific details, the representative apparatus, and illustrative examples shown and described. Accordingly, departures may be made from such details without departing from the spirit or scope of the applicant's general inventive concept.

Claims

1. A method for manufacturing a desired controller based on the design of a known controller, comprising: identifying a known controller in a controller class where the known controller controls a first plant; identifying a scaleable parameter for the known controller; identifying a desired controller in the controller class, where the desired controller controls a second plant that is frequency related by a frequency relation to the known controller; establishing the frequency relation between the known controller and the desired controller; and scaling the known controller to the desired controller by scaling the scaleable parameter based on the frequency relation.

2. The method of claim 1, where the known controller is a PID controller.

3. The method of claim 1, where the scaleable parameter is the plant frequency scale ωp.

4. The method of claim 1, comprising producing the desired controller by programmatically adapting the known controller.

5. A computer readable medium storing computer executable instructions operable to perform computer executable portions of the method of claim 1.

6. The method of claim 1, where the known controller and the desired controller are TFB controllers of the form

7. The method of claim 6, comprising producing the desired TFB controller by programmatically adapting the known TFB controller.

8. The method of claim 1, where the known controller and the desired controller are PID controllers of the form

9. The method of claim 8, comprising producing the desired PID controller by programmatically adapting the known PID controller.

10. A method for producing a controller, comprising: normalizing a plant into a UGUB form plant yielding a gain scale and a frequency scale; identifying a controller function for the UGUB form plant given a desired closed loop transfer function; and programmatically scaling the controller function for the UGUB form plant to a desired controller function based on the gain scale and the frequency scale.

11. The method of claim 10, where the controller function is a PID controller function.

12. A computer readable medium storing computer executable instructions operable to perform computer executable portions of the method of claim 10.

13. A method for producing a controller, comprising: identifying a scaleable controller Gc (s) that controls a plant Gp(s) to within a desired tolerance; and producing a controller {overscore (G)}c(s) by programmatically scaling the controller Gc(s) according to {overscore (G)}c(s)=Gc(s/ωp)/k, where the controller {overscore (G)}c(s) will control a plant {overscore (G)}p(s)=kGp(s/ωp) to within a desired tolerance, where ωp is the frequency scale of a plant Gp(s/ωp), and where k is the gain scale of a plant kGp(s).

14. The method of claim 13, where the controller Gc(s) is a PID controller of the form

15. The method of claim 14, where

16. The method of claim 14, where PID gains {overscore (k)}p, {overscore (k)}i, and {overscore (k)}d for the controller {overscore (G)}c(s) are obtained from kp, ki and kd according to

17. The method of claim 13 where the controller Gc(s) is a linear PID.

18. The method of claim 13, where the controller Gc(s) is a non-linear PID.

19. A computer readable medium storing computer executable instructions operable to perform computer executable portions of the method of claim 13.

20. A method for producing a parameterized controller, comprising: selecting a controller to parameterize; identifying two or more scaleable parameters for the controller; programmatically relating the two or more scaleable parameters to a single controller parameter; relating a controller with the single controller parameter to a plant; and programmatically configuring the parameterized controller by configuring the single controller parameter.

21. The method of claim 20, where the scaleable parameters include one or more of, proportional gain kp, integral gain ki, derivative gain kd, and plant frequency scale ωp.

22. The method of claim 21, where the single controller parameter is controller bandwidth ωc.

23. The method of claim 22, where a controller Gc is related to a plant Gp in terms of the single parameter ωc according to:

24. The method of claim 20, where the controller is a PID controller.

25. The method of claim 20, where the controller is an SF controller.

26. The method of claim 20, where the controller is an SO based controller.

27. The method of claim 20, where the controller is an LESO based controller.

28. The method of claim 20, where the controller is an LADRC controller.

29. The method of claim 20, where the controller is a TFB controller.

30. A method for producing a controller, comprising: establishing one or more loop gain constraints based on one or more design specifications; programmatically accessing a parameterized loop shaping model; selecting a controller Gc(jω) from the model based on the one or more loop gain constraints; and programmatically establishing a loop gain frequency response of the form L(Jω)=Gp(jω)Gc(jω), where ωc is the bandwidth of a feedback control system and a controller Gc(s,ωc) related to the controller Gc(jω).

31. The method of claim 30, where establishing a loop gain constraint based on a design specification comprises: identifying a bandwidth ωc, where ω1<ωc and where ω2>ωc; and for a design specification concerning command following, establishing a ωc less than ω1.

32. The method of claim 30, where establishing a loop gain constraint based on a design specification comprises: identifying a bandwidth ωc, where ω1<ωc and where ω2>ωc; and for a design specification concerning disturbance rejection, establishing a ωc less than ω1.

33. The method of claim 30, where establishing a loop gain constraint based on a design specification comprises: identifying a bandwidth ωc, where ω1<ωc and where ω2>ωc; and for a design specification concerning sensor noise, establishing a ωc, greater than ω2.

34. The method of claim 30, where establishing a loop gain constraint based on a design specification comprises: identifying a bandwidth ωc, where ω1<ωc and where ω2>ωc; and for a design specification concerning unknown dynamics, establishing a ωc greater than ω2.

35. The method of claim 31, where the default value for ω1 is ωc/10.

36. The method of claim 31, where the default value for ω2 is 10ωc.

37. The method of claim 31, where default values for ω1 and ω2 yield a phase margin greater than forty-five degrees.

38. The method of claim 30, where the controller Gc(jω) is determined from:

39. A computer readable medium storing computer executable instructions operable to perform computer executable portions of the method of claim 30.

40. A method for designing and optimizing an LADRC, comprising: selecting a ωo and ωc based LESO and feedback control law; establishing a transient profile for the LADRC with an equivalent bandwidth of {overscore (ω)}c; selecting an ωo from ωo≈5␣10{overscore (ω)}c; setting ωc=ωo; inputting the feedback control, ωo and ωc, into an LADRC simulator; incrementally increasing ωc and ωo in the simulator until a constraint exceeds a pre-determined tolerance; and selectively incrementally changing ωc or ωo in the simulator until a desired behavior is observed.

41. The method of claim 40, where a design consideration is a maximum error during the transient period.

42. The method of claim 40, where a design consideration is a disturbance attenuation.

43. The method of claim 40, where a design consideration is a magnitude and a smoothness of a controller.

44. The method of claim 40 where the constraint is one or more of, a noise level, an oscillation level in a control signal, an oscillation level in an output signal, and a noise level magnitude rate of change.

45. A controller design method, comprising: identifying a plant transfer function for a plant to be controlled by the controller; computing a frequency scale ωp and a gain scale k for a controller from the plant transfer function; selecting a controller Gc(s, ωc) corresponding to a scaled plant in a known form based on the plant transfer function, the frequency scale, and the gain scale; scaling the controller according to 681k⁢Gc⁡(sωp,ωc);digitizing Gc(s/ωp, ωc)/k; simulating the digitized controller in a computer component; setting an initial value of ωc in the simulated controller based on a bandwidth requirement derived from a transient response; and varying ωc in the simulated controller until one or more of, a simulated control signal increases beyond a noise threshold, the simulated control signal exceeds an evenness threshold, or an instability indicator in the simulated controller rises beyond a stability threshold.

46. A method for producing a PID controller, comprising: identifying a plant signature for a plant for which a PID controller exists; identifying an existing PID controller appropriate for controlling the plant based on the plant signature; and programmatically scaling the existing PID controller to a desired controller.

47. A controller design system, comprising: means for frequency scale relating a desired controller to an existing controller; and means for scaling the existing controller to the desired controller based on the frequency scale relating.

48. A method for producing a controller, comprising: identifying a known controller in a controller class where the known controller controls a first plant; identifying two or more scaleable parameters for the controller; programmatically relating the two or more scaleable parameters to a single scaleable controller parameter; identifying a desired controller in the controller class, where the desired controller controls a second plant that is frequency related by a frequency relation associated with the single scaleable controller parameter to the known controller; establishing the frequency relation between the known controller and the desired controller; and scaling the known controller to the desired controller by scaling the single scaleable parameter based on the frequency relation.

49. The method of claim 48, where the controller is a PID controller of the form

50. The method of claim 48, where the controller is a TFB controller of the form

51. A method for tuning a controller, comprising: identifying a single tunable parameter for a controller to which two or more other tunable parameters for the controller can be related; programmatically relating the single parameter to the other tunable parameters; and programmatically varying the single tunable parameter until a desired controller performance is observed.

52. The method of claim 51, where the controller is a TFB controller of the form

53. The method of claim 52, where the single tunable parameter is a plant frequency scale ωp for a plant that is controlled by the TFB controller.

54. The method of claim 51, where the controller is a PID controller of the form

55. The method of claim 51 where the controller is an SF controller.

56. The method of claim 51, where the controller is an SO or a LESO based controller.

57. The method of claim 51, where the controller is an LADRC controller.

58. A set of application programming interfaces embodied on a computer readable medium for execution by a computer component in conjunction with frequency scaling a controller, comprising: a first interface for communicating a controller information; a second interface for communicating a plant information; and a third interface for communicating frequency scaling information derived, at least in part, from the controller information and the plant information.

59. In a computer system having a graphical user interface comprising a display and a selection device, a method of providing and selecting from a set of data entries on the display, the method comprising: retrieving a set of data entries, each of the data entries representing one of a frequency scaling choice for scaling a known controller to a desired controller; displaying the set of entries on the display; receiving a data entry selection signal indicative of the selection device selecting a selected data entry; and in response to the data entry selection signal, initiating an operation associated with the selected data entry.

60. A computer data signal embodied in a transmission medium, comprising: a first set of instructions for identifying a plant signature for a plant; a second set of instructions for identifying a controller class for a controller that controls the plant; and a third set of instructions for scaling the controller based, at least in part, on the plant signature.

61. A data packet for transmitting frequency scaling data, comprising: a first field that stores a known frequency for a known controller; a second field that stores a desired frequency for a desired controller; and a third field that stores a frequency scaling data computed from the known frequency and the desired frequency.

62. A method for auto-tuning a controller, comprising: identifying a plant Gp(s) and a nominal controller Gc(s,ωc) for the plant to be tuned; programmatically determining k and ωp for the plant Gp(s) and the controller Gc(s,ωc); programmatically determining a new controller for a new plant {overscore (G)}p(s)=kGp(s/ωp) according to {overscore (G)}c(s,ωc)=Gc(s/ωp, ωc)/k; and programmatically varying ωc for the new plant until a desired behavior is observed.

63. A method for adaptive self-tuning a controller, comprising: identifying a plant {overscore (G)}p(s)=kGp(s/ωp), where k and ωp are subject to change during plant operation; programmatically estimating, in real-time, k and ωp for the plant {overscore (G)}p(s); programmatically determining when the performance of the controller for the plant {overscore (G)}p(s) is degraded beyond a pre-determined, configurable threshold; programmatically updating the controller according to {overscore (G)}c(s,ωc)=Gc(s/ωp, ωc)/k; selectively decreasing ωc if dynamics of the plant deviate significantly from a model kGp(s/ωp) causing a performance problem or a stability problem; and selectively increasing ωc, subject to one or more ωc-optimization constraints, if the model can be updated to reflect one or more changes of the plant beyond k and ωp.

64. The method of claim 63, where the ωc-optimization constraints are one or more of, a noise level, an oscillation level in a control signal, an oscillation level in an output signal, and a noise level magnitude rate of change.

65. A method for automatically designing and optimizing ADOAC, comprising: if a model of a plant is available, accepting a mathematical model of the plant in one or more of, transfer function, differential equation, and state space form; if a model is not available, accepting a step response data; selectively accepting a non-modeled dynamic data; accepting zero or more hardware limitations; accepting zero or more software limitations; accepting one or more design requirements; selectively indicating whether a control law should be provided in a difference equation form; accepting a control law preferred form data; verifying a design feasibility by evaluating one or more of the mathematical model, the step response data, the non-modeled dynamic data, the hardware limitations, and the software limitations in light of the design requirements; selectively determining an ωc parameterized solution in one or more formats based on the design feasibility verifying; and producing one or more parameterized solutions of one or more different kinds, orders, and/or forms, as references.

66. The method of claim 65, where the software limitations include, an actuator saturation limit, a noise tolerance, a sampling rate limit, a noise level from a sensor, and a finite word length.

67. The method of claim 65, where the hardware limitations include, an actuator saturation limit, a noise tolerance, a sampling rate limit, a noise level from a sensor, and a finite word length.

68. The method of claim 65, where the design requirements include one or more of, settling time, overshoot, accuracy, and disturbance attenuation.

69. The method of claim 65, where the control law preferred form data include transfer function form and model independent LADRC form.

70. The method of claim 65 where the references are ranked separately according to one or more of, simplicity, command following quality, and disturbance rejection.

71. A system for designing a controller, comprising: a plant data store that stores plant information; a controller information data store that stores controller class information and controller scaleable parameter information; a controller identifier that identifies a controller that controls a first known plant, where the controller has one or more scaleable parameters; and a controller scaler that scales the controller identified by the controller identifier to a scaled controller suitable for controlling a second, frequency scale related plant based, at least in part, on one or more of the controller class information, the controller scaleable parameter information, and the plant information.

72. A method for optimizing controller performance based on tuning controller bandwidth ωc, comprising: selecting an initial ωc value; programmatically altering ωc one or more times to one or more altered ωc values; electronically examining a controller performance at the one or more altered ωc values; and programmatically selecting a final ωc value from the initial ωc value and the altered ωc values based on the controller performance.

73. The method of claim 72, where the controller performance is examined on one or more of, a control signal noise threshold, a control signal evenness threshold, and an instability indicator threshold.

74. A system, comprising: a plant; a controller for controlling the plant, where the controller can be tuned on a single, frequency scaleable controller parameter; an observer for observing the controller, where the observer can be tuned on a single, frequency scaleable observer parameter; and a tuner for tuning the controller based on the single controller parameter and for tuning the observer based on the single observer parameter.

75. The system of claim 74, where the single frequency scaleable controller parameter is ωc.

76. The system of claim 76, where the single frequency scaleable observer parameter is ωo.