Integrating DP/DP Coupler 6ES7158-0AD00 with PCS7 V5.1 via GSD

Problem Overview

Engineers integrating a Siemens DP/DP Coupler (order number 6ES7158-0AD00-0XA0) into a SIMATIC PCS 7 V5.1 (including service release V5.1.1) PROFIBUS DP topology will observe that the module is not selectable from the HW Config catalog while the active catalog profile is set to PCS7 V5.1. Switching the catalog profile to a generic profile such as Current Modules Version 12.200 makes the coupler visible in the catalog tree, but the compatibility question still remains: is the device released for use with PCS7 V5.1, and if it is not released as a homogeneous component, what is the supported integration path?

This article documents the engineering rationale and the field-proven GSD-based integration path for the DP/DP Coupler inside a PCS7 V5.1 plant. The procedure avoids unsupported module-specific blocks (no PCS7 message/diagnostic blocks, no WinCC faceplate) while preserving correct PROFIBUS DP cyclic data exchange between two DP masters.

Hardware Identification and Catalog Behavior

The DP/DP Coupler family is a PROFIBUS DP gateway that connects two DP networks and exposes a DP slave interface on both sides. A DP master on network 1 reads/writes process data through the coupler to a DP master on network 2, with the coupler performing transparent byte-level data transfer.

The catalog-profile filtering is a PCS7 V5.1 display behavior, not a runtime limitation. The PCS7 V5.1 PROFIBUS master stack accepts any DP slave that conforms to EN 50170 / IEC 61158, including the DP/DP Coupler, provided the slave is integrated through a GSD file (GSD = Generalized Station Description).

Root Cause: PCS7 V5.1 Catalog Profile Restrictions

PCS7 V5.1 enforces a catalog profile that lists only components formally released against the V5.1 system release notes. The PCS7 V5.1 System Description (Edition 10/2000) explicitly states that PROFIBUS DP communication is not limited to Siemens-native components:

• Section 1.3.7: communication with components from other manufacturers via PROFIBUS DP is supported.
• Section 6.1.1: the channel-granular, hardware-independent driver blocks address ET 200M, S7-400 I/O, and all standard I/O systems via PROFIBUS DP.

Because the DP/DP Coupler is a standard DP slave (no vendor-specific diagnostic frame required for cyclic I/O), it falls inside the "standard I/O via PROFIBUS DP" envelope. The catalog filter, however, omits Siemens modules that were not formally released against the V5.1 release list, so the part is hidden when the profile is PCS7 V5.1. Switching to a generic profile (Current Modules Version 12.200) lifts the filter and exposes the part, but it does not certify the part for homogeneous PCS7 use (no pre-built diagnostic block, no WinCC faceplate).

Solution: GSD-Based Integration Workflow

Integrate the DP/DP Coupler into PCS7 V5.1 as a third-party DP slave using its GSD file. The resulting integration:

• Provides correct PROFIBUS DP cyclic I/O exchange.
• Does not provide PCS7 native driver blocks, automatic diagnostic message configuration, or WinCC faceplates.
• Allows the application program to read/write the I/O area using standard SCL/ST/FBD PEW / PAW / PED / PAD accesses against the configured slot/I-addresses.

Step-by-Step Configuration Procedure

1. Obtain the GSD file. Download the Siemens GSD for the DP/DP Coupler from the official Siemens support portal (search order number 6ES7158-0AD00-0XA0 → product support → downloads → "GSD file"). The GSD filename typically matches SIEM81C9.GSD for the original release.
2. Install the GSD into HW Config. Open HW Config in the PCS7 V5.1 ES. Choose Options → Install GSD File… and browse to the downloaded SIEM81C9.GSD. Confirm the readme file dialog and allow HW Config to rebuild the catalog index.
3. Switch the catalog profile if the part is still hidden. Use Options → Catalog Profile… and select PCS7 V5.1. If the coupler still does not appear under PROFIBUS DP → Additional Field Devices → I/O, switch to Current Modules Version 12.200 for the duration of the drag-and-drop step only, then restore PCS7 V5.1.
4. Insert the coupler on the DP master system. Drag the DP/DP Coupler from the catalog onto the PCS7 V5.1 PROFIBUS DP master system. HW Config assigns it the next free PROFIBUS address; align this with the rotary DIP switches on the physical device (valid range 1–125, default 1 for PG/ES, 126 for service).
5. Configure the I/O slot. Open the coupler object properties → DP Slave Properties → Configuration Table. Define the input/output byte counts consistent with the partner network's master configuration. The DP/DP Coupler supports up to 244 bytes input + 244 bytes output per direction, configured in fixed module slots.
6. Save and compile. Save the HW Config station and run Station → Consistency Check. Then compile the PC station / S7-400 station.
7. Download to the AS. Use PLC → Download to push the new PROFIBUS configuration to the PCS7 AS (S7-400 CPU).
8. Wire the application. In the PCS7 CFC/SFC plan, instantiate channel drivers (CH_xx blocks) only if PCS7-native handling is required. For pure byte transfer, use direct peripheral access (L PED 0 / T PAD 0) inside an OB1, OB35, or a custom FB.

DP/DP Coupler Diagnostics and LED Indicators

The Helmholz manual (a compatible third-party reference for the Siemens DP/DP Coupler MLFB 6ES7158-0AD02) documents the front-panel LEDs that reflect the operational state of both PROFIBUS segments. The same LED meaning applies to the Siemens 6ES7158-0AD00 release.

Reference: DP/DP Coupler Manual (Helmholz, MLFB 6ES7158-0AD02). The manual documents GE1 (red) as "general error" and follows Siemens PROFIBUS DP slave LED conventions.

I/O Addressing and Data Consistency

After integration, HW Config assigns I-addresses and Q-addresses to the coupler slot. For a 16-byte-per-direction configuration the addresses typically appear as I 0…15 and Q 0…15 of the slave's process image partition. The application must read/write the full configured length; partial reads produce inconsistent data.

For the PCS7 application use the following ST snippet as a reference:

// OB35 cyclic read (25 ms typical PCS7 cycle)
// I/O addresses assigned by HW Config for the DP/DP Coupler slot
DATA_BLOCK DB_Coupler
  STRUCT
    In0  : BYTE;   // I 0
    In1  : BYTE;   // I 1
    Out0 : BYTE;   // Q 0
    Out1 : BYTE;   // Q 1
  END_STRUCT
END_DATA_BLOCK

// In OB1 / OB35:
L     PED    0          // load inputs from coupler (bytes 0–3)
T     DB_Coupler.In0    // store
L     PAB    0          // write outputs back
// or: read process image directly with L PIW / T PQW for 16-bit channels

Compatibility Considerations and Firmware Versions

The DP/DP Coupler is firmware-agnostic from the PCS7 master perspective: PROFIBUS DP cyclic exchange uses the standard GSD file, not the Siemens-specific "homogeneous" PCS7 add-ons. The compatibility question reduces to three engineering checks:

1. Catalog presence: the part is present in a generic HW Config profile (not the PCS7 V5.1 profile).
2. PROFIBUS DP slave conformance: the part conforms to EN 50170 / IEC 61158 DP slave behavior.
3. PCS7 V5.1 add-on support: not required for the integration path described here. If PCS7-native driver blocks, diagnostic messages, or WinCC faceplates are mandatory, escalate through the formal PCS7 release list and contact Siemens technical support.

For the equivalent current-generation reference architecture, see DP/DP coupler in the hardware catalog (TIA Portal, S7-300/S7-400/S7-1500). This reference confirms the DP/DP Coupler's role as a DP master-to-DP master gateway and applies to PCS7 V8.x / V9.x as well.

Verification and Commissioning Checks

1. Online diagnostics in HW Config: right-click the coupler in the PROFIBUS DP master system → Object Properties → Diagnostics. Confirm the slave reports OK and the cyclic I/O indicator is active.
2. LED inspection: with both networks powered and at least one DP master online on each side, all four error LEDs (GE1, GE2, BF1, BF2) must be off. The two green ON LEDs (ON1, ON2) must be lit steady.
3. Loopback test: configure the partner master to echo its outputs to its inputs. With a temporary cross-over on the coupler, confirm that the echo pattern is observed at the originating master within one PROFIBUS cycle.
4. CFC online test: force a single output byte on the originating AS, observe the corresponding input byte on the partner AS via a CFC chart online view. Repeat for the reverse direction.
5. Bus timing: at the target PROFIBUS baud rate (typically 1.5 Mbps for PCS7 V5.1 DP segments), verify the segment with a BT200 or equivalent PROFIBUS tester. The bus must show < 1 bit-time jitter on the coupler's reflected frames.

Troubleshooting Matrix