How to Propagate Custom Block Icon Changes Across All WinCC Pictures Without Overwriting Layouts in PCS 7

To propagate bug fixes or script modifications made in a template block icon (@PCS7Typicals) across hundreds of existing picture instances without destroying custom layouts, use the WinCC Dynamic Wizard 'Update of the picture objects' instead of the Plant Hierarchy generator. Configure the update wizard to match the specific icon type, ensure the template icon resides on the intended graphic layer, and update screens incrementally. If block icons contain customized geometric scaling or positions, utilize the Block Icon Export/Import utility to preserve coordinates during propagation.

Challenges of Updating Distributed Block Icons in PCS 7

In SIMATIC PCS 7, block icons serve as the primary operational graphical symbols on WinCC mimic displays, representing pumps, valves, analog transmitters, and controllers. These icons are generated from template files—specifically @PCS7Typicals.pdl (and user-defined variants such as @PCS7Typicals_Custom.pdl).

When a project has reached commissioning or production, hundreds or thousands of block icon instances are distributed across dozens of process pictures (.PDL files). If an engineer discovers a defect in a customized block icon—such as an uninitialized data type in the Value.Change C-script causing continuous errors in APDIAG—fixing the issue in the template file does not automatically update deployed instances.

Executing a naive update presents severe operational hazards:
* Overwriting Custom Geometry: Plant operators and graphic designers often resize, rotate, or align individual icons to fit specific piping schematics.
* Layer Resetting: Standard wizards can force all updated icons onto Layer 0, burying them beneath process lines or background equipment bitmaps.
* Full Re-Compile Risks: Running a full Plant Hierarchy update can regenerate unwanted default icons and discard manual customizations.

Plant Hierarchy Generator vs Dynamic Wizard Update Method

PCS 7 provides two distinct mechanisms for managing block icons:

Plant Hierarchy 'Create/Update Block Icons':
* Accessed from SIMATIC Manager by right-clicking a Plant Hierarchy folder and selecting Plant Hierarchy > Create/Update Block Icons....
* This tool parses CFC charts, checks S7_m_c attributes, and places block icons into the designated picture assigned in the hierarchy.
* Limitation: If an icon was already manually placed or modified in Graphics Designer, or if the hierarchy path has changed, the generator can fail, create duplicate icons, or scramble existing coordinates.
WinCC Dynamic Wizard 'Update of the Picture Objects':
* Accessed directly inside WinCC Graphics Designer under the Dynamic Wizard window (Picture Functions > Update of the picture objects).
* This wizard specifically scans existing .PDL files, finds graphical objects whose type attribute matches the template icon in @PCS7Typicals.pdl, and replaces internal scripts, dynamic links, and properties while keeping picture interconnections intact.
* This is the recommended tool for propagating script and property fixes to existing icons.

Preventing Layer 0 Defaulting and Visual Stacking Errors

A frequent frustration when using the Dynamic Wizard is that all updated block icons are placed onto Layer 0 by default, corrupting the z-order visual stacking of the screen.

To prevent or easily resolve layer corruption:
* Template Layer Alignment: Open @PCS7Typicals.pdl in Graphics Designer. Select the custom block icon and open the Properties palette. Set the object's layer property explicitly to the desired runtime layer (e.g., Layer 5 or Layer 10). When the wizard generates or updates an object, it inherits the layer configured in the template file.
* WinCC Graphics Designer Default Layer: In Graphics Designer, ensure the active working layer matches the target layer before launching the wizard.
* Block Icon Configuration File (XML/CFG): Siemens provides a configuration utility (Block Icon Export/Import) that exports the coordinates, layer assignments, and custom properties of all block icons into an XML file. After running an update wizard, the configuration file can be re-imported to restore all custom positions and layers instantly.

Step-by-Step Block Icon Batch Propagation Procedure

Follow this structured procedure to safely deploy template icon fixes across a multi-screen project:

Fix and Validate the Master Template:
* Open @PCS7Typicals.pdl (or your customized @PCS7Typicals_*.pdl) in Graphics Designer.
* Correct the erroneous C-script or missing data type in the Value.Change or Mouse.Click event.
* Ensure the object's type property (e.g., @CustomMotor/1) matches the deployed instances.
* Save and close the template file.
Stage the Fix on a Single Test Screen:
* Open one non-critical process screen in Graphics Designer.
* Open the Dynamic Wizard window, expand Picture Functions, and double-click Update of the picture objects.
* In the wizard dialog, select Update only selected picture and point to @PCS7Typicals.pdl.
* Complete the wizard and inspect the updated icons.
Verify with APDIAG:
* Launch WinCC Runtime, open the test screen, and run apdiag.exe.
* Confirm that clicking the updated icon produces zero script errors.
Batch Update Remaining Pictures:
* Once validated on the test screen, re-run the wizard across remaining project screens in controlled batches.
* Check visual layers and verify piping alignments before committing the screens to production servers.

Comparison of Block Icon Updating Mechanisms

The table below compares the two primary methods for updating block icons in SIMATIC PCS 7.

CharacteristicPlant Hierarchy GeneratorDynamic Wizard (Update Picture Objects)Execution LocationSIMATIC Manager (ES)WinCC Graphics DesignerTrigger MechanismMenu Plant Hierarchy > Create/UpdateDynamic Wizard Picture FunctionsScope of UpdateRecreates icons based on CFC chart hierarchyReplaces scripts/properties of existing iconsPreservation of Manual PlacementsHigh risk of displacement or duplicationPreserves screen positions and connectionsHandling Custom SizingResets icon to default template dimensionsReplaces scripts; can preserve custom scales via config fileRecommended UsageInitial plant generation or adding new equipmentMaintenance bug fixes and script patches on existing screens

Verification

To confirm successful propagation of block icon fixes:
1. Open multiple updated process pictures in Graphics Designer and verify that block icons remain on their assigned layers without visual displacement.
2. Open apdiag.exe (C:\Program Files (x86)\Siemens\WinCC\uTools\apdiag.exe) and set focus to the Output Window.
3. Launch WinCC Runtime and navigate through each updated process screen.
4. Verify that the previous Value.Change C-script error messages no longer appear in the APDIAG diagnostics stream.
5. Click each block icon to confirm that faceplates open seamlessly and display live process data.

Limitations and Operational Precautions

Always create a complete zip archive backup of the WinCC OS project before running any batch update wizard; automated wizards modify .PDL files directly on disk.
Never run the Plant Hierarchy block icon generator with 'Delete existing block icons' checked on a production plant; this obliterates all manual graphic alignments.
If icons have been mirrored or scaled non-proportionally, the Dynamic Wizard may revert them to the aspect ratio of the template icon.
In redundant OS server systems, perform block icon updates on the Engineering Station and download the project to OS Servers rather than editing local server pictures directly.

Engineer FAQ

Why did the Plant Hierarchy 'Create/Update Block Icons' fail to fix my icons?

The Plant Hierarchy generator is designed to instantiate new icons from CFC charts based on TH (Technological Hierarchy) rules. It does not perform surgical script replacements inside existing icons and often skips instances that have already been detached or customized in Graphics Designer.

Where does WinCC store the template block icons?

Templates are stored as .PDL files directly in the GraCS folder of the WinCC project, typically named @PCS7Typicals.pdl, @PCS7Typicals1.pdl, or @Template.pdl. PCS 7 parses these files in numerical order during icon compilation.

How do I avoid having updated icons dumped onto Layer 0?

Before running the update wizard, open the template file (@PCS7Typicals.pdl), select the master icon, and assign it to the desired layer (e.g., Layer 5). The wizard will place updated instances onto the layer specified in the template.

Technical References

Related Tags

Block Icons
@PCS7Typicals
WinCC Graphics
Dynamic Wizard
apdiag

How to Propagate Custom Block Icon Changes Across All WinCC Pictures Without Overwriting Layouts in PCS 7