C135 PCS 7 (PCS7)
6C
6 Cielo Ciencia y Tecnología
·Publicada en C135 PCS 7 (PCS7)

Engineering PN-PN Couplers for Deterministic Data Exchange Across PCS 7 and S7-1500 Subnets

Engineering PN-PN Couplers for Deterministic Data Exchange Across PCS 7 and S7-1500 Subnets

Connecting SIMATIC PCS 7 automation systems to standalone SIMATIC S7-1500 package units is achieved reliably using a hardware PROFINET PN/PN Coupler (such as 6ES7158-3AD10-0XA0). The PN/PN Coupler provides deterministic, galvanically isolated cyclic data exchange between two independent PROFINET subnets without merging IP ranges or sharing network management. In STEP 7 HW Config, engineers configure matching input and output module lengths on both subnet sides, maintain total length data consistency, and evaluate coupling diagnostic states to ensure plant safety.

Table of Contents

Hardware Coupling Architecture and Network Decoupling

Integrating skid-mounted package units (e.g., chillers, air compressors, water treatment systems controlled by SIMATIC S7-1500 or third-party controllers) into a central SIMATIC PCS 7 automation system requires strict network separation:

  • Galvanic and Logical Segregation: The Siemens PN/PN Coupler (6ES7158-3AD10-0XA0) features two completely independent PROFINET interfaces (Subnet 1 / Side X1 and Subnet 2 / Side X2). Each side operates with its own IP address, subnet mask, device name, and PROFINET IO controller.
  • Deterministic Memory Mirroring: The coupler internal ASIC mirrors output data written by Subnet 1 directly into the input image of Subnet 2, and vice versa, with cycle update times typically under 1 millisecond.
  • Cybersecurity and Broadcast Isolation: Broadcast storms, DHCP traffic, network loops, or engineering changes on the package unit subnet cannot propagate into the PCS 7 plant bus.
+-------------------------------------------------------------------+
|               PN/PN Coupler Interconnection Flow                  |
+-------------------------------------------------------------------+
|  PCS 7 Plant Bus Subnet (192.168.1.x)                             |
|  CPU 410-5H Controller (IO Controller 1)                          |
|                             |                                     |
|                             v (Side X1)                           |
|  +-------------------------------------------------------------+  |
|  |             SIMATIC PN/PN Coupler (6ES7158-3AD10-0XA0)       |  |
|  |  Internal Data Buffer: Mirrored Cyclic Transfer Registers   |  |
|  +-------------------------------------------------------------+  |
|                             ^ (Side X2)                           |
|                             |                                     |
|  Package Unit Subnet (172.16.0.x)                                 |
|  S7-1500 Controller (IO Controller 2)                             |
+-------------------------------------------------------------------+

HW Config Sizing and Symmetrical Module Mapping

Proper engineering requires exact symmetrical alignment of module slots between the two separate engineering projects:

  1. Side X1 Configuration (PCS 7 STEP 7 HW Config):
    * Open HW Config for the CPU 410-5H or S7-400 station.
    * In the hardware catalog, locate PROFINET IO -> Gateway -> PN/PN Coupler -> 6ES7158-3AD10-0XA0.
    * Drag the coupler onto the PROFINET IO system and assign its device name (e.g., pn-coupler-skid01).
    * Configure virtual I/O slots:
    • Slot 1: Input 16 bytes (Start address: IB 512)
    • Slot 2: Output 16 bytes (Start address: QB 512)
  2. Side X2 Configuration (S7-1500 TIA Portal HW Config):
    * In TIA Portal, open the package unit project.
    * Add the PN/PN Coupler to the S7-1500 PROFINET IO system.
    * Configure reversed symmetrical slots:
    • Slot 1: Output 16 bytes (Matches PCS 7 Slot 1 Input)
    • Slot 2: Input 16 bytes (Matches PCS 7 Slot 2 Output)
  3. Compile and Download: Save and compile both hardware configurations and download them to their respective controllers.

Data Consistency and Process Image Partitioning

To prevent data corruption when transferring multi-byte analog signals, setpoints, or energy counters across the coupler:

  • Consistency Assignment: In HW Config, double-click each configured module slot. Set Consistency to Total Length.
  • Process Image Partitioning: Assign the coupler addresses to a Process Image Partition (PIP) updated cyclically with your execution organization block (e.g., OB35 / 100 ms).
  • Using SFC14 / SFC15: If input/output addresses fall outside the cyclic process image partition, user code must call SFC14 (DPRD_DAT) and SFC15 (DPWR_DAT) to read and write data blocks consistently.

Evaluating Coupling Validity and Diagnostic States in CFC

A critical safety requirement is monitoring whether the remote partner subnet is active or disconnected:

  1. Coupling Validity Bit (Data_Valid):
    * The PN/PN Coupler can be configured with a 1-byte status module or evaluation of module diagnostic flags.
    * When the partner subnet loses power, disconnects Ethernet, or enters STOP mode, the coupler asserts a diagnostic interrupt (OB82) and flags the input data as invalid.
  2. APL Interconnection:
    * Read the validity bit in CFC using standard channel driver blocks (Pcs7DiIn).
    * Interconnect the validity bit to downstream interlocks (Intlk02) or APL block quality pins (SubsData_En).
    * If communication fails, the PCS 7 controller immediately transitions skid controls to safe fallback states.

Verification

Confirm deterministic cyclic data exchange across the coupler:

  1. Physical LED Verification on Coupler:
    * RN (Run): Green on both sides X1 and X2.
    * ER (Error): Off on both sides.
    * MT (Maintenance): Off.
    * If Side X2 is unconfigured or powered off, Side X1 illuminates ER (red flashing) and SF.
  2. Variable Cross-Check:
    * In TIA Portal, force a test integer (e.g., 16#1234) on the S7-1500 output word.
    * In SIMATIC Manager, open a variable table (VAT) monitoring the corresponding input word on the S7-400.
    * Confirm instantaneous receipt of 16#1234.
  3. Disconnection Fault Test:
    * Unplug the Ethernet cable on Side X2.
    * Confirm that Side X1 triggers OB82 and asserts diagnostic alarms in WinCC.

Limitations and Operational Precautions

  • Symmetrical Length Mandate: If the module byte length on Side X1 does not match Side X2 exactly (e.g., configuring 16 bytes Out on X1 but 8 bytes In on X2), the coupler refuses to establish data exchange on that slot and asserts a configuration error.
  • Maximum Telegram Sizing: The standard PN/PN Coupler supports up to 1440 bytes of input and output data per cycle, which is more than sufficient for skid integration.
  • No Direct Routing: The coupler does not route TCP/IP traffic, HTTP, or S7 routing frames; it is strictly an I/O data exchanger. Engineering access to the S7-1500 from the PCS 7 ES requires a separate physical connection.

Engineer FAQ

  • What is the primary function of a PN/PN Coupler in PCS 7?
    It connects two separate, independent PROFINET subnets to exchange cyclic I/O data without merging IP address spaces or sharing bus configurations.
  • Must the I/O slot configurations on both sides of the coupler be identical?
    They must be symmetrical: an Input module of X bytes on Side 1 must correspond to an Output module of exactly X bytes on Side 2.
  • What happens to PCS 7 inputs if the partner S7-1500 controller is powered off?
    The coupler detects the partner loss, reports a diagnostic alarm to the PCS 7 CPU (OB82), and substitutes zeros or configured fallback values into the input image.
  • Does integrating an S7-1500 via a PN/PN Coupler consume AS Process Object (PO) licenses?
    The coupler itself does not consume AS PO licenses; only technological blocks (motors, valves, analog inputs) created in the PCS 7 program to handle skid signals consume POs.
  • Can I transfer REAL floating-point numbers across a PN/PN Coupler?
    Yes, by configuring a 4-byte (DWORD) slot with Total Length consistency, floating-point variables can be transferred directly.
  • What is the order number for the standard SIMATIC PN/PN Coupler?
    The standard modern PROFINET coupler order number is 6ES7158-3AD10-0XA0.
  • Does the PN/PN Coupler support PROFINET System Redundancy (S2)?
    Yes, newer hardware revisions and firmware of the PN/PN Coupler support S2 system redundancy, enabling redundant connection to AS 410-5H controllers.
  • How do I configure device names on the PN/PN Coupler?
    Each side (X1 and X2) must have its device name assigned independently via the respective engineering tool using 'Edit Ethernet Node'.
  • Can a PN/PN Coupler be used to exchange safety-related data via PROFIsafe?
    Yes, by utilizing certified F-Send and F-Receive blocks in conjunction with compatible fail-safe module profiles, fail-safe signals can be exchanged.
  • What is the maximum data exchange capacity of the PN/PN Coupler?
    The coupler supports up to 1440 bytes of inputs and 1440 bytes of outputs per cyclic exchange.

Technical References

  • Siemens Industry Online Support (SIOS) Portal: SIMATIC PN/PN Coupler Hardware and Installation Manual (Entry ID: 44319532).
  • SIMATIC PCS 7 PROFINET IO Architecture and Configuration Guide, Siemens AG.
  • SIMATIC S7-1500 / ET 200MP PROFINET Communication Manual, Siemens AG.

Related Articles

Related Tags

PCS 7, PROFINET, PN/PN Coupler, S7-1500, Skid Integration, HW Config, Data Consistency, Automation Systems

20 respuestas