Siemens S7-1500 SF Fault LED — Reading the Diagnostic Buffer

Siemens · beginner · 25 min

A steady red SF (System Fault) LED on an S7-1500 CPU means a diagnosable hardware or module fault. Use the diagnostic buffer in TIA Portal to find the exact cause instead of guessing.

ℹ️ SF is a diagnostics LED, not a program error. The CPU has logged exactly what happened — the whole job is to read that log rather than swap parts blindly.

What the SF LED tells you

On a SIMATIC S7-1500 CPU, a steady red SF (System Fault / ERROR) LED signals a diagnosable fault somewhere in the station — a failed or misconfigured module, a wiring fault on a channel that supports diagnostics, or a firmware/configuration mismatch. It is distinct from BF (Bus Fault), which points at a PROFINET/PROFIBUS network problem. When SF is lit, the CPU has already written a timestamped entry to its diagnostic buffer describing the cause.

The fastest path: read the diagnostic buffer

  1. Go online. In TIA Portal connect to the CPU (Online & Diagnostics), or on an HMI/web server open the CPU's diagnostics.
  2. Open Diagnostics → Diagnostics buffer. Each entry is timestamped, newest at the top. Read the most recent entries around the time the SF LED came on. The buffer names the event in plain text — e.g. a module fault, a channel error, a supply-voltage problem, or a rack/station change.
  3. Note the module and channel. Entries reference the affected module by slot and, where relevant, the channel. This is what tells you which card and which point to inspect.

Resolve by fault class

  • Module fault / module removed or replaced: Confirm the physical module matches the configured one (order number and firmware). Reseat it; if it was swapped, make sure the replacement is the configured type.
  • Channel diagnostic (e.g. wire break, short, over/under-range on analog): Inspect the field wiring on the named channel — broken sensor wire, shorted output, or an out-of-range transmitter. Many analog and fail-safe channels only annunciate when channel diagnostics are enabled in the hardware configuration.
  • Parameter/configuration mismatch: If the hardware config in TIA Portal no longer matches the physical station, recompile and download the correct hardware configuration.
  • Supply issue: Check the 24 VDC load-group / module supply feeding the affected card.

Verify the fix

After correcting the cause, the diagnostic buffer logs an incoming/outgoing pair for the event, and the SF LED goes out once no diagnosable fault remains. If SF stays lit, re-read the buffer — there may be a second, older fault still active. Always clear faults by resolving the logged cause, never by ignoring the buffer.

Good practice

Enable channel diagnostics on analog and fail-safe modules during commissioning so future faults appear in the buffer with a specific channel and cause, turning a vague red LED into an actionable message.

Key points

  • Steady red SF = a diagnosable system/module fault; BF instead means a network (PROFINET/PROFIBUS) fault.
  • The CPU has already logged the cause — open Online & Diagnostics → Diagnostics buffer in TIA Portal.
  • Buffer entries are timestamped and name the module/slot and channel involved.
  • Resolve by class: module mismatch, channel wire-break/short, config mismatch, or 24 VDC supply.
  • SF clears automatically once no diagnosable fault remains — never just ignore the buffer.

Codes and symptoms

SF — System Fault LED (steady red)
A diagnosable hardware, module, channel, or configuration fault is active; details are in the CPU diagnostic buffer.
BF — Bus Fault LED
A PROFINET/PROFIBUS network fault — check bus wiring, device addresses, and terminations (distinct from SF).