Troubleshooting S7-400 EXTF LED Flashing: Root Causes and Repairs

1. EXTF LED Behavior on S7-400 CPUs

The EXTF (External Fault) LED on a Siemens S7-400 CPU is a front-panel indicator used to surface fault conditions detected in the I/O, communication, or peripheral system that the CPU cannot classify as an internal logic error. A continuously lit or flashing EXTF LED signals that the operating system has recorded an external error event. The EXTF LED is distinct from the INTF (Internal Fault) LED, which surfaces programming errors, CPU firmware exceptions, and stack overflows that originate inside the user program or CPU core.

On the S7-400 CPU front panel, the EXTF LED is located next to the INTF, FRCE, RUN, and STOP indicators. When EXTF activates, the CPU does not necessarily transition to STOP; many EXTF events are non-fatal and the program continues executing in RUN. The actual transition to STOP is governed by the corresponding organization block (OB) configured to handle the error. If the matching OB is missing, the CPU goes to STOP. If the OB is present, the error is handled and the CPU remains in RUN.

2. Sources That Trigger EXTF on S7-400

The S7-400 Programmable Controller System Manual (chapter 1.2, indicator/LED functions) documents the classes of conditions that drive the EXTF LED. The diagnostic buffer should always be read first, because each event carries a unique event ID, OB reference, and module address that pinpoints the root cause.

The Siemens Knowledge Base article 5406022 documents the latching behavior of the EXTF LED on the SM422-7BL diagnostics-capable digital output module: after a ground short-circuit occurs at an output and is subsequently cleared, the module's error detection mechanism continues to assert the EXTF LED even when the diagnostic buffer no longer contains an active incoming event. This is a known service event that frequently causes the diagnostic buffer to appear empty even though the LED remains on.

3. Reading the S7-400 Diagnostic Buffer

When EXTF activates, the first action is to read the CPU diagnostic buffer through STEP 7 (V5.x), TIA Portal, or directly via the CPU's web server (where supported). The diagnostic buffer is non-volatile and survives a CPU restart.

1. Establish an online connection to the CPU through MPI, PROFIBUS, or PROFINET.
2. Open the target system and select Online > Diagnostics > Diagnostic Buffer.
3. Read the most recent events from newest to oldest.
4. Note the Event ID, OB reference, and module logical address.
5. Click each event to see the detailed description with date, time, and event context.
6. If the buffer is empty or shows no incoming events, proceed to hardware checks covered in the next sections.

4. SM422-7BL Output Module Latch Behavior

The SM422-7BL (a 32-channel 24 V DC digital output module with diagnostics) exhibits a documented latching fault behavior. When a ground short-circuit occurs on one of its outputs, the channel trips and reports a diagnostic interrupt. Once the short-circuit is physically removed, the trip condition in the module does not auto-clear; the module continues to assert the fault and the EXTF LED remains on. The diagnostic buffer shows the original ground short event but no new incoming event after the fault is removed.

According to the Siemens KB article 5406022, this is by design in the module's error detection mechanism. The only ways to clear the latched EXTF are:

• Power-cycle the SM422-7BL by removing the front connector and reinserting it (a brief field procedure).
• Issue an output disable/re-enable through STEP 7 with the CPU in STOP-RUN transition.
• Cycle the load voltage supply on the module's power input.

If the EXTF LED is the only symptom and the diagnostic buffer shows a historical ground short event, the SM422-7BL is the prime suspect. The presence of multiple SM422-7BL modules in the rack complicates diagnosis because the module address and the diagnostic interrupt OB must be cross-referenced. Add OB82 with the module's logical base address in OB82_MDL_DEFECT or read LBAD/LBAB to identify the specific channel.

5. Power Supply, Battery, and BAF LED

The S7-400 power supply modules (PS 405 for AC, PS 407 for DC) include backup battery compartments. When the backup battery voltage falls below the threshold or a battery is missing, the power supply module reports a battery fault. The power supply front panel has a BAF (Battery Fault) LED for this purpose.

On most PS 405/PS 407 variants there is a BAT IND switch with three positions: OFF, 1 BATT, and 2 BATT. The switch is set during commissioning to match the installed battery configuration:

• 1 BATT: One backup battery installed, single-battery monitoring active.
• 2 BATT: Two backup batteries installed (redundancy), two-battery monitoring active.
• OFF: Battery monitoring disabled. The PS will not report a battery fault via BAF, but the CPU may still log a missing-battery event depending on CPU firmware and OB81 configuration.

6. Bent Connector Pin: Hidden Hardware Root Cause

A documented field case shows an S7-400 CPU continuing to flash EXTF even after the user program was removed and the project downloaded with only the hardware configuration. With the diagnostic buffer clear, the rack was inspected and a bent pin was found on the rear-mounted connector linking a module to the backplane.

The S7-400 backplane uses mechanical connectors that pass power and signal lines between the rack and each inserted module. If a pin is bent on insertion, or partially compressed by a side-loaded module, contact resistance rises and the module's power-good handshake fails. The CPU's operating system interprets the resulting backplane fault as an external I/O error and asserts EXTF.

The remedy in the documented case was mechanical: the bent pin was straightened and the connector was re-seated fully. The EXTF LED cleared without software changes, OB reloads, or memory reset.

7. Step-by-Step Field Diagnosis Procedure

Use the following decision tree to isolate the cause of a persistent EXTF LED. The order matters: start with the cheapest, fastest checks (visual inspection, diagnostic buffer) before moving to invasive hardware work.

1. Read the diagnostic buffer. Note the most recent event ID, OB reference, and module address. If a module address is present, jump to step 7.
2. Check the power supply BAF LED and battery voltage. Measure the battery voltage at the PS module terminals. Replace if below 2.8 V per cell. Verify the BAT IND switch is set to 1 BATT or 2 BATT, not OFF.
3. Verify error OBs are loaded. Confirm that OB82 (diagnostic interrupt), OB121 (programming error), OB122 (I/O access error), and OB81 (battery fault) are present in the active program. Missing OBs cause STOP on first occurrence, but even when present, OB load status can mask symptoms.
4. Visually inspect every backplane connector. Power down, then remove each module and inspect both the module's rear connector pins and the rack's backplane mating connector. Look for bent, recessed, or contaminated pins.
5. Reseat every module one at a time. After each reseat, power the rack and observe whether EXTF clears. This isolates the module whose connector is the culprit.
6. Power-cycle suspect modules. For SM422-7BL or any diagnostics-capable digital output with a known ground-fault history, power-cycle the module to clear latched faults per the Siemens KB 5406022 procedure.
7. Remove and re-insert the CPU. Power down, remove the CPU, inspect its connector, reseat, and reapply power. Listen for the CPU's diagnostic relays to click during the self-test.
8. Isolate the rack. Disconnect expansion racks (UR2/ER1/ER2) one at a time. EXTF triggered by an IM (IM460/IM461) or a downstream rack will clear when the IM is removed.
9. Cross-check the hardware configuration. In STEP 7 / TIA Portal, compare the configured module order to the physically installed order. A mismatch generates peripheral errors and EXTF on every scan cycle.

8. Repair and Verification

After identifying the root cause, apply the appropriate repair, then perform the verification sequence below to confirm the EXTF LED has truly cleared and will not return on the next scan.

8.1 Bent Pin Repair Procedure

1. Power down the rack. Wait 30 seconds for capacitor discharge on the PS module.
2. Remove the affected module by releasing the front connector and unscrewing the module.
3. Inspect both the module's rear connector and the rack backplane pin with a magnifier and flashlight.
4. Using a fine non-magnetic pick (e.g., a watchmaker's tool), gently straighten the bent pin. Do not use pliers. The pin should return to its original perpendicular alignment without lateral force.
5. Clean the backplane mating connector with isopropyl alcohol (≥ 90%) and a lint-free swab.
6. Reinsert the module firmly. Verify the module's mounting screws are torqued to the specified value (typically 0.8-1.0 Nm on S7-400 modules).
7. Apply power. Observe the EXTF LED for at least 60 seconds (one full diagnostic scan cycle).

8.2 SM422-7BL Latched Fault Clearing

1. Verify the physical output short-circuit has been removed. Use a multimeter on the affected output terminal, measuring between output and ground.
2. Place the CPU in STOP.
3. Remove the SM422-7BL front connector.
4. Power down the rack, wait 10 seconds, restore power.
5. Reconnect the front connector.
6. Run the CPU. The latched diagnostic bit should be cleared on the next OB82 cycle.

8.3 Battery Replacement Verification

1. Note the date code on the new battery. S7-400 backup batteries (lithium thionyl chloride, 3.6 V, AA-size) have a typical service life of 3-5 years.
2. Insert the battery with correct polarity. Verify the BAT IND switch is on 1 BATT or 2 BATT.
3. Cycle the rack power once to force a battery check.
4. Confirm the BAF LED is off and OB81 is not called.

8.4 Final Verification Checklist

• EXTF LED off after 5 minutes of continuous RUN.
• Diagnostic buffer has no incoming external fault events since the repair.
• All modules are present in the online hardware view (no "fault" or "not reachable" status).
• Communication (PROFIBUS, PROFINET, MPI) is online with no diagnostic alarms.
• Force table is consistent with the application (no stuck forces from prior debugging).
• Backup program archive reflects the post-repair hardware configuration.

9. Common Pitfalls and Edge Cases

The following issues routinely cause an EXTF LED to persist after a "fix" attempt.

9.1 Diagnostic Buffer Cleared Before Reading

On a CPU memory reset (MRES), the diagnostic buffer is wiped. Service teams that escalate without first saving the buffer lose the only authoritative log of the original event. Always read the buffer before any reset and save a screenshot or export the buffer to a CSV file for the ticket.

9.2 BAT IND Switch Left OFF

Some sites disable battery monitoring to silence persistent BAF LED complaints. This is a poor practice because it also silences OB81 and any EXTF driven by battery faults. The CPU's battery-backed RAM may lose retentive data on a power dip and the application may behave erratically on the next restart without an obvious cause.

9.3 Hot-Swapping a Non-Hot-Swap Module

Most S7-400 signal modules are not hot-swappable. Removing a SM module under power can bend pins on both the module and the backplane, and can corrupt the CPU's slot table. Only the PS module and the CPU can typically be hot-swapped (and even then only on certain UR configurations). Always power down the rack before reseating modules.

9.4 Ground Fault Outside the Module

A ground fault on a field wiring cable that runs through a junction box may not be detectable by the SM module if the leakage is below the diagnostic threshold. The SM422-7BL detects ground faults via channel-impedance monitoring and reports them as diagnostic events. If the EXTF LED is solid and the diagnostic buffer shows a ground fault event, check the field wiring, not just the module output.

9.5 Mixed Module Generations

Some older S7-400 modules (e.g., early -0AB00 series) have different diagnostic behaviors than later revisions (e.g., -0AB01). When replacing a module in an emergency, confirm the new module's firmware and MLFB match the configuration. A mismatch can cause persistent peripheral errors that look exactly like a bent pin or a missing OB.

9.6 Expansion Rack IM Module Failure

An IM460/IM461 Interface Module failure on a multi-rack S7-400 system generates an OB84 event and EXTF. The diagnostic buffer will show the IM address. However, if the IM partially fails, the diagnostic buffer may show the rack error only intermittently. A re-seat of the IM and a tightening of the bus terminator can resolve the symptom.

10. Preventive Measures and Best Practices

• Battery maintenance schedule: Replace backup batteries every 3 years regardless of BAF LED state. Log the replacement date on the PS module label and in the maintenance management system.
• Connector handling: When inserting modules, align the rear connector before pushing the module into the backplane. Apply even pressure on both the top and bottom of the module face. Do not use a single-sided force.
• Module storage: Store spare S7-400 modules in anti-static packaging with rear connector protectors. A single bent pin on a spare module can be inserted into a running rack and create a fault that takes the line down.
• OB hygiene: Load OB82, OB83, OB84, OB85, OB86, OB87, OB121, and OB122 even if the program does not use them. Empty OBs prevent CPU STOP on first occurrence of a recoverable error.
• Diagnostic buffer archival: Configure STEP 7 or TIA Portal to archive the diagnostic buffer to a project log on each major event. This preserves the evidence for future root-cause analysis.
• Power supply redundancy: In critical applications, use a redundant PS configuration (two PS modules, BAT IND on both). The redundant PS masks a single PS fault and keeps the EXTF LED off while the alarm is reported through OB81.
• Module grounding: Verify the S7-400 rack is bonded to a low-impedance ground at the installation. Floating grounds cause transient EXTF events that are very hard to reproduce and very hard to diagnose.

Frequently Asked Questions