Fixing WinCC Unified V20 S7-1200 Connection via PG/PC Interface

Problem Overview: WinCC Unified V20 Loses Communication with S7-1214C

A WinCC Unified PC Runtime V20 installation deployed on a customer workstation stops exchanging data with a SIMATIC S7-1214C DC/DC/DC (article number 6ES7214-1AG40-0XB0) after several months of stable operation. The TIA Portal V19 project compiled successfully, the offline transfer ran without errors, the WinCC Unified RT license was activated, and the SCADA PC (192.168.0.2/24) could still ping the S7-1214C (192.168.0.1/24). Despite this Layer-3 reachability, Runtime tags display ##QUALITY_BAD and the connection status indicator in the Unified RT shows the HMI connection in the Disconnected state.

This failure pattern is the most common post-deployment outage reported for WinCC Unified PC RT V20 against SIMATIC S7-1200/1500 controllers. The Siemens documentation library identifies the troubleshooting path in the Procedure if there is no connection (RT Unified) guide, which checks cabling, connector seating, and the online state of the configured connection. When those basics pass, the next suspect is the PG/PC interface assignment in the Windows Control Panel, which is the layer that WinCC Unified PC RT uses to bind the S7Online protocol stack to a physical Ethernet adapter.

Affected Environment & Versions

WinCC Unified PC RT V20 requires either TIA Portal V19 or V20 on the engineering station to compile and download. Runtime targets running V20 must be programmed against a matching project version. Mismatch between engineering and runtime is a separate failure mode and is documented as such in the TIA Portal V20 release notes.

Root Cause Analysis: PG/PC Interface Assignment

The S7Online protocol stack, used by every TIA Portal component and by WinCC Unified PC RT for S7-1200/1500 communications, binds to a physical or virtual network adapter through the Set PG/PC Interface entry in the Windows Control Panel. This selection lives in the registry hive HKLM\SOFTWARE\Siemens\SINEC\S7ONLINE\S7ONLINE.DLL\Protocols and is consulted by the Unified runtime whenever it opens an HMI connection to a SIMATIC PLC.

Three failure modes produce the reported symptom of "connection not established" after a previously working deployment:

1. Adapter changed: A different NIC was selected (e.g., a Wi-Fi adapter or a Hyper-V virtual switch) following a Windows update, driver update, or installation of additional software such as a PLC simulator or a second virtualization stack.
2. S7Online not selected as access point: The access point of the application is no longer routed to S7ONLINE. WinCC Unified defaults to the S7ONLINE access point for integrated connections; if the application is bound to another access point (e.g., CP_HMI_1), the runtime will fail to open the connection.
3. Third-party software overwrites the binding: Floating licenses for TIA Portal, STEP 7, or SIMATIC NET installers can rewrite the PG/PC interface table when their setup routines run. Software that adds TAP adapters, VPN clients, or virtual Ethernet bridges also pushes the original physical NIC down the priority list.

The original incident in the field report matches the third pattern. After installation of additional floating-license tooling and other TIA-related software on the SCADA PC, the Set PG/PC Interface dialog showed the Ethernet port bound to S7Online, but it pointed to a virtual adapter created by the third-party tooling rather than the physical Intel/Realtek Ethernet port wired to the PLC.

Pre-Diagnostic Checklist

Before re-binding the PG/PC interface, eliminate the simpler failure modes documented in the Siemens TIA Portal V20 troubleshooting procedure:

1. Cabling and connectors: Verify the RJ45 link LED on the SCADA PC and on the S7-1214C X1 port. Replace the patch cable. Confirm the switch port (if used) is not administratively down.
2. PLC IP reachability: From an elevated command prompt on the SCADA PC, execute ping 192.168.0.1 -t. A reply confirms Layer-3 reachability but does not prove S7 communication.
3. PLC online state: Open TIA Portal on the engineering station, switch to Online → Accessible nodes, and confirm the S7-1214C appears with its configured IP. The MAC address should match the label on the CPU front.
4. CPU run/stop state: The CPU must be in RUN mode, not STOP. A CPU in STOP still answers Ping and accepts TIA online connections but will refuse HMI tag updates in some configurations.
5. Connection configuration in TIA: Open the project, navigate to Devices & Networks → Networks view → Connections, and verify the HMI connection between the WinCC Unified PC station and the S7-1214C is marked online in the project and points to the correct PLC IP.
6. License state: Open the Automation License Manager. The Unified PC RT V20 license must be on the local drive or on a reachable license server. A missing or expired RT license will produce connection errors that can be misread as PG/PC interface problems.
7. Firewall: Confirm Windows Defender Firewall or a third-party host firewall allows outbound TCP/UDP on port 102 (ISO-on-TCP / S7Comm) from the WinCC Unified RT service account. Siemens uses port 102 for S7 communication by default; do not change unless the project explicitly remaps it.

If items 1 through 7 all pass and the runtime still shows disconnected, proceed to the PG/PC interface re-binding in the next section.

Step-by-Step Resolution: Reassigning the PG/PC Interface

The PG/PC interface is configured outside of TIA Portal, in the Windows Control Panel. WinCC Unified PC RT reads this binding at service start and again whenever a connection is reopened. The procedure below restores the binding to the physical Ethernet port connected to the PLC network.

Step 1 - Open Set PG/PC Interface

On the SCADA PC, click Start → Control Panel → Set PG/PC Interface. If the Control Panel view is set to Category, switch to Small icons or Large icons to expose the legacy applet. The dialog can also be invoked directly with "C:\Program Files (x86)\Siemens\Automation\SimaticOam\bin\s7onlinestep.exe" if installed by a TIA Portal setup.

Step 2 - Select the S7ONLINE Access Point

In the Access Point of the Application dropdown, choose S7ONLINE. This is the access point that WinCC Unified PC RT and every TIA Portal online operation use by default. Do not select access points such as CP_HMI_1 or S7ONLINE (STEP7) unless the project explicitly requires them.

Step 3 - Bind the Correct Network Adapter

In the Interface Parameter Assignment Used list, locate the entry whose description matches the physical Ethernet adapter wired to the PLC network. Typical identifiers on a SCADA PC:

• Intel(R) Ethernet Connection I219-LM
• Realtek PCIe GbE Family Controller
• Broadcom NetXtreme Gigabit Ethernet

Select that entry. The right pane shows the assigned interface parameterization, which for S7-1200/1500 over Ethernet should be TCP/IP (Auto). Do not select:

• Wi-Fi adapters (Intel Wi-Fi 6 AX201 and similar) - they route through unrelated subnets.
• Hyper-V, VirtualBox, or VMware virtual switches (Hyper-V Virtual Ethernet Adapter) - they are not bound to the physical PLC network.
• VPN TAP adapters (WireGuard Tunnel, TAP-Windows Adapter V9) - these can hijack the routing table.
• Dongle-based mobile broadband - will not reach the PLC subnet.

Step 4 - Apply and Restart the Runtime

Click OK to apply the binding. Then restart the WinCC Unified PC RT service to force the runtime to re-open all HMI connections through the new binding:

sc stop "Siemens HMI RuntimeManager"
sc start "Siemens HMI RuntimeManager"

On a fresh installation the runtime host service is named Siemens HMI RuntimeManager. Older V17/V18 deployments may still use WinCC Unified PC RT; confirm the actual service name in services.msc before issuing the stop/start commands.

Step 5 - Validate from TIA Portal

With the PG/PC interface correctly bound, open TIA Portal on the engineering station and perform Online → Accessible nodes. The S7-1214C should appear with its MAC address. The WinCC Unified PC station should also be visible if a reverse connection is configured. This is the cleanest way to confirm that the S7Online stack is now talking to the correct adapter.

Verifying Connection Recovery

Once the PG/PC interface is corrected, validate the runtime end-to-end with the following three checks:

1. Runtime diagnostics view: In the WinCC Unified PC RT tray icon, open Diagnostics → Connections. The connection to the S7-1214C should transition from Disconnected to Connected (establishing connection) within a few seconds and then to Connected. The status word reflects the OPC UA subscription state underneath.
2. Tag values: Open any screen that displays a tag from the S7-1214C (for example, an analog input from an SM1231 module or a Boolean from the AHU enable coil). The ##QUALITY_BAD overlay should disappear within one polling cycle. Default Unified PC RT cycle is 1 s for the data manager; verify by checking HMI tags → Cycle in the TIA project.
3. Event log: Filter the Windows Event Log under Siemens Automation → HMI Runtime for the source Siemens.Hmi.Wincc.Unified.Runtime. A successful reconnection emits HmiConnection: Connection established with the configured connection name.

Secondary Configuration Checks After a Connection Drop

If the PG/PC interface is confirmed correct and the runtime still does not connect, work through the secondary layer of checks:

Certificate Validation

WinCC Unified PC RT V20 enforces TLS on integrated HMI connections when the project is configured for certificate-based authentication. Self-signed certificates are generated at install time and rotated on the first connection attempt. If the certificate on the PLC was replaced (for example, after a firmware update that resets the security settings), the Unified RT will reject the new certificate and refuse the connection.

Procedure:

1. On the SCADA PC, open the certificate store under Local Computer → Personal → Certificates. Look for a certificate issued to CN=Siemens, O=Siemens AG.
2. In the Unified RT configuration (accessible via the Unified Configuration tool installed with the runtime), verify the certificate path under Security → Certificates.
3. If the certificate does not match, re-import the certificate exported from TIA Portal under Devices & Networks → CPU → Properties → Security → Certificate manager.

Time Synchronization

OPC UA sessions in Unified V20 require a clock skew of less than 60 seconds between the SCADA PC and the PLC. If the workstation clock drifts (common after a Windows update on a domain-isolated PC), the runtime will reject the session handshake. Set both devices to an NTP source or manually synchronize them.

CPU Protection & Access Level

The S7-1214C's Protection & Security → Connection mechanisms must allow PUT/GET communication from the HMI. In TIA Portal, navigate to CPU Properties → Protection → Connection mechanisms and confirm Permit access with PUT/GET communication is enabled. Without this, HMI connections from third-party or pre-V14 PC systems can be denied.

Antivirus / Endpoint Protection

Some endpoint security suites (CrowdStrike, SentinelOne, Trend Micro) intercept raw TCP port 102 traffic and inject a TLS termination that breaks S7 communication. Add the WinCC Unified PC RT installation folder (C:\Program Files\Siemens\Automation\WinCCUnified) and the Siemens HMI RuntimeManager service to the AV exclusion list.

Preventive Hardening for Field Deployments

To prevent recurrence, fold the following measures into the standard deployment procedure for any Unified PC RT V20 workstation:

1. Lock the PG/PC interface from a deployable script. Use the registry path HKLM\SOFTWARE\Siemens\SINEC\S7ONLINE with the value SetInterfaceForOnline = "S7ONLINE:<AdapterName>:TCPIP.Auto" and apply via Group Policy or a deployment script.
2. Disable unused adapters. In Device Manager, disable Wi-Fi, Bluetooth PAN, Hyper-V virtual switches, and any VPN TAP adapter that the SCADA workstation does not need. This removes them as candidates in the PG/PC interface list.
3. Standardize on a single NIC per SCADA PC. If the workstation has both an onboard NIC and a PCIe NIC, wire the PLC network to a known, labeled NIC and bind S7ONLINE to it exclusively.
4. Document the deployment image. Capture the working PG/PC binding and the network adapter order in the deployment runbook so that a future image rebuild reproduces the same state.
5. Restrict installation of additional Siemens software. Floating licenses for STEP 7, TIA Portal, and SIMATIC NET can rewrite the PG/PC interface table during their setup. Schedule these installations during planned maintenance windows and revalidate the PG/PC interface after each.
6. Add a startup watchdog. Use the Windows Task Scheduler to run a PowerShell script at boot that checks the PG/PC interface binding against a known-good value and writes a Windows Event Log entry if the binding has drifted.

Troubleshooting Matrix

Field Note: Why This Issue Surfaces Months After Deployment

Most reported incidents of this type do not surface during commissioning. The commissioning engineer installs the project, validates the runtime, and hands the PC to the customer. Months later, the customer installs software updates, antivirus updates, or additional engineering tools, and one of those installers silently rewrites the PG/PC interface table. The runtime continues to load and the screens render, but the OPC UA subscription layer cannot reach the PLC through the now-wrong adapter, and the SCADA goes blind.

The fix is small in scope (one dialog, one restart) but the diagnostic path is non-obvious because every other layer of the stack still appears healthy. The Siemens TIA Portal V20 procedure for "no connection" with RT Unified walks through this exact sequence and should be the first reference consulted when an established Unified PC RT deployment loses its S7-1200/1500 connection.

Frequently Asked Questions