Constraints and robustness

11 min read
On this page

An actuator can apply only 100% heating even when the controller requests 120%. If integration ignores the difference, error can accumulate internally and delay recovery after the target becomes feasible. This chapter connects PID with frequency-domain analysis.

Requested versus applied action

Let be the unclipped request. Applied action is

Only enters the thermal plant. With ambient 20 °C, heat loss 20 W/K and maximum heating 1000 W, the highest equilibrium is 70 °C. A target of 80 °C cannot be reached by increasing integral gain.

With , positive error keeps increasing during saturation. After the target drops to 40 °C, even negative error may take time to unwind it. Clipping the output does not stop the internal state growing.

Preparing the visual
Constraints and robustness · Experiment

Ambient 20 °C; infeasible reference 80 °C drops to 40 °C at 200 s. Kp=0.04, Ki=0.001, action limited to 0–1. Back-calculation corrects integration using applied-minus-requested action. Components exclude baseline 0.4.

Start at 40 °C, request 80 °C, then return to 40 °C at 200 s. Compare temperature, unclipped request, applied action and integral contribution with and without back-calculation. Anti-windup does not make the original infeasible target feasible.

Back-calculation and conditional integration

Back-calculation feeds the applied-minus-requested difference into the integral state:

At upper saturation, the correction is negative. With K, , , , s, , rather than +0.01 without correction. Smaller speeds this internal tracking loop but can introduce excessively fast dynamics.

Conditional integration instead pauses integration when saturation and error push farther into the limit. Integration that moves the request back into range should remain possible; do not freeze permanently whenever saturation occurs.

Feedforward, other controllers or rate limits require an actual-action signal measured at the appropriate location. Manual-to-automatic transitions also need a consistent integral state to avoid jumps. MathWorks examples distinguish back-calculation, clamping and external tracking.

Identify the sensitivity paths

For unity negative feedback, output disturbance , measurement and loop , rearrange :

maps reference to output and, with a minus sign, sensor noise to output. maps this output disturbance to output. Meanwhile : small output noise can coexist with large control activity.

A disturbance at the plant input instead has path . Extra thermal power uses the power-to-temperature plant, not the duty-to-temperature gain. Draw the injection point before assigning a transfer.

is a complex identity, not . Both cannot be arbitrarily small at the same frequency, but full cross-frequency “waterbed” integral statements require additional assumptions.

Define the uncertainty before claiming robustness

Keep the controller fixed and vary thermal capacitance, heat-loss coefficient and delay separately. Compare tracking, disturbance recovery, peak action and saturation duration. Capacitance mainly changes dynamics; heat loss also changes static gain; delay reduces phase. A single unspecified “percentage error” hides these differences.

More formally, write , where bounds frequency-dependent multiplicative uncertainty and stable satisfies . With nominal internal stability and a well-posed interconnection, is a small-gain sufficient condition for robust stability. A few parameter samples do not prove stability over the entire set.

Check your understanding

At upper saturation, should integration pause after error becomes negative?

Reasoning

Normally allow integration that lowers the request toward the valid range. Check the direction of integration, not saturation alone.

Why can an actuator move frequently while measured output looks smooth?

Reasoning

The plant may filter high-frequency actions. The noise-to-action path is , different from the noise-to-output path . Record both action and output.

Further reading

The python-control robust SISO example uses frequency weights to express performance requirements. Physical validation must still include model validity, actuator limits and measurement quality.