Configuring PCS7 with Redundant S7-1500R via PROFINET

David Krause13 min read
Industrial NetworkingSiemensTutorial / How-to
Licensed PE Working through this on a live machine? A Maine-licensed engineer can take it from here — included with IMD hardware, by the hour for everything else. Book an engineer

Configuring PCS7 Communication with Redundant S7-1500R/H via PROFINET

Integrating a SIMATIC PCS 7 AS410 (S7-400H) process automation system with a redundant S7-1500R/H controller over PROFINET requires coordinated engineering across two tool environments: SIMATIC Manager / PCS 7 for the H-station side and TIA Portal for the S7-1500R side. The integration pattern is well-supported in PCS 7 V9.0 SP2 and later with TIA Portal V16/V17, but several engineering constraints must be respected: the redundant CPU is addressed through its System IP, the PROFINET ring must use MRP with a SCALANCE redundancy manager, and the S7 connection type must be configured as a Fault-tolerant S7 connection on the AS410 side.

Engineering scope: This procedure covers unicast S7 fault-tolerant connections between an AS410 station and an S7-1500R/H pair over PROFINET. It does not cover S7-1500H with R1 redundancy behavior or S7-1500 software redundancy, nor does it cover integration with PCS 7 V8.x or earlier.

1. Architecture Overview

The reference architecture pairs the high-availability PCS 7 controller (AS410 / S7-400H) with a redundant S7-1500R or S7-1500H station over a single PROFINET ring. Both CPU pairs present a single logical interface to the upper-level system by means of a shared System IP address, which is moved from the active primary CPU to the backup CPU when a redundancy event occurs. The AS410 sends and receives process data through two independent PROFINET interfaces on the S7-400H side and a single System IP on the S7-1500R side.

1.1 Logical Topology

  • AS410 pair: S7-400H with two CP443-1 modules (PROFINET IO) and one or two Sync modules for redundancy. Two PROFINET interfaces connect to ring A and ring B.
  • S7-1500R/H pair: Two CPUs (e.g., 1515R-2 PN or 1517H-4 PN) connected via PROFINET ring. The System IP is bound to the active CPU. Each CPU has its own PROFINET interface and a separate MRP-capable switch port.
  • SCALANCE XC/XB/XR switch: Acts as the MRP redundancy manager in the PROFINET ring. Connect one device as the MRP manager, all others as MRP clients.
  • Optional OS server / Engineering station: Used for PCS 7 Operator Station and WinCC communication.

1.2 Connection Model

The PCS 7 side terminates the S7 fault-tolerant connection on a CP443-1 EX30 or higher. The S7-1500R side terminates the connection on the PROFINET interface of either CPU, but from the AS410 perspective it appears as a single partner identified by the System IP. Fault tolerance is implemented at the S7 application layer (S7 fault-tolerant connection), not at the PROFINET ring level.

2. System Components and Prerequisites

Component Minimum Version Purpose
SIMATIC PCS 7 V9.0 SP2 (with HSP for S7-1500R/H) AS410 station engineering and OS server
SIMATIC Manager / STEP 7 V5.x V5.6 + HF for PCS 7 V9 Hardware configuration of AS410, NET PRO connection
TIA Portal V16 Update 7 or V17 S7-1500R/H hardware config, program, System IP
S7-1500R/H CPU Firmware V2.8.x or V2.9.x Redundant CPU pair with PROFINET ring
CP 443-1 EX30 / EX40 Firmware V3.x PROFINET interface on the AS410 side
SCALANCE XC/XB/XR Firmware V6.x (XR-100/XR-300) MRP manager in the PROFINET ring
CP 1543-1 (optional) Firmware V2.x External CPU interface on S7-1500R
Hardware compatibility: Verify that the S7-1500R/H order numbers are accepted by the installed TIA Portal version. CPUs released after V16 (e.g., 1518H-4 PN with firmware V2.9) require TIA Portal V17 with the matching HSP. The Siemens Industry Online Support portal lists compatible CPUs under "S7-1500R/H Compatibility Tool".

3. PROFINET Ring Topology with MRP

The PROFINET ring is the physical foundation of S7-1500R/H redundancy. Configure a closed PROFINET ring with the SCALANCE switch as the MRP manager.

3.1 Ring Construction

  1. Connect Port 1 of CPU 0 to Port 1 of the SCALANCE switch.
  2. Connect Port 1 of CPU 1 to the next SCALANCE port.
  3. Connect the CP443-1 modules of the AS410 to two additional ports of the SCALANCE switch.
  4. Close the ring by wiring back to an unused SCALANCE port (not required if star topology is used, but a closed ring is required for MRP).

3.2 MRP Configuration

Inside TIA Portal, navigate to Devices & Networks > Topology view. Define the ring ports on each device. For the SCALANCE manager, set MRP role = Manager; for both CPUs and the CP443-1 set MRP role = Client. The MRP manager must support MRP-Rev1 or higher; do not enable MRPD or MRP-Auto Manager on the manager port that is connected to a CPU ring port.

Ring port guidance: The PROFINET ring must not contain more than one MRP manager. Connecting two manager-capable switches in the same ring causes a permanent MRP alarm. For S7-1500R the CPU ports themselves are MRP clients and cannot act as manager.

4. S7-1500R/H System IP Configuration (TIA Portal)

The System IP is the single IP address visible to external partners. When the primary CPU fails, the System IP moves to the backup CPU. This is what AS410 will use to reach the redundant station.

4.1 Enable System IP in TIA Portal

  1. Open the S7-1500R device configuration in TIA Portal.
  2. Select the PROFINET interface X1 (or X2, depending on which is the PROFINET ring port).
  3. Open Properties > PROFINET interface > Ethernet addresses.
  4. Tick the box "Activate system IP" and enter the IP address and subnet mask that will be visible to the AS410. Example: 192.168.0.10 / 255.255.255.0.
  5. Each CPU still receives its own IP address under IP protocol > Set IP address in the project for diagnostic access (e.g., CPU0 = 192.168.0.11, CPU1 = 192.168.0.12).

4.2 Hardware Configuration Parameters

Parameter CPU 0 CPU 1 Notes
IP address (device) 192.168.0.11 192.168.0.12 Used for engineering/diagnostics
System IP 192.168.0.10 Used by AS410 S7 connection
Subnet mask 255.255.255.0 255.255.255.0 Same subnet as AS410 CP443-1
PROFINET device name s71500r-cpu0 s71500r-cpu1 Unique per CPU, mandatory for ring
Role Primary Backup Set under Redundancy > Role assignment

The official Siemens Function Manual describes this procedure under "Configuring PROFINET IO on a redundant S7-1500R/H system" (see Siemens PROFINET with redundant S7-1500R/H). The same document states that additional PROFINET IO devices should be attached through a switch in the ring rather than chained.

5. AS410 H-System Configuration (SIMATIC Manager)

The PCS 7 side uses SIMATIC Manager (STEP 7 V5.6) for hardware configuration of the AS410. The CP443-1 modules must have PROFINET IO mode activated and the partner network must include the System IP of the S7-1500R.

5.1 CP443-1 Configuration

  1. Open the AS410 hardware configuration (HW Config) in SIMATIC Manager.
  2. Open the properties of the CP443-1 EX30 module in slot 4 (PROFINET IO side).
  3. Set the IP address (e.g., 192.168.0.20), subnet mask, and PROFINET device name.
  4. Select the Ethernet tab and verify that the S7 protocol is enabled.
  5. In Time-of-day synchronization, configure the synchronization mode if needed for time stamping in PCS 7.

5.2 Network Entry in NET PRO

Open NET PRO from SIMATIC Manager (Options > Configure Network). The S7-1500R is inserted as a SIMATIC S7 Station with a generic S7 CPU placeholder, then connected to the AS410 subnet.

  1. Right-click the AS410 station > Insert New Object > SIMATIC S7 Station.
  2. Select the S7-1500R placeholder type. NET PRO will list "S7-1500R/H" only after the matching PCS 7 HSP is installed.
  3. Set the partner IP address to the System IP 192.168.0.10 (NOT the individual CPU IPs).
  4. Set the partner rack/slot to 0 / 0 (rack 0, slot 0 of the System IP).

6. Establishing the Fault-Tolerant S7 Connection

The fault-tolerant S7 connection is configured in NET PRO. Both endpoints are required.

6.1 Insert the Connection in NET PRO

  1. In NET PRO, select the CP443-1 of the AS410.
  2. Right-click and choose Insert New Connection > S7 Connection.
  3. Choose the S7-1500R placeholder as the partner.
  4. In the connection properties, set:
    • Connection type: S7 connection fault-tolerant.
    • Connection name: e.g., AS410_to_1500R_FT1.
    • Local ID: assigned by NET PRO, used in the CFC block.
    • Partner IP: 192.168.0.10 (System IP).
    • Rack / Slot partner: 0 / 0.
  5. Compile and download the NET PRO data to the AS410.

6.2 Connection Properties Cross-Check

Field AS410 (local) S7-1500R (partner)
IP address 192.168.0.20 (CP443-1) 192.168.0.10 (System IP)
Connection type Fault-tolerant S7 Passive / active on partner side
Connection resource Auto (1) Auto on the CPU side
Rack / Slot 0 / 4 (CP443-1) 0 / 0
S7 protocol Enabled Enabled (S7 server on the S7-1500R)

7. CFC Communication Blocks for the Process Data Exchange

The communication blocks are inserted on the PCS 7 side (AS410) only. The S7-1500R exposes the data through standard DBs and operates as the S7 server.

7.1 Block Selection

Block Direction Use case Notes
FB 12 "BSEND" / FB 13 "BRCV" Bidirectional segmented Large data packets up to 64 KB Use for bulk diagnostics or recipe data
FB 14 "GET" / FB 15 "PUT" Unidirectional read/write Status, setpoints, parameters Most common for process I/O
FB 8 "USEND" / FB 9 "URCV" Uncoordinated send/receive Fast alerts, 32-Bit variables No acknowledgment at application layer
SFB 9 "S_R" / SFB 11 "S_P" (compact log) Print / diagnostic OS message forwarding Sometimes used for message frames
Tip: For PCS 7 V9 with AS410, the CFC library "PCS7 Library" provides ready-made channel blocks (e.g., C_PUTR, C_GETR) that wrap PUT/GET with PCS 7 status mapping. Use these instead of raw FB14/FB15 if you need signal status (Quality Code) propagation.

7.2 Example: PUT Block to Write a Setpoint

The PUT block writes one or more DB areas to the S7-1500R. Configure the inputs as follows in CFC:

  • REQ: 1 (start trigger)
  • ID: Local ID from NET PRO (e.g., W#16#0001).
  • DONE, ERROR, STATUS: Output status words.
  • SD_1: P#DB200.DBX0.0 BYTE 32 – local source area on AS410.
  • ADDR_1: P#DB100.DBX0.0 BYTE 32 – partner destination on S7-1500R.
  • LEN: 32 (bytes)

For a fault-tolerant connection the block automatically retries over the redundant CP443-1 if the active path fails. No additional block parameters are required.

7.3 Example: GET Block to Read Process Variables

  • ID: same connection ID as the PUT block.
  • SD_1: local destination area on the AS410 side (e.g., DB300).
  • ADDR_1: source area on S7-1500R (e.g., DB100, offset 0, length 32 bytes).

Pair GET with PUT to maintain a 2-way handshake: GET reads the acknowledgment word written by the S7-1500R program, PUT writes new setpoints each cycle. Trigger both blocks every 250–500 ms depending on the OS update cycle.

8. Compilation, Download, and Verification

8.1 Download Sequence

  1. Download the S7-1500R hardware configuration (with System IP) to both CPUs from TIA Portal. Ensure Online > S7-1500R/H Diagnostic > Redundancy Status shows RUN/standby.
  2. Download the S7-1500R program (DBs and any OB1 logic) to both CPUs.
  3. From SIMATIC Manager, download the AS410 hardware configuration including the CP443-1 and NET PRO data.
  4. Compile the AS410 CFC chart and download only the chart (not the program) to keep the running program intact.

8.2 Verification Matrix

Check Tool Expected Result
PROFINET ring is closed TIA Portal Topology All ports show "OK"
MRP manager detected SCALANCE Web UI MRP ring status = OPEN; clients list contains both CPUs and CP443-1
System IP responds to ping Engineering station Reply from 192.168.0.10
S7 connection established AS410: NetPro > Online > Connection status Connection state = ESTABLISHED
CFC block DONE / ERROR AS410: CFC online DONE = 1, ERROR = 0, STATUS = 0
Redundancy switchover Manual: TIA Portal > Online > "Switch to backup CPU" Connection drops briefly and re-establishes on System IP without program stop

8.3 Diagnostic Information

  • TIA Portal: Online & Diagnostics > S7-1500R/H Redundancy shows the current primary, standby status, and last sync age.
  • AS410: CFC online > block STATUS returns W#16#0000 (no error) or W#16#80XX (transport-level issue).
  • SCALANCE: Information > MRP page shows whether a ring port is currently blocked (normal behavior with one manager).

9. Troubleshooting Matrix

Symptom Likely Cause Fix
Connection in NET PRO shows "NOT ESTABLISHED" immediately Partner IP is the individual CPU IP, not the System IP Re-enter the partner IP as the System IP (192.168.0.10). Confirm TIA Portal shows "Activate system IP" ticked.
STATUS = W#16#80B1 in CFC block S7 connection resource busy (e.g., PUT/GET rate too high) Increase the cycle time of the trigger, reduce the number of simultaneous blocks per CP443-1, or split between CP443-1 EX30 and EX40.
MRP ring alarm: "Multiple managers" SCALANCE configured as manager and a CPU also acts as manager Confirm MRP role = Client on both S7-1500R CPUs. Only the SCALANCE should be manager.
System IP unreachable after CPU switchover PROFINET device name mismatch after firmware update Re-assign the PROFINET device name from TIA Portal under Online > Assign PROFINET device name.
S7 connection status flapping (UP/DOWN every few seconds) Subnet mask mismatch between CP443-1 and System IP Align subnet mask on AS410 and S7-1500R System IP (e.g., both 255.255.255.0).
Fault-tolerant connection compiles but download fails Missing HSP for S7-1500R/H on the SIMATIC Manager side Install the latest HSP from Siemens Industry Online Support, then rebuild HW Config.
DONE never goes to 1, no error REQ is not edge-triggered in CFC Wire REQ to a pulse generator or to the BO flag of a cycle counter that flips each scan.
OS messages stop after PCS 7 V9 OS restart S7 connection broke during OS startup Verify the S7 connection status in NET PRO after OS download; in some cases the connection ID must be re-mapped after a CFC master restart.

10. Field-Proven Engineering Notes

  • System IP requirement: Without a System IP the AS410 will address the active CPU only. After a switchover the S7 connection breaks until it times out. With a System IP the S7 layer follows the active CPU within ~200 ms.
  • CFC block placement: Place the SEND/PUT block on the master AS410 only; the partner AS410 (backup AS410) does not need the same chart. The fault-tolerant connection handles redundancy transparently.
  • MRP ring vs. star: A pure star with SCALANCE works, but the redundant ring protects against a single switch failure. Siemens explicitly recommends a ring for S7-1500R/H (see Siemens PROFINET function manual).
  • Firewall / routing: If a router separates the AS410 and S7-1500R, route the System IP through the same subnet or open the ISO-on-TCP port (TCP port 102). The default S7 communication uses port 102.
  • Time stamping: For PCS 7 sub-second time stamping, synchronize both the AS410 and S7-1500R through the same NTP server or use SIMATIC Time; mismatched time stamps will degrade the audit trail.
  • CPU 1518H-4 PN (firmware V2.9) and PCS 7 V9.0 SP2: official Siemens product compatibility matrix confirms the combination works with TIA Portal V17 and the matching HSP.

FAQ

Which IP address should the AS410 use to reach the S7-1500R pair?

The System IP address (e.g., 192.168.0.10), not the individual CPU IP addresses. Activate the System IP in TIA Portal under Properties > PROFINET interface > Ethernet addresses > Activate system IP. Each CPU retains its own diagnostic IP, but the S7 connection must use the System IP.

Do I need to configure the connection in both SIMATIC Manager and TIA Portal?

Yes. SIMATIC Manager / NET PRO defines the fault-tolerant S7 connection on the AS410 side, while TIA Portal configures the S7-1500R hardware including System IP and the DBs that hold the exchanged data. The S7-1500R only needs a "Permit S7 communication" option on the CPU's PROFINET interface; no partner configuration is needed in TIA Portal for the S7 connection itself.

Which CFC block is best for exchanging setpoints and process values?

Use FB 15 "PUT" to write setpoints and FB 14 "GET" to read process values. For PCS 7 with signal status, use the wrapped blocks C_PUTR / C_GETR from the PCS 7 Library. Avoid plain BSEND/BRCV unless the payload exceeds 64 KB.

Do I need an MRP manager in the PROFINET ring?

Yes. The ring requires exactly one MRP manager. Use a SCALANCE switch (XC208, XC216, XR-100, or similar) as the manager, and set all other ring participants (both S7-1500R CPUs and CP443-1 modules) to MRP client role in TIA Portal and SIMATIC Manager respectively.

What happens to the S7 connection during an S7-1500R switchover?

The connection drops briefly (~200–500 ms) while the System IP migrates from CPU 0 to CPU 1, then the fault-tolerant connection re-establishes automatically. The CFC block's STATUS may briefly indicate a transport error (e.g., W#16#80B1); with REQ retriggered it resumes without intervention.

Is the S7-1500R system IP enough for redundancy or do I need two redundant connections?

A single fault-tolerant S7 connection targeting the System IP is sufficient for application-level redundancy. Do not create two separate connections (one to each CPU); the System IP abstraction is the entire point of the S7-1500R/H architecture.

Back to blog