Configuring the PN/PN Coupler in PCS 7 for Third-Party Controller Integration

The SIMATIC PN/PN Coupler is a PROFINET gateway that links two physically separated PROFINET subnets, allowing a PCS 7 controller on one side to exchange process data with a non-Siemens controller (or another Siemens controller) on the other side without routing the entire plant bus. In a PCS 7 environment, the PN/PN Coupler is the preferred method for bridging two PROFINET networks while keeping the IP subnets and IO controller domains strictly isolated. This guide walks through the complete configuration, the PCS 7 driver library 9LA1110-6CG20-0AA0, quality-code handling, and the steps required to bring a non-Siemens controller online.

1. Overview and Use Cases

The PN/PN Coupler addresses a recurring plant requirement: two autonomous automation cells, each governed by its own PROFINET IO controller, need to share a small, well-defined set of process variables without merging their fieldbus segments. Typical PCS 7 scenarios include:

• PCS 7 AS communicating with a third-party PLC (Allen-Bradley CompactLogix/ControlLogix, Schneider Modicon M340/M580, ABB AC500, Mitsubishi MELSEC, Yokogawa, Emerson DeltaV) over PROFINET on the foreign side.
• PCS 7 AS 410 exchanging status and commands with a separate PCS 7 AS 410 redundancy domain that must remain isolated for availability reasons.
• PCS 7 operator station level (OS) accessing a SIMOTION or SINUMERIK subsystem without breaking the strict PCS 7 plant bus hierarchy.
• PCS 7 connecting to a packaged unit shipped with its own PROFINET controller (skid-mounted subsystem).

For PCS 7 the configuration is supported by a dedicated driver library, 9LA1110-6CG20-0AA0, which contains the function blocks, data structures, and diagnostics needed to consume the coupler data with full quality-code fidelity. The library is the recommended path because raw I/O access via PEW/PAW loses the diagnostic semantics that PCS 7 OS faceplates and SFC charts expect.

2. Prerequisites and Required Components

Before configuring the PN/PN Coupler in PCS 7, confirm the following are in place:

• PCS 7 installation at a version that supports the driver library 9LA1110-6CG20-0AA0. Verify in the readme of the library release notes which PCS 7 versions are listed as compatible.
• SIMATIC PN/PN Coupler hardware on the plant (the device appears in the hardware catalog as PN/PN Coupler in the Network Components > PN/PN Coupler family). Confirm the firmware level matches the GSD revision that you intend to install.
• GSD file for the PN/PN Coupler (matching the installed firmware). Import the GSD into the PCS 7 engineering tool (HW Config for SIMATIC Manager-based PCS 7; TIA Portal configuration tool for newer PCS 7 projects).
• Driver library 9LA1110-6CG20-0AA0 — installed and licensed.
• IP plan for both PROFINET subnets. Each side of the PN/PN Coupler must be on a distinct IP subnet.
• Two PROFINET IO controllers — one in PCS 7 (the AS 410), and one on the partner side (the third-party controller or remote Siemens CPU).
• Process variable list documenting which signals flow in each direction, the data types used, and the quality-code semantics required by downstream PCS 7 blocks.

3. PN/PN Coupler Operating Principle

Although the PN/PN Coupler looks like a single device with two RJ45 ports, the configuration tool treats it as two PROFINET IO Devices, one for each port, with each IO Device belonging to a separate station/subnet. From the perspective of each IO controller, the coupler is just another IO Device on its local PROFINET line. Internally the device copies the output process image written by the left-side controller into the input process image of the right-side controller, and vice versa, in deterministic cycle time.

The configuration model is therefore:

• Left side (Subnet A) — owned by IO Controller #1. Output area (controller → partner) is configured on this side. Input area (partner → controller) is read on this side.
• Right side (Subnet B) — owned by IO Controller #2. The same data is mirrored: what the left side wrote as outputs appears as inputs on the right side, and what the right side wrote as outputs appears as inputs on the left side.

Up to sixteen input/output slots can be defined per side, and each slot can be sized to a byte-granular data block. The total payload per direction is bounded by the PROFINET slot size limit (244 bytes per slot). The exact number of slots available, the maximum slot size, and the total number of bytes that can be exchanged depend on the specific firmware release of the PN/PN Coupler you have installed — always cross-check against the manual of the firmware version in service.

4. Network Topology

Each side of the PN/PN Coupler must live on its own IP subnet. The following SVG summarizes a typical PCS 7 deployment where a PCS 7 AS 410 (left) exchanges data with a non-Siemens controller (right).

5. Installing the PCS 7 Driver Library 9LA1110-6CG20-0AA0

The driver library 9LA1110-6CG20-0AA0 is the recommended integration path for PCS 7 because it preserves quality codes, supports diagnosis routing, and exposes a clean CFC block interface that the OS faceplates can consume.

1. Obtain the library from the Siemens Industry Online Support portal. Confirm the article / download ID and the readme document before installation.
2. Run the setup. The library registers itself with the SIMATIC Manager / TIA Portal configuration tool and adds its master data library to the project navigation.
3. Open the PCS 7 master data library and copy the driver blocks into the project S7 program (or the project-specific master data library).
4. Compile the S7 program to make the new block types and UDTs available in CFC.
5. Review the release notes: the readme lists PCS 7 versions, AS firmware versions, and known restrictions. Do not skip this step — block interface changes between revisions are common.

6. Step-by-Step Configuration in HW Config (SIMATIC Manager PCS 7)

Configuration differs slightly between a SIMATIC Manager-based PCS 7 project and a TIA Portal PCS 7 project. The sequence below targets SIMATIC Manager (HW Config); the TIA Portal equivalent follows in the next section.

6.1 Install the GSD file

1. Open HW Config and choose Options > Install GSD File.
2. Point to the GSD XML for the PN/PN Coupler (matching the device firmware).
3. After installation the device is listed in the hardware catalog under PROFINET IO > Network Components > PN/PN Coupler (the exact catalog path depends on the GSD release).

6.2 Insert the PN/PN Coupler on Subnet A

1. Open the PCS 7 AS station (the AS 410) in HW Config.
2. Drag the PN/PN Coupler from the hardware catalog onto the PROFINET IO system of the AS 410.
3. Assign the IO Device a unique device number and a PROFINET name that complies with the PCS 7 naming convention. The PROFINET name must be reachable by the AS 410 as the IO controller.
4. Set the IP address on the left port in the correct subnet (e.g., 192.168.1.x for Subnet A).
5. Configure the slots: for each input/output area you need, add a slot in the slot table. Choose the data type that matches the process data (BYTE, WORD, DWORD, or a structured type). The first slot is typically the status/control byte pair.

6.3 Insert the PN/PN Coupler on Subnet B

1. Open the foreign controller's station in HW Config (or in the partner's engineering tool if it is non-Siemens — see section 8).
2. Drag the PN/PN Coupler a second time from the hardware catalog onto the second PROFINET IO system (the foreign controller's PROFINET).
3. Assign a different device number and a different PROFINET name (this is a different IO Device, even though it is physically the same box).
4. Set the IP address on the right port in the other subnet (e.g., 192.168.2.x for Subnet B).
5. Configure the same slot structure on the right side, keeping the slot order consistent with the left side so that the data mirror maps correctly.

6.4 Compile and download

1. Compile the AS 410 station. Verify that no duplicate IO Device names or IP addresses are reported.
2. Compile the partner station (Siemens) or export the partner's PROFINET configuration if the partner is non-Siemens.
3. Download both station configurations to the controllers.
4. Assign PROFINET device names to the physical PN/PN Coupler ports using PRONETA or the topology editor. The left port receives the name of the IO Device on Subnet A; the right port receives the name of the IO Device on Subnet B.

7. Configuration in TIA Portal (Newer PCS 7 Projects)

PCS 7 projects that use the TIA Portal engineering tool follow the same logical model — two IO Devices on two subnets — but use the device-and-network editor.

1. Install the GSD file for the PN/PN Coupler: Options > Manage general station description files (GSD).
2. Open the device-and-network editor and drag the PN/PN Coupler from the catalog to the PROFINET subnet of the AS 410.
3. Repeat for the partner subnet, inserting the same PN/PN Coupler a second time on a different PROFINET subnet.
4. Configure the IO Device slots (input/output areas) on both sides. Each side exposes its own slot table; the order of slots defines the byte offset in the process image.
5. Compile the two stations and download.

Reference: TIA Portal V20 help — Editing devices and networks > Bus coupling with PN/PN > PN coupler > Application and function at docs.tia.siemens.cloud.

8. Integrating Non-Siemens Controllers

The partner side does not need to be a Siemens controller. PROFINET is an open standard, and a third-party controller can be configured as the IO controller on Subnet B. The non-Siemens controller's engineering tool sees the PN/PN Coupler as a PROFINET IO Device using the GSD that Siemens publishes for the coupler. Steps:

1. Import the PN/PN Coupler GSD into the third-party engineering tool (for example, Studio 5000 / Logix Designer for Allen-Bradley, EcoStruxure Control Expert for Schneider, Automation Studio for B&R, CODESYS for any CODESYS-based controller).
2. Add the PN/PN Coupler to the PROFINET topology on Subnet B as an IO Device under the third-party controller.
3. Configure the same slot structure as on the PCS 7 side. The byte order and slot numbering must match exactly so the data mirror maps correctly.
4. Assign the device a PROFINET name and IP address in Subnet B.
5. Verify with the third-party tool's PROFINET diagnostics that the IO Device is in data exchange.

PCS 7 supports third-party automation integration at multiple levels. For an overview of the available options (PROFINET, PROFIBUS, MODBUS/TCP, OPC, and the like) consult the Siemens Industry Online Support article on integrating third-party automation in PCS 7.

9. Data Exchange Areas and Slot Mapping

The exchange area between the two subnets is defined as a list of slots. Each slot is sized to match the underlying PROFINET data type. A typical bidirectional exchange for a small process cell looks like this:

Slot 0 is reserved for the status/control byte. The PCS 7 driver library expects this byte to be present and parses the PROFINET quality code from it. If the slot order or the slot types diverge from the convention expected by the library, the driver block will return a bad quality code regardless of the actual PROFINET state.

10. Quality Codes and Status Bytes

PROFINET defines a quality byte (the lower seven bits of slot 0 on the input side) that mirrors the quality semantics of PROFIBUS/PROFINET. The most important values for PCS 7:

The status byte of the PN/PN Coupler additionally carries vendor-specific bits for port errors, channel diagnostics, and PRONETA-style maintenance information. The exact bit assignment is documented in the PN/PN Coupler manual that ships with the firmware version installed in the field — always verify against the manual revision that matches the device label.

11. Driver Block Integration in PCS 7 CFC

Once the hardware configuration is compiled and downloaded, integrate the driver blocks in the PCS 7 CFC chart that owns the data exchange.

1. Open the CFC chart for the AS 410 (typically a chart dedicated to the foreign controller interface, e.g., PNPN_IFC).
2. Insert the driver block from the 9LA1110-6CG20-0AA0 library. The exact block instance name varies by library release; consult the library manual.
3. Wire the input addresses of the block to the PEW range assigned to the PN/PN Coupler IO Device on the AS 410.
4. Wire the output addresses of the block to the PAW range assigned to the PN/PN Coupler IO Device on the AS 410.
5. Connect the block's QUALITY output to the quality input of the downstream CFC blocks, and the VALUE outputs to the value inputs.
6. Connect the block's FAULT and MAINT outputs to the PCS 7 maintenance station or to the OS message configuration.
7. Compile the CFC chart and download to the AS 410.

The driver block's UDT output is structured to match the slot table you defined in HW Config. If the slot order changes after commissioning, the UDT instance must be re-compiled.

12. Diagnostics and Troubleshooting

The PN/PN Coupler exposes rich diagnostics. The most common commissioning faults and the diagnostic checks that resolve them:

For PCS 7–specific issues with the PN/PN or PN/MF coupler, the canonical Siemens Industry Online Support article is How to integrate the PN/PN coupler or the PN/MF coupler into PCS 7? at support.industry.siemens.com. That article also documents the matching PN/MF Coupler variant when the foreign side speaks PROFIBUS instead of PROFINET.

13. Verification and Commissioning

After download, run a structured verification pass before handing the system over to operations.

1. PROFINET diagnostics. On the AS 410, open the online PROFINET diagnostics. Both IO Devices (the left and right sides of the coupler) must be in data exchange with no active alarms.
2. Partner-side diagnostics. From the third-party engineering tool, verify that the coupler is in data exchange on Subnet B as well.
3. Slot round-trip test. Force a known value on slot 1 of the AS 410 side; read the same slot from the partner side. The value must match bit-exact.
4. Quality code round-trip test. Disconnect the partner side PROFINET cable. Within one PROFINET update cycle, slot 0 on the AS 410 side must report bad (0x00). Reconnect; the quality must return to good (0x80).
5. CFC chart run state. The CFC chart that hosts the driver block must be in run, and the block's QUALITY output must be good.
6. OS faceplate. Open the OS faceplate that consumes the foreign controller's data. All signals must update live, and the quality indicator must be green.
7. Maintenance station. Open the PCS 7 maintenance station. No open maintenance or fault messages for the PN/PN Coupler should be present.
8. Diagnostics buffer. Read the diagnostic buffer of the AS 410 and of the partner controller. Only the expected startup entries should be present.

14. Operational Notes

• Determinism. The PN/PN Coupler introduces one PROFINET cycle of latency per direction. In time-critical loops this must be added to the closed-loop budget.
• Redundancy. A single PN/PN Coupler is a single point of failure. For high-availability paths, plan a redundant coupler pair and an application-level switchover in the CFC.
• Firmware updates. A firmware update of the PN/PN Coupler requires a re-import of the matching GSD on both sides and a recompile of the IO Device configuration. Schedule a maintenance window.
• Cybersecurity. The PN/PN Coupler terminates PROFINET at the IP layer. Configure the access control list on Subnet A so that the foreign side cannot reach PCS 7 controllers or the OS network beyond the coupler.
• Library updates. When 9LA1110-6CG20-0AA0 is updated, the block interface may change. Always read the release notes and re-test in a non-production environment before rolling out.

FAQ