Replacing S7-400 CPU 414-3 with 416-3: Compatibility & Procedure

Replacing an S7-400 CPU 414-3 with a 416-3 Spare in TIA Portal V16

1. Overview

The SIMATIC S7-400 family groups rack-mounted CPUs by performance class. Within the same generation, a higher-class CPU (416-3) can physically and logically replace a lower-class CPU (414-3) provided that:

• Both CPUs share the same firmware generation (V6 / V7 family).
• The application footprint (memory, blocks, connections, I/O count) fits within the smaller CPU's limits.
• The engineering tool supports both catalog numbers.
• Interface slot assignments and module count stay within the rack topology.

When these constraints hold, TIA Portal's Change Device function rebuilds the hardware configuration against the new CPU while keeping all program blocks, symbols, and connection data intact.

2. Prerequisites

1. Project backup: Archive the STEP 7 / TIA Portal project before any modification (Project → Archive).
2. Engineering tool: TIA Portal V16 (or newer) must have both CPU 414-3 and CPU 416-3 hardware support packages (HSP) installed. Confirm via Options → Hardware Catalog. See the TIA Portal V16 Installation and Maintenance guide.
3. Document the existing CPU's MLFB (order number) and firmware version from the module's front labeling or via Online → Accessible Nodes → Diagnostics.
4. Identify spare CPU MLFB and firmware version; physically confirm the spare is a 416-3 (third-generation interface variant) and not a 416-2 or 416F.
5. Capture the slot assignment of every signal module, FM, CP, and IM in the rack. Photograph the rack with module order and slot addresses visible.
6. Export the existing hardware configuration: Device → Export HW configuration or note the system data blocks.

3. CPU 414-3 vs 416-3 Specification Comparison

The following table compares the S7-400 CPUs typically encountered in the field. Always verify against the current S7-400 Automation System Manual, since firmware revisons V6 and V7 have different memory layouts.

4. Compatibility Constraints

Replacing a 414-3 with a 416-3 is treated by TIA Portal as an online-change-compatible swap only when the following hold true. If any check fails, a full re-download is required.

4.1 Firmware Generation

Both CPUs must run firmware from the same major generation. Common allowed combinations:

• 414-3 V6.x ↔ 416-3 V6.x
• 414-3 V7.x ↔ 416-3 V7.x
• Mixing V6 firmware into a V7 program (or vice versa) is rejected by the loader with diagnostic buffer entry "Firmware version of module is not compatible".

4.2 Interface Slot Compatibility

The "-3" suffix indicates the interface plug arrangement. Confirm the PN/DP slot assignment maps 1:1:

• Slot X1 (IF1): MPI / PROFIBUS DP master
• Slot X2 (IF2): PROFIBUS DP master or DP slave
• Slot X3 (IF3): PROFINET interface (model dependent)

If your application uses PROFINET on IF3 of the 414-3, ensure the 416-3 also exposes PROFINET on IF3. Older 416-3 variants without PROFINET are labeled 416-2 and cannot substitute for a 416-3 PROFINET user.

4.3 Application Footprint

Even though 416-3 has more headroom, do not assume the program automatically scales. Verify:

• Total work memory used ≤ 416-3 capacity (TIA: PLC → Resources → Memory usage).
• Maximum cycle time stays within the smaller CPU's budget; if your cycle was marginal on the 414-3, it will improve on the 416-3 but check the OB1 scan time after swap.
• Number of active S7 connections ≤ 96 (limit of 416-3).
• All used OBs, FBs, FCs, and SFBs exist in the 416-3 instruction set (the 416-3 supports the full S7-400 instruction set).

4.4 Safety-Conscious Applications

If the 414-3 is the F-variant (414F-3, 6ES7414-3FM05-0AB0) used in a Failsafe program, do not substitute a standard 416-3. Use only a 416F-3 (6ES7416-3FR05-0AB0 or 6ES7416-3XR05-0AB0). Mixing failsafe and standard CPUs in an F-runtime group produces diagnostic buffer entry "F-capability mismatch" and the CPU refuses RUN.

5. Pre-Replacement Engineering Checks

1. Read the diagnostic buffer of the failing CPU (Online → Online & Diagnostics → Diagnostic buffer) and document the fault that triggered the swap. This protects warranty/RMA claims.
2. Compare PLC tags and DB instances: confirm that the project does not rely on retained tags whose retention address differs between 414-3 and 416-3. Retain area is generally compatible, but verify in PLC → Properties → Retentive Memory.
3. Check DP slave and PN device names: the device name assigned to PROFINET devices is stored in the CPU. Swapping CPUs without exporting/re-importing the topology will leave PN devices unnamed. In TIA Portal: Devices & Networks → PROFINET interface → PROFINET device name.
4. Confirm CP and FM firmwares: any CP443-1 / CP443-5 / FM458 in the rack has its own firmware; these are independent of the CPU swap and need no change.

6. TIA Portal V16 Replacement Procedure (Step-by-Step)

When two plants run different CPU variants but only one spare exists, the engineering change can be made offline (in the engineering office) and then transferred to the spare before the physical swap. This is the recommended workflow.

Step 1 — Open the project

Open TIA Portal V16 and load the 414-3 project. Confirm the project opens without HW catalog warnings.

Step 2 — Change device

1. In the project tree, expand Devices & Networks → [Plant PLC].
2. Double-click Device configuration.
3. Right-click the CPU 414-3 slot in the rack view.
4. Select Change device → SIMATIC S7-400 → CPU 416-3 → [matching MLFB].

TIA Portal validates compatibility. If the validation fails, the tool reports the specific parameter (for example: "Maximum number of S7 timers exceeded") in the Inspector window. Resolve before continuing.

Step 3 — Compile and review

1. Right-click the device → Compile → Hardware and software (rebuild all blocks).
2. Inspect the Info / Compile output. Look for warnings of type "Interface of block differs between old and new CPU".
3. Confirm the program structure is intact: open Program blocks → System blocks → SFB / SFC and verify no entries are flagged red.

Step 4 — Export configuration for the spare

The spare 416-3 must receive the device name and IP. From the project tree:

• Right-click the PLC → Export device assignment → save as .bin or .dat file on a USB stick or SD card.
• Insert the SD card into the spare 416-3 before powering up the rack.

Step 5 — Bring the spare CPU online and transfer

1. Mount the spare 416-3 into a programming rack (or the target rack with power off).
2. Connect the engineering PG to the spare via MPI/PROFIBUS.
3. Download the rebuilt project: Online → Download to device → Configure PG/PC interface → Slot = CPU.
4. Tick Reset PROFIBUS / PROFINET configuration if you need PN device names reassigned.

Step 6 — Verify before field swap

• Check Online → Online & Diagnostics → Diagnostic buffer for the entry "Module restart (cold start)" and no faults.
• Force-check critical tags in monitor mode.
• Cycle through STOP ↔ RUN transitions to confirm the project runs cleanly.

7. Hardware Swap Procedure (Field)

1. Isolate the plant section per lockout-tagout (LOTO) rules. Bring the controlled process to a safe state.
2. Place the CPU in STOP via the mode selector.
3. Remove the memory card (MMC or RAM) from the failed 414-3.
4. Power down the rack. Wait at least 5 seconds for the PS407 power supply to discharge.
5. Loosen the four captive screws and lift the 414-3 out. Note the slot keying.
6. Insert the prepared 416-3. Press firmly; confirm the front connector seats.
7. Restore rack power. Observe the CPU's LED pattern: STOP (yellow steady), RUN (green steady), SF / BF / BUSF should all be off.
8. Flip the mode selector from STOP → RUN. The CPU performs a cold restart if no retentive data is required, or a warm restart if retain memory was preserved on the MMC.

7.1 SD Card Handling

The S7-400 uses a 5 V Flash card or 5 V RAM card. The card from the 414-3 is hardware-compatible with the 416-3 (both use the same slot). However, the card contains the device name and PROFINET topology, so:

• If the SD card came from the failed 414-3 and is intact, transferring it to the 416-3 typically preserves PROFINET device names.
• Re-import the topology from TIA Portal regardless to verify I/O names: Devices & Networks → PROFINET → Topology editor.

8. Commissioning and Verification

After the field swap, run a structured verification sweep:

9. STEP 7 Classic (V5.x) Equivalent Procedure

If the original project lives in STEP 7 V5.6 (Classic) rather than TIA, the procedure is the same conceptually but the UI differs:

1. Open SIMATIC Manager and the S7 program.
2. Open HW Config.
3. Double-click the CPU 414-3 slot. In the Properties → General tab, click Change CPU or use the Catalog → SIMATIC 400 → CPU 416-3 drag-drop.
4. Save and compile (Station → Save and Compile).
5. Download the new system data (PLC → Download → All) to the spare CPU after physical swap.

Reference: S7-400 Automation System Manual, chapter "Replacing and Removing Modules".

10. Troubleshooting Matrix

11. Field-Proven Caveats

• Always keep a labeled spare SD card per plant, formatted on the same firmware generation as the operating CPU.
• Document the firmware version of every CPU in the cabinet; a 414-3 V6.0.4 and a 416-3 V7.0 cannot share a project.
• The "-3" interface layout differs between MLFB variants within the 416-3 family (e.g., 6ES7416-3ES06 vs 6ES7416-3XR05). Match the catalog number, not just the model string.
• If the application uses OPC UA server via the PN interface, the 416-3 PN firmware must include the OPC UA activation; older 416-3X (V6.x) firmware does not run the OPC UA server.
• Time stamping and isochronous mode require matching firmware between CPU and the affected FM/CP; verify with the S7-400 manual if you use these features.

12. Document Your Swap

After every successful swap, record in the plant maintenance log:

• Failed CPU MLFB and firmware
• Spare CPU MLFB and firmware
• Project revision (TIA Portal archive hash)
• Diagnostic buffer pre-swap (exported)
• Diagnostic buffer post-swap (clean)
• Date, time, operator, and engineer signatures

This record supports root-cause analysis if the same rack faults again later.