S7-1200 CPU 1214C "Partner Not Found" Error After Ethernet Disconnect: TIA Portal Topology Resolution

1. Problem Statement and Field Symptoms

Engineers commissioning a single-pair PROFINET installation — one S7-1200 CPU 1214C and one HMI PC station — frequently encounter a diagnostic alarm on the CPU the first time the Ethernet patch cable is removed for laptop access. The reported symptoms are:

• CPU diagnostic buffer (or HMI tag logging) shows "Error: Partner not found" or "Partner not found (IO device failure)".
• The error reappears every time the laptop-to-CPU programming cable is unplugged, even though no logical S7 connection was defined between the laptop and the CPU.
• Re-loading the TIA Portal project and performing an MRES do not clear the alarm.
• Reconnecting the cable to the HMI PC station does not auto-clear the alarm until the next power cycle of the CPU.
• The HMI runtime reports communication faults on its connection status indicator even though runtime data is being exchanged.

The error is non-fatal (the program keeps executing and the HMI exchange usually continues), but it floods the diagnostic buffer and obscures real faults, which is why it is considered a serious nuisance in 24/7 operations.

2. Affected Hardware and Software Stack

This issue is documented primarily on the following configuration:

The CPU 1214C ships with two integrated PROFINET interfaces on a single X1 socket (port 1 and port 2). Both ports support PROFINET IO Controller and IO Device roles, switching, and the topology/port-interconnection model that drives this fault.

3. Root Cause: Topology View Port Interconnection

Inside the TIA Portal project, the engineer typically performs two distinct network definitions:

1. Network View — A logical view. It defines which devices belong to which PROFINET subnet (PN/IE_1, for example) and which S7/HMI connections exist. The Network View does not specify which physical port is used.
2. Topology View — A physical view. It defines port-to-port cabling: e.g., CPU 1214C Port 1 ↔ HMI PC Port 1. The Topology View is required for advanced PROFINET features: device replacement without programming device (neighborhood detection), IRT (Isochronous Real-Time), and MRP / MRPD redundancy rings.

If the Topology View contains a port interconnection between the CPU and the HMI PC, the CPU expects a PROFINET link partner on that exact port at all times. When the cable is unplugged and routed to a laptop, the CPU's link partner at that port disappears. The PROFINET stack raises the diagnostic alarm "Partner not found" (PROFINET channel-error / maintenance alarm class) and writes it to the diagnostic buffer and to the HMI tag if one is mapped.

Because the alarm is generated by the PROFINET layer (not by the user program), a memory reset, a STOP→RUN transition, or a project reload will not clear it. The alarm self-clears only when the originally defined partner reappears on the same port — which never happens after a cable swap.

4. Network View vs Topology View — Functional Comparison

For a small cabinet with one PLC and one HMI that uses only PROFINET RT and does not require device replacement without a PG, the Topology View should normally be left empty. The Network View is sufficient.

5. Diagnostic Buffer and PROFINET Alarm Codes

The CPU records the alarm in the diagnostic buffer. Typical entries look like:

Event 1:  Connection aborted, partner not found
  Incoming event
  OB:           OB 82 (IO device fault / I/O access error)
  Port:         X1 P1
  Partner:      HMI_PC_1 / Port X1 P1
  Diagnostic ID: 0x0002  (Channel diagnosis - "Partner not found")

Useful diagnostic data points:

6. Step-by-Step Resolution Procedure

The verified fix is to remove the unintended port interconnection from the Topology View, recompile, and download. The procedure is reproduced below for both TIA V13 SP1 and current TIA versions (V16/V17/V18/V19).

6.1 Prerequisites

• Full offline project backup (.zap13 / .zap19 archive).
• Online connection to the CPU (PG/PC interface set to the CPU's PROFINET subnet).
• Know the CPU's IP address and PROFINET device name.

6.2 Delete Topology Interconnections

1. Open the TIA Portal project.
2. Navigate to Devices & Networks → select the network editor.
3. Click the Topology tab at the bottom of the network editor (next to Network view and Device view).
4. Inspect the topology canvas. Look for any line that connects a port of the CPU to a port of the HMI PC or another station.
5. Click each such interconnection line and press Delete (or right-click → Delete).
6. Confirm that the topology view now shows the stations without inter-port connections. The Network view should still show the original subnet/connection assignments.
7. Save the project (Ctrl+S).

6.3 Recompile and Download

1. Right-click the CPU → Compile → Hardware (rebuild all).
2. Select the CPU in the project tree and choose Download to device.
3. In the download dialog, tick "Consistent download" and "All blocks" to overwrite runtime data.
4. Confirm the download and let the CPU restart into RUN.

6.4 Clear Residual Diagnostics

1. Online → Diagnostics → Diagnostic buffer → Clear.
2. Power-cycle the CPU (optional but recommended) so any latched LLDP neighbour tables are purged.

6.5 Verification

1. Disconnect the Ethernet patch cable from the HMI and plug it into the programming laptop.
2. Watch the diagnostic buffer — no new "Partner not found" entries should appear.
3. Reconnect the HMI and confirm continuous data exchange.
4. Repeat unplug/replug several times to confirm the alarm does not recur.

7. Alternative Engineering Solutions

Removing the topology view works but assumes the engineer never needs IRT, MRP, or PG-less device replacement. When those features are needed, the cleaner long-term solutions are:

7.1 Add a Managed or Unmanaged PROFINET Switch

Inserting a Siemens SCALANCE XB005 (or any unmanaged PROFINET switch) between the CPU and the HMI means the laptop can be plugged into any spare switch port without disturbing the CPU ↔ HMI topology. This is the recommended pattern in any installation with more than two PROFINET nodes. The CPU's port-to-port topology remains intact regardless of which device the laptop talks to.

7.2 Define Topology for All Real Connections

If the cabinet uses IRT or MRP, every physical cable must be modelled in the Topology view. Leaving even one connection unmodelled causes the same alarm class during unplanned topology changes. Use the TIA Topology Editor's "Compare with real topology" function to detect any mismatch after commissioning.

7.3 Disable LLDP on the Affected Port (Last Resort)

LLDP is the mechanism by which a PROFINET device discovers neighbours and validates topology. Disabling LLDP on a port suppresses the alarm but is generally not recommended because it also disables device replacement without a PG. Use only on isolated programming ports.

7.4 Use a Dedicated PG Port on the CPU

The CPU 1214C exposes two ports. If port 1 is reserved for the HMI and port 2 is reserved for engineering access, the topology view can model only port 1's connection to the HMI, leaving port 2 free for the laptop. This is a clean architectural answer when the cabinet layout permits it.

8. Verification Test Plan

9. Preventive Configuration Best Practices

• Use the Topology View only when at least one of the following PROFINET features is required: device replacement without PG, IRT, or MRP/MRPD. Otherwise leave it empty.
• Document each topology edge with a cable label that matches the project (e.g., "C-PLC/HMI-01"). This dramatically simplifies field troubleshooting.
• After every project change, run Project → Compile → Hardware (rebuild all) and download the entire station, not just the changed blocks.
• For cabinets larger than two PROFINET nodes, install a PROFINET switch (SCALANCE XB-005 or XC-100/XC-200) rather than daisy-chaining on the CPU ports.
• Lock the CPU's port assignment in the device configuration to prevent an engineer from accidentally re-linking the wrong port to the topology.
• Maintain a project archive after every commissioning change so that the topology decision is reversible.

10. Related PROFINET Diagnostics and Cross-References

The "Partner not found" alarm is one of a family of channel-diagnostic alarms that the S7-1200 can emit. Engineers encountering this issue should also review:

• "Station failure" — Raised when an entire PROFINET IO Device drops off. Often co-occurs with "Partner not found" when the HMI is the dropped station.
• "Link down" — Pure layer-1 alarm. No link pulse on the RJ45. Check cabling, SFP, or port damage before suspecting topology.
• "Name assignment error" — PROFINET device name does not match what the controller expects. Common after CPU replacement.
• "Device replacement without PG failed" — Only fires when Topology view is defined and a replacement device cannot be located by serial number / neighbourhood.

The diagnostic mechanism is documented in the Siemens SIMATIC PROFINET with STEP 7 V13 function manual and the S7-1200 programmable controller system manual, available from the Siemens Industry Online Support portal (entry ID 109751826 and 91696622). Always cross-check with the firmware-specific manual because the diagnostic buffer format has evolved across FW V2, V3, and V4 generations of the S7-1200.

11. Troubleshooting Matrix

12. Frequently Asked Questions