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

Activating Disabled APL_ANALOG_OP_DISPLAY Faceplate Elements in SIMATIC PCS 7

Activating Disabled APL_ANALOG_OP_DISPLAY Faceplate Elements in SIMATIC PCS 7

The APL_ANALOG_OP_DISPLAY object copied from @PCS7ElementsAPL.pdl remains permanently disabled and greyed out in runtime when its operational permission attributes are unconfigured. Specifically, LinkTag3 must connect to the block's OS_PermLog or OS_Perm_Out tag, and BitIndex4 must reference the exact permission bit that enables analog setpoint modification. If testing without an AS permission tag, setting LinkTag3 statically to +1 with BitIndex4 set to 0 enables the element. Furthermore, the logged-in operator must hold WinCC User Administrator Authorization Level 5 or 6, and the picture window must define an active TagPrefix.

Table of Contents

Executive Summary

When developing custom WinCC faceplates or embedding Advanced Process Library (APL) operator elements into custom process screens in SIMATIC PCS 7 V9.0, engineers often copy the APL_ANALOG_OP_DISPLAY object from @PCS7ElementsAPL.pdl. However, upon opening the faceplate in runtime, the analog display appears visually inactive, clicks do not trigger the numeric input or analog limit dialog, and the control behaves as read-only. This occurs because APL faceplate elements are designed with built-in multi-layered security and operational permission checks. Unlike basic WinCC text or I/O fields, APL_ANALOG_OP_DISPLAY continuously queries permission tags (LinkTag3), bit masks (BitIndex4), and WinCC User Administrator authorizations before unlocking user input.

Architecture and Fundamental Mechanics

The operational logic of APL_ANALOG_OP_DISPLAY relies on three interconnected runtime parameters defined within the APL Style Guide architecture:

1. Permission Evaluation Pipeline: LinkTag3 and BitIndex4

In @PCS7ElementsAPL.pdl, the click event script (OnLButtonDown) and visual status script of APL_ANALOG_OP_DISPLAY evaluate operator permissions dynamically:
- LinkTag3: Connects to the permission word of the target block, typically OS_PermLog (logged operator permissions) or OS_Perm_Out generated by the AS block (e.g., PIDConL or OpAnL).
- BitIndex4: An integer defining the specific bit inside LinkTag3 that authorizes this operation (for instance, Bit 2 for internal setpoint change, Bit 4 for limit modifications).
- If LinkTag3 is left empty or defaults to -1 (unconnected), the internal C-script interprets the permission as zero (forbidden), disabling mouse clicks and rendering the text in disabled grey.
- To bypass the AS permission tag during testing, configuring LinkTag3 statically as +1 (or connecting to an internal tag with value 1) and setting BitIndex4 to 0 resolves the check as TRUE.

2. WinCC User Administrator and TagPrefix Hierarchy

Beyond tag-level permissions, the control validates the logged-in user's role:
- The property Authorization must match an active WinCC user authorization level (Level 5 'Process controlling' for basic changes, or Level 6 'Higher process controlling' for critical limits).
- The hosting Picture Window must have a populated TagPrefix matching the instance name of the CFC block (e.g., Plant/Unit/TIC101.). Without TagPrefix, relative tag links (LinkTag3 = OS_PermLog) fail to resolve against the WinCC tag database.

Step-by-Step Implementation Procedure

To properly configure and activate APL_ANALOG_OP_DISPLAY in a custom faceplate:

Step 1: Configure LinkTag Properties in Graphics Designer

  1. Open the custom faceplate PDL (e.g., @PG_CustomBlock_Standard.pdl) in WinCC Graphics Designer.
  2. Select the APL_ANALOG_OP_DISPLAY object and open the Object Properties dialog.
  3. Under the Parameters (or Links) property group, locate:
    - LinkTag1: Connect to the primary analog value (e.g., SP_Op or SP_Int).
    - LinkTag2: Connect to the high/low limit structure or unit tag if applicable.
    - LinkTag3: Connect to OS_PermLog (or OS_Perm_Out).
  4. Under property BitIndex4, enter the integer corresponding to the permitted operation bit (e.g., 0 or 1 depending on custom block SCL).
  5. Testing Shortcut: If no permission tag exists on your custom block, set the static value of LinkTag3 to +1 (or enter 1 as a static constant) and set BitIndex4 to 0.

Step 2: Configure Operator Authorization Level

  1. In the Object Properties of APL_ANALOG_OP_DISPLAY, locate the Authorization property.
  2. Assign Authorization Level 5 (Process controlling) or Level 6 (Higher process controlling).
  3. Ensure the OpLevel property aligns with the standard APL hierarchy.

Step 3: Validate TagPrefix on Picture Window

  1. If this object is embedded inside a picture window, verify that the calling script passes the correct TagPrefix.
  2. Open APDiag (apdiag.exe -> Output Window) and confirm no tag connection errors (Tag not found: OS_PermLog) occur when clicking the element.

Verification

To verify that APL_ANALOG_OP_DISPLAY is fully operational:

  1. Runtime Visual Check:
    - Launch WinCC Runtime with an operator logged in possessing Level 5 authorization.
    - Verify that the numeric text appears crisp and black/white (not dimmed grey).

  2. Interaction and Faceplate Popup:
    - Click on the APL_ANALOG_OP_DISPLAY element.
    - Confirm that the APL analog input keypad / slider dialog (@PG_APL_OA_Analog101.pdl or @PG_APL_OA_AnalogLimit.pdl) opens immediately.
    - Enter a new value and verify that it successfully writes to the target AS block.

Limitations and Operational Precautions

Operational limitations and precautions:

  1. Custom SCL Block Alignment: If using a custom AS block, the block must declare S7_m_c = 'true' on all tags mapped to LinkTag1, LinkTag2, and LinkTag3.
  2. Style Guide Compliance: Modifying standard scripts inside @PCS7ElementsAPL.pdl directly is prohibited by Siemens engineering standards; always copy elements into project-specific faceplates (@PG_...).
  3. Static Value Syntax: In WinCC Graphics Designer, static string properties vs numeric properties must match exact C-data types. Setting LinkTag3 as a string "1" when a tag name is expected will fail tag resolution.
  4. Commercial Disclaimer: Verify all software libraries, engineering options, and SIMATIC PCS 7 versions with an authorized Siemens distributor or the Siemens Industry Mall.

Engineer FAQ

Why is APL_ANALOG_OP_DISPLAY greyed out even when logged in as Administrator?

Even full administrators cannot operate the control if LinkTag3 is unconnected or evaluates to zero. In APL, tag-level operational permission (OS_PermLog) takes precedence over WinCC user levels.

How do I enable the control if my custom AS block does not have OS_PermLog?

Set LinkTag3 to a static integer value of +1 (or connect it to an internal tag set to 1) and configure BitIndex4 to 0.

What is the function of BitIndex4?

BitIndex4 defines which specific bit of the 32-bit permission DWORD (OS_PermLog) governs this individual display element.

Which popup window opens when clicking APL_ANALOG_OP_DISPLAY?

It typically opens @PG_APL_OA_Analog101.pdl (standard setpoint keypad) or @PG_APL_OA_AnalogLimit.pdl depending on the configured OpAreaPicture property.

Where can I find detailed definitions of all APL element properties?

Consult the official Siemens manual 'SIMATIC PCS 7 APL Style Guide', which documents all standard element attributes, dynamic scripts, and permission bit mappings.

Technical References

Related Articles

Related Tags

  • APL Elements
  • WinCC Faceplate
  • OS_PermLog
  • LinkTag3
  • BitIndex4
20 respuestas