Resolving BF LED on Siemens SINAMICS CU240S DP: P2040 Fix

The Bus Fault (BF) LED on a Siemens SINAMICS CU240S DP Control Unit (MLFB 6SL3244-0BA20-1PA0) is driven by the on-board PROFIBUS stack, not by the power section. On a stand-alone drive (no PLC, no PROFIBUS cable connected) the indicator will be ON because the stack reports "no peer" — this is documented behaviour, not a drive-side fault. This reference explains the BF LED state machine, the role of P2030 (field-bus protocol selection) and P2040 (field-bus watchdog time), and the two parameter changes that extinguish the LED on a drive that is intentionally run without a bus.

1. Affected Hardware, MLFBs and Default Parameters

Sources: CU240S Operating Instructions (27069930) and CU240S List Manual V2.1 (24371755).

2. BF LED State Machine (per Siemens Documentation)

Siemens defines the BF LED behaviour for the CU240S DP variants in the Operating Instructions as follows:

Source: CU240S Operating Instructions, section "LED status indication". The RDY LED (green/red) and the COM LED (yellow) provide additional, independent status information that you should always read in combination with BF.

3. Root Cause: Watchdog vs. Protocol Selection

The BF LED is driven by the PROFIBUS stack inside the Control Unit. There are two independent reasons for a steady BF indication on a drive that is not networked:

1. Watchdog timeout (P2040): The field-bus watchdog supervises cyclic PZD exchange. If no new PZD telegram is received within the configured time (default 500 ms), the firmware raises a bus failure and the BF LED turns on. Writing P2040 = 0 disables the watchdog entirely.
2. Protocol mismatch (P2030): The CU is set to PROFIBUS DP (P2030 = 1) but the bus connector is removed, the bus is not terminated correctly, or no master is connected. The stack reports the missing peer and drives BF.

For drives commissioned in local mode (terminals / keypad, no PLC), both causes are present by default. The correct resolution is to either set P2030 = 0 (No Protocol) or to deactivate the watchdog via P2040 = 0. The source case used the latter and the BF LED extinguished on the next boot.

4. Solution A — Disable Watchdog (P2040 = 0)

This is the most common field fix and the procedure that cleared the BF LED on the source case:

4.1 Prerequisites

• STARTER commissioning tool (V5.x or later), TIA Portal with STARTER plug-in, the IOP (Intelligent Operator Panel), or the BOP-2 basic operator panel.
• Access level P0003 ≥ 3 (Expert) is required to write P2040.
• The drive must be at standstill with the ON command removed.
• If using STARTER over USB, install the SINAMICS USB driver and use the correct COM port. If using IOP / BOP-2, no PC is required.

4.2 Procedure

1. Connect to the drive via STARTER / IOP / BOP-2 and go online.
2. Navigate to parameter P2040 — Field bus watchdog time.
3. Read the current value (typically 500 ms on a default-configured DP slave).
4. Set P2040 = 0 ms to deactivate the watchdog.
5. Save the parameter to non-volatile memory (RAM → ROM, "Copy RAM to ROM" in STARTER, or the save icon on the BOP-2/IOP).
6. Power-cycle the Control Unit (24 V off/on or mains off/on). The change only takes effect at boot.
7. Verify: the BF LED on the CU240S DP should extinguish within 2 s of the new boot.

4.3 Watchdog timing math

The watchdog runs on the firmware's PROFIBUS tick. If P2040 = 500 ms, the firmware starts a 500 ms timer on every received PZD and clears the timer on the next valid telegram. If the timer expires, the BF LED is forced on and — depending on P2042 — fault F01910 is raised. Setting P2040 = 0 short-circuits this check; the firmware never starts the timer, and BF can only be lit by a hard bus hardware error (broken cable with bus still terminated at the CU, for example).

5. Solution B — Set Protocol to "No Protocol" (P2030 = 0)

Setting P2030 = 0 is the cleanest resolution because it disables the PROFIBUS stack on the next boot — the firmware no longer allocates the X126 UART, no PROFIBUS driver runs, and BF cannot be lit for any reason.

1. Set the access level: P0003 = 3 (Expert).
2. Read P2030; if the parameter is read-only, the drive is in factory state. The parameter is unlocked once the drive has been commissioned at least once with STARTER or IOP, or once Expert access is enabled from the BOP-2.
3. Set P2030 = 0 (No Protocol).
4. Save (RAM → ROM) and power-cycle.
5. Verify on next boot: BF LED is OFF, RDY LED is green, and the drive responds to digital inputs at the terminal strip.

Reference: CU240S parameter list (23132008) for P2030 and the Expert-level bit assignments.

5.1 P2030 encoding

6. Decision Matrix — When to Use P2030 = 0 vs. P2040 = 0

7. Related PROFIBUS Parameters

The following parameters are commonly inspected together with P2030 and P2040 when troubleshooting the BF LED on a CU240S DP:

Refer to the SINAMICS G120 CU240S Getting Started V3.2 (31657660) for the PROFIBUS connector handling rules and the BICO routing rules that govern the send/receive word assignment.

8. Hardware-Level PROFIBUS Setup on the CU240S DP

Before concluding that the BF LED is a "no master" condition, verify the hardware:

1. DP address DIP switches (S1): Both rotary switches together form the DP address. The firmware reads the switches at boot and writes the result to P0918. If the switches are at 00 the firmware uses the value already stored in P0918 (default 126).
2. Bus termination: The CU240S DP does not include an internal PROFIBUS terminator. If the CU is the last node on a segment, install an external 9-pin D-sub terminator (220 Ω between pins 3-8 and pins 3-5 on the X126 connector) with switchable bias. Active terminators with 24 V feed (6GK1 500-0AA10) are recommended for noisy cabinets.
3. Cable shielding: The shield of the PROFIBUS cable must be bonded to the D-sub metal hood with 360° contact (EMC backshell). Loose hoods cause intermittent F01910 trips that look like the watchdog is firing randomly.
4. Baud rate: Set P2034 = 0 (auto-detect) unless the DP-Master is locked to a fixed rate. Mismatched baud rate is a common source of "BF on at power-up, then off when the master starts polling" symptoms.

Source: CU240S Operating Instructions, section "PROFIBUS DP interface".

9. Commissioning Sequence (Stand-Alone, No Bus)

For a CU240S DP that will be operated in stand-alone mode (terminals or keypad only) and that must show a dark BF LED at all times, use this sequence:

1. Set P0003 = 3 to unlock Expert access.
2. Set P2030 = 0 (No Protocol) and save RAM → ROM.
3. Set P2040 = 0 (watchdog off) as a safety measure and save.
4. Power-cycle the Control Unit.
5. Verify on next boot: BF LED is OFF, RDY LED is green (steady), and the drive responds to digital inputs at the terminal strip.
6. Run a jog command from the BOP-2 / IOP to confirm the power section is functional.
7. Record the parameter set (STARTER: File → Save project; BOP-2: STORE function) so the settings survive a firmware update or factory reset.

10. Verification Checklist

After the parameter change and power-cycle, confirm:

• BF LED: dark, even with the PROFIBUS connector removed.
• RDY LED: steady green (run-inhibit or ready, depending on ON command).
• COM LED: dark (no comm activity, expected when P2030 = 0).
• Drive response: ON command via terminal 5 (DIN0) and frequency setpoint via analog input 1 cause the motor to ramp to the commanded speed.
• Parameter persistence: power-cycle the unit twice in succession and verify the BF LED remains dark; this confirms the RAM-to-ROM save was successful.
• No spurious faults: the r0947 / r2131 buffer should be empty (no F01910, no A01910).

11. Troubleshooting Matrix

Fault code F01910 (PROFIBUS communication failure) and F08501 (PROFINET / PROFIBUS comm fault) are the two firmware-level faults that latch when the watchdog expires. Both are cleared by an OFF1 command once the bus is restored, or by setting P2040 = 0 for stand-alone operation. The reaction is governed by P2042 (0 = fault, 1 = warning).

12. Edge Cases and Field Caveats

• Read-only P2030: If P2030 is greyed out, you are at access level P0003 = 1 (Standard) or P0003 = 2 (Extended). Set P0003 = 3 and re-enter. The parameter is also locked when the drive is in commissioning state (r0007 = 2) — run the basic commissioning first, then revisit P2030.
• RAM-to-ROM: Pressing OK on the BOP-2 writes to RAM only. Use the long-press on the FN key (or the "STORE" menu) to write to ROM. Without the ROM write, P2030 / P2040 revert to their previous values on the next power cycle.
• GSD mismatch: If the PLC uses an older GSD (e.g. SIEM802D.GSD for MICROMASTER 4), the master sees a different ident number and the slave goes to BF after one watchdog cycle even though the cabling is correct. Set P2041 = 1 for MM4 compatibility or import the SINAMICS GSD into the PLC's hardware catalog.
• IOP communication lost: Setting P2030 = 0 with an IOP plugged in can confuse the panel if it expects the PROFIBUS diagnostic channel. If the IOP stops responding, cycle power once with the panel detached; the panel handshake will re-establish.
• Safety variants (CU240S DP-F): The Fail-Safe variant (6SL3244-0BA21-1PA0) has additional PROFIsafe parameters. Changing P2030 = 0 disables the PROFIsafe channel; this is acceptable for non-safety operation but invalidates the safety function — confirm with the application safety case before doing this on a safety drive.
• Power Module mismatch (6SL3351-1AE33-1AA2): The source case lists a G130-class power module with a CU240S DP. The CU240S DP is officially designed for the SINAMICS G120; using it on a G130 is outside the documented configuration. The BF LED analysis above still applies, but confirm with Siemens support that the CU firmware is compatible with the G130 power stack before any further commissioning.

13. Documentation Cross-References

• CU240S Operating Instructions (27069930) — LED definitions, commissioning menu, PROFIBUS connector pinout.
• CU240S List Manual V2.1 (24371755) — full parameter reference, including P2030, P2040, P0918, P0922, P2041, P2042.
• CU240S parameter list / compatibility note (23132008) — speed-controller optimization, F0042 trip behaviour, parameter write protection rules.
• SINAMICS G120 CU240S Getting Started V3.2 (31657660) — first-power-up flow, looped-through PROFIBUS cable, connector handling.

14. FAQ