Freezing Manipulated Value Output and Pausing Control in APL PIDConL
To freeze the manipulated value (MV) output of an APL PIDConL controller at a constant value during a specific plant operation phase without stopping block execution, use the forced tracking inputs MV_ForOn and MV_Forced. Asserting MV_ForOn = 1 immediately clamps MV to the value of MV_Forced, freezing control output regardless of setpoint or process variable variations. Alternatively, to freeze MV at its current position, wire MV to tracking input MV_Trk and assert MV_TrkOn = 1. Never deactivate the block's EN (Enable) input, as disabling EN halts cyclic execution, creates derivative gain spikes upon re-enabling, and causes severe process bumps.
Table of Contents
- APL PIDConL Control Modes and Output Overrides
- Why Deactivating Block Enable (EN) is Operationally Dangerous
- Method 1: Clamping Output via Forced Tracking (MV_ForOn / MV_Forced)
- Method 2: Freezing Current Value via Output Tracking (MV_TrkOn / MV_Trk)
- Comparison of PIDConL Output Freezing Techniques
- Verification
- Limitations and Operational Precautions
- Engineer FAQ
- Technical References
- Related Articles
- Related Tags
APL PIDConL Control Modes and Output Overrides
In industrial process automation, continuous PID controllers (such as the APL block PIDConL FB 1874) frequently require pausing during batch holds, catalyst injection pauses, or auxiliary flushing phases. While the plant waits, the control valve must remain immobilized at a fixed opening (e.g. 0%, 50%, or current position) without accumulating integral error ($I$-windup).
Why Deactivating Block Enable (EN) is Operationally Dangerous
Engineers unfamiliar with continuous control principles sometimes attempt to pause controllers by setting EN = 0:
- Halts Internal Time Accounting: Setting
EN = 0suppresses execution of the block algorithm entirely. The internal sample time calculation stops, and message blocks (Alarm_8P) fail to dispatch process alarms. - Massive Derivative and Integral Kick: When
ENis restored to1minutes or hours later, the internal filter evaluates the elapsed time as a single step change. The derivative term ($D$) spikes violently, driving the valve to full open or shut within a single cycle, potentially bursting pipes or blowing relief valves.
Method 1: Clamping Output via Forced Tracking (MV_ForOn / MV_Forced)
To force the valve to an exact, predefined position (e.g., maintaining exactly 25.0% opening during a hold phase):
- Assign the desired fixed position to parameter
MV_Forced(REAL, e.g.25.0). - When the freezing condition triggers, assert
MV_ForOn = 1. PIDConLinstantly clampsMV = 25.0, halts integral accumulation, and sets feature bit feedback flags.- When
MV_ForOnreturns to0, control resumes smoothly according to configured anti-windup rules.
Method 2: Freezing Current Value via Output Tracking (MV_TrkOn / MV_Trk)
To freeze the valve at whatever position it occupied the moment the pause occurred:
- Wire the current output
PIDConL.MV(or valve position feedback) into tracking inputMV_Trk. - Assert
MV_TrkOn = 1upon initiating the pause. - While
MV_TrkOn = 1, the controller halts PID calculation and maintainsMV = MV_Trk. - When
MV_TrkOntransitions back to0, the controller resumes automatic calculation with zero bump.
Comparison of PIDConL Output Freezing Techniques
The table below contrasts methods for freezing manipulated values in PIDConL:
MV_ForOn = 1, MV_ForcedMV_TrkOn = 1, MV_TrkManModLi = 1, ManHold = 1EN = 0Verification
Verify output freezing and bumpless resumption in CFC:
- Open the CFC chart online with
PIDConLin automatic mode (AutAct = 1) controlling a live or simulated loop. - Note the active valve output (e.g.
MV = 42.5%). - Assert
MV_TrkOn = 1; confirm thatMVremains frozen at42.5%despite inducing deliberate changes inSPorPV. - Change process input
PV_In; confirm the integral error accumulator does not wind up. - Reset
MV_TrkOn = 0; confirmPIDConLsmoothly transitions back into closed-loop control without valve surging.
Limitations and Operational Precautions
Observe the following safeguards when manipulating PID outputs:
- Feature Bit Verification: Verify
Feature.Bit5(Tracking behavior) to ensure tracking takes precedence over manual commands. - Alarm Suppression: During prolonged forced periods, consider asserting
MsgLock = 1to suppress nuisance control deviation alarms (ER_Alarm). - Anti-Windup Limits: Ensure
MV_HiLimandMV_LoLimremain properly clamped to prevent invalid tracking values.
Engineer FAQ
Why is disabling the EN input on a PID block considered dangerous?
Disabling EN suspends cyclic time tracking. When re-enabled, the algorithm evaluates the elapsed time as a single timeslice, producing an enormous derivative spike that slams control valves and destabilizes the process.
What is the difference between MV_Forced and MV_Trk?
MV_Forced forces the output to a specified numeric value regardless of operating mode. MV_Trk tracks a dynamic external signal (such as actual valve feedback) to provide bumpless synchronization.
Can operators override MV_Forced from the WinCC faceplate?
No. Forced inputs (MV_ForOn) originate from automation logic and take priority over manual faceplate commands to ensure process safety overrides.
Technical References
- SIMATIC PCS 7 Advanced Process Library (APL) Function Manual: https://support.industry.siemens.com/cs/ww/en/view/109780765
- SIMATIC S7-300/400 PID Control Function Blocks Manual: https://support.industry.siemens.com/cs/ww/en/view/109756486
- Advanced Process Control Concepts in SIMATIC PCS 7: https://support.industry.siemens.com/cs/ww/en/view/102601737
Related Articles
- Multiplexing Dual PID Controller Outputs to a Single Analog Output in SIMATIC PCS 7 CFC
- Configuring Normalization Range on CTRL_PID with Thermocouple Inputs in SIMATIC PCS 7
- Preserving Motor Command States and Operating Modes After Fault Reset in APL MotSpdCl
Related Tags
- PIDConL
- MV_Forced
- MV_TrkOn
- Bumpless Transfer
- Output Freezing
- APL Control