How to Troubleshoot S7-H Communication Alarms Between Automation Stations and WinCC OS in PCS 7

In SIMATIC PCS 7, an Operator Station reporting system alarms for communication loss to an Automation Station (AS) while process tags continue updating normally indicates that one physical sub-connection of a redundant S7 Fault-Tolerant Connection (S7-H connection) has failed while the partner sub-connection remains healthy. The fault-tolerant communication driver automatically routes traffic through the surviving network ring, maintaining live process visualization. Diagnosing the issue requires opening WinCC Channel Diagnosis to identify which specific physical link (Sub-connection 1 or 2) failed, checking switch port links, and ensuring the 'Default Master' setting is disabled on the Standby Server.

Architecture of S7 Fault-Tolerant Connections (S7-H)

In high-availability SIMATIC PCS 7 installations (using S7-400H or CPU 410-5H controllers paired with redundant OS Servers), process data communication across the Plant Bus utilizes S7 Fault-Tolerant Connections (S7-H Connections).

An S7-H connection is an advanced Layer 4/Layer 7 communication mechanism designed to survive cable breaks, switch failures, and communication processor faults:
1. Physical Redundancy: An S7-H connection comprises two independent physical sub-connections (Sub-connection 1 on Plant Bus Ring 1, and Sub-connection 2 on Plant Bus Ring 2).
2. Deterministic Driver Layer: In the OS Server (running SIMATIC NET S7-1613 / S7-RedConnect with CP 1623 or Hardnet-IE), the driver continuously supervises both physical paths using high-frequency keep-alive telegrams.
3. Bumpless Failover: If a physical cable is severed or a switch port goes down on Ring 1, the driver transparently redirects data traffic to Ring 2 within milliseconds without dropping a single process variable or operator command.

Root Cause Analysis for Communication Alarms with Active Tags

Engineers frequently encounter a confusing scenario:
* WinCC Alarm Logging displays prominent system alarms: 'Connection to AS faulted' or 'Communication error between AS and OS'.
* Yet, when looking at the process graphics, all motor icons, valve faceplates, and analog trend curves are actively updating with green healthy quality!

The Reason Behind the Discrepancy

Partial Redundancy Loss: The system alarm is triggered because one of the two sub-connections has failed. The OS is alerting maintenance that fault tolerance is lost.
Active Surviving Link: Because the secondary sub-connection is fully operational, WinCC continues receiving live AS data seamlessly.
Common Triggering Faults:
1. A severed patch cable between an AS CP 443-1 and SCALANCE switch Ring 1.
2. Duplicated IP addresses on one of the redundant subnets.
3. Misconfiguration of the 'Default Master' checkbox in WinCC Redundancy settings (the Standby Server must have 'Default Master' unchecked).
4. Network card operating mode mismatch in Station Configuration Editor (PG mode vs Configured mode).

Diagnostic Workflow via WinCC Channel Diagnosis and NetPro

To identify the exact broken link without disrupting operations:

Step 1: Launch WinCC Channel Diagnosis

On the OS Server in WinCC Runtime, open Start -> Siemens Automation -> SIMATIC WinCC -> WinCC Channel Diagnosis (or launch WinCC\bin\ChannelDiagnosis.exe).
In the tree view, expand SIMATIC S7 Protocol Suite -> Named Connections.
Select the connection to the affected controller (e.g., OSS_AS01):
* Inspect the Connection Status: It will indicate Fault-Tolerant (Partial Link Down).
* Observe Sub-connection 1: Note whether state is Ready / Connected or Disconnected / Error.
* Observe Sub-connection 2: Identify which specific physical path reports error code 0x0001 or 0xFFDF.

Step 2: Correlate with NetPro Routing

In SIMATIC Manager, open NetPro.
Select the PC Station and double-click the S7 fault-tolerant connection:
* Identify which CP module (e.g., CP in Slot 5 vs Slot 6) corresponds to the disconnected sub-connection.
* Trace the physical cable from that CP to the SCALANCE switch.

Step 3: Check WinCC Redundancy Settings

In WinCC Explorer, double-click Redundancy.
On the Master OS Server, ensure that 'Default Master' is checked if intended.
On the Standby OS Server, ensure that 'Default Master' is strictly UNCHECKED. (Having both checked causes simultaneous master contention).

S7-H Connection States and Redundancy Diagnostic Matrix

The following table outlines the diagnostic states reported by WinCC Channel Diagnosis for S7-H connections:

Reported Connection StateSub-connection 1Sub-connection 2Tag Value QualityGenerated System AlarmCorrective ActionFully OperationalConnectedConnectedHealthy (16#80)NoneNormal fault-tolerant operationDegraded (Partial Loss)DisconnectedConnectedHealthy (16#80)Connection DegradedRepair physical cable/switch on Ring 1Degraded (Partial Loss)ConnectedDisconnectedHealthy (16#80)Connection DegradedRepair physical cable/switch on Ring 2Total LossDisconnectedDisconnectedBad (16#00)Connection BrokenCheck CPU power, AS rack, or bus cablesContention ConflictConnectedConnectedChatteringRedundancy ConflictUncheck 'Default Master' on Standby OS

Inspecting sub-connection states isolates the physical failure point immediately.

Verification

To verify that fault-tolerant communication is fully restored:
1. Repair the physical Ethernet connection or correct the NetPro routing.
2. In WinCC Channel Diagnosis, verify that both Sub-connection 1 and Sub-connection 2 report status: Connected / Operational.
3. In WinCC Alarm Logging, verify that the system communication alarm transitions to 'Outgoing' (acknowledged and cleared).
4. Simulate a fault by disconnecting Sub-connection 1: confirm that tags continue updating without interruption.
5. Reconnect Sub-connection 1: confirm automatic return to fully redundant operational status.

Limitations and Operational Precautions

Do not ignore 'partial connection loss' alarms; operating on a single sub-connection leaves the plant with zero communication redundancy.
Never reboot an active OS Server while its redundant partner is in a degraded connection state, as this will blind the operators.
Ensure CP 1623 communication processors in the OS PC have identical firmware and driver updates installed.
Ensure SCALANCE industrial switches have ring redundancy (HRP or MRP) configured properly without topology loops.

Engineer FAQ

Why did the OS alarm report communication failure when tags were still updating?

In redundant S7-H connections, a failure on one network ring triggers an alarm alerting you to lost redundancy, while the surviving secondary ring continues delivering live tag values.

Where do I find WinCC Channel Diagnosis?

Launch ChannelDiagnosis.exe from C:\Program Files (x86)\Siemens\WinCC\bin, or access it via WinCC Explorer under Tools -> Channel Diagnosis.

What is the 'Default Master' setting in WinCC Redundancy?

'Default Master' defines which server acts as the preferred active master upon simultaneous system startup. It must only be checked on Server 1 and never on Server 2.