Overview: The DP/DP Coupler as a Gateway
The Siemens DP/DP Coupler is a PROFIBUS DP gateway module that physically and logically separates two PROFIBUS DP networks while allowing selected process data to pass between them. On each side of the coupler, the device appears as a standard DP slave toward its attached master. Internally, the module exchanges a configured number of input and output bytes between the two segments; from the outside, every master simply sees a slave with a defined I/O footprint.
Per the official TIA Portal hardware catalog documentation for S7-300, S7-400, and S7-1500, a DP/DP coupler connects two PROFIBUS DP networks as a gateway so that "the DP master from one network can transfer data to the DP master of the other network." That gateway model is what makes multimaster bridging practical inside a single physical device, and it is the foundation for every architecture decision described in this article.
The fundamental rule of the device is short: a DP/DP coupler is a bridge between two masters. When a design calls for more than two masters to share data, the question becomes whether multiple masters can share one side of a single coupler. Field deployments confirm that the answer is yes: a single DP/DP coupler can serve multiple masters on one side, provided each master owns an independent data set within the coupler's configured I/O image.
This article focuses on a representative case: three S7-400 PLCs (each equipped with a CP 443-5 Extended) that must exchange data with a single third-party PROFIBUS DP master. The same engineering logic applies to any combination of S7-300, S7-400, and S7-1500 masters.
Architecture Decision: One Coupler or Three?
Two architectures are technically valid for the case above. Choosing between them is a trade-off between hardware cost, configuration effort, electrical isolation, and fault-domain size.
| Architecture | Hardware Required | Strengths | Trade-offs |
|---|---|---|---|
| Three independent couplers | 3 × DP/DP Coupler | Full electrical isolation between each S7-400 and the third-party network. A bus fault on one S7-400 side cannot affect the others. Independent baud rates and bus profiles per segment. | Higher hardware cost, three configuration projects to maintain, more panel space and wiring. The third-party master must address three slaves instead of one. |
| One shared coupler | 1 × DP/DP Coupler | Lowest hardware cost, single point of configuration, consistent data semantics across all three S7-400s. | Segment A becomes a shared failure domain. Any bus fault, address conflict, or removed terminator takes down all three S7-400s simultaneously. Data sets must be carefully partitioned. |
For a single shared coupler, all three S7-400 stations connect to segment A, and the third-party master connects to segment B. From the third-party master, the coupler appears as a single DP slave with one PROFIBUS address. From each S7-400 master, the coupler appears as a single DP slave on segment A with its own assigned I/O area.
Multimaster Data Exchange Model
Inside a DP/DP coupler, the module maintains a fixed maximum of input and output bytes that are exchanged between the two segments. The classic configurations support a range of data set sizes that, combined, must not exceed the coupler's total buffer. Each data set is a contiguous block of input/output words that one master on one side maps to one master on the other side.
In a three-master deployment, the partitioning is straightforward:
- Master M1 (S7-400 #1) reads and writes data set 1 on segment A. The same data set is exposed to the third-party master on segment B.
- Master M2 (S7-400 #2) reads and writes data set 2 on segment A. The same data set is exposed to the third-party master on segment B.
- Master M3 (S7-400 #3) reads and writes data set 3 on segment A. The same data set is exposed to the third-party master on segment B.
The third-party master on segment B sees all three data sets combined into a single logical slave with one PROFIBUS address and one contiguous I/O image. The internal partitioning on the S7-400 side is invisible to it, which keeps the third-party integration simple.
| Data Set | Owner (Segment A) | Consumer (Segment B) | Suggested Size |
|---|---|---|---|
| DS 1 | S7-400 #1 (Master, addr 1) | Third-party master (addr 1, slave image offset 0) | e.g., 16 bytes in / 16 bytes out |
| DS 2 | S7-400 #2 (Master, addr 2) | Third-party master (slave image offset 16) | e.g., 16 bytes in / 16 bytes out |
| DS 3 | S7-400 #3 (Master, addr 3) | Third-party master (slave image offset 32) | e.g., 16 bytes in / 16 bytes out |
Key constraints:
- Data sets must not overlap in either segment.
- The combined length of all data sets on segment A must equal the combined length on segment B; a mismatch produces a configuration fault at PROFIBUS startup.
- Each master on segment A must use a unique PROFIBUS address; the coupler itself uses two addresses, one per segment, and these must not collide with any master or slave.
- The total I/O size must fit within the coupler's maximum buffer. Older 6GK1 500-0DA00 modules support smaller totals than later variants; verify against the GSD file used.
CP 443-5 Extended vs. Integrated CPU DP Interface
Each S7-400 in this scenario can attach to segment A through either of two PROFIBUS interfaces:
| Interface Option | Module Family | Typical Use Case | Notes |
|---|---|---|---|
| CP 443-5 Extended | Communications processor in the S7-400 backplane | Offloads PROFIBUS DP traffic from the CPU; supports DP master Class 1 and Class 2 diagnostics; recommended when the CPU is heavily loaded or when an independent segment is needed for routing | Consumes one slot in the central rack; licensed and configured as a separate PROFIBUS interface |
| Integrated DP port (MPI/DP) | Built-in DP interface on CPU 412-2 DP, 414-2 DP, 414-3 PN/DP, 416-2 DP, 416-3 PN/DP, 417-4 | Reduces hardware count, eliminates a slot, lowers cost | The MPI/DP switch must be set to DP; configured in HW Config or TIA Portal device configuration |
Note also that CP 443-5 Extended requires its own PROFIBUS address on segment A and must be configured as a master in HW Config (TIA Portal: device configuration). The CPU's integrated DP port, when used as a master, requires a separate address from the CP. Plan addresses before commissioning to avoid later conflicts.
PROFIBUS Address and Bus Parameter Planning
Segment A (S7-400 side) and segment B (third-party side) each require an independent PROFIBUS address plan. The DP/DP coupler occupies one PROFIBUS address on each side; the two addresses are independent and configured separately.
| Station | Segment A Address | Segment B Address |
|---|---|---|
| S7-400 #1 (Master) | 1 | — |
| S7-400 #2 (Master) | 2 | — |
| S7-400 #3 (Master) | 3 | — |
| DP/DP Coupler (segment A view) | 32 | — |
| DP/DP Coupler (segment B view) | — | 32 |
| Third-party master | — | 1 |
| Third-party slaves (if any) | — | 10, 11, 12… |
Highest station address (HSA): Set the HSA on each segment to one address above the highest real station. This bounds the token-passing loop and shortens bus startup after a fault.
Baud rate: The two segments do not need to run at the same baud rate. The DP/DP coupler regenerates the electrical signal and can bridge between, for example, a 12 Mbit/s segment and a 1.5 Mbit/s segment. The slowest segment sets the worst-case cross-network update time, so size the third-party side baud rate to match the S7-400 polling expectation (typically 1.5 Mbit/s for cable lengths approaching the PROFIBUS maximum).
Bus parameters: Each segment must be configured with its own bus parameters (Tslot, Tset, Tqui, min TSDR, max TSDR, HSA) in STEP 7 HW Config or in the TIA Portal device & network configuration. Use the PROFIBUS bus profile "DP" on both sides unless a specific slave requires "Universal" or "User-defined." Do not mix bus profiles across the two segments without verifying that all masters accept the resulting Tslot values.
Configuring the DP/DP Coupler in TIA Portal and STEP 7
The DP/DP Coupler appears in the TIA Portal hardware catalog under Other field devices > PROFIBUS DP > Gateways > DP/DP coupler, as documented for S7-300, S7-400, and S7-1500. Reference the official documentation at the TIA Portal help URL for the exact catalog path in your installed version.
Procedure outline:
- Add the DP/DP Coupler to the project from the hardware catalog. The GSD file is bundled with TIA Portal and STEP 7; no external download is required.
- Assign the segment A PROFIBUS address and connect the coupler to segment A in the network view.
- Assign the segment B PROFIBUS address and connect the coupler to segment B in the same network view. The two addresses are configured as two separate PROFIBUS interfaces on the same device.
- Open the coupler device properties and define the data sets: for each data set, specify the number of input bytes and output bytes. The sum across all data sets must match between segment A and segment B.
- On each S7-400 master, install the coupler as a DP slave on segment A. Map the appropriate data set area into the S7-400 I/O image using the standard DP slave configuration dialog.
- On the third-party master, install the coupler as a single DP slave on segment B. Map the combined I/O image (data set 1 + data set 2 + data set 3) into the third-party controller's process image.
- Compile and download the configuration to each S7-400 station.
- Power up segment A first; verify all three S7-400 masters establish DP communication with the coupler. Then power up segment B and verify the third-party master establishes communication.
STEP 7 (Classic) users: The same workflow applies in HW Config. Insert the DP/DP Coupler from the catalog PROFIBUS DP > Other field devices > Gateways. The GSD file siem80b9.gsd or equivalent is installed with STEP 7.
Diagnostics and Status LEDs
The DP/DP Coupler provides front-panel LED diagnostics that are essential for commissioning and for first-line fault response.
| LED | State | Meaning |
|---|---|---|
| ON (Power) | Green, steady | Power supply OK |
| BF1 (Bus Fault, segment A) | Red, steady | No PROFIBUS communication on segment A (cable break, address conflict, no master active) |
| BF1 | Red, flashing | Configuration fault on segment A (data set size mismatch, GSD mismatch) |
| BF2 (Bus Fault, segment B) | Red, steady | No PROFIBUS communication on segment B |
| BF2 | Red, flashing | Configuration fault on segment B |
| SF (System Fault) | Red | Internal coupler fault; cycle power; replace unit if persistent |
On the S7-400 side, each master's diagnostic buffer records DP slave diagnostic telegrams from the coupler. Open the online diagnostic view of the coupler in TIA Portal or STEP 7 to read the standardized DP diagnostics, including station status, module status, and channel-specific diagnostics.
Common Failure Modes and Troubleshooting
| Symptom | Likely Cause | Corrective Action |
|---|---|---|
| Coupler does not appear on segment B | Missing or reversed termination, broken cable, segment B power issue | Verify termination is powered at both ends of segment B; check 9-pin D-sub wiring against PROFIBUS pinout; verify baud rate matches the third-party master |
| Data set 2 reads all zeros from M2 | PROFIBUS address conflict between M2 and the coupler on segment A, or M2 is configured as a slave instead of a master | Reassign M2 to a free address; verify master/slave role in HW Config; capture a PROFIBUS trace to confirm token passing |
| Configuration fault (BF1 or BF2 flashing) at startup | Mismatched I/O lengths between segment A and segment B; GSD revision mismatch | Match byte counts exactly in both directions; re-install the GSD on both masters and recompile |
| Sporadic bus faults when one S7-400 is stopped | Stop event corrupts token rotation; missing termination beyond the stopped station | Verify that active termination is present at the physical ends of segment A, not at a station that may be stopped; consider adding a PROFIBUS repeater with diagnosis |
| All three S7-400s lose the coupler simultaneously | Coupler power loss, segment A cable damage, or shared failure domain collapse | Check coupler ON LED; inspect segment A cabling; verify power supply capacity for the coupler |
| Cross-network data updates are slow or jittery | Mismatched baud rates; third-party master polling slower than S7-400 side | Align baud rates; verify the third-party master's cycle time; reduce total I/O if the coupler is near its buffer limit |
| Diagnostic buffer of one S7-400 reports "Station Failure" | Coupler temporarily offline; segment A disturbance | Capture the PROFIBUS trace at the time of the event; check for ESD or improper grounding near the bus cable |
Network Isolation, Termination, and Cable Considerations
The DP/DP Coupler provides galvanic isolation between segment A and segment B, but it does not isolate the segment A bus from faults introduced by any of the three S7-400 stations. The following rules apply regardless of whether one or three couplers are used:
- Termination: Segment A must be terminated at both physical ends. Active terminators are strongly recommended in multimaster segments because passive terminators rely on the station at the end of the bus being powered. If any of the three S7-400 stations may be powered down for maintenance, an active terminator at that end prevents bus collapse.
- Cable type: Use PROFIBUS cable type A (impedance 150 Ω, 3-core, shielded) for both segments. Cable type B is deprecated and should not be used for new installations.
- Shield grounding: Ground the PROFIBUS cable shield at both ends with low-impedance connections to a single ground reference. Avoid daisy-chaining shield grounds through multiple panels.
- Distance: Maximum segment length depends on baud rate. At 1.5 Mbit/s the maximum is 200 m; at 12 Mbit/s it drops to 100 m. Use repeaters if the third-party network requires longer runs.
- Connectors: Use Siemens PROFIBUS connectors with integrated termination switch (e.g., 6GK1 500-0FC10 or equivalent). Ensure the termination switch is ON only at the two end stations.
Alternative Topologies and Edge Cases
One master on each side plus slaves: The most common deployment. The master on side A polls the coupler as a slave; the master on side B does the same. The coupler appears as a slave with the configured I/O image on both segments.
Multiple masters on one side, single master on the other side: Valid, as covered in this article. Each master on the multi-master side must use a unique PROFIBUS address and own an independent data set.
Multiple masters on both sides: Not supported by a single DP/DP coupler. If two masters must coexist on segment B as well, use a second DP/DP coupler or restructure the network so that segment B becomes a single-master segment.
Master/slave role confusion: If one of the S7-400 stations is configured as a DP slave (not a master) by mistake, it will not own a data set on segment A and will not see the coupler. Verify the master/slave role of every station on segment A before commissioning.
Replacement during operation: The DP/DP coupler is a passive gateway; it has no project data of its own beyond the data set configuration stored in the GSD-installed masters. A replacement unit of the same type resumes operation after the next bus startup with no programming required. Verify behavior with a controlled hot-swap test if the plant requires live replacement.
Verification and Commissioning Checklist
- Confirm all three S7-400 stations are PROFIBUS masters on segment A with unique addresses 1, 2, 3.
- Confirm the coupler's segment A address (e.g., 32) does not collide with any master or slave on segment A.
- Confirm the third-party master address (e.g., 1) on segment B does not collide with the coupler's segment B address.
- Confirm data set byte counts match exactly between segment A and segment B in the coupler device properties.
- Power up segment A; observe BF1 LED on the coupler is OFF; observe each S7-400 online diagnostic shows the coupler as "OK."
- Power up segment B; observe BF2 LED on the coupler is OFF; observe the third-party master reports the coupler as reachable.
- From each S7-400, write a known pattern to its data set; from the third-party master, verify the pattern appears at the expected offset in the combined I/O image.
- From the third-party master, write a known pattern; from each S7-400, verify the pattern appears in its assigned data set.
- Capture a PROFIBUS trace on segment A during normal operation; verify all three masters appear in the token rotation list and that no station is being skipped.
- Capture a PROFIBUS trace on segment B; verify the third-party master and coupler exchange diagnostics cleanly with no retry storms.
TIA Portal V20 documentation: DP/DP Coupler in the hardware catalog (S7-300, S7-400, S7-1500) is the primary reference for current catalog paths, supported data set counts, and total I/O limits for the installed coupler variant.
Frequently Asked Questions
Can one DP/DP coupler connect three S7-400 multimaster networks to one third-party PROFIBUS master?
Yes. Connect all three S7-400 stations to segment A as DP masters with unique PROFIBUS addresses, and connect the third-party master to segment B. Configure three independent data sets on the coupler, one per S7-400, with matching I/O sizes on both segments. The third-party master addresses the coupler as a single DP slave.
Should I use the CP 443-5 Extended or the integrated DP port on the S7-400 CPU?
Prefer the integrated DP port on CPUs that have one (CPU 412-2 DP, 414-2 DP, 416-2 DP, 417-4) for new designs. Use the CP 443-5 Extended when the CPU is already heavily loaded, when an independent segment is required for routing, or when redundant PROFIBUS masters are needed on the same S7-400.
Do segment A and segment B need to run at the same PROFIBUS baud rate?
No. The DP/DP coupler regenerates the electrical signal and bridges between segments at different baud rates. Plan the baud rate of each segment independently based on cable length, number of stations, and the master's expected cycle time. The slower segment sets the worst-case cross-network update time.
What happens if one of the three S7-400 stations is stopped while the others continue running?
Segment A remains operational as long as the bus termination at both ends is intact and no other master drops. The two remaining S7-400 stations continue to exchange data with the third-party master through their assigned data sets. The stopped station's data set is simply not updated until it returns to run.
Why does the coupler show BF1 or BF2 flashing red at startup?
A flashing BF LED indicates a configuration fault. The most common cause is a mismatch between the data set byte counts configured for segment A and segment B in the coupler device properties. Verify that the sum of input bytes and the sum of output bytes match exactly on both segments and that the same GSD revision is installed on both masters.