Skip to content
Feb 25

Steady-State Error Analysis

MT
Mindli Team

AI-Generated Content

Steady-State Error Analysis

In the design of any control system, from an automotive cruise control to a satellite's orientation thruster, one fundamental question is: how accurately does the system track its command? A system that oscillates wildly is useless, but so is one that settles to the wrong final value. Steady-state error is the persistent difference between the desired output and the actual output of a system once all transient behavior has died out. Analyzing this error is not just an academic exercise; it is essential for quantifying a system's precision and determining the necessary controller complexity to meet performance specifications for everyday commands like step changes, ramps, and parabolic trajectories.

Defining Steady-State Error

Steady-state error () is formally defined as the difference between the input (desired value) and the output as time approaches infinity, provided the system is stable. For a standard unity-feedback system, where the output is subtracted directly from the input to generate an error signal, we can analyze this using the Final Value Theorem from Laplace transform theory. This theorem states that if a function has a limit as , then that limit can be found from its Laplace transform via .

Applying this to the error signal in a unity-feedback system gives us the powerful formula: For a system with open-loop transfer function , the error signal for a reference input is . This framework allows us to calculate the steady-state error for different standard test inputs systematically, leading directly to the concept of system type.

System Type and Its Fundamental Significance

The system type is a classifying integer (N) equal to the number of free integrators (poles at the origin, ) present in the open-loop transfer function . This simple number has profound implications for a system's ability to track different inputs with zero error. We categorize systems as Type 0, Type 1, Type 2, and so on.

Think of an integrator as a mathematical accumulator. A Type 0 system (no integrators) has no inherent ability to "remember" or "integrate" past error. A Type 1 system (one integrator) can integrate a constant error over time to produce an output that eventually catches up to a step command. A Type 2 system (two integrators) can integrate the integral of an error, allowing it to catch up to a constantly changing ramp input. The system type sets the ceiling for precision: a Type N system can track a polynomial input of degree N with zero steady-state error. However, higher type numbers make the system more difficult to stabilize, a critical trade-off explored later.

Error Constants: Quantifying the Imperfection

When a system cannot achieve zero steady-state error for a given input, we quantify the remaining error using static error constants. These constants are derived from the open-loop transfer function and directly correspond to common test inputs. For a unity-feedback system, they are defined as follows.

The position error constant () predicts steady-state error for a step input (e.g., suddenly setting a thermostat to a new temperature). It is defined as: For a step input of magnitude , the steady-state error is . A Type 0 system will have a finite and thus a finite error. Systems of Type 1 or higher have , leading to zero error for a step.

The velocity error constant () predicts error for a ramp input (e.g., a cruise control tracking a slowly increasing speed). It is defined as: For a ramp input with slope (), the steady-state error is . A Type 1 system yields a finite , while a Type 0 system has (infinite error), and a Type 2 or higher system has (zero error).

The acceleration error constant () predicts error for a parabolic input (e.g., tracking an object under constant acceleration). It is defined as: For a parabolic input , . Only a Type 2 system provides a finite . Lower types give zero (infinite error), and higher types give infinite (zero error).

A Worked Example

Consider a unity-feedback system with an open-loop transfer function .

Step 1: Determine System Type. The denominator of has one factor of . This is a pole at the origin. Therefore, the system type N = 1. We expect zero steady-state error for a step input and a finite error for a ramp.

Step 2: Calculate Error Constants.

  • Position Error Constant ():

  • Velocity Error Constant ():

  • Acceleration Error Constant ():

Step 3: Compute Steady-State Errors.

  • For a unit step input (): .
  • For a unit ramp input (): .
  • For a unit parabolic input (): .

This matches our prediction: a Type 1 system perfectly tracks steps, follows ramps with a constant lag of 0.25 units, and cannot track a parabola at all.

The Trade-Off: Accuracy vs. Stability

A key principle in control design is that higher system type reduces steady-state error but complicates stability. Adding integrators (increasing system type) moves poles to the origin and tends to shift the root locus further into the right-half plane, making the closed-loop system more oscillatory and potentially unstable. A Type 2 system can be very accurate but is notoriously more difficult to stabilize than a Type 1 or Type 0 system. The designer's challenge is to add just enough integration (often within a compensator) to meet error specifications while using other design techniques (like lead compensation) to ensure adequate stability margins, such as phase and gain margin. You cannot simply add integrators indefinitely to chase zero error; you will eventually lose control of the system's dynamic response.

Common Pitfalls

  1. Misidentifying the System Type: The most common error is to look at the closed-loop transfer function or to miscount poles at the origin in the forward path. Remember: System type (N) is defined by the number of pure integrators (poles at ) in the open-loop transfer function for a unity-feedback configuration. Do not include zeros at the origin; they do not affect system type.
  2. Forgetting the Unity-Feedback Assumption: All standard formulas for , , , and the resulting calculations assume a unity-feedback structure. If the feedback path is not unity (e.g., it contains a transfer function ), you must first reduce the system to an equivalent unity-feedback form or use the Final Value Theorem directly on the specific system's error signal .
  3. Applying the Final Value Theorem Incorrectly: The Final Value Theorem is only valid if the limit exists and, crucially, if the closed-loop system is stable. Always verify stability before calculating steady-state error. An unstable system does not settle to a steady state, so the calculation is meaningless.
  4. Confusing Input Type with Error Constant: Students often try to use for a ramp input. Remember the direct pairing: Step input → , Ramp input → , Parabolic input → . A quick mnemonic: the power of '' in the limit definition of the constant ( for , for , for ) matches the power of '' in the denominator of the corresponding input Laplace transform (, , ).

Summary

  • Steady-state error quantifies a stable control system's precision in tracking a constant, ramp, or parabolic command after transients have settled. It is calculated using the Final Value Theorem: .
  • The system type (N), defined by the number of free integrators in the open-loop transfer function, determines which inputs can be tracked with zero error. A Type N system can track a polynomial input of degree N with zero steady-state error.
  • Static error constants (, , ) quantify the non-zero error for step, ramp, and parabolic inputs, respectively. Their formulas are derived from : , , and .
  • A fundamental design trade-off exists: increasing system type reduces steady-state error but complicates stability, making the system more oscillatory and harder to stabilize. Control design balances accuracy with robust dynamic performance.
  • Always verify closed-loop stability before computing steady-state error and ensure you are applying the correct formulas for a unity-feedback system configuration.

Write better notes with AI

Mindli helps you capture, organize, and master any subject with AI-powered summaries and flashcards.