C135 PCS 7 (PCS7)
6C
6 Cielo Ciencia y Tecnología
·Publicada en C135 PCS 7 (PCS7)

Differentiating External Reset Features and Anti-Windup Mechanics in PIDConR and PIDConL

Differentiating External Reset Features and Anti-Windup Mechanics in PIDConR and PIDConL

The external reset parameters ExtResOn and ExtReset belong exclusively to the restartable PID controller block PIDConR, not to ConPerMon or PIDConL. In PIDConR, setting ExtResOn = 1 forces the internal integrator to track an external value (ExtReset) for smooth bumpless transitions during feedforward control or override routines. Conversely, the standard continuous controller PIDConL natively incorporates built-in anti-windup protection without requiring external reset inputs: whenever the manipulated variable reaches high or low limits (MV_HiLim, MV_LoLim), the integrator automatically halts integration, preventing saturation.

Table of Contents

Executive Summary

Control engineers implementing Advanced Process Library (APL) regulatory algorithms in SIMATIC PCS 7 V8.2 and V9.0 frequently encounter confusion when referencing technical manuals regarding anti-windup and external integrator presetting. A common misunderstanding involves searching for ExtResOn and ExtReset inputs on the standard continuous controller PIDConL (FB1874) or the diagnostic block ConPerMon (FB1805). These parameters belong exclusively to PIDConR (FB1875), the restartable PID controller designed for override, select, and batch transition control loops. While PIDConR provides explicit manual manipulation of the integral state via external pins, PIDConL delivers fully automated internal anti-windup limiting that freezes the integral accumulator whenever physical actuator thresholds are reached.

Architecture and Fundamental Mechanics

The mathematical and algorithmic divergence between PIDConL and PIDConR stems from their intended application domains:

1. PIDConL Built-In Anti-Windup Mechanics

In PIDConL, the algorithm continuously evaluates the calculated manipulated variable against configured actuator boundaries (MV_HiLim and MV_LoLim):
- When the actuator reaches an output limit (e.g., $MV = 100\%$ on a fully open valve) while control error ($e = SP - PV$) persists, the algorithm automatically clamps the integrator.
- The integration accumulation is frozen ($\Delta I = 0$) until the sign of the error reverses, indicating that process recovery has begun.
- This prevents 'windup'—the phenomenon where an integrator accumulates enormous imaginary error that requires minutes or hours to unwrap.
- For external override, PIDConL provides tracking inputs (MV_TrkOn and MV_Trk), which force the entire output rather than just the integrator.

2. PIDConR External Reset Mechanics (ExtResOn and ExtReset)

PIDConR was engineered for complex override, split-range, and cascade configurations where a secondary controller must remain primed and ready to assume control without bumping the process:
- ExtReset: An analog input parameter representing the desired baseline value of the controller output.
- ExtResOn: A boolean control input. When ExtResOn = 1, the controller forces its internal integral memory to equal $(ExtReset - P - D)$, ensuring that the total calculated output $MV$ precisely tracks $ExtReset$.
- When ExtResOn drops back to 0, PIDConR smoothly resumes normal PID integration from the exact level of the external reset signal.

Step-by-Step Implementation Procedure

To properly implement external reset or anti-windup control depending on application requirements:

Scenario A: Configuring Standard Anti-Windup on PIDConL

  1. In your CFC chart, place a PIDConL block instance.
  2. Configure actuator output limits:
    - Set MV_HiLim = $100.0\%$ (or maximum valve opening).
    - Set MV_LoLim = $0.0\%$ (or minimum valve opening).
  3. Anti-windup functions automatically. No additional CFC logic or external reset inputs are required.
  4. If output tracking during interlocks is required, connect the fallback value to MV_Trk and activate via MV_TrkOn = 1.

Scenario B: Implementing External Integrator Reset on PIDConR

  1. Replace PIDConL with PIDConR from the APL library (or use template PIDConR_ConPerMon).
  2. Locate the inputs ExtResOn and ExtReset (ensure they are visible in CFC Object Properties -> I/O tab).
  3. Connect the tracking signal (e.g., the output of an active override controller or manual bias) to PIDConR.ExtReset.
  4. Connect the override activation logic (e.g., high-pressure trip condition) to PIDConR.ExtResOn.
  5. Compile and download CFC changes to the Automation Station.

Verification

To verify controller performance:

  1. PIDConL Anti-Windup Verification:
    - In CFC online test mode, force a large setpoint step causing $MV$ to saturate at $100.0\%$.
    - Monitor the internal integral component. Confirm that it stops increasing once $MV_HiLim$ is reached.
    - Lower the setpoint below $PV$. Observe that $MV$ drops immediately without delayed unwinding time.

  2. PIDConR External Reset Verification:
    - With PIDConR in Automatic mode, assert ExtResOn = 1 with ExtReset = 45.0\%.
    - Confirm that output MV locks instantly to $45.0\%$.
    - De-assert ExtResOn = 0. Confirm that the controller smoothly resumes integral control starting from $45.0\%$.

Limitations and Operational Precautions

Operational limitations and precautions:

  1. Template Selection: If control performance monitoring is required alongside restartable PID control, instantiate PIDConR_ConPerMon rather than standard PIDConL_ConPerMon.
  2. Block Footprint: PIDConR consumes slightly more work memory in the S7-400 CPU than PIDConL due to its dual tracking registers.
  3. Bumpless Parameter Changes: In both blocks, ensure parameter Feature.Bit4 ('Bumpless switchover to automatic mode') is parameterized according to process requirements.
  4. Commercial Disclaimer: Verify all software libraries, engineering licenses, and system packages with an authorized Siemens distributor or the Siemens Industry Mall.

Engineer FAQ

Why can't I find ExtResOn and ExtReset on the PIDConL block?

These parameters belong exclusively to PIDConR (the restartable PID controller). PIDConL manages anti-windup internally without external reset inputs.

Does PIDConL suffer from integrator windup?

No. PIDConL features automatic internal anti-windup clamping that freezes integration whenever $MV$ reaches configured high or low limits.

When should I use PIDConR instead of PIDConL?

Use PIDConR when designing override controllers, selector control schemes, or batch processes requiring external integrator presetting.

What is the function of the ExtReset input in PIDConR?

ExtReset provides the target analog value to which the internal integrator will synchronize when ExtResOn = 1.

How does PIDConL handle external tracking?

PIDConL provides the parameters MV_Trk (tracking value) and MV_TrkOn (tracking enable), which force the total controller output to a predetermined value.

Technical References

Related Articles

Related Tags

  • PIDConL
  • PIDConR
  • Anti-Windup
  • ExtReset
  • APL Controllers
20 respuestas