WinCC RT Advanced V17: Resolving IE General Connection Failures to S7-1200

This technical reference addresses a recurring failure mode encountered when commissioning WinCC Runtime Advanced V17 on Windows 10 with S7-1200 CPUs using the IE General (PROFINET/Industrial Ethernet) interface. The most common symptom is a configured project that compiles cleanly and starts the runtime, but the HMI tags show Connection failed or remain in No connection state, while the same physical wiring worked under TIA Portal V14/Windows 7. The fix is rarely a single switch; it spans HMI connection creation, PG/PC interface assignment, S7-1200 firmware revision, and TLS-secure-communication settings introduced in V17.

1. Problem Overview and Failure Mode

Engineers migrating from TIA Portal V14 SPx (Windows 7) to TIA Portal V17 (Windows 10) frequently report that their WinCC Runtime Advanced projects fail to establish an S7 connection even though:

• The HMI and PLC are on the same subnet (e.g., 192.168.0.0/24).
• The PLC is reachable via ping from the engineering station.
• The TIA Portal project compiles without errors.
• The Online > Accessible nodes function in TIA Portal detects the S7-1200 CPU.

The runtime starts, but the connection status in the WinCC RT Advanced diagnostics window reports one of the following:

The diagnostic step that resolves more than 70% of field cases is the explicit creation of an HMI connection inside Devices & Networks. Without this object, WinCC Runtime Advanced has nothing to bind to when the runtime image is generated.

2. Root Cause Categories

Three independent root-cause families account for nearly all reported failures. Each must be eliminated in turn.

2.1 Missing HMI Connection Object

Unlike WinCC flexible or early TIA versions where the HMI tag automatically inferred its PLC partner from the symbolic address, TIA Portal V17 requires the user to draw an explicit HMI connection between the HMI device and the S7-1200 CPU inside the Devices & Networks editor. If the connection is missing, the runtime starts but the tag DB remains unbound.

2.2 PG/PC Interface Mis-assignment on Windows 10

Windows 10 manages network adapters differently than Windows 7, especially when Hyper-V, VMware, or VPN virtual adapters are present. The S7ONLINE access point must point to the physical Ethernet adapter that is wired to the PLC subnet. Mis-assignment to a virtual adapter results in silent failure.

2.3 S7-1200 Firmware Compatibility

Siemens introduced stricter security defaults in CPU firmware V4.5 and V2.9 (for S7-1200). With these revisions, the PLC rejects connection attempts from HMI devices that do not have a valid slot or that use legacy, unencrypted access. WinCC Runtime Advanced V17 and lower require either firmware patches on the PLC side or the secure-communication path documented by Siemens.

3. Prerequisites

Before troubleshooting, confirm the following engineering environment:

• TIA Portal: V17 Update 4 or later (recommended V17 + HSP for S7-1200 V4.6).
• WinCC Runtime Advanced: V17, build 17.0.0.0 or later.
• Operating system: Windows 10 LTSC 2019/2021 (64-bit) or Windows 11 IoT Enterprise.
• S7-1200 CPU: any 12xx with PROFINET interface (CPU 1211C/1212C/1214C/1215C/1217C), firmware V4.x.
• Administrator rights on the engineering PC to modify the PG/PC interface and the Windows firewall.
• Network: direct Ethernet cable, managed switch, or routed subnet. Both PC and PLC must be in the same broadcast domain or have a route.
• Available IP addresses: assign static IPs (do not rely on DHCP for HMI/PLC links).

4. Step-by-Step Resolution Procedure

Step 1 — Create the HMI Connection in TIA Portal V17

1. Open the TIA Portal project.
2. Switch to Devices & Networks in the project tree.
3. In the network view, click the Connections button on the toolbar.
4. Select HMI connection from the dropdown.
5. Click the HMI device (e.g., HMI_1) and drag a line to the S7-1200 CPU (PLC_1).
6. In the inspector window, under Properties > General > Interface, confirm:
   • End point 1: WinCC Runtime Advanced (or panel)
   • End point 2: PLC_1, interface PN/IE_1
7. Open the Properties > General > Connection tab and verify:

8. Compile the project: Right-click HMI_1 > Compile > Software (rebuild all).
9. Download to the RT station: Online > Download to target device > PC station.

Step 2 — Configure the PG/PC Interface in Windows 10

1. Open Control Panel > Set PG/PC Interface (search for "Set PG/PC" in the Windows search box).
2. Under Access Point of the Application, select S7ONLINE.
3. In Interface Parameter Assignment Used, choose the physical Ethernet adapter bound to the PLC subnet (e.g., Intel(R) Ethernet Connection I219-LM.TCPIP.1).
4. If the adapter is not listed, click Add/Remove and install the TCP/IP protocol for the adapter.
5. Click OK and confirm the Windows dialog.
6. Restart the WinCC Runtime Advanced service: services.msc > Siemens WinCC Runtime Advanced > Restart.

The same setting is reachable inside TIA Portal at Online > Accessible nodes > [PG/PC interface]. Always verify both paths; they are independent and may diverge after VPN client installation.

Step 3 — Confirm S7-1200 Firmware Compatibility

1. Read the CPU firmware in Online > Accessible nodes > PLC_1 > Online & Diagnostics.
2. Compare the firmware revision against the table below.

For S7-1200 firmware V4.5 and V2.9 specifically, Siemens published a FAQ documenting that panels and WinCC RT Advanced V17 or lower may fail to connect when the PLC has the new connection-security mechanism active. The corrective action is one of:

• Upgrade the HMI/RT project to a version that supports secure communication.
• Disable the "Connection security" check in the CPU properties.
• Insert the HMI into the PLC's connection resource list explicitly.

Step 4 — Disable Secure Communication (Quick Fix Only)

1. Select the S7-1200 CPU in the project tree.
2. Open Properties > General > Connection mechanisms.
3. Uncheck Permit access with PUT/GET communication from remote partner if it is the source of conflict; alternatively, ensure Secure communication is enabled on both sides and that the PLC certificate is loaded into the Runtime Advanced certificate store.
4. Recompile and re-download.

Step 5 — Activate Secure Communication (Recommended for Production)

WinCC Runtime Advanced / Runtime Professional supports TLS-encrypted communication to S7-1200 / S7-1500 CPUs. The connection is encrypted using certificates issued by the TIA Portal project CA and exchanged during project download.

1. In the HMI device properties (Properties > General > Connection mechanisms), set Secure communication = Activated.
2. In the PLC properties, set Secure communication = Activated and select the certificate issued for this CPU.
3. Ensure the Siemens Engineering TLS CA certificate is installed on the Runtime PC in the local computer store: certlm.msc > Trusted Root Certification Authorities.
4. Compile and download both devices.
5. Restart the WinCC Runtime Advanced service.

5. Network and Addressing Setup

5.1 IP Addressing Reference

5.2 Minimum Topology

The two critical ports for S7 communication are:

• 102/tcp — ISO-TSAP (COTP), used by S7ONLINE legacy connections.
• 443/tcp — HTTPS / TLS, used by secure communication in V17.

Confirm port reachability from an elevated command prompt before blaming the runtime:

Test-NetConnection 192.168.0.20 -Port 102
Test-NetConnection 192.168.0.20 -Port 443

6. WinCC Runtime Advanced Configuration

6.1 Runtime Project Generator Settings

6.2 Configuration File Locations

WinCC Runtime Advanced stores runtime data in %ProgramData%\Siemens\Automation\RTAdvanced\<ProjectName>\. Connection diagnostics are appended to:

C:\ProgramData\Siemens\Automation\RTAdvanced\<Project>\Logs\WinCCRTAdvanced.log
C:\ProgramData\Siemens\Automation\RTAdvanced\<Project>\Logs\Connection.log

Search the file for the strings 0x80072EE2, 0x80070005, or WCCRT: connection failed to narrow down the cause.

7. Verification Procedure

After applying the configuration changes, run the following verification sequence:

1. Compile and download the HMI project to the PC station.
2. Start the runtime: Start > Programs > Siemens Automation > WinCC Runtime Advanced, or via services.msc.
3. On the runtime screen, insert a diagnostics screen with a tag showing the connection status (e.g., @ConnectionState_HMI_Connection_1).
4. In the WinCC RT Advanced "Runtime Diagnostics" window, verify the status bar reads Connected.
5. In TIA Portal, run Online > Online & Diagnostics > Connection diagnostics on the S7-1200 CPU. Confirm at least one HMI partner is listed with state Established.
6. Toggle a discrete output on the PLC and observe the corresponding HMI tag update within one polling cycle.
7. Force a value from the HMI to a PLC tag and verify it appears in the PLC's watch table.

8. Extended Troubleshooting Matrix

9. Edge Cases and Field-Proven Caveats

9.1 Virtual Network Adapters

Hyper-V, WSL, Docker, and Cisco AnyConnect virtual adapters register themselves as TCP/IP interfaces and may hijack the S7ONLINE access point. Disable these adapters in Device Manager or demote them below the physical adapter in binding order:

ncpa.cpl > Advanced > Advanced Settings > Provider Order

9.2 Dual-NIC Engineering Stations

If the PC has one NIC for the office network and another for the plant, configure the plant NIC with the lower metric to win the S7ONLINE binding. In PowerShell:

Set-NetIPInterface -InterfaceAlias "Plant_NIC" -InterfaceMetric 10

9.3 IPv6 Interference

Windows 10 prefers IPv6 by default. If the PLC only supports IPv4, the HMI may attempt to resolve the PLC's DNS name to an IPv6 address and fail. Either disable IPv6 on the engineering NIC or force IPv4 resolution by editing %windir%\System32\drivers\etc\hosts with a static IPv4 entry.

9.4 Windows Firewall Rules

The Windows Firewall may block inbound responses on port 102. Add an explicit rule for CCRTAdvanced.exe:

New-NetFirewallRule -DisplayName "WinCC RT Advanced S7" `
  -Direction Inbound -Program "C:\Program Files\Siemens\Automation\WinCC RT Advanced\CCRTAdvanced.exe" `
  -Action Allow -Protocol TCP -LocalPort 102,443

9.5 Project Reused from V14

When migrating a V14 project to V17, the compiler may keep stale connection IDs. Open Project > Compile > Software (rebuild all) to force regeneration of the HMI connection DB.

9.6 TIA Portal Multiuser Server

If the project resides on a TIA Portal multiuser server, the local cache may not contain the latest HMI connection definition. Run Server > Synchronize with server before compiling.

10. Standards and Documentation References

• Secure communication (RT Advanced, RT Professional) — TIA Portal V20 Communication Manual
• WinCC Runtime Advanced V17 system manual — available inside the TIA Portal V17 help system under Visualize processes > WinCC > Runtime Advanced.
• S7-1200 programmable controller system manual — chapter "Communication" lists the ISO-TSAP slot assignment.

11. Recommended Workflow Summary

WinCC RT V17 / S7-1200 Connection Failure
        │
        ▼
Does an HMI connection exist in Devices & Networks?
        │
   ┌────┴────┐
   No        Yes
   │         │
   ▼         ▼
Create HMI  Is the PG/PC interface
connection, assigned to the physical
recompile   NIC with S7ONLINE?
                │
           ┌────┴────┐
           No        Yes
           │         │
           ▼         ▼
       Reassign   Does ping succeed?
       S7ONLINE       │
                 ┌────┴────┐
                 No        Yes
                 │         │
                 ▼         ▼
            Check cable  Is PLC firmware
            & firewall   >= V4.5?
                            │
                       ┌────┴────┐
                       No        Yes
                       │         │
                       ▼         ▼
                  Upgrade    Enable TLS or
                  firmware   disable secure-comm
                              on PLC