S7-300 CPU 314C-2DP Network Integration: PROFIBUS, NetLink, SCADA

1. Problem Scope and Integration Goal

The deployment target described in this reference is a plant floor populated with approximately twenty SIMATIC S7-300 CPU 314C-2DP controllers (Siemens part number 6ES7314-6CF00-0AB0) that must report process data to a SCADA host — currently evaluated as Wonderware InTouch — while leaving room to absorb future Allen-Bradley controllers on the same supervisory network. Because the controllers are already commissioned, the field engineer is constrained from wholesale CPU swaps and must select a SCADA-facing transport that respects the 314C-2DP's hardware profile, its connection budget, and the SCADA package's driver preferences.

This article consolidates the realistic transport options (PROFIBUS DP, third-party PROFIBUS-to-Ethernet converters often marketed as NetLink adapters, CP343-1 Lean Ethernet communications processors, and PC-side PROFIBUS cards such as CP5621/CP5613), the connection-resource math for a 20-CPU fleet, the OPC-versus-native-driver SCADA decision, and the migration path to a 314C-2PN/DP or IM151-8 PN controller when a controller swap becomes justifiable. It also outlines the multi-vendor steps needed to bolt Allen-Bradley controllers onto the same supervisory backbone.

The reference is anchored on the official Siemens product support entry for the CPU at the SIMATIC S7-300 entry ID 6ES7314-6CF00-0AB0 (CPU 314C-2DP product support).

2. CPU 314C-2DP Hardware Profile

The 314C-2DP is a compact CPU in the S7-300 family with integrated digital and analog I/O and an onboard PROFIBUS DP master/slave interface. The compact-C suffix means the analog and digital I/O are wired through the same front connector area and are scanned by the CPU firmware directly, leaving the PROFIBUS port for external networking rather than local I/O expansion.

The defining limitation of the 314C-2DP for SCADA work is that there is no integrated PROFINET port. Any Ethernet path to the SCADA host therefore requires either a CP module in the rack (CP343-1 Lean/CP343-1) or a third-party PROFIBUS-to-Ethernet gateway. The PROFIBUS DP port itself cannot directly carry TCP/IP traffic to a Wonderware or WinCC node.

3. Communication Interfaces Available on the 314C-2DP

Three distinct paths reach the SCADA host from the 314C-2DP, with very different cost and reliability profiles:

1. MPI / PROFIBUS DP integrated port (X1) — 9-pin D-sub, RS-485 physical layer, supports MPI at 187.5 kbaud and DP up to 12 Mbaud. This is the only integrated fieldbus.
2. CP343-1 Lean / CP343-1 / CP343-1 Advanced — inserted in a free S7-300 slot (typically slot 4 or 6), gives the CPU an ISO-on-TCP / TCP / UDP / PROFINET interface. Adds up to 16 S7 connections depending on configuration.
3. External PROFIBUS-to-Ethernet gateway (NetLink-class converters) — third-party box attached to the DP port, exposing an Ethernet socket on the SCADA side. No CP slot is required in the 314C-2DP rack.

PC-side options for the SCADA host mirror these transports: CP5621 (PCIe, PROFIBUS DP master) and CP5613 (PCI/PCIe, PROFIBUS DP master, higher diagnostic depth) plug into the engineering/SCADA station and terminate the PROFIBUS line. The drawback of this arrangement — DP cabling to a control-room PC that is far from the field — is the bus length budget and the need for repeaters or fiber segments, which is why gateways are usually preferred for greenfield SCADA tie-ins.

4. Network Architecture Options for a 20-CPU Installation

For a plant with 20 controllers, the architecture must answer three questions:

• Does the SCADA host attach over PROFIBUS, Ethernet, or mixed?
• How are S7 connection resources distributed across 20 CPUs without oversubscribing any single CPU?
• How will future Allen-Bradley controllers enter the supervisory layer?

The decision matrix below compares the three realistic deployment paths. "Cost per controller" is shown as the relative per-CPU incremental cost to reach the SCADA host, normalized to a 20-CPU plant:

4.1 Topology Diagram (SVG)

5. Option A — PROFIBUS-to-Ethernet Third-Party Converter (NetLink-Class)

This is the path that minimizes incremental hardware while preserving the existing DP cabling. A NetLink-class adapter is a small DIN-rail module with a PROFIBUS-DP slave port and an Ethernet (or RS-232) port. It exposes the DP master's cyclic data as a TCP/UDP socket on the SCADA side, where a Wonderware DAServer or a Siemens S7 OPC server (SIMATIC NET) reads it.

Field-proven characteristics of this class of converter:

• Per-segment sizing. Place one converter per 4–5 CPUs; this keeps the PROFIBUS segment length within the 12 Mbaud timing budget and avoids DP timeouts when the SCADA host pauses I/O.
• Configuration. The converter is configured as a DP slave with a fixed I/O slot assignment (typically 32 bytes in / 32 bytes out per slave). The DP master (CPU 314C-2DP) transfers the SCADA-relevant tags via DPWR_DAT / DPRD_DAT SFCs.
• SCADA-side driver. Wonderware's DAServer for SIMATIC S7 (or a generic S7-TCP/ISO driver) reads the converter over TCP. Each converter becomes one "device" in the DAServer.
• Failure mode. If the SCADA host goes offline, the converter does not block DP traffic — it simply discards inbound telegrams after a watchdog timeout.

Typical commissioning checklist for this option:

1. Import the converter's GSD file into STEP 7 (or TIA Portal via the GSD import tool).
2. Add the converter as a DP slave on the 314C-2DP's X1 line with a unique PROFIBUS address (e.g., 3–7).
3. Map the SCADA tag DB (e.g., DB100) onto the converter's I/O slots in HW Config.
4. Program the CPU to copy DB100 data into the process image using DPRD_DAT / DPWR_DAT SFCs.
5. Configure the SCADA DAServer with the converter's IP and slot mapping; verify tag updates with the OPC Quick Client.

6. Option B — CP343-1 Lean Ethernet Communications Processor

For installations where SCADA will be polled aggressively, where future OPC UA servers will be required, or where multiple HMI clients must connect simultaneously, the CP343-1 Lean is the Siemens-recommended path. The CP343-1 Lean occupies one slot (commonly slot 4) in the S7-300 rack and provides an ISO-on-TCP / TCP / UDP interface to the CPU via the backplane.

The CP343-1 Lean is the lowest-cost Ethernet CP in the S7-300 family but it does not support OPC UA on its own. OPC UA would require either a CP343-1 Advanced or an external PC-based OPC UA server reading the CP's S7 connection. Wonderware InTouch integrates through the DAServer for SIMATIC S7 over ISO-on-TCP, which the CP supports natively.

When wiring this path, the slot position is critical: TIA Portal's rack placeholder for the S7-300 must place the CPU in slot 2 and the CP in slot 4 to match the physical rack; mismatch causes the project to download but the CP fails to come up at startup.

7. Option C — Native PROFIBUS DP with CP5621 / CP5613 in the SCADA Host

Running PROFIBUS DP all the way to the SCADA host is technically viable and avoids the per-CPU CP cost, but it concentrates the bus on a single Windows machine and ties the SCADA reliability to that host's uptime and to DP cable routing into the control room. CP5621 is the modern PCIe PROFIBUS DP master; CP5613 is its PCI/PCIe predecessor with deeper diagnostics.

• CP5621 (6GK1562-1AA00) — single-channel PROFIBUS DP master, 12 Mbaud, suitable for SIMATIC NET OPC server and Wonderware DAServer.
• CP5613 (6GK1561-3AA00) — single-channel DP master with extended diagnostics, useful for service laptops but functionally interchangeable for SCADA polling.

The reported consensus from similar deployments is that this option is fragile: bus termination, repeater power, and PC reboot timing all introduce failure modes that are easier to isolate with an Ethernet gateway. Use this path only when the SCADA host is physically adjacent to the DP segment and when a second redundant PC card is out of budget.

8. SCADA Driver Selection — OPC, Native, or DAServer

For Wonderware InTouch, the realistic choices are:

Because the plant will later host Allen-Bradley controllers, prefer the OPC UA / OPC DA path on a SIMATIC NET or RSLinx gateway so that Wonderware sees a uniform tag namespace. Avoid proprietary driver pairs that do not share a common tag database format.

9. Connection Resource Budget for 20 CPUs

Every 314C-2DP has a fixed number of S7 communication resources (sometimes called "connection resources" or "connection slots"). Default partitioning reserves 1 for PG, 1 for OP/HMI, and 1 for S7 communication per CPU; the remainder are configurable. On the 314C-2DP the practical ceiling is 8–16 communication connections depending on the firmware version and STEP 7 configuration.

For a 20-CPU plant with one SCADA server, one engineering PG, and one HMI client, the connection budget per CPU looks like:

Total per CPU: 4–7 connections. With a 16-connection ceiling on the 314C-2DP this is comfortable for a single SCADA host. The risk emerges only when redundant SCADA servers or additional OPC gateways are added; at that point raise the "Max communication connections" parameter in HW Config and verify the firmware build supports the requested count.

10. Migration Path — 314C-2PN/DP and IM151-8 PN/DP

When a controller swap becomes justifiable (failed unit, capacity upgrade, new PROFINET tool roll-out), two drop-in replacements preserve the S7-300 footprint and add PROFINET:

For plants already standardized on TIA Portal, the 314C-2PN/DP is the lowest-friction swap: existing programs load with the same I/O address map, and the new PROFINET port opens the door to OPC UA on the CP343-1 Advanced or directly on the CPU's PN interface.

11. Multi-Vendor Considerations for Future Allen-Bradley Integration

When Allen-Bradley controllers (CompactLogix or ControlLogix) join the supervisory layer, the SCADA-facing transport must speak both S7 (or OPC UA from Siemens) and EtherNet/IP (or CIP from Allen-Bradley). Practical options:

1. Common OPC UA server per vendor. Each vendor's OPC UA server (SIMATIC NET for S7, RSLinx/FactoryTalk Linx for AB) exposes tags; Wonderware reads them through an OPC UA client driver. Cleanest tag namespace.
2. Kepware / TOP Server as a unified bridge. A single KEPServerEX instance with both Siemens TCP and AB EtherNet/IP drivers feeds Wonderware. Lower license cost than two vendor-native servers for small tag counts.
3. Direct I/O driver per vendor. Wonderware DAServer for S7 plus a DAServer for AB. Maintained but doubles the SCADA server administration.

Whichever path is selected, design the SCADA tag-naming convention around a plant-area hierarchy (e.g., AREA1_UNIT3_TEMP_PV) rather than around CPU addresses, so that swapping either vendor's CPU later does not cascade into the SCADA database.

12. Commissioning and Verification Procedure

The following sequence applies regardless of which transport option (A, B, or C) is chosen. Steps marked with a checkmark are the verification gates:

1. Inventory: confirm part numbers (6ES7314-6CF00-0AB0 on every CPU, plus CP/GW part numbers) and firmware versions on the operator panel.
2. Reserve connection resources in HW Config: set the CPU's "Max communication connections" to at least 8; reserve 1 for PG, 1 for OP, 1 for SCADA, 1 for routing headroom.
3. Configure the transport (NetLink GSD import + DP slot mapping, or CP343-1 IP / subnet mask, or CP5621 station parameters).
4. Download the STEP 7 / TIA Portal project to the CPU; perform a warm restart.
5. From the SCADA host, ping the CP or gateway IP address. ✓
6. Start the OPC / DAServer client; verify that the configured DB tags update at the expected rate. ✓
7. Disconnect the SCADA host network cable; verify that the CPU enters but does not deadlock — DP slaves should remain online, alarms should fire on comm-loss, and the PLC should resume SCADA polling within the configured retry window once the cable is restored. ✓
8. Run a 24-hour soak with Wonderware logging active; verify tag updates per second and absence of "Bad" quality codes. ✓

13. Troubleshooting Matrix

14. Field-Proven Recommendations

• Default selection for a 20-CPU plant already running on PROFIBUS: Option A — one NetLink-class gateway per 4–5 CPUs, paired with the Wonderware DAServer for SIMATIC S7. Lowest per-CPU cost and shortest retrofit window.
• Default selection for a new TIA Portal project or a plant expecting frequent SCADA tag-set changes: Option B — CP343-1 Lean in every rack. Higher per-CPU cost, but standard Ethernet, easy IP changes, and clean migration to OPC UA.
• Avoid Option C unless the SCADA host is physically co-located with the DP segment and a PROFIBus-trained controls engineer is available on site.
• Always raise the CPU's connection resource ceiling before commissioning. Default values are tuned for a single PG/OP and will not accommodate SCADA + engineering PG + routed SINAMICS connections.
• When Allen-Bradley arrives, choose OPC UA or KEPServerEX as the supervisory bridge; do not run two parallel SCADA drivers.