Resolving 'RT Station Not Available' During WinCC Online Changes Download in SIMATIC PCS 7

In SIMATIC PCS 7 environments, 'RT station not available' (Runtime-Station nicht verfügbar) errors encountered during changes-only OS downloads from the Engineering Station (ES) to an Operator Station (OS) occur when network discovery is interrupted, security permissions are misconfigured, or database structural changes invalidate delta loading. Once delta loading is locked, the 'Changes only' option becomes grayed out, forcing an entire project download that interrupts WinCC Runtime. Resolving this issue requires auditing Simatic Shell adapter priority, verifying matching Windows user accounts, and adhering to strict online-change engineering rules.

Prerequisites for Online Changes Download in PCS 7

The SIMATIC PCS 7 'Download changes online' feature enables engineers to deploy graphic modifications, updated CFC block parameters, and alarm text adjustments from the Engineering Station directly to running Operator Stations without shutting down WinCC Runtime or blinding plant operators.

To maintain continuous runtime execution during delta downloads, specific prerequisites must be maintained:
- Active Runtime State: WinCC Runtime must be actively running on the target OS.
- Synchronized Delta Tracking: The local change-tracking database on the ES must remain in lockstep with the target OS database.
- Unbroken RPC and SQL Channel: Bidirectional communication via Remote Procedure Call (RPC) and Microsoft SQL Server named instances (WINCC) must be fully operational over the Terminal Bus.
- Identical Security Credentials: The Windows user account initiating the download on the ES must exist on the target OS with the exact same password and membership in the SIMATIC HMI user group.

Network and Communication Root Causes in Simatic Shell

When the download wizard reports that the runtime station is unavailable, communication across the Terminal Bus has failed:

Simatic Shell Adapter Binding:
- On both the ES and OS, open Windows Explorer, right-click Simatic Shell, and select Settings....
- Verify that the active network interface is bound exclusively to the physical Terminal Bus network adapter. If multi-homed computers bind Simatic Shell to an office LAN, corporate gateway, or SIMIT adapter, multicast broadcast packets will be lost.
Encrypted Communication Mismatch: In PCS 7 V8.1/V8.2, Simatic Shell supports encrypted station communication. If encryption is enabled on the ES but disabled on the OS, or if the pre-shared key (PSK) does not match, the stations cannot authenticate.
Name Resolution and Ping Test: Execute forward and reverse ping commands using hostnames (ping OS_NAME and ping -a IP_ADDRESS). If DNS or NetBIOS resolution returns incorrect IP addresses, update the local Windows hosts file.

Database Modifications That Invalidate Delta Downloads

Certain engineering modifications alter the core SQL database schema or internal communication architecture, which automatically disables the delta-download mechanism:

Redundancy Configuration Changes: Modifying redundant partner assignments, serial/Ethernet connection cables, or archive sync paths.
User Administrator Structural Changes: Adding new authorization levels or changing fundamental security roles in WinCC Explorer.
Modifying Alarm Logging Archive Configuration: Changing segment sizes, archive swap directories, or time-based archiving rules.
Modifying Tag Logging Structure: Adding new archive tags that alter cyclic database table partition schemes.
Modifying Symbolic Server Package Names: Renaming the server prefix or changing server data package options.
When any of these structural changes occur, PCS 7 deliberately grays out Changes only, requiring an Entire download to re-initialize database tables.

Diagnostic Matrix for OS Download Failures

The following table details diagnostic checks and recovery actions for OS download errors:

Failure SymptomProbable CauseCorrective Action'RT station not available'Simatic Shell bound to incorrect network adapterRebind Simatic Shell to Terminal Bus NIC; restart PCStation visible in shell, download fails immediatelyUser authentication failure (RPC Error)Verify matching Windows username, password, and SIMATIC HMI group on both PCs'Changes only' option grayed outStructural database change made in ES projectPlan a maintenance window; perform a complete project download (Entire download)Download stalls at SQL table copyWindows Firewall blocking SQL / RPC trafficEnsure Windows Firewall allows ports 135, 445, 1433, 1434, and WinCC executablesStation disappears intermittentlyNetwork switch dropping multicast trafficConfigure IGMP snooping and multicast forwarding on Terminal Bus network switches

Note: In redundant OS configurations, never perform an entire download to both servers simultaneously. Always download Server Standby first, verify client failover, and then download Server Master.

Verification

Verify recovery and successful changes-only download:
1. Open Windows Explorer on the ES and confirm the target OS appears with an active blue icon under Simatic Shell.
2. Right-click the OS computer in Simatic Shell and verify status reads 'Accessible'.
3. In SIMATIC Manager, right-click the OS object and select Target OS > Download.
4. Select Changes only; confirm that the progress bar advances through database generation, file copying, and runtime notification without error.
5. In WinCC Runtime on the OS, verify that the modified graphic screen displays updated elements immediately without restarting the WinCC process.

Limitations and Operational Precautions

Essential rules to prevent unrecoverable download lockouts:
- Never edit files directly inside the OS project folder on the target workstation while runtime is active.
- Never use Windows Remote Desktop (RDP) in standard console-switching mode to access an OS station during downloads; use Siemens-approved VNC or administrative session tools (mstsc /admin).
- If an online change download fails halfway due to a network disruption, do NOT attempt immediate re-downloading; reboot the target OS, verify runtime stability, and re-attempt delta compilation on the ES.

Engineer FAQ

Can I restore the 'Changes only' option without performing a full download?

Generally no. Once the change-tracking delta engine detects an inconsistent database transaction or structural change, delta tracking is severed. A complete download is required to establish a new synchronized baseline.

How do I perform a complete download without shutting down plant operations?

In a redundant server environment, perform the complete download to the Standby server. When it re-enters runtime, force client switchover to the Standby server, and then download the Master server.

Which Windows services manage the changes-only download?

The Remote Procedure Call (RPC) service, DCOM Server Process Launcher, and SQL Server (WINCC) service coordinate file transfer and database synchronization.