Creating Custom Faceplates and Block Icons from Scratch in SIMATIC PCS 7 WinCC

Creating custom faceplates and block icons from scratch in SIMATIC PCS 7 WinCC requires a structured methodology leveraging either the Siemens Faceplate Designer or modular Picture Description Language (.pdl) template architecture. The workflow comprises: 1) Designing the AS block in SCL with { S7_m_c := 'true' } attributes, 2) Creating a block icon in @PCS7Typicals...pdl with the block type and index, 3) Building the multi-window faceplate structure (Header @PG_<Block>_Overview.pdl and View @PG_<Block>_Standard.pdl), and 4) Wiring dynamic object properties using relative dot-notation tags bound via the WinCC TagPrefix mechanism.

Architectural Hierarchy of PCS 7 WinCC Faceplates

In SIMATIC PCS 7, operator interaction with automation objects (motors, valves, controllers, analog inputs) is handled via faceplates. A PCS 7 faceplate is not a single monolithic window, but a coordinated composite assembly:
1. Block Icon (Process Screen): Placed on operational mimic diagrams, providing condensed status indicators (running, stopped, faulted, interlocked) and alarm status banners.
2. Top Field / Header (@PG_<Type>_Overview.pdl): Displays the technological tag name, operational mode (Auto/Manual/Local), alarm acknowledgment buttons, and view selection tabs.
3. View Windows (@PG_<Type>_<View>.pdl): Swappable central displays showing Standard controls, Parameters, Limits, Maintenance, or History.

Using Faceplate Designer vs Modular Template Duplication

Engineers can create custom faceplates using two distinct engineering methodologies:
* Method A: Siemens Faceplate Designer Utility:
- Accessible via WinCC Explorer -> Tools -> Faceplate Designer.
- Wizard-driven interface where you define block type name, view types, and tag parameters.
- Generates the standard structure .pdl files and registers them with the PCS 7 OpenFaceplate engine.
* Method B: Modular Template Duplication (APL Recommended):
- Copy an existing APL faceplate set matching the mechanical behavior of your device (e.g., duplicate @PG_VlvL_... for an actuated gate).
- Rename files to @PG_CustomBlock_....
- Adjust internal controls and tag links to match the custom SCL block interface.
- This preserves native APL styling, high-DPI font sizing, and multi-monitor positioning routines.

Block Icon Structure and `@PCS7Typicals` Integration

To enable automatic placement during Create/update block icons:
1. Open the project typicals file (e.g. @PCS7TypicalsUser.pdl).
2. Construct or paste the graphical block icon object.
3. Configure the standard user-defined properties:
- type: Must match @<BlockType>/<IconNumber> (e.g., @CustomPump/1).
- server_name: Set to PCS7 CustomPump Control or APL_Default.
- tag: Connected via dynamic wizard to the block instance during generation.
- Event -> Mouse Action: Calls APL_OpenFacePlate or SSMOpenTopField.

Faceplate Internal Scripting and Relative Tag Binding

The fundamental technical mechanism enabling a single set of faceplate PDLs to control thousands of unique plant devices is the TagPrefix:

Object Dynamic PropertyStatic Full Tag Path (Incorrect)Relative Tag Binding (Correct)Runtime ResolutionSpeed FeedbackUnit1/Motor12.PV_Out#Value.PV_Out#ValueTagPrefix (Unit1/Motor12) + .PV_Out#ValueStart CommandUnit1/Motor12.StartAut.StartAutTagPrefix (Unit1/Motor12) + .StartAutFault Alarm StateUnit1/Motor12.Fault.FaultTagPrefix (Unit1/Motor12) + .FaultPermission StatusUnit1/Motor12.Permit.PermitTagPrefix (Unit1/Motor12) + .Permit

When an operator clicks the block icon, WinCC writes the controller instance path to the TagPrefix property of the Faceplate Picture Window, causing all relative tags to bind instantaneously.

Verification

To confirm that the custom faceplate and block icon operate reliably:
1. In WinCC Graphics Designer, open the created @PG_CustomBlock_Standard.pdl and confirm that all dynamic tags start with a leading dot (.).
2. In SIMATIC Manager, run Plant Hierarchy -> Create/update block icons; verify that block icons are placed on target process screens.
3. Launch WinCC Runtime, locate the newly placed block icon, and verify that status color changes reflect the live controller state.
4. Click the block icon; confirm that the top field header opens with the correct plant tag title, and the Standard view displays live parameters.
5. Command a state toggle (e.g. Manual to Auto); verify that the command writes to the AS without script errors in apdiag.exe.

Limitations and Operational Precautions

Never create faceplates with hard-coded absolute tag names. Hard-coding tag paths destroys multi-instance reusability and causes faceplates to command incorrect field equipment if opened for different instances. Always verify that custom C-scripts executed within faceplate buttons release allocated GDI handles and memory to prevent OS memory exhaustion.

Engineer FAQ

Where does the Faceplate Designer store generated files?

Faceplate Designer saves generated PDL files directly into the WinCC project's GraCS (Graphics) directory.

Why does clicking my block icon open an empty picture window?

Check the type property on the block icon. If the string before the slash does not match the PDL name prefix (@PG_<Type>), WinCC cannot locate the file and displays an empty window.

Can I create custom faceplates using VBScript instead of C-Script?

Yes. Both VBScript and C-Script are supported in WinCC faceplates, but standard PCS 7 APL routines primarily utilize C-scripts (SSM... and APL_... functions) for speed.

What tool monitors script errors when opening faceplates?

Run the WinCC diagnostic tool apdiag.exe (located in Siemens\WinCC\bin) and open the 'Output Window' to monitor real-time C-script and VBScript execution faults.

Technical References

Related Tags

Faceplates
Block Icons
Faceplate Designer
TagPrefix
WinCC GraCS

6 respuestas

Creating Custom Faceplates and Block Icons from Scratch in SIMATIC PCS 7 WinCC