How to Create and Name Custom Block Icons in SIMATIC PCS 7 OS
To create custom block icons for user-defined function blocks in SIMATIC PCS 7 OS without modifying default system graphics, save your custom symbols inside a dedicated picture file named @PCS7Typicals<ProjectName>.pdl rather than altering @PCS7Typicals.pdl. Custom block icons require specific object attributes: the type property must follow the format @<FB_Name>/<Icon_Index> (such as @CustomValve/1), and the ServerName property must be set to PCS7 <FB_Name> Control to link runtime faceplate popups. When you run the OS 'Create/Update Block Icons' wizard, PCS 7 scans template files in alphabetical priority, instantiating the custom icon wherever the block's s7_m_c and icon variant attributes match.
Table of Contents
- Block Icon Architecture: Template Pictures vs. Process Pictures
- Naming Conventions for Custom Typical Pictures
- Configuring Essential Block Icon Object Properties
- Method: Step-by-Step Creation and OS Generation Workflow
- Verification
- Limitations and Operational Precautions
- Engineer FAQ
- Technical References
- Related Articles
- Related Tags
Block Icon Architecture: Template Pictures vs. Process Pictures
In SIMATIC PCS 7, process pictures (*.pdl) do not require manual placement and tag-binding of every valve, motor, and analog indicator. Instead, the engineering system automates generation via the Create/Update Block Icons function:
1. The compiler inspects the Continuous Function Charts (CFC) for all blocks with the attribute s7_m_c := 'true'.
2. It reads the block icon variant number assigned in the block properties (parameter type or block icon number field).
3. It scans typical template pictures located in the OS project's GraCS directory.
4. It clones the matching graphical object, places it onto the target process picture, and dynamically configures all tag connections, alarm color dynamics, and faceplate jump scripts.
Modifying the factory default template @PCS7Typicals.pdl is forbidden by best practices because PCS 7 software updates, library upgrades, and OS project editor runs overwrite factory files.
Naming Conventions for Custom Typical Pictures
PCS 7 supports user-defined typical pictures using a strict prefix-based naming convention:
@PCS7Typicals<FreeText>.pdl
Examples of valid filenames include:
* @PCS7TypicalsMyPlant.pdl
* @PCS7TypicalsCustomAPL.pdl
* @PCS7Typicals_SpecialDrives.pdl
Template File Scanning Hierarchy
When the Create/Update Block Icons wizard executes, it scans all files matching @PCS7Typicals*.pdl in reverse alphabetical order (from Z to A), followed finally by @PCS7Typicals.pdl. This priority sequence guarantees that a custom block icon defined in @PCS7TypicalsCustom.pdl overrides a default block icon of the same name in @PCS7Typicals.pdl.
Configuring Essential Block Icon Object Properties
A custom block icon must be constructed as a Custom Object in WinCC Graphics Designer. It must contain the following core system attributes:
type@<FB_Name>/<Variant> (e.g. @CustomDrive/1)TagNameTagName)ServerNamePCS7 <FB_Name> ControlTypeID1031.0000)VersionIDIf your custom block does not have a faceplate popup, leave ServerName blank or omit the click action script to prevent runtime errors.
Method: Step-by-Step Creation and OS Generation Workflow
Follow this procedure to create and generate a custom block icon:
- In WinCC Explorer, open Graphics Designer.
- Open an existing template (such as
@PCS7TypicalsAPLV8.pdlor@PCS7Typicals.pdl), select a block icon resembling your target equipment, copy it, and paste it into a new picture. - Save the new picture as
@PCS7TypicalsMyProject.pdlin the OSGraCSdirectory. - In Graphics Designer, right-click the pasted object and select Configuration Dialog:
- Change thetypeproperty to@YourFBName/1(whereYourFBNamematches the S7 block name or symbolic name).
- ChangeServerNametoPCS7 YourFBName Control. - Adjust visual elements (bitmaps, text strings, status indicators) and save
@PCS7TypicalsMyProject.pdl. - In SIMATIC Manager, open the target CFC chart. Double-click the user-defined block:
- Ensure the block input/output parameters intended for OS communication haves7_m_c := 'true'.
- In block properties, set the Block Icon number to1. - In SIMATIC Manager Plant View, right-click the OS project or hierarchy folder and select Plant Hierarchy > Create/Update Block Icons.
- Select the target process pictures and click OK. The wizard locates your custom template and places the fully bound icon onto the process picture.
Verification
To verify that the custom block icon generates and operates correctly:
- In SIMATIC Manager, review the generation log in the dialog after Create/Update Block Icons completes. Ensure no errors indicate
Icon not found in typicals. - Open the target process picture in Graphics Designer. Confirm that the custom block icon is present and that its
TagNameattribute matches the AS hierarchy path (e.g.,Plant/Unit/Motor1). - Start WinCC Runtime.
- Verify that process variable values update dynamically and that alarm states trigger visual color changes.
- Click the custom icon. Verify that the associated faceplate window opens without generating script error dialogs.
Limitations and Operational Precautions
- Do Not Ungroup Custom Objects: Never use Ungroup on a block icon in Graphics Designer. Ungrouping destroys the custom object property interface, wiping out dynamic bindings and wizard functionality.
- Property Interface Preservation: When adding new graphical shapes to a block icon, use Custom Object > Edit to add internal elements, then expose dynamic properties via Custom Object > Configuration Dialog.
- Clean GraCS Directory: Avoid saving backup copies such as
@PCS7Typicals_Old.pdlin theGraCSdirectory. Because the wizard scans all matching files, an old file may unintentionally override active icons.
Engineer FAQ
Can I have multiple block icon designs for the exact same function block?
Yes. Define multiple variants in @PCS7Typicals<Name>.pdl using sequential index numbers in the type property (e.g., @CustomMotor/1, @CustomMotor/2, @CustomMotor/3). In CFC, enter the desired number in the block icon field.
What happens if I update the graphic in @PCS7Typicals after icons are already placed?
Rerunning Plant Hierarchy > Create/Update Block Icons will automatically update all existing instances on process pictures without deleting manual coordinate placements.
Why does the OS compiler report that my custom block icon cannot be found?
This occurs if the block name in the type property (@FBName/1) does not match the block symbolic name in the SIMATIC Manager block symbol table, or if the template PDL is missing the @PCS7Typicals prefix.
Technical References
- Siemens Industry Online Support Entry ID 109765887: SIMATIC Process Control System PCS 7 APL Style Guide
- Siemens Industry Online Support Entry ID 109809264: How do you create your own block icons with SIMATIC PCS 7?
- SIMATIC PCS 7 OS Process Control Manual (Document No. A5E00278788)
Related Articles
- https://industrialautomation.net/search?query=pcs7+create+custom+block+icons
- https://industrialautomation.net/search?query=pcs7typicals+custom+templates+naming
- https://industrialautomation.net/search?query=apl+block+icon+generation+wizard
Related Tags
- https://industrialautomation.net/search?query=simatic+pcs7
- https://industrialautomation.net/search?query=graphics+designer
- https://industrialautomation.net/search?query=block+icons
- https://industrialautomation.net/search?query=wincc+os