Configuring PROFIBUS DP Master-Slave (I-Slave) Coupling Between AS 410 and CPU 412 in SIMATIC PCS 7

Coupling a main SIMATIC PCS 7 AS 410 controller to a secondary S7-400 CPU 412 over PROFIBUS DP in a Master-Slave (Intelligent Slave / I-Slave) configuration establishes high-speed, cyclic data exchange directly across internal process images. On the programming side, data transfer is completely decoupled from standard PCS 7 APL field drivers: the master AS 410 sees the CPU 412 not as distributed field I/O, but as pre-mapped virtual input/output bytes (PIW/PQW). In CFC, engineers must either assign these I/O addresses to a Process Image Partition (PIP) and access them symbolically via standard data conversion blocks, or manage multi-word data consistency using system function blocks SFC 14 (DPRD_DAT) and SFC 15 (DPWR_DAT), bypassing the automated driver generator.

Architectural Principles of I-Slave Coupling in PCS 7

In industrial plants, a central PCS 7 DCS (often built on high-performance controllers like the CPU 410-5H) frequently coordinates subsidiary machine packages, skids, or material handling subsystems controlled by smaller PLCs (such as an S7-400 CPU 412 or S7-300 CPU 315-2 DP).

When configuring the secondary CPU 412 as an Intelligent Slave (I-Slave) on the AS 410 PROFIBUS DP master line, the two controllers exchange cyclic process data deterministically at the PROFIBUS bus cycle rate (typically 1.5 to 12 Mbps). The CPU 412 executes its local logic autonomously, controlling its own field I/O, while exchanging a defined window of setpoints, actual values, and interlock bits with the master AS 410.

HW Config Setup: Configuring the AS 410 Master and CPU 412 I-Slave

To establish the I-Slave configuration across projects in SIMATIC Manager:

Slave Configuration (CPU 412):
- In HW Config of the CPU 412, open the DP interface properties.
- Set Operating Mode to Slave (check 'Active station on bus').
- Under the Configuration tab, define the exchange areas (e.g., Row 1: Master Output 16 Bytes -> Slave Input 16 Bytes; Row 2: Slave Output 16 Bytes -> Master Input 16 Bytes).
Master Configuration (AS 410):
- In HW Config of the AS 410, open the PROFIBUS DP master system.
- Insert the CPU 412 from the Hardware Catalog under PROFIBUS-DP > Configured Stations (or via GSD if in separate projects).
- Link the master DP address to the defined I-Slave data slots.
- Assign consistent S7 I/O addresses (e.g., Master Input IW 512..527, Master Output QW 512..527).

Programming and Addressing Implications in CFC

The fundamental programming impact on the PCS 7 AS 410 engineering workflow includes:

Bypassing the PCS 7 Driver Generator: The PCS 7 Generate Module Drivers utility does NOT generate standard MOD_ diagnostic blocks or APL channel blocks (Pcs7AnIn, Pcs7DiIn) for I-Slave virtual slots. It treats them as raw digital/analog operands.
Mapping Process Tags in CFC: To read data from the CPU 412 into the AS 410 CFC program, engineers create user data blocks or connect inputs directly to conversion blocks (e.g., Strg_BO for packed bits, R_to_Word for analog values).
Life-Beat Monitoring (Heartbeat): Because standard hardware diagnostics do not monitor slave software execution, engineers MUST program a cyclic heartbeat counter (toggling bit or incrementing integer) between the AS 410 and CPU 412 to detect PLC stops or frozen program loops.

Ensuring Data Consistency: Process Image Partitions vs SFC 14/15

When transferring multi-byte process variables (such as 32-bit REAL setpoints or structured recipes), data consistency is vital to prevent reading corrupted intermediate byte combinations:

Process Image Partition (PIP) Method (Recommended for PCS 7): In HW Config, assign the I-Slave addresses to an OB-specific Process Image Partition (e.g., PIP 1 assigned to OB 35). S7-400 CPUs guarantee complete data consistency across the entire configured partition, allowing CFC blocks to read symbolic operands directly without extra system functions.
System Functions SFC 14 / SFC 15 Method: If data slots exceed standard process image sizes or require event-driven updates, call SFC 14 DPRD_DAT (Read Consistent Data from a DP Standard Slave) and SFC 15 DPWR_DAT (Write Consistent Data) inside CFC or SCL.

Comparison of I-Slave PROFIBUS Coupling vs S7 Named Connections

The following table compares I-Slave PROFIBUS DP coupling with Industrial Ethernet S7 connections:

| Technical Dimension | PROFIBUS DP I-Slave Coupling | Industrial Ethernet S7 Connection (BSEND/BRCV) |
|---|---|---|---|
| Physical Media | RS485 Copper Cable (PROFIBUS DP) | Industrial Ethernet (Cat6 / Fiber) |
| Transmission Determinism | High (Cyclic at bus scan rate: < 10 ms) | Moderate (Acyclic packet dispatch via TCP/IP) |
| Maximum Data Volume | Limited (Up to 244 bytes per transfer) | Large (Up to 64 KB per block transfer) |
| Programming Overhead in CFC | Minimal (Direct I/O operand access) | Moderate (Requires BSEND/BRCV handshake blocks) |
| Diagnostic Hierarchy Integration | Manual heartbeat logic required | Native S7 connection health monitoring |
| Controller Redundancy Support | Requires Y-Link or redundant CP if fault-tolerant | Native Fault-Tolerant S7 Connection on S7-400H |

Verification

Verify Master-Slave data exchange between AS 410 and CPU 412:
1. Inspect the physical DP bus connectors: verify that the BF (Bus Fault) LEDs on both the AS 410 and CPU 412 are extinguished.
2. In the AS 410 CFC chart, monitor the received input words from the CPU 412; verify that values match the slave's sent variables.
3. Switch the CPU 412 from RUN to STOP mode; verify that the AS 410 detects the communication failure via the heartbeat timeout logic and triggers an operator alarm.
4. Verify that the CPU 412 diagnostic buffer reports normal cyclic DP exchange without address alignment errors.

Limitations and Operational Precautions

Never configure the AS 410 master outputs and CPU 412 slave inputs with mismatched slot lengths; a 1-byte length mismatch in HW Config will prevent the slave from entering data exchange mode (permanent BF LED). If the AS 410 is a redundant system (CPU 410-5H Redundant Pair), connecting a non-redundant single CPU 412 directly via PROFIBUS DP creates a single-point connection unless routed through an active Y-Link module or switched via an DP/DP Coupler.

Engineer FAQ

Why doesn't the PCS 7 driver generator create channel blocks for my CPU 412 I-Slave?

The driver generator only creates channel blocks for physical I/O modules and certified field devices. An I-Slave is treated as an intelligent communication partner whose internal data structure is defined by user software, requiring custom CFC mapping.

What is the maximum data size that can be exchanged via an I-Slave configuration?

The standard PROFIBUS DP specification limits total cyclic data exchange for an I-Slave to a maximum of 244 bytes of input data and 244 bytes of output data per slave node.

Can an S7-400H redundant system act as a master to an I-Slave without a Y-Link?

No. An S7-400H redundant master requires either redundant slave interface modules (which CPU 412 does not possess) or a Y-Link (6ES7197-1LA12-0XA0) to couple the redundant DP lines to a single non-redundant slave.