Tracing Block Icon Locations Across WinCC Graphics in SIMATIC PCS 7

In SIMATIC PCS 7 projects containing custom technological blocks and block icons, locating the specific WinCC process picture (.pdl) files where an icon is instantiated can be achieved without manually opening every graphic screen. Engineers can inspect the OS compilation block icons log file (THPOfile.txt), query the Process Object View in SIMATIC Manager under the Picture Objects tab, utilize the WinCC Cross-Reference editor, or execute a VBA search script within WinCC Graphics Designer. The block icons log provides an immediate, plain-text audit of every block icon generated across the plant hierarchy.

Block Icon Generation and Hierarchy Linkage

In SIMATIC PCS 7, block icons are graphic representations of technological function blocks placed within WinCC process pictures (.pdl). The linkage between AS CFC instances and WinCC graphics is managed through the Plant Hierarchy (PH). When the Plant Hierarchy option Create/update block icons is executed, the engineering system scans all CFC charts for blocks possessing the S7_m_c = true attribute and configured with an icon type identifier (e.g., @VlvL/1).

The system places the corresponding block icon into the picture file assigned to that specific hierarchy folder, parameterizing the object's TagPrefix or tag property with the CFC tag name. Over years of plant modifications, identifying which graphic screens contain specific custom block icons becomes necessary for upgrades, styling audits, and display optimization.

Locating Block Icons via the THPOfile.txt Log

The most direct and authoritative source of block icon deployment data is the THPOfile.txt log generated during OS compilation:

File Location: The log file resides in the OS project directory at:
[Multiproject]\[OS_Project]\wincproj\[OS_Name]\THPOfile.txt
Opening from SIMATIC Manager:
- In SIMATIC Manager, navigate to the Plant View.
- Right-click the root Multiproject or target Plant Hierarchy folder.
- Select Plant Hierarchy > Open Block Icons Log.
Inspecting Log Content: Open the file in a text editor (e.g., Notepad). Search for your custom block name or tag name. The log records:
- Target picture name (e.g., Area1_Overview.pdl)
- Technological block instance (e.g., Plant1/Unit2/CFC_Pump/CustomBlock)
- Graphic object name (e.g., @CustomBlock/1)
- Generation timestamp and status.

Auditing Graphic Locations Using Process Object View

For an interactive, spreadsheet-style interface within SIMATIC Manager:

Open Process Object View (View > Process Object View or press Ctrl + 4).
Select the target project or multiproject in the tree.
Navigate to the Picture Objects tab.
The table displays every graphic object linked to plant hierarchy blocks:
- Picture: Name of the .pdl file hosting the object.
- Object Name: The graphic element ID within the picture.
- Type / Block Type: Shows the underlying block type (e.g., CustomBlock, VlvL).
- Hierarchy Path / Chart: Displays the exact CFC location.
Use column sorting or the filter bar (Ctrl + F) to isolate instances of the custom block type across all plant areas.

Alternative Methods: WinCC Cross-Reference and VBA Scripting

Two additional methods allow direct identification inside WinCC Explorer:

WinCC Cross-Reference Assistant:
In WinCC Explorer, open Cross-Reference.
Select search scope Pictures and search for the tag name or block name associated with the custom block.
The tool lists every picture, script, and dynamic dialog where the tag or object is referenced.
WinCC Graphics Designer VBA Automation:
Engineers can run a VBA script across project pictures to iterate through the HMIObjects collection:
vba Sub FindCustomBlockIcons() Dim doc As Document Dim obj As HMIObject Dim targetType As String targetType = "@CustomBlock" For Each doc In Application.Documents For Each obj In doc.HMIObjects If InStr(obj.ObjectName, targetType) > 0 Then Debug.Print "Found in: " & doc.Name & " Object: " & obj.ObjectName End If Next obj Next doc End Sub

Comparison of Block Icon Tracing Methods

The following table compares methods for identifying block icon locations across a PCS 7 project:

Tracing MethodTool RequiredSearch SpeedScopeProvides PDL NameAllows Direct NavigationTHPOfile.txt LogText Editor / SIMATIC ManagerInstant (Text Search)Entire OS Server ProjectYesNo (Informational only)Process Object ViewSIMATIC Manager POVFast (Tabular Filter)Entire MultiprojectYesYes (Double-click opens CFC/PDL)WinCC Cross-ReferenceWinCC ExplorerMedium (Index Scan)Single OS ProjectYesYes (Direct jump to WinCC object)Graphics Designer VBAWinCC Graphics DesignerSlow (Scans Open PDLs)Active / Selected PicturesYesYes (Highlights object on canvas)

Note: For project-wide audits during migrations, Process Object View provides the most comprehensive data.

Verification

Verify that located block icons correspond to active plant instances:
1. Open the identified .pdl file in WinCC Graphics Designer.
2. Select the block icon and inspect the Properties > Dynamic > Tag or TagPrefix attribute.
3. Confirm that the tag path matches the active CFC instance.
4. Launch WinCC Runtime, open the graphic picture, and verify that clicking the block icon correctly opens the custom technological faceplate.

Limitations and Operational Precautions

Observe the following engineering constraints:
- Manually copied block icons that were pasted into pictures without using the 'Create/update block icons' wizard will NOT appear in THPOfile.txt.
- WinCC Cross-Reference must have an up-to-date index; rebuild the cross-reference database after major project modifications.
- Running intensive VBA scripts across hundreds of graphic pictures simultaneously in Graphics Designer can consume substantial memory; perform large scans in batches.

Engineer FAQ

Where can I find THPOfile.txt if it does not appear in SIMATIC Manager?

The file is physically located in your project directory at <Project_Dir>\<OS_Dir>\wincproj\<OS_Server>\THPOfile.txt. It is generated whenever 'Create/update block icons' or OS compilation runs.

Why does a block icon exist in a picture but not in Process Object View?

If an icon was manually dragged from @PCS7Typicals.pdl into the screen and manually wired rather than generated by the Plant Hierarchy, it lacks the hierarchy linkage required for Process Object View tracking.

Can I rename a block icon object in WinCC without breaking OS compilation?

No. The object name encodes the tag linkage and type definition. Modifying the object name causes subsequent 'Create/update block icons' runs to either overwrite changes or create duplicate icons.