Resolving WinCC Yellow Triangle on S7 PC Station Connection

Problem Overview: WinCC Runtime Yellow Triangle

The yellow triangle displayed on a WinCC object in Runtime is the standard SIMATIC WinCC visualization indicator that the tag's configured connection cannot be reached. The tag is correctly defined in the WinCC Explorer, but the underlying S7 channel — typically the named S7 connection to a SIMATIC S7-300 or S7-400 — is not in Connected state when the picture is loaded. The connection layer between PC Station and PLC must be verified first; tag mapping, picture scripting, and process value scaling can only be debugged after the channel is alive.

In a single-user, multi-user, or distributed HMI station the yellow triangle maps to one of the following root cause families:

• PC Station configured in STEP 7 HW Config but never downloaded to the runtime PC
• WinCC application slot not RUN-P in Station Configurator (pen shows red bar)
• SIMATIC NET / NCM PC runtime layer missing — channel DLL cannot bind to the S7 connection
• S7 connection built in NetPro but not downloaded to the PC Station and to the PLC
• PC Station name in STEP 7 not identical to the Windows computer name (including trailing characters)
• Ethernet adapter bound to the wrong access point in Set PG/PC Interface
• Transport protocol mismatch between PC Station and PLC (TCP/IP RFC1006 vs ISO-on-TCP, or different S7 connection partner address)

Affected Environment and Versions

PC Station Architecture and Component Roles

The PC Station is the runtime container that STEP 7 HW Config builds on the engineering station and that Station Configurator replicates on the runtime PC. Each slot represents a SIMATIC software module. The two slots that must be RUN-P for WinCC tags to reach the PLC are:

Diagnostic Matrix: Symptom to Root Cause

Prerequisites

1. STEP 7 V5.4 or higher with HF/SP installed on the same Windows account that will run WinCC Explorer.
2. WinCC V7.x installed; verify WinCC Information Server and WinCC Channel Diagnosis are present.
3. SIMATIC NET CD installed (provides S7DOS / SAPI / IE General driver). If STEP 7 was installed first, the SIMATIC NET runtime layer is registered automatically; if WinCC was installed first, run the SIMATIC NET setup and select NCM PC as the install profile.
4. Windows administrator privileges during STEP 7, WinCC, and Station Configurator edits.
5. Ethernet adapter present on the runtime PC (laptop LAN port or USB-to-Ethernet) and reachable to the PLC subnet.
6. Both PLC and PC Station placed in the same IP subnet (for example PC 192.168.0.10 / 24, PLC 192.168.0.1 / 24).
7. Firewall rule allowing S7 communication on TCP/102 (default ISO-on-TCP port). Disable Windows Firewall temporarily during commissioning, then re-enable with explicit rules.

Step-by-Step Resolution Procedure

Step 1 — Verify Installation and Station Name

1. Open Control Panel → Programs and Features and confirm the following entries are present: SIMATIC WinCC V7.x, SIMATIC STEP 7 V5.x, SIMATIC NET (version should match or be higher than STEP 7).
2. Open Start → Programs → Siemens Automation → SIMATIC → Station Configurator. Note the computer name shown in the title bar — for example DESKTOP-AB12CD3. Note the trailing period: it is part of the fully qualified DNS name and must be reproduced exactly in the STEP 7 PC Station object.
3. Open Start → Settings → System → About and copy the device name as a sanity reference.

Step 2 — Build the PC Station in STEP 7 HW Config

1. In SIMATIC Manager open the STEP 7 project, then double-click Hardware.
2. If a PC Station is missing, right-click the project, choose Insert New Object → SIMATIC PC Station.
3. Rename the PC Station so that its Name property matches the Windows computer name exactly, including any trailing period. The case is not enforced but keep it identical to avoid the warning dialog during download.
4. Open the PC Station hardware catalog. Drag WinCC Application → WinCC Application V7.x into slot 1.
5. Drag IE General → IE General into slot 2 (older projects use slot 3). Set the IP address, subnet mask, and router only if no other Industrial Ethernet interface is assigned.
6. If a CP1613 / CP1623 / CP1628 is present, insert IE → IE (CP1613/CP1623/CP1628) instead of IE General.
7. Save and compile the HW Config.

Step 3 — Configure the S7 Connection in NetPro

1. Open NetPro from the SIMATIC Manager toolbar.
2. Click the WinCC Application in the PC Station row to select it; the lower table now shows the connections owned by that application.
3. Right-click in the connection table and choose Insert New Connection. Select S7 connection, partner = the PLC CPU, and confirm.
4. Open the new connection's Properties dialog. Set Type to TCP/IP or ISO-on-TCP — the choice must match what the PLC CP supports. For onboard PROFINET interfaces on S7-300 / ET200S, use TCP/IP. For older CP343-1 / CP443-1, use ISO-on-TCP.
5. Verify the partner IP address matches the PLC interface IP. Set Establish active connection = checked (WinCC is the active endpoint).
6. Close the properties and save NetPro.

Step 4 — Compile OS

1. In SIMATIC Manager, right-click the PC Station and choose Compile OS.
2. The Compile OS dialog appears. Select the previously created S7 connection so the tag pointers are written to the WinCC project under the Named Connections folder.
3. Wait for the compile to finish. If the dialog warns "No WinCC project found" or "No S7 connection selected", return to Step 3 and confirm the connection was actually inserted on the WinCC application slot, not on the IE slot.
4. Open WinCC Explorer. Under Tag Management → SIMATIC S7 PROTOCOL SUITE → Named Connections the S7 connection must now appear. Drag it open — if the folder is empty, OS compile did not write the pointers.

Step 5 — Assign Tags and Pictures

1. In WinCC Explorer, expand Tag Management, right-click the named connection, and choose New Tag.
2. Set the tag Address to the absolute PLC address (for example DB100.DBD0). The Quality Code property should be set to According to OPC.
3. Open the Graphics Designer picture, drag an I/O field onto the canvas, and bind the configured tag to the Output Value property.
4. Save the picture. The yellow triangle is still expected at this point — the Runtime is not yet running.

Step 6 — Download HW Config to PC Station and PLC

1. Return to HW Config of the PC Station.
2. Right-click the PC Station object and choose Download to PC Station. Select the target PC Station name (must match Windows computer name). Confirm the download.
3. Open NetPro, right-click the S7 connection, and choose Download → Selected and Partner Stations. Confirm. The download writes the connection table to both the PC Station and the PLC.
4. If only the PC Station downloads but the PLC does not, open HW Config of the PLC, choose PLC → Download to Target System, and verify the CPU is in STOP or RUN-P with consistent project data.

Step 7 — Start Station Configurator in RUN-P

1. Open Station Configurator. Right-click WinCC Application and select RUN-P. The pen should clear.
2. Right-click IE General and select RUN-P. The pen should clear.
3. Open the Diagnostic tab. The Status row must read OK for both slots. If any module shows a red X or red bar, expand the row to read the reason (for example Address already in use or Driver not loaded).
4. Click Save. Station Configurator persists the component states across reboots.

Step 8 — Configure Set PG/PC Interface

1. Open Start → SIMATIC → STEP 7 → Set PG/PC Interface.
2. Select the Application Access Point = S7ONLINE (STEP 7) → TCP/IP → <your Ethernet adapter>. If multiple adapters exist, pick the one whose IP address is on the PLC subnet.
3. Click OK and reboot the PC. Windows service SIMATIC S7DOS Help Service binds to the chosen adapter only after restart.

Step 9 — Activate WinCC Runtime and Verify

1. In WinCC Explorer click Activate Runtime.
2. The picture loads; I/O fields bound to configured tags should display the actual process value within 1–2 seconds. Yellow triangles must be absent.
3. Open Tools → Channel Diagnosis. Confirm Connection Status shows Connected for the named S7 connection. The byte count and packet count increase on every PLC scan cycle.

Verification Checklist

Channel Diagnosis and Error Code Mapping

Channel Diagnosis logs each named connection. Hex error codes originate from the S7DOS / SAPI layer:

Laptop-Specific Pitfalls

When the runtime PC is a single laptop with one Ethernet adapter and no separate system bus, three configuration traps appear repeatedly:

1. Single network adapter for terminal and system bus — When the PG/PC interface is the same Ethernet port used to talk to the PLC, STEP 7 download works because it goes through TCP/IP to the PLC's PROFINET interface. WinCC Runtime must use the same path. Disable any virtual adapters (Hyper-V, VPN, VirtualBox host-only) that could win the route to the PLC subnet.
2. Power management turning off the LAN port — Windows default power profile disables the Ethernet adapter to save battery. Open Device Manager → Network Adapters → Properties → Power Management and uncheck Allow the computer to turn off this device to save power.
3. Sleep / hibernation — When the laptop wakes, the SIMATIC S7DOS service may not rebind the S7 connection. Workaround: disable sleep on AC power in Control Panel → Power Options.

NetPro Status Field Interpretation

After the OS is compiled and both ends have been downloaded, opening the S7 connection in NetPro and selecting Active/Deactivate Connection Status frequently returns "not available" even when WinCC tags update correctly. This is normal: NetPro polls the WinCC Application via OPC, and a yellow-triangle Runtime will report the connection as DOWN. Trust Channel Diagnosis in WinCC Explorer rather than NetPro status during commissioning.

Restart Procedure When Nothing Else Works

1. Close WinCC Explorer and stop WinCC Runtime.
2. Open Station Configurator and set both components to STOP.
3. Delete the STEP 7 project on the engineering station if corrupted; back up first.
4. Reboot Windows.
5. Re-open STEP 7, rebuild PC Station, repeat Steps 2–9 above in order.

FAQ