A WinCC Professional V13 SP1 station can target two displays from one industrial PC by assigning an independent screen window to a monitor number that matches the Windows display configuration. The available evidence does not establish that this creates separate Runtime sessions; validate simultaneous operator input and navigation before acceptance.
Define the Dual-Display Requirement
The documented setup uses one industrial PC, one CPU, and a graphics card connected to two displays. The client requires different SCADA content on each monitor and operator interaction at both displays.
| Item | Confirmed requirement | Verification needed |
|---|---|---|
| Software | TIA Portal WinCC Professional V13 SP1 | Confirm the installed project and Runtime versions |
| Computer | Single industrial PC | Confirm Windows detects both monitors |
| Display output | Graphics card driving two displays | Record each Windows monitor number |
| Operation | Different display content with interaction on each screen | Test simultaneous input, focus, navigation, and command execution |
Configure the Independent Screen Window
- Open the WinCC Professional project and insert a screen window.
- Define the inserted screen window as an independent screen window.
- Assign its monitor number according to the monitor numbering shown in Windows display settings.
- Configure the content intended for that monitor, then repeat the project configuration as required for the other display.
The evidence uses both “screen window” and “picture window” terminology without confirming the exact V13 SP1 editor label. Select the project object that provides an independent window and monitor assignment; do not infer an unverified object name.
Distinguish Independent Windows from Independent Sessions
Monitor assignment separates where content appears. It does not, based on the available evidence, prove separate users, separate Runtime processes, independent security contexts, or isolation between operator actions. Treat “individual operation” as an acceptance requirement that still needs functional testing.
Define whether each operator must navigate independently, enter commands concurrently, acknowledge alarms separately, or use distinct credentials. If any of these are mandatory, verify them directly because the evidence only supports independent screen-window placement.
Commission and Verify Both Displays
Start Runtime and confirm that each independent window opens on the monitor number assigned in the project. Operate controls on both displays and verify that navigation on one display does not unintentionally replace or redirect content on the other.
Also test concurrent input, window focus, command execution, and Runtime restart behavior. Acceptance is complete only when both displays return to their assigned content and meet the client’s defined meaning of independent operation.
FAQ
How do I show WinCC Professional V13 SP1 on two monitors?
Insert an independent screen window and assign its monitor number to match the numbering in Windows display settings. Verify the destination of each window in Runtime.
Can two operators control WinCC from separate monitors on one industrial PC?
The evidence supports interactive content in independently assigned screen windows, but it does not confirm separate Runtime sessions or security contexts. Test concurrent input, navigation, focus, and commands against the project requirements.
Is a WinCC screen window the same as a picture window?
The available V13 SP1 evidence uses both terms without confirming the exact editor label. Use the window object that supports independent operation and monitor-number assignment, then verify its behavior in Runtime.