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

Retaining Duplicate SFC Type Block Icons Across OS Compiles in SIMATIC PCS 7

Retaining Duplicate SFC Type Block Icons Across OS Compiles in SIMATIC PCS 7

To prevent a duplicate block icon for an SFC Type instance from being deleted during an OS compile ('Create/update block icons'), open the copied block icon's properties in WinCC Graphics Designer, navigate to Object Properties > General, and remove the leading '@' symbol from the 'type' attribute (for example, changing '@SFC_Type/1' to 'SFC_Type/1' or a custom descriptor). The PCS 7 OS compiler and Plant Hierarchy generation tools exclusively track and delete managed icons prefixed with '@'; removing this symbol converts the icon into an unmanaged static instance that preserves its process connections while surviving subsequent OS compiles.

Table of Contents

Executive Summary

In SIMATIC PCS 7 operator stations, block icons represent the primary visualization and operator control interface for technological blocks and SFC types in WinCC process pictures. While the standard Plant Hierarchy workflow automatically generates one block icon per chart block or SFC instance on the picture assigned to that hierarchy folder, operational requirements often dictate placing secondary or duplicate block icons across multiple process screens (such as summary overview displays, area headers, or multi-unit monitoring screens).

When a standard block icon is copied and pasted onto another picture, the OS compile process ('Create/update block icons') identifies the duplicate icon as an orphaned or redundant managed object and automatically removes it. For standard APL blocks, engineers prevent deletion by altering the Type attribute under the System property group. However, SFC Type block icons possess a different internal property structure where system properties are omitted. This guide details the fundamental mechanism of OS block icon management, provides the exact procedure to decouple duplicate SFC icons from automatic cleanup routines by removing the @ prefix, and outlines lifecycle management rules for persistent multi-screen SFC visualization.

Architecture and Fundamental Mechanics

The PCS 7 OS compiler manages the lifecycle of WinCC block icons through the 'Create/update block icons' wizard. During compilation, the wizard queries the ES plant hierarchy, identifies all CFC instances and SFC types marked with the 'OCM' (Operator Control and Monitoring) attribute, and scans the target process picture for matching graphical objects.

The wizard uses internal naming and attribute conventions to distinguish between managed system icons and user-created static objects:
1. Template Naming: Managed icons are instantiated from @PCS7Typicals... template pictures. Their internal type attribute follows the syntax @<TypeName>/<IconVariant> (for example, @SFC_Type/1 or @SFC_TYPE_PB/1).
2. Managed Identification: The leading @ character serves as an explicit marker indicating to the OS compiler that the object is managed by the system. During an OS compile, any icon in a process picture whose type attribute starts with @ is evaluated against the current ES hierarchy.
3. Duplicate Deletion Logic: If the compiler detects an icon whose tag connection points to an SFC instance that does not belong to that specific hierarchy folder, or detects a second icon for the same SFC instance within managed scope, the compiler treats the icon as invalid or redundant and purges it from the picture file (.pdl).

For standard APL blocks, the icon structure contains an explicit property group System with property Type. SFC Type block icons, historically derived from the SFC visualization subsystem, encapsulate their configuration under the General property group with an attribute labeled type. By stripping the leading @ symbol from this attribute (converting @SFC_Type/1 to SFC_Type/1), the OS compiler's filtering logic ignores the object during compilation sweeps, ensuring that the object remains untouched while preserving all dynamic WinCC tag connections and faceplate opening scripts.

Step-by-Step Implementation Procedure

Step 1: Copy the Generated SFC Type Block Icon

  1. In SIMATIC Manager, perform an initial OS compile with 'Create/update block icons' enabled so the system generates the primary SFC block icon in its designated plant hierarchy picture.
  2. In WinCC Explorer, open the source picture in Graphics Designer.
  3. Select the generated SFC Type block icon, right-click, and select Copy (or press Ctrl+C).

Step 2: Paste and Relocate the Icon on the Target Screen

  1. Open the target secondary process picture (e.g., an area overview or summary graphic) in Graphics Designer.
  2. Paste the icon into the desired position (Ctrl+V).

Step 3: Modify the Type Attribute to Strip the '@' Prefix

  1. Right-click the newly pasted SFC block icon and select Properties to open the Object Properties dialog.
  2. In the left navigation pane of the Object Properties dialog, select General (or inspect Properties > General).
  3. In the right pane, locate the attribute named type.
  4. Double-click the current string (e.g., @SFC_Type/1 or @SFC_TYPE_PB/1).
  5. Edit the value to remove the @ symbol at the very beginning of the name (e.g., change @SFC_Type/1 to SFC_Type/1, or enter a custom name such as SFC_Type_Manual/1).
  6. Press Enter to confirm the change.

Step 4: Verify Tag Connections and Dynamic Tooltips

  1. In the Object Properties dialog, select the Links tab or inspect the Tag attribute.
  2. Ensure the dynamic tag connection still points to the correct SFC instance runtime tag prefix (e.g., Plant/Unit1/SFC_Inst).
  3. Save the process picture in Graphics Designer.

Step 5: Execute an OS Compile to Validate Persistence

  1. In SIMATIC Manager, right-click the OS station and select Compile.
  2. In the OS Compile wizard, ensure the option 'Create/update block icons' is checked.
  3. Complete the compilation process.

Verification

  1. After the OS compile finishes without errors, re-open the secondary process picture in Graphics Designer.
  2. Verify that the secondary SFC block icon is still present on the picture canvas and has not been deleted.
  3. Open WinCC Runtime on the engineering station or an OS client.
  4. Navigate to the secondary process picture and observe the SFC block icon.
  5. Verify that the icon dynamically displays the active SFC operating state (e.g., 'Ready', 'Running', 'Held', 'Completed') and active step number.
  6. Click the block icon and confirm that the standard SFC faceplate opens with operator control permissions intact.

Limitations and Operational Precautions

  1. Once the @ prefix is removed, the block icon will no longer receive automated structural updates if the master template in @PCS7Typicals... is updated or replaced during a library upgrade.
  2. If the SFC Type instance is renamed or deleted in SIMATIC Manager, the unmanaged duplicate block icon will not be deleted automatically and must be removed manually from the picture.
  3. Modifying the type attribute does not update the underlying dynamic tags if the instance tag prefix changes; tag updates must be performed manually or via the WinCC Dynamic Wizard / Linking tool.
  4. Do not alter the underlying object script events (such as mouse click actions) while modifying properties, as this may break standard faceplate opening functionality.

Engineer FAQ

Why does the OS compiler delete duplicate block icons by default?

The OS compiler enforces consistency between the Plant Hierarchy and WinCC process pictures. Any icon marked with '@' that does not match the strict single-instance hierarchy mapping is flagged as orphaned and deleted.

Is removing the '@' symbol supported for standard APL block icons as well?

Yes. For APL blocks, you modify the Type property under the System property tab (e.g., changing @MotL/1 to MotL/1). For SFC Type icons, the property is located directly under General.

What happens to the secondary icon if I perform a full OS Compile with memory reset?

The secondary icon remains intact in the picture file because the OS compiler ignores any picture object whose type attribute does not begin with '@'.

Can I create more than two block icons for the same SFC instance?

Yes. You can paste as many duplicate icons as needed across different screens, provided that all duplicates have the @ prefix removed from their type attribute.

Do duplicate block icons require additional WinCC Runtime or Process Object licenses?

No. WinCC licensing is based on process tags and archive tags, while PCS 7 AS/OS runtime licensing is based on Process Objects (PO). Duplicate block icons referencing an existing SFC instance consume zero additional POs or tags.

Technical References

Related Articles

Related Tags

  • SFC Type
  • Block Icons
  • OS Compile
  • WinCC Graphics Designer
  • Plant Hierarchy
20 respuestas