S7-400H PROFINET on CPU 414-5H vs CP443-1: When Each Interface Is Required
The recurring engineering question on the S7-400H platform is straightforward: if the redundant CPU pair already carries an integrated PROFINET interface, do the two CP 443-1 communication processors still have to be configured, ordered, and installed? The answer is conditional. For most non-safety, non-routed HMI/PG, and standard PROFINET I/O tasks the integrated PROFINET port of the CPU 414-5H PN/DP (order number 6ES7414-5HM06-0AB0) is functionally sufficient, but several production-grade scenarios in redundant H-systems still require one or two CP 443-1 modules per CPU. This reference walks through the architecture, the catalog capabilities, the redundancy topology with the IM 155-5 PN HF (6ES7155-5AA00-0AC0), and a field-ready decision matrix.
1. S7-400H System Architecture Recap
The S7-400H is Siemens' high-availability PLC platform designed for fail-safe, hot-standby operation. Two CPUs of identical type and firmware execute identical user programs and synchronize via fiber-optic sync modules (up to 10 km with the appropriate sync module). A fault on the master causes the reserve to take over bumplessly. Communication is duplicated to match the redundancy model:
- Two independent PROFINET networks, each terminating on one of the H-CPUs (or a CP).
- Two independent PROFIBUS DP networks, each terminating on the integrated DP master of the CPU or on a CP 443-5 Extended.
- Two sync-module links (fiber pair) for event-synchronous data exchange between the two halves.
Communication processors are not "nice to have"; they are part of the redundant channel plan. A single CP 443-1 on one CPU creates an asymmetric failure domain: if that CPU fails, the CP goes with it. For S7-400H the rule is that any external network required for the process must be reachable from both halves of the pair.
2. CPU 414-5H PN/DP (6ES7414-5HM06-0AB0) Integrated Interfaces
The 6ES7414-5HM06-0AB0 is the PROFINET-enabled variant of the CPU 414-5H. Its on-board interface set is the starting point of the decision:
| Interface | Count | Physical | Typical Role |
|---|---|---|---|
| PROFINET (PN/IE) | 1 (2-port switch) | RJ45 x2, integrated 2-port switch | PROFINET IO, I-device, open IE communication, S7 communication, PG, HMI, web server, SNMP |
| PROFIBUS DP | 1 | 9-pin D-sub | PROFIBUS DP master or DP slave |
| MPI/DP | 1 (combined) | 9-pin D-sub | PG, HMI, MPI master, optional DP master |
| Sync module interface | 2 | Sync cable LC/LC fiber | Redundancy sync to the partner CPU |
The integrated PROFINET is a managed 2-port switch (100 Mbit/s, full duplex, auto-negotiation, auto-crossover). It supports PROFINET IO controller, IO device (I-device), and the full TCP/IP stack for S7 communication, open user communication (T-blocks), ISO-on-TCP, TCP, UDP, and the integrated web server. The number of PROFINET IO devices, S7 connections, and HMI connections is finite and CPU-specific. The CPU 414-5H PN/DP supports the lower tier of connection resources of the H family, so on dense HMI or routing projects the integrated port can saturate quickly.
3. CP 443-1 Family and Where It Is Used
CP 443-1 is the external PROFINET/Industrial Ethernet communication processor for the S7-400 and S7-400H. Variants relevant to H-systems include:
| Article Number | Short Designation | Ports | Notable Capabilities |
|---|---|---|---|
| 6GK7443-1EX30-0XE0 | CP 443-1 | 1 x RJ45 (10/100) | Standard PROFINET IO controller, S7 and open IE communication, IP routing, IP Access Control List, firewall on later firmware |
| 6GK7443-1EX40-0XE0 | CP 443-1 | 1 x RJ45 (10/100/1000) | Gigabit variant for high-traffic uplinks |
| 6GK7443-1GX30-0XE0 | CP 443-1 Advanced | 1 x RJ45 + IT functions | FTP, HTTP, e-mail, integrated switch on later firmware, security diagnostics |
| 6GK7443-1UX00-0XE0 | CP 443-1 OPC UA | 1 x RJ45 | OPC UA server, classic PROFINET IO controller |
The CP 443-1 occupies one slot in the S7-400 rack and is configured in STEP 7 V5.x (and in TIA Portal for compatible variants) as a separate PROFINET IO system. It brings its own set of connection resources independent of the CPU. In S7-400H each rack hosts one CP 443-1 per CPU, and the two CPs are configured as a redundant pair using the H-system redundancy mechanism in HW Config (H-station editor).
4. Functional Comparison: Integrated PROFINET vs. CP 443-1
The following table captures the engineering-relevant differences for the S7-400H use case. "Both" indicates equivalent support on the integrated port of the CPU 414-5H PN/DP and on the CP 443-1.
| Capability | Integrated PROFINET (CPU 414-5H) | CP 443-1 |
|---|---|---|
| PROFINET IO controller (PN IO) | Yes | Yes |
| PROFINET I-device (controller + device role) | Yes | Yes (via configuration) |
| Number of PN IO devices supported | Limited by CPU 414-5H resource budget (typically 256 IO devices with firmware V6) | Independent resource pool, often larger on Advanced variants |
| S7 communication (PUT/GET, BSEND/BRCV, USEND/URCV) | Yes, counts against CPU connection budget | Yes, counts against CP connection budget |
| Open IE communication (T-blocks TCON/TSEND/TRCV) | Yes | Yes |
| PG / engineering routing | Yes | Yes |
| HMI communication (WinCC, HMI Panels) | Yes, limited by HMI license and CPU connections | Yes, isolated from CPU connections |
| ISO-on-TCP / TCP / UDP | Yes | Yes |
| Modbus TCP (via CP or blocks) | Possible with user blocks; no certified Modbus master firmware | Yes on CP 443-1 with Modbus/TCP option (license/order variant) |
| OPC UA server | No native server firmware on CPU PN port | CP 443-1 OPC UA (6GK7443-1UX00-0XE0) provides OPC UA server |
| IP routing between subnets | Limited; CPU can act as a router but with restrictions | Yes, full IP routing with Access Control List |
| Integrated 2-port switch | Yes (on CPU) | Only CP 443-1 Advanced (6GK7443-1GX30-0XE0) and later variants |
| Gigabit uplink | No, 100 Mbit/s only | Available on 6GK7443-1EX40-0XE0 |
| Diagnostics web server | Yes (CPU web server) | Yes (CP web server, separate URL) |
| Connection-resource separation between PG/HMI and IO | No, all share the same CPU resource pool | Yes, isolation by design |
| Failure-domain separation in H-system | Lives on the CPU; a CPU fault takes the port with it | Lives on the CP; a CP fault does not take down the CPU; if both CPs are equipped, the partner CP continues serving |
The two columns are functionally similar for the standard PROFINET IO controller role. The differences become decisive for connection-resource isolation, gigabit uplinks, OPC UA, IP routing, Modbus TCP, and for separating the HMI/PG traffic from the IO traffic on a redundant network.
5. System Redundancy and the IM 155-5 PN HF
In the S7-400H the PROFINET IO field is normally built from two independent PN networks (PN1 and PN2), each connecting to a redundant IO station. The standard interface module on those stations is the IM 155-5 PN HF (6ES7155-5AA00-0AC0). The Siemens TIA Portal documentation explicitly states that when system redundancy is used, the IM 155-5 PN HF can be connected to H-CPUs with system redundancy, allowing a single IO station to be reachable from both H-CPUs simultaneously and to survive the loss of one H-CPU without reconfiguration.
From a topology perspective, two valid constructions exist:
5.1 Topology A - Integrated PROFINET only
Each H-CPU connects to one of the two PN rings. The two IM 155-5 PN HF stations of the redundant IO line are physically split: one IM is on PN1 (the integrated port of CPU A), the partner IM is on PN2 (the integrated port of CPU B). The ET 200MP station then internally couples the two IM 155-5 PN HF backplanes via the backplane bus, so the same I/O modules are visible to both H-CPUs.
This topology is valid, is documented in the IM 155-5 PN HF system-redundancy section of the ET 200MP manual, and it does not require any CP 443-1.
5.2 Topology B - Integrated PROFINET plus CP 443-1
The integrated PROFINET is dedicated to PROFINET IO (the field network). A CP 443-1 per CPU is added for HMI, PG, and external routed traffic on a separate plant network. The two CPs are configured as a redundant pair in the H-station editor; the partner CP takes over seamlessly if the active CP fails.
The redundancy model is identical: each network has two physical paths, one from each half of the H-pair. The difference is functional separation - IO traffic on the integrated ports, HMI/PG on the CPs - which is the most common production-grade pattern in S7-400H plants.
6. When the CP 443-1 Is Required
Despite the integrated PROFINET port, the following conditions make a CP 443-1 per CPU mandatory, or at least strongly recommended, in S7-400H:
- HMI/PG resource isolation. Every S7 connection, every HMI variable, and every PG routing slot consumes a connection resource. On dense HMI deployments (50+ WinCC tags/second, multiple Comfort Panels, WinCC Runtime) the CPU 414-5H connection budget can be exhausted before the IO budget is reached. Moving HMI traffic to a CP 443-1 leaves the CPU resources for IO and program execution.
- OPC UA exposure. The CPU integrated port does not run an OPC UA server in the S7-400H generation. If an OPC UA client (SCADA, MES, third-party historian) must read the PLC, a CP 443-1 OPC UA (6GK7443-1UX00-0XE0) is the only in-rack solution.
- Modbus TCP master/slave. The integrated port has no certified Modbus/TCP server stack. CP 443-1 with Modbus/TCP option supports polled and unsolicited Modbus communication with up to 64 connections per CP.
- IP routing with Access Control List. When the H-system is the gateway between the field network and the control network, the CP 443-1 (firmware V3.x and later) provides a routable interface with ACL and time-stamped diagnostics. The CPU integrated port can route but lacks the granular ACL.
- Gigabit uplink to the control network. The integrated port is 100 Mbit/s. If the plant network is gigabit (typical for video, large WinCC, or remote IO), the CP 443-1 EX40 (6GK7443-1EX40-0XE0) brings the gigabit uplink.
- Logical network separation for cybersecurity. Many plant-architecture standards (IEC 62443, ISA 99 zones and conduits) require that the HMI/SCADA network be on a separate routed segment from the IO network. A CP 443-1 is the conduit; the integrated port is the field network.
- Connection-redundancy for non-PROFINET-PROFINET paths. Although system redundancy is handled between the integrated ports and the IM 155-5 PN HF, S7-classic connections and open IE connections to a third-party system benefit from a redundant CP pair so that a single CP failure does not break the link.
7. When the CP 443-1 Is Not Required
Conversely, the following conditions allow the integrated PROFINET of the 6ES7414-5HM06-0AB0 to carry the full communication load, and the two CP 443-1 modules can be omitted from the bill of materials:
- The PROFINET IO field is the only network needed (no HMI, no SCADA uplink, no PG from outside the rack).
- PG access is local to the rack or to a single PN network segment.
- HMI is implemented as PROFINET IO panels (Comfort Panels with PN connection to the IO network), not as S7-communication clients on a separate network.
- Connection count remains inside the CPU 414-5H resource budget (verify with STEP 7 Connection Diagnostics: the warning threshold is 80% of the budget).
- No OPC UA, no Modbus TCP, no IP routing, no gigabit uplink required.
- The system-redundancy pattern with IM 155-5 PN HF (6ES7155-5AA00-0AC0) is implemented and the IO stations support S2 redundancy.
In these constrained greenfield configurations the cost saving is two CP 443-1 modules (roughly EUR 1,500 - 3,000 each, plus a slot in each rack and a SIMATIC NET manual) and the engineering effort to commission the redundant CP pair.
8. Decision Matrix
| Project Requirement | Integrated PN Only | Add CP 443-1 Pair |
|---|---|---|
| PROFINET IO only, <100 IO devices | Yes | Optional |
| PROFINET IO + S2 redundancy via IM 155-5 PN HF | Yes | Optional |
| PROFINET IO + <10 HMI clients on same network | Yes | Optional |
| PROFINET IO + 50+ HMI tags or many HMI clients | No (resource-tight) | Yes |
| OPC UA server to SCADA/MES | No | Yes (CP 443-1 OPC UA) |
| Modbus TCP to third-party devices | No | Yes |
| Gigabit plant network uplink | No | Yes (CP 443-1 EX40) |
| Routed network separation (control vs. field) | No | Yes |
| Security ACL on the uplink | No | Yes |
| Many S7 connections to other PLCs (gateway role) | Tight | Yes |
9. Configuration Steps in STEP 7 V5.x for Topology A (Integrated PROFINET only)
- Open SIMATIC Manager and load the H-station from the offline archive of the 414-5H pair.
- In HW Config, click on the H-CPU and open the PROFINET interface "PN-IO" properties. Assign an IP address and a PROFINET device name to each CPU (two independent IP subnets, e.g. 192.168.1.1 for CPU A and 192.168.2.1 for CPU B).
- Insert an ET 200MP station. In its slot 0, place the IM 155-5 PN HF (6ES7155-5AA00-0AC0). Assign it a device name in the same subnet as CPU A.
- Place a second IM 155-5 PN HF in the same ET 200MP station, on the backplane. Assign it the device name in CPU B's subnet. The two IMs together form the S2-redundancy-capable interface to the H-system.
- Configure the IO modules on the backplane. They are visible to both H-CPUs through the system-redundancy mechanism.
- Set the redundancy role of the H-CPUs (master/reserve) in the H-station editor. The CPU with the lower rack number is normally the master.
- Compile and download. Verify in NetPro that the H-system redundancy is consistent (both CPU PROFINET interfaces show the same PN IO system number, two independent subnet rows).
10. Configuration Steps for Topology B (Integrated PN + CP 443-1 Pair)
- Same as Topology A, steps 1-2, for the integrated PROFINET (field network).
- In the rack, insert a CP 443-1 (e.g. 6GK7443-1EX30-0XE0) into a free slot of each H-CPU rack. Each CP gets its own IP address in the plant network (e.g. 192.168.10.2 for CP-A, 192.168.10.3 for CP-B).
- Open the CP 443-1 properties and, in the "H-system redundancy" tab, mark both CPs as part of the H-redundant pair. STEP 7 will automatically configure the H-sync for the CP pair.
- Create the S7 connections from the WinCC server or HMI panels to the redundant CP pair. The HMI uses the MAC address of the active CP for ISO-on-TCP or the virtual IP of the redundant CP pair (defined in the CP properties).
- For OPC UA, select the CP 443-1 OPC UA (6GK7443-1UX00-0XE0) variant and enable the OPC UA server in the CP properties. Configure the security policy and the authentication certificate.
- For IP routing, enable the router function in the CP properties and add the static routes. The CP then becomes the default gateway for the H-station into the plant network.
- Compile, download, and run a connection test from WinCC to the virtual IP. Verify with the CP web server that the active CP is the expected one.
11. Verification Checklist
After commissioning either topology, perform the following verification steps:
- PROFINET IO startup. All IO stations reach the active CPU within the configured PROFINET startup time (typically 1-3 s). The partner IM 155-5 PN HF should report "standby" in the device diagnostics.
- CPU switchover test. Stop the active CPU via the H-station control panel. The reserve CPU must take over within <100 ms, IO must continue updating, HMI must not lose the S7 connection.
- CP switchover test (Topology B). Disconnect the network cable from the active CP 443-1. The partner CP must take over the plant-network connection within 1-3 s. Verify with WinCC: no "connection broken" alarm.
- Connection-resource check. Open the CPU diagnostics buffer and the CP diagnostics web page. Confirm that the number of active connections is below 80% of the configured maximum.
- Sync link health. In the H-station diagnostics, both fiber sync links must be GREEN. Any YELLOW or RED state disqualifies redundancy and must be cleared before production run.
12. Field-Proven Caveats and Edge Cases
- Connection-resource budget is global on the CPU. Every HMI variable, every PG connection, every S7 route through the CPU counts against the same 414-5H pool. The "integrated PROFINET supports HMI" statement is technically true but operationally limited.
- PROFINET device name must be unique per subnet. When you split the field network between PN1 and PN2, the two IM 155-5 PN HF stations have different device names even though they share the same backplane. The PROFINET discovery will treat them as two separate IO devices on two separate IO systems. This is by design.
- CP 443-1 firmware must match the H-system firmware window. STEP 7 will refuse to download the HW Config if the CP firmware is incompatible with the CPU firmware. Check the compatibility list in the Siemens Industry Online Support entry for the CP article number.
- Removing the CP 443-1 from an existing project. If a plant is being migrated from a CP 443-1-based design to the integrated PN, all S7 connections, all HMI tags, all routing entries must be re-pointed to the integrated PROFINET interface. This is a planned outage, not a hot edit.
- IM 155-5 PN HF redundancy role. In the device properties of the IM 155-5 PN HF, the role must be set to "IO device for system redundancy" (S2) and the partner IM must reference the same ET 200MP backplane. Misconfiguring this is a common source of "IO device not reachable on partner CPU" alarms during switchover.
- Gigabit uplink is asymmetric. If only one CP 443-1 is gigabit, the gigabit link is not redundant. Use two CP 443-1 EX40 modules to maintain redundancy at gigabit speed.
- OPC UA security policy. CP 443-1 OPC UA supports Security Policy None, Basic128Rsa15, Basic256, and Basic256Sha256 on recent firmware. Production deployments must disable None and Basic128Rsa15 per current hardening guidance.
13. Common Misconceptions
"PROFINET means all PROFINET features are present." False for the S7-400H generation. The integrated port of the CPU 414-5H PN/DP does not provide an OPC UA server, a certified Modbus/TCP stack, or gigabit. Those features live on the CP family.
"Two CPs in H-rack means double the bandwidth." False. The H-redundant CP pair shares the same logical plant network and the active CP is the single point of contact. The partner CP is a standby, not a load-balancer.
"IM 155-5 PN HF works the same in PROFINET and in S7-400H system-redundancy mode." Functionally the same module, but the configuration of the redundancy role differs. The system-redundancy configuration path is described in the Siemens TIA Portal ET 200MP manual collection, system redundancy on S7-400H section.
14. Cost and Engineering Trade-Off Summary
| Aspect | Integrated PROFINET Only | Integrated PROFINET + CP 443-1 Pair |
|---|---|---|
| Hardware cost per rack | Lower (no CP 443-1) | Higher (2 x CP 443-1 + slots) |
| Engineering effort | Lower (single network) | Higher (two networks, redundancy pairing) |
| Connection-resource headroom | Tight on HMI-heavy projects | Generous |
| Cybersecurity (zoning, ACL) | Limited | Strong |
| OPC UA / Modbus TCP / gigabit | Not supported | Supported |
| Switchover isolation for HMI | Tied to CPU switchover | Independent CP switchover available |
| Future scalability | Limited by CPU 414-5H connection budget | CP 443-1 resources can be expanded independently |
15. Recommendation
For a greenfield S7-400H with the CPU 414-5H PN/DP (6ES7414-5HM06-0AB0), start the design with the integrated PROFINET for the PROFINET IO field and the IM 155-5 PN HF for the redundant IO stations. Add the CP 443-1 pair as soon as any of the following is true: more than 10 HMI clients, an OPC UA requirement, a Modbus TCP requirement, a gigabit plant network, or a cybersecurity mandate for routed network separation. The CP 443-1 is not redundant in the sense of load-sharing; it is redundant in the sense that the plant network remains reachable when either half of the H-pair is unavailable.
For brownfield migrations, retain the existing CP 443-1 pair and consider it part of the H-system's external contract with the HMI/SCADA. Do not remove the CP 443-1 from an existing project without a planned outage and a full re-pointing of every HMI connection.
Do I have to install a CP 443-1 in every S7-400H rack with a CPU 414-5H PN/DP (6ES7414-5HM06-0AB0)?
No. If the only network required is the PROFINET IO field, the integrated PROFINET port of the CPU 414-5H PN/DP is functionally sufficient and the CP 443-1 pair can be omitted. A CP 443-1 pair becomes mandatory when HMI/SCADA, OPC UA, Modbus TCP, gigabit uplinks, or routed network separation are required.
What is the article number of the redundant PROFINET interface module for ET 200MP in an S7-400H system-redundancy setup?
The standard interface module for S7-400H system redundancy is the IM 155-5 PN HF, article number 6ES7155-5AA00-0AC0. It connects to H-CPUs with system redundancy so a single ET 200MP station is reachable from both halves of the H-pair.
Can the integrated PROFINET port of the CPU 414-5H replace the CP 443-1 for HMI communication?
For small HMI counts (typically below 10 clients with light tag loads), yes. Beyond that, the CPU 414-5H connection-resource budget is exhausted and the HMI traffic should be moved to a CP 443-1 to keep the CPU resources free for PROFINET IO and the user program.
Does the CP 443-1 provide OPC UA on the S7-400H?
Only the CP 443-1 OPC UA variant, 6GK7443-1UX00-0XE0, exposes an OPC UA server. The standard CP 443-1 (6GK7443-1EX30-0XE0 or EX40) and the CPU integrated port do not run an OPC UA server in this generation.
How do the two CP 443-1 modules in an S7-400H achieve redundancy?
They are configured in HW Config as a redundant H-CP pair using the H-station editor. One CP is active on the plant network, the other is standby. On a CP or CPU failure the partner CP takes over the S7 connections and the HMI/SCADA loses no data beyond a short switchover (typically 1-3 s).
Is the integrated PROFINET on the CPU 414-5H gigabit?
No. The integrated PROFINET of the CPU 414-5H PN/DP is a 100 Mbit/s, two-port managed switch. For gigabit uplink to the plant network, install the CP 443-1 EX40 (6GK7443-1EX40-0XE0) in each rack.