S7-1200 Wrong Partner Port Error: TIA Portal Topology Fix

1. Problem Statement

A Siemens S7-1200 CPU 1211C (any firmware version from V1.0 through V4.x at time of writing) returns the diagnostic string Error on partner - wrong partner port immediately after a project is loaded from TIA Portal. The CPU's ERROR LED blinks red at roughly 2 Hz, the CPU remains in STOP, and the diagnostic buffer accumulates one entry per power cycle or per reconnection attempt of the PROFINET interface.

The condition is non-destructive: the project is not corrupt, the hardware is functional, and the same project loads successfully to a different CPU of the same part number. The fault lies in PROFINET topology metadata that TIA Portal embeds in the device configuration but that the CPU validates against the physical cabling.

2. Understanding the "Wrong Partner Port" Error

PROFINET devices, including the integrated PROFINET interface of an S7-1200 CPU, advertise the physical port numbers they expose (Port 1 = X1 P1, Port 2 = X1 P2 on the CPU's RJ45 sockets). When the engineering tool generates a project, it can also describe expected neighbours at each port — the partner device, partner port, and the cable that should connect them. This is the PROFINET topology model (see IEC 61784-2 / PROFIBUS & PROFINET International specification "PROFINET Topology").

If the CPU starts up and either:

1. finds a device at a port that does not match the expected partner, or
2. finds no device at a port where the project expected a partner,

it raises a port-diagnostics alarm and the string "Error on partner - wrong partner port" surfaces in TIA Portal's Online & Diagnostics view.

3. Why S7-1200 on the Bench Triggers It

The S7-1200 family does not require a PROFINET topology to be configured for normal operation. Topology editing is mandatory on S7-1500 / ET200SP high-availability or MRP-ring commissioning because those features depend on it. On the S7-1200, the topology editor is informational only — but TIA Portal will still write whatever topology it finds in the project into the device, and the CPU will validate it on every startup.

The first time a beginner opens Devices & Networks and clicks the Topology view at the bottom of the editor, TIA Portal often shows a single line from CPU → (unconnected port). After dragging any HMI or ET200 onto the same subnet, the editor begins to draw lines. Lines that are drawn by the engineer, but not present on the bench, cause exactly this error class.

4. Diagnostic Buffer Entries to Expect

Open the diagnostic buffer with the CPU online:

1. Mark the CPU device in the project tree.
2. Click Go online (or right-click → Online & Diagnostics).
3. Open the Diagnostics group → Diagnostic buffer.

Typical entry shape for this fault:

Event 1  of  5   09:42:11.317  2024-03-18
  Event ID            : 0x001E  (Port diagnostics data changed)
  Description         : PROFINET interface - Port 1
  Port                : X1 P1
  Error               : Partner port not configured / wrong partner port
  Direction           : ---  ---
  Operating state     : CPU in STOP

Event ID 0x001E is the standard PN port-diagnostics change event. The exact description text in TIA Portal is "Error on partner - wrong partner port" or "Wrong partner port" depending on TIA Portal version. Earlier portals (V13/V14) show "Wrong partner port"; V15 and later show "Error on partner - wrong partner port".

5. Step-by-Step Resolution (Primary Method)

Goal: delete every topology link in the project and download again.

1. In the TIA Portal project tree, open Devices & Networks.
2. At the bottom of the editor, click the Topology tab (next to Network view and Device view).
3. Click into an empty area of the canvas to deselect anything.
4. Press Ctrl+A to select all topology objects (devices, ports, interconnect lines).
5. Press Delete. Confirm any prompt that warns about removing links.
6. Repeat Ctrl+A / Delete until the topology canvas is empty.
7. Do not delete anything in the Network view tab — keep the PROFINET subnet and the CPU→HMI/IO device connections.
8. Right-click the CPU device → Compile > Hardware (rebuild all).
9. Right-click the CPU device → Download to device > Hardware and software (or use the Download toolbar button).
10. Confirm the PG/PC interface points to the correct network adapter and the CPU is found by the search.
11. After the download completes, observe the ERROR LED: it should stop blinking within 2–3 seconds as the CPU performs port re-initialisation.

6. Alternative Resolution (Clean Project Download)

If the topology view still appears to hold objects after step 6 (this can happen after a TIA Portal version migration), take the "clean slate" approach:

1. Create a new empty project.
2. Add a new S7-1200 CPU device matching the part number on the front panel (e.g. 6ES7 211-1BE40-0XB0 for CPU 1211C DC/DC/DC, or 6ES7 211-1HE40-0XB0 for DC/DC/Relay).
3. Set the PROFINET interface IP address to the one your machine uses (default 192.168.0.1 for CPU 1211C).
4. Do not open the topology view at all.
5. Drag a single observation OB (e.g. OB1 with one normally-open contact wired to a single output Q0.0) to verify I/O.
6. Compile → Download → verify the CPU goes to RUN and the ERROR LED is off.
7. Once the bare configuration works, re-import the user's actual program blocks or paste logic from the original project.

This approach is recommended when the original project was inherited from a different engineer and the offline/online mismatch is unclear. It removes all invisible port relationships the editor may have retained.

7. Port-to-LED Reference for the CPU 1211C

For the CPU 1211C, both PROFINET ports sit on the same MAC and the same IP; they form a built-in switch. A wrong-partner-port diagnostic will normally reference Port 1 because Port 1 is where most project templates auto-place the first neighbour.

8. When Topology Configuration Is Required

Although the S7-1200 does not require topology for the project to run, there are legitimate cases to populate the topology editor on a different device in the same project:

• S7-1500 CPU with PROFINET devices configured for IRT (Isochronous Real Time). IRT topologies are validated at compile time and again at runtime.
• MRP (Media Redundancy Protocol) ring with an S7-1500 acting as MRP manager. The ring ports must be defined and the ring must close physically.
• PROFIenergy shutdown signals on a tool where the tool controller validates that the cable from CPU Port 1 actually arrives at the expected ET200 Port 1.
• Port-interconnect-based diagnostics web pages where the maintenance team wants the CPU's web server to highlight a broken cable between two specific ports.

If your S7-1200 project is none of these, leave the topology empty.

9. Verification Procedure

After applying the fix, validate that the CPU is healthy:

1. Power-cycle the CPU (or use Online → MRES followed by a STOP→RUN transition).
2. Go online and open Online & Diagnostics on the CPU.
3. Open Diagnostic buffer and confirm there is no new port-diagnostics entry after the most recent STOP→RUN transition.
4. Open PROFINET interface → Port statistics. Port 1 and Port 2 should both show Link status: Up (if physically connected), and Discarded frames: 0.
5. Open Topology on the live CPU. The LLDP neighbours list should match the physical cabling (or be empty if the CPU is the only device on the segment).
6. Confirm the ERROR LED is off and the MAINT LED is off.
7. Force a single boolean output (e.g. Q0.0) from a watch table to confirm the program executes.

10. Troubleshooting Matrix

11. Common Pitfalls After the Fix

• Re-introducing the fault during peer review: if a colleague later opens the topology view and drags a connection across the canvas, the project file is dirty again. Add topology content only via the Network view; do not use the Topology view on S7-1200 projects unless the design specification explicitly requires it.
• Library reuse: if the S7-1200 is used as a copied master in a library (typed/non-typed), the topology metadata travels with the copy. Run the §5 cleanup on the library type, not just the instance.
• HMI on the same subnet: the HMI's integrated PROFINET port is reported as a neighbour; if the HMI is added but not yet physically connected, the CPU complains. Either add the HMI after bench validation, or use the topology editor to delete only the HMI link.
• GSD re-import: importing a new GSD for a third-party IO device can rewrite the device's port order. After every GSD update, repeat the topology-clean procedure.

12. Long-Term Practice for S7-1200 Projects

Document a project-wide convention for the S7-1200 family so the same fault never reappears:

1. Treat the Network view as the single source of truth for PROFINET connections.
2. Treat the Topology view as disabled by default. Enable per-device only via a project option flag the team's checklist tracks.
3. In the project template, place a Placeholder device at the subnet root with a comment "Topology intentionally empty".
4. At the end of every project, the engineer runs a macro that exports the topology view to a PDF and checks it is one page of empty canvas. The PDF is filed with the project.