How to Configure Two PCS 7 Operator Stations for an S7-400H System
Configure each intended PCS 7 OS station explicitly in the engineering project and review its NetPro connection to the S7-400H system. The Siemens OS manual describes selecting a fault-tolerant S7 connection for an H-station and repeating configuration for other operator stations. This provides a documented implementation baseline; it does not establish why, in a PCS 7 V9.0 SP3 installation, loading the second station disconnects the first.
Table of Contents
- Establish the Intended OS Architecture
- Configure the OS-to-AS Connections
- Check Each PC Station Before Downloading
- Verification
- Limitations and Operational Precautions
- Engineer FAQ
- Technical References
- Related Articles
- Related Tags
Establish the Intended OS Architecture
The reported configuration uses PCS 7 V9.0 SP3, WinCC V7.4, CPU 414-5H controllers and two PC stations with CP 1623 interfaces. After copying an initial OS configuration and downloading, only the most recently downloaded OS communicates.
First establish whether the two computers are independent OS single stations, a redundant OS pair or clients of a server. These are different engineering arrangements. H-system controller redundancy does not, by itself, establish OS redundancy.
Preserve the project before changing the connection model. Record both OS station identities, their WinCC applications, configured interfaces and intended AS partner.
Configure the OS-to-AS Connections
The closest verified manufacturer procedure is in the PCS 7 V9.0 SP1 Operator Station manual, section 6.2.2. Confirm the corresponding installed V9.0 SP3 instructions before deployment.
- Insert the required OS and AS stations and configure their communication processors in HW Config.
- Open NetPro through Options > Configure network in SIMATIC Manager.
- Select the first OS's WinCC application and a free row in its connection table.
- Choose Insert > New Connection and select the intended CPU partner.
- For an H-station, choose S7 connection fault-tolerant. Review its properties and enter the symbolic connection name in Local ID.
- Repeat for the second OS.
Do not assume that a copied runtime project establishes the second PC station's engineering identity or connection configuration.
Check Each PC Station Before Downloading
Section 6.2.3 documents comparison of a SIMATIC-CP-based OS with its Station Configuration Editor. Compare the configured component indices and names and the PC-station name, then inspect component status.
As a project-specific review, prepare a two-row checklist recording the intended physical computer and configured station for each OS. Verify the selected download destination against that checklist. Keep engineering configuration, connection compilation, PC-station loading and OS runtime deployment as separate recorded actions.
A warning that existing system data will be replaced is not evidence that the correct destination has been selected. Do not accept it until the target and intended scope are established.
Verification
Demonstrate communication from both operator stations at the same time. Observe current process information and relevant connection status on both, then repeat the observations after the reviewed deployment to the second station.
If the first connection fails again, preserve the before-and-after connection tables, selected targets and diagnostic messages. This provides a reproducible symptom for investigation without assuming that a CPU connection resource or a copied identity is the cause.
Controller failover and OS redundancy tests are separate acceptance activities and require an approved test plan.
Limitations and Operational Precautions
The exact cause of the last-downloaded-station symptom is unresolved. No confirmed correction or successful simultaneous operation is documented. The opened connection procedure is from V9.0 SP1, while the affected installation is V9.0 SP3; its exact component and download applicability still require confirmation.
Do not reset the H CPUs, delete connection data or repeatedly overwrite system data as an exploratory repair. Preserve the working configuration, review redundancy state and controller availability, and establish a rollback before any live configuration change.
Engineer FAQ
Can two OS computers be configured with connections to an H-station?
The manufacturer procedure explicitly repeats connection configuration for other operator stations; the actual architecture and installed-version requirements still apply.
Does copying OS1 finish OS2 configuration?
No. Review the second station's identity, target and connection model separately.
Is this a proven repair for the reported download symptom?
No. The cause and recovery remain unconfirmed.
Technical References
- Siemens: Operator Station V9.0 SP1, October 2017, A5E39219159-AB — sections 6.2.2–6.2.3, OS connections and SIMATIC PC-station checks. This edition is the documented baseline, not proof of every V9.0 SP3 deployment detail.