Resolving Block Icon Generation Conflicts When Migrating Projects to APL V9: @PCS7Typicals vs @PCS7TypicalsAPLV9

In SIMATIC PCS 7, when compiling an OS and executing 'Create/update block icons' on a project containing both legacy V7 AS stations and new V9 AS stations, the wizard mistakenly generates older block icons instead of modern APL V9 icons because WinCC prioritizes template pictures in alphabetical order. In the project GraCS folder, the legacy template @PCS7Typicals.pdl precedes @PCS7TypicalsAPLV9.pdl. WinCC evaluates the block's 'type' attribute (e.g., @MotL/1): if a matching icon is found in the legacy template, it instantiates the old icon. To resolve this, specify the explicit template file in the block icon wizard, configure the 'type' attribute to reference V9 specifically, or update template files in GraCS.

Executive Summary

Process plants transitioning from PCS 7 V7 to PCS 7 V9 often modernize in stages, maintaining existing S7-400 AS controllers with legacy APL V7 libraries while adding new AS controllers running modern APL V9 libraries to the same multiproject. When engineers execute the 'Create/update block icons' function in WinCC Graphics Designer to populate new graphic screens, they discover that WinCC generates outdated V7-style block icons (with older color palettes and missing status symbols) for the new V9 blocks. This occurs because WinCC scans typical template pictures (@PCS7Typicals*.pdl) in the GraCS directory using fixed search heuristics. This guide explains how the block icon generator selects templates and provides the procedure to force modern V9 block icon creation.

Architecture and Fundamental Mechanics

The PCS 7 automated block icon generation engine operates via template matching in the WinCC Graphics Designer:
1. The Block Icon Creation Workflow:
When 'Create/update block icons' runs, the wizard scans all CFC charts assigned to the OS picture. For each technological block with the attribute S7_m_c := 'true' and parameter type configured (e.g., type = @MotL/1), the wizard searches for a matching icon prototype in template files located in the project GraCS directory.
2. Template File Naming Hierarchy and Search Priority:
- Legacy Templates: @PCS7Typicals.pdl, @TemplateAPL.pdl
- Version-Specific Templates: @PCS7TypicalsAPLV8.pdl, @PCS7TypicalsAPLV9.pdl
By default, WinCC searches all files matching @PCS7Typicals*.pdl in alphabetical order. Because @PCS7Typicals.pdl is evaluated first, if it contains an icon with tag @MotL/1, the wizard instantiates that legacy icon and stops searching, never reaching @PCS7TypicalsAPLV9.pdl.
3. Coexistence of Multiple APL Generations:
In a mixed V7/V9 plant, older AS stations require legacy icons, while new AS stations require modern V9 icons. Standardizing template assignments requires using explicit template file declarations or differentiating icon variant numbers (e.g., configuring type = @MotL/2 or assigning template names in the block icon configuration dialog).

Step-by-Step Implementation Procedure

Verify Template Pictures in WinCC GraCS Directory:
a. Open Windows File Explorer and navigate to <OS_Project>\GraCS\.
b. Check for existing template files:
- @PCS7Typicals.pdl (legacy V7 icons)
- @PCS7TypicalsAPLV9.pdl (modern V9 icons)
  c. If @PCS7TypicalsAPLV9.pdl is missing, copy it from the Siemens installation directory: C:\Program Files (x86)\SIEMENS\WINCC\Options\pdl\ into the OS GraCS folder.
Option A: Configure Explicit Template File in Block Icon Wizard:
a. In WinCC Graphics Designer, open the target process picture (.pdl).
b. Select Tools -> Create/update block icons....
c. In the configuration dialog, inspect the 'Template file' field.
d. By default, it may say @PCS7Typicals.pdl or @PCS7Typicals*.pdl.
e. Change the template file explicitly to @PCS7TypicalsAPLV9.pdl for pictures belonging to the new V9 AS station.
f. Click 'OK' to regenerate block icons: verify that modern V9 icons are instantiated.
Option B: Configure Unique Icon Types on Technological Blocks in CFC:
a. In the master CMT or individual CFC chart for new V9 blocks, open block properties.
b. In the block attributes, locate parameter type (or Block Icon Type).
c. In @PCS7TypicalsAPLV9.pdl, inspect the available icon variants (e.g., variant 1, 2, 3, or customized variants like @MotL/V9).
d. Assign a unique type string that exists only in the V9 template (e.g., set type = @MotL/2 or customize the icon index).
e. Recompile the OS and update block icons.
Option C: Rename or Archive Legacy Typical Files (If V7 Icons are No Longer Needed):
a. If the entire plant is transitioning to V9 graphics, open GraCS.
b. Rename @PCS7Typicals.pdl to @PCS7Typicals_Legacy_V7.bak.
c. Ensure @PCS7TypicalsAPLV9.pdl is the primary template.
d. Re-run 'Create/update block icons' across all plant pictures.

Verification

In WinCC Graphics Designer, inspect the newly generated block icon: confirm it displays modern APL V9 styling, rounded borders, and updated alarm color bars.
In WinCC Runtime, open the faceplate from the new block icon: verify that the faceplate matches APL V9 layout and feature bit indicators.
Check an older graphic picture belonging to the V7 AS: confirm that existing legacy icons and faceplates continue to function without disruption.

Limitations and Operational Precautions

Directly editing system @ template pictures without making backup copies risks having modifications overwritten during future PCS 7 software updates or OS Project Editor executions.

Engineer FAQ

Why did WinCC generate old V7 icons for my new V9 blocks?

Because @PCS7Typicals.pdl appears alphabetically before @PCS7TypicalsAPLV9.pdl in the GraCS directory, causing the wizard to match the legacy icon prototype first.

Can a single OS project host both V7 and V9 block icons?

Yes. By configuring distinct icon variant indices (e.g., variant 1 for V7, variant 2 for V9) or specifying the template file per picture in the wizard, both generations can coexist.

Where are standard APL V9 typical templates installed by default?

In C:\Program Files (x86)\SIEMENS\WINCC\Options\pdl\ under the Siemens installation directory.

What attribute on a CFC block specifies its icon prototype?

The type attribute (e.g., @MotL/1 or @VlvL/2).

Does regenerating block icons delete custom connections on the screen?

No. The block icon wizard updates the icon visual appearance and tags while preserving its position on the screen unless 'Re-arrange icons' is selected.