Resolving S7-1200 PLC Connection Error in TIA Portal

David Krause13 min read
S7-1200SiemensTroubleshooting
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

Resolving S7-1200 PLC Connection Error in TIA Portal

The "Connection Error" reported when a Siemens SIMATIC S7-1200 CPU 1214 DC/DC/DC fails to appear in the Accessible nodes pane of TIA Portal (V15–V19) is one of the most common commissioning blockers. Although the engineering station can sometimes read the device's MAC or IP address from the network, the PG/PC cannot complete the S7COMM handshake required to populate the Online > Accessible nodes tree. The fault almost always traces to one of six layers: the physical Ethernet segment, the PROFINET switch, the Windows PG/PC interface assignment, the TIA Portal project subnet, the Windows firewall, or a CPU firmware/protocol mismatch. This reference walks through the diagnostic sequence a control engineer should follow, the parameter values to set, and the verification steps that prove the link is restored.

1. Problem Definition and Symptoms

The reported condition is consistent across all firmware generations of the CPU 1214 DC/DC/DC (order number 6ES7214-1AG40-0XB0, V4.x) when TIA Portal cannot establish an S7 online connection:

  • The S7-1200 LED pattern shows LINK steady green on the PROFINET port (X1), confirming physical link-up, but the CPU RUN/STOP remains in RUN, indicating the PLC program is unaffected.
  • The PG/PC sees the IP address of the CPU in the Network and Sharing Center via ARP or via the Siemens Primary Setup Tool (PST), but the S7-1200 does not appear under Online > Accessible nodes.
  • TIA Portal returns one of the following system events: 0x0010 Connection error, Online: A connection could not be established, or Failed to read the device description.
  • Clicking Flash LED from the Accessible nodes dialog does not illuminate the CPU's MAINT or LINK LED.
Important: Seeing the IP address in the Windows network adapter state does not confirm an S7 connection. ARP resolution proves layer 2/3 reachability only; the S7COMM protocol at ISO-on-TCP (port 102) must still be allowed and matched to the PG/PC interface.

2. S7-1200 PROFINET Interface Reference

Before changing any setting, capture the baseline parameters of the CPU 1214 DC/DC/DC. The relevant electrical and protocol characteristics of the integrated PROFINET interface X1 are documented in the SIMATIC S7-1200 Programmable Controller System Manual (Entry ID 109751706):

Parameter Value Source
Ethernet connector RJ45, 10/100 Mbit/s, auto-crossover (Auto-MDI/MDIX) S7-1200 System Manual, Section 4.2
Default IP address (factory) 0.0.0.0 (unconfigured) or 192.168.0.1 (after first download) S7-1200 System Manual, Section 4.3
Supported protocols PROFINET IO Controller/Device, S7COMM, SNMP, LLDP, DCP S7-1200 System Manual, Section 4.4
Number of S7 connections Up to 8 PG/OP + 8 S7 (configurable) TIA Portal device configuration
Port used for PG communication TCP/102 (ISO-on-TCP, TSAP 01.01) S7COMM standard
Power consumption of PROFINET interface Internally powered, no external load S7-1200 Data Sheet

3. Root Cause Matrix

The following matrix maps the six failure layers to the diagnostic evidence and the corrective action. A control engineer should eliminate the upper layers first because they are reversible without any hardware substitution.

Layer Symptom Quick Check Fix
L1 – Physical LINK LED off, no ARP entry Loopback plug or known-good patch cable Replace cable, use shielded Cat 5e minimum
L2 – Switch LINK on, but no PROFINET DCP discovery Direct PC-to-CPU crossover, disable managed switch features Bypass managed switch, disable EEE (green Ethernet), disable Spanning Tree on PROFINET port
L3 – PG/PC interface No nodes visible in TIA Portal Set S7ONLINE access point to the physical NIC Reassign PG/PC interface in Control Panel > Set PG/PC Interface
L4 – IP/subnet Device visible, connection refused ping from command prompt Set PG/PC to same subnet (e.g., 192.168.0.10/24) with no duplicate address
L5 – Firewall Ping OK, S7COMM blocked Temporarily disable Windows Firewall Add inbound rule for TCP 102 and UDP 34964 (DCP)
L6 – Firmware/protocol Accessible nodes list empty with newer TIA Portal Compare CPU firmware with TIA Portal release Update CPU firmware via SIMATIC Automation Tool or use compatible TIA Portal version

4. Prerequisites Before Changing Settings

Document the following items before any modification. They are the inputs the verification step will need:

  1. CPU order number and firmware version (read from the side-panel label, e.g., 6ES7214-1AG40-0XB0 / V4.5.1).
  2. TIA Portal version and installed HSP (Hardware Support Package), e.g., TIA Portal V17 Update 5 with HSP 0296.
  3. Project device configuration: PROFINET device name, IP address, subnet mask, router address.
  4. Current PG/PC IP address, subnet mask, and the S7ONLINE access point assignment (default: S7ONLINE (STEP7) > TCP/IP > <NIC>).
  5. Topology sketch: which switch port, which VLAN, whether the switch is managed and whether PROFINET QoS or LLDP is enabled.
  6. Whether Online > Accessible nodes has ever worked with this PC on a different machine (rules out PC-level issues).

5. Step-by-Step Diagnostic Procedure

5.1 Confirm Physical Link (Layer 1)

Verify the LINK LED on the CPU's X1 socket. If it is dark, swap the patch cable and try a different switch port. For a CPU 1214 DC/DC/DC, the LINK LED behavior is documented in the S7-1200 System Manual (Entry ID 109751706) Section 4.2.1: a steady green LINK LED indicates an established 100 Mbit/s link, an amber LED indicates 10 Mbit/s. If both ends negotiate 10 Mbit/s, the connection will be functional but slow; verify that the managed switch port is not hard-coded to 10 Mbit/s half-duplex.

5.2 Bypass the Switch (Layer 2)

Many "Connection Error" messages on S7-1200 commissioning are caused by managed switches with energy-efficient Ethernet (EEE, IEEE 802.3az) or aggressive Spanning Tree enabled. Connect the PG/PC directly to the CPU using a Cat 5e crossover or straight-through cable (the S7-1200 supports Auto-MDI/MDIX, so either wiring is acceptable). If Accessible nodes now displays the CPU, the switch is at fault. Disable the following features on the PROFINET port of the managed switch:

  • Green Ethernet / Energy Efficient Ethernet (EEE)
  • Spanning Tree (RSTP) for the port, or enable port-fast/edge mode
  • IGMP snooping for the PROFINET multicast groups (FF02::1, 239.255.255.255)
  • Storm control and broadcast throttling below 5%
  • VLAN tagging (PROFINET is untagged by default, VLAN 0/native)

5.3 Assign the PG/PC Interface (Layer 3)

The most frequent cause of Accessible nodes returning an empty list is an incorrect S7ONLINE access point assignment. The PG/PC may be sending discovery (DCP) on the Wi-Fi adapter while the cable is plugged into the wired NIC. Reassign as follows:

  1. Open the Start menu > Siemens Automation > Set PG/PC Interface.
  2. Under Access point of the application, select S7ONLINE (STEP7).
  3. Under Interface parameterization used, choose the wired network adapter currently connected to the CPU. The TCP/IP(RFC1006) protocol must be checked.
  4. Click OK and restart TIA Portal.

If the wired NIC is named Intel I219-LM on a TIA Portal V18 installation, the dialog will show the path as Intel I219-LM → TCP/IP → S7ONLINE (STEP7). Confirm the same path appears in Windows Control Panel > Network and Internet > Network Connections.

5.4 Match the IP Subnet (Layer 4)

Open a Windows command prompt and execute:

ipconfig /all arp -a ping <CPU IP address>

Compare the PG/PC IPv4 address and subnet mask with the CPU's PROFINET configuration in TIA Portal. The CPU 1214 DC/DC/DC's PROFINET interface is configured in Device View > Properties > PROFINET interface > Ethernet addresses. If the project shows 192.168.0.1/24 and the PG/PC is on 192.168.1.10/24, the broadcast domain is split. Either:

  • Reconfigure the CPU to match the PG/PC subnet (online), or
  • Use the Primary Setup Tool or SIMATIC Automation Tool to set a temporary IP from the same subnet, or
  • Use a direct Ethernet cable and configure the PG/PC with a static IP in 192.168.0.10/24.

5.5 Configure the Windows Firewall (Layer 5)

TIA Portal's Accessible nodes mechanism uses PROFINET DCP on UDP port 34964 for discovery and ISO-on-TCP (RFC 1006) on TCP port 102 for S7 communication. Windows Defender Firewall blocks both by default on a non-domain workstation. Siemens provides a hardening guide in Entry ID 109751706. Add the following inbound and outbound rules to the Domain and Private profiles:

Protocol Port Direction Application
TCP 102 Inbound/Outbound Siemens.TIA.Portal.exe, S7DOSDST.EXE
UDP 34964 Inbound/Outbound Siemens.TIA.Portal.exe
UDP 49152–65535 Outbound DCP response and SIMATIC discovery
Caution: Disabling the firewall entirely is a temporary diagnostic step only. Re-enable it and add explicit rules before returning the station to production.

5.6 Verify Firmware and TIA Portal Compatibility (Layer 6)

Cross-reference the CPU firmware against the TIA Portal release matrix published in the S7-1200 system manual and the SIMATIC S7-1200 CPU 1214C DC/DC/DC firmware update article. A typical matrix entry looks like:

CPU Order Number FW Min TIA Portal Recommended
6ES7214-1AG40-0XB0 V4.0–V4.2 V14 SP1 V15.1
6ES7214-1AG40-0XB0 V4.3 V15.1 V16
6ES7214-1AG40-0XB0 V4.4 V16 V17
6ES7214-1AG40-0XB0 V4.5 V17 Update 3 V18
6ES7214-1AG40-0XB0 V4.6 V18 Update 3 V19

If the CPU firmware is newer than the TIA Portal version can service, Accessible nodes will detect the device but TIA Portal will refuse the connection with 0x80072EFD or 0xE0EB0005. Either install the matching HSP or update the CPU firmware to a known-good revision using a SIMATIC Memory Card (SMC) and the S7-1200 firmware update procedure.

6. Restoring the Connection from TIA Portal

Once the layers above are confirmed, perform the in-TIA Portal repair sequence:

  1. Open the project and select the CPU device in the project tree.
  2. From the menu, choose Online > Accessible nodes. TIA Portal should display the CPU within 5–10 s. The MAC address, IP address, PROFINET device name, and firmware version are listed in the Accessible nodes dialog.
  3. Click Flash LED to physically verify you are targeting the right device. The LINK LED on X1 will blink at 2 Hz for three seconds.
  4. If the CPU is not configured, right-click and select Online & diagnostics > Assign IP address. Enter a free address inside the project subnet and click Assign.
  5. If the PROFINET device name is unset, use Assign PROFINET device name. The device name must match the entry in the project under Device View > PROFINET interface > PROFINET tab; it is case-sensitive.
  6. Download the configuration: Right-click CPU > Download to device > Hardware and software (only changes).

7. Verification Checklist

Run the following checks in order. Each must pass before the next is attempted. Record the result in the commissioning log.

Check Expected Result Pass / Fail
LINK LED on X1 Steady green (100 Mbit/s)
ping to CPU IP < 5 ms, 0% loss, 4 of 4 replies
ARP entry present Static or dynamic entry for CPU MAC
Accessible nodes lists CPU Visible with IP, MAC, name, FW
Flash LED responds LINK LED blinks 2 Hz × 3 s
Online & diagnostics opens Diagnostic buffer readable, no entries with time stamp 0
Download completes Compile clean, transfer OK, restart type: Run
CPU enters RUN RUN LED green, STOP off, MAINT off

8. Edge Cases and Field-Proven Caveats

8.1 Duplicate IP Address

If another device on the network has the same IP, the CPU's LINK LED remains lit but the S7-1200 will intermittently drop the connection. Symptoms include Connection Error followed by short recovery. Use arp -a on the PG/PC to confirm only one MAC resolves to the IP. If duplicates appear, change the CPU's IP via the SIMATIC Automation Tool.

8.2 Virtualization and VPN

TIA Portal running inside a VMware Workstation, Hyper-V, or a Remote Desktop session over VPN often sees Accessible nodes empty because the virtual NIC is bound to the S7ONLINE access point. Force the S7ONLINE access point to the bridged physical NIC, or run TIA Portal on the host OS.

8.3 PROFINET Device Name Conflicts

The S7-1200 PROFINET device name is unique per network. If two CPUs were both configured with the default cpu1214 name in past projects, only the first responder will be found by DCP. Rename the device under Device configuration > PROFINET interface > PROFINET > PROFINET device name to a unique, machine-relative value (e.g., line3-press-cpu01).

8.4 Energy Efficient Ethernet (IEEE 802.3az)

Some Cisco, HPE, and Hirschmann switches ship with EEE enabled. The S7-1200 does not support EEE. When the switch goes into low-power idle state, the CPU's LINK LED flickers and S7COMM timeouts occur. Disable EEE globally on the switch or per port.

8.5 Multiple Network Adapters

A laptop with active Wi-Fi and a wired Ethernet connection may route the DCP discovery frames over the wrong interface. Open Set PG/PC Interface, select the wired adapter explicitly, and disable Wi-Fi during commissioning.

9. Diagnostic Buffer Interpretation

When Online & diagnostics is reachable, the diagnostic buffer is the single most informative resource. Common S7-1200 events that correlate with a Connection Error:

Event ID Meaning Likely Cause
0x013C Connection established Informational; the issue is upstream of the S7 stack
0x013D Connection terminated TIA Portal closed session; normal
0x0117 Number of connections exceeded Reduce active PG/OP/HMI connections in device configuration
0x05E0 PROFINET IO controller: station failure Switch or device on PROFINET network lost
0x0070 Parameter assignment error Project hardware configuration mismatch

10. Escalation to Siemens Support

If all six layers pass and the CPU still does not appear in Accessible nodes, gather the following package before opening a Support Request at the Siemens Industry Online Support portal:

  • CPU order number, firmware version, and serial number (printed on the side label).
  • TIA Portal version, installed HSPs, and Windows build number.
  • IP configuration of the PG/PC and the CPU.
  • Output of tracert and pathping to the CPU IP.
  • TIA Portal diagnostic logs: C:\Users\<user>\AppData\Local\Siemens\Automation\Logfiles.
  • Wireshark capture filtered on udp.port == 34964 || tcp.port == 102, 60 s duration, while reproducing the error.

Quote the relevant Siemens Knowledge Base entry IDs in the request. The most frequently referenced entries for this scenario are Entry ID 109751706 (S7-1200 system manual) and Entry ID 109760042 (Accessible nodes troubleshooting).

11. Preventive Measures

To keep an installation free of recurring Connection Error reports after commissioning:

  1. Maintain a cell-specific commissioning checklist that records the S7ONLINE access point, the PG/PC IP, the CPU IP, and the PROFINET device name on a per-station basis.
  2. Pin the TIA Portal version per cell. Mixing TIA Portal V16 and V18 within the same production line is a common cause of "invisible" CPUs after a hardware swap.
  3. Lock the PROFINET device name in TIA Portal so it is downloaded with the project; do not leave it for the operator to assign.
  4. Standardize the managed switch configuration: disable EEE, enable PROFINET QoS (DSCP 46 for cyclic traffic, DSCP 34 for acyclic), enable LLDP on the port facing the CPU.
  5. Periodically export the CPU's diagnostic buffer to the plant historian so the timestamp correlation is preserved across shifts.

Why does the S7-1200 appear in Windows network discovery but not in TIA Portal Accessible Nodes?

Windows discovery uses the Link Layer Topology Discovery (LLTD) and SMB browser service, which have no relationship to the PROFINET DCP frames on UDP 34964 that TIA Portal uses. The S7-1200 only answers DCP, not LLTD, so visibility in Windows does not imply S7COMM reachability. Reassign the S7ONLINE access point to the wired NIC and confirm the firewall allows UDP 34964 and TCP 102.

Can a managed Ethernet switch cause a Connection Error on a single S7-1200?

Yes. The most common managed-switch defects that break PROFINET discovery are Energy Efficient Ethernet (IEEE 802.3az), aggressive Spanning Tree timers, IGMP snooping filtering PROFINET multicast groups, and storm control. Disable EEE, set the PROFINET port to port-fast/edge, and either disable IGMP snooping or whitelist the 239.255.255.255 range.

How do I reset the IP address of an S7-1200 CPU 1214 to factory defaults?

Power down the CPU, insert a SIMATIC Memory Card (SMC) with a freshly written firmware file from the S7-1200 system manual, then power up. The CPU will boot with the firmware on the card and the IP address will be reset to 0.0.0.0 (unconfigured). You can then assign a new IP from TIA Portal via Online > Accessible nodes > Assign IP address.

What is the default TSAP for an S7-1200 PG connection?

The default Transport Service Access Point (TSAP) for a PG connection on the S7-1200 is 01.01 on the local end and 01.01 on the partner end. TIA Portal's Accessible nodes uses this default automatically; manual override is only required when integrating third-party OPC servers or non-Siemens HMIs.

Is TIA Portal V19 compatible with CPU 1214 DC/DC/DC firmware V4.4?

Yes, TIA Portal V19 supports all S7-1200 V4.x firmware revisions when the corresponding Hardware Support Package is installed. However, Siemens recommends running a CPU on the firmware revision that matches the TIA Portal version used for its last project download to avoid surprise configuration defaults after a download.

Back to blog