Problem Overview
When commissioning a SIMATIC S7-300 station with an integrated Profibus DP master (CPU 314C-2DP) and an ET 200B distributed I/O slave, two recurring faults appear at first power-up:
- SF/BUSF LED lit on the master, with the diagnostic buffer reporting "module configured, but not available" for the ET 200B station.
- "Transmission rate does not match the network transmission rate or wrong interrupt" error when a second slave is added to the same segment.
Both faults trace to the same class of physical-layer mistakes: incorrect Profibus termination switch positions, programming-cable termination left active, and inconsistent Profibus DP baud-rate configuration between master and slave GSD files. The remainder of this reference covers the underlying Profibus DP rules, the Siemens-specific parameters, the diagnostic workflow, and the verification sequence that brings the bus up cleanly.
Affected Hardware and Firmware
| Component | Order Number (typical) | Role | Key Specs |
|---|---|---|---|
| CPU 314C-2DP | 6ES7314-6CG03-0AB0 (or -6CH04-0AB0) | DP master (X2) and DP slave | Profibus DP-V0/V1; 9.6 kbps to 12 Mbps; 9-pin D-sub; integrated termination off by default |
| ET 200B (16 DI) | 6ES7141-1BF11-0XB0 / -1BF12-0XB0 | DP slave (IP20 / IP65/67) | Address range 1 to 125; selectable baud rate via DIL switch or auto-detect |
| CP 5611 | 6GK1561-1AA01 | PC Profibus interface | PCI card, 9-pin D-sub, integrated bus terminator (DIP switch on the card bracket) |
| Profibus connector | 6ES7972-0BA12-0XA0 (35°, with PG socket) | Bus termination | 220 Ω + 390 Ω terminator network; slide switch ON = terminator active |
| Profibus cable | 6XV1830-0EH10 (purple, FC) | Bus medium | 150 Ω nominal, 3-core shielded twisted pair, max segment length depends on baud rate |
Confirm the firmware level of the CPU 314C-2DP before commissioning. The integrated DP master on the 314C-2DP requires STEP 7 V5.4+ or TIA Portal V13+ for full diagnostic support. Firmware versions earlier than V2.6 do not support the 12 Mbps profile, and you may see "Baud rate not supported" events if the slave GSD declares 12 Mbps.
Profibus DP Termination Fundamentals
Profibus DP is a multi-drop RS-485 bus. Each segment must be terminated at exactly two points — the physical start and the physical end of the segment — with a 220 Ω resistor (combined with the 390 Ω pull-up/pull-down network inside a Profibus connector). The termination serves three purposes:
- Establishes a defined idle bus voltage of nominally 5 V between A and B lines.
- Suppresses signal reflection on the segment ends.
- Defines the DC bias so that idle bits are correctly decoded as '1'.
Siemens Profibus connectors (e.g., 6ES7972-0BA12-0XA0, 6ES7972-0BB12-0XA0) expose a slide switch labelled ON / OFF. ON inserts the terminator. The same physical arrangement is duplicated on the ET 200B module: most ET 200B variants expose a small DIL switch bank or a slide switch next to the bus connector.
1. Termination must be active at the two end nodes only — never on a middle node.
2. The terminator must be powered from the bus segment; an unpowered terminator silently loads the bus with 220 Ω to B and destroys signal integrity.
3. A Profibus programming cable that contains an integrated bus terminator (e.g., 6ES7901-4BD00-0XA0) must be set to OFF if the PG/PC is connected in the middle of a live segment.
Root Cause: "Module Configured, but Not Available"
When the master CPU reports "Module configured, but not available" (German: "Baugruppe projektiert, aber nicht vorhanden", event ID 0xE401 / 0xE402 with diagnostic interrupt), the master has a Profibus configuration in HW Config / TIA Portal device configuration that includes the ET 200B at a specific Profibus address, but the master does not see any reply from that address during the parameterization telegram cycle. The top three causes, in order of frequency, are:
- Bus termination missing or wrong — the most common cause. The slave never receives a valid frame, so it never replies, so the master never sees it.
- Profibus address mismatch — the slave is set to address 3 (via DIL switches on the ET 200B) but the master is configured to expect address 5. The master polls address 5, gets no response, and raises the diagnostic event.
- Shielding and grounding fault — the cable shield is not bonded at the cabinet entry, or the shield is continuous but not referenced to PE at both ends. Profibus requires the shield bonded to PE at every connector.
The CP 5611 programming interface is a frequent contributor when the PG/PC is left connected to the bus during commissioning. If the cable's integrated terminator (or the CP 5611 card's terminator DIP) is set to ON and the PG is connected in the middle of the segment, you have three terminators on the bus. The signal level collapses, no device can reliably frame bits, and the master reports the slave as missing. The official guidance for the CP 5611 is to leave its termination switch in the OFF position when it is used as a programming device on a live segment, and to switch it ON only when the CP 5611 is the physical end of the segment.
Root Cause: Transmission Rate Mismatch
After fixing termination, adding a second slave often surfaces a new error: "Transmission rate does not match the network transmission rate or wrong interrupt" (German: "Übertragungsgeschwindigkeit passt nicht zur Netzwerk-Übertragungsgeschwindigkeit oder falscher Interrupt"). Profibus DP only operates when all nodes on a segment agree on a single baud rate — there is no auto-baud negotiation beyond the master's "Find baud rate" service. The error is reported when:
- The newly added slave is set to a fixed baud rate (via DIL switch) that differs from the master's profile. For example, the master is configured for 1.5 Mbps in HW Config but the new ET 200B is set to its default auto-detect position, which on older firmware defaults to 9.6 kbps until a successful parameterization telegram has been received.
- The new slave's GSD file declares a maximum baud rate (e.g., 12 Mbps) that the master's firmware revision does not support. CPU 314C-2DP firmware earlier than V2.6 cannot run at 12 Mbps.
- The slave is a "DP-V1" device and the master has "DP-V1" disabled in the master's Profibus properties. The first parameterization handshake fails and the master falls back to 9.6 kbps while the slave holds at the configured rate.
| Master setting (HW Config / TIA) | Required slave GSD | Required slave DIL switch |
|---|---|---|
| 1.5 Mbps, DP-V0 | Siemens ET 200B GSD, profile DP-V0, supports up to 12 Mbps | Auto-detect (recommended) or 1.5 Mbps |
| 12 Mbps, DP-V1 | Slave GSD profile DP-V1, master set to DP-V1 | Auto-detect, slave must be DP-V1 capable |
| 187.5 kbps (P+F / hazardous area segments) | Slave GSD supports 187.5 kbps | 187.5 kbps or auto-detect |
CP 5611 Programming Interface Configuration
The CP 5611 is a PCI Profibus interface that integrates into STEP 7 and TIA Portal as the PG/PC interface. It has a small DIP switch block on the rear bracket that controls whether the card itself terminates the bus. The correct configuration depends on the role of the PG/PC in the segment:
| PG/PC connection point | CP 5611 termination | PG cable terminator |
|---|---|---|
| PG is the only node on the segment (single-node bench test) | ON | ON |
| PG is connected to the live segment end (last device) | ON | ON |
| PG is connected mid-segment between two powered nodes | OFF | OFF |
| PG connected via the master (PG socket of the Profibus connector) | OFF | OFF |
For commissioning, the recommended workflow is to keep the PG/PC on the master's PG socket (the second D-sub on the bus connector at the CPU 314C-2DP end) with the master's terminator active and the PG cable's terminator set to OFF. The CP 5611's onboard terminator is irrelevant when the PG is connected through the master because the bus connector on the master side is a passive tap, not a bus end.
To browse the live bus from the PG, use the online access function in TIA Portal. Double-click "Update accessible devices" below the CP 5611 entry in the project tree to enumerate all reachable Profibus nodes. The TIA Portal documentation describes this in the "Displaying accessible devices" online help article.
Diagnostic LED Interpretation
Both the CPU 314C-2DP and the ET 200B expose status LEDs that pinpoint the fault class. Reading them before opening STEP 7 / TIA Portal saves time.
| LED (CPU 314C-2DP) | State | Meaning | Action |
|---|---|---|---|
| SF (red, group fault) | On, steady | Diagnostic event pending, e.g. slave not reachable | Read diagnostic buffer |
| BUSF (red, Profibus fault) | On, steady | Bus short-circuit or no slave responding at the configured address | Check termination, addresses, baud rate |
| BUSF | Flashing (~0.5 Hz) | At least one slave is failing the parameterization check | Check GSD revision and DP-V0/V1 setting |
| RUN (green) | Off | CPU in STOP, no user program running | Switch to RUN after diagnostics |
| LED (ET 200B) | State | Meaning |
|---|---|---|
| BF (red, bus fault) | Flashing | Slave is on the bus, parameterization is failing (baud rate, GSD, DP-V1) |
| BF | Steady ON | Slave is offline — no parameterization telegram received at all |
| ON (green, power) | Off | No 24 V supply, or polarity reversed |
Step-by-Step Resolution Procedure
Follow this sequence in order. Do not skip to TIA Portal / STEP 7 configuration changes until the physical layer is confirmed clean — software changes will not recover a mis-terminated bus.
- De-energize the segment. Power down the CPU 314C-2DP, the ET 200B, and any repeaters on the bus.
- Identify the physical ends of the segment. Trace the purple Profibus cable from the master's X2 connector to the last device. The end nodes are the master (CPU 314C-2DP) and the last ET 200B (or any other DP device) on the chain.
-
Set termination ON at exactly those two points.
- CPU 314C-2DP: slide the bus connector's switch to ON on the connector that sits on the master's X2 socket. There is no onboard terminator on the CPU itself.
- Last ET 200B: slide its bus connector switch to ON. If the ET 200B is a B-16DI variant, the terminator is integrated — set the DIL switch on the module front to ON for the last station, OFF for every station in between.
- Verify the in-between nodes are OFF. Every ET 200B, repeater, or other DP device between the two physical ends must have its terminator switch set to OFF. A middle terminator collapses signal amplitude and causes intermittent faults that look like baud rate errors.
- Set the CP 5611 termination to OFF. If the PG/PC is connected via the master's PG socket, both the CP 5611's onboard terminator and the programming cable's terminator must be OFF.
- Re-apply power and observe LEDs. The master should show RUN (green), no SF, no BUSF. The ET 200B should show its ON (green) and no BF.
- Verify the Profibus address of every slave. On the ET 200B, the Profibus address is set by a rotary or DIL switch on the module front. Cross-check against the HW Config / TIA device configuration. A common commissioning error is leaving the default address (3) when the configuration expects address 4.
- Open TIA Portal / STEP 7 and use "Update accessible devices" on the CP 5611 interface. All configured slaves should appear in the online accessible nodes window. Reference: TIA Portal – Displaying accessible devices.
- Resolve any residual baud rate error. If the second slave raises "transmission rate does not match", open HW Config (STEP 7) or the device configuration (TIA) on the master, select the Profibus subnet, and check the "Network settings" tab. Match this rate on the slave's DIL switch if it is set to a fixed rate, or leave the slave in auto-detect (recommended for ET 200B).
- Download the hardware configuration to the CPU 314C-2DP and observe the BUSF LED — it should extinguish within two to three parameterization cycles (typically 1–2 seconds at 1.5 Mbps).
Verification and Commissioning
After the physical layer is clean and the configuration is downloaded, perform the following verification checks before placing the system in production:
- Diagnostic buffer: In TIA Portal / STEP 7, open Online & Diagnostics → Diagnostic buffer on the CPU. The buffer should not contain any new Profibus entries after a 5-minute run. If BUSF reappears, the bus is flapping — usually a loose connector, a missing shield bond, or a marginal terminator contact.
- Bus statistics (master-side): From the CPU's online diagnostics, read the Profibus statistics counters. The "Frame repeats", "Frame errors", and "Slave diagnostics" counters should be stable over time. Repeated frame errors on a specific slave indicate a marginal signal — typically a terminator problem on a neighbor device, not on the failing slave.
-
ET 200B I/O sweep: Force each input from the field side and verify it in the CPU's input process image (e.g.,
IW 0for the first word of the ET 200B-16DI). Toggle each output from the PLC program and verify field-side voltage. A clean bus shows no input chatter; a bus with a marginal terminator shows random input bits flipping at the baud rate. - Disconnect the PG and re-power. Once commissioning is complete, remove the PG cable. A common production failure is leaving the PG cable connected with its terminator ON — the bus works during commissioning and fails intermittently in production because the operator's PG cable is added to the segment.
Edge Cases and Field-Proven Caveats
Several non-obvious situations surface repeatedly on Profibus DP commissioning of S7-300 + ET 200B stations:
- Segment length vs. baud rate. The maximum segment length on Profibus DP with type-A cable (6XV1830-0EH10) is 1200 m at 9.6 kbps, 200 m at 1.5 Mbps, and 100 m at 12 Mbps. Exceeding the length budget does not surface as a hard error — it surfaces as a slow degradation in frame error rate that is invisible until the cell is in production.
- Stubs. Profibus DP supports short stubs off the main segment up to 6.6 m at 1.5 Mbps. Long stubs (1 m or more at 12 Mbps) act as unterminated transmission lines and cause intermittent framing errors. Avoid daisy-chaining off the side of a connector instead of running a continuous cable.
- Shield bonding. Profibus cable shields must be bonded to PE at every connector, at the cabinet entry, and at the field device. A shield that is continuous but not bonded at one end acts as an antenna and injects noise into the bus, which can present as "transmission rate mismatch" because the master's parameterization checksums intermittently fail.
- Repeaters count as a bus segment. A Profibus repeater (e.g., 6GK1711-1PE12-0AA0) regenerates the bus and starts a new segment. The terminator ON / OFF rules apply separately to each side of the repeater. A repeater is the only device that should have two terminators active — one on each segment it faces.
- GSD version drift. When you update the master's HW Config library or the TIA Portal hardware catalog, the slave GSD file is sometimes updated to a newer revision. Newer GSD files can change the default DP-V0/V1 setting. If a previously working slave suddenly reports "not available" after a software update, check the master's Profibus interface properties → "Operating mode" → "DP-V0/V1" toggle.
- CP 5611 versus CP 5621. The CP 5621 is the modern PCI Express successor to the CP 5611. The DIP switch convention is identical, but the CP 5621 ships with termination OFF by default. The CP 5611 ships with the DIP switch position undefined — verify the as-delivered state with a multimeter across pins 3 and 8 of the D-sub before commissioning.
Quick Reference: Termination and Baud Rate Matrix
| Node | Position on segment | Termination | Baud rate source |
|---|---|---|---|
| CPU 314C-2DP (X2) | End node 1 | ON (via bus connector) | From HW Config / TIA subnet profile |
| ET 200B #1 | Middle | OFF | Auto-detect |
| ET 200B #2 | Middle | OFF | Auto-detect |
| ET 200B #N | End node 2 | ON (DIL or connector switch) | Auto-detect |
| CP 5611 (PG) | Tap off master's PG socket | OFF | N/A — passive listener |
| Repeater port A | End of segment 1 | ON | Inherited from segment 1 master |
| Repeater port B | End of segment 2 | ON | Independent subnet, set on segment 2 master |
Frequently Asked Questions
Why does the master report "module configured, but not available" even when the ET 200B is wired and powered?
Almost always a Profibus termination fault. Verify that the terminator is active at the two physical ends of the segment and OFF on every middle node, and that the CP 5611 / programming cable terminator is OFF when the PG is connected mid-segment. The second most common cause is an ET 200B Profibus address that does not match the master's configuration.
The new slave reports "transmission rate does not match the network transmission rate" — what setting do I change?
Open the master's Profibus subnet properties in HW Config or TIA Portal and read the configured baud rate (e.g., 1.5 Mbps). Set every slave to auto-detect, or to that exact rate via its DIL switch, and re-download the configuration. If the master is at 12 Mbps, confirm the CPU 314C-2DP firmware is V2.6.0 or later — earlier firmware does not support 12 Mbps.
Should the CP 5611's onboard bus terminator be ON or OFF?
ON only when the CP 5611 is the physical end of the segment. For normal commissioning against a live S7-300 + ET 200B segment, the CP 5611 should be OFF. The PG connects through the master's PG socket, which is a passive tap that does not require termination on the CP 5611 side.
What is the maximum cable length for Profibus DP between the CPU 314C-2DP and the ET 200B?
With Profibus type-A cable (6XV1830-0EH10, 150 Ω), the limits are 1200 m at 9.6 kbps, 1000 m at 187.5 kbps, 400 m at 500 kbps, 200 m at 1.5 Mbps, and 100 m at 12 Mbps. A repeater doubles the reach for a given baud rate.
How do I confirm the bus is healthy in TIA Portal?
Open the project, navigate to Online & Diagnostics on the CPU 314C-2DP, and use Update accessible devices on the CP 5611 interface. All configured slaves appear with a green check; the diagnostic buffer shows no Profibus events; the bus statistics counters hold steady. Reference: TIA Portal – Displaying accessible devices.