How to Find Which PCS 7 Template PDL Supplies a Block Icon
To find the template used for an automatically generated PCS 7 block icon, inspect the OS project's GraCS folder and sort @PCS7Typicals*.pdl files in reverse alphabetical order. The PCS 7 Operator Station V9.1 SP1 manual says the first template in that order containing a matching block icon is used by Create/Update Block Icons. If OpDi01/100 is absent from every template, it may have been copied into a picture manually rather than generated from a template.
Table of Contents
- Search the template files
- If the icon is not in a template
- Interpret
OpDi01/100carefully - Regeneration precautions
- Limitations and Operational Precautions
- Verification
- Engineer FAQ
- Technical References
- Related Articles
- Related Tags
Search the template files
- Open the OS project's
GraCSfolder and list files matching@PCS7Typicals*.pdl. - Sort filenames in reverse alphabetical order.
- Inspect the template pictures in that order for an object whose
Typematches the icon variant, such asOpDi01/100. - The first matching template is the one Siemens documents as the source used by Create/Update Block Icons.
- Back up the project before editing templates or regenerating icons.
If the icon is not in a template
An icon visible in a process picture is not necessarily template-generated. It may have been copied from another project and connected manually or through a Dynamic Wizard. Siemens' search procedure identifies icons present in template PDL files; if the object is missing from them, inspect the actual process picture and object properties.
Interpret OpDi01/100 carefully
The Type value identifies an icon type/variant in the project context. It does not name the PDL file. The ticket found OpDi01/100 in use while locating only variants 01 through 04 in templates; this is consistent with a custom or copied object, but inspection of the project files is needed to establish its origin.
Regeneration precautions
PCS 7 can update picture objects from available template files. Before running this operation, archive the OS and verify the template ordering and project-specific icons because the operation can update generated graphics.
Limitations and Operational Precautions
Confirm version applicability and operational impact before changes to a running control system. Use approved backup, testing, change-control and rollback procedures.
Verification
Verify configuration and observable runtime behavior against the intended process requirements.
Engineer FAQ
How are PCS 7 OS areas created? PCS 7 derives OS areas from the configured picture hierarchy; the PCS 7 V9.0 manual maps the second Picture Tree Manager level to OS areas for user rights.
Can a client create its own unrelated area hierarchy? The OS client editor configures visible areas and rights from the OS picture structure; it does not replace the engineering hierarchy as the source.
What does an empty CSV export prove? Only that the generated file has headings but no rows; it does not reveal whether the cause is filtering, project data, or an export defect.
Can an installer compatibility bypass establish support? No. A successful setup launch does not prove that a software and operating-system pairing is tested or supported.
Does PCS 7 V8 license entitlement automatically cover V9? The applicable license and upgrade entitlement must be checked for the exact product and contract; do not infer it from version numbering.
Does local mode bypass all motor stops? No. Mode selection and interlocks or stop inputs are separate logic conditions; inspect the exact block version and signal states.
How does PCS 7 treat cyclic interrupt process images? A process image partition assigned to a cyclic interrupt OB is updated when that OB runs; without such assignment, the regular OB1 update may leave cyclic logic using older values.
Can several PDL pictures appear in one WinCC screen? Yes. WinCC picture-window objects can display project PDL files; PCS 7 APG V9.0 SP2 also documents a four-quadrant display.
Should APG Quad Screen be assumed present in every project? No. Confirm the installed APG release and compatibility with the project's PCS 7 and APL versions.
When should an issue be escalated? Provide exact product versions, project context, reproducible steps, and relevant logs or configuration evidence with private details removed.