Engineering Custom PCS 7 Block Icons: Configuring Type Attributes and ServerName Faceplate Associations

To configure a custom function block so that its block icon is generated automatically during OS compilation and opens its faceplate on click, engineers must configure specific attributes across SCL and WinCC. In the SCL block header, declare { S7_m_c := 'true' } and assign the block symbol name in the Symbol Table. In the template picture (@PCS7Typicals.pdl or @PCS7TypicalsAPLV8.pdl), configure the customized object with attribute 'type' set to @/ (e.g. @MY_BLOCK/1). To link the faceplate, set the 'serverName' attribute to 'PCS7 Control' (e.g. 'PCS7 MY_BLOCK Control') and create matching faceplate files (@PG_MY_BLOCK.pdl, @PG_MY_BLOCK_Standard.pdl).

Object-Oriented Visualization Architecture in SIMATIC PCS 7

In SIMATIC PCS 7, process visualization is tightly coupled to the AS control logic. Rather than manually drawing and tagging graphic symbols on dozens of mimic screens, PCS 7 utilizes automated block icon generation during the AS-OS compilation process.

A complete technological object requires three aligned components:

AS Function Block (SCL/STL): Contains control logic and OCM (Operator Communication and Monitoring) attributes.
Block Icon Template (@PCS7Typicals.pdl): A WinCC customized object that is instantiated automatically into process pictures.
Faceplate Picture Set (@PG_<Name>.pdl): A standardized multi-window dialogue providing detailed diagnostics and operator controls.

SCL Block Header Declarations: S7_m_c and Symbol Table Binding

In the SCL source file of the custom function block:

Declare the system attribute { S7_m_c := 'true' } directly on the block header:
scl { S7_m_c := 'true'; S7_tasklist := 'OB100' } FUNCTION_BLOCK FB5001 TITLE = 'POLYMER_DOSER'
In the STEP 7 Symbol Table, map FB5001 to a clear symbolic name: POLY_DOS.
This symbolic name serves as the technological block type identifier across the entire engineering system.

The Anatomy of the Block Icon 'type' Attribute (@Type/Number)

In WinCC Graphics Designer, open the template file @PCS7Typicals.pdl (or @PCS7TypicalsAPLV8.pdl). When inspecting a customized object's properties under General, the property type defines the compiler binding:

The Leading @: Mandatory. Instructs the AS-OS compiler that this customized object is a dynamic template managed by the OS compiler.
The Type Name: Must match the exact Symbol Table name of the block (e.g. POLY_DOS).
The Suffix (/1, /2): Represents the visual variant number. A block may have multiple icon designs (e.g. @POLY_DOS/1 for standard horizontal, @POLY_DOS/2 for compact vertical).
In CFC, opening block properties allows selecting which icon variant (1 or 2) to instantiate.

The 'serverName' Attribute and Faceplate File Naming Conventions

Under the General property group, the serverName attribute instructs the WinCC script engine which faceplate files to open upon mouse click:

Syntax: PCS7 <FaceplateName> Control (e.g., PCS7 POLY_DOS Control).
WinCC dynamic faceplate scripts parse <FaceplateName> and construct picture names matching this strict naming convention:
@PG_POLY_DOS.pdl (Main faceplate container window)
@PG_POLY_DOS_Overview.pdl (Header bar with alarms and mode status)
@PG_POLY_DOS_Standard.pdl (Main operator control view)
@PG_POLY_DOS_Limits.pdl (Limit values and alarm threshold view)
@PG_POLY_DOS_ViewToolbar.pdl (Navigation button bar)

If serverName does not match the file prefix identically, clicking the icon in runtime fails with 'Picture not found'.

Comparative Structure Matrix: Block Icon Attributes vs Faceplate Files

The following table maps SCL definitions to WinCC block icon properties and faceplate files:

Engineering ElementConfiguration LocationExample ValueFunctional Role in PCS 7Block Header AttributeSCL Source Code{ S7_m_c := 'true' }Enables block for AS-OS compilationSymbolic Block NameSTEP 7 Symbol TablePOLY_DOSAuthoritative block type identifierBlock Icon typeObject Properties -> General@POLY_DOS/1Matches CFC block type to template iconBlock Icon serverNameObject Properties -> GeneralPCS7 POLY_DOS ControlTells C-script which faceplate files to instantiateMain Faceplate PDLWinCC GraCS Directory@PG_POLY_DOS.pdlMaster multi-window faceplate frameStandard View PDLWinCC GraCS Directory@PG_POLY_DOS_Standard.pdlWorking operator view for commands and setpoints

Step-by-Step Procedure to Create a Custom Block Icon and Faceplate

Follow this sequence to implement custom technological visualization:

Author and Compile SCL: Declare { S7_m_c := 'true' } on FB header and operational pins (Start, Stop, PV_Out). Compile to FB.
Assign Symbol: In STEP 7 Symbol Table, assign symbol POLY_DOS to the FB.
Instantiate in CFC: Place an instance into a CFC chart. In block properties, confirm Create block icon is checked and variant is 1.
Build Block Icon Template: In WinCC Graphics Designer, open @PCS7Typicals.pdl. Copy an existing motor icon (@MOTOR/1).
Configure Icon Properties: In Object Properties -> General:
- Set property type to @POLY_DOS/1.
- Set property serverName to PCS7 POLY_DOS Control.
- Connect object animations to .STATUS or .PV_Out.
Create Faceplate PDLs: Copy standard templates (e.g. @PG_MOT_L*.pdl) and rename them to @PG_POLY_DOS.pdl, @PG_POLY_DOS_Standard.pdl, etc.
Execute OS Compilation: Run OS Compile with 'Create/Update Block Icons' checked. Open plant picture; confirm icon is placed automatically.

Verification

Confirm block icon and faceplate health through these checks:

Automatic Placement Audit: Open the target plant picture in Graphics Designer. Confirm the custom block icon was created with valid Tag and TagPrefix.
Runtime Click Test: Launch WinCC Runtime. Click the custom icon; verify @PG_POLY_DOS.pdl opens instantly without script warnings.
Control Action Verification: Operate a command button on @PG_POLY_DOS_Standard.pdl. Verify the command reflects online in the S7-400 CPU.
Diagnostic Check: Inspect apdiag.exe Output Window; confirm zero 'Picture file missing' errors.

Limitations and Operational Precautions

Observe the following design precautions:

Backup Template Pictures: Always archive @PCS7Typicals.pdl before modifying; syntax errors in this picture halt block icon generation project-wide.
Tag Prefix Synchronization: Faceplates rely on relative tag names (.Start, .PV_Out); ensure all faceplate dynamic properties omit absolute chart paths.
Commercial Accuracy Disclaimer: Software order numbers (MLFBs), package structures, and hardware capacity prerequisites vary across PCS 7 versions and hardware platforms. System integrators must confirm exact software entitlements and licensing requirements against the official Siemens Catalog CA 01 and obtain an authorized Siemens distributor quotation prior to purchasing.

Engineer FAQ

Can the faceplate name differ from the block type name?

Yes, as long as the faceplate PDL files match the string defined in the block icon's serverName attribute, the faceplate name does not need to match the SCL symbol name.

How do I create multiple visual icon variants for the same block?

Create multiple icons in @PCS7Typicals.pdl with identical block type names but differing suffix numbers, such as @MOTOR/1 (horizontal) and @MOTOR/2 (vertical).