How to Resolve WinCC Alarm 1011101 'PTM Error During Start-up' in SIMATIC PCS 7

How to Resolve WinCC Alarm 1011101 'PTM Error During Start-up' in SIMATIC PCS 7

In SIMATIC PCS 7, WinCC system alarm message 1011101 stating 'PTM Error during start-up' indicates a database desynchronization or corrupted layout cache in Picture Tree Manager (PTM) during Operator Station runtime initialization. This occurs when process picture files (.pdl) referenced in the Plant Hierarchy were renamed or deleted outside SIMATIC Manager, or when standard layout templates (@Overview1.pdl, @AreaButtons.pdl) became corrupted. Resolving the error requires opening Picture Tree Manager in WinCC Explorer to save and re-index the hierarchy, running OS Project Editor with factory default templates, and performing an OS compile with 'Picture Tree' checked.

Table of Contents

Role of Picture Tree Manager (PTM) in the PCS 7 OS Architecture

In SIMATIC PCS 7, the human-machine interface navigation structure is governed by the Picture Tree Manager (PTM) editor within WinCC.

PTM acts as the bridge between the engineering Plant Hierarchy (PH) and the runtime display:
1. Hierarchy Mapping: Translates Plant View folders (Plant Area -> Unit -> Function) into hierarchical navigation menus and container buttons.
2. Overview Navigation: Automatically populates the plant area buttons displayed in the top header banner (@Overview1.pdl).
3. Alarm Group Summaries: Collects alarms originating from subordinate process pictures and aggregates them into Area Group Displays (@AreaButtons.pdl), enabling operators to identify which plant section has an active alarm at a glance.

During WinCC Runtime startup, the PTM runtime service initializes, verifies database pointers, and builds the memory navigation tree.

Root Cause Analysis for Alarm 1011101 During Startup

When activating WinCC Runtime on an OS Server or Single Station, engineers frequently observe the high-priority system alarm:
* Alarm ID 1011101: PTM Error during start-up

Underlying Failure Mechanisms

  • Orphaned Picture File References in SQL Database: If an engineer renamed, moved, or deleted a process picture (.pdl) directly in Windows Explorer rather than inside SIMATIC Manager, the WinCC SQL database table (PTM_Pictures) retains references to the non-existent file. On startup, PTM cannot resolve the picture file handle, throwing Alarm 1011101.
  • Corrupted Overview Graphic Templates: The PTM service binds dynamic scripts directly to graphic templates (@Overview1.pdl, @AreaButtons.pdl). If these pictures were edited manually, converted between resolutions improperly, or damaged during an aborted OS compile, PTM fails during initialization.
  • Desynchronized Server Data Packages: On OS Clients or multi-server systems, outdated server data packages (.pck) containing stale hierarchy references trigger PTM binding failures.

Step-by-Step Remediation Procedure

Follow this procedure to eliminate PTM startup errors and rebuild the navigation database:

Step 1: Open and Re-index Picture Tree Manager

  1. In WinCC Explorer, double-click Picture Tree Manager.
  2. Inspect the plant container tree: look for any container marked with a red cross or pointing to a missing picture.
  3. If orphaned containers exist, delete them or re-link them to valid pictures.
  4. Click the Save (diskette) icon in Picture Tree Manager: this forces the utility to re-calculate container IDs and rebuild the SQL tables.
  5. Close Picture Tree Manager.

Step 2: Restore Standard Templates via OS Project Editor

  1. In WinCC Explorer, double-click OS Project Editor.
  2. Navigate to the Basic Data tab.
  3. Ensure that all @Overview*.pdl, @AreaButtons*.pdl, and @PTM*.pdl files are marked with 'Update' (or select the radio button 'All project pictures with factory settings').
  4. Click OK. OS Project Editor copies fresh, pristine template files from the Siemens base pool into GraCS.

Step 3: Compile OS with Picture Tree Option Checked

  1. On the Engineering Station, open SIMATIC Manager.
  2. Right-click the OS project and select Compile.
  3. In the OS Compilation Wizard:
    * Select Changes only or Entire OS.
    * Ensure that the checkbox Picture Tree is explicitly checked.
  4. Complete the compilation.

Step 4: Download and Restart Runtime

  1. Download the updated project to the target OS Server.
  2. Activate WinCC Runtime.
  3. Confirm that Alarm 1011101 no longer appears during startup.

Picture Tree Manager Database Tables and Diagnostic Matrix

The following table outlines the database components, template files, and diagnostic indicators associated with Picture Tree Manager:

System ComponentFile / Database TableOperational FunctionFault Symptom / ErrorPTM_ContainersWinCC SQL DatabaseStores plant area hierarchy nodesAlarm 1011101 on startupPTM_PicturesWinCC SQL DatabaseMaps .pdl files to hierarchy nodesMissing picture references@Overview1.pdlOS Project GraCSRenders top area navigation bannerArea buttons fail to navigate@AreaButtons.pdlOS Project GraCSRenders dynamic group alarm statesAlarms fail to propagate to headerWinCC_Sys_01.logSiemens\WinCC\DiagnoseLogs runtime initialization errorsPTM: Initialization failed

Rebuilding the database and restoring factory templates resolves PTM initialization faults.

Verification

To verify that Picture Tree Manager initializes cleanly:
1. Deactivate and reactivate WinCC Runtime on the OS Server.
2. Open the WinCC AlarmList (@AlarmActive.pdl); verify that Alarm 1011101 does NOT appear.
3. Confirm that the top overview banner renders all configured plant area buttons cleanly.
4. Click each area button: confirm that the workspace navigates immediately to the assigned plant picture.
5. Trigger a test alarm in a subordinate chart: confirm that the corresponding area button in the top banner flashes red or yellow to prove group alarm propagation.

Limitations and Operational Precautions

  • Never rename, copy, or delete .pdl process pictures directly in Windows Explorer; always manage process pictures through SIMATIC Manager Plant View.
  • Running OS Project Editor with 'All project pictures with factory settings' overwrites manual modifications to system templates; back up customized layout graphics before running the editor.
  • Ensure all redundant OS Servers receive identical compilations so Picture Tree table structures remain synchronized.
  • If multi-screen multi-VGA configurations are used, ensure the monitor resolution selected in OS Project Editor exactly matches physical display hardware.

Engineer FAQ

What does PTM stand for in SIMATIC WinCC?

PTM stands for Picture Tree Manager, the WinCC subsystem responsible for managing the plant hierarchy navigation structure and top-level area alarm group displays.

Why did deleting a picture in Windows Explorer cause Alarm 1011101?

Deleting the .pdl directly bypassed the database. PTM retained an internal SQL record pointing to the missing file, triggering an initialization error on startup.

Can I compile the OS without compiling the Picture Tree?

Yes, but if you modified the Plant Hierarchy, renamed folders, or added pictures, you must check 'Picture Tree' during compilation to keep PTM synchronized.

Technical References

Related Articles

Related Tags

  • Picture_Tree_Manager
  • PTM_Error
  • Alarm_1011101
  • OS_Project_Editor
  • Area_Buttons
6 respuestas