Restoring Missing @PCS7TypicalsIL Pictures Using the OS Project Editor in PCS 7
When the block icon template picture @PCS7TypicalsIL.pdl is missing from a WinCC OS project following the installation of the SIMATIC PCS 7 Industry Library (IL), run the OS Project Editor in WinCC Explorer. Installing the Industry Library copies master template files into the global PCS 7 directories, but does not inject them into existing WinCC projects automatically. Opening WinCC Explorer, launching the OS Project Editor, verifying monitor resolution and layout settings, and clicking 'OK' triggers the editor to scan installed library options, copy @PCS7TypicalsIL.pdl and corresponding faceplates into the project's 'GraCS' folder, and register the templates so that subsequent OS compiles successfully generate Industry Library block icons.
Table of Contents
- Executive Summary
- Architecture and Fundamental Mechanics
- Step-by-Step Implementation Procedure
- Verification
- Limitations and Operational Precautions
- Engineer FAQ
- Technical References
- Related Articles
- Related Tags
Executive Summary
The SIMATIC PCS 7 Industry Library (IL) extends standard Advanced Process Library functionality with specialized technological blocks tailored for municipal water/wastewater, building automation, and chemical process package units. When engineers install the Industry Library software package onto an existing engineering station and instantiate IL blocks (such as IL_Motor, IL_Valve, or Time16) in CFC charts, they frequently discover that subsequent OS compilations fail to generate block icons in process pictures. Furthermore, inspecting the WinCC Graphics Designer folder reveals that the master template picture @PCS7TypicalsIL.pdl is entirely missing from the project.
While creating a brand-new PCS 7 project automatically populates all installed library templates, existing projects retain their legacy picture libraries until explicitly updated. The OS Project Editor is the administrative utility responsible for populating global system pictures, script actions, and library typicals into an active WinCC project. This guide details the template instantiation architecture of the PCS 7 OS compiler, explains why template pictures are not populated retroactively upon software installation, and provides the exact procedure to run the OS Project Editor safely without overwriting customized plant displays.
Architecture and Fundamental Mechanics
The PCS 7 OS compiler utilizes a multi-tiered template architecture to generate dynamic block icons during the 'Create/update block icons' phase:
1. Template Hierarchy and Typicals Files:
* Standard APL: Managed icons are defined in @PCS7TypicalsAPLV8.pdl or @PCS7TypicalsAPLV9.pdl.
* Industry Library (IL): Managed icons specific to Industry Library blocks are defined in @PCS7TypicalsIL.pdl (and @PCS7TypicalsILV9.pdl).
* User Customizations: Custom plant icons reside in user typicals files (e.g., @PCS7Typicals_Custom.pdl).
2. Installation vs. Project Scope:
* When Industry Library is installed via Setup.exe, the master template .pdl files are deposited into global installation directories (e.g., C:\Program Files (x86)\Siemens\WinCC\Options\PDL\IL and C:\Program Files (x86)\Siemens\Step7\S7DATA\...).
* Existing WinCC projects located in project workspaces do not automatically receive these new files because WinCC protects active project directories from unintended file modifications during background package installations.
3. Role of the OS Project Editor:
* The OS Project Editor (OS Project Editor tool in WinCC Explorer) inspects the installed PCS 7 components, compares project picture versions against system master libraries, and updates the project's GraCS (Graphics) directory.
* When executed, the editor detects the newly installed Industry Library option and copies @PCS7TypicalsIL.pdl, along with all associated standard faceplate pictures (@pg_*.pdl) and C-script actions, into the project's local GraCS folder.
* Once @PCS7TypicalsIL.pdl resides in the project GraCS folder, the OS compile engine scans it during compilation, matches block type names (e.g., IL_Motor), and instantiates the appropriate graphical block icons onto designated process pictures.
Step-by-Step Implementation Procedure
Step 1: Verify Industry Library Installation on the ES
- Open Windows Control Panel >
Programs and Features(or checkInstalled Softwarein SIMATIC Manager). - Confirm that
SIMATIC PCS 7 Industry Library(e.g., V9.0 or V9.1) is installed on the Engineering Station. - Verify that the Industry Library master data library is present in SIMATIC Manager under
Libraries.
Step 2: Open WinCC Explorer on the Target OS Station
- In SIMATIC Manager, navigate to the target OS station object.
- Right-click the OS project and select
Open Objectto launch WinCC Explorer. - In the WinCC Explorer navigation tree, locate and expand
OS Project Editor.
Step 3: Configure and Execute the OS Project Editor
- Double-click
OS Project Editorto open the configuration dialog. - On the
Layouttab:
* Verify that the selected monitor resolution (e.g.,1920x1080or1680x1050) matches your physical operator monitors.
* Confirm the screen layout configuration (e.g.,SIMATIC Standard 1920x1080). - On the
Basic Datatab:
* Review the list of system pictures to be updated.
* Ensure that the option to copy new/updated system pictures is selected.
* If custom modifications have been made to standard@...pictures in the past, ensure those modified pictures are backed up or unchecked to prevent accidental overwriting. - Click
OKto initiate the generation process. - Wait for the OS Project Editor progress bar to complete (this copies missing
@PCS7TypicalsIL.pdl, faceplates, and system scripts into the project).
Step 4: Verify the Presence of @PCS7TypicalsIL in Graphics Designer
- In WinCC Explorer, click on
Graphics Designerin the navigation pane. - In the file list, scroll down and confirm that
@PCS7TypicalsIL.pdlis now present in the list of project pictures. - Double-click
@PCS7TypicalsIL.pdlto open it in Graphics Designer: verify that Industry Library block icons are visible on the canvas. - Save and close Graphics Designer.
Step 5: Execute an OS Compile to Generate Block Icons
- Return to SIMATIC Manager on the Engineering Station.
- Right-click the OS station and select
Compile. - In the compile wizard, select 'Tags and screen objects' and ensure the checkbox
Create/update block iconsis CHECKED. - Complete the OS compilation process.
Verification
- In WinCC Explorer, open the target process picture where Industry Library block icons were expected.
- Verify that the OS compiler successfully instantiated the IL block icons (e.g., motor, valve, or monitoring icons) on the picture canvas.
- Double-click an instantiated icon: verify that its
Tagandtypeattributes correctly reference the IL block hierarchy path. - Launch WinCC Runtime: click the newly generated Industry Library block icon and confirm that the corresponding IL faceplate opens smoothly without script errors.
Limitations and Operational Precautions
- Running the OS Project Editor can overwrite custom modifications made directly to system pictures (pictures prefixed with
@, such as@Overview1.pdlor@AlarmOneLine.pdl). Always create a complete project backup before running the editor. - Never rename or modify master template pictures (
@PCS7TypicalsIL.pdl) directly; if custom block icons are required, copy them into@PCS7Typicals_Custom.pdl. - The OS Project Editor must be executed individually for each OS project (Server, Standby Server, and Single Station) within the multiproject.
- The Industry Library version installed on the ES must match the installed PCS 7 software release and service pack.
Engineer FAQ
Why didn't installing Industry Library copy @PCS7TypicalsIL into my project automatically?
PCS 7 installers place files only in global system directories to prevent modifying active project workspaces without engineering consent. The OS Project Editor is the designated tool to import system updates into projects.
Will running OS Project Editor delete my custom process screens?
No. The OS Project Editor touches only system files prefixed with @. Your custom process screens (e.g., Reactor.pdl, Overview.pdl) are completely untouched.
Can I manually copy @PCS7TypicalsIL.pdl from another project instead of running OS Project Editor?
While copying the file manually imports the block icons, it will omit dozens of required IL faceplate pictures (@pg_*.pdl) and C-script actions. Running the OS Project Editor ensures all supporting files are deployed.
What should I do if I customized @Overview1.pdl?
In the OS Project Editor under the Basic Data tab, you can uncheck specific @... files to prevent the editor from overwriting your custom changes, or back up your modified files and restore them after running the editor.
Do I need a separate license for SIMATIC PCS 7 Industry Library?
Yes. The Industry Library is an optional engineering and runtime software package requiring dedicated licenses. Consult an authorized Siemens distributor or the Siemens Industry Mall for exact licensing packages.
Technical References
- SIMATIC PCS 7 Industry Library Engineering Manual (Entry ID: 109780589)
- SIMATIC Process Control System PCS 7 OS Process Control (Entry ID: 109780584)
- SIMATIC WinCC V7.5 SP2 - OS Project Editor Manual (Entry ID: 109792585)
Related Articles
- Diagnosing and Resolving Missing Block Icons in PCS 7 OS Process Pictures
- Preserving Manually Copied Block Icons During Plant Hierarchy Updates in PCS 7
- Locating and Installing the Legacy PCS 7 Standard Library in SIMATIC PCS 7 V9.1
Related Tags
- Industry Library
- OS Project Editor
- Block Icons
- Typicals
- WinCC Graphics Designer