Configuring S7-1200 PC-Based HMI with TIA Portal WinCC Runtime

Overview: PC-Based HMI for S7-1200 Systems

Many automation architectures pair a Siemens S7-1200 PLC with a physical Comfort or Basic Panel for operator visualization. However, when a project already supplies an industrial PC or a control-room workstation for a cobot controller or upstream MES/SCADA node, dedicating a separate HMI panel to visualization becomes redundant. In these cases, the PC itself can host the operator interface using TIA Portal's PC Station concept and one of the WinCC Runtime packages, eliminating the cost and panel-cutout work of an additional hardware HMI.

Two technically distinct paths exist for displaying an S7-1200 HMI on a PC screen:

1. WinCC Runtime on a Windows PC (TIA Portal path) — A full WinCC project is loaded onto the PC's runtime and exchanges tags with the S7-1200 over PROFINET/Ethernet. This delivers the same look, feel, alarms, recipes, and scripting capabilities as a physical Comfort Panel.
2. S7-1200 integrated webserver (firmware path) — The PLC's onboard webserver serves standard diagnostic pages, and optionally user-defined HTML pages with AWP (Automation Web Programming) variable placeholders. Any browser on the network can view them. No WinCC license is required, but functionality is limited to read-mostly dashboards unless JavaScript is added.

The choice between the two depends on the required depth of operator interaction, licensing budget, and whether the PC must run other control software (cobot runtime, vision, MES client) in parallel.

Prerequisites

Before starting either path, confirm the following items are in place:

• TIA Portal installed: A version that matches the target S7-1200 firmware. TIA Portal V17 supports S7-1200 firmware V4.5; TIA Portal V18 supports firmware V4.6; TIA Portal V19/20 support firmware V4.7. Mixed-version projects are blocked by the TIA Portal compiler.
• STEP 7 Basic or Professional license: Required to author the S7-1200 program and HMI configuration.
• WinCC Runtime license: For the PC-based HMI path, WinCC Runtime Advanced (16, 128, 512, 2048, 4096, 8192 PowerTags) is needed. The license is keyed to the PC and is activated via Automation License Manager (ALM).
• S7-1200 firmware: V4.0 or higher recommended for full webserver AWP capability. V4.4+ adds HTTPS/TLS and improved user-defined page syntax.
• Network infrastructure: Managed switch (or direct crossover) on a common subnet. The PC, S7-1200, and any cobot controller must share a routable subnet.
• Static IP addressing: Avoid DHCP for automation devices. Reserve IPs in a documentation register.

WinCC Version Selection Matrix

TIA Portal bundles four WinCC editors whose runtime targets differ. The selection determines which PC configuration objects and runtime installers are loaded.

For a single S7-1200 driving a cobot cell with one PC acting as the operator interface, WinCC Runtime Advanced is the correct and most economical selection. WinCC Professional is over-scoped unless the project grows into a multi-server SCADA topology.

Step-by-Step: WinCC Runtime Advanced on PC

Step 1 — Add the PC Station

1. Open the existing TIA Portal project that contains the S7-1200 (PLC_1).
2. In the project tree, click Add new device > PC systems > PC station.
3. Select WinCC Runtime Advanced from the catalog and drag it onto the PC Station's slot 1.
4. If the WinCC Advanced editor is not visible in the portal, install the optional package from the TIA Portal installation medium under Setup > WinCC Advanced.

Step 2 — Configure the Network Interface

1. Open the PC Station Device view.
2. Click the PC Station's Ethernet port and assign a static IPv4 address on the same subnet as the S7-1200 (for example, PC = 192.168.0.10 / 255.255.255.0; S7-1200 = 192.168.0.20 / 255.255.255.0).
3. Open the S7-1200 Device view > PROFINET interface > Ethernet addresses and confirm the IP/subnet match.
4. In the project tree, right-click the PC Station and select Connect to PLC > S7-1200 PROFINET interface. TIA Portal draws a PROFINET line between the two devices.

Step 3 — Add an HMI Connection

1. Switch from the portal to the project view.
2. Expand WinCC Runtime Advanced > HMI tags.
3. Create a new connection of type S7-1200 / S7-1500.
4. Set the partner (PLC) IP to the S7-1200's address.
5. Set the connection name to a meaningful identifier (for example, HMI_PLC_1).

Step 4 — Author Screens

1. Open WinCC Runtime Advanced > Screens and add a new screen (for example, Overview, Manual_Control, Alarm_Log).
2. Use the toolbox to place I/O fields, buttons, bars, gauges, alarm views, and trend views.
3. Bind each element to an HMI tag. Tags can be internal (local) or external (pointed at PLC DB bits/words via the connection).
4. For PLC-side variables, declare the DB unoptimized (non-optimized block access) when external HMI tags use absolute addressing; symbolic access works regardless.

Step 5 — Compile and Download

1. Select the PC Station and click Compile > Software (rebuild all).
2. Resolve any compile errors. Common ones include missing tags, invalid connection paths, or expired trial licenses.
3. Connect the engineering PC to the S7-1200 over Ethernet and click Download to device > PC Station.
4. In the wizard, select the network adapter that faces the S7-1200.
5. Confirm the transfer; WinCC Runtime starts automatically on the PC after download completes.

Step 6 — Verify Runtime Operation

1. Launch WinCC Runtime on the PC. The configured start screen should appear.
2. Force a bit in the S7-1200 from the online monitor; the corresponding HMI I/O field must update within one polling cycle (default 1 s).
3. Trigger a configured alarm from the PLC program; confirm the alarm view populates and the alarm buffer increments.
4. Toggle a button on the HMI and verify the PLC receives the write via online tag monitoring.

Step-by-Step: S7-1200 Webserver Path

When the project tolerates read-mostly dashboards and avoids the cost of a WinCC license, the S7-1200's integrated webserver is a viable path. The PLC itself acts as a web server on TCP port 80 (HTTP) or 443 (HTTPS from firmware V4.4 onward).

Step 1 — Enable the Webserver

1. Open the S7-1200 Device view > Web server.
2. Check Activate web server on this module.
3. Select HTTP, HTTPS, or both based on network security policy. HTTPS is mandatory when user-defined pages carry credentials or write operations.
4. Assign user rights (Administrator, Read-only, Custom) under User management. Define password complexity per site IT policy.
5. Download the configuration to the PLC.

Step 2 — Access Standard Pages

1. From any PC on the same subnet, browse to http://192.168.0.20 (replace with PLC IP).
2. The default Introduction, Diagnostics, Module Information, Communication, and Variable Status pages appear.
3. The Variable Status page accepts a tag name and displays its current value, useful for quick commissioning checks without WinCC.

Step 3 — Build User-Defined Web Pages

1. In the S7-1200 Device view > Web server > User-defined pages, add a new HTML file.
2. Author the HTML/CSS locally in any text editor. Use AWP (Automation Web Programming) commands to read and write PLC tags: <!-- AWP_Out_Variable Name="MyTag" -->, <!-- AWP_In_Variable Name="MyTag" -->, ::=MyTag: for variable substitution.
3. Reference tags by symbolic name from the PLC program or DB.
4. Transfer the HTML file to the PLC via the Download to device wizard under Web server.
5. Browse to http://192.168.0.20/yourfile.html to view the user page.

Connection Topologies

The diagram below illustrates the typical cabling when both paths coexist. The cobot controller, PC running WinCC Runtime, and S7-1200 share a managed switch on a 192.168.0.0/24 subnet. The webserver path uses the same physical cable but a different application layer (HTTP over TCP 80/443) versus WinCC Runtime (PROFINET/S7 over TCP 102 and DCP on UDP 34964).

Configuration Parameters Reference

Troubleshooting Matrix

Verification Checklist

Before handing the cell to operations, run the following acceptance tests and record values in the commissioning log:

• PLC IP ping from PC: ping 192.168.0.20 -t for 60 seconds, zero packet loss.
• WinCC Runtime boots within 30 seconds after Windows login.
• Every external HMI tag updates when the corresponding PLC tag is forced in STEP 7 online monitor.
• Every HMI write button reflects in the PLC tag within one cycle.
• Alarm acknowledgment from the HMI clears the alarm in the PLC's diagnostic buffer.
• Webserver returns the configured HTML page with correct tag values.
• Browser HTTPS padlock is present (if HTTPS enabled).
• Power cycle the PC: WinCC Runtime auto-starts (verify under Windows Startup settings).
• Network switch link lights remain solid under load (no flapping).

Field-Proven Caveats

The following points come up repeatedly on commissioning sites and are worth addressing in the design phase:

• TIA Portal version drift: If the project file is opened in a newer TIA Portal than originally authored, the project is upgraded and may become incompatible with peers still on the older version. Lock the project to a single TIA version across the engineering team.
• WinCC license reactivation after hardware swap: Reactivating a license on new PC hardware consumes one activation event. Plan for a license pool sized to expected PC turnover.
• S7-1200 webserver throughput: The webserver is implemented in the PLC's firmware and shares CPU with the user program. Heavy polling of many tags from many browser clients can slow scan time. Limit the number of simultaneous browser sessions and refresh intervals to ≥ 2 s for non-critical dashboards.
• Browser compatibility: User-defined HTML pages may include JavaScript that runs differently across Chrome, Edge, and Firefox. Test across the browser fleet that operations uses.
• Operating system support: WinCC Runtime Advanced supports specific Windows builds (currently Windows 10 LTSC and Windows 11 per the TIA Portal compatibility matrix). Verify before deploying on a new PC SKU.

FAQ