Connecting S7-1200 to OP170B HMI: Limits & Workarounds

Overview

Engineers upgrading or expanding SIMATIC installations frequently ask whether a legacy Siemens text/graphics panel of the OP 170 / OP 170B family can talk directly to a modern SIMATIC S7-1200 CPU. The short, definitive answer is no: the OP 170B does not provide an Industrial Ethernet interface, the S7-1200 has neither an MPI port nor a PROFIBUS DP-slave port, and the only communication stack that both sides share (PROFINET/Ethernet) is missing on the panel side. This article documents the hardware boundaries on both ends, the protocol drivers available in WinCC flexible 2008 SP2, the exact incompatibility matrix that rules out a native link, and the four practical migration paths that engineers have used in field retrofits.

OP 170B Hardware & Communication Capabilities

The OP 170B is a 5.7" monochrome or STN-color HMI from the SIMATIC HMI Component series (originally launched with ProTool, later migrated to WinCC flexible). Two variants exist:

Both variants carry exactly one physical communication port: a 9-pin sub-D RS-485 socket that can be parameterized as either MPI (default) or PROFIBUS DP slave. The operating-instructions manual ("TP 170micro, TP 170A, TP 170B, OP 170B (WinCC flexible) Operating Instructions", Siemens order 6AV6 691-1DA01-0AB0) lists the section "Process coupling" which enumerates every PLC family the panel will accept:

• SIMATIC S7-200 via PPI / MPI / PROFIBUS
• SIMATIC S7-300 / S7-400 via MPI or PROFIBUS
• SIMATIC S7-1200 — not listed
• SIMATIC S7-1500 — not listed
• SIMOTION, SINUMERIK, third-party PLCs (via OPC or Modbus slave driver) — not listed for this MLFB

The OP 170B has no Ethernet MAC, no PROFINET controller/device capability, and no integrated TCP/IP stack. Any WinCC flexible project that selects "Ethernet" as the connection type will fail to download to the panel because the runtime firmware refuses an Ethernet channel.

S7-1200 Communication Interfaces

The S7-1200 CPU family (firmware V4.0 through V4.7, plus the TIA-Portal V20 S7-1200 G2 line) provides the following on-board and plug-in interfaces:

Key facts every engineer must internalize when judging S7-1200 ↔ legacy-HMI compatibility:

1. No MPI. The MPI protocol stack is not implemented in any S7-1200 CPU or in any communication module offered for it.
2. No native PROFIBUS DP slave. The CP 1242-5 (6GK7 242-5DX30-0XE0) operates only as a DP-Master for distributed I/O, never as a slave. There is no DP-Slave CP for S7-1200.
3. No Modbus RTU/TCP master natively for legacy Siemens panels. Modbus master / slave blocks are runtime libraries (MB_CLIENT / MB_SERVER / MB_SERIAL) added in the user program; the panel would still need a driver that supports Modbus on its own RS-485 port, which WinCC flexible 2008 SP2 only supplies for S7-300/400 and S7-1200, not Modbus.
4. PROFINET is the only native deterministic bus. Connection to any modern Siemens HMI therefore requires the panel to have an Ethernet/PROFINET port.

Direct Compatibility Assessment

Combine the two hardware matrices above and the result is unambiguous:

Every row collapses to the same conclusion. There is no combination of off-the-shelf cabling, baud-rate switching, or firmware update that bridges the missing endpoints.

Process-Coupling Matrix from the Operating Manual

Section 3.4 ("Process coupling") of the WinCC flexible operating instructions for TP 170micro / TP 170A / TP 170B / OP 170B enumerates the legal PLCs. Reproducing the relevant excerpt prevents mis-communication with end-customers who assume "Siemens-to-Siemens" should always work:

The matrix is the same in every language edition of the manual; the OP 170B firmware does not receive a "hidden" Ethernet upgrade through service packs.

Alternative Connection Architectures

When the OP 170B must remain in service (for example, because the panel is mechanically embedded in a stainless-steel console with a long lead-time spare, or because the end customer insists on "touch nothing"), four workarounds appear in field practice. They are listed in increasing cost and complexity.

Option A — Replace the OP 170B with a PROFINET-Compatible Panel

The cleanest answer. Recommended replacements that fit a 5.7" cut-out:

• SIMATIC HMI KTP400 Basic mono PN (6AV2 123-2DB03-0AX0) — 4" wide-screen, PROFINET, configurable from TIA Portal or WinCC flexible 2008 SP2.
• SIMATIC HMI TP1500 Basic (6AV2 123-1DB02-0AX0) — 15" PROFINET, requires TIA Portal V13+.
• SIMATIC HMI TP700 Comfort (6AV2 124-1GC01-0AX0) — 7" PROFINET, requires TIA Portal V14+.

Drop-in replacement is rarely mechanical because the OP 170B uses a 198 × 142 mm cut-out while KTP/TP7xx use different hole patterns. A bezel adapter is usually required. Configuration: import the OP 170B WinCC flexible project into TIA Portal V16 or higher using "Migrate project". Tags and screens come across; alarm logging requires manual rework because the OP 170B lacked the bit-level alarm archive. Verification: open the migrated project, compile, download, and read back the S7-1200 tags with the panel online diagnostic (\"Settings → OPC diagnostic\" in the Comfort series).

Option B — Insert an S7-300/400 as a PROFIBUS-to-PROFINET Gateway

Insert a SIMATIC S7-315-2 PN/DP (or any S7-300 with both a PN port and a DP port) between the OP 170B (on the DP side) and the S7-1200 (on the PN side). Configure the S7-315-2 PN/DP as a DP slave to the OP 170B (operating mode "DP slave" in STEP 7 Hardware) and as a PROFINET IO controller to the S7-1200 (with the S7-1200 acting as a PROFINET device). Data exchange is realized in the S7-300 by a copy program (e.g., copy DB100 of the OP 170B-side image into the PN output area of the S7-1200). This architecture is field-proven and re-uses both the existing panel and the new S7-1200, but introduces a third PLC and a second programming tool (STEP 7 V5.5 or TIA Portal). Limitations: the S7-300 must remain powered; a stop of the gateway drops the panel connection.

Option C — Use a Stand-alone Industrial Gateway

A third-party PROFINET-slave-to-PROFIBUS-DP-slave converter such as the Helmholz DP/PN Coupler (700-158-3SH02) or HMS Anybus X-Gateway PROFIBUS Slave ↔ PROFINET Slave (AB7648) maps memory ranges 1:1 between the two buses. Configuration procedure:

1. Mount the gateway between the OP 170B DP socket and the S7-1200 PROFINET cable.
2. In TIA Portal, add the gateway as a PROFINET device to the S7-1200 project. The GSD file is supplied by the gateway vendor.
3. In WinCC flexible 2008 SP2, add the gateway as a "PROFIBUS DP slave" with the configured slot length (typical: 32 bytes in / 32 bytes out for the Anybus AB7648).
4. Define the S7-1200 tag DBs that map to the gateway slots; configure the OP 170B tags against the gateway input/output slots.
5. Download both projects and verify with the gateway's web diagnostic page.

This option costs less than Option B and removes the S7-300. It is the canonical retrofit path for OEMs that ship hundreds of identical machines with an OP 170B already wired.

Option D — Convert the OP 170B Project to OPC-UA on a PC-RT

When the project was originally targeting a PC runtime, the PC can be retained as the OP 170B front-end while talking to the S7-1200 through OPC UA. The OP 170B itself cannot be reused as the PC panel; it has no OPC UA client and no Ethernet. This option is therefore listed for completeness only and is not a true "OP 170B to S7-1200" solution.

Configuration Procedure When Using the Helmholz DP/PN Coupler (Option C, expanded)

The Helmholz DP/PN Coupler is field-tested with both WinCC flexible 2008 SP2 and TIA Portal V16+. The procedure below assumes the S7-1200 is the PROFINET IO controller and the OP 170B is the PROFIBUS DP master.

Prerequisites

• Helmholz DP/PN Coupler, FW ≥ 2.4 (700-158-3SH02).
• S7-1200 CPU with firmware ≥ V4.2 (TIA Portal V16).
• OP 170B with WinCC flexible 2008 SP2 project archive (.hmi file or .zap16).
• GSD file "HELM_7648.gsd" supplied on the Helmholz USB stick.

Step-by-Step

1. Wire the bus. PROFIBUS cable from the OP 170B DP socket (terminator ON at the panel) to the gateway's DB-9. PROFINET cable from the gateway's RJ-45 to the S7-1200 PROFINET port 1. Apply 24 V DC to the gateway.
2. Add the gateway in TIA Portal. Options → "Manage general station description files (GSD)" → import "HELM_7648.gsd". Drag the gateway to the PROFINET topology. Set its device name to dp-pn-coupler and assign IP 192.168.0.50 / 255.255.255.0.
3. Configure the PROFINET slot. Insert modules "16 bytes I / 16 bytes O" or "32 bytes I / 32 bytes O" as needed. Compile and download the S7-1200 project.
4. Configure the gateway's web UI. Open http://192.168.0.50 → "Diagnostics" → verify "PROFINET connection: established" and "PROFIBUS connection: data exchange".
5. Configure WinCC flexible 2008 SP2. Connection → "SIMATIC S7-300/400" → type "PROFIBUS DP". Address = the PROFIBUS station number assigned to the gateway (default 3). Configure the I/O slot mapping in "Area pointer" to match the PROFINET slot chosen in step 3.
6. Transfer the WinCC flexible project. Use Ethernet or RS-232 "PPI / MPI transfer" to push the panel runtime. Because the OP 170B has no Ethernet, use the Siemens PC adapter USB / MPI 6GK1 571-0BA00-0AA0 plus the OP 170B configuration port.
7. Verify tag traffic. In WinCC flexible "Tools → Tags → Status", force a value change on an S7-1200 tag bound to the gateway and confirm the panel reflects it within one bus cycle (≤ 50 ms at 1.5 Mbit/s PROFIBUS).

Diagnostics & Verification

Use the following matrix when the panel connection fails after configuration:

For deeper PROFINET analysis on the S7-1200 side, open TIA Portal → "Online → Online & diagnostics" on the CPU → "PROFINET diagnostics" → inspect "Connection status" and "Port statistics". A healthy link shows 0 CRC errors and 0 discarded frames; CRC counts rising faster than one per 10 minutes indicate a marginal cable run.

Common Pitfalls

1. Assuming "Siemens-to-Siemens just works". The protocol-mismatch table above is the single most-ignored fact in retrofit bids.
2. Confusing the OP 170B with the TP 170B. TP 170B is Ethernet-capable; OP 170B is not. The "B" suffix is a generation marker, not a model distinction that implies Ethernet.
3. Buying a CP 1242-5 to fix the issue. The CP 1242-5 is a DP master, not a slave. Adding it to the S7-1200 does not allow the OP 170B to poll the CPU.
4. Forgetting to enable the S7-1200 PUT/GET server. When a third-party panel or gateway uses unsolicited reads (PUT/GET), the option must be enabled in TIA Portal under "Properties → Protection & Security → Connection mechanisms → Permit access with PUT/GET from remote partner". This is on by default but blocked by "Know-how protection" if the program is encrypted.
5. Pulling the wrong GSD revision. Helmholz ships separate GSD files for DP and PN sides. Using the PN-side GSD on the DP side, or vice versa, gives a "module mismatch" error at compile time.

Migration Path Recommendations

When neither the OP 170B nor the S7-1200 is locked by the end customer, the recommended migration sequence is:

1. Replace the OP 170B with a TIA Portal Comfort Panel (TP700 / TP900 / TP1200). Comfort panels ship with PROFINET and full S7-1200 symbolic tag support.
2. Migrate the WinCC flexible project to TIA Portal using "Project → Migrate HMI project".
3. Re-author any scripts that used legacy "Set / Get" bit commands (the Comfort firmware uses the newer "PLC tags with symbolic addressing").
4. Validate the HMI runtime against an S7-PLCSIM instance of the S7-1200 program before downloading to the live CPU.

This removes the panel-bus question entirely and unifies the engineering toolchain on TIA Portal V16+ (V20 for new deployments).

FAQ