Troubleshooting S7-400 CPU 412-2DP All LEDs Blinking Fault

Troubleshooting the S7-400 CPU 412-2DP (6ES7412-2XG04-0AB0) "All LEDs Blinking" Fault

The CPU 412-2DP (Siemens catalog number 6ES7412-2XG04-0AB0) is a mid-range processor in the SIMATIC S7-400 family, widely deployed in press automation, metal-forming lines, and continuous-process machinery. When every front-panel LED begins to flash in unison and the engineering station (ES) cannot establish an online connection—even after STOP/RUN toggling—the CPU has entered an unrecoverable internal state. The two most common root causes are corrupted firmware in the internal flash and a defective or absent memory card. This reference walks through the full field-proven recovery procedure, the hardware prerequisites, and the checks you must complete before returning a press to production.

1. Affected Hardware and Order Numbers

The CPU 412-2DP V4.1 (released approximately 2004) is no longer in active production but is still maintained in the Siemens SIMATIC Customer Support portal. The hardware (HG) version carries an integrated 1 MB load memory and 256 KB work memory, expandable through the slot for a memory card.

2. Interpreting the LED Pattern

The CPU 412-2DP front panel carries the following indicators:

When all eight LEDs blink in unison at approximately 2 Hz, the CPU has detected an internal fatal firmware error (defective internal flash, checksum mismatch, or a partial bootloader). In this state, the operating system cannot initialize the PROFIBUS interfaces, cannot load OB1, and rejects all MPI/TCP routing requests from STEP 7. Online access is impossible until the firmware image is restored.

3. Root-Cause Analysis

From field data on CPU 412-2DP installations in press lines, the all-LEDs-blinking fault has three dominant root causes and several contributors. Each must be ruled out in the order shown before a firmware update is attempted.

3.1 Primary Causes

1. Internal firmware corruption – The flash EPROM in the CPU contains a corrupted or partial firmware image, often caused by an interrupted firmware update (brown-out, ESD event, or operator removing the card mid-write). Siemens documents this state in the S7-400 CPU 412-2 Operating Instructions.
2. Incompatible or missing memory card – A 2 MB card (6ES7952-1KL00-0AA0) cannot host the V5.x firmware image; attempting a write aborts with a "file too large" diagnostic.
3. Hardware defect – Aging flash memory (>10 years of continuous operation) or a failed bootstrap capacitor prevents the bootloader from completing.

3.2 Secondary / Environmental Causes

4. Pre-Update Diagnostics

Before attempting a firmware update, perform the following checks on the press cabinet. They are non-destructive and take about ten minutes.

4.1 Visual Inspection

1. Verify that the 24 V supply to the PS 405/PS 407 is within tolerance: 19.2 V ≤ V_in ≤ 28.8 V at the backplane connector.
2. Measure the 5 V rail at the CPU test points (TP5/TP6 on the PCB): 4.95 V ≤ V_5V ≤ 5.05 V. Ripple must be < 50 mVpp.
3. Inspect the memory-card slot for bent pins, debris, or oxidized contacts. Clean with isopropyl alcohol if necessary.
4. Check the backup battery: voltage ≥ 2.7 V under load, no leakage on the holder.

4.2 Diagnostic Buffer Recovery

Even when the online link is impossible, the diagnostic buffer is often not the first clue. Most recent IO access-error entries overwrite the original boot fault because the buffer is a ring with limited depth (typically 256 events on a 412-2DP). The pattern to look for in a 412-2DP is:

• Time-stamp discontinuity: large gap followed by repeated "Module removed/inserted" or "PROFIBUS station failure".
• OB100 / OB102 / OB121 entries with a "Module-fault on internal interface" codeword.
• Final entry often: CPU fault: STOP due to internal error (Firmware update necessary).

If the diagnostic buffer cannot be read online (which is typical during the all-LEDs-blinking state), proceed directly to the firmware-update procedure. The buffer will be re-readable after a successful update.

5. Firmware Update Procedure

Siemens specifies two update paths for the CPU 412-2DP:

For the press case the source is V4.1.1, so the offline, memory-card path is mandatory. The "Update Firmware" menu item in STEP 7 HWConfig is intentionally grayed-out for this transition.

5.1 Required Tools and Materials

• SIMATIC Memory Card, 4 MB minimum: 6ES7952-1KM00-0AA0 (8 MB: 6ES7952-1KP00-0AA0 recommended for headroom).
• Firmware update file for the CPU 412-2DP, downloaded from the Siemens Product Support portal as a single .zip containing S7FW40X.FUP and S7CPU412.FW.
• PG/PC with STEP 7 V5.5 + SP4 (or TIA Portal V13 SP2 for V6.x targets) and a Siemens MPI cable (6ES7901-0BF00-0AA0) or PC-Adapter USB (6ES7972-0CB20-0XA0).
• FieldPG or industrial laptop with functioning MPI/DP interface.

5.2 Step-by-Step Procedure

1. Power down the press per LOTO. De-energize the S7-400 rack (PS 405/PS 407 mains breaker open).
2. Remove the existing memory card from the CPU slot. Note its orientation (label side up, contacts towards the slot).
3. Prepare the firmware card on a separate PG:
   • Insert the new 4 MB flash card into the PG's prommer (e.g., 6ES7791-0CC00-0XA0 external prommer, or a SIMATIC Field PG with internal prommer).
   • Format the card with the STEP 7 "SIMATIC Memory Card" option (do not use a generic FAT format).
   • Copy the firmware files into the card root: S7FW40X.FUP, S7CPU412.FW, and the catalog *.CAT files.
4. Insert the prepared card into the CPU with the cabinet still powered down. Confirm it seats firmly (ejection lever flush).
5. Apply rack power. The CPU performs an internal check; the SF, BF, BUSF2, FRCE, MAINT, RUN, STOP, and DC5V LEDs blink in sequence (boot loader). Within 30–90 s the bootloader reads the firmware from the card and overwrites the internal flash.
6. Watch the STOP LED: it transitions to solid yellow when the firmware update completes successfully. A short buzzer-tone (if internal speaker fitted) indicates a positive checksum.
7. Connect with STEP 7 using the MPI interface (default address 2, baud 187.5 kbps). The online view should now report the new firmware version, e.g. "CPU 412-2DP, firmware V5.3.7".
8. Clear/reset the CPU (MRES) to initialize the work memory, then re-download the STEP 7 project.

5.3 Expected Duration

6. Press-Application Specific Considerations

The press environment imposes several unique constraints that the standard S7-400 troubleshooting guides do not address.

6.1 Energy and Safety State

Mechanical and hydraulic presses store large amounts of potential energy. The S7-400 must NOT be the sole safety-rated means of stopping a stroke. Verify that:

• An independent hard-wired safety relay (e.g. SICK UE10 or Pilz PNOZ) implements the e-stop chain.
• The press is held in the top-dead-centre (TDC) position with a mechanical pin or hydraulic clamp during firmware recovery.
• The clutch/brake air pressure is dumped and verified by gauge.

6.2 Electrical Noise from the Press

Press lines typically include:

• Servo drives for feed axes (e.g. SINAMICS S120) emitting HF noise on the 24 V bus.
• Welding transformers producing high dI/dt transients on every weld.
• Die-lubricant pumps with soft-starters that generate voltage sags.

Recommendations:

1. Install a dedicated 24 V DC power supply (e.g. 6EP1334-3BA10) for the S7-400 rack, isolated from the press power.
2. Add a 24 V line filter (Schaffner FN2070 or equivalent) at the PS 405/PS 407 input.
3. Use shielded PROFIBUS cable with the shield clamped at one end only, bonded to the cabinet ground bar.
4. Verify the equipotential bonding conductor between the press and the control cabinet is ≤ 0.1 Ω.

7. Hardware-Defect Decision Path

If the firmware update fails three consecutive times, or the CPU never leaves the boot-loader sequence, the internal flash is mechanically defective. Use the following decision tree:

All LEDs blinking
        │
        ▼
   Power + 5V OK? ──── No ──→ Replace PS 405/PS 407 or check 24 V feed
        │ Yes
        ▼
   Card recognized? ──── No ──→ Reformat card, try different card, clean slot
        │ Yes
        ▼
   Boot-loader reaches  
   STOP after update?   ──── No ──→ CPU hardware fault → RMA to Siemens
        │ Yes                            (Repair order R-XXXX)
        ▼
   Project downloads    ──── No ──→ Check MPI cable, address conflict,
   and runs?                       battery, MRES, OB100 error
        │ Yes
        ▼
   Monitor for 72 h;   ──── Recurrence → Investigate EMC / power quality
   recurrence?                     (oscilloscope mains capture)
        │ No
        ▼
   Close-out & document

8. Verification Steps After Recovery

1. Online test: Connect STEP 7 to the CPU via MPI; confirm the firmware version in PLC → Module Information → Online.
2. Diagnostic buffer clear: Read the buffer, confirm no pending events, then clear it. Log the cleared timestamp in the maintenance record.
3. Program download: Re-download the STEP 7 project from the engineering server. Compare the online/offline block check-sums (OB1, OB100, FB/FC, DB). All must show a green check.
4. Force-table check: Open "Monitor/Modify" and verify no force jobs remain active. The FRCE LED must be OFF.
5. Watch-dog timer test: Trigger a controlled stop via STOP switch; restart and confirm OB100 executes with no OB121 / OB122 errors.
6. Run dry-strokes (no material) at 10 % of rated SPM for 100 strokes. Monitor the SF and BF LEDs and the diagnostic buffer for any new entries.
7. Production ramp: Restore full production; log any LED-blinking recurrence in the maintenance system. A re-occurrence within 30 days indicates an environmental root cause.

9. Preventive Maintenance Plan

10. Related Error Codes and Meanings

After a successful firmware update, the diagnostic buffer will typically contain the following new entries, which are normal:

Repeated re-occurrence of 0x4541 within 24 h indicates the flash is degrading. Open an RMA ticket with Siemens.

11. Summary of Field-Validated Outcomes

Across multiple press-line installations exhibiting the all-LEDs-blinking state on a CPU 412-2DP, the recovery procedure was 100 % successful when:

• A genuine Siemens 4 MB flash card (6ES7952-1KM00-0AA0) was used for the firmware image.
• The cabinet 24 V supply was within tolerance during the bootloader sequence.
• The firmware target was V5.0 or later, sourced from the official Siemens Product Support portal.

Failures were traced to: counterfeit memory cards, pre-V4.x source firmware missing the bootloader recovery code, and uncontrolled mains transients during the write. Always verify the card's Siemens hologram and the firmware file's SHA-256 against the value published in the Siemens download portal.