Resolving Missing Block Icons for Newly Installed Libraries in SIMATIC PCS 7

In SIMATIC PCS 7, when newly installed library blocks (such as the Industry Library, CEMAT, or third-party packages) fail to generate block icons in WinCC process pictures after an OS compilation, the root cause is that the library's template pictures (@PCS7Typicals*.pdl) reside in the Siemens installation directory but have not been deployed to the WinCC OS project. To resolve this, run the OS Project Editor in WinCC Explorer with 'Basic Data' update enabled, ensure the library typicals reside in the OS project's 'GraCS' folder, and execute 'Options > Plant Hierarchy > Create/update block icons' in SIMATIC Manager.

Executive Summary

Extending a SIMATIC PCS 7 installation with supplementary function block libraries—such as the PCS 7 Industry Library (IL), CEMAT (Minerals), Advanced Process Functions (APF), or vendor-specific packages—expands plant automation capabilities with specialized technological blocks. After installing the software and placing the new blocks into CFC charts, engineers execute an AS-OS compilation and expect block icons to populate on WinCC process pictures automatically.

However, engineers frequently discover that while standard APL motor and valve icons appear normally, the newly installed library blocks produce zero icons on process screens. This failure occurs because the PCS 7 Block Icon Generation Wizard cannot locate the visual template representations (@PCS7Typicals*.pdl) within the local WinCC project's Graphics (GraCS) directory. This guide explains how block icons are resolved during compilation and details the procedure to deploy templates and generate missing icons.

Architecture and Fundamental Mechanics

The automated block icon generation workflow in SIMATIC PCS 7 links CFC block type attributes to WinCC graphical templates:

The Block Type 'type' Attribute: In CFC, every technological block instance possesses an object property: 'Create block icon' (checked) and an icon type identifier (e.g., @IL_MotL/1, @C_DRV_1D/2).
The Template Resolution Precedence: When an engineer executes 'Options > Plant Hierarchy > Create/update block icons' in SIMATIC Manager, the generation wizard scans the local OS project's GraCS directory for template files matching the pattern @PCS7Typicals*.pdl (such as @PCS7TypicalsIL.pdl or @PCS7Typicals_CEMAT.pdl). The wizard searches for an icon whose user attribute type matches the block's identifier.
The Installation Gap: When a supplementary library is installed, its setup wizard copies template PDLs into the centralized Siemens directory: C:\Program Files (x86)\Siemens\WinCC\Options\PDL\.... However, the installer does NOT inject these files into existing WinCC project directories on disk. If the local OS project's GraCS folder lacks the library's @PCS7Typicals*.pdl file, the wizard finds no matching template and silently skips icon creation.
Role of the OS Project Editor: Launching the OS Project Editor in WinCC Explorer inspects newly installed options and copies the updated system templates, scripts, and @PCS7Typicals*.pdl files from the Siemens product repository into the active OS project's GraCS folder, immediately bridging the gap.

Step-by-Step Implementation Procedure

Follow these steps to deploy missing block icon templates and generate icons for newly installed libraries in PCS 7:

Confirm Library Installation and CFC Block Configuration:
- In SIMATIC Manager, open the CFC chart containing the new library block.
- Open Block Properties (double-click block header) and verify that 'Create block icon' is checked.
- Note the block type string: e.g., @IL_MotL or @C_VALVE.
Run OS Project Editor to Transfer Library Templates:
- In SIMATIC Manager Component View, right-click the OS project and select 'Open Object' to launch WinCC Explorer.
- In WinCC Explorer, double-click 'OS Project Editor'.
- Switch to the 'Basic Data' tab.
- In the file list, ensure that the newly installed library template pictures (e.g., @PCS7TypicalsIL.pdl or @PCS7Typicals_CEMAT.pdl) are selected for transfer into the project.
- Click 'OK'. The OS Project Editor copies the template PDLs from the Siemens installation repository into the local project's GraCS directory.
Verify Template Presence in Graphics Designer:
- In WinCC Explorer, open 'Graphics Designer'.
- Confirm that @PCS7Typicals<Library>.pdl is now listed in the project file tree.
- (Optional) Open the file: confirm that the required block icon and version variant (e.g., /1 or /2) exist.
Assign OS Pictures in Plant Hierarchy:
- In SIMATIC Manager Plant View, ensure that the hierarchy folder containing the CFC chart has a WinCC picture (.pdl) assigned.
- Block icons can only be instantiated into pictures assigned to the same hierarchy level (or a designated parent).
Execute 'Create/Update Block Icons':
- In SIMATIC Manager Plant View, right-click the top-level plant hierarchy folder (or target unit folder).
- Select 'Plant Hierarchy > Create/update block icons...' from the context menu.
- In the dialog window, ensure the target OS is selected and the hierarchy level range is set to cover all sub-folders.
- Click 'OK'. The generation wizard parses all CFC charts, queries @PCS7Typicals*.pdl in GraCS, and automatically places the new block icons into their assigned process pictures.
Compile OS and Verify in Runtime:
- Execute an AS-OS compile ('Changes only').
- Open the target process picture in WinCC Graphics Designer to inspect icon placement, then download to OS Runtime.

Verification

In WinCC Graphics Designer, open the process picture corresponding to the plant area: confirm that the new library block icon is placed on the screen canvas.
Select the block icon and inspect its Object Properties: verify that the attributes tag, tagname, and Servername correctly link to the CFC block tag.
Activate WinCC Runtime: confirm that the block icon displays live status (e.g., motor stopped/running, valve open/closed).
Click the block icon in Runtime: verify that the matching APL or library-specific faceplate opens cleanly without script error popups.

Limitations and Operational Precautions

If you have customized existing standard block icons, running the OS Project Editor can overwrite user-modified templates with factory defaults unless customized icons are stored in custom typical files starting with a single at-sign (e.g., @PCS7Typicals_Custom.pdl). Supplementary libraries (such as Industry Library or CEMAT) require dedicated engineering and runtime license keys installed via Automation License Manager. Validate all software packages and library licensing through an authorized Siemens distributor or the Siemens Industry Mall.

Engineer FAQ

Why does installing a new library not automatically put icons in my WinCC project?

The library installer places template PDLs into the global Siemens installation directory. The OS Project Editor must be executed on each OS project to copy those templates into the project's local GraCS folder.

What naming pattern identifies block icon template files?

Block icon template files follow the pattern @PCS7Typicals*.pdl (e.g., @PCS7TypicalsAPL.pdl, @PCS7TypicalsIL.pdl).

Can I create custom block icons for the new library?

Yes. Create a custom template file named @PCS7Typicals<Name>.pdl in GraCS, copy the library icon into it, customize its appearance, and re-run 'Create/update block icons'.