Diagnosing Unexpected Manipulated Values and Safe Position Behavior in PCS 7 APL VlvAnL

In SIMATIC PCS 7 Advanced Process Library (APL), when an analog control valve block VlvAnL in Automatic mode outputs an unexpected manipulated value (such as holding 15% instead of closing to 0%) upon an interlock trip (Intlock = 0), the behavior is caused by the parameter SafePos being configured to 2 (Stop / Hold last position). In VlvAnL, SafePos = 0 drives the valve to its low limit (closed), SafePos = 1 drives it to its high limit (open), and SafePos = 2 freezes the valve at its last position. Additionally, interconnecting external signals to MV_Int is an anti-pattern that creates feedback conflicts because MV_Int is an internal tracking parameter written back by the block algorithm.

Executive Summary

Analog control valves are primary final control elements regulating flow, pressure, and temperature across process plants. In the SIMATIC PCS 7 Advanced Process Library (APL), the VlvAnL function block coordinates analog positioning, auxiliary open/close valves, operator setpoints, and protective interlocking. Commissioning engineers frequently encounter puzzling behavior where, following an interlock activation (Intlock = 0), the manipulated output MV remains frozen at an intermediate operating value (e.g. 15%) rather than driving the valve completely closed. Furthermore, engineers often wire external signals to both internal and external setpoint pins (MV_Int and MV_Ext), causing tracking discrepancies. This article explains the safe position logic of VlvAnL, clarifies the internal setpoint tracking architecture, and details verified parameter settings.

Architecture and Fundamental Mechanics

VlvAnL Safe Position Mechanics, Interlock Actions, and Internal Tracking Architecture:

The Role and Settings of the Parameter SafePos:
Whenever a protective interlock (Intlock = 0, Protect = 0), permit failure (Permit = 0), or emergency stop condition occurs, VlvAnL forces the manipulated value MV to its predefined Safe Position (Ruhelage).
The safe position behavior is dictated exclusively by the configuration parameter SafePos:
- SafePos = 0 (Default: Closed): The block drives the output to the low limit: MV.Value = MV_LoLim (typically 0.0%).
- SafePos = 1 (Open): The block drives the output to the high limit: MV.Value = MV_HiLim (typically 100.0%).
- SafePos = 2 (Stop / Freeze): The block holds the last manipulated value: MV.Value remains frozen at whatever value it held at the exact cycle the interlock occurred.
If an engineer intended the valve to fail-close on an interlock trip, configuring SafePos = 2 causes the exact failure reported: the valve remains frozen at 15% instead of closing.
Manipulated Value Routing: External (MV_Ext) vs. Internal (MV_Int):
MV_Ext: Dedicated input for automated continuous control (e.g. connected to the output of a PID controller PidConL.MV).
MV_Int: Internal operator setpoint used in Manual mode.
The Algorithm Write-Back Rule: During Automatic mode (AutAct = 1), the VlvAnL block algorithm continuously writes the current effective output back into MV_Int to guarantee bumpless transfer when an operator switches from Auto to Manual.
If an engineer interconnects an external signal directly to MV_Int in CFC, the block's internal write-back mechanism collides with the external connection, causing status display inconsistencies between online CFC views and faceplates.

Step-by-Step Implementation Procedure

Inspect the SafePos Parameter in CFC:
* Open the CFC chart hosting the VlvAnL instance.
* Locate the block parameter SafePos.
* Check its configured value. If it is set to 2, change it to 0 (to drive the valve closed upon interlock) or 1 (if fail-open is required).
Remove External Interconnections from MV_Int:
* In the CFC chart, inspect the input pin MV_Int.
* If MV_Int is interconnected to an external block or signal source, delete the interconnection.
* Ensure external automated setpoints (from PID or recipe logic) connect exclusively to MV_Ext.
* Connect the automated mode selection signal to MV_ExtAct or use ModLiOp = 1 with AutModLi = 1.
Verify Auxiliary Valve Configuration (Feature.Bit5):
* Inspect Feature.Bit5 ('Auxiliary valve available').
* If the physical valve has no auxiliary shutoff valve, ensure Feature.Bit5 = 0.
* Note that when no auxiliary valve is used, manual mode strictly utilizes internal setpoint tracking.
Compile and Download Changes:
* Compile CFC charts with 'Changes only'.
* Download changes to the CPU in RUN mode.

Verification

In WinCC Runtime, open the VlvAnL faceplate and place the valve in Automatic mode with an active setpoint of 15%.
Simulate an interlock condition by setting Intlock = 0 in CFC.
Observe that the faceplate indicates an active Interlock and the manipulated value output MV immediately drops to 0.0%.
Reset the interlock (Intlock = 1); confirm that the valve smoothly ramps or steps back to the active external setpoint.

Limitations and Operational Precautions

Altering SafePos changes plant safety response during emergency trips. Always consult the plant Piping and Instrumentation Diagram (P&ID) and Process Safety Requirements before changing a control valve's safe position between Closed, Open, and Stop.

Engineer FAQ

Why did VlvAnL hold 15% instead of closing when the interlock tripped?

The parameter SafePos was set to 2 (Stop / Hold last position). Set SafePos = 0 to drive the valve closed upon an interlock.

What are the settings for SafePos in VlvAnL?

SafePos = 0 means Closed (MV_LoLim); SafePos = 1 means Open (MV_HiLim); SafePos = 2 means Stop (Hold last valid value).

Should I connect an external signal to MV_Int?

No. MV_Int is an internal tracking parameter for Manual mode written back by the block algorithm. Connect external control signals to MV_Ext.

What does Feature.Bit5 do in VlvAnL?

Feature.Bit5 enables or disables the auxiliary shutoff valve logic associated with the analog control valve.

Can SafePos be modified online in RUN mode?

Yes, SafePos is an offline/online configurable parameter that can be changed in CFC and downloaded without stopping the CPU.

Technical References

20 respuestas

Diagnosing Unexpected Manipulated Values and Safe Position Behavior in PCS 7 APL VlvAnL