Resolving OS Changes Download Failures and Network Name Violations in SIMATIC PCS 7

In SIMATIC PCS 7 systems, 'Could not establish connection to RT station' errors during changes-only OS downloads from the Engineering Station (ES) to an Operator Station (OS) frequently stem from computer name syntax violations (such as using hyphens or underscores), improper deployment via the WinCC Project Duplicator, or network misconfigurations in Simatic Shell. Resolving the failure requires renaming computers to conform to strict 15-character alphanumeric naming standards, configuring stations as proper PC Stations in SIMATIC Manager, and executing downloads exclusively via SIMATIC Manager Target OS functions.

Strict Computer Naming Rules for PCS 7 and WinCC

A foundational prerequisite for reliable distributed PCS 7 operation is strict compliance with Siemens computer naming conventions. Microsoft Windows permits hyphens (-) and underscores (_) in hostnames, but the underlying Siemens communication architecture—which relies on NetBIOS name resolution, SQL Server named instances, and RPC/DCOM services—strictly prohibits these characters.

Key rules for PCS 7 workstation hostnames:
- Character Set: Only letters (A–Z, a–z) and numbers (0–9).
- Forbidden Characters: No hyphens (-), underscores (_), periods (.), spaces, or special symbols. Names such as WOLLY-PC or WOLLY_ASUS violate these rules and break internal remote SQL connection strings.
- Length Constraint: Maximum 15 characters (due to NetBIOS limits).
- First Character: Must always begin with a letter, never a numeral.

Project Duplicator Incompatibility in PCS 7 Architectures

In standalone WinCC SCADA systems, the WinCC Project Duplicator is commonly used to replicate projects between servers. However, using Project Duplicator in SIMATIC PCS 7 is strictly prohibited:

Destruction of Engineering Links: PCS 7 OS projects are integral components of a STEP 7 Multiproject. Moving projects via Project Duplicator detaches the OS project from the Master Data Library and Plant Hierarchy.
Delta Tracking Corruption: Changes-only compilation and download rely on change-logging tables synchronized between the ES database and the target OS. Duplicating files overwrites these tracking tables, corrupting the delta-download mechanism.
Correct PCS 7 Deployment Procedure:
- Configure the OS as a SIMATIC PC Station in SIMATIC Manager.
- Configure the target computer name and target path in the PC Station properties.
- Deploy initial and delta projects exclusively via PLC > Download (or right-click OS > Target OS > Download).

Simatic Shell Configuration and Terminal Bus Routing

Simatic Shell coordinates encrypted and unencrypted network discovery between PCS 7 stations across the Terminal Bus:

Network Adapter Binding: In Windows Explorer, right-click Simatic Shell and select Settings.... Verify that the network adapter selected is the dedicated Terminal Bus card, not corporate LAN, WiFi, or a virtual VPN adapter.
Multicast Communication: Simatic Shell utilizes multicast (Port 5222 or broadcast) to discover partner stations. Ensure network switches allow multicast traffic across the Terminal Bus subnet.
Windows User Credentials: Both the ES and OS workstations must have identical local Windows user accounts with identical non-blank passwords, and the user must be a member of the local groups SIMATIC HMI, SIMATIC NET, and Administrators.

Troubleshooting Matrix for OS Download Failures

The following table details diagnostic checks when OS changes download fails:

Diagnostic CheckSymptom / Failure StateCorrective ActionComputer Name SyntaxHostname contains - or _ (e.g. WOLLY_ASUS)Rename PC in Windows System Settings; update PC Station name in SIMATIC Manager; rebootDeployment MethodProject copied manually or via Project DuplicatorPerform full initial download from SIMATIC Manager (Target OS > Download > Entire Project)Simatic Shell VisibilityTarget OS not visible in ES Simatic ShellCheck network adapter binding in Simatic Shell; verify Terminal Bus subnet; check firewallWindows User RightsAccess denied / RPC server unavailableEnsure identical username and password on both machines; assign to SIMATIC HMI groupSQL Server InstanceSQL Server service stopped on target OSOpen Windows Services (services.msc); ensure SQL Server (WINCC) is running

Note: Following any computer rename in Windows, the computer name must be updated in the STEP 7 PC Station properties, followed by a full OS compilation and full project download.

Verification

Verify OS download connectivity after correcting naming and network settings:
1. Open Windows Explorer on the ES and expand Simatic Shell; verify that the target OS computer appears in the list and shows blue workstation status.
2. Right-click the OS computer in Simatic Shell and select Properties; confirm communication state is 'Accessible'.
3. In SIMATIC Manager, right-click the OS object and select Target OS > Download.
4. Select Changes only; verify that the transfer progress bar completes without RPC connection errors.
5. In WinCC Runtime on the OS station, confirm that modified graphic screens update online without interrupting operator runtime.

Limitations and Operational Precautions

Essential rules for PCS 7 OS engineering:
- Renaming a computer hosting an active WinCC SQL database requires running the Siemens CCConfigStudio or WinCC database rename utilities, or reinstalling SQL instances; never rename a PC without reviewing WinCC documentation.
- If changes-only download has been broken by an illegal action (such as manual file modification), a Full Download is mandatory, which deactivates WinCC Runtime and closes operator screens.
- Always perform complete OS compilation and downloads during planned maintenance windows when recovering from corrupted station states.

Engineer FAQ

Why does WinCC allow hyphens in Windows if PCS 7 forbids them?

Windows permits hyphens, but WinCC's underlying Microsoft SQL Server instance configuration and internal SIMATIC communication protocols interpret hyphens and underscores as delimiters or invalid syntax.

Can I use Project Duplicator to set up a redundant OS server in PCS 7?

No. In PCS 7, redundant servers are configured in SIMATIC Manager under the same OS PC Station object. Project Duplicator is only for standalone WinCC projects outside PCS 7.

What should I do if 'Download Changes' is grayed out?

If the option is disabled, the system has detected a database structural mismatch or interrupted download. You must execute a complete project download to re-synchronize delta tracking.