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

Configuring APL OpDi01 for Single-Button Toggle Mode Versus Classical OpD Behavior in PCS 7

Configuring APL OpDi01 for Single-Button Toggle Mode Versus Classical OpD Behavior in PCS 7

In SIMATIC PCS 7 Advanced Process Library (APL), the digital operator block OpDi01 (FB 1866) defaults to a two-button operational model (separate SetOp and RstOp commands) to prevent ambiguous operator inputs. To emulate the single-button toggle behavior of the classical PCS 7 Standard Library OpD block without rewriting internal WinCC faceplate scripts, configure the block attribute Text 1 to the identical label on both SetOp and RstOp inputs in CFC. In WinCC Runtime, because OpDi01 dynamically disables the currently active command via OS permissions and internal state feedback, only the inactive command button is operable. Consequently, the faceplate presents a single contextual button that alternates between Set and Reset states. Alternatively, connect Out.Value through an external toggle flip-flop in CFC.

Table of Contents

Executive Summary

Process automation systems frequently utilize digital operator blocks to allow control room operators to enable sequences, acknowledge interlocks, or toggle operational modes from WinCC faceplates. In legacy PCS 7 Standard Library projects, the OpD block supported a single-button pushbutton interface. When migrating to or engineering within the Advanced Process Library (APL), engineers notice that OpDi01 provides two separate commands: SetOp (Turn On) and RstOp (Turn Off). While dual-button control adheres to ISA-101 and NAMUR safety guidelines against accidental toggles, specific plant requirements still call for single-button interfaces. Understanding how APL evaluates OS permissions, button labels, and internal feedback allows engineers to implement single-button operational paradigms seamlessly.

Architecture and Fundamental Mechanics

The operator interface and execution mechanics of OpDi01 differ fundamentally from classical blocks:

  1. The APL Dual-Command Philosophy:
    * Standard APL technological design avoids indeterminate toggling by segregating commands into discrete SetOp and RstOp parameters.
    * Each command maintains independent OS permission bits (OS_Perm.Bit0 and Bit1), process interlocks, and audit trail operator message declarations.
  2. Dynamic Button Arbitration in APL Faceplates:
    * The WinCC APL faceplate for OpDi01 does not render hardcoded static buttons; it queries the runtime status of Out.Value and the configured OS permission attributes.
    * When Out.Value = 0, the block requires a SetOp pulse to assert; RstOp is deemed redundant and automatically greyed out (inoperable).
    * When Out.Value = 1, the block requires a RstOp pulse; SetOp is greyed out.
  3. The Shared Label Configuration Strategy:
    * If both SetOp and RstOp are assigned the identical text string in their Text 1 property (e.g., 'Execute' or 'Toggle Mode'), the operator sees a single operational control in the standard view.
    * The faceplate illuminates the active operational state while exposing only the valid opposing action, replicating single-button functionality without compromising safety interlocking.

Step-by-Step Implementation Procedure

Follow these procedures to configure OpDi01 for contextual single-button operation in PCS 7:

  1. Instantiate OpDi01 in CFC:
    * In the CFC editor, drag OpDi01 (FB 1866) from Libraries > PCS 7 AP Library > Operation into your technological chart.
  2. Configure Identical Button Text Attributes:
    * In CFC, open the block properties of OpDi01.
    * In the I/Os tab, locate parameter SetOp.
    * Select the attribute Text 1 and enter your desired label (e.g., 'START / STOP' or 'ENABLE').
    * Locate parameter RstOp.
    * Select the attribute Text 1 and enter the exact same string ('START / STOP' or 'ENABLE').
  3. Configure Interlock and Feedback Interconnections:
    * If the command is subject to process conditions, connect the interlocking signal to input Intlock.
    * Ensure Feature.Bit0 = 0 (Operator commands are evaluated in process automation mode).
  4. Compile and Download:
    * Compile CFC charts with 'Scope: Changes only'.
    * Download the changes to the AS controller in RUN mode.
    * Execute an AS-OS compile to transfer updated text attributes to the WinCC Text Library.
  5. Verify Runtime Faceplate Behavior:
    * Open WinCC Runtime on the OS station.
    * Click the block icon for OpDi01 to open the standard faceplate view.
    * Observe that when Out = 0, only the Set action is operable; clicking it turns Out = 1. Once active, the same visual button position now enables the Reset action, cleanly resetting Out = 0.

Verification

In WinCC Runtime, open the faceplate of OpDi01. Verify that only one button is operable at any time. Click the button to toggle Out = 1; confirm that the button status toggles and downstream logic responds. Click the button again to toggle Out = 0. Check the WinCC Alarm Logging Operation List (Bedienmeldungen); verify that distinct operator audit messages are generated for both Set and Reset actions.

Limitations and Operational Precautions

Do not attempt to modify internal WinCC @PG_OpDi01_Standard.pdl scripts directly, as future PCS 7 software updates or OS compilations will overwrite custom script edits. For safety-instrumented systems (SIS), dual-action confirmation buttons must always be maintained to comply with IEC 61511 functional safety standards.

Engineer FAQ

Why did Siemens replace OpD with OpDi01 in APL?

OpDi01 incorporates modern NAMUR NE107 signal status handling, granular OS permission bitmasks, and structured data interfaces not supported by legacy Standard Library blocks.

Can OpDi01 be configured as a momentary pushbutton?

Yes, by connecting the output to logic that resets SetOp automatically, or by evaluating pulse parameters in CFC.

What happens if SetOp and RstOp are asserted simultaneously?

OpDi01 evaluates command priority: by default, Reset (RstOp) takes precedence over Set (SetOp) to guarantee safe shutdown.

Does changing Text 1 require an AS-OS compile?

Yes. The button labels are stored in the AS block attributes and must be transferred into the WinCC Text Library via an AS-OS compile.

Technical References

Related Articles

Related Tags

  • OpDi01
  • OpD
  • APL Operation
  • Faceplates
  • OS Permissions
20 respuestas