Troubleshooting Profibus Repeater: SF and BF LED Diagnostics

Problem Definition: Repeater LEDs Stay Dark After Power-Up

A Profibus DP segment reports communication loss to the PLC the moment a new RS485 repeater is inserted into the trunk. The repeater's top-row status indicators (typically labelled SF – group fault, and BF – bus fault) fail to illuminate or stay in their abnormal state, while the segment cable leaving the repeater's downstream port appears to be wired correctly. This condition is most often observed in factories where Profibus DP was shipped from the OEM (for example, pre-built machines coming out of China) and the on-site commissioning team is the first to power the network under real load.

Before assuming the repeater hardware is defective, walk the RS485 physical layer end-to-end. Roughly 80% of "dead repeater" incidents on Profibus DP are wiring or termination problems on the upstream segment, not a failed repeater.

Profibus RS485 Physical Layer Recap

Profibus DP uses an RS485 differential physical layer at 9.6 kbit/s up to 12 Mbit/s. Every segment must obey the following physical constraints as defined in IEC 61158 / IEC 61784 and reiterated in the Siemens SIMATIC NET PROFIBUS Network Manual:

Each Profibus DP segment is a single shielded, twisted-pair line. Stubs, stars, and T-taps are not permitted at baud rates above 1.5 Mbit/s. This is the most common cause of a repeater showing SF/BF even when the cable "looks" connected.

Profibus RS485 Repeater Rules That Decide Whether It Receives Signal

Per the Siemens RS485 Repeater in PROFIBUS and MPI Bus Systems application note, the repeater is a transparent signal regenerator. It does not start a new logical network; it starts a new electrical segment. Therefore:

1. The repeater's upstream port (port 1 / "IN") must see a properly terminated, live RS485 signal. If the upstream segment is open, shorted, or unterminated, the repeater will not see a valid differential voltage and its SF or BF will flag a bus error.
2. The repeater regenerates the signal; it does not provide bus power. The 5 VDC termination bias must come from the station at the end of the segment (typically the PLC or the final slave, or the built-in terminator in the Profibus connector).
3. The repeater's downstream port (port 2 / "OUT") must be terminated only if it is the physical end of that sub-segment. If you continue the cable to a slave, leave the repeater's downstream termination OFF and turn it ON at the last device instead.
4. All segments on either side of the repeater must use the same baud rate and the same PROFIBUS protocol (DP, MPI, or FMS). A baud-rate mismatch causes the BF to latch even though the cable is good.

Wiring Diagnosis: A, B, Shield, and the Red/Green Trap

On the standard Profibus cable (Siemens 6XV1830-0EH10 purple, or compatible), the two cores are colour-coded. The conventions used by 95% of European and Chinese OEMs:

If a Profibus connector is wired with red-to-A and green-to-B, the entire segment is inverted. Many slaves will refuse to communicate and the BF LED on the CPU and on the repeater will stay solid red. The fix is to swap the two cores at the offending connector, not to invert terminations.

Termination Resistor Rules at the Profibus Connector

Almost every Siemens-style Profibus D-sub connector (e.g. 6ES7972-0BA12-0XA0, 6GK1500-0FC10) has a built-in termination resistor that is switched ON or OFF by a slide or by the position of the outgoing cable entry. The rules are unambiguous and yet account for the majority of bus-fault tickets:

If the cable leaving the repeater's downstream port is the end of the sub-segment, the terminating resistor at that end or the active terminator block must be ON. If the repeater sits in the middle of a chain (cable in, cable out), both of its termination switches must be OFF. A repeater with one termination ON while sitting in the middle of a chain is the single most common cause of a "repeater that will not see the PLC."

Reading the LED Status Correctly

Before assuming a wiring fault, identify exactly which LED is dark and which CPU/repeater is in question. The Siemens 6GK1500-0FC10 (RS485 repeater) and the equivalent PROFIBUS repeater family share the following LED map:

If only the BF on segment 1 is red, the fault is on the PLC side of the repeater (upstream). If only the BF on segment 2 is red, the fault is on the slaves side. If SF is red and both BFs are off, the repeater has detected an internal error or the supply is out of tolerance. If all four are dark, the repeater has no 24 V supply – check the power terminals and the fuse on the cabinet, not the Profibus cable.

Also inspect the CPU's own LEDs. On a Siemens S7-300/400/1500 the two Profibus-relevant indicators are SF (group fault, red) and BF (bus fault, red, flashing at 0.5 Hz during search, solid after timeout). Per the SIMATIC S7-300 CPU 31x/31xC Manual:

• BF flashing, SF off → PLC is trying to reach slaves, no response yet (normal during startup or with slaves still in fault).
• BF solid, SF off → Bus physically broken or no slave answered after parameterisation.
• BF solid, SF solid → A slave reported a diagnostic, or the configuration in HW Config does not match the real bus.

Step-by-Step Troubleshooting Procedure

1. Confirm 24 V supply to the repeater. Measure between the +24 V and 0 V terminals on the repeater. A reading below 19.2 V will latch the SF LED and the bus electronics will not initialise. Siemens repeaters require 19.2 – 28.8 VDC per the datasheet for the 6GK1500 series.
2. Power down and visually inspect every Profibus connector from PLC to repeater. Confirm shield drain wire is landed on pin 1 (or on the D-sub backshell). Confirm A is on pin 3 and B is on pin 8 at every connector. A single crossover is enough to kill the segment.
3. Measure idle DC voltage at the repeater's upstream port with all slaves on that segment powered. Expected: B (pin 8) approximately 1 V higher than A (pin 3). If you read 0 V or the polarity is reversed, the upstream segment is not terminated or is wired backwards.
4. Walk the termination switches. For each connector, ask: "Is this the first or last device on this sub-segment?" If yes, ON. If it sits in the middle, OFF. On a 3-device chain (PLC → repeater → slave), the PLC-end connector is ON, the repeater's upstream-side termination is OFF, the repeater's downstream termination depends on whether the cable ends at the slave (ON at the slave) or continues further (OFF in the middle).
5. Check baud rate consistency. Open HW Config (STEP 7 V5.x) or TIA Portal (V15 and newer) and read the configured DP baud rate on the master and every slave. All must match. A baud-rate mismatch will not light the SF LED but will leave BF red solid on the repeater.
6. Disconnect the downstream segment and verify whether the upstream LED recovers. If it does, the fault is downstream – a short, a miswired slave, or a double-terminated segment. If it does not, the fault is upstream – usually the PLC connector or the PLC's own Profibus port.
7. Test with a known-good terminator. Replace the segment terminator with a Siemens 6GK1500-0FC00 active terminator. If BF clears, the original terminator was open-circuit.
8. Substitute the repeater with a spare of the same order number. If the spare behaves identically, the repeater is exonerated; the fault is on the cable. If the spare recovers, the original repeater has a failed RS485 transceiver – RMA the unit.

SVG: Diagnostic Decision Tree

Verification: How to Confirm the Segment is Healthy

After the corrective action, verify the bus with the following checks before handing the line back to production:

1. All repeater LEDs: PWR green solid, SF off, both BFs off.
2. CPU BF: flashing at 0.5 Hz (searching) for < 5 seconds, then OFF once all slaves are in data exchange.
3. From STEP 7 / TIA Portal, run PLC → PROFIBUS → Diagnostics → Bus Statistics. Read the "Error count" and "Repeated token" counters – both should remain 0 over a 5-minute observation.
4. Open a slave's online diagnostic with PG click. The slave should report "Data exchange, no diagnostic."
5. Use a Profibus tester (e.g. Softing PROFINET/PROFIBUS diagnostic tool, or any class-2 master in monitor mode) to capture the bus telegram count and confirm the configured baud rate appears at the repeater's downstream port.

Common Field Pitfalls and Corrections

Preventive Measures for the Next Commissioning

• Adopt a fixed wiring convention and label both ends of every Profibus drop. The most common field mistake is re-using a Profibus cable that was already in place from a previous machine and not re-verifying the A/B orientation after the new installation.
• Use a Profibus D-sub connector with diagnostic LEDs (e.g. 6GK1500-0FC10 family) so segment-level faults are visible at the connector itself, not only at the CPU.
• Pre-configure the segment in HW Config with a single baud rate, never auto-detect, on a green-field segment. Auto-detect works on a perfect segment only.
• Document the termination switch position (ON/OFF) for every connector in the cabinet drawing, not only in the schematic.
• Run a "ring test" before energising: disconnect the PLC, short pin 3 to pin 3 and pin 8 to pin 8 across the segment with a short jumper, and measure the loop resistance from one end. Expected < 110 Ω (two 220 Ω terminators in parallel) for a healthy cable. An open reading means a broken conductor inside the cable.

FAQ