S7-400 CPU Stays in STOP After Power Cycle: Causes and Fix

David Krause14 min read
S7-400SiemensTroubleshooting
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

1. Problem Statement: S7-400 CPU Returns to STOP After Power Restoration

The reported failure mode: a SIMATIC S7-400 CPU 414-2 (order number 6ES7414-2XK05-0AB0) is running in RUN mode. The 24 V DC system supply is removed. When the supply is re-applied, the CPU goes through its power-on sequence and ends up in STOP rather than RUN. The mode selector remains in the RUN position, no SF (group fault) LED is lit, and the diagnostic buffer shows no programming or I/O error. The operator must toggle the mode selector from RUN to STOP and back to RUN to bring the program back online. No fault is reported by the user program; the program simply does not resume on power-on.

This symptom is characteristic of a CPU that cannot perform a warm restart (Wiederanlauf) on power restoration and is forced into a complete restart / cold restart (Kaltstart, Neuanlauf). The most frequent cause in field service is a missing, exhausted, or loose backup battery. The case in the source thread was resolved by reseating the battery, not by replacing it.

Safety: Replacing the backup battery in an S7-400 should be performed with the PLC powered up if at all possible, within the buffer time window. The buffer time is typically several weeks for a healthy battery. Always observe ESD precautions and the safety instructions in the S7-400 installation manual.

2. Affected Hardware and Catalog Identification

The reported configuration uses a standard S7-400 mid-range CPU with a flash memory card. Confirm the exact catalog number from the front-panel label and the firmware version in the diagnostic buffer before ordering spares. The family of order numbers below the "-0AB0" suffix and the "-XK05" mark are decoded in the SIMATIC S7-400 S7-400 Automation System, CPU Specifications manual.

Component Order Number Key Specs
CPU 414-2 6ES7414-2XK05-0AB0 Firmware V5.x; 1.4 MB work memory (code + data); 0.7 MB retentive; MPI/DP interface; 1 slot for memory card; 8 KB bit memory, 2 KB S7 timers / counters
Flash EPROM card (16 MB) 6ES7952-0KH00-0AA0 Non-volatile load memory expansion; 5 V; 16 MB; suitable for all S7-400 CPUs
Power supply (typical) 6ES7405-0KA02-0AA0 (PS 405 4 A) or 6ES7407-0KA02-0AA0 (PS 407 10 A) 24 V DC in; 5 V / 24 V DC out to backplane; battery backup integration
Backup battery 6ES7971-0BA00 (PS-battery, D-size) or 6ES7971-1AA00-0AA0 (CPU-battery, 2 × AA) Lithium 3.6 V; service life 1-3 years at 25 °C

For full mechanical, electrical, and ordering data, refer to the S7-400 CPU Specifications manual on the Siemens Industry Online Support portal.

3. Root Cause: Loss of Retentive Backup

The S7-400 CPU preserves a portion of its state across a power loss through a lithium backup battery. The battery powers an SRAM area that holds:

  • Retentive bit memory (M, MB, MW, MD, and the first 16 bytes of MB0..MB15 by default)
  • Retentive S7 timers (T) and counters (C) declared as retentive in the configuration
  • Retentive instances of FBs declared with the "non-retain" attribute disabled
  • The last operating mode and the "last transition" status (RUN -> STOP, RUN -> power-fail)

If the battery is missing, exhausted, or has a poor contact, the CPU loses all of the above on power-down. On the next power-on the firmware detects the missing data and refuses to perform a warm restart. It executes a complete restart (cold restart) and stops at the end of OB 102 initialization, awaiting operator acknowledgement.

The flash memory card (6ES7952-0KH00-0AA0) keeps the project itself safe (blocks, hardware configuration, symbols) but does not retain runtime values. A flash card is therefore necessary but never sufficient to recover RUN mode automatically. This is the most common misconception in field service.

24 V DC restoredBattery present and OK?Warm restartCold restartAuto -> RUNAuto -> RUNManual -> STOPYesNo

4. S7-400 Startup Modes

The S7-400 distinguishes three startup types. The selection depends on backup state and STEP 7 / TIA Portal hardware configuration. Compare the table below with the S7-400 CPU Specifications manual for the exact behavior of your firmware version.

Startup Mode German term Pre-condition OB called Behavior on Power-On
Warm restart Wiederanlauf Battery serviceable, work memory contents valid OB 101 Retentive data preserved, program returns to RUN automatically if configured
Cold restart (complete restart) Kaltstart / Neuanlauf Battery missing or invalid, or forced by configuration OB 102 All work memory cleared (except default-retentive MB0..MB15), CPU goes to STOP by default
Hot restart — (S7-300 only) — OB 100 (S7-300) Not supported on S7-400

The relevant STEP 7 / TIA Portal setting is in the CPU properties, Startup tab. The radio options are:

  1. Warm restart - manual: After power-on, the CPU enters STOP and waits for the operator to toggle the mode switch to RUN. Requires a healthy battery.
  2. Warm restart - automatic: After power-on, the CPU executes OB 101 and transitions to RUN without operator action. Requires a healthy battery.
  3. Complete restart - manual / automatic: Same as above, but the warm restart is replaced with a cold restart (OB 102). This option is the only auto-run fallback when the battery is exhausted.

Default in STEP 7 and TIA Portal for new S7-400 projects is "Warm restart - manual". This is the most common reason why a healthy, recently-installed CPU still requires a manual mode-switch toggle after a power cycle.

5. Memory Card Function in the S7-400 Power-On Sequence

Every S7-400 CPU exposes a slot for a memory card on the front panel. The card acts as an extension of the load memory and is the only non-volatile program storage on the CPU. Detailed information is published in the Siemens TIA Portal help:

What you should know about memory cards for S7-400

Key points for the auto-run question:

  • The flash card preserves the project (blocks, symbols, HW configuration) across power-off and battery loss. Without a card, the project is lost when the battery is exhausted; the card is therefore mandatory for unattended sites.
  • The card does not retain the work memory, the last operating mode, or any runtime values. It does not, by itself, enable warm restart.
  • When the card is present and the battery is healthy, the power-on sequence copies project blocks from the card into the work memory, checks their CRC, then triggers the configured startup type.
  • Three card types exist: RAM (volatile, battery-backed, allows online editing), FLASH (non-volatile, cannot be edited online), and EPROM (non-volatile, programmed externally with a Prommer). FLASH is the most common choice for production CPUs and the one used in the reported case.
  • The card type is detected automatically. Inserting a FLASH card over an existing RAM card requires a manual reload of the project to update the on-card content.
Do not confuse the memory card slot with the backup battery holder. They are physically separated on the CPU. The card slot is on the front panel, the battery holder is behind the front cover, usually on the lower part of the CPU or on the PS module.

6. Battery Backup System and Service Life

The backup battery is the deciding component. The typical part numbers for an S7-400 rack are listed below. Always order by the exact order number printed on the existing cell or on the parts list in the CPU manual.

Use Order Number Cell Type Nominal Voltage Service Life
PS 405 / PS 407 backup 6ES7971-0BA00 1 × D-size lithium 3.6 V ~1-2 years at 25 °C ambient
CPU backup (no PS battery) 6ES7971-1AA00-0AA0 2 × AA-size lithium 2 × 3.6 V ~2-3 years at 25 °C

Service life is shortened by:

  • High ambient temperature (derate by ~50% per 10 °C above 25 °C)
  • Long storage time of the CPU before commissioning (battery discharges even with the CPU off)
  • Repeated deep discharge (long power-off periods without a PS battery)
  • Loose contact in the holder (intermittent high-resistance path)

The CPU monitors the battery voltage and writes a warning event into the diagnostic buffer when the voltage drops below ~2.7 V. The BATF LED on the front panel lights up. After this warning, the user has typically a few weeks of buffer time before the CPU drops the work memory.

A loose battery contact in the holder produces the same effect as a missing battery: the BATF LED may still light, but the voltage check can be intermittent and the diagnostic buffer may not show a clear "battery exhausted" event. Always verify the spring tension of the battery contacts and the orientation of the cell before replacing the battery outright. The case in the source thread was resolved by reseating the cell, not by replacing it.

7. Mode Switch Behavior

The S7-400 mode selector is a 4-position key switch on the front panel. The positions and their effect on startup are:

Position Function Effect on Power-On
RUN Operating mode, program changes blocked Startup as configured
RUN-P Operating mode, program changes allowed Startup as configured
STOP CPU stopped, no program execution CPU remains in STOP
MRES Memory reset CPU performs a full memory reset, requires operator confirmation

For automatic restart, the switch must be in RUN or RUN-P. If the switch is in STOP or MRES at the moment of power restoration, the CPU will not enter RUN automatically regardless of the configuration. Confirm the switch position as the first step in any "no auto-run" troubleshooting case.

8. Reading the Diagnostic Buffer for Confirmation

Before touching the hardware, read the CPU diagnostic buffer online. This is the most reliable confirmation that the root cause is the battery and not, for example, an I/O fault during startup, a missing hardware configuration, or a programming error.

Procedure with STEP 7 V5.x:

  1. Open SIMATIC Manager and the project.
  2. Select the CPU in the project tree.
  3. PLC > Online > Accessible Nodes (or use the established online connection).
  4. PLC > Diagnostics / Setting > Diagnostic Buffer.
  5. Inspect the most recent entries, in particular the events around the last power-on.

Procedure with TIA Portal V16 and later:

  1. Open the project, select the S7-400 device.
  2. Click Go online and accept the online connection.
  3. In the project tree, Online & diagnostics > Diagnostic buffer.
  4. Filter for "Power" or "Battery" events.

Common event IDs to look for:

Event ID (hex) Meaning Interpretation
0x4300 Power ON CPU just powered up
0x4301 Power OFF 24 V DC removed
0x4310 Warm restart performed Battery and configuration OK; healthy warm restart
0x4311 Complete restart / cold restart Retentive data lost; usually battery-related
0x4380 Battery exhausted / failure Direct confirmation of root cause
0x4390 Battery low warning Replace the cell soon
0x4308 STOP caused by startup problem CPU cannot complete startup; check the next event for the underlying cause

A pattern of 0x4311 (Cold restart) -> 0x4308 (STOP) -> 0x4300 (Power ON) across several power cycles is the smoking gun for the battery fault. If the diagnostic buffer is empty, the CPU is unable to enter operational state at all; the cause is more likely a missing or corrupted memory card.

9. Step-by-Step Resolution

The reported case was resolved by reseating the battery, not by replacing it. Follow the procedure below, which combines inspection, reseating, reconfiguration, and verification.

Step 1: Capture the current state

Connect to the CPU online, download the diagnostic buffer, and export the hardware configuration. Note the BATF LED state, the mode switch position, and the firmware version.

Step 2: Open the front cover and locate the battery holder

Power the PLC down (or, on S7-400, perform the battery swap with the power on, within the buffer time window). Open the front cover. The battery holder is typically at the bottom of the CPU or on the PS module, in a slot labelled "BATT".

Step 3: Inspect the holder

  • Check the spring contacts for oxidation, deformation, or loss of tension.
  • Check the orientation of the cell: the polarity is marked on the holder and the cell.
  • Check the connector cable to the PS / CPU board; on some PS types the battery is wired to the PS, not the CPU.

Step 4: Reseat the cell

Remove the cell, clean the contacts with a dry eraser or isopropyl alcohol, and reinstall it. Confirm the cell snaps into the holder. This step alone resolved the original case in the source thread.

Step 5: Replace if voltage is low

Measure the cell voltage under load (use a 100 Ω resistor in parallel to simulate the CPU drain). A healthy cell reads > 3.4 V. Below 3.0 V the cell is exhausted and must be replaced. Use only the approved Siemens types listed in section 6.

Step 6: Power on and verify

Apply 24 V DC. Watch the CPU LEDs in this order:

  1. SF / BF off (no fault)
  2. DC5V on (backplane powered)
  3. FRCE on if forced jobs are active
  4. RUN on within a few seconds

If the CPU now goes to RUN automatically after power-on, the problem is solved. Re-check the diagnostic buffer; a "Warm restart" event should be present at the top.

10. Enabling Automatic Restart in STEP 7 / TIA Portal

If the battery is healthy but the CPU still requires operator intervention, the cause is the STEP 7 startup configuration.

STEP 7 V5.x

  1. HW Config > open the CPU properties > Startup tab.
  2. Set Startup on power on: Warm restart - automatic (battery must be serviceable).
  3. Alternatively, set Complete restart - automatic if you need a guaranteed cold start on every power-on.
  4. Save, download, and perform a STOP-to-RUN transition to make the new settings active.

TIA Portal V16+

  1. Project tree > Devices & networks > select the CPU.
  2. Properties > Startup.
  3. Set the same Startup on power on drop-down.
  4. Compile and download.
The "automatic" option does not override the BATF LED or the diagnostic buffer. If the battery fails after the project download, the CPU will still fall back to a manual cold restart, regardless of the configuration.

11. Verification Procedure

After the fix, perform at least three cold power cycles to confirm the result. Document each cycle in the maintenance log.

  1. Cycle 1: Power off for 10 s, power on. CPU should reach RUN within 5 s.
  2. Cycle 2: Power off for 60 s, power on. Same behavior.
  3. Cycle 3: Power off for 5 min, power on. Same behavior.

For each cycle, capture the diagnostic buffer and confirm a 0x4310 Warm restart event. If a 0x4311 Cold restart re-appears, the battery is marginal even though it measures > 3.0 V on the bench. Replace it.

Optional acceptance test: force a retentive bit (M 100.0) to TRUE, perform a power cycle, and verify that M 100.0 is still TRUE in the online watch table. This confirms that the warm restart is preserving retentive memory.

12. Preventive Maintenance and Best Practices

  • Replace S7-400 backup batteries every 24 months as a preventive measure, regardless of the BATF LED state.
  • Mark the battery installation date on the cell with a permanent marker.
  • Keep at least one spare cell per CPU on the cabinet shelf.
  • For unmanned sites, configure a battery-low alarm via the OB 81 (I/O fault) or via a CP 443-1 email / SMS push.
  • Use the optional 2-cell holder (e.g. 6ES7971-1AA00-0AA0) for redundant battery capacity where supported.
  • Always pair any battery change with a diagnostic buffer download for the maintenance record.
  • Avoid mixing old and new cells in multi-cell holders; replace both at the same time.
  • Verify the mode switch position in the maintenance log to prevent accidental STOP position during power-on.

13. Related S7-400 CPU Models

The same root cause and remediation apply to the entire S7-400 mid-range and high-range CPU family. The catalog numbers differ but the diagnostic events and the battery slot location are consistent.

CPU Order Number Work Memory Retentive
CPU 412-1 6ES7412-1XK05-0AB0 0.5 MB 0.25 MB
CPU 412-2 6ES7412-2XK05-0AB0 0.5 MB 0.25 MB
CPU 414-2 6ES7414-2XK05-0AB0 1.4 MB 0.7 MB
CPU 414-3 6ES7414-3XK05-0AB0 2.8 MB 1.4 MB
CPU 416-2 6ES7416-2XK05-0AB0 5.6 MB 2.8 MB
CPU 416-3 6ES7416-3XK05-0AB0 11.2 MB 5.6 MB
CPU 417-4 6ES7417-4XK05-0AB0 30 MB 15 MB

14. Frequently Asked Questions

Why does the S7-400 CPU go to STOP after a power cycle even though the flash card is installed?

The flash card (e.g. 6ES7952-0KH00-0AA0) keeps the project safe but does not retain the work memory or the last operating mode. If the backup battery is dead or loose, the CPU performs a cold restart and the default configuration requires operator acknowledgement. The flash card is necessary but not sufficient; the backup battery is the deciding component.

How do I distinguish a warm restart from a cold restart in the diagnostic buffer?

Read the diagnostic buffer online in STEP 7 or TIA Portal. A warm restart appears as event ID 0x4310, a cold restart as 0x4311. A sequence of 0x4311 events across multiple power cycles is a strong indicator of a battery problem.

Can I configure the S7-400 to go to RUN automatically even without a battery?

Yes. In the CPU properties, set the Startup on power on option to Complete restart (cold restart) - automatic. The CPU will then execute OB 102 and transition to RUN without operator action. Note that all work memory is cleared on each power-on, and you lose retentive data protection.

Which battery fits a CPU 414-2XK05-0AB0?

The PS 405 / PS 407 typically uses a single D-size 3.6 V lithium cell (order number 6ES7971-0BA00). Some configurations use a 2-cell AA holder (6ES7971-1AA00-0AA0) on the CPU. Refer to the CPU and PS manuals for the exact assignment in your rack.

Does the S7-400 support a hot restart like S7-300?

No. The S7-400 family only supports warm restart and complete restart. S7-300 supports a hot restart via OB 100; S7-400 does not have an equivalent. The closest S7-400 construct is OB 101 (warm restart) and OB 102 (cold restart).

Back to blog