Configuring S7-400H to Yokogawa CS3000 via PROFIBUS DP

David Krause14 min read
ProfibusSiemensTutorial / How-to
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

Integration Overview

Interfacing a Siemens SIMATIC S7-400H redundant controller with a Yokogawa CENTUM CS 3000 distributed control system over PROFIBUS DP is a common requirement in hybrid plants where Siemens PLC subsystems handle discrete/batch interlocks and Yokogawa DCS layers handle continuous regulatory control. The CPU 414-4H (order number 6ES7 414-4HJ04-0AB0) ships with an integrated PROFIBUS DP interface (IF1, MPI/DP) that can be configured as a DP Master (Class 1) per EN 50170. Yokogawa's CENTUM CS 3000, built on the Windows NT operation/monitoring platform, supports PROFIBUS DP through dedicated field control station modules.

The core architectural problem is that both controllers want to be DP Masters - the S7-414-4H CPU is a DP Master by default and the Yokogawa PROFIBUS interface module is also a DP Master. A PROFIBUS segment allows exactly one active Class 1 master, so the two masters must be coupled through a DP/DP Link coupler rather than connected to a common bus. The coupler isolates the two masters, replicates the input image from one side into the output image of the other, and provides galvanic isolation between the segments.

System Components and Prerequisites

Component Specification / Order Number Notes
Siemens CPU 6ES7 414-4HJ04-0AB0 (S7-414-4H) Firmware V4.x or later; integrated DP interface on X1
Siemens DP/DP Link 6ES7 158-0AD01-0XA0 (or current variant) Coupler, 2 x PROFIBUS DP interfaces, max 244 bytes input + 244 bytes output per direction
STEP 7 V5.5 + SPx (or TIA Portal V15.1+ for S7-400) HW Config required for DP master configuration
Yokogawa CENTUM CS 3000 VP/NP station, FCS, or AFV30-V card cage Windows NT-based HMI; field control station hosts PROFIBUS module
Yokogawa PROFIBUS Module ALP121 (or equivalent PIO/PROFIBUS card) DP Master (Class 1) capable; GSD file required
GSD File (Yokogawa side) YOKO0xxx.GSD Provided by Yokogawa; install via HW Config > Options > Install GSD
PROFIBUS Cable 6XV1 830-0EH10 (Siemens) or equivalent Shielded twisted pair, characteristic impedance 150 Ω
Connectors 6GK1 500-0EA02 (with PG port) or 6ES7 972-0BA52-0XA0 Terminating resistors ON at both line ends only
Verify the Yokogawa CS 3000 PROFIBUS module catalog number against the Yokogawa project documentation. ALP121 is a representative part; the exact module, revision, and DP firmware version determine the GSD revision and the maximum number of cyclic slots.

PROFIBUS DP Master-to-Master Architecture

PROFIBUS DP defines three device classes: DP Master Class 1 (DPM1), DP Master Class 2 (DPM2, used for configuration/diagnostics), and DP Slave. In a single segment, only one DPM1 may be active at a time. When two controllers must exchange data, three viable topologies exist:

  1. Single-master, single-slave: One controller is DPM1, the other is a DP slave. Both retain the role asymmetry; one cannot be a master on its own bus. Not applicable here because both sides are designed as masters.
  2. DP/DP Link coupler (recommended): Each side sees the coupler as a slave on its own segment. The coupler buffers up to 244 input and 244 output bytes per direction and mirrors them across the two electrically isolated segments. Each side retains its full master status on its own bus and is unaware of the topology beyond the link.
  3. Direct master-master via FMS/FDL: Historically possible with FMS services, but FMS is largely deprecated in favor of DP and is not supported by the S7-414-4H integrated DP port.

The DP/DP Link is the only solution that preserves native DP behavior on both sides and works with the standard Yokogawa PROFIBUS module.

DP/DP Link Coupler Selection and Wiring

The Siemens DP/DP Link (e.g., 6ES7 158-0AD01-0XA0) is a standalone DIN-rail module. It contains two electrically isolated DP interfaces (X1 and X2), each presenting as a DP slave to the connected master. Configuration is performed via the DIP switches on the front of the device - no programming tool is required. The total transfer capacity is 244 input bytes and 244 output bytes per direction. Data is mirrored from the inputs of one segment to the outputs of the other and vice versa.

Wiring Topology

S7-414-4H CPU6ES7 414-4HJ04-0AB0DP Master (X1)DP/DP Link6ES7 158-0AD01244/244 bytesYokogawa CS3000ALP121 PROFIBUSDP MasterSegment 1 (master)Segment 2 (master)Each segment: independent baud rate, independent master, electrically isolated

Connect the S7-414-4H X1 (DP) port to the DP/DP Link's X1 (or X2 - the link's two ports are identical). Connect the Yokogawa ALP121 PROFIBUS port to the other DP/DP Link port. Enable terminating resistors only at the two physical line ends (one per segment). The DP/DP Link supplies internal bus termination if the segment is short and only the coupler is on that segment, but in practice the S7-400 and Yokogawa module remain the line ends, and the link sits in the middle with termination off.

STEP 7 Hardware Configuration

Step 1 - Configure the S7-414-4H DP interface

Open the SIMATIC Manager, load the S7-400H station, and open HW Config. Double-click the CPU 414-4H, select the DP tab, and click Properties on the integrated DP interface. Configure:

  • Interface: PROFIBUS
  • Address: e.g. 2 (must be unique on the segment)
  • Subnet: Create a new PROFIBUS subnet, e.g. "PROFIBUS(1)"
  • Highest PROFIBUS address: 126 (default)
  • Profile: DP
  • Mode: DP Master

Step 2 - Add the DP/DP Link as a slave

In the PROFIBUS DP catalog, expand Additional Field Devices > Gateway > DP/DP Link. Drag the DP/DP Link onto the PROFIBUS(1) subnet. Assign it slave address 3 (any unused address). Right-click the link symbol, open Properties > DP Slave Configuration, and define the slot mapping. Each slot corresponds to one byte of input and one byte of output as seen from the S7-414-4H side.

Step 3 - Configure slot consistency

Critical decision: how much data per slot and at what consistency level.

Total bytes per direction Slot configuration Consistency SFCs required
1 - 2 bytes 1 x I, 1 x O, 1 byte each Byte / Word No (direct I/O access)
3 bytes Cannot split; use 1 x 3 bytes Unit (3) Yes (SFC14/15)
4 bytes 1 x I, 1 x O, 4 bytes Word / DWord (Unit 4) Optional (recommended)
5 - 32 bytes 1 x I, 1 x O, consistent over full length Unit (whole) Yes (SFC14/15)
33 - 244 bytes Multiple slots, each up to 32 bytes Unit per slot Yes (SFC14/15) per slot

Rule: If any data block exceeds 4 bytes, or if a block is 3 bytes, the read/write must use SFC14 (DPRD_DAT) for reading and SFC15 (DPWR_DAT) for writing. These block transfers handle the consistency over the entire DP cycle. Reading and writing the process image directly (L PIW / T PQW) only works for byte/word/dword up to 4 bytes and is consistent within the OB1 scan only when the data fits into a single I/O update.

GSD File Installation and Slot Mapping

For the Yokogawa side, obtain the GSD file shipped with the ALP121 module (Yokogawa typically provides it on the installation DVD or the Yokogawa download portal). In HW Config, choose Options > Install GSD File and select the file. The Yokogawa module then appears in the catalog under PROFIBUS DP > Other Field Devices > Yokogawa. The GSD describes the available I/O modules (digital in/out, analog in/out) and their consistency behavior.

The Yokogawa CS 3000 PROFIBUS master must be configured with matching slot data. Any mismatch between the slots defined in STEP 7 (S7 side) and the Yokogawa CENTUM Builder (Yokogawa side) produces a DP configuration error and the slave will not enter cyclic data exchange.

SFC14/15 Consistent Data Programming

For slot data larger than 4 bytes (or equal to 3), use the standard SFCs in OB1 or a dedicated OB (for time-critical data, OB35 at 100 ms is common).

Reading from the Yokogawa side (inputs from DP/DP Link)

// STL example - read 32 bytes of consistent data
// LADDR  = I/O start address from HW Config (e.g. 256)
// RET_VAL= error code returned by SFC
// RECORD = destination DB area (must match length)

CALL  "DPRD_DAT"
     LADDR  := W#16#100      // 256 decimal, from HW Config slot 0
     RET_VAL := MW100        // 0 = OK; see error table below
     RECORD := P#DB20.DBX0.0 BYTE 32

// Evaluate RET_VAL
L     MW100
L     0
==I
JC    ok
// non-zero: see SFC14 error code table
ok: NOP 0

Writing to the Yokogawa side (outputs to DP/DP Link)

CALL  "DPWR_DAT"
     LADDR  := W#16#110      // 272 decimal, outputs from HW Config
     RECORD := P#DB21.DBX0.0 BYTE 32
     RET_VAL := MW102

Structured Text (SCL) alternative

// FB block-style wrapper - call in OB1
IF #bInit THEN
   #iStatusRead := DPRD_DAT(LADDR := #wInAddr,
                            RECORD := #tRxArea);
   #iStatusWrite := DPWR_DAT(LADDR := #wOutAddr,
                             RECORD := #tTxArea);
END_IF;

// Common pattern: re-trigger every OB1 pass for steady exchange
DPRD_DAT(LADDR := 16#100, RET_VAL := #iStatusRead, RECORD := #tRxArea);
DPWR_DAT(LADDR := 16#110, RET_VAL := #iStatusWrite, RECORD := #tTxArea);

SFC14/15 RET_VAL error codes

RET_VAL (hex) Meaning Remedy
0000 No error Continue
8090 Addressed module does not exist / wrong base address Verify LADDR against HW Config slot start
8092 DP protocol error at the slave / link Check link power, wiring, terminating resistors
8093 DP protocol error: data length mismatch Slot data length in HW Config must match partner configuration
80A0 Access error - slave not in data exchange Slave diagnostics: address conflict, baud rate, GSD mismatch
80B0 SFC call not permitted in current OB priority Move SFC to OB1 / OB35 (not OB100/OB101 startup)
80B1 Length of RECORD parameter exceeds user data length Reduce RECORD length to slot size
80B2 System error (resource) Reduce SFC14/15 call rate; check CPU utilization
80C0 Data not yet readable from slave Initialize on first scan; add retry logic
80C2 Short-circuit / bus fault Inspect cable, shield, connectors, termination

Bus Parameter Calculation

When two masters are coupled via a DP/DP Link, each segment is independent - baud rate, slot time, and rotation time can differ between them. The link buffers and re-issues frames, so a slow Yokogawa segment (e.g. 1.5 Mbit/s) and a fast Siemens segment (e.g. 12 Mbit/s) coexist without issue. However, each segment must be tuned to its own set of slaves.

Key parameters (set in HW Config > Properties > PROFIBUS > Network Settings)

Parameter Description Typical value at 1.5 Mbit/s Typical value at 12 Mbit/s
Baud rate Bus transmission speed 1.5 Mbit/s 12 Mbit/s
Tslot Slot time - max time to wait for a slave response 300 Tbit 30 Tbit
Max Tsdr Max station delay of responders 150 Tbit 15 Tbit
Min Tsdr Min station delay of responders 11 Tbit 11 Tbit
Tset Setup time 1 Tbit 1 Tbit
Tqui Quiet time (modulator settle) 0 Tbit 0 Tbit
Gap factor Idle time between tokens 10 10
HSA Highest station address 126 126

Tbit at 1.5 Mbit/s = 0.667 µs. Tbit at 12 Mbit/s = 0.0833 µs. For each additional slave, the cycle time grows by approximately the slot time plus the telegram length. Use the bus parameter diagnostic in HW Config (PROFIBUS > Bus Diagnostics) to verify the calculated cycle time stays well below the CPU scan time (a 100 ms cycle budget leaves generous margin).

Yokogawa CENTUM CS 3000 PROFIBUS Setup

On the Yokogawa side, the PROFIBUS module is configured inside the CENTUM Builder engineering tool. The CS 3000 architecture is built on Windows NT for HMI components and the VP/NP station for operation/monitoring; the PROFIBUS master module resides in the field control station (FCS) and acts as a Class 1 DP master over its segment. Reference the Yokogawa technical report on the CS 3000 system architecture for the overall network topology and the Yokogawa Technical Information TI33Q01B10-01E for migration and field controller details.

  1. Create a PROFIBUS subnet in CENTUM Builder matching the physical segment.
  2. Insert the DP/DP Link as a Yokogawa-side slave (address must match the address set on the link's DIP switches and the address set in STEP 7 - they are different addresses on the two segments, but the link is one device, not two).
  3. Define input and output modules in the Yokogawa configuration with the same byte/word counts and consistency as in STEP 7.
  4. Build and download the configuration to the FCS.
The DP/DP Link's two segments are independent. The address on the Siemens side (e.g. 3) is the address the Siemens master uses to reach the link. The address on the Yokogawa side (e.g. 4) is the address the Yokogawa master uses to reach the link. Both addresses are set on the link via its DIP switches and must agree with the engineering tools on the respective sides.

Verification and Diagnostics

  1. Physical layer: Verify the link LED on each DP/DP Link port is solid green (cyclic exchange). Verify LEDs on the S7-414-4H X1 port and on the Yokogawa ALP121 module.
  2. STEP 7 online diagnostics: In HW Config, right-click the DP/DP Link slave and choose DP Slave Diagnostics. Confirm the slave is in Data Exchange state and the slot configuration matches the engineering.
  3. Buffer the SFC14 return value: Capture MW100/MW102 into a status DB and trend in WinCC or HMI to confirm 0000 (no error) under steady state and 0000 immediately after Yokogawa FCS restart (re-establishment within one DP cycle).
  4. Yokogawa side: View the PROFIBUS diagnostic in CENTUM Builder; verify the DP/DP Link is in Data Exchange and all configured slots show OK.
  5. Loopback test: Send a fixed pattern from S7-414-4H to Yokogawa, mirror it back via Yokogawa logic, and read it back on S7. Compare pattern to received value in OB35 to validate full bidirectional integrity.

Troubleshooting Matrix

Symptom Likely cause Action
Link LEDs all off No 24 V supply to the DP/DP Link Check terminal block; verify 24 V DC at the link
Link LED red on one side Configuration mismatch, slave address conflict, or wiring error Compare GSD slot definition on both sides; verify terminating resistors on/off pattern
Bus fault BF (bus fault) on S7 CPU Short circuit, missing termination, or wrong baud rate Disconnect segments; use PROFIBUS tester to locate reflections
SFC14 RET_VAL 8093 Data length mismatch between S7 and Yokogawa slot definitions Recompile and download both configurations identically
SFC14 RET_VAL 80A0 intermittently Slave dropping out of data exchange Check shield bonding, EMC, distance limits, redundant power
Data updates slowly on Yokogawa side Yokogawa segment at low baud rate (e.g. 187.5 kbit/s) Increase baud rate if cable length permits; review bus parameters
Writes from S7 never appear in CS 3000 Output direction not configured on Yokogawa side Add output modules in CENTUM Builder; reload FCS
Writes from CS 3000 never appear in S7 Address space overlap; or SFC15 not called Verify HW Config output slot base address and LADDR; add OB1 call to DPWR_DAT
Intermittent consistency errors on 4-byte blocks Direct L/T access used instead of SFC14/15 on unit-consistency slots Convert access to SFC14/15; do not mix direct access on unit-consistency slots

Safety and Commissioning Notes

  • The S7-414-4H is a redundant CPU. Both CPUs participate on the same DP segment; the active CPU holds the token. Verify in HW Config that the redundant partner does not also try to claim the bus as a separate master - by default the H system handles this automatically, but a re-check after a CPU swap is recommended.
  • Functional safety data must not be routed through a non-safety-certified link unless the integrated PROFIBUS safety (PROFIsafe) layer is used end-to-end. The DP/DP Link itself is not PROFIsafe-compatible; do not pass safety signals through it.
  • Apply shield bonding at both cable ends with low-impedance connections. The recommended shield current capacity is below 1 kA for typical plant environments; check against site fault levels.
  • Document the byte map of both segments in the project documentation. The map must show: tag name, byte offset, scaling, engineering units, and direction (read/write from S7 perspective).
  • When replacing a DP/DP Link in operation, set both masters to STOP, swap the device, re-apply power, and restart masters in sequence. Hot-swap is not supported by the link.

Frequently Asked Questions

Can the S7-414-4H integrated DP port act as a DP slave for a Yokogawa master?

Yes, the integrated DP port can be reconfigured as a DP slave in HW Config (interface mode = DP Slave). However, this is generally not advisable for a redundant controller: a slave cannot initiate communication, and the H-system's active/standby arbitration interferes with the slave role. The DP/DP Link approach is the field-proven pattern.

Do I always need SFC14 and SFC15 for S7-400H to Yokogawa CS 3000 data exchange?

Only when the slot exceeds 4 bytes, is exactly 3 bytes, or when the slot is configured with "Unit" consistency. For 1-2 byte slots, or 4-byte slots in "Total length" (DWord) consistency, direct I/O access (L PIW / T PQW) is sufficient because the S7-400 updates the process image atomically within a 4-byte aligned access.

What is the maximum data volume between S7-400H and Yokogawa CS 3000 via a DP/DP Link?

Up to 244 input bytes and 244 output bytes per direction on the Siemens 6ES7 158-0AD01-0XA0. For larger payloads, segment the data into multiple slots and use multiple SFC14/15 calls - or move to PROFINET IO if both sides support it.

Can the S7-414-4H talk directly to a Yokogawa CS 3000 PROFIBUS module without a DP/DP Link?

Not in a master-to-master configuration. A direct master-to-master connection on a single PROFIBUS segment is not permitted by EN 50170. The only valid alternative is to operate one side as a slave, which sacrifices master capability and is rarely acceptable in hybrid plants.

Does the Yokogawa CS 3000 PROFIBUS module need a GSD file from Siemens?

No. The CS 3000 PROFIBUS master is configured from a GSD file that describes the DP/DP Link (Siemens) as a slave. The Siemens GSD for the DP/DP Link is available in STEP 7 and on the Siemens support site. Match GSD revision to the link's firmware revision.

Back to blog