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

Configuring Block Icon Preserved Properties and @@PCS7Typicals.cfg in SIMATIC PCS 7 APL

Configuring Block Icon Preserved Properties and @@PCS7Typicals.cfg in SIMATIC PCS 7 APL

In SIMATIC PCS 7 with the Advanced Process Library (APL, V8.x and V9.x), the properties of existing block icons that are preserved or overwritten during OS compilation ('Create/update block icons') are governed by the configuration file @@PCS7Typicals.cfg located in the OS project's GraCS directory. When an engineer modifies visual properties (such as TrendColor3 or TrendConfiguration3) on a template icon in @PCS7Typicals_APL.pdl or a custom @PCS7Typicals.pdl, existing instances in process pictures will not update if those properties are protected under the [PreservedProperties] section of @@PCS7Typicals.cfg. To force OS compilation to update existing block icons with the new template properties, engineers must remove the specific property from [PreservedProperties] in @@PCS7Typicals.cfg, increment the 'version' property of the Customized Object in the template picture, or execute the Dynamic Wizard 'Update Picture Objects' using @TemplateControlAPL.cfg.

Table of Contents

Architecture of Block Icon Property Preservation During OS Compilation

When an engineer designs human-machine interface graphics in SIMATIC PCS 7, process pictures (.pdl) contain hundreds of instantiated block icons representing field motors, valves, and instruments. During initial creation, the OS Compiler places these icons from template pictures (@PCS7Typicals_APL.pdl) and positions them on screen.

Over the plant lifecycle, an engineer may manually reposition an icon, adjust an instance-specific label, or alter an individual trend color inside Graphics Designer.

If the OS Compiler completely overwrote every property of every block icon during subsequent compilations, all manual screen placements and custom tweaks would be destroyed!

To balance automated synchronization with engineering flexibility, PCS 7 implements a Property Preservation Architecture:
1. When Create/update block icons executes, the compiler scans existing icons in process pictures.
2. It consults an internal configuration rulebook that specifies which properties are System Maintained (overwritten by the compiler, such as tagname and dynamic tag connections) and which properties are Preserved (retained from the existing graphic instance, such as coordinates Left, Top, and specific visual attributes).

The Role of @@PCS7Typicals.cfg vs @TemplateControlAPL.cfg

PCS 7 utilizes two distinct configuration files to govern block icon updates, depending on whether the update is triggered by the automated OS Compiler or by manual Graphics Designer wizards:

1. @@PCS7Typicals.cfg (Automated OS Compile Engine)

  • Execution Context: Invoked automatically during WinCC OS Compilation (Compile OS) or when manually executing Options > Plant Hierarchy > Create/Update Block Icons... in SIMATIC Manager.
  • Physical Location: Stored in the OS project directory:
    $$\text{\\wincproj\\GraCS\@@PCS7Typicals.cfg}$$
    (with master defaults located in C:\Program Files (x86)\Siemens\WinCC\apllib\...).
  • Function: Defines the [PreservedProperties] list for batch automated updates.

2. @TemplateControlAPL.cfg / @TemplateControl.cfg (Dynamic Wizard Engine)

  • Execution Context: Invoked inside WinCC Graphics Designer when an engineer runs the Dynamic Wizard > Picture Functions > Update Picture Objects.
  • Physical Location: Stored in the project's GraCS directory or the global WinCC wizards folder.
  • Function: Governs manual, interactive picture-by-picture symbol synchronization against @TemplateAPL.pdl.

Why Template Modifications Fail to Propagate to Existing Icons

When an engineer modifies a template icon in @PCS7Typicals_APL.pdl (for example, modifying TrendColor3 or TrendConfiguration3 on block type MotL) and runs 'Create/update block icons', existing instances in process graphics remain unchanged.

This failure to propagate stems from three specific configuration barriers:
1. Property Listed in [PreservedProperties]: If TrendColor3 is listed under [PreservedProperties] inside @@PCS7Typicals.cfg, the OS Compiler explicitly reads the color from the existing graphic instance, ignores the template's new color, and writes the old color back to the icon!
2. Customized Object Version Not Incremented: The compiler checks the internal property version of the Customized Object. If the template's version string (e.g., 1.0) matches the instance's version string, the compiler assumes the structural definition has not changed and skips updating non-tag attributes.
3. Local Project File Overridden by System Library: If the engineer edits @@PCS7Typicals.cfg in the wrong directory (or if the file is recreated during a software update), the compiler falls back to default preservation rules.

Step-by-Step Procedure to Propagate Template Changes

To permanently update visual properties (such as trend configurations or colors) across all already-placed block icons:

Step 1: Remove Protected Properties from @@PCS7Typicals.cfg

  1. Close WinCC Explorer and SIMATIC Manager.
  2. In Windows Explorer, navigate to the OS project GraCS folder:
    $$\text{\\wincproj\\GraCS}$$
  3. Open @@PCS7Typicals.cfg in a text editor (Notepad).
  4. Locate the section:
    ini [PreservedProperties]
  5. Find the lines corresponding to the properties you want to update (e.g., TrendColor3, TrendConfiguration3).
  6. Delete those lines (or comment them out with a semicolon ;).
  7. Save and close @@PCS7Typicals.cfg.

Step 2: Increment the Version Property in the Template Picture

  1. Open @PCS7Typicals_APL.pdl (or your custom @PCS7Typicals.pdl) in Graphics Designer.
  2. Select the modified block icon (e.g., @MotL/1).
  3. Open Object Properties > General.
  4. Locate the property version (e.g., currently set to 1.0).
  5. Change the version to 1.1 (or increment to next decimal).
  6. Save and close the template picture.

Step 3: Execute Create/Update Block Icons

  1. In SIMATIC Manager, select the OS station.
  2. Select menu Options > Plant Hierarchy > Create/Update Block Icons....
  3. Select the target process pictures and click OK.
  4. The compiler detects the version mismatch, consults the updated @@PCS7Typicals.cfg, overwrites the unprotected trend properties with the new template values, and preserves only coordinates (Left, Top).

Block Icon Configuration Files and Update Matrix

The following matrix details the configuration files governing block icon behavior:

Configuration FileOperational EngineFile LocationPrimary Function@@PCS7Typicals.cfgOS Compiler (Compile OS)Project GraCS folderDefines properties preserved during batch automated compiles@TemplateControlAPL.cfgDynamic Wizard in Graphics DesignerProject GraCS / wizardsControls manual picture-by-picture symbol updates@PCS7Typicals_APL.pdlOS Compiler Master TemplateProject GraCS folderContains master APL block icon symbols and version tags@TemplateAPL.pdlDynamic Wizard TemplateProject GraCS folderContains template symbols for manual wizard replacement

Verification

To confirm that the updated template properties propagated to placed instances:
1. Open a target process picture in Graphics Designer.
2. Select an instantiated block icon that previously held the old trend configuration.
3. Open Object Properties: Inspect the TrendColor3 and TrendConfiguration3 properties.
4. Verify that their values now match the updated values configured in @PCS7Typicals_APL.pdl.
5. Verify that the physical coordinates (Left, Top) of the icon on the canvas remained completely undisturbed.
6. Launch WinCC Runtime: Open the block icon faceplate and confirm that historical trends render with the newly assigned color.

Limitations and Operational Precautions

Observe the following engineering precautions:
- Never Remove Left and Top from PreservedProperties: If you delete Left or Top from [PreservedProperties] in @@PCS7Typicals.cfg, every block icon in your entire plant will be moved to coordinate $(0, 0)$ in the top-left corner of the screen during the next compile!
- Project Archives: Keep a backup copy of your customized @@PCS7Typicals.cfg. During PCS 7 version migrations or library updates, Siemens installers may overwrite template configuration files in system folders.
- Custom Typicals Naming: Always place customized templates in @PCS7Typicals.pdl or @PCS7Typicals<Custom>.pdl rather than directly modifying @PCS7Typicals_APL.pdl.

Engineer FAQ

Why did removing the property from @@PCS7Typicals.cfg still fail to update the icon?

Because the 'version' property of the Customized Object in the template picture was not incremented. The OS Compiler checks the version string first; if the version has not changed, it skips updating non-essential visual properties.

Where is @@PCS7Typicals.cfg located?

It is located directly inside the WinCC project's GraCS folder: \\wincproj\\GraCS\@@PCS7Typicals.cfg.

What happens if Left and Top are removed from [PreservedProperties]?

Removing Left and Top causes the OS Compiler to reset the position of every block icon in the plant back to the default coordinates defined in the template picture, destroying all manual screen layouts.

Technical References

Related Articles

Related Tags

  • Block Icons
  • @@PCS7Typicals.cfg
  • WinCC
  • OS Compilation
  • APL
  • Graphics Designer
  • SIMATIC PCS 7
6 respuestas