PCS 7 V8 CPU 410-5H ISO Connection Setup with CP443-1 Plantbus

Overview of PCS 7 V8 Plantbus Architecture with AS 410

The SIMATIC PCS 7 V8 process control system uses a layered network model that physically and logically separates the engineering/operator traffic (Plantbus) from the field-level I/O traffic (PROFINET). The SIMATIC PCS 7 AS 410 station, based on the CPU 410-5H (article number 6ES7 410-5HX08-0AB0 for the H-version), exposes two onboard PROFINET interfaces (PN/IE interfaces X1 and X2) on the front panel. These onboard ports are optimized for PROFINET IO controller / IO device operation and for TCP/IP-based S7 communication, but they do not expose a classical S7-ISO transport endpoint that PCS 7 historically expects on the Plantbus. As a result, ISO transport between the Engineering Station (ES), the OS Server, and the AS 410 cannot be bound to the onboard ports without a third-party S7-OPC redirector or a TCP/IP-only OS project.

To preserve the standard S7-ISO Plantbus design, Siemens recommends a separate CP 443-1 communication processor in the AS 410 rack (or two CP 443-1 modules in a redundant AS pair) dedicated to Plantbus traffic. The CPU 410-5H onboard PROFINET ports are then reserved for PROFINET IO and field-level diagnostics, with deterministic, isolated traffic.

Network Topology: Plantbus vs. PROFINET Fieldbus

A correct PCS 7 V8 cell follows a three-tier network model:

1. Plantbus (terminal bus / engineering bus) – Connects the Engineering Station (ES), the OS Server / OS Clients, the BATCH station, the Route Control station, and the AS 410 (via CP 443-1). It runs S7-ISO transport, ISO-on-TCP (RFC1006), TCP/IP, and the PCS 7 Plantbus protocol for time stamping and life-list. Typical bandwidth: 100 Mbit/s or 1 Gbit/s. Recommended media: industrial Ethernet (SCALANCE XC/XB/XR or X-200/X-300 series) or a managed Layer-2 switch configured with broadcast/multicast limiting.
2. Fieldbus (PROFINET IO / PROFIBUS DP) – Connects distributed I/O (ET 200SP, ET 200MP, ET 200M, ET 200iSP) to the AS. With the AS 410, the fieldbus is normally PROFINET IO over the onboard PN interfaces (X1 / X2). PROFIBUS DP is still supported when a CP 443-5 Ext is plugged into the AS rack.
3. Terminal/operator LAN (OS client LAN) – Connects OS Clients to the OS Server. Can share the same physical Plantbus when bandwidth is sufficient; otherwise a separate VLAN is recommended.

Reference: PCS 7 V8.0 Getting Started – PCS 7 Getting Started (PDF).

Hardware: CP 443-1 vs. Onboard PROFINET Ports

The CP 443-1 EX30 (6GK7443-1EX30-0XE0) is the current PCS 7-released version. Older variants (EX11, EX20, EX21) are still supported in V8 but follow the same configuration principle. Always cross-check the released version in the PCS 7 Released Modules list for the installed PCS 7 version.

ISO Transport Addressing in NetPro: MAC vs. IP

PCS 7 V8 historically uses S7-ISO as the primary Plantbus transport. The ISO endpoint is identified at Layer 2 by the MAC address of the CP 443-1, not by the IP address. This is the reason a CP 443-1 must be inserted in the AS 400 station in HW Config and inserted into the Plantbus subnet in NetPro before the S7 connection icons can be drawn.

Step-by-step configuration sequence:

1. Open the SIMATIC 400 station in HW Config and slot a CP 443-1 into an open slot of the UR2/UR2-H rack. Set the order number to the variant that matches the physically installed module (for example, 6GK7 443-1EX30-0XE0).
2. Open the CP 443-1 properties and assign a fixed MAC address from the address range reserved for the cell. (Many engineers use the last three bytes of the module's label MAC, e.g. 08-00-06-6B-12-34.)
3. In NetPro, connect the CP 443-1 to the Plantbus subnet (S7-ISO subnet). The subnet must be of type Ethernet (ISO).
4. Create the S7 connections: one S7 connection from the ES station to the AS, and one S7 connection from the OS Server station to the AS. Both are created by right-clicking the AS and choosing Insert New Connection; the partner is the ES or the WinCC Application on the OS Server PC station.
5. Compile and download the AS hardware. The CP 443-1 firmware is loaded at the first connection establishment; the module LED LINK and RX/TX confirm physical connection.

TCP/IP as an Alternative Plantbus Path

If a CP 443-1 is not available, the CPU 410-5H onboard PROFINET ports can still be used for Plantbus, but only with S7-TCP/IP (RFC 1006) or standard TCP/IP sockets. The OS server project must be created with an S7-TCP connection, and the Engineering download must be performed with a TCP S7 connection. In this scenario:

• NetPro shows the S7-TCP subnet, not the ISO subnet.
• The OS application must be configured to use SIMATIC S7 PROTOCOL SUITE → TCP/IP as the channel unit.
• Time stamping resolution is identical to ISO; however, certain legacy PCS 7 components (older BATCH, older Route Control) may require ISO and refuse to come up over TCP.
• Performance is similar at 1 Gbit/s but degrades faster under heavy multicast/broadcast on the fieldbus segment.

For new installations, Siemens guidance is unambiguous: use CP 443-1 for Plantbus, reserve the onboard PN ports for PROFINET IO. For H systems, use two CP 443-1 modules to provide a fully redundant Plantbus path.

PC Station Configuration (ES and OS Server)

The PC station in PCS 7 V8 contains virtual slots for the OPC server, the WinCC application, the S7-APL application, and the IE interface (a virtual Industrial Ethernet adapter bound to the Windows NIC). Configure as follows:

1. Insert a SIMATIC PC station in the PCS 7 project and open HW Config.
2. Slot 1: OPC Server (e.g. SW V8.0 SPx) – order number 6GK1 706-1NW08-3AA0 for V8.0.
3. Slot 2: WinCC Application (the OS Server runtime).
4. Slot 3: IE General – bind to the Windows Ethernet NIC that is physically connected to the Plantbus switch.
5. Add a CP 1613 or CP 1623 / CP 1628 hardcard in the PC station if the Plantbus must use ISO at Layer 2 with a dedicated MAC. (CP 1613/CP 1623 is the typical industrial NIC for ISO-Plantbus. Softnet IE is the software-based alternative.)
6. In NetPro, connect the IE General (or CP 1613) to the same ISO Plantbus subnet used by the CP 443-1 in the AS 410.
7. Compile the PC station and download the configuration to the OS / ES host using Station Configuration Editor → Configure Station matching the order numbers of the inserted components.

For an H-system AS, repeat the PC station entries on each OS Server and use a redundant Soft PLC or CP 1613 A2 on a second server to provide OS server redundancy.

Resolving the "Data Context Does Not Exist" Error

The error "Data Context Does Not Exist" appears during project transfer from the ES to the OS Server (or during OS Project Editor → Compile OS on the server) when one of the following root causes is present:

1. PC station is not configured in NetPro on the same ISO subnet as the CP 443-1. The S7 connection icon is missing or points to a TCP subnet while the AS is on ISO. – Fix: open NetPro on the ES, insert the OS Server PC station, drag the IE General or CP 1613 to the same ISO subnet, recompile, redownload to the server.
2. Station Configuration Editor on the server does not match the HW Config of the PC station. Components are missing or have different order numbers/firmware. – Fix: re-run Configure Station on the server so the installed components match the symbols exactly. The OPC server, WinCC application, and IE General (or CP 1613) entries must all be present and active.
3. Software version mismatch. The ES is on a newer Service Pack than the server, or the server has WinCC flexible installed alongside PCS 7, which corrupts the WinCC channel DLLs. – Fix: bring ES and OS to the same Service Pack of PCS 7 V8, remove conflicting WinCC flexible / TIA Portal installations, and re-run the PCS 7 setup.
4. Project file is damaged (incomplete download, antivirus quarantine, or interrupted ZIP during backup). – Fix: re-archive the ES project, copy the .S7P file via a clean share, and re-download the OS server project.
5. S7 connection partner is set to a CPU without the Plantbus (i.e. the partner was set to the wrong CPU, or to the CPU 410-5H without specifying the CP 443-1 as the connection endpoint). – Fix: in NetPro, right-click the S7 connection, choose Object Properties → Connection Path, and set Local = CP 443-1 in the AS 410, Partner = IE General on the OS Server.

Redundant AS 410 (H-System) Specifics

When the AS 410 is configured as a redundant H pair (two CPU 410-5H modules in UR2-H racks, interconnected with fiber-optic sync modules), Plantbus redundancy must also be in place:

• Two CP 443-1 modules, one in each H rack, each with its own MAC address, connected to the same ISO Plantbus subnet (logically redundant, physically two paths).
• The S7 connection in NetPro is then automatically resolved to the active CPU by the H system; the OS Server sees a single Plantbus endpoint at any time.
• If only one CP 443-1 is configured, a CPU failover will briefly interrupt the OS-AS connection and may surface as a "Data Context Does Not Exist" until the S7 connection is re-established by the H system. For H, always install two CP 443-1 modules.
• Sync cable length: up to 10 km per module pair, redundant sync module pairs are mandatory.

Commissioning Verification

1. From the ES, run PLC → Download to Target System for the AS 400 station. Confirm the CP 443-1 reports RUN with LINK and RX/TX active on the front panel.
2. In NetPro, select the S7 connection ES → AS and run PLC → Verify Connection. The status must be OK.
3. From the OS Server, open WinCC Explorer and confirm Server Status shows all channels OK, all connections Established, and the AS life-list is fully populated (no red icons in the life-list display).
4. Force a value in the AS via Monitor/Modify on the ES and confirm the value appears in the OS faceplate within one Plantbus cycle (typically 1 s, configurable via the OS project editor under Time Synchronization / Acquisition Cycle).
5. Open OS Project Editor → Compile OS on the server. The compile must complete without the "Data Context Does Not Exist" error. If it does not, re-apply the fix in the previous section.
6. For H systems, perform a manual failover (PCS 7 → AS → Switchover / H-CPU) and repeat steps 1–5 on the standby CPU.

Troubleshooting Matrix

Best-Practice Reference Cell

• AS 410 with CPU 410-5H firmware ≥ V8.0 (released for PCS 7 V8.0); current released is V8.2.
• CP 443-1 EX30 (6GK7443-1EX30-0XE0) as Plantbus interface. Two modules in H systems.
• PC station on ES and OS Server with OPC Server V8.0, WinCC Application V8.0, IE General bound to a dedicated Plantbus NIC, plus CP 1613 A2 for ISO if deterministic MAC-based ISO is required.
• SCALANCE XC/XB-200 switch on the Plantbus, no PROFINET devices, no IRT.
• PC station subnet type: Ethernet (ISO) for Plantbus, never mixed with the PROFINET subnet.
• S7 connection ES → AS and OS Server → AS created in NetPro with local endpoint = CP 443-1.
• OS project compiled on the ES first, then downloaded to the server, then Compile OS re-run on the server to regenerate the runtime database.

Field Notes and Caveats

• The "Data Context Does Not Exist" error is the most common Plantbus symptom in PCS 7 V8.1/V8.2 upgrades where the customer moved from CP 443-1 to onboard PN without re-typing the S7 connections. Always re-validate NetPro after any Plantbus topology change.
• Do not install WinCC flexible 2008 SPx on the same OS server as PCS 7 V8 – the channel DLLs overlap and the OS server will refuse to start the S7 channel.
• When the AS is redundant, the OS server's CP 1613 A2 (or Softnet IE) must be set to the same Index as the Plantbus interface in HW Config, otherwise the H failover will not re-route.
• Plantbus switches should have Broadcast Limiter and Multicast Limiter set to allow at least 200 frames/s of S7 PDU traffic; the default Storm Control threshold on consumer switches often breaks Plantbus.

References Used in This Article

• PCS 7 Getting Started (V8.0 or higher with APL)
• SIMATIC PCS 7 AS 410 System Manual (CPU 410-5H), Siemens Industry Online Support
• SIMATIC NET CP 443-1 Manual, Siemens Industry Online Support
• SIMATIC PCS 7 Released Modules list for V8.0 / V8.1 / V8.2