PROFINET Network Setup Across Plant Subnets: Configuration Guide

1. PROFINET Subnet Fundamentals

PROFINET is an Industrial Ethernet protocol defined in IEC 61158 and IEC 61784 that uses standard IEEE 802.3 frames to transport cyclic process data, acyclic parameter data, and diagnostic information between an IO Controller (typically a PLC such as a SIMATIC S7-1500 or S7-1200), IO Devices (distributed I/O like ET 200SP, field instruments, weight transmitters, drives), and IO Supervisors (engineering or HMI stations). Although PROFINET is "Ethernet-based," it is not drop-in compatible with the managed switches, VLAN policies, and DHCP pools that IT departments deploy for office traffic.

The PROFINET specification, published by PROFIBUS & PROFINET International (PI), requires the IO Controller to assign the IP address, station name, and subnet mask to every IO Device via the Discovery and Configuration Protocol (DCP). DCP is a Layer 2 multicast protocol operating on Ethernet multicast address 01:0E:CF:00:00:00. Because DCP is non-routable, an IO Controller cannot reach an IO Device that lives behind a Layer 3 router unless an explicit router path is configured in TIA Portal and the underlying switch fabric forwards the multicast frame.

Two practical conclusions follow:

1. If all PROFINET nodes are addressed in the same IP subnet (for example 192.168.1.0/24) and on the same broadcast domain, the IO Controller discovers and assigns every device without any router configuration.
2. If the plant topology forces nodes onto different subnets (such as 172.16.102.0/24 on the ground floor and 172.16.103.0/24 on the third floor), the IO Controller can still reach the IO Devices only when (a) the network between subnets is configured with router awareness in TIA Portal, (b) DCP multicast is permitted through the routing devices, and (c) Quality of Service is preserved end-to-end.

2. Why Mixing IT and OT Networks Fails

Connecting an IO Controller or IO Device to the office intranet is a recurring anti-pattern that almost always produces latent failures. The mismatch between Information Technology (IT) and Operational Technology (OT) priorities manifests in several concrete ways:

The PI Working Group "PROFINET Installation" documents the same conclusion in the PROFINET Installation Guide: PROFINET segments should be physically or logically separated from any other Ethernet traffic unless the network planner can guarantee end-to-end QoS and zero packet loss.

3. Architecture Options for Distributed Plants

When devices are physically separated by more than the 100 m copper reach of PROFINET type-C cable, the engineer has three viable architectures, ranked by preference.

3.1 Option A — Dedicated OT Backbone (Preferred)

Install PROFINET-rated switches (Siemens SCALANCE XC-200, SCALANCE XR-300, or third-party PN-certified switches from Phoenix Contact, Hirschmann, Cisco IE-3300, etc.) at each floor, then interconnect them with PROFINET type-C copper patch cords or single-mode fiber. The IO Controller, all IO Devices, and engineering stations share one private subnet (commonly 192.168.0.0/24 or 172.16.0.0/24). No router is required. A SCALANCE XC208 manages eight PROFINET devices per port cluster and provides SNMP, LLDP, and PROFINET diagnostics.

3.2 Option B — Fiber Optic Extension

Where civil works allow, run single-mode 9/125 µm fiber between floors. PROFINET supports fiber media via SCALANCE fiber switches (SCALANCE XF204-2BA, for example) or media converters. Single-mode OS2 fiber reaches 70 km at 100 Mbit/s, eliminating any distance concern between the 1st and 3rd floor. PROFINET type-D fiber cabling has no practical length limit for industrial use.

3.3 Option C — IT-Managed VLAN (Compromise)

If plant policy mandates use of the IT infrastructure, negotiate a dedicated VLAN with the IT department. Configure the access port on each floor as an untagged member of a specific VLAN ID (e.g., VLAN 200) and the trunk port between switches to carry that VLAN with 802.1Q tagging. TIA Portal can be configured to use a router if the VLAN spans routed subnets. This option remains fragile: any IT-side change can disable production.

4. PROFINET Real-Time Classes and Switch Requirements

The PROFINET specification defines three conformance classes that directly determine which switch hardware is acceptable.

Weight transmitters (Siemens SIWAREX, Mettler-Toledo IND360, Sartorius PR 6241, Minebea Intec PR 5900) typically publish at update times of 10–100 ms over PROFINET RT. They do not require IRT, so a Conformance Class B switch is sufficient. The vendor datasheet must always be checked for the published conformance class.

PROFINET uses Priority Tagging (VLAN ID 0, PCP bits 6 for RT, 7 for IRT). Office switches that interpret a zero VLAN ID as "not a VLAN member" will drop the frame. Managed switches must be configured to trust the priority field even when the VLAN ID is zero. The PI organization maintains a list of PROFINET-certified devices.

5. IP Assignment and the DCP Protocol

During commissioning, the IO Controller assigns IP, subnet mask, and station name to every IO Device through DCP. The sequence is:

1. IO Controller sends DCP Identify multicast (01:0E:CF:00:00:00).
2. IO Devices without an IP respond with their MAC address and current name.
3. Engineer assigns the station name in TIA Portal (e.g., wt-floor3-01).
4. IO Controller sends DCP Identify (unicast) to confirm the device by name.
5. IO Controller sends DCP Write to push IP, mask, and gateway.
6. IO Device reboots its network stack and joins the configured subnet.

6. TIA Portal Configuration for Multi-Subnet PROFINET

6.1 Prerequisites

• TIA Portal V17 or later (V18 / V19 recommended for current device libraries)
• S7-1500 CPU firmware V2.9 or higher (for full PN IRT and MRPD support)
• GSD files for each IO Device, installed via Options → Manage General Station Description (GSD) files
• Each IO Device must support DCP-based identification (all PROFINET-certified devices do)

6.2 Step-by-Step Cross-Subnet Configuration

1. Define the PROFINET interface on the IO Controller. Open Device → Properties → PROFINET interface, set IP address (e.g., 192.168.1.10/24), and clear the automatic router.
2. Assign a station name to the controller, e.g., plc-floor1. PROFINET uses names, not IPs, for device discovery.
3. Assign each IO Device an IP address and station name. For cross-subnet nodes, set the IP outside the controller's native subnet, e.g., 192.168.2.20/24, and enter the gateway as the router interface on the local subnet.
4. Enable "Use router": in the IO Controller's PROFINET interface properties, navigate to Ethernet addresses → PROFINET and tick "IO Controller uses a router to reach IO Devices." This adds the router (default gateway) to the controller's ARP table so DCP can be initiated across subnets.
5. Compile and download the project. TIA Portal downloads the routing table and IO Device IP list into the CPU.
6. Online → Assign PROFINET device name. Right-click each IO Device and assign its station name. The CPU then writes the IP and gateway to the device over DCP.
7. Verify: Online → Diagnostics shows all IO Devices in RUN. In the topology editor, confirm that the LLDP neighbors match the physical wiring.

6.3 Router and Gateway Configuration

Each IO Device must know the IP address of the router that connects its subnet to the IO Controller's subnet. If the plant uses SCALANCE switches with Layer 3 capability, configure the switch as a router with the appropriate VLAN interfaces and IP helpers. The SCALANCE XR-300 series, for example, supports static routes and OSPF, see the SCALANCE XR-300 operating instructions on the Siemens Industry Online Support portal.

7. Switch Selection and Certification

Switch selection drives the maximum achievable PROFINET cycle time and the diagnostic depth available in TIA Portal.

Always confirm the PN certificate number (format "PN-Cert-NNNNN") on the vendor datasheet and cross-check against the PI product catalog. A switch sold as "PROFINET-compatible" without PI certification will not be listed.

8. Fiber Optic Extension for Long Distances

Where copper cable cannot bridge the distance, PROFINET supports fiber-optic media at the physical layer. Two implementation patterns are common:

• Media converter pair: install a copper-to-fiber media converter at each floor (e.g., SCALANCE XF204-2BA, which has two fiber SC ports and four RJ45 ports). The IO Controller and IO Devices connect to copper ports; the converters link over fiber.
• Native fiber switch: use a switch with integrated fiber uplink, eliminating the converter. SCALANCE XC-200GF and SCALANCE XR-300 have SFP slots for 1000BASE-SX or 1000BASE-LX single-mode optics.

PROFINET does not require any change in the application program when switching from copper to fiber. The PROFINET frame format is identical; only the physical layer changes.

9. VLAN and Priority Tag Handling

PROFINET RT frames use VLAN priority tagging per IEEE 802.1Q with VLAN ID = 0 and PCP = 6 (for RT) or PCP = 7 (for IRT). VLAN ID 0 is a special case in IEEE 802.1Q called "Priority Tagged Frame" and carries only priority, no VLAN membership.

Common office switch pitfalls include:

• Cisco IOS default: Frames with a non-zero PCP but VLAN ID 0 are dropped because the port is not a member of any VLAN. Workaround: enable mls qos trust cos and vlan dot1q tag native, or configure the access port as "voice VLAN" so the priority field is accepted.
• HP/Aruba: Some firmware versions strip the VLAN tag by default, downgrading the priority to best-effort. Set the port to tagged-all mode.
• Unmanaged switches: Pass VLAN ID 0 transparently; usually safe for PROFINET RT.

10. Commissioning and Verification Procedures

1. Topology check: TIA Portal Online → Topology should show every switch and IO Device with its LLDP neighbor. A missing neighbor indicates a wiring or LLDP problem.
2. Station status: Online → Accessible nodes must list every PROFINET device with its assigned IP and station name in green.
3. Port statistics: in the PROFINET diagnostics, each port should show zero or near-zero discarded frames. A non-zero discard counter indicates QoS or multicast filtering issues.
4. Cycle time measurement: in the IO Controller's PROFINET interface diagnostics, record the actual update time and jitter. With PROFINET RT on a Conformance Class B switch, expect <1 ms jitter.
5. Wireshark capture: install Wireshark on a mirrored switch port and confirm that PROFINET RT frames arrive with PCP = 6 and VLAN ID = 0 intact.
6. Failure-injection test: temporarily disconnect the cable to one IO Device and verify that the IO Controller raises the expected diagnostic interrupt within one update cycle.

11. Troubleshooting Matrix

12. Field-Commissioning Notes and Best Practices

• Use Siemens PRONETA (free utility) for offline network analysis, IO test, and topology discovery during commissioning. PRONETA 3.x supports all PROFINET conformance classes and can read/write device names without TIA Portal.
• Reserve a /24 subnet for PROFINET even if it seems wasteful. Future expansions (additional ET 200 stations, drives, instruments) will consume addresses quickly.
• Document the network: keep an up-to-date topology diagram, IP plan, and station name list in the plant CMMS. PROFINET station names are case-sensitive and must match exactly between TIA Portal and the device.
• Apply IEC 61918 / IEC 61784-2 installation rules for cable separation from power, grounding, and shielding. The PROFINET Installation Guide from PI consolidates these.
• Enable SNMP on switches: TIA Portal integrates switch diagnostics when SNMPv3 is configured on the SCALANCE switch and the controller. This gives cycle-time statistics, port errors, and temperature in the same HMI as the process values.
• Disable unused services: turn off PROFINET discovery on office-facing ports to prevent accidental connection of misconfigured IT devices into the OT segment.