Renaming Customized Block Icons and Managing Typicals in PCS 7 Graphics Designer

Renaming Customized Block Icons and Managing Typicals in PCS 7 Graphics Designer

In SIMATIC PCS 7 v7.1 and newer, renaming a customized block icon in @PCS7Typicals.PDL or @PCS7TypicalsV7.PDL cannot be done simply by editing the alias in the Configuration Dialog, which reverts changes upon closing. To rename a customized object permanently, select the object, open the WinCC Object Properties window, and modify the 'Object Name' attribute under the 'Miscellaneous' property group. Alternatively, open the Configuration Dialog, delete the customized object interface, rename the underlying group, and re-create the customized object.

Table of Contents

Architecture of Customized Block Icons in @PCS7Typicals

In SIMATIC PCS 7, block icons represent AS technological function blocks (such as MotL, VlvL, PIDConL) inside operator process pictures. The standard templates for these icons reside in template pictures:
* @PCS7Typicals.PDL (standard library template catalog)
* @PCS7TypicalsV7.PDL / @PCS7Typicals_Custom.PDL (version-specific or project-specific catalogs)
* @Template.PDL (legacy or fallback templates)

Each block icon template is implemented as a Customized Object (User Object / Anwenderobjekt). A customized object combines multiple basic graphical primitives—such as static text, rectangles, status displays, and dynamic SVGs—into a unified container with an external property interface (e.g., Tag, type, ServerData, CollectMsg). When the PCS 7 OS Compiler executes the function Create/Update Block Icons, it scans these typical pictures, locates matching block icon templates based on the type attribute, and clones them into plant overview pictures.

Why the Configuration Dialog Reverts Object Name Changes

When an engineer opens @PCS7Typicals.PDL, right-clicks a customized object, and selects Configuration Dialog, the displayed dialog manages the Property Interface Mapping (linking internal element properties to public external properties).

Inside this dialog, the top-level name field often displays the interface definition tag. If an engineer modifies the text in this dialog and clicks OK, the Graphics Designer saves the property assignments but immediately re-reads the underlying WinCC object name from the container's Windows GDI object descriptor. Because the WinCC Graphics Designer differentiates between the internal interface identifier and the system Object Name, changing text in the Configuration Dialog does not update the WinCC runtime object handle, causing the name to snap back to @WR_R_/WCC1_1.

Procedure to Permanently Rename Customized Objects in Graphics Designer

To permanently rename a customized object or typical icon, use one of the two following validated methods:

Step / ActionMethod A: Direct Property Window (Recommended)Method B: Interface Re-creationStep 1: SelectionOpen @PCS7Typicals.PDL and left-click the customized object once.Open picture and select the customized object.Step 2: Open ToolPress Alt + Enter or right-click and select Properties.Right-click, select Configuration Dialog, click Delete User Object (ungroups interface).Step 3: Edit NameIn the left pane, click Miscellaneous. Double-click Object Name in the right pane.Select the grouped primitives, open Properties, and edit Miscellaneous > Object Name.Step 4: ApplyEnter the new name (e.g., @WR_R/WCC1_9), press Enter, and save the PDL file.Select primitives, right-click, select Customize > Create Customized Object, and re-map properties.ResultName changes immediately without losing existing dynamic property scripts.Clean interface generation; required if internal sub-objects were added/removed.

Table 1: Comparison of validated methods for renaming WinCC customized objects.

Naming Syntax Rules for Automatic Block Icon Generation

For the PCS 7 OS Compiler to automatically instantiate customized block icons during Create/Update Block Icons, strict naming syntax must be followed:

  1. Object Name Syntax:
    * Standard format: @<BlockType>/<TypeIndex>
    * Example: @MotL/1, @PIDConL/2, @WR_R/WCC1_9
  2. Mandatory Object Attributes:
    * type: Must match the exact technological block type or the type parameter configured on the CFC block (e.g., @MotL/1 requires property type = @MotL/1).
    * Tag: Must be exposed as a public property so the compiler can bind the CFC technological tag path (e.g., Plant/Unit/Motor01).
    * ServerData: Must be exposed for multi-client server prefix resolution.
  3. Template Search Priority:
    * During compilation, PCS 7 searches template files in alphanumeric order: @PCS7Typicals_1.PDL, @PCS7Typicals_2.PDL, and finally @PCS7Typicals.PDL. Placing custom typicals in @PCS7Typicals_Custom.PDL prevents them from being overwritten during PCS 7 software updates.

Verification

To confirm the customized object was successfully renamed and operates correctly:

  1. In Graphics Designer, click the renamed object. Observe the status bar and the Object Properties window: verify that Miscellaneous > Object Name displays the new name (e.g., @WR_R/WCC1_9).
  2. Close and reopen the PDL file in Graphics Designer to ensure the name persists across sessions.
  3. Open a test process picture, copy the renamed block icon into it, and connect a test tag.
  4. Activate WinCC Runtime: confirm that the block icon opens the associated faceplate upon click and updates dynamic status indicators without graphic script errors.

Limitations and Operational Precautions

  • Never edit default template pictures (@PCS7Typicals.PDL) directly without creating a backup; future PCS 7 software updates or OS library migrations will overwrite standard system pictures.
  • Always save project-specific typicals into a custom file such as @PCS7Typicals_Project.PDL so the OS Compiler scans your custom icons first.
  • If you modify internal primitives of a customized object, re-verify all C-scripts and direct connections in the property interface to avoid runtime script aborts.

Engineer FAQ

Why did reinstalling PCS 7 resolve the user's issue in the forum?

Reinstalling or running PCS 7 setup resets damaged Graphics Designer DLL registrations and clears temporary cache files in %TEMP% and the WinCC project directory that were locking the object template definition.

Can two block icons in the same typicals picture share the same object name?

No. WinCC Graphics Designer strictly enforces unique object names within any single .pdl picture. Attempting to assign a duplicate name causes WinCC to append numbers or revert to default.

What is the difference between @PCS7Typicals and @Template?

@PCS7Typicals.PDL contains dynamic block icons linked to AS function blocks for automatic generation by the OS Compiler. @Template.PDL contains static graphic primitives, pipes, pumps, and symbols for manual drag-and-drop design.

Technical References

Related Articles

Related Tags

  • Graphics Designer
  • @PCS7Typicals
  • Customized Object
  • Block Icons
  • PCS 7 v7.1
  • WinCC
  • Operator Station
6 respuestas