C135 PCS 7 (PCS7)
6C
6 Cielo Ciencia y Tecnología
·Publicada en C135 PCS 7 (PCS7)

Preserving Custom Screen Layouts During Dual-Monitor OS Project Editor Runs

Preserving Custom Screen Layouts During Dual-Monitor OS Project Editor Runs

When configuring an OS Client for a dual-monitor workstation (2 screens) in SIMATIC PCS 7, running the WinCC OS Project Editor overwrites customized system screens (@screen.pdl, @overview.pdl, @desk.pdl) with default multi-monitor templates. To preserve customizations, navigate to the 'Basic Data' (Grunddaten) tab in the OS Project Editor before applying changes, and deselect the replacement arrow for any pictures you wish to protect from overwriting. For mandatory multi-monitor frame pictures that must be regenerated to establish dual-display coordinate boundaries, backup your modified files in a separate directory and re-apply custom graphics to the newly generated multi-screen templates using a post-configuration batch script.

Table of Contents

Multi-Monitor Screen Generation in Basic Process Control

In industrial control centers, operator ergonomics often demand multiple physical screens per client PC (e.g., Dual Monitor, Triple Monitor, or Quad Monitor setups). In SIMATIC PCS 7, multi-monitor display is handled by the Basic Process Control (BPC) engine via the WinCC OS Project Editor.

When an engineer transitions an OS Client from single-monitor to dual-monitor operation, the OS Project Editor reorganizes the desktop layout: Screen 1 hosts overview banners, alarm lines, and workspace area A, while Screen 2 hosts auxiliary alarm logs and workspace area B. To build this dual-monitor framework, the editor generates new coordinate geometry across all core system pictures (@screen.pdl, @overview1.pdl, @overview2.pdl, @desk.pdl, @1001.pdl).

Why the OS Project Editor Overwrites Custom @ Screens

System pictures beginning with an @ character are owned by the Siemens DCS framework. By default, running the OS Project Editor treats the project directory as a deployment target, copying fresh, unedited multi-monitor templates from C:\Program Files (x86)\Siemens\WinCC\Options\PDL\... directly into the project's GraCS directory.

If an engineer previously added custom company logos, specialized script buttons, or modified coordinate margins directly inside @screen.pdl or @overview.pdl, those files are overwritten by factory templates, completely wiping out custom modifications.

The Role of the 'Basic Data' Protection Tab

The OS Project Editor includes a dedicated mechanism to control file replacement:

  1. Basic Data (Grunddaten) Tab: Lists every system picture, script, and configuration template deployed by the editor.

  2. Replacement Arrows: Columns display an arrow pointing from the installation repository to the project directory. For certain customizable pictures, clicking the arrow toggles it off, instructing the editor: 'Do not overwrite this file; retain the existing version in GraCS.'

  3. Mandatory Multi-Monitor Files: However, for files that define coordinate geometry (such as @screen.pdl which scales from 1920 pixels to 3840 pixels wide for dual monitors), the editor forbids deselecting replacement. Retaining an old single-screen @screen.pdl would prevent the second monitor from displaying any graphics at all.

Comparison of Screen Preservation Techniques

The table below contrasts different strategies for maintaining custom screen designs across OS Project Editor runs.

Engineering TechniqueMechanismRetains Dual-Monitor Geometry?Overwrite RiskRecommended Best PracticeDirect Edit Without BackupModify @ files directly in GraCSOverwritten100% Lost on Editor RunStrictly DiscouragedBasic Data DeselectionUncheck arrow in Grunddaten tabFails (Retains single-screen width)ProtectedUse only for non-geometric screensAutomated Batch Restore ScriptBatch script copies custom files back post-runYes (If batch accounts for 2 screens)LowGood for corporate standardized scriptsRe-Applying Custom Logic to Multi-FramesRe-insert custom buttons into new dual-monitor PDLsYES (100% Native Geometry)Zero (Backed up in separate folder)Official Siemens Standard

Step-by-Step Procedure to Configure Dual-Monitor Clients Safely

Follow this procedure to successfully configure dual monitors while safeguarding custom graphics:

  1. Create an Offline Backup of Current Custom Graphics:
    - In Windows Explorer, open the OS Client project directory: navigate to the GraCS folder.
    - Create a backup folder outside the project (e.g., D:\Custom_Screen_Backup\).
    - Copy all modified system pictures (@screen.pdl, @overview.pdl, @desk.pdl) to the backup directory.

  2. Configure Multi-Monitor in OS Project Editor:
    - Open WinCC Explorer on the OS Client: launch the OS Project Editor.
    - Under the Layout tab, select the appropriate dual-monitor resolution (e.g., SIMATIC Multi-Monitor 2 Screens: 1920*1080 or 1920*1200).
    - Switch to the Basic Data (Grunddaten) tab: inspect the list and deselect replacement arrows for any non-geometric custom pictures (e.g., custom sound scripts or toolbar bitmaps).
    - Click OK to execute: the editor builds the dual-monitor coordinate framework.

  3. Re-Apply Custom Elements to the New Dual-Monitor Templates:
    - Open the newly generated @overview1.pdl and @overview2.pdl in Graphics Designer.
    - Copy your custom corporate logos, navigation buttons, or script objects from the backup files into the new templates.
    - Save the modified files in GraCS and archive a copy in your backup directory.

  4. Deploy and Verify:
    - Launch WinCC Runtime: confirm that Screen 1 and Screen 2 display the coordinated dual-monitor desktop.

Verification

Verify dual-monitor configuration through the following operational tests:
1. Launch WinCC Runtime across the physical dual monitors: confirm that the desktop spans both screens without horizontal distortion.
2. Verify that Screen 1 displays the main plant overview and navigation buttons, while Screen 2 displays the secondary workspace/alarm view.
3. Confirm that all custom buttons, corporate logos, and plant navigation links function properly.
4. Navigate between plant areas: verify that picture changes on Screen 1 do not disrupt monitoring on Screen 2.

Limitations and Operational Precautions

Ensure that Windows Display Settings on the physical client PC are configured with monitors positioned side-by-side with identical scaling (100% DPI scaling). Configuring mismatched DPI scaling (e.g., 100% on Monitor 1 and 125% on Monitor 2) causes the WinCC graphics engine to miscalculate coordinate boundaries, resulting in clipped mouse hitboxes and misplaced faceplates.

Engineer FAQ

Can I configure dual monitors on an OS Client without running the OS Project Editor?

No. The OS Project Editor is mandatory because it calculates internal coordinate bounding boxes and instantiates the multi-screen picture window handlers required by Basic Process Control.

Why did my custom faceplate position offset after changing to dual monitors?

Faceplate popup coordinates in APL are calculated relative to the active screen. In dual-monitor setups, APL evaluates screen index tags (@LocalScreenName) to open faceplates on the monitor where the operator clicked the icon.

Can different resolutions be used on Monitor 1 and Monitor 2 of the same PC?

Siemens strictly recommends identical monitor resolutions and identical aspect ratios across multi-monitor workstations. Using mismatched resolutions on the same PC causes window clipping.

Technical References

Related Articles

Related Tags

  • OS Project Editor
  • Multi-Monitor
  • Dual Display
  • Basic Process Control
  • GraCS
  • WinCC Graphics
6 respuestas