Resolving Block Icons Not Updating After Type Number Changes - The 10-Picture Typicals Limit

When changing a block icon type number in CFC (e.g. from '@MonAnL/11' to '@MonAnL/12') fails to update the icon on the WinCC process graphic following an OS compilation, the root cause is typically exceeding the 10-picture limit for typicals files, duplicate icon declarations, or disabled compilation options. SIMATIC PCS 7 enforces a hardcoded architectural limit: the OS compiler processes a maximum of ten '@PCS7Typicals' pictures in alphabetical order; any additional typical files are silently ignored. To resolve this: confirm that at most ten '@PCS7Typicals*.pdl' files exist in the OS GraCS directory, verify that the requested icon variant exists uniquely within one of those ten files, and execute 'Options -> Plant Hierarchy -> Create/Update Block Icons' with 'Lower hierarchy levels' selected.

Executive Summary

In SIMATIC PCS 7, the visual representation of technological blocks on operator screens is driven by automated block icon generation based on master templates stored in typicals picture files (@PCS7Typicals.pdl). During plant standardization or graphic revisions, engineers frequently assign a new icon type variant to a CFC block (e.g. switching from standard variant /11 to compact variant /12). However, after performing an AS-OS compilation and download, the graphic screen stubbornly retains the old icon or fails to generate the new icon entirely. This article exposes the little-known 10-file ceiling for typicals pictures in WinCC, explains alphabetical evaluation priority, and provides a verified procedure for ensuring clean block icon updates.

Architecture and Fundamental Mechanics

Block Icon Generation Mechanics and the 10-Picture Typicals Architecture:

How 'Create/Update Block Icons' Works:
In PCS 7, each technological block instance in CFC possesses an attribute named type (e.g. @MonAnL/1, @VlvL/2).
During OS compilation (or when running the 'Create/Update Block Icons' wizard), PCS 7 scans the process pictures assigned to the Plant Hierarchy.
For every block marked with OCM := 'true', the wizard searches the template picture pool for a Customized Object whose type property matches the CFC attribute, instantiating the graphic object in the target .pdl and wiring dynamic tag connections automatically.
The Hardcoded 10-Picture Typicals Limit:
To conserve compilation time and memory, the PCS 7 block icon generation engine queries the OS project's GraCS folder for template pictures named @PCS7Typicals*.pdl.
Crucial Manufacturer Constraint: The compiler sorts all matching files alphabetically and processes only the first 10 picture files (e.g. @PCS7Typicals.pdl, @PCS7Typicals1.pdl through @PCS7Typicals9.pdl).
If an engineering team creates additional template pictures—such as @PCS7Typicals_Custom.pdl or @PCS7Typicals10.pdl—that fall beyond the 10th alphabetical slot, the compiler completely ignores them without issuing a warning! Any custom icons stored inside those ignored files will never be recognized during compilation.
Alphabetical Search Precedence and Shadowing:
If identical icon types (e.g. @MonAnL/12) exist in multiple typicals pictures, the compiler takes the icon from the first picture encountered in alphabetical order, shadowing any definitions in subsequent files.

Step-by-Step Implementation Procedure

Audit Typicals Picture Files in the OS Project:
* In Windows File Explorer, open the OS project graphics directory:
<Project_Dir>\wincproj\<OS_Name>\GraCS.
* Filter the directory for files matching @PCS7Typicals*.pdl.
* Count the total number of matching files: If the count exceeds 10, consolidate custom icons into fewer files or delete obsolete typicals pictures.
* Ensure your primary custom typicals file is named so that it sorts within the first 10 alphabetically (e.g. @PCS7Typicals_Custom.pdl sorting ahead of @PCS7Typicals_Z.pdl).
Verify Icon Type Declaration in the Template Picture:
* Open WinCC Explorer on the Engineering Station.
* Open your active typicals picture (e.g. @PCS7Typicals_Custom.pdl) in Graphics Designer.
* Select the target block icon object.
* Open Object Properties -> General.
* Verify the type attribute: It must match the requested CFC identifier exactly (e.g. @MonAnL/12).
* Confirm that no duplicate @MonAnL/12 object exists in @PCS7Typicals_APLV8.pdl or other typicals files.
* Save and close Graphics Designer.
Configure Block Icon Number in CFC Object Properties:
* In SIMATIC Manager, open the CFC chart containing the technological block.
* Right-click the block (e.g. MonAnL) and select Object Properties.
* In the 'Block icon' or 'type' field, set the variant suffix to 12 (or full string @MonAnL/12).
* Confirm that the checkbox 'Create block icon' is checked.
* Click OK and close the chart.
Execute the 'Create/Update Block Icons' Wizard:
* In SIMATIC Manager, select the OS project in the tree (or select a Plant Hierarchy folder).
* Select Options -> Plant Hierarchy -> Create/Update Block Icons.
* In the wizard dialog, verify that the active OS is selected.
* Check the checkbox Lower hierarchy levels.
* Click OK to execute icon generation.
Validate Updated Icon on the Target Process Screen:
* Open the target plant picture in Graphics Designer.
* Confirm that the previous icon is replaced with the new /12 variant.
* Check Object Properties -> General -> type to verify that @MonAnL/12 is assigned.

Verification

Verify Block Icon Replacement and Tag Binding:
1. In Graphics Designer on the target picture, confirm that the block icon exhibits the visual geometry of variant /12.
2. Open the WinCC compilation log (<OS_Dir>\log\OS_Compile.log); confirm that the block instance was processed with 'Icon created successfully'.
3. Activate WinCC Runtime; confirm that the new icon displays live process values and opens the correct faceplate on click.

Limitations and Operational Precautions

Operational Precautions and Manual Overwrite Boundaries:
- If an engineer previously modified an instantiated block icon directly on a plant picture (such as disconnecting customized object properties), the wizard will not overwrite it unless the old icon is manually deleted first.
- Standard Siemens typicals files (@PCS7Typicals_APLV8.pdl) should never be deleted, as core system faceplates rely on standard definitions.

Engineer FAQ

Why did my block icon not update after changing the type in CFC?

The most common cause is having more than 10 @PCS7Typicals*.pdl files in GraCS (the compiler ignores files beyond the 10th), duplicate icon names, or the icon being manually detached from wizard management.

How many @PCS7Typicals pictures does PCS 7 support?

PCS 7 processes a maximum of 10 @PCS7Typicals picture files in alphabetical order during compilation.

What happens if the same icon type exists in two different typicals pictures?

The compiler uses the icon from the first picture file encountered in alphabetical order, shadowing the second.

How do I force PCS 7 to recreate a stuck block icon?

Open the plant picture in Graphics Designer, manually delete the old block icon, save the picture, and run 'Create/Update Block Icons' from SIMATIC Manager.