Resolving S7-300 to WinCC RT Professional Communication Failures

Problem Summary

An S7-314 CPU (SIMATIC S7-300 family) is connected over Industrial Ethernet to a PC station running WinCC Runtime Professional. The TIA Portal V17 project downloads to the CPU successfully, and online monitoring of inputs and outputs functions correctly through the engineering software. However, the HMI runtime on the PC cannot establish an S7 connection to the CPU. The runtime stays in a "Connecting" state, the WinCC tag simulator shows no value updates, and no tag transitions to the "connected" quality code.

This failure mode is most often caused by one of three configuration gaps: (1) the wrong runtime flavor installed on the PC (for example, only the WinCC Tag Simulator / "RT Pro" rather than a full WinCC Runtime), (2) the SIMATIC NET PC software stack missing from the runtime PC, or (3) the S7ONLINE access point on the runtime PC bound to the wrong network adapter. The remainder of this reference covers the diagnostic path, the mandatory software components, and the configuration sequence required to bring the S7-300 ↔ WinCC RT Professional link online.

S7-314 Hardware Reference

The S7-314 is part of the SIMATIC S7-300 family. The IP configuration referenced in the source (CPU 192.168.80.10, PC 192.168.80.15) is valid; both addresses are usable hosts in the 192.168.80.0/24 subnet with the default mask 255.255.255.0. The first decision point is whether the CPU variant itself has a PROFINET interface.

PROFINET connectivity is only available on the -6EH04 variant (CPU 314C-2 PN/DP). For all other S7-314 CPUs, Ethernet communication to WinCC requires a CP 343-1 communications processor (for example 6GK7343-1EX30-0XE0 with firmware V3.0 or later, or 6GK7343-1CX10-0XE0 for older builds) installed in the S7-300 rack, or a third-party gateway that proxies S7 communication to the WinCC runtime.

WinCC Runtime Variants and Software Requirements

Siemens offers three runtime products commonly confused with one another when commissioning HMI applications on a PC station. The original failure described in the source was caused by installing "RT Pro" (the WinCC Tag Simulator shipped with the engineering license) rather than a real runtime that can talk to a live PLC.

For WinCC Runtime Professional, the installation media is "SIMATIC WinCC Professional V17" (DVD bundle or download via the Siemens Online Software Delivery portal). This package includes SIMATIC NET with the S7-DO protocol driver used for S7-300/400/1500 communication. Without installing SIMATIC NET, the WinCC channel "SIMATIC S7-300/400 Channel" will not bind to a TCP socket and connection status remains "Disconnected".

WinCC Runtime Advanced uses its own internal S7 stack and does not require SIMATIC NET, but it does not support all PC-based SCADA features (multi-client, redundancy, archive server) that WinCC Runtime Professional provides. Always match the runtime product to the licensing scope and the project requirements before assuming the install is complete.

Root Cause Matrix

Diagnostic Flowchart

Prerequisites

Before reconfiguring the link between an S7-300 CPU and a WinCC Runtime Professional PC station, verify the following items are present and at matching version levels:

• TIA Portal V17 (or matching V17 Update x) installed on the engineering station. Apply the latest TIA Portal V17 Update (commonly V17 Update 4 or later at the time of writing) before commissioning.
• WinCC Professional V17 engineering license (for example 6AV2101-0AA07-0AA5 or higher).
• WinCC Runtime Professional V17 license (6AV2105-1xx07-xxxx, tag-count dependent) installed on the target PC.
• SIMATIC NET V17 (PC software) installed on the target PC. This is the most commonly missed dependency and is shipped together with the WinCC Professional V17 media.
• S7-300 CPU with PROFINET interface (CPU 314C-2 PN/DP 6ES7314-6EH04-0AB0, or any 315-2 PN/DP / 317-2 PN/DP / 319-3 PN/DP), or CP 343-1 (6GK7343-1EX30-0XE0, firmware V3.0+) for non-PN CPUs.
• Ethernet cabling between PLC port and PC Ethernet adapter, both on the same subnet (in this case 192.168.80.0/24).
• Administrator privileges on the PC to install/remove software and configure S7ONLINE access points.

Procedure: Assigning the PG/PC Interface in TIA Portal V17

The PG/PC interface controls which network adapter TIA Portal (and, indirectly, the WinCC runtime started under the same access point) uses for S7 routing. Misalignment between the PG/PC interface and the physical Ethernet port breaks both programming and runtime communication.

1. Open TIA Portal V17 on the engineering station.
2. Select Options → Set PG/PC Interface.
3. In the access point dropdown, select S7ONLINE.
4. In the interface parameterization list, expand the TCP/IP entry that corresponds to the physical Ethernet port connected to the S7-300.
5. Confirm that the chosen adapter matches the OS-level network adapter name (for example "Intel(R) Ethernet Connection I219-LM" or "Realtek PCIe GbE Family Controller"). Avoid selecting virtual adapters, Hyper-V virtual switches, VPN tunnels, or disabled adapters.
6. Click OK to apply. Restart TIA Portal so the change takes effect.

Procedure: Configuring the HMI Connection in TIA Portal V17

The HMI connection in the Devices & Networks editor is the bridge between the WinCC Runtime Professional PC station and the S7-300 CPU. Misconfigured endpoints or missing connections are a leading cause of runtime disconnection. The configuration steps below follow the Siemens reference Communication connections to PC stations (S7-300, S7-400, S7-1500).

1. In the TIA Portal project tree, expand Devices & Networks.
2. Open the Devices and Networks editor (network view).
3. Drag the WinCC PC station (or add it via Add new device → SIMATIC PC → WinCC Runtime Professional) into the network view.
4. Select the S7-300 CPU (or CP 343-1 if used).
5. Click the Connections button in the editor toolbar, then drag a connection line from the PC station's "HMI" interface to the S7-300's PROFINET interface.
6. In the Connection properties dialog, verify the following:

7. Compile the PC station (Right-click → Compile → All (rebuild)) and download to the PC runtime.
8. Restart the WinCC Runtime after download.

Verify the connection was correctly routed. According to the Siemens documentation, an existing S7 connection is routed by the CPU assignment of the interface of the CPU. An invalid routed S7 connection is displayed only when the endpoints of the connection are checked. If the connection appears invalid, right-click the connection and select Check connection to see the routing status.

Procedure: Installing SIMATIC NET for WinCC Runtime Professional

SIMATIC NET installs the S7-DO protocol driver, the OPC server (if licensed), and the S7ONLINE access point binding required by WinCC Runtime Professional. Without it, the runtime cannot open a TCP socket to the S7-300 CPU.

1. Insert the SIMATIC WinCC Professional V17 installation DVD or mount the ISO image (for example SIMATIC_WinCC_Professional_V17.iso).
2. Run Setup.exe as administrator.
3. Select Install → SIMATIC WinCC Professional V17.
4. On the component selection screen, ensure the following are checked:

• WinCC Runtime Professional V17
• SIMATIC NET V17 (S7-300/400/1500 Communication)
• SIMATIC NET OPC Server (optional, required only for third-party OPC clients)

5. Accept the license agreement and complete the installation.
6. Restart the PC to register the SIMATIC NET services and channel DLLs.
7. Verify: Open Start → SIMATIC → Communication Settings and confirm that the access point S7ONLINE is bound to TCP/IP → your network adapter.
8. Verify the channel DLL is loaded: in Windows Explorer, navigate to C:\Program Files\Siemens\Automation\SIMATIC_NET\bin and confirm S7CHN.DLL (or S7ONLINE.DLL) is present.

Procedure: Validating IP Addresses and Subnet Configuration

Both the CPU/CP and the PC must be on the same IP subnet and the same broadcast domain (no router hops). Subnet mismatch is a classic reason why TIA Portal works (because the routing stack handles it) while the WinCC Runtime fails.

1. On the PC, open cmd as administrator and run:

ipconfig /all
ping 192.168.80.10
arp -a

2. On the S7-300 (via TIA Portal online or the CPU's integrated display if available), verify the following parameters:

3. If the ping fails, perform the following checks:

• Inspect the Ethernet cable and switch port LED status (link LED green = physical link up).
• Disable Windows Firewall temporarily for testing: netsh advfirewall set allprofiles state off.
• Verify no IP conflict by inspecting the ARP table for duplicate MAC addresses.
• Try a direct crossover or patch cable between the CPU/CP and the PC to rule out switch issues.
• Check that VLAN tagging is not applied to the port (S7-300 PN does not support tagged frames by default).

Procedure: Configuring the PC Station Access Point Outside TIA Portal

The runtime PC station must have S7ONLINE bound to the correct adapter. This is independent of TIA Portal's PG/PC interface and is the most frequently missed configuration step on the runtime machine.

1. On the runtime PC, open Start → Control Panel → Set PG/PC Interface (also accessible via SIMATIC → Communication Settings → Set PG/PC Interface).
2. Set the access point S7ONLINE to TCP/IP → <your Ethernet adapter>.
3. Click Diagnostics to confirm the binding reads "OK".
4. Open SIMATIC → Communication Settings → Access Points and confirm the following access points are assigned:

5. Restart the WinCC Runtime service: from an elevated command prompt run net stop "CCAgent" then net start "CCAgent", or reboot the PC to load all services.

Communication Diagnostics Tools

WinCC Channel Diagnostics

1. In TIA Portal, expand the PC station → WinCC Runtime → Connections.
2. Open the connection to the S7-300 and confirm the channel is assigned to SIMATIC S7-300/400 Channel (for S7-300/400 CPUs) or SIMATIC S7-1200, S7-1500 Channel (for S7-1500).
3. Right-click the connection → Channel diagnostics to view the live state.

Runtime Logger

1. On the runtime PC, navigate to C:\ProgramData\Siemens\CoRtHmiRtm\Logs.
2. Open WinCC_RT_LogFile.log and search for entries containing S7, channel, or the connection name.

Common entries and their interpretations:

SIMATIC NET Diagnostics

1. Open SIMATIC NET → Commissioning → Diagnostics.
2. Verify the S7-DO protocol is installed and the S7 connection resource exists.
3. Use S7 Connection Test to send a single S7 read to the CPU and verify a response.

Tag Configuration for S7-300 Variables

After the S7 connection is online, tag mapping must match the actual CPU memory layout. For an S7-314, the relevant memory areas are:

Verify that the tag address actually exists in the CPU memory. The S7-314 has a process image of 128 bytes input and 128 bytes output by default. Analog values in the process image are accessed as 16-bit words (e.g., PIW 304 for the first analog input on a typical SM 334 module) and must be scaled in the WinCC tag using a linear scaling function block if engineering units are required.

Verification Procedure

After applying the configuration fixes, run the following verification sequence to confirm the runtime is fully online:

1. Start the WinCC Runtime on the PC.
2. Open the runtime project and confirm the "Project activated" indicator is green.
3. Verify the connection status field shows "Connected" (typically in the bottom-right corner of the runtime window, or via a system diagnostic screen configured in the project).
4. Toggle a digital input on the S7-300 and verify the corresponding tag in the runtime updates within the configured update cycle (default 1 s, configurable from 100 ms to 5 s).
5. Force an output from the runtime (if operator privilege permits) and verify the digital output module LED changes state.
6. Open the WinCC Channel Diagnostics on the runtime PC and confirm ConnectionState = OK for the S7 connection.
7. Inspect the S7 connection statistics: WinCC → Tools → Channel Diagnostics → Connection → Statistics to verify request and response counters are incrementing.

Common Error Codes and Recovery Actions

Switching from "RT Pro" to a Working Runtime

The original failure described in the source arose from installing "RT Pro" (the WinCC tag simulator, which simulates values internally) rather than a real runtime. The two practical fixes are:

1. Switch to WinCC Runtime Advanced if the panel runtime is sufficient for the application scope. WinCC RT Advanced communicates with S7-300/400/1500 over PROFINET without requiring SIMATIC NET. License order number: 6AV2104-0xx07-xxxx (RT Advanced V17).
2. Install WinCC Runtime Professional + SIMATIC NET if multi-tag SCADA functionality, server/client distribution, redundancy, or long-term archiving is required. License order number: 6AV2105-1xx07-xxxx (RT Professional V17, tag-count dependent).

After switching the runtime flavor, recompile the PC station in TIA Portal (right-click the PC station → Compile → All) and re-download. The HMI tags and screens remain unchanged; only the target runtime device selection is updated in the project tree. Re-verify the connection by following the Verification Procedure above.

Best Practices

• Reserve a fixed IP block for HMI/PLC networks (for example 192.168.80.0/24) and document the address plan.
• Keep TIA Portal, WinCC, and SIMATIC NET versions in sync. Cross-version stacks (for example TIA V17 with SIMATIC NET V16) are unsupported and produce intermittent faults.
• Disable Windows Firewall on the runtime PC, or add explicit inbound rules for ports 102 (ISO-on-TCP / S7), 5000 (WinCC RT), and 1025-1100 (SIMATIC NET internal).
• Avoid MC/IT antivirus real-time scanning on C:\Program Files\Siemens; it delays the S7 channel DLL load and can block communication packets.
• Use a dedicated industrial Ethernet switch (managed, e.g., SCALANCE XB005 / XC206) when more than two nodes connect to the S7-300 PN interface.
• Document the PG/PC interface assignment in the project documentation so commissioning teams do not switch it during maintenance.
• On the S7-314, limit HMI connections to no more than 2 simultaneous S7 connections to leave resources for programming and other engineering tools.

FAQ