Resolving 'Error in Picture' on Multi-Monitor WinCC OS Clients in SIMATIC PCS 7 Redundant Systems

In SIMATIC PCS 7 redundant architectures, 'Error in picture' displayed on the left monitor of an OS Client for standard template graphics (@AreaButtons.pdl, @AlarmOneLine.pdl, @Logo.pdl) is caused by incomplete Server Data package synchronization, multi-monitor coordinate mismatches, or thin-client graphics display virtualization faults. Because Monitor 1 (left) relies on @1001.pdl and Server Data bindings, an out-of-sync or partially downloaded Server Data package on OS Server 1 causes tag resolution failures. To resolve this, re-generate Server Data on both OS Servers, assign Windows Primary Display to Monitor 1, and re-download Server Data to the clients.

Multi-Monitor Split Screen Architecture in SIMATIC PCS 7

In SIMATIC PCS 7, multi-monitor operator consoles (2, 3, or 4 displays) are coordinated by the Split Screen Manager (SSM):
* The Master Screen Layout:
Configured in WinCC OS Project Editor -> Layout tab (e.g., SIMATIC Standard 1920x1080 2 Monitor).
* Display Allocation:
* Monitor 1 (Left Display): Configured as the primary interaction screen. It hosts @screen.pdl, which embeds the primary workspace (@1001.pdl), the area selection buttons (@AreaButtons.pdl), the single-line alarm banner (@AlarmOneLine.pdl), and the plant logo (@Logo.pdl).
* Monitor 2 (Right Display): Operates as an auxiliary workspace hosting @1002.pdl, displaying secondary process overviews or permanent trend windows.

Root Causes of Left-Monitor 'Error in Picture' Failures

Corrupted or Incomplete Server Data Package:
The OS Client reads area buttons and alarm counts from the OS Server's Server Data package (.pck). If Server 1's package was compiled with errors or partially loaded, Monitor 1's script engine cannot bind the area tags, flagging an unhandled script error that renders 'Error in picture'.
* The Redundancy Switchover Clue: When Server 1 is stopped, the client automatically switches to Server 2's healthy package, instantly refreshing the area buttons!
Windows Primary Display Mismatch:
WinCC expects Monitor 1 in the OS Project Editor to correspond to Display 1 (Primary Display) in Windows Display Properties. If the right monitor is set as Windows Primary, coordinates wrap into negative virtual desktop space.
Thin Client Virtualization Resolution Scaling:
On virtualized thin clients (e.g., Dell Wyse / VMware Horizon), if the virtual GPU assigns mismatched DPI scaling (e.g., 100% on one screen and 125% on the other), WinCC's coordinate calculation engine fails.

The Role of Server Data Packages (.pck) in Client Visualization

On an OS Client, no local AS-OS compilation occurs. The client is an empty container that imports Server Data:
* Package Generation:
On each OS Server, SIMATIC Manager generates <Project>_<Server>.pck.
* Standard Server Assignment:
In WinCC Explorer on the client, the Standard Server for alarms and SSM must point to the redundant server pair. If the client cannot access the package share during boot, Monitor 1's initialization scripts fail.

Comparison Table: Monitor 1 vs Monitor 2 Screen Loading Mechanics

The table below outlines operational differences between monitor channels:

Display ChannelUnderlying TemplateEmbedded Standard PicturesSensitivity to Server DataMonitor 1 (Left / Primary)@screen.pdl -> @1001.pdl@AreaButtons.pdl, @AlarmOneLine.pdl, @Logo.pdlCritical (Area hierarchy and alarm bindings)Monitor 2 (Right / Auxiliary)@screen.pdl -> @1002.pdlSecondary working area / Trend windowLow (Renders assigned graphic directly)

Step-by-Step Procedure to Resolve Multi-Monitor Client Graphic Errors

Verify Windows Display Settings:
* On the OS Client (or thin client OS), open Windows Display Settings.
* Identify displays: Ensure Monitor 1 is positioned on the left and set as Main Display (Primary).
* Ensure both monitors share identical screen resolution (e.g., 1920x1080) and 100% scaling.
Re-Generate Server Data on Redundant OS Servers:
* In SIMATIC Manager on the ES, right-click OS Server 1 -> Server Data -> Generate.
* Right-click OS Server 2 -> Server Data -> Generate.
* Right-click OS Client -> Server Data -> Update.
Run OS Project Editor on OS Client:
* Open WinCC Explorer on the OS Client project.
* Open OS Project Editor.
* On the Layout tab, select the exact multi-monitor resolution (e.g., SIMATIC Standard 1920x1080 2 Monitor).
* On the Basic Data tab, ensure template replacement options are enabled to restore clean @AreaButtons.pdl files. Click OK.
Re-Download OS Client Project:
* Close WinCC on the OS Client.
* From SIMATIC Manager, perform a full download to the OS Client (PLC -> Download -> Entire OS).
Verify Runtime Redundancy:
Activate WinCC Runtime on the client. Verify that Monitor 1 loads smoothly without 'Error in picture' warnings.

Verification

To verify multi-monitor rendering:
1. Open WinCC OS Runtime on the client.
2. Confirm that Monitor 1 displays the top area selection buttons, single-line alarm banner, and company logo cleanly.
3. Click through multiple plant area buttons on Monitor 1. Verify that process screens update instantly.
4. Stop WinCC on OS Server 1. Verify that the client switches to OS Server 2 bumplessly without graphic distortion on either monitor.

Limitations and Operational Precautions

Hardware Acceleration on Thin Clients: Ensure that virtual desktop infrastructure (VDI) clients have virtual 3D graphics acceleration enabled. Software-only CPU rendering on dual 1080p monitors can drop frames during script execution.
Never Mix Monitor Orientations: Avoid mixing portrait and landscape orientations or differing refresh rates across an operator console.
Licensing Disclaimer: OS Client runtime operations require valid WinCC Client licenses (6AV6381-2BC07-4AX0) and PCS 7 Client packages verified via Automation License Manager.