Siemens S7-319-3 SF LED Diagnostics Profibus Fault

1. Problem Scope: SF LED on a SIMATIC S7-319-3 CPU

The SF (System Fault) LED on a Siemens SIMATIC S7-300 CPU 319-3 PN/DP is a collective error indicator. It illuminates whenever the CPU detects any unrecoverable or unacknowledged error condition, whether the origin is internal (program execution, memory, firmware, hardware on the CPU module itself) or external (a distributed I/O node on PROFIBUS-DP or PROFINET, a failed DP slave power supply, a wiring break, or a parameterization mismatch). Because the SF LED is a single bit summarizing many possible fault sources, the LED alone never identifies the root cause. Field engineers must consult the diagnostic buffer of the CPU and, where needed, the online hardware diagnostics in STEP 7 or TIA Portal to isolate the offending node or instruction.

This reference applies to the high-performance CPU 319-3 PN/DP used in production-engineering applications. The front-panel LED layout, the meaning of the BF (Bus Fault) LED, and the diagnostic buffer structure are documented in the official SIMATIC S7-300 CPU 31xC and CPU 319-3 PN/DP manual on the Siemens Industry Online Support portal.

2. Hardware Identification: CPU 319-3 PN/DP Front-Panel Elements

Before interpreting any LED, confirm the exact module variant and firmware version. The CPU 319-3 PN/DP has two PROFIBUS interfaces (MPI/DP combined on X1, DP on X2) plus a PROFINET interface on X5 (depending on the order number). The following front-panel elements are relevant to fault diagnosis (per the CPU 31xC/319-3 manual):

The SF and BATF (battery fault), DC5V (internal 5 V OK), and FRCE (force active) LEDs are grouped together so a single visual sweep covers CPU-internal health.

2.1 LED Truth Table for Fault Conditions

*BF behavior depends on whether the failed slave is on X1 or X2; the unused bus BF remains dark.

3. Classifying the Fault: Internal vs External

The first diagnostic decision tree branch is the source of the fault. S7-300 CPUs make this distinction in their diagnostic buffer event classification:

3.1 External Fault Path

For an external (PROFIBUS) fault the diagnostic buffer records the diagnostic address of the failed DP slave. Reading the buffer in STEP 7 (classic) or TIA Portal (V13 and later) immediately yields the slave's PROFIBUS station number, diagnostic address, and the slave-specific diagnostic bytes (per EN 50170 / IEC 61158). The SF LED is lit because the CPU has classified the slave diagnostic as an external error; the corresponding BF LED on the affected interface is also lit or flickering.

3.2 Internal Fault Path

For an internal fault the S7-300 diagnostic buffer typically identifies the block type and number that triggered the error, the OB that was missing (e.g. OB121 for programming error), and the priority class. However, on S7-300 CPUs the diagnostic buffer entry for an internal error is sometimes less specific than the equivalent entry produced by an S7-400 CPU with identical user software. This is a known limitation, documented across multiple Siemens support entries; field engineers frequently replicate the project on an S7-400 PLCSIM or a real S7-400 CPU to obtain the deeper diagnostic detail that S7-300 omits.

4. BF LED Behavior on the CPU 319-3 PN/DP

The CPU 319-3 PN/DP has three bus error LEDs:

• BF1 – PROFIBUS interface X1 (combined MPI / DP master)
• BF2 – PROFIBUS interface X2 (DP master or DP slave, hardware-configurable)
• BF3 – PROFINET interface X5

4.1 BF LED States and Meanings

4.2 Specific Scenario: A DP Slave Loses Power

When any node on the configured PROFIBUS network is powered down, the CPU 319-3 PN/DP detects the missing slave on the next token rotation. The sequence is:

1. CPU polls slave → no response within T_slot.
2. CPU records a station failure event in the diagnostic buffer (event ID 0x39E0 series for DP master system errors on S7-300).
3. CPU calls OB86 (rack failure / station failure). If OB86 is not loaded, the CPU transitions to STOP.
4. The BF LED on the affected interface begins to flash (slave-down) or stays lit (total bus failure).
5. The SF LED illuminates because the CPU has an unacknowledged external fault.

5. Reading the Diagnostic Buffer (STEP 7 Classic and TIA Portal)

5.1 STEP 7 (Classic) Procedure

1. Open the project in SIMATIC Manager with the CPU online (via TCP/IP, MPI, or PROFIBUS).
2. Select the CPU 319-3 PN/DP in the project tree.
3. Right-click → Target System → CPU Messages / Diagnostic Buffer.
4. The buffer shows the most recent 100 events (default). Each event contains:
   • Time stamp (CPU time-of-day)
   • Event ID (hexadecimal)
   • Event description
   • Additional information (block number, OB, address, slave diagnostics bytes)
5. Double-click any event to view the full details; for DP station events, double-click again to open the slave's module diagnostics.

5.2 TIA Portal Procedure

1. Open the project in TIA Portal (V13 SP1 minimum for CPU 319-3 PN/DP).
2. Switch to Project view, select the CPU in the device tree.
3. From the menu: Online → Online & Diagnostics.
4. Select the Diagnostics buffer tile. TIA Portal decodes the same event IDs as STEP 7 and adds hyperlinks to the affected block or device.
5. For PROFINET diagnostics, expand PROFINET IO → Diagnostics for station-level, module-level, and port-level information.

6. Hardware Diagnostics via HW Config (STEP 7 Classic)

For external PROFIBUS faults, open HW Config with the CPU online. The PROFIBUS DP master system shows a red X on the failed slave. Right-click the slave → Object Properties → Diagnostics opens the slave's live diagnostic data, including:

• Station status (1 = OK, 0 = failure)
• Module status bitmap
• Channel-specific diagnostic bytes
• Identifier-related diagnostics

This view directly answers the question "which node has failed?" without requiring further disambiguation.

7. Common Diagnostic Event IDs (S7-300)

The following event IDs are emitted by the CPU 319-3 PN/DP diagnostic buffer and frequently observed during field service. They are documented in the STEP 7 online help and in the CPU 31xC/319-3 manual referenced above.

8. Why Use an S7-400 Simulator for Internal Faults

When an internal fault causes STOP on the CPU 319-3 PN/DP and the diagnostic buffer entry is generic (for example, "Programming error in OB1, block FCxxx" without further detail), running the identical user program on an S7-400 CPU (real or PLCSIM) frequently yields a more verbose diagnostic entry. The S7-400 firmware provides additional diagnostic depth because:

• The S7-400 diagnostic buffer has a larger format and additional fields.
• S7-400 supports priority-class-specific error OBs that S7-300 combines.
• PLCSIM (the Siemens S7 simulator bundled with STEP 7) can reproduce the same program fault with full diagnostic detail, allowing the engineer to identify the exact instruction and operand.

This is a documented workaround when the S7-300 buffer is insufficient for root-cause analysis. No firmware modification is required; only a parallel test on S7-400 / PLCSIM.

9. Step-by-Step Troubleshooting Procedure

9.1 Prerequisites

• STEP 7 V5.5 SPx or TIA Portal V13 SP1 or later installed on the engineering station.
• Online connection to the CPU 319-3 PN/DP via MPI/PROFIBUS/PROFINET.
• User project (matching firmware version) available offline.
• Access to the PROFIBUS cable path and the physical DP slaves.

9.2 Procedure

1. Confirm the SF LED state. If SF is off, the issue is elsewhere (BATF, FRCE, or BF-only). If SF is on, proceed.
2. Read the diagnostic buffer (STEP 7 or TIA Portal as described in §5).
3. Identify the fault class from the event description:
   • Event references a DP slave → go to step 4.
   • Event references a block / OB → go to step 6.
   • Event references CPU hardware / MMC → go to step 7.
4. External / PROFIBUS fault path:
   1. Note the slave's PROFIBUS address and diagnostic address from the event.
   2. Open HW Config online and locate the slave in the DP master system.
   3. Right-click → Diagnostics. Read the station status and module status.
   4. Physically verify: 24 V supply at the slave, bus connector seated, termination at both ends of the segment, shield grounded at one point only.
   5. Power-cycle the failed slave. Confirm the diagnostic buffer records a station return (0x39E2).
   6. Confirm BF LED returns to off and SF clears.
5. External / PROFINET fault path: Use TIA Portal → Online & Diagnostics → PROFINET IO → Diagnostics. Check port LED on the affected device. Replace cable or device as indicated.
6. Internal fault path:
   1. Note the block number and OB identifier.
   2. Load the corresponding error OB if missing (OB82 for diagnostic interrupt, OB85 for priority class errors, OB86 for rack failure, OB121 for programming error, OB122 for I/O access error).
   3. If the error persists with all error OBs loaded, replicate the program on S7-400 / PLCSIM to obtain deeper diagnostics.
7. CPU hardware / MMC fault path:
   1. Re-seat the SIMATIC Micro Memory Card; verify write-protect switch position.
   2. Re-format the MMC using STEP 7 → SIMATIC Memory Card → Format.
   3. If SF persists, perform an MRES (master reset) and reload the project.
   4. If SF still persists, the CPU module is suspect; replace.

10. Verification Checklist

11. Edge Cases and Field-Proven Caveats

• SF + BF lit, CPU stays RUN: The user program has OB86 loaded and the CPU is configured to continue on station failure. This is correct behavior for a process where DP slaves may be temporarily de-energized.
• SF + BF lit, CPU goes to STOP: OB86 is missing or faulty. Load a valid OB86 from the standard library and re-download.
• BF flashing but no DP slave obviously failed: Check for duplicate PROFIBUS addresses, baud-rate mismatch, or a slave with address 0 (default, often reserved for a master class 2). Verify with a PROFIBUS bus monitor (e.g., Softing PROFIbus diagnostic tool) if available.
• SF lit, all BFs dark, no entry in diagnostic buffer: Possible battery-backed RAM or MMC write error. Check BATF. If BATF is off but SF is on with no event, perform an MRES; persistent SF without a buffer entry indicates a CPU hardware fault.
• Diagnostic buffer flooded with retries: A flapping DP slave (intermittent power or connector) can produce thousands of station-failure / station-return pairs per hour. Resolve the physical issue first, then clear the buffer to confirm a clean baseline.
• S7-300 vs S7-400 buffer detail asymmetry: Documented behavior. Use S7-400 / PLCSIM only as a parallel test environment; do not substitute it for the production CPU.

12. Frequently Asked Questions