S7-1500 SF/BF LED Troubleshooting: Common Causes and Fixes

You walk up to your S7-1500 rack and see a flashing orange LED — either SF (System Fault) or BF (Bus Fault). The machine is still running, or maybe it just stopped. Either way, you need to know what the LED means and how to clear it.

This guide covers every S7-1500 CPU front-panel LED, explains the most common causes behind SF and BF faults, and walks through the diagnostic steps to get back to a solid green RUN state.

S7-1500 CPU LED indicators: what each one means

Every S7-1500 CPU has the same set of front-panel LEDs. Here is the complete list and what they tell you.

SF LED: system fault causes and fixes

The SF LED turns on when the CPU detects a diagnostic event from any module in the station or from the CPU itself. It stays on until the event is acknowledged or the root cause is cleared.

Cause 1: I/O module configuration mismatch

Symptom: SF LED on, plus the ERROR LED on the specific I/O module.

What happened: The module configured in TIA Portal does not match the physical module in the slot. Common scenarios:

• You replaced a module with a different hardware version
• A module was removed from the rack but is still configured in the project
• The front connector is not fully inserted

Fix:

1. Open TIA Portal → Online & Diagnostics → Diagnostics buffer
2. Identify which module is faulting (the diagnostics buffer shows the slot number)
3. Verify the physical module matches the configured part number
4. If you replaced a module, update the hardware configuration in TIA Portal and download
5. Check the front connector — push it firmly until it clicks

Cause 2: Channel-level wire break or short circuit

Symptom: SF LED on, specific channel(s) show diagnostics in TIA Portal.

What happened: An analog input module detects an open wire (no sensor connected or wire broken) or a short circuit on a measurement channel. S7-1500 analog modules with HF designation (6ES7531-7KF00-0AB0, for example) perform continuous wire-break detection.

Fix:

1. Check the diagnostics buffer to identify the exact channel
2. Measure continuity on the field wiring to that channel
3. If the channel is intentionally unused, disable wire-break detection for that channel in TIA Portal (Module properties → Channel parameters → Diagnostics → uncheck "Wire break")

Cause 3: Module not reachable (empty slot)

Symptom: SF LED on, one or more modules show "Module not available" in diagnostics.

What happened: TIA Portal expects a module in a specific slot, but the slot is physically empty. This occurs when a module is removed for repair or when a system is partially assembled.

Fix:

1. Install the missing module, or
2. Remove the module from the TIA Portal hardware configuration and re-download

Cause 4: Program error (OB not found)

Symptom: SF LED on, CPU goes to STOP.

What happened: The CPU tried to call an Organization Block that does not exist in the user program. For example, a hardware interrupt (OB40) fires but no OB40 is programmed. On S7-1500, missing OBs cause a STOP by default (unlike S7-300, which could be configured to ignore missing OBs).

Fix:

1. Check the diagnostics buffer for "OB not loaded" entries
2. Either add the required OB to your program or disable the interrupt source (e.g., turn off hardware interrupts on the module that triggers them)

Cause 5: Safety program error (F-CPUs only)

Symptom: SF LED on, safety program passivates (F-DI/F-DO modules go to safe state).

What happened: A safety-related fault occurred. Common causes include F-I/O module communication timeout, safety signature mismatch after program change, or discrepancy error on a dual-channel safety input.

Fix:

1. Check the safety diagnostics in TIA Portal (Safety Administration → Diagnostics)
2. For F-I/O timeouts: check PROFINET cable and switch connections to the F-DI module
3. For signature mismatches: re-download the safety program after confirming changes
4. Acknowledge the safety fault via TIA Portal or the HMI

BF LED: bus fault causes and fixes

The BF LED indicates a communication failure. On S7-1500, this typically means a PROFINET device or PROFIBUS slave is not responding.

Cause 1: PROFINET device not reachable

Symptom: BF LED flashing, one or more PROFINET devices shown as "not accessible" in TIA Portal.

Common causes:

• Ethernet cable disconnected or damaged
• Network switch port failure
• PROFINET device powered off or in fault
• IP address conflict on the network
• Device name not assigned (new or factory-reset devices have no PROFINET name)

Fix:

1. Check LINK LEDs on the CPU's PROFINET ports — no light = no physical link
2. Verify Ethernet cables (try a known-good cable)
3. In TIA Portal, go to Online → Accessible devices to scan the network
4. If the device appears with no name, assign it using "Assign PROFINET device name"
5. Check for IP conflicts using TIA Portal's network diagnostics or your switch's MAC table

Cause 2: PROFIBUS slave not responding

Symptom: BF LED on (for CPUs with DP interface like CPU 1516-3 PN/DP or CPU 1517-3 PN/DP).

Common causes:

• PROFIBUS cable break or shield grounding issue
• Slave address conflict (two devices with the same address)
• Terminating resistor missing at end of bus segment
• Slave powered off or in fault

Fix:

1. Check the diagnostics buffer — it identifies which slave address is faulting
2. Verify physical PROFIBUS cable connections and termination
3. Check slave address DIP switches against the TIA Portal configuration
4. If using a CM 541-1, check the LED on the communication module itself

Cause 3: ET 200 remote I/O station offline

Symptom: BF LED on, plus SF LED on. Entire remote station's I/O goes to substitute values.

What happened: An ET 200SP or ET 200MP remote station lost its PROFINET connection to the CPU.

Fix:

1. Check network connectivity between the CPU and the ET 200 interface module
2. Verify the ET 200 interface module has power and shows a green BF LED (not red)
3. Check the managed switch port status if using infrastructure switches
4. Test with a direct cable from CPU to ET 200 to rule out switch issues

Diagnostic tools built into the S7-1500

The S7-1500 has more detailed built-in diagnostics than the S7-300 or S7-400. Use these tools before reaching for a multimeter.

CPU display (front panel)

S7-1500 CPUs with a display module (6ES7591-1AA01-0AA0) show fault details directly on the front panel. Navigate to Diagnostics → Diagnostic buffer using the mode selector.

TIA Portal online diagnostics

Connect to the CPU via PROFINET and go to Online & Diagnostics. The diagnostics buffer lists every event with a timestamp, module ID, and description. This is the fastest way to pinpoint the exact fault.

Web server

Every S7-1500 CPU has a built-in web server. Access it at http://[CPU-IP-address] from any browser. The web interface shows CPU status, diagnostic buffer, module status, and communication statistics — no TIA Portal installation needed. Useful for maintenance techs who do not have engineering software on their laptop.

Quick troubleshooting flowchart

1. Which LED is on?
   • SF only → Module or program issue (see SF section above)
   • BF only → Communication failure (see BF section above)
   • SF + BF → Remote I/O station offline (causes both)
   • ERROR (red) → Hardware failure — CPU may need replacement
2. Check the diagnostics buffer (display, TIA Portal, or web server)
3. Identify the faulting module or device (slot number, PROFINET name, or DP address)
4. Inspect physical connections (front connectors, Ethernet cables, power)
5. Compare configuration to physical hardware (right part number? right address?)
6. Fix and clear — some faults auto-clear, others require acknowledgement in TIA Portal

Frequently asked questions

Need replacement parts?

If diagnostics point to a failed module, we stock the full range of S7-1500 CPUs, I/O modules, and accessories. See our S7-1500 Buyer's Guide for help choosing the right replacement, or browse our Siemens PLC Systems collection. Need a specific part number? Request a quote for fast shipping.