BF and SF Faults in Siemens S7-300: What They Mean

July 21, 2026 • PLC Department Tech Team • 7 min read

Walk up to a Siemens S7-300 rack and see a red LED blinking — you need to know fast whether you have a bus problem, a configuration mismatch, or a failing CPU. Two LEDs cause most of the confusion: BF (Bus Fault) and SF (System Fault). They look similar. They mean different things. Diagnosing the wrong one wastes hours.

Quick Answer

SF (System Fault) means the CPU has detected an internal error — a hardware fault, configuration mismatch, or a module reporting a diagnostic interrupt. BF (Bus Fault) means the CPU cannot communicate on a fieldbus — typically PROFIBUS DP. BF2 is a second bus interface fault on CPUs that carry two DP ports. Read the diagnostic buffer in STEP 7 or TIA Portal to pinpoint the exact cause of either LED.

⚠️ Safety First

Do not assume a faulted PLC is de-energized. The CPU may still be powering field devices. Apply full LOTO to the machine before swapping any module. Verify zero energy at every energy-isolating device before touching hardware.

BF vs. SF: Core Differences

These two LEDs live on the CPU front panel. They are not interchangeable. Knowing the distinction is step one.

BF and SF serve completely different diagnostic purposes — reading the wrong one sends you down the wrong path.

LED	Full Name	What It Watches	Common Triggers
SF	System Fault	CPU internals, module diagnostics, program errors	Failed I/O module, config mismatch, OB not loaded, hardware fault
BF	Bus Fault	PROFIBUS DP interface (port 1)	Missing slave, bad cable, address conflict, baud rate mismatch
BF2	Bus Fault (Port 2)	Second PROFIBUS DP or MPI/DP interface	Same as BF — applies to CPUs with dual DP ports

What Is the SF (System Fault) on an S7-300?

SF lights red any time the CPU detects a fault that is not specifically a bus communication problem. Think of it as the CPU raising its hand and saying something is wrong inside the system.

Most frequent causes:

A signal module (SM) or function module (FM) is missing, failed, or does not match the hardware config in STEP 7
A diagnostic interrupt (OB 82) was triggered by a module and OB 82 is not loaded — CPU goes to STOP
A programming error called an OB that does not exist — CPU transitions to STOP and lights SF
Battery/memory card fault on older CPUs
Internal CPU hardware degradation

Pro tip: SF + STOP together almost always means an OB is missing. SF + RUN means a module is reporting a diagnostic interrupt but the CPU is still running. Check OB 82, OB 86, and OB 122 — if any are absent and the relevant interrupt fires, the CPU stops.

What Is the BF (Bus Fault) on an S7-300?

BF is exclusively about PROFIBUS DP communication on the CPU's onboard DP port. It has nothing to do with the backplane bus connecting modules in the rack — that is a different path entirely.

BF lights when:

One or more configured PROFIBUS slaves are not responding
The cable is broken, terminated incorrectly, or connectors are loose
A slave address in the hardware config does not match the physical device's set address
Baud rate on the slave does not match the master configuration
The bus has no termination resistors enabled at both ends

What Is BF2?

Some S7-300 CPUs carry two integrated DP interfaces. The second port gets its own LED labeled BF2. Diagnose it exactly like BF — same causes, same tools — but focus on the slaves assigned to DP master system 2 in your hardware config. Which CPU models include a second DP port and a physical BF2 LED varies across the product line — confirm against the specific CPU's product manual at support.industry.siemens.com before drawing conclusions about your hardware.

Follow this sequence when BF lights — do not swap hardware until you have confirmed the cable and address first.

How to Diagnose SF and BF Step by Step

Read the diagnostic buffer first. In STEP 7, navigate to the module information area and open the Diagnostic Buffer — exact menu names vary by STEP 7 version. In TIA Portal, go online and look for the diagnostics or online diagnostics section — menu structure varies by TIA Portal version. The buffer tells you the exact event — do not guess before you read it.
For SF: Look at the event description. Note whether the CPU is in RUN or STOP. Check which module address is flagged. Walk the rack and look for a module with its own red fault LED.
For BF: In STEP 7 Hardware Config, open the DP master properties and check configured slave addresses. Walk to each PROFIBUS slave and verify the physical address switch matches the config. Check termination resistors at both cable ends.
Check OBs. If SF is lit and CPU is in STOP, verify OB 82 and OB 86 exist in your project. Add them — even empty bodies — download, and attempt to restart.
Inspect hardware. Reseat modules. Check backplane bus connectors. Look for damaged PROFIBUS connectors — broken pins are common on nodes that get bumped.
Swap suspect hardware last. Replace only after the diagnostic buffer points at a specific module or the physical inspection reveals damage.

Common Problems and What They Actually Mean

Match your symptom to a probable cause before touching hardware.

When Replacement Makes More Sense Than Repair

If the diagnostic buffer shows repeated internal CPU errors with no external cause — or if the CPU shows SF even after you've verified the config, reloaded the program, and confirmed all modules are healthy — the CPU itself may be failing. Same logic applies to a CP module or FM that keeps triggering SF regardless of what you do downstream.

⚡ Need a tested replacement?

PLC Department stocks tested Siemens S7-300 CPUs, signal modules, and communication processors — 1-year warranty, same-day shipping from Texas.

Shop Siemens S7-300 →

Pro tip: When ordering a used S7-300 CPU, verify the firmware version matches your existing project. Older firmware may not support all blocks your program expects. Check the CPU product manual at support.industry.siemens.com before downloading a new config.

Disclaimer: This guide is provided for general information only. Procedures vary by model, series, and firmware version. Industrial equipment can cause serious injury, equipment damage, or downtime if serviced incorrectly. Always consult the manufacturer's official documentation and a qualified professional before performing work, and follow your facility's lockout/tagout and safety procedures. PLC Department is an independent surplus supplier and is not affiliated with or endorsed by the manufacturers referenced. Use this information at your own discretion.