Resolving PROFINET PC Station Connection Issues in TIA Portal V20

Overview

Connecting a SIMATIC PLC to a PC station running TIA Portal with PROFINET often fails because engineers conflate three distinct communication paths: engineering online access, HMI (WinCC Runtime) data exchange, and PROFINET IO controller/device traffic. Each path uses different hardware, different protocol layers, and different configuration objects inside the TIA project. Misplacing CP1612 cards in an HMI configuration, choosing the wrong PC station interface, or selecting a virtual machine NIC as the online target are the most common root causes of the "failed to establish a connection to the device with address" error.

This reference consolidates the official Siemens configuration rules with the field-proven diagnostics for resolving PC Station → S7-PLC communication problems, including the IE General versus CP 1612/IE PB decision, the WinCC Runtime connection setup, and the PG/PC interface assignment in Windows.

Communication Path Classification

Before touching any TIA dialog, classify which communication path you actually need. Engineers regularly wire the wrong bus to the wrong PC station slot.

Prerequisites

1. TIA Portal V16 or later installed (V20 referenced in Useful Information on Configuring PROFINET / Industrial Ethernet in TIA V20).
2. SIMATIC S7-1500 / S7-1200 / S7-300 / S7-400 PLC with current firmware. Note the order number (6ES7 ...) and the firmware version (read from the PLC's online diagnostics or the device label).
3. Ethernet cabling verified: at least one of the PLC's PROFINET ports (X1, X2) connected to a switch, router, or directly to the PC's Ethernet NIC. A direct 1:1 cable is acceptable for point-to-point commissioning.
4. Windows Set PG/PC Interface dialog accessible (Control Panel → Set PG/PC Interface).
5. If WinCC Runtime is involved, install the matching WinCC RT version on the engineering PC and license the RT tag counts.
6. Disable third-party firewalls or open TCP/UDP ports 102 (S7), 34962/34963/34964 (PNIO), and 49152-65535 (OPC UA, optional).

Selecting the Correct PC Station Interface: CP 1612 vs IE General

Inside the TIA project, the PC station must contain one network adapter object that matches the physical hardware:

If your laptop does not have a Siemens CP 1612/1623 installed (laptops almost never do), drop the CP 1612 from the PC station entirely and insert IE General. Continuing to declare a CP 1612 that is not installed produces the online error: "The interface is not accessible" or "No PROFINET option in PG/PC interface."

Step-by-Step: Replace CP 1612 with IE General

1. In the TIA project tree, open Devices & Networks.
2. Click the PC station in the network view.
3. In the device view of the PC station, locate the CP 1612 module. Right-click → Delete.
4. In the hardware catalog, navigate to PC Systems > Communication modules > PROFINET/Ethernet > IE General.
5. Drag IE General onto an empty slot of the PC station. TIA prompts for an IP address; assign an address in the same subnet as the PLC (e.g. PLC = 192.168.0.1 / 255.255.255.0, PC = 192.168.0.10).
6. If the PC station is the WinCC Runtime target, ensure the IE General is not marked as PROFINET IO Controller unless you actually need cyclic I/O — for a pure HMI project leave it as a normal Ethernet endpoint.

PG/PC Interface Assignment in Windows

The Windows Set PG/PC Interface dialog (also called the PG/PC Interface applet) is independent of the TIA project's PC station. TIA Portal reads the access point S7ONLINE at runtime to determine which physical NIC is used for online access.

1. Open Start > Control Panel > Set PG/PC Interface. (If the Control Panel is in category view, switch to small icons.)
2. In the Access Point dropdown, select S7ONLINE.
3. In the Interface Parameter Assignment Used list, pick the physical NIC connected to the PLC. For an on-board Realtek NIC, choose Realtek PCIe GBE Family Controller.TCPIP.1. For a CP 1612, choose CP 1612.PROFIBUS.1 or the corresponding PROFINET variant.
4. Click OK. Windows may warn that this changes the access point; confirm.

Verifying Layer-3 Connectivity

Before debugging TIA, prove that IP packets can actually round-trip. Open a Windows command prompt on the engineering PC and run:

ping 192.168.0.1
ping -l 1500 -f 192.168.0.1   :: MTU test, do not fragment
arp -a                          :: confirm MAC learned

If ping fails:

• Confirm the PC's IP address is in the same subnet (no router required for point-to-point).
• Disable Windows Firewall temporarily for testing, or create an inbound rule for ports 102 and 34962-34964.
• Verify the link LEDs on both the PLC port and the PC NIC. A dark PLC port usually indicates a duplicate IP or a port that was administratively disabled.
• Check the PLC's PROFINET device name and IP in Online & Diagnostics > Ethernet address after a successful online connection via a different path (MPI/PROFIBUS adapter, secondary NIC).

Project-Side HMI Connection Configuration

Even with the right physical NIC, WinCC Runtime will refuse to start if the HMI connection in the TIA project does not match the runtime deployment. Inside Devices & Networks:

1. Select the WinCC RT application (HMI_RT_1) in the PC station.
2. Open the Connections editor (the connection tab in the Inspector window of the HMI device).
3. Click Add new connection. Confirm the partner is the S7 PLC and the interface is the IE General of the PC station.
4. Set the connection's S7 address: station number = the PLC's PROFINET device name or its IP, rack/slot = 0/1 for an S7-1500 or 0/2 for an S7-1200.
5. Compile the HMI and check the generated Connections.log for warnings.

For the engineering session itself (download to the PLC), TIA uses the Online > Accessible Nodes menu. The PLC should appear under the NIC selected for the S7ONLINE access point. If the PLC does not appear:

• Use the TIA Online > Online & Diagnostics > Ethernet node search (broadcast) to discover stations.
• Assign a temporary IP via PLC > Ethernet address > Assign IP address when the PLC is in STOP and the MAC matches.

WinCC Runtime: "Failed to Establish a Connection" Diagnostics

This is the specific error observed in the field. It indicates that the WinCC Runtime service could not complete the S7 handshake to the partner configured in the project. The most frequent root causes, ranked by prevalence:

Single-Laptop Engineering and Runtime

It is fully supported to run TIA Portal, WinCC Runtime, and the engineering online access on the same laptop. The constraint is the Windows network stack: only one S7ONLINE access point can be active, and that one access point determines the NIC for both engineering and HMI traffic.

1. Confirm the laptop has exactly one physical Ethernet NIC connected to the PLC (USB-to-Ethernet adapters count as additional adapters and may be selected by accident).
2. Set S7ONLINE to that NIC.
3. Build the PC station with one IE General bound to the same NIC.
4. Start WinCC Runtime. The status indicator in the HMI control panel should read Runtime: Started and the channel diagnostics should show a green S7 connection.

If WinCC Runtime is deployed on a second PC, repeat the PG/PC setup on that PC and ensure the HMI connection in the project is compiled/downloaded to that PC's RT file path. The engineering PC only needs to push the project; it does not need an HMI connection for the second PC's runtime.

Verification Checklist

Network Configuration Rules (TIA V20)

Per the official TIA Portal V20 Industrial Ethernet configuration documentation:

• Ethernet interfaces of SIMATIC devices ship with a default IP. Always change the default to a planned address before commissioning.
• PROFINET device names must be unique on the network and lower-case (S7-1200/1500 requirement).
• The PC station's IE General and the PLC's PROFINET interface must be on the same IP subnet unless a router is in path.
• Do not mix IE General and CP 1612/1623 in the same PROFINET IO system on a single PC station without explicit SIMATIC NET configuration.

For deeper commissioning workflows, Siemens SITrain offers the PROFINET with Industrial Ethernet in TIA Portal (IK-PNCOM) course, covering parameterization, commissioning, and PROFINET-specific diagnostics.

Integration with Third-Party PROFINET Devices

When the PC station needs to act as a PROFINET IO controller talking to a third-party slave (e.g. a Delta RMC motion controller, an I/O block, a drive), the slave's GSD file must be installed first:

1. Save the manufacturer's GSDML-V*.xml file to disk.
2. In TIA Portal, Options > Manage General Station Description Files (GSD), browse to the file, install.
3. Restart TIA Portal.
4. The device appears in the hardware catalog under the appropriate PROFINET IO > category. Drag it into the PROFINET IO system, assign the PC station as IO controller, configure slot mapping.

Refer to Using Siemens S7 PLCs via PROFINET (Delta Motion RMCtools help) for a worked example with a motion controller as a PROFINET device.

Troubleshooting Matrix

FAQ