Profibus BF (red LED) — 6 common causes & how to diagnose

A red BF (Bus Fault) LED on a Siemens CPU or DP master means the master cannot communicate with at least one slave on the Profibus DP network. The line can stop suddenly. Below are the 6 most common causes and how to diagnose them quickly on site.

6 common causes

1. Wrong termination — missing terminators at both segment ends, or a terminator switched on mid-line. This is the #1 cause.
2. Station address — duplicate address, or a slave set to the wrong address versus the PLC configuration.
3. Cable & connector — hidden break, loose, A/B pins swapped (green ↔ red), shield not grounded.
4. EMC noise — Profibus cable run in the same tray as power/VFD cables, poor grounding.
5. GSD config / baud rate — missing the correct GSD version, or a baud rate mismatch across the segment.
6. Slave power & hardware — slave lost power, faulty comms module, or hung and needs a power-cycle.

Step-by-step diagnosis

1. Identify which slave is missing Read the diagnostic buffer in the PLC, or the LEDs on each slave. Narrow it down: one station or the whole segment.
2. Check terminators Exactly 2 terminators, placed at both ends of the segment, switched correctly. Profibus connectors have a built-in ON/OFF switch.
3. Verify station addresses Compare the physical address (DIP/software) with the hardware config in the project. No duplicates, correct numbers.
4. Measure & inspect the cable Check continuity A-A, B-B; verify the shield is grounded at one point; reseat any suspect connectors.
5. Use a tool Use a Profibus analyzer (ProfiTrace) to see signal quality, retries, intermittent stations — separating physical from config faults.
6. Controlled power-cycle If a slave is hung, power each station off/on; keep before/after logs to pinpoint the culprit.

When to call an expert

If you have checked terminators + addresses + cable and BF persists, it is likely a hidden physical fault (noise, attenuation, repeater) or a GSD/baud config issue — needing a bus analyzer and waveform-reading experience. This is exactly DeepDebug's strength: we have the tools (ProfiTrace, a real lab) and can work remotely, including on legacy gear.