Adding IP Addresses to Existing S7-400 Controllers Without CPU Stop in PCS 7

In SIMATIC PCS 7, adding or modifying an IP address on an existing S7-400 controller or Communications Processor (CP 443-1) that is currently configured with only an ISO MAC address cannot be executed without placing the automation controller into STOP mode. In standalone S7-400 and CPU 410 systems, Ethernet interface parameter modifications in STEP 7 HW Config are non-CiR (Configuration in RUN) compatible, requiring a full hardware configuration download. In fault-tolerant redundant S7-400H or CPU 410-5H architectures, network address re-assignment can be accomplished bumplessly without plant shutdown by performing a staged, redundant H-system sequence (stopping Standby CPU, downloading, warm restarting, and syncing).

ISO Transport (MAC) vs TCP/IP Protocol Architecture in PCS 7

In early SIMATIC PCS 7 releases (such as V5.x and V6.x), the Plant Bus (Industrial Ethernet) frequently utilized the ISO Transport protocol. Under pure ISO transport, controllers and OS servers communicated strictly via layer-2 MAC addresses without IP addresses or subnet masks. This provided high-speed deterministic messaging immune to IP routing conflicts.

As modern automation migrated toward routed terminal buses, OpenPCS 7, central Process Historians, and corporate network integration, operating with TCP/IP became mandatory. Control engineers managing operational facilities often encounter controllers configured purely with MAC addresses and need to activate IP communications without disrupting continuous plant operations.

Why Network Parameter Changes Require CPU Stop in Standard AS

In standard non-redundant S7-400 controllers (e.g., CPU 414-3, CPU 416-3, or standalone CPU 410-5H), adding an IP protocol stack or binding an IP address to an active CP 443-1 interface fundamentally alters the controller's communication stack:

Communication Buffer Reallocation: Activating TCP/IP allocates internal memory buffers for IP routing, ARP tables, and socket listeners in the CP or CPU operating system.
Non-CiR Parameter: Configuration in RUN (CiR) permits adding decentralized I/O racks (ET 200M/SP) to fieldbus networks while the CPU runs. However, modifying network interface parameters on the controller's primary Industrial Ethernet port is not supported by CiR. HW Config explicitly forces a CPU STOP to download interface modifications.

CiR Constraints on Ethernet Interface Reconfiguration

Understanding CiR capabilities clarifies why online modifications fail:

Allowed CiR Operations: Adding new slave modules to existing PROFIBUS DP or PROFINET lines, adding new I/O channels, and re-parameterizing analog input ranges.
Blocked CiR Operations: Changing CPU hardware properties, altering bus clock rates, modifying controller memory allocations, and changing IP or MAC network configurations on integrated or rack-mounted communication processors.

Comparison of Network Migration Procedures across AS Topologies

The table below details CPU operating state requirements when assigning IP addresses across different PCS 7 architectures.

Automation System ArchitectureTarget Hardware InterfaceCiR Supported?Controller State RequiredOperational Plant ImpactStandalone S7-400 (Single AS)Integrated PN/IE PortNoCPU STOP RequiredPlant Outage: Full controller shutdownStandalone S7-400 (Single AS)External CP 443-1NoCPU STOP RequiredPlant Outage: Communication severedRedundant S7-400H / CPU 410-5HIntegrated PN/IE PortSupported via H-CiRStaged Redundant SwitchoverBUMPLESS: Continuous process controlRedundant S7-400HDual CP 443-1 ModulesSupported via H-CiRStaged Redundant SwitchoverBUMPLESS: Continuous process control

Step-by-Step Procedure to Add IP Address in Redundant S7-400H

In fault-tolerant redundant systems (S7-400H or CPU 410-5H), assign IP addresses bumplessly using the staged H-switchover procedure:

Modify Hardware Configuration in STEP 7:
- In HW Config, double-click the PN/IE interface or CP 443-1 of Subsystem 0 (Master CPU).
- Check 'Set IP protocol / Use IP address'. Enter the designated IP address and subnet mask.
- Repeat the exact parameterization for Subsystem 1 (Standby CPU) with its unique IP address.
- Save and compile HW Config.
Transition Standby Subsystem to STOP:
- Open SIMATIC Manager: verify that the H-system is in redundant state (Redundant LED on).
- Switch Subsystem 1 (Standby CPU) to STOP via the physical key switch or SIMATIC Manager.
- Master CPU continues controlling the plant without interruption.
Download HW Config to Standby CPU:
- In HW Config, select PLC -> Download to Module.
- Target the Standby CPU. Transfer the updated hardware configuration.
Restart and Synchronize Standby Subsystem:
- Switch the Standby CPU key switch back to RUN.
- The Standby CPU executes a memory reset, links up, and completes a bumpless synchronization with the Master CPU.
Execute Redundancy Switchover and Update Master:
- In SIMATIC Manager, execute an operating mode switchover: transition Subsystem 0 to Standby and make Subsystem 1 the active Master.
- Stop Subsystem 0, download HW Config, restart Subsystem 0, and restore full dual redundancy.

Verification

Verify network address assignment through the following operational tests:
1. Open Command Prompt on the Engineering Station: execute ping [New_IP_Address] to verify instant network response.
2. In NetPro online view, verify that the S7-400 communication processor displays healthy status with active IP sockets.
3. Verify that existing ISO MAC connections remain active during the IP transition.
4. Check the CPU diagnostic buffer: verify that no communication buffer overruns or synchronization faults are recorded.

Limitations and Operational Precautions

For single-CPU automation systems, do not attempt to bypass the CPU STOP requirement using third-party network tools or dynamic IP assignment utilities (e.g., Primary Setup Tool) while the CPU is executing logic. Doing so desynchronizes STEP 7 offline database checksums from the online controller, preventing future delta downloads and risking CPU memory corruptions.

Engineer FAQ

Can I use Primary Setup Tool (PST) to assign an IP address online?

PST can assign temporary IP parameters to a blank CP in STOP mode, but in PCS 7, any IP assigned outside STEP 7 HW Config causes a configuration mismatch and will be overwritten on the next hardware download.

Why did older PCS 7 systems use MAC addresses instead of IP addresses?

ISO Transport (MAC-based) provided faster cyclic communication, eliminated IP address conflicts, and required no subnet routing configuration on dedicated industrial plant buses.

Does changing an IP address break existing WinCC Named Connections?

If the S7 Named Connection in NetPro was configured using ISO protocol, adding an IP address does not break it. However, if the connection is migrated to TCP/IP, NetPro connections must be recompiled and downloaded to the OS.