Configuring WinCC PCS7 V7 Redundant S7 Connection to S7-414-4H

1. Overview

Establishing a redundant connection between a WinCC Operator Station and a Siemens SIMATIC S7-400H station (for example the CPU 414-4H) under PCS 7 V7.0 is a recurring engineering task on brownfield plants. The H-station uses two synchronized CPUs and a fault-tolerant backplane bus; the OS must therefore keep a logical connection alive regardless of which CPU is currently the active partner. The naive approach — running the standard WinCC "Create Redundant Connection" Dynamic Wizard against a normal IE General (onboard PROFINET/Industrial Ethernet) interface — produces a C-action script that monitors tags such as @ConnectionState and @ConnectionError, but it does not implement the fault-tolerant S7 connection expected by an H-station. This reference explains the boundary between what the wizard can do, why it cannot replace S7-Redundancy on an S7-414-4H, and how to deploy the correct configuration with SIMATIC NET CP 1613.

2. S7-400H Redundancy Architecture in PCS 7 V7

An S7-400H system (CPU 414-4H or CPU 417-4H) is composed of two redundant subsystems, each with its own CPU, power supply, and synchronization module, mounted on a fault-tolerant backplane (UR2-H or UR1-H). Both CPUs execute the same user program; only one is the master at any instant. A fiber-optic sync link keeps event-of-state and process-image data identical so that failover is bumpless for the connected I/O.

Two physical CP 443-1 modules are typically installed (one per CPU) so that the OS can reach both halves of the H-station. The S7-Redundancy driver on the OS PC must be able to address both CP 443-1 modules independently and switch the logical connection when the active CPU changes.

3. WinCC Redundant Connection Types

WinCC supports three conceptually different "redundant" mechanisms. They are not interchangeable.

The Dynamic Wizard "Create Redundant Connection" populates the tags @ConnectionState, @ConnectionError, and a C-action that toggles a quality bit. It is designed for software redundancy against two discrete PLCs, not for the synchronized CPU pair inside one H-station. Re-using the script on an H-station fails because the two "partners" the script cycles between are not two separate stations — they are two roles played by the same logical controller.

4. CP 1613 vs. IE General: Hardware Boundary

SIMATIC NET CP 1613 (and its successors CP 1623, CP 1628) is more than a network interface: it ships with the S7-Redundancy protocol stack that knows how to negotiate with an H-station through both CP 443-1 channels. An onboard IE General port uses the standard Windows TCP/IP socket path; it cannot terminate the redundant S7 connection state machine.

For a CP 1613 the configuration tool SIMATIC NET Commissioning (or Commissioning PC Station in newer releases) is used to bind the card to an "S7-Redundancy" access point. The access point is then referenced from the WinCC channel S7-Redundancy instead of S7.

5. The WinCC "Redundant Connection" Dynamic Wizard

The wizard invoked in a standard WinCC project from Dynamic Wizard > WinCC > Create Redundant Connection generates three artifacts:

1. An internal tag group prefixed with @:
   • @ConnectionState — DWORD, current state of the active connection
   • @ConnectionError — DWORD, last error code from the cyclic test
   • @ConnectionName — TEXT, name of the monitored logical connection
2. A C-action attached to a configurable trigger (default 1 s) that issues a small read request on the alternate connection and flips the active connection if the primary fails.
3. A Software redundancy.wnf script artifact referenced internally by the C-action.

The C-action skeleton (paraphrased to illustrate behavior; values are read at runtime from the tag database):

// Excerpt — WinCC "Create Redundant Connection" C-action
if (GetTagDWord("@ConnectionError") != 0)
{
    // Primary path failed, swap logical connection
    SetTagChar("@ConnectionName", "S7_REDUND_B");
    // Force quality code propagation
    SetTagDWord("@ConnectionState", 2); // 2 = backup active
}
else
{
    SetTagChar("@ConnectionName", "S7_REDUND_A");
    SetTagDWord("@ConnectionState", 1); // 1 = primary active
}

This logic is appropriate for two discrete PLCs on the network. For an S7-414-4H the two "partners" share process image and program; routing C-actions at them confuses the redundant state machine because there is no "other PLC" to fail over to — both IP addresses point at the same logical controller.

6. Why the Wizard Script Fails on an H-Station

Three concrete failure modes appear in field engineering:

7. Configuring S7-Redundancy for WinCC PCS 7 V7

The correct end-state configuration is a channel of type S7-Redundancy in the WinCC project, backed by an access point CP_HMI (or customer-named equivalent) bound to the CP 1613.

7.1 Prerequisites

• SIMATIC NET installed on the ES/OS PC (version aligned with PCS 7 V7 — verify in the PCS 7 V7.0 readme).
• CP 1613 (or CP 1623) installed and recognized by SIMATIC NET.
• Two CP 443-1 modules in the S7-400H station, each with a unique IP address on the plant bus.
• STEP 7 / PCS 7 project with the S7-400H station compiled and downloaded; H-station is in RUN/Redundant.
• WinCC PCS 7 OS project with the AS-OS connection generated by the PCS 7 engineering toolchain.

7.2 Step-by-step

1. In SIMATIC NET Commissioning, assign the CP 1613 to the access point CP_HMI and select the mode S7-Redundancy.
2. Verify both CP 443-1 IP addresses are reachable from the OS PC with ping; the S7-Redundancy driver uses both during partner discovery.
3. In the WinCC Explorer of the OS project, open Tag Management > S7-Redundancy. If the channel is missing, the SIMATIC NET install on this PC was either missing or installed after WinCC — repair the WinCC install.
4. Create a new connection named (e.g.) AS01_H. In the connection properties, set:
   • Partner IP A: CP 443-1 of CPU 0
   • Partner IP B: CP 443-1 of CPU 1
   • Rack/Slot: 0 / 3 (CPU 414-4H default slot in the H-rack)
   • Connection resource: Automatic (driver picks next free on each CPU)
5. Generate tags via the PCS 7 OS project editor; do not run the "Create Redundant Connection" Dynamic Wizard.
6. Activate the WinCC Runtime. The status bar should report Connection OK (Primary) or Connection OK (Backup) for the S7-Redundancy channel.

8. Connection Resources and Limits

Each connection — redundant or not — consumes resources on the controller side. For an S7-400H the resources are counted per CPU; for the modern S7-1500R/H successor family Siemens publishes explicit connection-resource tables.

The S7-1500R/H documentation states: "Each communication connection to the redundant system S7-1500R/H occupies connection resources in the S7-1500R/H station." The same principle applied to S7-400H means that doubling the apparent number of connections (one per partner CPU) does not double the resource pool — the redundant driver presents a single logical connection to the application.

Engineers must size the OS-side connection count against the controller resource table, not against the OS project tag count. Background: see the official Siemens function manual Connection resources of the redundant system S7-1500R/H. The principle — one redundant connection still consumes two physical resources on the H-system (one on each partner CPU) but is exposed as one logical handle to WinCC — is identical for the older S7-400H.

9. Verification and Diagnostics

After commissioning, verify the redundant path with the following checks:

1. Channel diagnostic: In WinCC Explorer, right-click S7-Redundancy > Connection > AS01_H > Status. Both partner IPs should report Reachable.
2. Tag diagnostic: Force a value in STEP 7 (VAT table) on the standby CPU. Confirm WinCC shows the same value within one polling cycle. Repeat on the master CPU.
3. Failover test: Run H-CiR or pull the master CPU from the rack. The WinCC status should transition Primary → Backup within ~1 s; tag values should remain constant.
4. Resource audit: In STEP 7 Hardware > CPU Properties > Communication, verify the connection count does not exceed the controller's documented maximum.
5. SIMATIC NET trace: Enable the S7-Redundancy trace in SIMATIC NET Commissioning during commissioning; review S7Redund.log for partner switch events.

10. Troubleshooting Matrix

11. Migration Note: From S7-400H to S7-1500R/H

Plants replacing S7-414-4H stations with the modern S7-1500R/H family must verify that the OS PC side still uses a SIMATIC NET card supporting S7-Redundancy (CP 1623 / CP 1628 or Softnet S7-Redundancy). The protocol principle is unchanged: one logical connection in WinCC backed by two partner IP addresses and a redundant-aware driver. Engineers migrating PCS 7 V7 OS projects to PCS 7 V9 should re-generate the S7-Redundancy channel rather than port it byte-for-byte; firmware-specific behavior is documented in the per-version function manual.

FAQ