Binding Access Point CP_H1_1 to CP 1613 in Configuration Console for S7-300 Integration

Binding the logical access point CP_H1_1 to a CP 1613 communications processor (6GK1161-3AA00) in the Siemens Configuration Console (or 'Set PG/PC Interface') on a redundant PCS 7 OS Server will NOT disrupt or negatively impact existing S7-400 plant bus communications. The CP 1613 hardware features independent onboard microprocessors supporting multiple concurrent protocols and logical access points. Standard PCS 7 AS-OS communication operates via Named Connections through S7-REDCONNECT, which functions independently of the classic ISO access point CP_H1_1. However, the CP 1613 must remain strictly in 'Configured mode' and must never be switched to 'PG mode'.

Architecture of SIMATIC NET Communications Processors (CP 1613)

In SIMATIC PCS 7 V7.0 redundant OS Server environments, high-performance plant bus communication is handled by specialized communications processors: the PCI card CP 1613 (6GK1161-3AA00) or its PCIe successor CP 1623 (6GK1162-3AA00).

Unlike standard commercial Ethernet network cards, the CP 1613 features its own dedicated onboard CPU that offloads the entire ISO/OSI transport protocol stack from the PC's host processor. It manages complex high-speed cyclic telegram queues deterministically.

Concurrent Logical Access Points and Multi-Protocol Operation

A foundational architectural design feature of SIMATIC NET is multi-protocol concurrency:

A single physical CP 1613 card can simultaneously process ISO transport protocol (layer 4), ISO-on-TCP (RFC 1006), TCP/IP, UDP, and S7 communications.
In the Windows operating system, applications bind to the hardware through Logical Access Points (Access Points of the Application).
Standard PCS 7 OS communication binds to the access point CP_L2_1 or Named Connections configured via the PC Station Component Configurator.
Adding or re-binding the logical access point CP_H1_1 (the default access point for classic ISO Industrial Ethernet) to CP 1613 (ISO) merely creates an additional software routing entry in the SIMATIC NET layer without modifying existing connections.

Why Named Connections and CP_H1_1 Coexist Safely

Standard PCS 7 communication utilizes S7-REDCONNECT and Named Connections defined in STEP 7 NetPro:

Named Connections bind directly to the Virtual Field Device (VFD) of the WinCC application registered in the Station Configuration Editor.
When integrating a standalone S7-300 PLC via the WinCC SIMATIC S7 Protocol Suite > Industrial Ethernet channel, WinCC queries access point CP_H1_1.
Because both channels utilize different connection endpoints and separate internal buffers on the CP 1613, both the redundant S7-400H plant bus and the S7-300 communication operate concurrently without interference.

Configuration Procedure in Configuration Console / Set PG/PC Interface

Follow this procedure on both redundant OS Servers:

Open Configuration Console / Set PG/PC Interface:
- Launch Configuration Console (Set PG/PC Interface) from Control Panel or SIMATIC NET tools.
Verify Operating Mode:
- Under Modules > CP 1613 > General, confirm the operating mode is Configured mode (never select PG mode).
Assign Access Point CP_H1_1:
- Navigate to Access Points.
- Select CP_H1_1 from the list.
- Assign its interface parameter assignment to CP 1613 (ISO) (or CP 1613 (RFC 1006) if using IP addressing).
- Click Assign and Apply.
Configure WinCC Tag Management:
- In WinCC Explorer on the ES, open Tag Management > SIMATIC S7 Protocol Suite > Industrial Ethernet.
- Add the S7-300 connection using its MAC address (or IP) and Rack 0, Slot 2.
- Download the updated OS project to both redundant servers.

Comparison of SIMATIC NET Access Points and Protocols

The table below details access point roles across SIMATIC NET drivers:

| Access Point Name | Target Hardware Interface | Used By Protocol Channel | Application Role |
|---|---|---|---|---|
| Named Connections | CP 1613 / S7-REDCONNECT | S7 Protocol Suite (Named) | Primary PCS 7 S7-400/AS 410 plant bus |
| CP_H1_1 | CP 1613 (ISO) | Industrial Ethernet (ISO) | S7-300 / S7-400 standalone connections |
| S7ONLINE | Dedicated Network Card / ISO | STEP 7 Engineering | PG/PC online programming & HW Config downloads |
| CP_L2_1 | CP 5613 (PROFIBUS) | PROFIBUS DP / S7 | Classic S7-400 PROFIBUS plant bus |

Verification

Verify communication health across both channels:

Open WinCC Channel Diagnosis (WinCCChnDiag.exe) in OS Runtime.
Inspect the Named Connections channel: confirm all S7-400 connections display green status OK.
Inspect the Industrial Ethernet channel: confirm the S7-300 connection displays green status OK.
Verify that process variables from both the S7-400 and S7-300 update simultaneously on WinCC graphic screens.

Limitations and Operational Precautions

Adhere to the following network precautions:

Never Select PG Mode: Switching CP 1613 to 'PG mode' unbinds the card from the Station Configuration Editor, instantly dropping all redundant S7-REDCONNECT communication to the plant.
Bandwidth Monitoring: S7-300 communication adds cyclic polling load; ensure S7-300 update cycles are set to at least 500 ms to preserve plant bus bandwidth.
Duplicate Configuration: Execute the identical access point assignment on both Server 1 and Server 2 to guarantee continuous S7-300 communication during redundancy failover.

Engineer FAQ

Will assigning CP_H1_1 to CP 1613 disrupt existing PCS 7 communication?

No. CP 1613 supports multiple concurrent access points and protocols. Standard PCS 7 plant bus communication operates via Named Connections and is unaffected by the CP_H1_1 assignment.

What happens if someone accidentally switches the CP 1613 to PG mode?

Switching to PG mode disconnects the card from the PC Station Component Configurator, immediately severing all S7 Named Connections to the plant controllers and causing a severe plant bus communication loss.

Can an S7-300 PLC be integrated into PCS 7 as an AS station?

No. S7-300 PLCs cannot run PCS 7 system libraries, CFC driver generators, or APL blocks. They can only be integrated into WinCC as standalone auxiliary controllers via standard communication channels.