Downloading PC Station Configurations from an ES to an OS Single Station in SIMATIC PCS 7

When remote hardware configuration download from an Engineering Station (ES/OS) to an independent OS Single Station fails despite successful ping and remote desktop connectivity, the failure is caused by a Station Configuration Editor (SCE) mismatch, misconfigured SIMATIC Shell adapters, or improper PC Station naming in HW Config. In small architectures with an ES/OS combined station and a separate OS Single Station, the reliable engineering method is to export the station configuration file (.xdb) from HW Config, copy it to the OS Single Station, and import it locally into the Station Configuration Editor. Once the station components and network connections are active online, compile and download the WinCC project directly via SIMATIC Manager.

Executive Summary

Compact and cost-sensitive PCS 7 architectures often deploy an Engineering Station configured as an ES/OS combined station alongside a secondary independent OS Single Station. When commissioning engineers attempt to deploy the hardware and network configuration from NetPro or HW Config to the secondary OS station, the transfer fails with communication errors, despite the fact that Windows ping and Remote Desktop Protocol (RDP) sessions function perfectly over the Terminal Bus. This issue stems from the strict protocol and name-matching requirements of the Siemens Station Configurator runtime environment. This article clarifies the architectural rules for multi-station deployment and details the verified XDB import workflow to establish robust remote engineering.

Architecture and Fundamental Mechanics

Station Configuration Editor Mechanics, XDB Deployment Architecture, and PC Station Identity Rules:

Architecture of the SIMATIC PC Station:
A PCS 7 PC Station is a software virtual rack (slots 1 to 32) managed by the Station Configuration Editor (SCE).
Typical configuration for an OS Single Station:
- Slot 1: WinCC Application (hosts the WinCC runtime engine).
- Slot 2: IE General (or CP 1623, connecting to the Terminal/Plant Bus).
For an online PLC download (PLC > Configure / PLC > Download) from ES to target OS to succeed:
1. The Station Name in HW Config must match the Station Name in the Station Configuration Editor exactly (case-sensitive).
2. The Windows Computer Name must match the Station Name.
3. SIMATIC Shell must be bound to the Terminal Bus on both machines.
Why Remote PC Station Downloads Often Fail in Small Plants:
In small setups, engineers often create an ES/OS combined PC station and clone it, leaving conflicting station names or misaligned slot indices.
Furthermore, Windows security policies or firewalls frequently block S7 communication to the Station Manager service (s7oiehsx.exe), preventing remote slot configuration.
The Verified XDB Offline Configuration Method:
When HW Config is saved and compiled, PCS 7 generates a station database file (<StationName>.xdb) inside the project directory.
Importing this .xdb locally into the target OS Station Configuration Editor bypasses network transfer vulnerabilities, establishing the virtual rack, network cards, and WinCC application slots with 100% fidelity.

Step-by-Step Implementation Procedure

Verify PC Station Structure in SIMATIC Manager:
* In Component View, confirm that the project contains two distinct PC Stations: one for the ES/OS (e.g. ES_STATION) and one for the OS Single Station (e.g. OS_SINGLE01).
* In HW Config for OS_SINGLE01, ensure Slot 1 contains WinCC Application and Slot 2 contains IE General.
* Ensure the PC Station Name in HW Config matches the exact Windows Computer Name of the OS Single Station machine.
Generate the XDB Station Configuration File:
* In HW Config, select menu Options > Customize > Station Configuration Editor.
* Verify the storage location for .xdb files (default is <ProjectFolder>\xdb\).
* Select Station > Save and Compile in HW Config; ensure compilation completes with zero errors.
Transfer and Import XDB on the OS Single Station:
* Copy the generated .xdb file (e.g. OS_SINGLE01.xdb) to a local folder on the OS Single Station.
* On the OS Single Station, right-click the Station Configuration Editor icon in the Windows taskbar tray and select Open.
* Click Import Station; browse to the copied .xdb file and click OK.
* Confirm that the components appear in the virtual rack (WinCC Application in Slot 1, IE General in Slot 2) with status 'Ready'.
Configure SIMATIC Shell Binding on Both Stations:
* Open Windows File Explorer; right-click SIMATIC Shell and select Settings.
* Ensure the network adapter connected to the Terminal Bus is selected.
* Confirm that both ES_STATION and OS_SINGLE01 are visible in the SIMATIC Shell browser.
Compile and Download WinCC Project:
* On the ES, configure the Target OS path under OS Properties (\\OS_SINGLE01\WinCC_Project).
* Compile the OS project in SIMATIC Manager.
* Right-click the OS object, select PLC > Download, and perform an Entire OS download.

Verification

On the OS Single Station, open the Station Configuration Editor; verify that all component indicators display a solid green icon.
Open SIMATIC Shell in Windows File Explorer; confirm that the OS Single Station lists the WinCC application as registered.
On the ES, initiate an OS download; verify that the transfer proceeds without target station or network timeout errors.

Limitations and Operational Precautions

Never configure the secondary station as a 'WinCC Application (appl. ref)' if it is intended to run as an independent OS Single Station with its own controllers and communication stacks. Reference applications are used exclusively for redundant server partners or identical client views.

Engineer FAQ

Why does PC Station download fail even though ping and RDP work?

Ping and RDP use standard Windows ICMP/TCP protocols, whereas PC Station downloads require SIMATIC Shell discovery, DCOM, and S7 Station Manager communication.