Troubleshooting

PROFINET Device Shows BF Red: Fixing "No Connection" Step by Step

The ET 200SP is powered, the cable is plugged in, and BF is red. Almost always it is the device name — here is how to prove it and fix it.

· 8 min read · By TryPLC Team

  • PROFINET
  • Siemens
  • Commissioning
  • Troubleshooting

The symptom

A remote IO station (for example an ET 200SP with an IM 155-6 PN interface module) is powered and cabled. Its BF (bus fault) LED is red or flashing, and the S7-1500 diagnostic buffer reports IO device failure or device not found.

Why PROFINET is different

A PROFINET controller does not find devices by IP address. It finds them by device name (for example et200sp-conveyor-1). At startup the controller asks the network "who is called et200sp-conveyor-1?" through DCP, then assigns the IP address itself. A brand-new or replaced device has no name, so nobody answers.

That is why "the IP is correct" proves nothing on PROFINET.

Step 1 — Read the LEDs precisely

  • BF flashing: the device has link but no controller connection — usually name or configuration mismatch.
  • BF steady red with no link LED: physical problem. Check the cable, the port and the switch.
  • Link/activity LED off: no Ethernet link at all. Swap the patch cable and try another port.

    • Step 2 — Check the name online

    In TIA Portal, use Online access → Update accessible devices on the network adapter connected to the plant network. Each device lists its name, IP and MAC. Compare the listed name, character for character, with the name in the hardware configuration. Common errors: missing name, a typo, a hyphen versus underscore, or the device still having its previous machine's name.

    Step 3 — Assign the name

    Select the device in the network view and use Assign device name. Identify the correct physical device by its MAC address (printed on the module) or by using Flash LED. Once the name matches, the controller assigns the IP and BF should go off within seconds.

    On a replacement, consider enabling device replacement without exchangeable medium: with topology configured, the controller names a new device automatically from its port neighbour.

    Step 4 — Check the configuration matches the hardware

    If BF stays red after naming, the controller connects but rejects the configuration. Look for:

  • Wrong interface module article number or firmware version in the project.
  • Modules plugged in a different order from the configuration.
  • An outdated GSDML file for third-party devices. Install the version that matches the device firmware.

    • Step 5 — Topology and duplicate names

    If topology is configured, a cable moved to a different port triggers a topology error. Either restore the cable or update the topology. Two devices with the same name give intermittent failures: rename one.

    Takeaway

    On PROFINET, check name first, configuration second, IP last. Explore the device lifecycle in the PROFINET lesson.

    Frequently asked questions

    What does a flashing BF LED mean on PROFINET?

    The device has an Ethernet link but no connection to its IO controller, most often because the device name is missing or does not match the project.

    Does PROFINET use the IP address to find devices?

    No. The controller identifies devices by device name via DCP and then assigns the configured IP address.