WinCC RT Professional Resolving S7ONLINE Interface Connection

Problem Overview

WinCC RT Professional (and the WinCC RT Advanced simulator/runtime) reports "PLC not connected" or fails to update HMI tags, even though the same engineering PC successfully goes online with the SIMATIC S7 PLC over the same Ethernet adapter via TIA Portal. The PC and PLC are typically connected point-to-point (direct LAN cable, no managed switch, no router), and the HMI connection has been compiled and downloaded inside the TIA project.

This is one of the most common commissioning blockers on WinCC RT systems. The root cause is almost never a defective cable, a missing IP route, or a firewall rule: the PC, the PLC, and the project network configuration are usually correct. The actual fault is the application access point that WinCC RT uses to reach the SIMATIC network — a Windows-level setting that lives outside the TIA Portal project and is not part of the device configuration that gets downloaded to the HMI/PC station.

Architecture: How WinCC RT Pro Reaches the PLC

WinCC RT Professional does not use the same communication channel that TIA Portal uses to go online. There are two separate access mechanisms in parallel on the same engineering PC:

1. TIA Portal online access – handled by the TIA Portal's own project tree under "Online > Accessible nodes". The interface is selected per session and does not influence the runtime.
2. WinCC RT runtime channel – handled by the SIMATIC communication layer (S7DOS / S7ONLINE). The runtime queries the Windows registry to find which physical network adapter is bound to the symbolic access point S7ONLINE and uses that adapter to open ISO-on-TCP (port 102) connections to the PLC.

Because the two mechanisms are independent, you can successfully go online with TIA Portal over, say, the Wi-Fi adapter, while WinCC RT is still trying to reach the PLC over a different — or non-existent — Ethernet adapter bound to S7ONLINE. The runtime does not consult the TIA project for interface assignment; it only consults the Windows-level PG/PC interface assignment.

What is S7ONLINE?

S7ONLINE is a symbolic application access point defined in the SIMATIC NET / TIA Portal installation. It maps a logical name to a specific physical protocol stack (for example, TCP/IP via a particular NDIS Ethernet adapter). Many SIMATIC applications — WinCC Runtime, WinCC flexible RT, SIMATIC Logon, S7-PLCSIM coupling, OPC servers — share this single entry point. If S7ONLINE is bound to the wrong adapter, every one of those applications breaks simultaneously, even though TIA Portal online access (which has its own internal access point) continues to work.

Root Cause Analysis

The TIA Portal's network view, the HMI connection editor, and the PG/PC interface configuration each govern a different layer of the communication stack. The relevant layers are:

When the S7ONLINE access point is misconfigured, three observable symptoms appear together:

• WinCC RT remains in "Connecting…" state, then shows "connection interrupted".
• All HMI tags display the worst quality code (e.g., 0x80 in OPC: OPC_QUALITY_BAD); no values are refreshed.
• TIA Portal "Online > Accessible nodes" still finds the PLC on the same physical adapter, because TIA online uses its own session-scoped interface.

A secondary root cause is a stale or missing PC station / Runtime name. The WinCC RT service identifies itself to STEP 7 and the PLC by the symbolic name assigned to the PC Station in the TIA project. If the local Windows computer name does not match the PC Station name embedded in the project, OPC DA / Symbol browsing will fail even when the S7 connection itself is healthy.

Prerequisites

Verify the following before changing any configuration:

1. TIA Portal (V16 or later recommended; compatible with WinCC RT Professional V16 / V17 / V18 / V19 / V20) is installed with the WinCC RT Professional option.
2. The PC has at least one active Ethernet adapter with a static IPv4 address in the same subnet as the PLC (for example PC 192.168.0.10/24, PLC 192.168.0.1/24).
3. WinCC RT Professional is licensed and the license key is valid on the engineering station.
4. The PLC project has been compiled and downloaded to the controller, and a simple GET from TIA Portal > Online > Accessible nodes returns the device type and order number (e.g., 6ES7 515-2AM02-0AB0).
5. You have local administrator rights on the engineering PC — editing the PG/PC interface writes to HKEY_LOCAL_MACHINE\SOFTWARE\Siemens\SINEC and related registry branches.

Solution: Configure the S7ONLINE Access Point

Bind the symbolic access point S7ONLINE to the same TCP/IP adapter that the PLC is connected to. This is a Windows-level operation, not a TIA Portal operation.

Step 1 – Open the PG/PC Interface dialog

1. Close all open TIA Portal and WinCC Runtime instances.
2. Open the Windows Control Panel.
3. Navigate to Set PG/PC Interface (German: PG/PC-Schnittstelle einstellen). The executable behind this Control Panel applet is S7EPATBX.EXE, located in the SIMATIC NET installation directory (typically C:\Program Files\Siemens\Automation\SIMATIC_NET\ or C:\Program Files (x86)\Siemens\Automation\SIMATIC_NET\).
4. When prompted, choose Standard interface for PG/PC and click OK.

Step 2 – Select the correct access point and adapter

1. In the "Access point of the application" list on the left, select S7ONLINE.
2. In the "Interface parameterization used" list on the right, expand the TCP/IP branch and select the physical Ethernet adapter connected to the PLC (e.g., Intel(R) Ethernet Connection I219-LM — TCP/IP).
3. Confirm the entry by clicking OK or Apply.

Typical valid selection values are:

Step 3 – Restart the WinCC Runtime

1. Stop the WinCC RT service (or the WinCC RT Pro instance) completely.
2. From the TIA Portal, perform a full Compile > Software (rebuild all) on the PC station / HMI device, then Download to target device > PC station if the PC station configuration changed.
3. Restart the runtime. Tag values should refresh within 2–5 seconds; the runtime status should transition from connecting to connected.

Configuring the HMI Connection in TIA Portal

Although the S7ONLINE fix resolves the immediate fault, the HMI connection inside the TIA project must also be valid. Per the official TIA Portal documentation for Creating a connection (RT Advanced), the parameters of every HMI connection are configured in the Inspector window of the HMI device or the PC station.

1. In the TIA Portal project tree, expand Devices & Networks and double-click the Networks view.
2. Click the Connections editor at the top of the network view.
3. If no HMI connection exists, drag a connection from the HMI / PC station to the PLC CPU. The connection type is S7 connection.
4. Select the connection line; the Inspector window shows its properties in the following categories.

After changes, compile the HMI / PC station and download it. The download pushes the connection configuration into the local WinCC Runtime's project database, but it does not change the Windows-level S7ONLINE binding — which is why the runtime is still controlled by Step 1 above.

PC Station and Runtime Naming

The PC Station name inside TIA Portal must match the Windows computer name, because the WinCC RT service registers itself under that name and the PLC's connection diagnostics identify the partner by it.

1. Check the Windows computer name: open System > About > Rename this PC (or sysdm.cpl). The full computer name is the value to record.
2. In TIA Portal, open the Devices & Networks editor and select the PC station.
3. In the Inspector window, open Properties > General > General and set the Name field to the Windows computer name. If the HMI is a panel (Comfort / Unified), the panel name must match the Windows name of the engineering PC only when the runtime is simulated locally.
4. Compile the PC station and download. Verify the new name in the Station Configuration Editor (the component config tool, launched from Start > Siemens Automation > Station Configuration Editor) — Component WinCC RT Pro should show RUN with a green icon.

Network Configuration Validation

Before assuming the S7ONLINE fix worked, validate the underlying network. From an elevated command prompt on the engineering PC, run:

ping 192.168.0.1
tracert 192.168.0.1
arp -a

Expected output:

• ping: replies in < 1 ms, 0% loss.
• tracert: a single hop to the PLC IP.
• arp -a: a static entry for the PLC MAC (PROFINET devices usually keep static ARP after the first connection).

On the PLC side, in TIA Portal > Online > Online & Diagnostics, open Diagnostics > Connections. After the runtime starts, a connection of type HMI connection with the partner IP equal to the PC should appear with state established. The connection resource (one of the S7-1500's 16 PG/OP / 124 S7 connections in total, depending on the CPU) is taken from the S7-1500 connection resources table; exceeding it produces error SF<CPU>: Connection resources exhausted in the diagnostic buffer.

Verification

To confirm the runtime is communicating, perform these checks in order:

1. Open the WinCC RT Pro image and click the integrated Diagnostics button (commonly bound to a "system diagnostics" screen). The "Connections" view should show the HMI connection in state Connected.
2. In the WinCC Explorer on the engineering PC, right-click the project and select Runtime > Status. The state should be Running; the connection LED should be green.
3. Force a tag update: bind an output field to a known PLC tag (e.g., "DB_HMI".iwCounter), increment the value from a watch table in TIA Portal, and confirm the HMI display follows within the configured update cycle (default 1 s).
4. Check the WinCC RT Pro log file at %ProgramData%\Siemens\Automation\WinCCRT_Pro\<ProjectName>\Logs\. Look for entries with severity Information and source S7DOS containing the text Connection established and the IP/port of the partner.

Common Pitfalls and Edge Cases

Advanced Diagnostics

When the S7ONLINE assignment is correct and the network is healthy, but the connection still fails, escalate to the lower-level diagnostic tools:

1. SIMATIC NET diagnostics: launch Start > Siemens Automation > SIMATIC NET Diagnostics. The Connections view shows every S7 / OPC / PROFINET connection the local station has opened, including the source and destination TSAP, port, and state.
2. S7Trace / S7PacketTrace: in the SIMATIC NET installation, run S7Trace.exe to capture raw S7 telegrams. Filter by partner IP and protocol (ISO-on-TCP, port 102) to verify the runtime is sending TPKT/COTP connect requests at all.
3. Wireshark: capture on the same interface bound to S7ONLINE. Apply the display filter tcp.port == 102. You should see a TPKT/COTP CR (Connection Request) from the PC to the PLC's IP, followed by CC (Connection Confirm) from the PLC. If no CR appears within 30 s, the runtime is not reaching the adapter at all — most likely a Windows-level binding issue, not a network issue.
4. PLC diagnostic buffer: read the PLC's diagnostic buffer via TIA Portal. Events of class Communication with IDs 0x01A4 (connection established), 0x01A5 (connection terminated), or 0x01A7 (connection rejected, no resources) pinpoint the side that is rejecting the connection.
5. Event Viewer: on the PC, the Applications and Services Log > Siemens Automation channel contains S7DOS and OPC events with vendor-specific error codes. Common codes:
   • 0xFF00 0x0008 — partner not reachable.
   • 0xFF00 0x0014 — TSAP not configured / partner resources exhausted.
   • 0xFF00 0x0030 — local S7DOS could not bind the configured interface (frequently caused by S7ONLINE mis-binding).

Preventive Measures for Future Commissioning

• Document the S7ONLINE binding for every engineering PC in the project quality plan; rebinding is required whenever a new network adapter is installed (USB-Ethernet, Thunderbolt dock, VPN client).
• Use a dedicated Ethernet adapter for the PLC network, configured with a fixed IP outside the DHCP range, and disable any "Internet sharing" or "metered connection" feature on the same adapter.
• For laptop engineering PCs, write a startup script that runs S7EPATBX /auto to enforce the standard assignment on every reboot.
• When adding a new HMI connection in TIA Portal, always verify the Access point property of the connection shows S7ONLINE, not the legacy CP-TCPIP or an empty string.