IMDTouchKnowledge BaseShop main store

How-to

Keep WinCC dual-monitor navigation inside picture windows

HMI and touchscreens Published 7 min read

Short answer

Keep the 2560 x 1024 parent picture loaded as the permanent start picture and retarget each navigation button's direct connection so its open-picture action lands on the picture window object instead of the full screen. Only the selected 1280 x 1024 window changes; the other monitor and the parent layout survive every press.

On this page
  1. Why does the second monitor fall to the background color when a button is pressed?
  2. How wide should the start picture be for two 1280 x 1024 monitors?
  3. What has to stay loaded for both picture windows to survive navigation?
  4. How do I change where a button's open-picture action opens?
  5. What if the buttons sit inside shared pictures and cannot reach the window by name?
  6. Should each monitor get its own start picture instead?
  7. What test proves the fix before I change every button?
  8. Which fix do I commit to for this project?
  9. Questions asked

Your start picture is already correct; the buttons are what break it. A 2560 x 1024 parent picture with a picture window on each side is the right design for two 1280 x 1024 monitors, so keep that parent loaded permanently and make every navigation button open its picture inside one of the windows instead of replacing the parent. The open-picture command you believe you cannot change is a direct connection on the button's event, and only half of it is fixed: the picture name stays, the destination is edited. Redirecting an event action like this is ordinary screen-and-event work — the same territory as what HMI programming covers from screens to controller tags.

Why does the second monitor fall to the background color when a button is pressed? #

Because the button executes a top-level open-picture action: it unloads the whole start picture, both picture windows are destroyed with it, and the replacement picture only covers one monitor while the remaining area shows its background color.

A picture window is an object owned by the parent picture: when the parent unloads, both windows unload with it. The button's caption and its position on screen tell you nothing about its destination — a button drawn inside an embedded picture can still carry an event that replaces the whole runtime picture. The replacement picture is sized for a single monitor, so it fills one display and its background color paints the rest. This is a destination fault, not a display fault, and no resolution change will fix it.

How wide should the start picture be for two 1280 x 1024 monitors? #

2560 x 1024 pixels — one picture spanning an extended desktop, where 1280 + 1280 = 2560 pixels of width and 1024 pixels of height, not a duplicated desktop showing the same 1280 x 1024 twice.

Your layout already proves this works, so leave it alone while you fix navigation. The arithmetic for the record:

  • Desktop width: 1280 px + 1280 px = 2560 px; height is 1024 px on both displays, so the parent picture is 2560 x 1024.
  • Left window object: x = 0, width = 1280 px, height = 1024 px — it covers pixels 0 through 1280.
  • Right window object: x = 1280, width = 1280 px, height = 1024 px — it covers pixels 1280 through 2560.
  • 1280 px + 1280 px = 2560 px, so the windows meet at the seam with no gap and no overlap.

In the operating system, the two displays must be set to extend the desktop and arranged horizontally to match their physical positions; a duplicated desktop shows the same picture twice and cannot use the width. Change display settings and button destinations one at a time — if you alter both together, you cannot tell which change produced the result.

What has to stay loaded for both picture windows to survive navigation? #

The parent picture itself: it must remain the loaded picture for the entire session, because it owns both picture window objects, and only the pictures inside those two windows are allowed to change.

Element Role Behavior during navigation
2560 x 1024 parent picture Fixed two-monitor layout Stays loaded on every press
Left picture window Content container for monitor one Swaps only when its own buttons are used
Right picture window Content container for monitor two Keeps its current picture during left-side navigation
Area pictures Process graphics inside a window Load inside the selected window, never over the parent

The two windows are separate display destinations inside one project and one runtime — they share one tag database, one script set and one archive, and they are not separate projects. What they give you is two independently navigable content areas on one WinCC Explorer 7.3 station.

How do I change where a button's open-picture action opens? #

Open the button's 'Object Properties' in Graphics Designer, go to the 'Event' tab, open the direct connection on its press event, and set the destination to the picture window object — 'PictureWindow1' in the documented example — instead of the current picture.

  1. Back up the project and do the edit and the testing on a commissioning copy with the runtime off the machine — not on a station an operator is using.
  2. Open the parent picture in Graphics Designer and confirm both picture window objects. If you need another one, insert it from the 'Standard' selection window by double-clicking the 'Picture Window' smart object.
  3. Write down the exact object names of the left and right windows; the destination must use those names exactly.
  4. Select the navigation button, open 'Object Properties', click the 'Event' tab, and open the direct connection configured on its press event.
  5. Leave the source side — the picture name — exactly as it is, and change only the destination side to the window object that should display that picture.
  6. Save, start Runtime, press the button: the one window changes, the other window and the parent stay on screen.
  7. Repeat for every navigation control, including return, overview and area-selection buttons; a single overlooked top-level action still destroys the layout.

The command you could not change is this connection. Open-picture behavior is not a fixed instruction in WinCC — it is an event configuration whose picture name you keep and whose destination you edit. The direct-connection route is documented for WinCC V7.5 and V8.0 and works the same way in 7.3; use the installed 7.3 help for the exact dialog wording, and do not carry over an interface from a differently named WinCC product.

What if the buttons sit inside shared pictures and cannot reach the window by name? #

Drive the window from a tag instead: right-click the picture window, open Properties, go to 'Miscellaneous' and 'Display Picture', enable dynamicity and link a char tag, then let any button anywhere navigate by writing the picture name into that tag.

A direct connection resolves its object reference in the picture where the action runs. From inside a nested or shared graphic, the window object in the parent is not addressable by name, and an object name that exists somewhere in the project is not a destination. The tag breaks that coupling: the window displays whatever picture name the tag holds, so a button two levels deep needs no object context at all. Give the left and right windows separate tags so the two sides navigate independently.

Should each monitor get its own start picture instead? #

Only if top-level navigation must stay untouched: projects built with the OS Project Editor can assign each monitor its own startup picture on the 'Monitor' tab and enable 'Start automatically', so each display runs its own picture tree from boot.

That layout gives every display its own picture tree with no picture windows at all, and it is the honest choice when the navigation genuinely cannot be reconfigured — for example a delivered application whose pictures you are not meant to edit. It costs a rebuild of the navigation structure: a plain WinCC runtime has one start picture, which is exactly why the wide parent with two windows is the standard dual-monitor answer. Your layout already displays correctly, so retargeting destinations inside it is the smaller, committed change.

What test proves the fix before I change every button? #

Retarget one button, press it in Runtime, and watch both monitors: the chosen window swaps its picture, the other window keeps its content, and the parent stays framed across both displays with no background-color area.

  • Press the retargeted button once: only its window changes; the other monitor still shows its picture and no background-color region appears.
  • Press a button for the other side: the first window now holds its content while the second swaps — both directions proven.
  • Open the button's event list and confirm no second action on the same event still opens a picture at the top level.
  • Navigate away and back: the parent returns full-frame across both displays, never as a lone picture on one monitor.

Which fix do I commit to for this project? #

Retarget the direct connections — that is the answer for this project: the buttons are editable event configurations, so keep the 2560 x 1024 parent and point each open-picture action at its window.

  • Buttons you can open and edit: retarget the destination on the event's direct connection and leave every picture name untouched.
  • Shared or nested pictures that cannot address the window: link each window's 'Display Picture' to its own char tag and navigate by writing the tag.
  • Navigation genuinely locked at the top level: stop fighting it, configure per-monitor startup pictures on the OS Project Editor's 'Monitor' tab with 'Start automatically', and accept the rebuild.

No picture size redirects an action — a wide parent with window-targeted buttons is the committed design, and the moment a press keeps both monitors alive, the job is done.

Questions asked

What size should the pictures inside each window be?

Build them at the window's own 1280 x 1024 so each area picture fills its container exactly: the left window covers pixels 0 through 1280 and the right covers 1280 through 2560 of the parent. A picture smaller than its window leaves the window background visible at the edges; match the two and the seam between the monitors stays clean.

Do the two picture windows act as separate projects?

No. Both windows are objects in one parent picture inside one runtime, sharing the same tag database, scripts and archives. They are independent display destinations: each shows whatever picture its own connection or Display Picture tag loads, and both disappear together if the parent is ever replaced.

Why does a button work from the parent picture but not from inside an embedded picture?

From a nested graphic, the window object living in the parent cannot be addressed by name, even though that name exists elsewhere in the project, so the direct connection has no valid destination. Route the navigation through a Display Picture tag instead, and the button's location stops mattering.

What happens if a top-level open-picture action is left on one button?

Pressing it unloads the parent and both windows with it: the new picture covers one monitor and the second monitor shows the background color until navigation returns to the parent start picture. Every button, including return and overview controls, must be retargeted or tag-driven before the layout is safe.

Keep reading

  • How-to

    Binding PLC tags from different DBs to a WinCC HMI UDT

    No configuration makes an HMI UDT span multiple data blocks: a structured HMI tag resolves to one addressable PLC instance. With the PLC program frozen, keep every existing address, create one external HMI tag per variable, and assign them to the faceplate interface properties at each instance; the screen-window tag prefix cannot supply per-equipment data and only reaches shared values with the documented marker.

    HMI and touchscreens

  • Troubleshooting

    Why WinCC 7.5 Runtime Fails Under a New Windows User

    Runtime failing under a newly created Windows account while Explorer opens is a Windows security-context problem, not a WinCC project problem. Put the account in the SIMATIC HMI group, sign out fully, verify effective access to the project, and after an Admin password change update the logon identities of services and scheduled tasks.

    HMI and touchscreens

  • Troubleshooting

    C-more Micro Alarm Control Setup Ignores Double-Clicks

    C-more Micro binds the double-click that launches a Navigation window item to its text label, so a double-click on the icon does nothing. Aim at the words 'Alarm Control Setup' in the Function tab, or use the Setup menu's Alarm Control Setup command; reinstalling will not change anything.

    HMI and touchscreens