Resolving WinCC OS Picture Tree Warning Triangle with PLC-SIM

Problem Description

A warning triangle (yellow) appears in the OS Picture Tree bar of a WinCC Operator Station (OS), typically within a PCS 7 or WinCC V7.x runtime environment. In the same hierarchy, signal errors such as process tag faults do not propagate into subordinate areas such as AREA1, leaving the lower node visually empty while the parent node carries the alert marker. Engineers observe this in the Graphics Designer runtime window, the WinCC Explorer diagnostics area, and the OS area overview bar of the standard PCS 7 faceplates.

The triangle symbol on the Picture Tree bar is not a generic icon; it is a status indicator driven by the WinCC area model. It signals that the WinCC runtime has detected a warning condition affecting the area hierarchy - most commonly a difference between the compiled OS project on disk and the online AS project, or a broken logical connection between the AS and the OS. When the icon is present but no per-area error detail propagates, the runtime is reporting that it cannot evaluate the area's tags at all, because the underlying channel is not bound to a live AS data source.

This article addresses the specific scenario where the OS runtime is launched against S7-PLCSIM rather than a physical S7-400 / S7-400H CPU. PLCSIM exposes a virtual interface that the SIMATIC S7 Protocol Suite must be told to use explicitly via the Logical Device Name parameter; without that setting the channel looks for a physical CP and fails silently, which is precisely the symptom that draws the triangle.

Understanding the OS Picture Tree Hierarchy

The Picture Tree is built from the WinCC Area Model, defined in the OS Project Editor under OS Project Editor > Area Hierarchy. Each area can represent a plant unit (UNIT), a sub-unit, or a logical grouping (AREA). At runtime the OS draws an area tree on the right-hand side of the standard picture; each node can carry one of three overlay icons:

• Gray/empty — no faults, no warnings, area is healthy.
• Yellow triangle (warning) — at least one tag in the area hierarchy has triggered a warning class, or the hierarchy cannot resolve its underlying tags because of a channel fault.
• Red bell / red exclamation — at least one tag has triggered an alarm (error / fault / higher-priority class).

The tri-state aggregation is computed by the WinCC runtime data manager reading the area's area-relevant tags (those marked with the Area-relevant attribute in the OS Project Editor). If the data manager returns no values because the channel DLL cannot establish a logical link, the area shows the warning triangle instead of a clean state - this is the situation engineers encounter when the AS-OS link is broken or PLCSIM is not bound.

Root Cause Analysis

Two failure modes converge to produce the reported behavior:

1. AS-OS channel not bound to PLCSIM. The SIMATIC S7 Protocol Suite > TCP/IP connection is configured with a logical device name that points to a real Softnet/CP (e.g., CP_H1_1:, CP_H1_2:, or an IE General channel). PLCSIM does not respond on those interfaces; the connection therefore remains down, the data manager logs a channel error, and the area tree receives the warning.
2. Project mismatch between OS and online AS. The OS server holds a compiled picture hierarchy, while the connected AS holds a different S7 program version. WinCC compares the S7 program identifier at connection setup; on mismatch the area tree is marked with the warning triangle because tag addresses may no longer resolve correctly.

The absence of signal error events inside AREA1 is the key diagnostic clue. If the warning were due to genuine tag-quality degradation, the runtime would still surface individual tag errors. The clean absence means the area's tags are simply not being polled at all — consistent with a missing channel binding.

AS-OS Communication Architecture

The OS-Software (OS Server / OS Client) communicates with the AS through one of the WinCC channel DLLs. In a PCS 7 plant, the standard selection is the SIMATIC S7 Protocol Suite, which provides the following logical drivers:

Each connection in the channel tree has two physical parameters: the IP address / MPI address / PROFIBUS address of the target AS, and the Logical Device Name that selects which PC interface card (or virtual interface) the channel will bind to.

Diagnostic Procedure

Before changing configuration, capture the current state with the following steps. This isolates whether the warning is a project mismatch or a channel binding problem.

1. Open WinCC Explorer on the OS server. Verify the project loaded is the OS server project, not a client project.
2. Right-click the OS server name and select Properties > Computer. Confirm Type = Server and Startup = WinCC Runtime (or Service Mode if running headless).
3. Expand Tag Management > SIMATIC S7 Protocol Suite. Note which sub-driver carries the warning (TCP/IP is the most common in PLCSIM scenarios).
4. Right-click the channel and choose System Parameters > Unit tab. Record the current Logical Device Name.
5. In the Diagnostics tab of the same dialog, force a reconnect and inspect the log. A successful PLCSIM connection prints Connection established to AS [n]; a failed attempt prints Cannot bind socket to logical device or Partner not reachable.
6. Compare the AS project identifier (visible in the S7 program properties) with the OS project identifier. A mismatch triggers the warning triangle independent of PLCSIM.

If the diagnostics tab confirms that the connection is bound to a physical interface such as CP_H1_1:, the OS is trying to talk to a real CP443-1 that does not exist on the engineering station. This is the smoking gun for the PLCSIM fix.

Solution: Binding TCP/IP to PLCSIM

The corrective action is to retarget the channel's logical device name to a PLCSIM device. Proceed in the following order.

Step 1 — Confirm PLCSIM is Running

Start S7-PLCSIM from the Windows Start menu (or SIMATIC Manager > Options > Simulate Modules). The PLCSIM instance window must be visible before WinCC Runtime is started; if WinCC comes up first, the channel will fail to bind. Load the S7 program into PLCSIM via Online > Download to Target and verify that the PLC is in RUN or RUN-P.

Step 2 — Open the Channel System Parameters

1. In WinCC Explorer, expand Tag Management.
2. Expand SIMATIC S7 Protocol Suite.
3. Right-click the TCP/IP sub-driver (or whichever driver is bound to your AS rack).
4. From the context menu choose System Parameters.

Step 3 — Set the Logical Device Name

In the System Parameter — TCP/IP dialog, select the Unit tab. The Logical Device Name field controls which PC interface the channel uses. Replace any existing value with a PLCSIM device name:

This is the canonical logical device name for the local PLCSIM instance. Apply the change with the Apply button. The dialog also accepts other PLCSIM variants depending on the topology you are simulating:

Step 4 — Restart WinCC Runtime

Close the System Parameters dialog. Close WinCC Explorer completely, then reopen it. WinCC reads the new logical device name only on Explorer startup; hot-edits in an open session will not take effect. Once the Explorer reloads, activate the runtime (Graphics Runtime). The Picture Tree bar should now show empty/clean node icons, and individual tag errors should begin appearing inside AREA1 if any genuine tag faults exist.

Logical Device Name Reference

The logical device name is a Windows-level handle, not a WinCC parameter. It is registered when the corresponding CP driver or PLCSIM installs. You can list the registered names with the Set PG/PC Interface applet or the modern Network and Sharing Center in Windows 10 / 11. The following devices are relevant to the typical PLCSIM scenario:

• PLCSIM.(local) — virtual PLCSIM loopback, always present if S7-PLCSIM is installed.
• PLCSIM.(slot <n>) — multi-PLCSIM, one slot per virtual CPU.
• TCPIP.<nic name> — physical NIC, used when the OS server talks to a real AS.

If PLCSIM.(local) does not appear in the dropdown of the Unit tab, S7-PLCSIM is not installed or has not been registered with Set PG/PC Interface. Reinstall PLCSIM or run Set PG/PC Interface > S7ONLINE (STEP7) > PLCSIM.(local) once manually.

Verifying the Fix

1. Activate the OS Graphics Runtime. The Picture Tree bar shows no triangle.
2. Open the WinCC Explorer Diagnostics tab on the TCP/IP connection. The status reads Connected, and the diagnostic log shows successful reads of the area-relevant tags.
3. In the runtime picture, force a tag error by disconnecting PLCSIM (or stopping the S7 program). The Picture Tree node for AREA1 flips to the red bell, and the iconography propagates up to the parent area. When you restore PLCSIM, all nodes clear within one polling cycle.
4. Cross-check with the WinCC Channel Diagnosis tool (Control Panel > Set PG/PC Interface > Diagnostics). A healthy PLCSIM link reports Online on the chosen logical device.

Extended Troubleshooting Matrix

Project Synchronization Best Practices

Even after binding to PLCSIM, the warning triangle can reappear if the AS project drifts from the OS project. PCS 7 mitigates this through the Plant View and CFC/SFC compiler chain. Use the following workflow:

1. Make CFC/SFC edits in the AS program.
2. Run Compile OS from the SIMATIC Manager or TIA Portal (PCS 7 V9.x). This regenerates the WinCC tag database and the picture tree.
3. Download the OS project to all OS servers and clients.
4. Download the AS program into PLCSIM (or the physical CPU).
5. Activate runtime on the OS server. The Picture Tree opens without warnings.

Skipping any of the first four steps reintroduces the project-mismatch warning.

Safety and Operational Considerations

Always validate the fix against a tag-fault scenario before declaring the channel healthy. Force a known tag-quality degradation (e.g., set an input to bad quality via PLCSIM I/O forcing) and confirm that the triangle / bell appears and clears as expected. Only after this end-to-end exercise should the OS be handed over to operators or test engineers.

Compatibility Notes

The logical device naming convention PLCSIM.(local) is preserved across all supported stacks for backwards compatibility. Sites migrating from PCS 7 V8.x to PCS 7 V9.x generally do not need to change this parameter.

Frequently Asked Questions