Activating WinCC OS on an Engineering Station Without Dedicated OS Servers - Resolving Disconnected Named Connections

When activating WinCC OS Runtime directly on an Engineering Station (ES) connected to a real S7-400H CPU while the dedicated redundant OS Servers are unavailable, the communication channel shows 'Disconnected' because PCS 7 'Named Connections' rely on Station Configuration Editor mappings and NetPro associations tied specifically to the OS Server's PC Station name and network card MAC/IP. To establish active communication on the ES, use one of two engineering workarounds: either run 'Start OS Simulation' from SIMATIC Manager (which maps the connection through the ES PG/PC interface), or open WinCC Tag Management on the ES, locate the S7 Protocol Suite, and temporarily configure an 'Industrial Ethernet' (ISO/TCP-IP) connection pointing directly to the S7-400 CPU's IP address and slot.

Architectural Mechanics of PCS 7 Named Connections vs Raw S7 Channels

In SIMATIC PCS 7, communication between OS runtime servers and AS controllers (S7-400 / S7-410) utilizes S7 Named Connections. Unlike classic PLC architectures where SCADA software communicates using direct IP addresses and rack/slot coordinates, Named Connections are symbolically managed and configured in NetPro:

NetPro Connection Routing: NetPro assigns symbolic connection names (e.g., OS_SRV1#AS01#CPU1) that bundle CP card endpoints, ISO-on-TCP addresses, and redundant subnets.
Station Configuration Editor: On the physical PC station, the Station Configuration Editor holds virtual application slots matching the NetPro station configuration (e.g., Slot 1: WinCC Application, Slot 2: CP 1623 / IE General).
High-Availability Support: For redundant S7-400H controllers, Named Connections provide automatic 4-way path failover across redundant Industrial Ethernet switches without losing dynamic tag values.

Root Cause: Station Configuration and Identity Mismatches on the ES

During project commissioning or staged factory testing, a common scenario occurs: the physical S7-400H controller and the Engineering Station (ES) are present, but the physical OS Server rack-mount machines are delayed or located off-site. The engineer attempts to open the OS Server project in WinCC Explorer directly on the ES and activate Runtime.

The result is a 'Disconnected' status across all tags:

Station Name Mismatch: The OS Server project expects to execute on a computer whose Windows computer name matches the PC Station name configured in SIMATIC Manager (e.g., OS_SRV1). The ES has its own computer name (e.g., ES_ENG01).
Station Configurator Registry: The local Station Configuration Editor on the ES does not contain the virtual components or connection tables compiled for OS_SRV1.
Physical MAC/IP Mismatch: The Named Connection database in NetPro was compiled using the MAC and IP addresses of the OS Server's network adapters, not the network card of the ES.

Method 1: Utilizing 'Start OS Simulation' from SIMATIC Manager

The officially supported Siemens method for testing an OS project on an Engineering Station is OS Simulation:

In SIMATIC Manager Component View, right-click the OS project icon and select Start OS Simulation.
When initiated via OS Simulation, the engineering environment temporarily redirects the WinCC communication drivers through the ES station's Set PG/PC Interface setting (e.g., PC internal.local.1 or the ES physical network adapter).
For this to succeed, a valid connection between the ES PC Station and the AS must be configured in NetPro, or the connection name in the OS must match an active path compiled for the ES.

Method 2: Temporary Industrial Ethernet Connection in WinCC Tag Management

When NetPro cannot be downloaded or recompiled on the ES, engineers frequently use a rapid commissioning workaround directly in WinCC:

Open the OS project in WinCC Explorer on the ES.
Open Tag Management.
Under SIMATIC S7 Protocol Suite, locate Industrial Ethernet (or TCP/IP).
Create a new connection named AS_Direct.
In Connection Properties, enter the physical IP address (or MAC address) of the S7-400 CPU or CP 443-1, and specify Rack 0, Slot 3 (or Slot 4).
Re-link the process tags or copy tags from the Named Connection group into the Industrial Ethernet group.

Caution: This is purely a temporary testing mechanism. Performing an 'Entire compile' or 'Changes compile' from SIMATIC Manager will reconcile tags against the Step 7 Named Connection database.

Method 3: Configuring the ES as a Temporary OS Single Station in NetPro

For a permanent and robust test setup without re-wiring WinCC tags:

In SIMATIC Manager, insert a new SIMATIC PC Station representing the ES (e.g., named ES_STATION).
Add a WinCC Application and an IE General card matching the exact Windows computer name and physical NIC of the ES.
In NetPro, configure an S7 Named Connection between ES_STATION and the S7-400H CPU.
In the Station Configuration Editor on the ES, import the Station Configuration (XDB file) or configure the slots to match NetPro.
Compile the OS targeting this ES station. WinCC can now activate natively in Runtime with fully functional, redundant Named Connections.

Comparative Solution Matrix: Operating WinCC OS Directly on the ES

The following table evaluates the three methods for running WinCC OS Runtime on an Engineering Station:

MethodEngineering EffortAS-OS Compile Resilient?Redundancy (H-Connection) Supported?Suitable for Formal Testing?1. Start OS SimulationMinimal (Right-click action)Yes (Native PCS 7 Feature)Yes (If ES configured in NetPro)Ideal for Quick Logic/Graphic Tests2. Manual Industrial EthernetLow (Tag Management edit)No (Overwritten on OS Compile)No (Single IP Connection Only)Commissioning Diagnostics Only3. Configure ES PC Station in NetProModerate (NetPro download)Yes (Fully Managed by PCS 7)Yes (Full Fault-Tolerant Named Connection)Recommended for FAT / Staged Testing

Step-by-Step Procedure to Establish Live Communication from ES to AS

Follow this step-by-step workflow to establish live communication from an ES to an S7-400H without dedicated servers:

Verify Physical Connectivity and IP Configuration:
- Ping the CP 443-1 or CPU Ethernet port from the ES command prompt.
- Ensure the ES network adapter is on the same subnet as the Plant Bus (e.g., 192.168.1.xxx).
Check PG/PC Interface on ES:
- Open Set PG/PC Interface in Windows Control Panel.
- Verify that the Access Point of the Application (S7ONLINE) is set to your active network card (e.g., TCP/IP(Auto) -> Intel... or ISO Ind. Ethernet).
Configure Temporary Industrial Ethernet Connection (Rapid Method):
- In WinCC Explorer, open Tag Management.
- Expand SIMATIC S7 Protocol Suite.
- Right-click Industrial Ethernet -> New Connection... (name it AS_Online).
- In Connection Parameters, enter the AS Ethernet IP/MAC, Rack 0, Slot 3.
- In the system parameters of the driver, set the Logical Device Name to match your active PG/PC network interface.
Reassign Tags or Test Connection:
- Move or map test tags to AS_Online.
- Activate WinCC Runtime.
- Open Channel Diagnosis (WinCCChannelDiagnosis.exe) from the Start menu.
- Confirm that the Industrial Ethernet channel displays a green checkmark (Ready / Connected).

Verification

Verify live communication through the following validation checks:

Open WinCC Runtime on the ES station.
Launch WinCC Channel Diagnosis from the Windows taskbar or Start menu.
In the Channel Diagnosis window, expand the active communication channel.
Verify that the connection state displays 'Connected' with a green checkmark, and the error count remains 0.
Open a process screen displaying live analog values. Confirm that values update dynamically without yellow quality exclamation marks.
Toggle a digital input in S7-PLCSIM or on the physical controller and confirm that the block icon state changes immediately in WinCC Runtime.

Limitations and Operational Precautions

OS Compile Reversion: If you configured a temporary Industrial Ethernet connection in Tag Management, running 'Compile OS' from SIMATIC Manager will re-assert Named Connection parameters. Do not compile the OS while using the temporary connection workaround.
Redundant S7-400H Switching: Standard Industrial Ethernet driver connections in WinCC do not support fault-tolerant switching between Master and Standby CPUs in an S7-400H system. If Master CPU transitions occur, communication will freeze until manually repointed.
License Enforcement: Running WinCC Runtime on an ES consumes an OS Runtime license. Ensure appropriate RC (Runtime/Configuration) floating licenses exist in Automation License Manager on the ES.

Engineer FAQ

Why can't I just rename my ES to match the OS Server's computer name?

Renaming the ES Windows computer name can cause severe licensing, SQL Server, and SIMATIC directory corruption if PCS 7 was installed under the original name. Siemens strongly advises against renaming an active Engineering Station.

What is the difference between OS Simulation and WinCC Runtime activation?

Activating Runtime directly runs WinCC as a standalone workstation using local Station Configurator tables. OS Simulation runs WinCC inside an emulation wrapper that redirects Named Connections through the ES engineering access points.

Can I download from CFC while WinCC Runtime is active on the ES?

Yes. You can perform CFC Changes Download while WinCC OS Runtime is active. However, you should avoid performing an OS compile until Runtime is deactivated.

Why does Channel Diagnosis show error 0x4104?

Error 0x4104 in WinCC Channel Diagnosis indicates that the specified connection partner (IP address, MAC, or Rack/Slot) did not respond or the network interface is unassigned. Check network cables, IP subnets, and CPU rack/slot numbers.

Can I test redundant servers on a single ES station?

No. A single computer cannot run two independent WinCC Server runtime engines simultaneously. To test redundancy, you must use virtual machines (e.g., VMware Workstation) hosting distinct OS Server instances.