Connecting ET200S PROFINET CPU to PC Ethernet: OPC Setup Guide

David Krause13 min read
OPC / OPC UASiemensTutorial / How-to
Licensed PE Working through this on a live machine? A Maine-licensed engineer can take it from here — included with IMD hardware, by the hour for everything else. Book an engineer

Overview

The SIMATIC ET200S distributed I/O system with an integrated PROFINET interface (typical module: IM 151-8 PN/DP, order number 6ES7151-8AB01-0AB0) behaves on the network exactly like a standard Ethernet TCP/IP node for non-real-time services. This means a programming device, engineering station, or visualization PC can be patched directly to the CPU's PROFINET port with a standard Ethernet patch cable or, where auto-negotiation/crossover is required, an industrial crossover cable, with no managed switch or media converter in the path for commissioning, programming, and OPC DA/UA data exchange.

This guide covers the canonical scenario of an OPC-based HMI/scada visualization on a PC that needs to read and write process tags from an ET200S PROFINET CPU. It documents the required Siemens software stack (SIMATIC NET OPC server, STEP 7 V5.x or TIA Portal with PC station, PRONETA for diagnostics), the IP/Subnet plan, the NetPro S7 connection configuration, and field-proven troubleshooting when the link does not come up.

PROFINET is Ethernet — but not all Ethernet features are PROFINET. PROFINET uses standard IEEE 802.3 Ethernet physical and data-link layers, but adds three traffic classes: NRT (non-real-time TCP/IP), RT (real-time, cyclic, priority-tagged), and IRT (isochronous real-time, scheduled). For OPC visualization you only need NRT. The CPU's PROFINET port services both simultaneously, so a single cable carries engineering traffic and visualization traffic at the same time.

ET200S CPU Variants with PROFINET Interface

Not every ET200S CPU exposes PROFINET. Confirm the variant before sizing the network:

Order Number (MLFB) Designation PROFINET PROFIBUS Notes
6ES7151-8AB00-0AB0 IM 151-8 PN/DP Yes (1× PN port) Yes (master/slave) Early PN variant; firmware V2.x
6ES7151-8AB01-0AB0 IM 151-8 PN/DP Yes Yes Standard replacement PN/DP CPU; firmware V3.x
6ES7151-8FB00-0AB0 IM 151-8F PN/DP Yes Yes F-variant (fail-safe)
6ES7151-7AA00-0AB0 IM 151-7 CPU No Yes PROFIBUS only — not valid for this guide
6ES7151-1AA00-0AB0 IM 151-1 No No Slave interface only — no PN CPU

The firmware version is critical because the OPC S7 connection is established against a CPU whose communication resources (max S7 connections, OPC UA server endpoints) depend on firmware. See the Siemens Industry Online Support product page for the IM 151-8 PN/DP for the latest firmware and function manuals.

Network Topology — Direct, Switch, or Crossover

Three topologies are valid for the ET200S PROFINET ↔ PC path:

  1. Direct PC ↔ ET200S (no switch) — accepted for engineering, commissioning, and small visualization cells. Use a crossover patch cable if either side lacks Auto-MDI/MDIX (rare on ET200S hardware ≥2008 and any modern PC NIC).
  2. PC ↔ Industrial PROFINET switch ↔ ET200S — preferred for permanent installations because it allows additional PROFINET devices, SNMP-managed diagnostics, and clean port segmentation. Managed PROFINET switches must be PN-certified (e.g., SCALANCE XC/XB/XR family).
  3. PC ↔ Media converter ↔ ET200S fiber port — required only when the ET200S CPU module has been ordered with a fiber-optic PROFINET variant (Pof/LC) and the PC end is copper.

A direct PC connection is the simplest and most common configuration for an OPC visualization station. The ET200S PROFINET interface supports Auto-Negotiation and Auto-MDI/MDIX on all current IM 151-8 PN/DP revisions, so a standard 1:1 patch cable (TIA-568A on both ends) is normally sufficient.

Half-duplex caveat. PROFINET operates at 100 Mbit/s full-duplex on the wire. If the PC NIC negotiates to half-duplex (for example because of a faulty patch cable or a 10/100 unmanaged hub), real-time RT frames will be dropped, the link may report "Port down" in PRONETA, and OPC item updates will stall. Always force the PC NIC to 100 Mbps Full Duplex for PROFINET networks.

Cable and Connector Specification

Parameter Specification
Cable type PROFINET Type C (fixed), Type B (flexible), or industrial Cat 5e / Cat 6 SF/UTP
Conductor count 2×2 twisted pair (4 wires) for 100BASE-TX; PROFINET spec also allows 4-pair Type A
Connector RJ45 (industrial IP20 / IP67 variants)
Max segment length 100 m copper between two nodes (switch or device)
Impedance 100 Ω ± 15 Ω at 1–100 MHz
Color code (PROFINET) Yellow outer jacket (PROFINET), Green (PROFIBUS), Blue (PROFINET in hazardous areas) per IEC 61784-5-3 / IEC 61918

A standard gray Cat 5e patch cable from a PC works perfectly for a single point-to-point link, but for permanent installation use the PROFINET green/yellow cable so the segment is identifiable on the plant floor. Detailed cable requirements are in PROFIBUS & PROFINET International (PI) cabling guidelines and IEC 61918.

IP Address Planning

PROFINET devices are addressed by IP, not by PROFIBUS-style station address. Before installing software, define the addressing scheme:

Node IP Address Subnet Mask PROFINET Device Name Notes
ET200S CPU (IM 151-8 PN/DP) 192.168.0.10 255.255.255.0 et200s-cpu1 Must match the configured name in the PROFINET IO controller or the ET200S project
PC (engineering + OPC server) 192.168.0.20 255.255.255.0 n/a (PC station) Same subnet, no router required for direct link
Optional: PG/PC for STEP 7 192.168.0.30 255.255.255.0 n/a May be the same as the OPC station
PROFINET device name resolution. Unlike pure TCP/IP, PROFINET IO exchanges cyclic RT frames only after the IO controller has assigned the device name via DCP (Discovery and Configuration Protocol). For an ET200S acting as CPU with an OPC S7 connection, the name is mostly cosmetic for NRT traffic, but it must still be unique on the subnet and must match the configured name in the ET200S project so that PRONETA can find the device.

Prerequisites

  • ET200S station with IM 151-8 PN/DP CPU, terminal module, 24 V DC power module, and at least one digital I/O module.
  • 24 V DC power supply (PS 305 / PS 307 or equivalent) sized for the I/O count.
  • PC with Windows 10 / Windows 11 (64-bit) or Windows Server 2016/2019, ≥8 GB RAM, free NIC for the PROFINET connection.
  • Siemens SIMATIC NET DVD (current version: SIMATIC NET PC Software V18 SPx or later) for the OPC server. Note: SIMATIC NET is licensed per PC station; the OPC Server license is a separate softkey.
  • STEP 7 V5.7 (or TIA Portal V17/V18 with STEP 7 Professional) for NetPro/PC station configuration.
  • PRONETA V3.x (free) for diagnostics — available from Siemens Industry Online Support (entry ID 67460624).
  • Cat 5e / PROFINET patch cable, 100 m max.

Step-by-Step Configuration

Step 1 — Wire the ET200S Station

  1. Mount the IM 151-8 PN/DP onto the terminal module (TM-P / TM-E).
  2. Insert the power module (PM-E) and 24 V supply. Verify the green "24 V" LED on the PM-E is steady.
  3. Insert the I/O modules per the configured slot order.
  4. Insert the CPU termination module (TM-C) at the right end. The CPU will not start without it.
  5. Patch the RJ45 from the IM 151-8 PN/DP PROFINET port (labeled "PN" or "X1") to the PC Ethernet NIC.

Step 2 — Assign the ET200S IP Address and PROFINET Name

Two options exist; use PRONETA for first-time commissioning:

  1. Install PRONETA on the PC. Launch and click Network analysis → Settings.
  2. Set the PC NIC to a static IP inside the same subnet (for example 192.168.0.20/24).
  3. Click Start network scan. PRONETA will list the ET200S as an unknown device.
  4. Right-click the ET200S → Assign PROFINET name → enter et200s-cpu1. Confirm.
  5. Right-click → Assign IP address → enter 192.168.0.10 / 255.255.255.0. Confirm.
  6. Re-scan. The device should now show name and IP correctly.

Step 3 — Install SIMATIC NET OPC Server

  1. Insert the SIMATIC NET DVD. Run Setup.exe.
  2. Select Install → SIMATIC NET PC Software.
  3. Choose the installation type OPC Server and the correct PC station mode (PC station with own S7 connection).
  4. When prompted, transfer the license key (softkey) from the accompanying USB stick to the local license server.
  5. Reboot. After reboot the services S7ONLINE and OPC Server must be running. Verify with sc query S7ONLINE in an elevated command prompt.

Step 4 — Configure the PC Station in STEP 7 / TIA Portal

In STEP 7 V5.x (NetPro workflow):

  1. Open the SIMATIC Manager and the ET200S project (or create a new project for the PC station).
  2. Insert a new SIMATIC PC Station.
  3. Open the hardware catalog and drag an OPC Server application onto slot 1 of the PC station.
  4. Drag an IE General (Industrial Ethernet) module onto the PC station and select the PC's physical NIC.
  5. Assign the IE General the IP 192.168.0.20 / subnet 255.255.255.0.
  6. Compile and download the PC station configuration using Station → Download to PC Station. The target PC must have the Configuration Console running.

Step 5 — Define the S7 Connection in NetPro

  1. In NetPro, right-click the OPC Server on the PC station → Insert New Connection.
  2. Select S7 Connection as the connection type and the ET200S CPU (IM 151-8 PN/DP) as the partner.
  3. In the connection properties dialog, set:
    • Local ID: e.g. S7CONN_1
    • Partner IP: 192.168.0.10
    • Rack / Slot: 0 / 2 (default for IM 151-8 PN/DP)
    • Connection path: S7 connection, ISO-on-TCP or TCP (TCP recommended)
  4. Compile NetPro and download to the PC station again.

Step 6 — Browse and Test OPC Items

  1. Open the OPC Scout V10 (bundled with SIMATIC NET).
  2. Add a new OPC DA group and select the local OPC server entry.
  3. Browse the server. You should see the S7 connection S7CONN_1 with all configured DBs, Merkers (M), Inputs (I/E) and Outputs (Q/A).
  4. Add an item, e.g. S7:[S7CONN_1]DB1,REAL0, and watch it update at the configured update rate (default 1 s).
  5. Toggle a bit in the ET200S program (or force it online) to verify the round-trip latency and correctness.

Step 7 — Visualization

The OPC server now serves items to any OPC DA / OPC UA client. Common visualization stacks that consume these tags directly:

  • WinCC Professional (TIA Portal) — OPC DA native
  • WinCC V7.x — OPC DA native, OPC UA via SIMATIC NET UA wrapper
  • Third-party SCADA (Ignition, iFIX, Citect) — OPC DA Classic client
  • Custom .NET / Python clients via opcua library or OPC Foundation .NET API

Verification Checklist

Check Expected Result Tool
Link LED on ET200S PROFINET port Steady green (100 Mbit/s, FD) Visual inspection
PRONETA scan finds the ET200S with assigned IP and name Device listed, status = "OK / reachable" PRONETA
S7ONLINE service state RUNNING Windows services / sc query
Configuration Console shows OPC Server index 1 as "configured" Index row green Configuration Console
OPC Scout V10 browses items Items appear and update OPC Scout
ET200S diagnostic buffer clean No "Communication error" entries STEP 7 → PLC → Diagnostic Buffer

When a Switch Is Actually Needed

Move from a direct PC ↔ ET200S link to a switch when any of the following applies:

  • More than one PROFINET IO device is on the segment (typical cell with drives + I/O + HMI).
  • The PC runs a PROFINET IO Controller (not just NRT) and must act as supervisor for additional devices.
  • Port diagnostics are required (SCALANCE switches expose port statistics, error counters, and topology via SNMP/PRONETA).
  • Cable runs exceed 100 m (use SCALANCE with fiber uplinks).
  • The plant-floor specification mandates managed, PN-certified switches for conformance to PROFINET Conformance Class B/C.

For multi-vendor PROFINET integration where a Siemens CPU must exchange data with an EtherNet/IP-based controller, an industrial gateway such as the EtherNet/IP-to-PROFINET IO Device Gateway from Prosoft Technology is appropriate. This is a different architecture (the gateway acts as PROFINET IO Device on one side and EtherNet/IP scanner/adapter on the other) and is not the same as a direct PC Ethernet connection.

Troubleshooting Matrix

Symptom Likely Cause Diagnostic Step Resolution
PRONETA scan does not see the ET200S Cable, NIC speed/duplex, firewall Swap cable; check NIC = 100 Mbps FD; temporarily disable Windows Firewall Use a PROFINET-certified cable and force NIC to 100FD
ET200S reachable via ping but OPC Scout shows "Server not available" S7ONLINE not running, OPC server not downloaded sc query S7ONLINE; open Configuration Console Start S7ONLINE; download PC station configuration again
OPC items appear but values never update S7 connection not established OPC Scout → right-click group → Properties → Status Check ET200S diagnostic buffer for connection abort; verify Rack/Slot 0/2
Items update for ~30 s then stop TCP keep-alive or OPC group timeout Windows Event Viewer → SIMATIC NET logs Increase the S7 connection's "Establishment" retries; verify partner IP unchanged
SF (red) LED on IM 151-8 PN/DP PROFINET name mismatch or duplicate IP PRONETA → Topology → check duplicate IP detector Reassign unique PROFINET name; clear duplicate IP
BF (red bus fault) LED No link, wrong cable type, half-duplex PRONETA → Port statistics Replace cable; force 100FD; remove any 10/100 hub
OPC Scout sees items but reads garbage values Wrong data type or DB offset Compare tag address to STEP 7 DB definition Match data type (BOOL/INT/REAL) and byte offset exactly

Notes on TIA Portal vs STEP 7 V5.x

If the project is built in TIA Portal instead of STEP 7 V5.x, the equivalent workflow uses the PC station in the project tree and the Devices & Networks editor to define the S7 connection from the OPC server's IE interface to the ET200S PROFINET CPU. The OPC server is added as a software PLC in the device configuration. After compiling, the PC station is downloaded via the Target PC entry in TIA Portal, which uses the same Configuration Console backend as STEP 7 V5.x. Functional behavior of the OPC DA server is identical; TIA Portal's advantage is unified device library management when both the ET200S project and the PC station live in the same project.

Safety and Operational Considerations

Do not connect the PROFINET cell directly to the corporate LAN. An ET200S PROFINET CPU exposed directly to an engineering PC is fine for commissioning, but for production operation isolate the cell behind a SCALANCE security module or, at minimum, a managed switch with port-based VLAN segmentation. PROFINET RT frames are not routable, but TCP/IP-based attack surface (S7 communication, optional web server on the CPU, optional OPC UA server) is reachable from the LAN otherwise.

For F-variant ET200S CPUs (IM 151-8F PN/DP), the F-connection for PROFIsafe is configured in STEP 7 / TIA Portal with separate F-CPU parameters and is independent of the OPC S7 connection. The OPC server must never be used to write F-tag values directly; only the F-runtime in the F-CPU is allowed to do so.

FAQ

Do I need a switch between the PC and the ET200S PROFINET CPU?

No, for commissioning and single-cell visualization a direct PC ↔ ET200S cable is sufficient. PROFINET is Ethernet, and both the ET200S PN port and any modern PC NIC support Auto-MDI/MDIX. Add a managed SCALANCE switch only when you need multiple PROFINET devices, port diagnostics, or production-grade network segmentation.

Which SIMATIC NET component provides the OPC server for an ET200S CPU?

Use SIMATIC NET PC Software with the OPC Server option installed, plus the matching softkey license. Configure the PC station (OPC server + IE General) in STEP 7 or TIA Portal, define an S7 connection to the ET200S CPU, and download the PC station configuration through the Configuration Console.

What rack and slot do I use for the ET200S CPU in the NetPro S7 connection?

For the IM 151-8 PN/DP (6ES7151-8AB01-0AB0) the default rack/slot is 0/2. If the ET200S CPU is acting as an I-Slave behind an external PROFINET IO controller, the slot is determined by the project configuration. Always verify with the ET200S hardware catalog entry.

Can I use OPC UA instead of OPC DA for ET200S visualization?

Yes. Modern SIMATIC NET versions include an OPC UA wrapper that exposes the same S7 items as a UA server. The wrapper is configured in the OPC server's properties; the client (WinCC UA, Ignition, custom) connects via opc.tcp://<PC>:<port>. This is the recommended path when the visualization client is a non-Windows system or when data must traverse a firewall.

What is the simplest tool to verify the PROFINET link and IP configuration?

PRONETA (free from Siemens Industry Online Support, entry ID 67460624). Run a network analysis scan, assign the PROFINET device name and IP, and inspect port statistics, topology, and duplicate-IP detection from one GUI. PRONETA does not require STEP 7 and is ideal for first-time commissioning.

Back to blog