Configuring Custom PCS 7 APL Block Icons in WinCC V8/V9

David Krause12 min read
HMI / SCADASiemensTutorial / How-to
Licensed PE Working through this on a live machine? A Maine-licensed engineer can take it from here — included with IMD hardware, by the hour for everything else. Book an engineer

1. Overview

Siemens PCS 7 uses the Advanced Process Library (APL) as the foundation for its standard block types. Each APL block type (such as MonAnL, MonAnS, CtrlPid, MotSpdCL, ValveAnl, and dozens more) is shipped with a pre-defined WinCC block icon template that the OS compilation routine instantiates into the appropriate plant picture during "Create/Update Block Icons".

A block icon is the small symbol visible on the OS picture (typically an @PCS7TypicalsAPLx.pdl reference) that the operator clicks to open the corresponding faceplate. By default, every instance of a given block type renders with the same look. When the project requires a different graphic layout, additional status bits, or a unique color scheme, the engineer must create a user-defined block icon variant without modifying the original APL PDL files.

This article documents the supported engineering workflow for deriving a custom block icon in PCS 7 V8.x and V9.0, based on the Siemens APL Style Guide (section 6.4.2, "Adapting Faceplates") and the official PCS 7 Operator Station configuration manual. The procedure is non-destructive to the original APL library, fully OS-recompilable, and survives subsequent CFC re-compiles as long as the block icon number is preserved.

Scope: This procedure applies to user-defined custom block icons that reuse an existing APL block type. It does not cover creation of new CFC block types from scratch, custom block icon wizards, or APL V8.2+ "Block Icon Editor" tooling (different workflow).

2. Prerequisites

Before starting the procedure, verify that the engineering station meets all of the following requirements:

  • PCS 7 installation: V8.0 SPx, V8.1, V8.2, or V9.0 with the matching APL library version installed via the SIMATIC PCS 7 setup.
  • WinCC Explorer open against the project OS server (or the OS client project, depending on the server/client topology).
  • SIMATIC Manager or PCS 7 Engineering Toolset available for CFC edits.
  • Graphics Designer available (installed automatically with WinCC).
  • Read/write access to the project's GraCS directory (default path: <OS_Project>\GraCS\).
  • WinCC user rights: at least configuration-level authorization to compile the OS.
  • Source PDL file present: @PCS7TypicalsAPL8.pdl (V8) or @PCS7TypicalsAPL9.pdl (V9) located in the project's GraCS folder. This file is the APL master template containing the standard block icon wizards.

Reference: Siemens SIMATIC PCS 7 OS Configuration documentation (support.industry.siemens.com).

3. Terminology and Reference Numbering

The "block icon" property on a CFC block is a numeric identifier that maps the block instance to a specific icon wizard inside the typicals PDL. The numbering rules are:

Block Icon Number Status Behavior
1, 2, 3, 4 Reserved by APL Used by the standard APL icon wizards inside @PCS7TypicalsAPLx.pdl. Selecting 1-4 with a custom PDL still loads the original APL wizard unless the PDL is renamed (see step 5).
0 (empty) No icon Block instance is rendered without any block icon; the faceplate is reachable only via the loop display.
5 – 99, 100+ Free for user-defined Custom number range. Using values such as 11, 21, 111, or 200 is recommended to clearly differentiate user-defined block icons from any future APL additions.

The number chosen in the CFC must match the wizard index in the user-defined typicals PDL: @MonAnL/<your_number>.

4. Step-by-Step Procedure

4.1 Phase 1 – Prepare the User-Defined Typicals PDL

  1. Open WinCC Explorer and load the OS project.
  2. Switch to the OS server (or master OS) where the typicals file lives.
  3. In the navigation pane, right-click on the Graphics Designer node and select Open.
  4. Browse the GraCS directory and locate @PCS7TypicalsAPL8.pdl (V8) or @PCS7TypicalsAPL9.pdl (V9).
  5. Copy the entire file and rename the copy following the convention @PCS7TypicalsAPL<x>UserDefined.pdl (the leading @ is mandatory; the suffix UserDefined is a recommendation, not a Siemens-enforced name).
  6. Save the new file in the same GraCS folder. Do not edit the original APL file.

4.2 Phase 2 – Modify the Block Icon Wizard

  1. Open the new @PCS7TypicalsAPL8UserDefined.pdl in Graphics Designer.
  2. From the palette or via the wizard tree, copy the existing MonAnL block icon wizard into the same picture. Graphics Designer will assign it the next free wizard number.
  3. Edit the visual elements of the wizard as required: change colors, add status LEDs, swap symbol geometry, insert user-defined C-scripts for animations, etc. The wizard remains a normal WinCC picture object.
  4. Save the picture with the modified wizard still embedded. Note the wizard index you selected — it determines the suffix in step 4.4.
Important: Do not delete or rename the original APL wizard inside the user-defined PDL. The OS compiler instantiates icons strictly by index; if your chosen index collides with an APL wizard, the wrong icon is rendered.

4.3 Phase 3 – Configure the CFC Block

  1. Open the CFC chart that contains the target MonAnL block.
  2. Double-click the block icon of the instance you want to redirect to the custom icon (or right-click → Object Properties → Block Icon tab).
  3. In the Block Icon section, locate the input field labeled Create block icon (sometimes displayed as Generate block icon). It accepts a positive integer.
  4. Enter the user-defined number — for example 11. Use any value greater than 4 to avoid clashing with the APL reserved indices 1–4.
  5. Confirm that the checkbox OCM possible is enabled. OCM (Operator Control and Monitoring) controls which parameters are compiled to the OS faceplate. Disabling OCM prevents the block icon from being clickable on the OS.
  6. Click OK to close the block properties dialog.
  7. Repeat for any additional instances that should use the same custom icon.
  8. Compile and download the CFC chart (menu Chart → Compile → Charts followed by PLC → Download).

4.4 Phase 4 – Re-route the Block Icon Reference in WinCC

  1. In Graphics Designer, open the user-defined typicals PDL created in step 4.1.
  2. Copy the original MonAnL block icon object and paste it back into the same picture. Graphics Designer creates a duplicate wizard with a new index (e.g., 5).
  3. Right-click the new wizard → Properties → System tab.
  4. Locate the Type property. By default it reads @MonAnL/1 (or @MonAnL/2..4 depending on which APL variant was copied).
  5. Change the suffix so the property reads @MonAnL/11 (matching the value entered in step 4.3).
  6. Save the PDL.

At this point the OS compiler will pick the modified wizard whenever it encounters a CFC instance with block icon number 11.

4.5 Phase 5 – OS Compilation and Verification

  1. Switch back to WinCC Explorer.
  2. Right-click the OS server → Compile OS.
  3. In the OS compiler wizard, ensure Create/update block icons is selected under the picture compilation scope.
  4. Run the compilation. The compiler writes the modified wizard into the target plant picture(s) and replaces any existing default icons for instances whose block icon number is now 11.
  5. Activate the OS server runtime and the OS client.
  6. Open the affected plant picture and verify that the new block icon is visible.
  7. Click the block icon. The standard faceplate (@PG_MonAnL_Standard.pdl) should open, confirming that the icon routing is correct.

5. Optional – Custom Faceplate Renaming

If you also need to change the underlying faceplate (for example to expose an additional parameter or add a new view), copy the full set of MonAnL faceplate files and rewire the block icon to point at the renamed copies.

5.1 Faceplate File Set (APL V8/V9 Standard)

Source File Purpose
@PG_MonAnL.pdl Top-level faceplate dispatcher
@PG_MonAnL_Standard.pdl Standard view (opened by default)
@PG_MonAnL_Limit.pdl Limit / message view
@PG_MonAnL_Overview.pdl Plant overview summary view
@PG_MonAnL_Parameter.pdl Operator-parameter view
@PG_MonAnL_Preview.pdl Loop preview thumbnail
@PG_MonAnL_ViewToolbar.pdl Toolbar window (view selector)

5.2 Renaming Procedure

  1. Copy the seven files above and rename the base part from MonAnL to a project-unique identifier, e.g., MonAnL_Custom. Result: @PG_MonAnL_Custom.pdl, @PG_MonAnL_Custom_Standard.pdl, etc.
  2. Open @PG_MonAnL_Custom.pdl in Graphics Designer.
  3. Select the @Faceplate object. In its properties, change the Firstview attribute from @PG_MonAnL_Standard.pdl to @PG_MonAnL_Custom_Standard.pdl.
  4. Select the ToolbarWindow object. Change its PictureName attribute to @PG_MonAnL_Custom_ViewToolbar.pdl.
  5. Select the Objcollection object. Change its BlockType attribute from MonAnL to MonAnL_Custom.
  6. Open the user-defined block icon wizard from section 4.4. Go to its System tab. Change the server name property PCS7 MonAnL Control to PCS7 MonAnL_Custom Control. The exact attribute name is ServerName on the C-scripts that drive the faceplate call.
  7. Save and re-run the OS compile.
Licensing: Custom faceplates do not require additional WinCC licenses as long as the underlying block type is still an APL standard block. Renaming the faceplate files only changes the display layer.

6. Verification Checklist

# Verification Step Expected Result
V1 Open the plant picture on the OS runtime The new icon appears at the correct unit location
V2 Click the new icon The custom or standard faceplate opens (depending on whether step 5 was executed)
V3 Close the faceplate No script error dialogs appear; the picture returns to normal
V4 Re-compile the CFC chart and download The icon survives the re-compile (block icon number preserved)
V5 Inspect the OS diagnostic file OS_Logfile.txt No entries about missing icons or unresolvable references
V6 Check the affected picture in Picture Tree mode The icon instance references the user-defined typicals PDL, not the original APL one
V7 Re-run Create/Update Block Icons only Icon is regenerated identically, no duplicate icons left behind

7. Troubleshooting Matrix

Symptom Likely Root Cause Remediation
The custom icon never appears; the original APL icon is rendered instead. Block icon number in CFC does not match the wizard index in the user-defined PDL. Re-open the user-defined PDL and verify that the wizard index suffix matches the number entered under Create block icon in the CFC block.
Block icon is visible but is not clickable. The OCM possible flag is disabled on the CFC block. Re-open the block properties, enable OCM possible, recompile and re-download the CFC.
OS compile reports "block icon @MonAnL/x not found". The custom typicals PDL is not located in GraCS or the wizard with the specified index was deleted. Confirm the user-defined PDL is in the GraCS folder of the active OS project. Re-add the wizard with the correct index.
Clicking the icon opens the wrong faceplate (or no faceplate at all). Step 5 was partially executed — block icon still references the original PCS7 MonAnL Control server name. Update the ServerName property on the block icon to the custom variant.
After re-compiling the CFC, the icon reverts to the default APL icon. The block icon number was reset to 0 or to an APL reserved value during the chart edit. Re-enter the user-defined block icon number, save the chart, and re-download to the AS.
Color animations do not update on the OS. The custom wizard contains C-script animations that were copied but point to the wrong tag prefix. Inspect the wizard's C-scripts and update tag references to match the renamed block instance.
The "Create/Update Block Icons" step inserts duplicate icons in the picture. The wizard was copied multiple times in the user-defined PDL with the same index. Delete duplicate wizards, save, and re-run OS compile.
The icon is rendered but the tooltip text is empty. The TooltipText property on the wizard was overwritten during editing. Re-bind the TooltipText property to the block instance comment tag.

8. Best Practices and Naming Conventions

  • Reserve high numbers. Use values such as 11, 21, 31 or 111, 211 for user-defined icons. Avoid the range 5–9 because PCS 7 patches occasionally introduce new APL variants in that range.
  • Suffix the typicals PDL with UserDefined, Project, or a plant-area code (e.g., @PCS7TypicalsAPL8_Unit100.pdl) to keep multiple variants sortable.
  • Never edit the original @PCS7TypicalsAPLx.pdl. Any modification is overwritten on every APL re-installation.
  • Document each custom number in a project-specific spreadsheet and reference it from the CFC block's Comment field. This prevents accidental collisions during subsequent engineering.
  • Verify after every OS upgrade that the custom typicals PDL still resolves all wizard references, because PCS 7 major upgrades (V8 → V9) can rename wizard indices.
  • Use WinCC version-controlled storage if available; the GraCS folder is otherwise difficult to audit.

9. Related Configuration Touchpoints

The block icon configuration interacts with the following OS-level settings:

  • Picture Tree Manager: defines into which plant picture the OS compiler writes each block icon. Custom icons follow the same hierarchy as the underlying block instance.
  • Tag Logging / Alarm Logging: custom icons can display additional operator hints via the C-script TagPrefix; alarm routing is unaffected.
  • User Archive / Parameter Set: if the block uses a parameter view, the custom faceplate must include the parameter view file (@PG_MonAnL_Parameter.pdl or the renamed equivalent).
  • AS-OS coupling: the block icon number travels with the CFC chart. A recompile + download does not require an OS recompile, but the OS recompile is required for the new icon to appear.

What is the recommended block icon number to use for a custom PCS 7 block icon?

Use any integer greater than 4 that does not conflict with existing user icons. Values such as 11, 21, 31 or any three-digit number (e.g., 111, 211) are recommended because the range 1–4 is reserved by the APL master typicals and values 5–9 may be claimed by future APL updates.

Is it necessary to copy the MonAnL faceplate files to create a custom block icon?

No. Copying the faceplate files (the seven @PG_MonAnL_*.pdl files) is only required when you want to modify the faceplate itself — for example, adding an extra operator parameter or a new view. If you only want a different block icon look on the OS picture while keeping the standard faceplate, steps 4.1 through 4.5 are sufficient.

Why does my custom block icon not appear after OS compile?

The most common cause is a mismatch between the block icon number entered in the CFC block property Create block icon and the wizard index defined on the Type property of the user-defined typicals PDL (@MonAnL/x). Re-check both values and ensure the user-defined PDL is stored in the GraCS directory of the active OS project, not in a backup folder.

Do custom block icons survive a PCS 7 upgrade from V8 to V9?

User-defined typicals PDLs are stored inside the project and are preserved across minor upgrades. However, during a major upgrade (V8.x → V9.0) the APL master typicals file is renamed from @PCS7TypicalsAPL8.pdl to @PCS7TypicalsAPL9.pdl. You must verify that each custom block icon's wizard index still resolves and, if necessary, copy the user-defined PDL content into a new @PCS7TypicalsAPL9UserDefined.pdl.

How is a custom block icon different from a custom block type?

A custom block icon is purely a WinCC-side visual variant that reuses an existing APL CFC block type. A custom block type involves creating a new S7 block (FB/FC/UDT) with new I/O signatures, registering it in the APL master data library, and generating a new typicals entry. Custom block icons require no PLC changes and no additional WinCC licenses; custom block types require both.

David KrauseIndustrial Controls Specialist – Siemens Platforms

Industrial controls specialist focused on Siemens SIMATIC S7 platform, from the S7-300/400 series through the latest S7-1200/1500 controllers. Expert in TIA Portal configuration and WinCC SCADA integration.

Planning your next automation project? Explore IMD panel PCs and touch monitors.

Back to blog

Related Articles

GT1055-QSBD Barcode Reader RS232 Connection Troubleshooting
12 min read
HMI / SCADAMitsubishi
More on this topic: HMI / SCADASiemens

Latest Knowledge Base Articles