Troubleshooting Profibus Routing Siemens CPU 414-2, ET 200M

David Krause14 min read
Industrial NetworkingSiemensTroubleshooting
Licensed PE Working through this on a live machine? A Maine-licensed engineer can take it from here — included with IMD hardware, by the hour for everything else. Book an engineer

1. System Overview and Typical Failure Mode

A common commissioning scenario pairs a SIMATIC S7-400 CPU 414-2 with a distributed ET 200M station on Profibus DP and a MP 377 Multi Panel for HMI. When the programming device (PG/PC), the PLC, the ET 200M, and the panel are all connected on different physical networks, transfers from WinCC Flexible 2008 SP2 fail with the dialog "Enable routing" not appearing, the touch panel stays unreachable, or the CPU reports a BUSF (Bus Fault) and EXTF (External Fault) LED combination. The root cause in nearly every case is not a cable, hardware, or Profibus termination problem but a misconfigured PG/PC interface assignment in the SIMATIC Manager combined with missing NetPro routing entries.

The architecture most often described is:

  • S7-400 CPU 414-2 with the integrated Profibus DP master (interface X2) on the Profibus segment.
  • ET 200M with an IM 153-1 / IM 153-2 / IM 153-4 interface module as a Profibus DP slave on the same segment.
  • MP 377 15" Touch (6AV6 644-...) either on Profibus (rare) or on Ethernet (recommended).
  • PG/PC with a CP 5611 / CP 5613 / CP 5711 Profibus card and an Ethernet card for TCP/IP.
  • A CP 443-1 (e.g., 6GK7 443-1EX11) Ethernet communications processor providing the routing gateway between the engineering subnet and the Profibus subnet.
Important architectural rule: The CPU 414-2 itself only contains an integrated Profibus interface on the DP side. To route between Ethernet (where WinCC Flexible / PG/PC lives) and Profibus DP (where the MP 377 and ET 200M live), the CP 443-1 must be inserted into the S7-400 rack and added as a routed node in NetPro. Without the CP, WinCC Flexible cannot "hop" from the Ethernet side into the Profibus side.

2. Hardware Identification and Module Part Numbers

Confirm the exact catalog numbers before commissioning, because LED behavior, Profibus diagnostics buffer text, and supported GSD revisions all vary by hardware release.

Module Typical Order Number Function
CPU 414-2 (firmware V4/V5/V6) 6ES7414-2XK05-0AB0 / 6ES7414-2XN05-0AB0 Profibus DP master (X2), MPI (X1)
CP 443-1 (Industrial Ethernet) 6GK7443-1EX11-0XE0 / 6GK7443-1GX11-0XE0 TCP/IP routing gateway to Ethernet
ET 200M IM 153-1 6ES7153-1AA03-0XB0 DP slave interface, simple
ET 200M IM 153-2 6ES7153-2BA10-0XB0 DP slave interface, redundant, FO capable
ET 200M IM 153-4 PN 6ES7153-4BA00-0XB0 Profinet IO device interface
MP 377 15" Touch 6AV6644-2AB01 / 6AV6644-2AC01 HMI device, Profibus DP or Ethernet
PG/PC Profibus card CP 5611 (6GK1561-1AA01), CP 5613, CP 5711 Profibus master for programming

ET 200M uses the I/O module catalog of the S7-300 automation system (SM 321 / SM 322 / SM 331 / SM 332 / SM 334 / FM / CP). For full configuration guidance see the Siemens documentation for ET 200M configuration in TIA Portal.

3. Decoding the BUSF and EXTF LED Patterns

On an S7-400 CPU, the front-panel LEDs are the fastest way to localize a Profibus problem before opening the diagnostics buffer.

LED Color / State Meaning in this Configuration
BUSF flashing Red, 0.5 Hz At least one configured DP slave is not reachable (timed out). Most common cause: ET 200M IM 153 or MP 377 is not on the bus, wrong Profibus address, or duplicate address.
BUSF on steady Red, static Profibus physical layer fault: broken segment, missing terminator, short, or reflection.
EXTF on Red, static External / I/O fault; entries exist in the CPU diagnostics buffer (e.g., station failure, diagnostic interrupt from ET 200M, OB82/OB86 not loaded).
BF on ET 200M IM 153 Red IM has no Profibus connection (no token from master, wrong baud rate, missing terminator, or wrong GSD).
SF on ET 200M IM 153 Red Module-level diagnostics (24 V missing, channel fault, configuration mismatch).

When the engineer sees BUSF flashing with EXTF on on the CPU and no BF on the ET 200M, the affected slave is almost always the MP 377 panel (because it is the only Profibus node that is not properly initialized in the project).

A missing OB82 (diagnostic interrupt), OB86 (rack/DP station failure), or OB122 (I/O access error) causes the CPU to enter STOP on the first DP station failure. If the S7 program must keep running, load the standard Siemens "empty" OBs from the Standard Library under S7 Program > Standard Library > Empty OB.

4. Root Cause Analysis: Why "Enable Routing" Disappears

WinCC Flexible 2008 / TIA Portal shows the "Use routing" check box in the transfer dialog only when three preconditions are simultaneously met:

  1. PG/PC interface (S7ONLINE access point) is bound to a TCP/IP-capable Ethernet card, not to a Profibus CP and not to an ISO protocol.
  2. NetPro contains a valid subnet gateway relationship from the PG/PC's Ethernet subnet, through the CP 443-1, to the Profibus subnet where the MP 377 lives.
  3. The WinCC Flexible project has the HMI station connected over the same subnet as the PG/PC or via a routable gateway; otherwise the routing check box is suppressed.

If the engineer assigns the Profibus CP (CP 5611 / CP 5613) to S7ONLINE with the ISO protocol, the routing tick box never appears because the routing logic is a property of the TCP/IP stack. Likewise, setting the CP 5611 as PC internal while the Ethernet is selected as the active interface hides the routing path. Switching the access point assignment and protocol clears the symptom in roughly 90 percent of the cases reported.

5. PG/PC Interface Configuration (S7ONLINE Access Point)

The single highest-leverage setting in the whole setup is the PG/PC interface assignment. Use the Windows control panel applet "Set PG/PC Interface" (in SIMATIC Manager: menu Options > Set PG/PC Interface).

Parameter Required Value Common Wrong Value
Access point of the application S7ONLINE (left blank)
Interface parameterization used TCP/IP → <Ethernet NIC> CP 5611 (ISO), CP 5613 (ISO), PC internal (local)
MAC / IP of NIC Matches WinCC project PG/PC station Wrong subnet or DHCP not refreshed
Firewall Allow port 102 (ISO-on-TCP), port 50000 (WinCC Flex transfer) Windows firewall blocking Siemens
  1. Open Start > SIMATIC > SIMATIC Manager > Options > Set PG/PC Interface.
  2. For Application access point: select S7ONLINE.
  3. For Interface parameterization used: select TCP/IP → <your Ethernet NIC>.
  4. Click OK, close the dialog, and restart WinCC Flexible Transfer.
Misconception: "Set MAC addresses use ISO protocol" was a legacy option for older SIMATIC NET drivers. It must be removed on every station in NetPro, otherwise the routing handshake fails even with the correct PG/PC interface.

6. NetPro Routing Configuration

Routing is configured graphically in NetPro within the SIMATIC Manager. The CPU, CP 443-1, MP 377, ET 200M, and PG/PC station must all live in the same STEP 7 project, and each subnet must be connected with subnet gateway relationships.

  1. In HW Config, drag a CP 443-1 into the S7-400 rack and configure its IP address and Ethernet subnet. Connect it to a new or existing Ethernet subnet object.
  2. Open NetPro (the button next to HW Config) and verify that the CP 443-1 port is connected by a line to the Ethernet subnet, and the CPU's Profibus port is connected to the Profibus subnet.
  3. Drag the MP 377 from the hardware catalog into the Profibus subnet (or the Ethernet subnet if migrating to Ethernet).
  4. Drag the ET 200M into the Profibus subnet and assign a unique DP address.
  5. Add the PG/PC station and assign it to the Ethernet subnet with the same TCP/IP driver as in Set PG/PC Interface.
  6. Right-click each network connection and confirm that Properties > Options shows the "Router" entries pointing at the CP 443-1 (i.e., the CP is the gateway).
  7. Compile and download NetPro to the S7-400 station (PLC > Download > to Target System).

Without these steps, WinCC Flexible sees the MP 377 as off-net and refuses to offer routing.

7. ET 200M with IM 153-x: Profibus Slave Setup

The ET 200M takes the place of a remote rack on Profibus. Configuration steps:

  1. From the hardware catalog select PROFIBUS DP > ET 200M > IM 153-1 / IM 153-2.
  2. Drag it onto the Profibus subnet in HW Config or NetPro.
  3. Assign a DP address that is unique on the segment (default is 3; avoid address 0, 1, 2 reserved by the master).
  4. Plug the same module types (SM 321 DI, SM 322 DO, SM 331 AI, SM 332 AO) into the IM 153 slots that are physically mounted in the field.
  5. Match the IM 153 hardware version with the GSD file used; mismatches trigger SF on the IM and EXTF on the CPU.

Detailed topology is documented in the Siemens reference for connecting an ET 200M to a STEP 7 project and in ET 200M configuration.

8. MP 377 Transfer Mode and IP Configuration

The MP 377 has two transfer paths: Profibus DP at the panel's PROFIBUS port, or Ethernet at the panel's LAN port. For Ethernet transfer:

  1. Power up the MP 377 and enter the Control Panel: Start > Settings > Control Panel.
  2. Tap Transfer and ensure Enable Channel is on, Remote Control is on, and the timeout is non-zero.
  3. Open S7 Transfer Settings and pick Ethernet (TCP/IP).
  4. Open Network & Dial-up Connections > LAN and configure a static IP in the same subnet as the CP 443-1 and PG/PC (e.g., 192.168.0.40 / 255.255.255.0).
  5. From the PG/PC run ping 192.168.0.40. If ping fails, the panel is offline.
  6. Force the panel into transfer mode either by selecting Transfer in the loader, or by ticking Remote Control in the Control Panel so the HMI accepts the transfer from WinCC Flexible automatically.

For Profibus DP transfer, set the panel's Profibus address and baud rate to match the CPU 414-2 (typically 1.5 Mbit/s) and ensure the DP cable is terminated at both ends (ON / OFF switch on the panel's Profibus connector).

9. WinCC Flexible Transfer Procedure with Routing

Once the S7ONLINE access point is TCP/IP and NetPro has the CP 443-1 routed to Profibus:

  1. Open WinCC Flexible 2008 SP2 and load the project.
  2. Select Project > Transfer > Transfer Settings.
  3. Choose Ethernet as the mode and enter the MP 377's IP address.
  4. Tick Enable routing — this is the check box that previously did not appear.
  5. Tick Display all accessible nodes and click Search. The MP 377 should appear even though it sits behind the CP 443-1 on a Profibus subnet.
  6. Select the panel and click Transfer.
Symptom: "not all the components have been downloaded in the RTM module set RTM installed in object properties of SIMATIC HMI station." This message means the WinCC project and the STEP 7 project have been integrated into each other but the RTM (Runtime Module) component has not been recompiled and downloaded. Solution: Project > Compiler > Compile and check all (Rebuild All), then retransfer. The RTM is the runtime parts catalog required for the MP 377 to load.

10. Why Ethernet Is Preferred over Profibus for the MP 377

Putting the MP 377 on Ethernet instead of Profibus DP solves the routing problem and improves performance.

Criterion Profibus DP Ethernet (TCP/IP)
Update time 5 ms – 50 ms per DP slave, depends on TTR 10 ms – 100 ms, independent of DP segment
Engineering complexity Requires DP address, GSD, Profibus topology Requires IP, gateway, subnet
Routing required from PG/PC? Yes, routing across CP 443-1 mandatory Only if PG/PC is on a different subnet
Effect on ET 200M DP cycle Adds DP cycle load via panel polling None — panel traffic stays off Profibus
Recommended by Siemens Legacy systems New projects and retrofits

Because the panel polls many tags per second, putting it on Profibus extends the DP cycle and can push the ET 200M beyond its target update time. Ethernet isolates that traffic.

11. Step-by-Step Commissioning Procedure

Use this ordered procedure to take a project from "blank" to "running".

  1. Build hardware: Insert CPU 414-2, CP 443-1, ET 200M (IM 153-x), and MP 377 in HW Config.
  2. Configure Profibus: assign the DP master system, set the baud rate (1.5 Mbit/s), and assign DP addresses (CPU default 2, ET 200M e.g., 3, MP 377 e.g., 4).
  3. Configure Ethernet: set the CP 443-1 IP, MP 377 IP, and PG/PC IP in the same subnet.
  4. Build NetPro: drag all stations onto the correct subnets and verify that the CP 443-1 routes from Ethernet to Profibus.
  5. Integrate the WinCC Flexible project into the STEP 7 project (Options > WinCC Flexible Integration in SIMATIC Manager).
  6. Compile and download both the STEP 7 station (with NetPro) and the HMI station. If RTM errors appear, rebuild all.
  7. Set PG/PC interface: S7ONLINE = TCP/IP → Ethernet NIC.
  8. Enable transfer mode on the MP 377 and ping its IP from the PG/PC.
  9. Transfer WinCC with Enable routing ticked.
  10. Verify I/O: monitor the ET 200M inputs in a VAT table and confirm BUSF / EXTF LEDs on the CPU are off.

12. Verification Checklist

Check Expected Result How to Verify
PG/PC → MP 377 ping Reply < 1 ms, 0% loss cmd > ping <MP377_IP> -t
Accessible nodes in WinCC Flex MP 377 visible WinCC Flex → Transfer → Show accessible nodes
CPU BUSF Off CPU front panel LED
CPU EXTF Off CPU front panel LED
ET 200M BF / SF Off IM 153 front panel LED
CP 443-1 RUN / LINK Green steady / green flick CP front panel LEDs
OB82 / OB86 / OB122 loaded Yes STEP 7 → Blocks container
CPU diagnostics buffer free of DP errors Yes STEP 7 → PLC → Online → Diagnostics Buffer
Profibus terminator ON at both ends ON / OFF switch correct Visual inspection

13. Troubleshooting Matrix

Symptom Likely Cause Action
"Enable routing" missing in transfer dialog S7ONLINE = ISO Profibus Switch S7ONLINE to TCP/IP → Ethernet NIC
CPU BUSF flashing, ET 200M BF off, MP 377 BF on MP 377 not on Profibus Check DP address, baud rate, terminator, cable
RTM error during NetPro download WinCC project not recompiled Compile all + transfer WinCC project again
Cannot ping MP 377 Wrong IP / wrong subnet / firewall Set static IP, disable Win firewall rule, cross-cable test
CPU EXTF on but no DP error in buffer OB82 / OB86 missing Load empty OB82, OB86, OB122 from Standard Library
ET 200M SF on, no BF I/O module missing 24 V or wrong config Check 24 V, compare modules vs HW Config
WinCC Flex transfer starts, then aborts Wrong HMI transfer channel Enable Ethernet channel in MP 377 Control Panel
Accessible nodes lists wrong PG/PC PG/PC station not in NetPro Add PG/PC station with same IP as Ethernet NIC

14. Recommended Best Practices

  • Always migrate the MP 377 to Ethernet unless a Profibus cable is already part of an approved installation plan.
  • Use a single CP 443-1 as the routing gateway; do not add multiple Ethernet CPs unless required for redundancy.
  • Always load empty OBs (OB82, OB86, OB121, OB122) into the S7-400 program so DP diagnostics do not STOP the CPU.
  • Pin the PG/PC's Ethernet IP to a fixed value rather than DHCP to make NetPro and WinCC consistent.
  • Document Profibus addresses in a label on the panel and IM 153; mismatched addresses are the single most common commissioning error.
  • When migrating between STEP 7 / WinCC Flexible 2008 SP2 and TIA Portal, recreate NetPro rather than copy-paste; the routing data structures changed.

Why does the "Enable routing" check box not appear in WinCC Flexible 2008?

The check box only appears when the PG/PC's S7ONLINE access point is bound to a TCP/IP Ethernet driver. If it is bound to a CP 5611/CP 5613 Profibus card in ISO mode or to "PC internal", the routing check box is suppressed. Open Options > Set PG/PC Interface and set S7ONLINE to TCP/IP → <Ethernet NIC>.

What does BUSF flashing plus EXTF on mean on a CPU 414-2?

BUSF flashing means at least one configured DP slave is unreachable (timed out), and EXTF means an external diagnostics event was logged. Combined, they almost always point at a missing Profibus slave — commonly the MP 377 if the ET 200M has no BF. Open the CPU diagnostics buffer to identify which slave address failed and check the cable, terminator, and DP address.

Can WinCC Flexible transfer reach an MP 377 on Profibus through a CP 443-1?

Yes, provided the CP 443-1 is inserted in the S7-400 rack and the NetPro routing table connects the Ethernet subnet to the Profibus subnet. The PG/PC must be on the Ethernet subnet and S7ONLINE must be TCP/IP. Ticking "Enable routing" in the WinCC Flexible transfer dialog then forwards the transfer through the CP 443-1 into the Profibus segment.

How do I fix "not all components have been downloaded in the RTM module set"?

Recompile the WinCC Flexible project from scratch (Project > Compiler > Compile and check all (Rebuild All)) and retransfer. The RTM (Runtime Module) is a catalog component that must be regenerated whenever the integration with STEP 7 changes. Restarting WinCC Flexible after the rebuild forces a clean load.

Why does the MP 377 stay offline even though ping works?

Ping only confirms the IP stack. Transfer mode also requires Enable Channel and Remote Control in the panel's Control Panel under Transfer. Without Remote Control, the panel ignores inbound transfer requests. After enabling it, manually trigger Transfer in the loader or click Transfer in WinCC Flexible; the panel should switch to transfer mode and complete the download.

Back to blog