Configuring S7-1500 PROFINET HMI Connection to a WinCC Professional PC Station
This guide walks through commissioning an HMI connection between a SIMATIC S7-1500 controller (typically with an external CP IE interface module) and a WinCC Professional Runtime PC station over PROFINET in TIA Portal. It also documents the two recurring field faults — the "Wrong partner" diagnostic in the HMI connection editor and the flashing red ERROR / SF LED on the CPU — and explains how the topology view interacts (or interferes) with the logical S7 connection.
1. Required Hardware and Software
| Component | Catalog / Order Number | Notes |
|---|---|---|
| S7-1500 CPU (e.g., 1515-2 PN) | 6ES7515-2AM02-0AB0 | PROFINET interfaces X1 / X2 |
| S7-1500 CPU 1516-3 PN/DP | 6ES7516-3AN02-0AB0 | 3-port PN/DP variant |
| CP 1543-1 (PROFINET / Industrial Ethernet) | 6GK7543-1AX00-0XE0 | External IE module with security functions |
| CP 1545-1 | 6GK7545-1AX00-0XE0 | Higher performance variant |
| SCALANCE XC/XB/XR switch | 6GK5xxx-x series | Optional, recommended for ring topology |
| WinCC Professional V17/V18/V19/V20 | 6AV2xxx-1xxxxx | Must match TIA Portal major version |
| WinCC RT Professional (PC station) | 6AV2xxx-1xx00-xAA0 | Runtime license per tag count |
TIA Portal, the WinCC Professional option, and the CP IE HSP (Hardware Support Package) must all be installed before the CP can be inserted into the device configuration. Install matching versions of TIA Portal and WinCC Professional — mixing V18 TIA Portal with V17 WinCC Runtime is not supported.
2. Network Architecture
Two valid topologies exist:
- Direct connection (recommended for engineering): Engineering PC ↔ CPU PN port ↔ CP 1543-1 ↔ WinCC RT PC. PROFINET and HMI traffic share one subnet.
- Separated subnets: The CP IE connects to a dedicated PN/IE_1 subnet that is physically isolated from the field-level PROFINET used by distributed I/O. The CPU's PROFINET interface handles the field network, the CP IE handles the HMI/IT network.
For the separated subnet case (the most common in customer projects), the IP scheme below is a working baseline:
| Device | Interface | IP Address | Subnet Mask | Router |
|---|---|---|---|---|
| Engineering PC | Ethernet | 192.168.0.10 | 255.255.255.0 | — |
| S7-1500 CPU 1515-2 PN | X1 (PN/IE_1) | 192.168.0.1 | 255.255.255.0 | — |
| CP 1543-1 | X1 (PN/IE_1) | 192.168.0.2 | 255.255.255.0 | — |
| WinCC RT Professional PC | Ethernet | 192.168.0.20 | 255.255.255.0 | — |
All devices must share the subnet PN/IE_1 as it is declared in the project. PROFINET device names must be unique across the subnet; the WinCC PC station uses its own name (default PCStation.x) and the CPU uses a separate name (default plc1.x).
3. Device Configuration in TIA Portal
- Open the TIA Portal project and add the S7-1500 CPU to the project. Use Add new device > SIMATIC S7-1500 > CPU and select the exact order number and firmware version. The firmware version of the inserted CPU must match the physical hardware; mismatched firmware is the most common reason for a flashing SF LED after a download.
- From the hardware catalog, expand Communication modules > CP 1543-1 and drag the module into a free slot of the S7-1500 rack. Confirm the firmware version.
- Add the PC station: Add new device > PC systems > SIMATIC PC Station. Insert a WinCC Professional RT application from the catalog into slot 1 of the PC station. Insert an IE General (CP IE) into a free PCI/PCIe slot of the PC station so it can be connected to the PROFINET subnet.
- Open the Devices & Networks editor. The Network view shows the CPU, CP 1543-1, and PC station.
3.1 Connect the CP IE of the PC Station to PN/IE_1
In the network view, select the IE General (CP IE) module on the PC station and look at Properties > Ethernet addresses. In the Interface connected with dropdown, choose PN/IE_1. Assign the WinCC RT PC IP (192.168.0.20) and the matching subnet mask. TIA Portal will create a logical network that the CP 1543-1 and the CPU can also be assigned to.
For the CPU, the X1 (or X2) PROFINET interface must also be assigned to PN/IE_1. Likewise the CP 1543-1 X1 interface. Three devices, one logical subnet, all reachable.
4. Creating the HMI Connection
With the network in place:
- In Devices & Networks, click the Connections button in the toolbar at the top. The editor mode switches from network view to the connection editor.
- In the dropdown on the left of the connections editor toolbar, choose HMI connection.
- The left pane lists the HMI-capable endpoints in the project. Locate WinCC RT Professional under the PC station.
- Drag a connection from WinCC RT Professional onto the S7-1500 CPU. The endpoint is the CPU's PROFINET interface — not the CP 1543-1.
TIA Portal now creates a named HMI connection. The connection name and parameters can be reviewed in the connection table. By default the access point is S7ONLINE and the connection uses the S7 protocol over TCP/IP (ISO-on-TCP, port 102).
4.1 Connection Parameters
| Parameter | PC Station / WinCC RT | S7-1500 CPU |
|---|---|---|
| Partner IP | 192.168.0.20 (WinCC RT) | 192.168.0.1 (CPU) |
| Connection type | HMI connection | S7 server |
| Access point | S7ONLINE | — |
| Connection resource (CPU side) | — | Automatically assigned, OP / HMI slot |
| Connection diagnostics | Online > Online & diagnostics > Connection information | Available on CPU web server / TIA diagnostics |
5. WinCC Professional Project Settings
Open the WinCC RT Professional project node and verify:
- Runtime settings > General: The configured computer name matches the Windows hostname of the RT PC. TIA Portal compiles the RT project with this name; mismatched names cause "Cannot find partner" errors at runtime.
- Runtime settings > Services: The WinCC RT process is set to start automatically. The "Autostart" option is recommended for production lines.
- Tag management: Tags pointing to the S7-1500 use the connection name created in step 4. TIA Portal auto-fills the connection name; if the connection is renamed later, tag references break silently.
6. Compile, Download, and Verify
- Right-click the CPU > Compile > Hardware and software (rebuild all). Resolve any compilation errors before continuing — the most common is "Device with order number X cannot be configured because the HSP is not installed."
- Right-click the PC station > Compile > PC station. The compile output generates the PC station configuration file (typically
PCStation.cfg) that the RT loader (WinCC RT) reads at startup. - Download the S7-1500 station first. The CPU's MRES or RUN/STOP switch should be set to STOP if the hardware configuration has changed (e.g., a new CP 1543-1 was added). After a successful download, set the switch back to RUN.
- Download the PC station. Confirm the RT loader reports the new configuration and that the WinCC RT service restarts.
7. Resolving the "Wrong Partner" Error
The "Wrong partner" message is reported by the WinCC Runtime when it attempts to establish the S7 connection and the device on the configured IP does not respond as an S7 server. Common causes and their fixes:
| # | Cause | Diagnostic | Fix |
|---|---|---|---|
| 1 | IP / subnet mismatch between TIA Portal and Windows |
ping from RT PC to CPU and to CP 1543-1 |
Set Windows adapter IPv4 to the same subnet; align TIA Portal with Windows |
| 2 | Topology line drawn instead of network line | Open topology view, inspect edges | Delete the topology edge; use network view only |
| 3 | CPU's PROFINET interface is not enabled for S7 communication | Properties of CPU PROFINET interface > Access to the CPU via S7 routing | Enable "Permit access with PUT/GET" if needed, ensure interface is enabled |
| 4 | Firewall on RT PC blocks port 102 (ISO-on-TCP) | Windows Defender Firewall log | Allow WinCC RT and Port 102 inbound/outbound |
| 5 | Connection partner is the CP 1543-1 instead of the CPU | Connection table partner field | Change partner to the S7-1500 CPU |
| 6 | Wrong PLC hostname / PROFINET name assigned to PC station | Compare TIA Portal name with Set PC/PG interface | Use the same PROFINET device name on the RT PC adapter via "Set PG/PC interface" |
ping 192.168.0.1. A reply proves IP-layer reachability. If ping fails, the HMI connection cannot succeed, regardless of TIA Portal settings.
8. Resolving the Flashing Red CPU LED After Hardware Download
When the CPU shows a steady or flashing red ERROR / SF LED immediately after downloading a hardware configuration that includes a CP IE module, the most frequent root causes are:
- Firmware version mismatch. The CP IE inserted into the device configuration has firmware X, but the physical module has firmware Y. TIA Portal flags this as an "IO device error." Update the catalog entry or update the physical module firmware via the TIA Portal online dialog.
- Missing or incorrect PROFINET device name on the CPU. The CPU's PROFINET interface must have a unique device name (not the default empty name) for IO controllers to address it. Assign the name online using Online & diagnostics > Assign PROFINET device name.
- Duplicate IP address on the subnet. Two devices share the IP entered in TIA Portal. The CPU's SF LED combined with a BF on the PROFINET port indicates this. Use Wireshark or the ARP table of a managed switch to find the duplicate.
- CP 1543-1 security / firewall settings. The CP IE supports an internal stateful firewall. If "Security > Firewall" is enabled and the WinCC RT PC IP is not in the allowed list, the CP silently drops S7 traffic. Disable the firewall during commissioning and re-enable with a clean rule set afterwards.
The CPU's diagnostic buffer (Online & diagnostics > Diagnostics buffer) provides the exact error code and timestamp. Common diagnostic buffer entries for PROFINET issues are:
-
IO device failure (channel / station)— physical disconnect or duplicate IP. -
PROFINET IO: Device name assignment error— name on the device does not match the configured name. -
Security event: Communication blocked by firewall— CP IE firewall drop. -
Connection resource exhausted— too many HMI / S7 connections opened.
9. Secure Communication Considerations (TIA Portal V17 and Later)
From TIA Portal V17 onward, secure S7 communication can be configured for S7-1500 controllers. The basics are documented in the official Siemens TIA Portal help under Useful information on Secure Communication.
For a WinCC RT connection, the typical secure setup is:
- The S7-1500 CPU has a security user with appropriate rights (HMI access).
- The HMI connection in TIA Portal is created with Connection type = HMI connection, secure.
- The PC station's local security certificate is imported into the CPU's certificate manager under Devices & networks > CPU > Security > Certificate manager.
- The WinCC RT PC trusts the CPU's certificate (the runtime loads it automatically from the project).
10. Topology View vs. Network View — Field Practice
The confusion between the network view and the topology view is the single most repeated mistake when commissioning S7-1500 with WinCC PC stations. Rules of thumb:
- Network view = logical assignment of devices to subnets (PN/IE_1). This is where the HMI connection lives.
- Topology view = physical port-to-port wiring for PROFINET devices, used by PROFINET IO controllers for neighbor detection. It is not required for HMI-only connections.
Procedure to clean up after a topology mistake:
- Switch to Topology view.
- Identify any line drawn between the S7-1500 CPU and the PC station. The PC station's IE General will show as a "PROFINET endpoint" but the WinCC RT application is not an IO device.
- Right-click the line and choose Delete. Save and recompile the project.
- Re-download both the CPU and the PC station configuration.
11. Verification Checklist
| Check | Command / Location | Expected Result |
|---|---|---|
| Physical link | CPU PROFINET port LED | Green steady (link up, no activity) or flashing (traffic) |
| IP-layer reachability |
ping 192.168.0.1 from RT PC |
Reply < 1 ms |
| CPU PROFINET name assigned | Online & diagnostics > PROFINET device name | Name matches project configuration |
| HMI connection status in TIA Portal | Connections editor, right-click > Go online | All HMI connections green / established |
| CPU diagnostic buffer | Online & diagnostics > Diagnostic buffer | No "IO device failure" or "connection aborted" entries |
| WinCC RT connection diagnostics | WinCC RT Explorer > Connections | Connection shows "OK" / green check |
| Tag test | WinCC RT — connect a tag to an internal CPU tag and force it | Tag value updates in the HMI |
12. Troubleshooting Matrix
| Symptom | Likely Root Cause | First Action |
|---|---|---|
| WinCC RT: "Wrong partner" | Connection endpoint wrong, or IP mismatch, or topology line | Verify endpoint = CPU, verify IP, delete topology edge |
| CPU: red ERROR LED steady | Firmware mismatch, missing PROFINET name, duplicate IP | Diagnostic buffer > firmware update or rename device |
| CPU: red ERROR LED flashing | PROFINET IO device fault on at least one IO device | Online & diagnostics > Distributed IO > identify offending device |
| CPU BF LED on PROFINET port | No link, wrong cable, port disabled | Check cable, port LED, switch configuration |
| CP 1543-1: SF LED + WinCC RT no connection | Firewall or ACL on CP IE blocking port 102 | Temporarily disable CP IE firewall |
| WinCC RT: TLS / certificate error | Secure comm enabled but certs not exchanged | Import / export certificates per TIA Portal secure comm help |
| Connection drops intermittently | Watchdog timeouts, broadcast storm, switch port flap | Check switch port statistics, enable port fast / disable storm control |
13. Frequently Asked Questions
Why does my WinCC PC station show "Wrong partner" even though ping to the CPU succeeds?
The IP layer is reachable but the S7 endpoint is misconfigured. In the Connections editor verify that the HMI connection's partner is the S7-1500 CPU (not the CP 1543-1 or the PC station itself). Also delete any topology-view line between the CPU and PC station — topology relationships override logical S7 connections.
Should the CP 1543-1 be used as the partner for the HMI connection?
No. The WinCC RT HMI connection should terminate on the S7-1500 CPU's PROFINET interface (X1 or X2). The CP 1543-1 is for IT / cybersecurity segmentation; it can route the S7 traffic but it should not be the connection endpoint in TIA Portal.
Which TIA Portal versions support S7-1500 to WinCC PC station HMI connections?
TIA Portal V15.1 and later support S7-1500 with WinCC Professional. For secure communication features, TIA Portal V17 or later is required. Match the WinCC Professional version to the TIA Portal version — mixed versions are not supported.
What does the flashing red LED on the CPU mean after downloading the hardware configuration?
The CPU diagnostic buffer will list the exact cause. The most common are: PROFINET device name not assigned, duplicate IP on the subnet, CP 1543-1 firmware mismatch, or a missing IO device. Open Online & diagnostics > Diagnostic buffer for the timestamped error.
Do I need the Topology view for an HMI-only connection?
No. The Topology view is only required for PROFINET IO port-to-port neighbor relationships. For a WinCC RT HMI connection over PROFINET, only the network view (logical subnet PN/IE_1) is needed. Drawing a topology line between the CPU and the PC station is a common cause of "Wrong partner" errors and should be removed.
How do I verify the HMI connection is live without running WinCC?
In TIA Portal, open the Connections editor, right-click the HMI connection and choose Go online. The status column turns green when the S7 connection is established. You can also use the CPU web server (if enabled) under Diagnostics > Connection information.
Is secure communication between S7-1500 and WinCC RT required?
It is optional in TIA Portal V17 and later, but recommended for production networks. Secure communication uses TLS and requires certificates to be exchanged between the CPU and the RT PC. Without certificate exchange, the runtime will fail to establish the connection with a security error rather than a "Wrong partner" error.