This is machine translation

Translated by Microsoft
Mouseover text to see original. Click the button below to return to the English version of the page.

Note: This page has been translated by MathWorks. Click here to see
To view all translated materials including this page, select Country from the country navigator on the bottom of this page.

Stability Margins of a Simulink Model

This example illustrates how to compute classical and disk-based gain and phase margins of a control loop modeled in Simulink®. To compute stability margins, linearize the model to extract the open-loop responses at one or more operating points of interest. Then, use allmargin or diskmargin to compute the classical or disk-based stability margins, respectively.

MIMO Control Loop

For this example, use the Simulink model airframemarginEx.slx. This model is based on the example Trimming and Linearizing an Airframe (Simulink Control Design).

open_system('airframemarginEx.slx')

The system is a two-channel feedback loop. The plant is the one-input, two-output subsystem Airframe Model, and the controller is a two-input, one-output system whose inputs are the normal acceleration az and pitch rate q, and whose output is the Fin Deflection signal.

Loop Transfer Functions

To compute the gain margins and phase margins for this feedback system, linearize the model to get the open-loop transfer functions at the plant outputs and input. You can do so using linearization analysis points of the loop-transfer type. For more information about linearization analysis points, see Specify Portion of Model to Linearize (Simulink Control Design).

Create a loop-transfer analysis point for the plant input, which is the first output port of the q Control subsystem.

ioInput = linio('airframemarginEx/q Control',1,'looptransfer');

Similarly, create analysis points for the plant outputs. Because there are two outputs, specify these analysis points as a vector of linearization I/O objects.

ioOutput(1) = linio('airframemarginEx/Airframe Model',1,'looptransfer');
ioOutput(2) = linio('airframemarginEx/Airframe Model',2,'looptransfer');

Linearize the model to obtain the open-loop transfer functions. For this example, use the operating point specified in the model. The loop transfer at the plant input is SISO, while the loop transfer at the outputs is 2-by-2.

Li = linearize('airframemarginEx',ioInput);   % SISO
Lo = linearize('airframemarginEx',ioOutput);  % MIMO

Classical Gain and Phase Margins

To compute the classical gain margins and phase margins, use allmargin. For an open-loop transfer function, allmargin assumes a negative-feedback loop.

The open-loop transfer function returned by the linearize command is the actual linearized open-loop response of the model at the analysis point. Thus, for an open-loop response L, the closed-loop response of the entire model is a positive feedback loop.

Therefore, use -L to make allmargin compute the stability margins with positive feedback. Compute the classical gain and phase margins at the plant input.

Si = allmargin(-Li)
Si = 

  struct with fields:

     GainMargin: [0.1633 17.6572]
    GMFrequency: [1.5750 47.5284]
    PhaseMargin: 44.4554
    PMFrequency: 5.3930
    DelayMargin: 14.3869
    DMFrequency: 5.3930
         Stable: 1

The structure Si contains information about classical stability margins. For instance, Li.GMFrequency gives the two frequencies at which the phase of the open-loop response crosses –180°. Li.GainMargin gives the gain margin at each of those frequencies. The gain margin is the amount by which the loop gain can vary at that frequency while preserving closed-loop stability.

Compute the stability margins at the plant output. Because there are two output channels, allmargin returns an array containing one structure for each channel. Each entry contains the margins computed for that channel with the other feedback channel closed.

So = allmargin(-Lo)
So = 

  2x1 struct array with fields:

    GainMargin
    GMFrequency
    PhaseMargin
    PMFrequency
    DelayMargin
    DMFrequency
    Stable

Index into the structure to obtain the stability margins for each channel. For instance, examine the margins with respect to gain variations or phase variations at the q output of the plant, which is the second output.

So(2)
ans = 

  struct with fields:

     GainMargin: [0.3456 17.4301]
    GMFrequency: [3.4362 49.8484]
    PhaseMargin: [-78.2436 52.6040]
    PMFrequency: [1.5686 6.5428]
    DelayMargin: [313.5079 14.0324]
    DMFrequency: [1.5686 6.5428]
         Stable: 1

Disk-Based Gain and Phase Margins

Disk margins provide a stronger guarantee of stability than the classical gain and phase margins. Disk-based margin analysis models gain and phase variations as a complex uncertainty on the open-loop system response. The disk margin is the smallest such uncertainty that is compatible with closed-loop stability. (For general information about disk margins, see Stability Analysis Using Disk Margins.)

To compute disk-based margins, use diskmargin. Like allmargin, the diskmargin command assumes a negative-feedback system. Thus, use -Li to compute the disk-based margins at the plant input.

DMi = diskmargin(-Li)
DMi = 

  struct with fields:

     GainMargin: [0.4419 2.2628]
    PhaseMargin: [-42.3153 42.3153]
     DiskMargin: 0.7740
      Frequency: 4.2515

The field DMi.GainMargin tells you that the open-loop gain at the plant input can vary by any factor between about 0.44 and about 2.26 without loss of closed-loop stability. Disk-based margins take into account variations at all frequencies.

For a MIMO loop transfer function such as the response Lo at the plant outputs, there are two types of disk-based stability margins. The loop-at-a-time margins are the stability margins in each channel with the other loop closed. The multiloop margins are the margins for independent variations in gain (or phase) in both channels simultaneously. diskmargin computes both.

[DMo,MMo] = diskmargin(-Lo);

The loop-at-a-time margins are returned as a structure array DMo with one entry for each channel. For instance, examine the margins for gain variations or phase variations at the q output of the plant with the az loop closed.

DMo(2)
ans = 

  struct with fields:

     GainMargin: [0.3771 2.6521]
    PhaseMargin: [-48.6811 48.6811]
     DiskMargin: 0.9047
      Frequency: 4.4982

The multiloop margin, MMo, takes into account simultaneous variations in gain (or phase) across all feedback channels. Therefore, it typically yields the smallest margins.

MMo
MMo = 

  struct with fields:

     GainMargin: [0.6236 1.6036]
    PhaseMargin: [-26.1063 26.1063]
     DiskMargin: 0.4637
      Frequency: 3.5176

MMo.GainMargin shows that if the gains in both output channels vary independently by factors between about 0.62 and about 1.60, the closed-loop system is guaranteed to remain stable. MMo.PhaseMargin shows that stability is preserved against independent phase variations in each channel of about ±26°.

Margins at Multiple Operating Points

When you use linearize, you can provide multiple operating points to generate an array of linearizations of the system. allmargin and diskmargin can operate on linear model arrays to return the margins at multiple operating points. For example, linearize the airframe system at three simulation snapshot times.

Snap = [0.1; 2; 5];
LiSnap = linearize('airframemarginEx',ioInput,Snap);
LoSnap = linearize('airframemarginEx',ioOutput,Snap);

LiSnap is a 3-by-1 array of SISO linear models, one for the loop transfer at the plant input obtained at each snapshot time. Similarly, LoSnap is a 3-by-1 array of 2-input, 2-output linear models representing the loop transfers at the plant outputs at each snapshot time.

Compute the classical gain and phase margins at the plant inputs at the three snapshot times.

SiSnap = allmargin(-LiSnap)
SiSnap = 

  3x1 struct array with fields:

    GainMargin
    GMFrequency
    PhaseMargin
    PMFrequency
    DelayMargin
    DMFrequency
    Stable

Each entry in the structure array SiSnap contains the classical margin information for the corresponding snapshot time. For instance, examine the classical margins for the second entry, t = 2 s.

SiSnap(2)
ans = 

  struct with fields:

     GainMargin: [0.0171 18.2489]
    GMFrequency: [0.0502 51.4426]
    PhaseMargin: 93.1051
    PMFrequency: 2.8476
    DelayMargin: 57.0662
    DMFrequency: 2.8476
         Stable: 1

Compute the disk margins at the plant outputs.

[DMoSnap,MMoSnap] = diskmargin(-LoSnap);

Because there are two feedback channels, the structure array containing the loop-at-a-time disk margins has dimensions 2-by-3.

DMoSnap
DMoSnap = 

  2x3 struct array with fields:

    GainMargin
    PhaseMargin
    DiskMargin
    Frequency

The first dimension is for the feedback channels, and the second is for the snapshot times. In other words, DMoSnap(j,k) contains the margins for the channel j at the snapshot time k. For instance, examine the disk margins in the second feedback channel at the third snapshot time, t = 5 s.

DMoSnap(2,3)
ans = 

  struct with fields:

     GainMargin: [0.1345 7.4338]
    PhaseMargin: [-74.6771 74.6771]
     DiskMargin: 1.5257
      Frequency: 24.2045

There is only one set of multiloop margins for each snapshot time, so MMoSnap is a 1-by-3 structure array. Examine the multiloop disk margins at the second snapshot time, t = 2 s.

MMoSnap(2)
ans = 

  struct with fields:

     GainMargin: [0.3518 2.8423]
    PhaseMargin: [-51.2330 51.2330]
     DiskMargin: 0.9589
      Frequency: 1.1433

See Also

|

Related Topics