IMDTouchKnowledge BaseShop main store

Selection guide

Where WinCC Unified Runtime Can Run and Remote HMI Options

HMI and touchscreens Published 7 min read

Short answer

The Unified runtime executes only on a PC, a Panel IPC, a Unified Comfort Panel or the MD-34 tablet; a browser or Sm@rtServer VNC client displays it and never replaces the host. With no PC in the cabinet, a Unified Comfort Panel is the host and the tablet browser is the client. If a safety function must travel with the operator, no Unified mobile panel exists and the design stays Comfort-based.

On this page
  1. Host and client are two different jobs
  2. The four host classes and two non-Unified alternatives
  3. What the browser and the VNC client actually do
  4. The safety function decides the platform
  5. Comfort panels, licenses and versions
  6. Choosing the host for an outdoor machine with no PC in the cabinet
  7. Commissioning the branch you chose
  8. Questions asked

The WinCC Unified runtime executes on four device classes: a PC running WinCC Unified, a Panel IPC, a Unified Comfort Panel, or the MD-34 tablet that runs Unified RT. A browser or a Sm@rtServer VNC client never replaces the host; it only views and operates a runtime that already runs somewhere. A classic Comfort Panel cannot host Unified at all. So with no PC in the cabinet, the host is either a Unified Comfort Panel on the machine or the MD-34 tablet itself, and if a safety function must travel with the operator, no Unified mobile panel exists and the project stays on the Comfort platform.

Host and client are two different jobs #

Unified splits the work in two. The runtime is the process that talks to the PLC and holds the alarms, recipes and scripts; the client is what the operator sees and touches. The runtime needs exactly one host; the client can be almost anything with network access. This is the same direction question that decides HMI OPC UA server vs client: which direction works, and it is where Unified migrations go wrong: whether the panel can serve its own web server only becomes a question once you know which device executes the runtime. A device that executes the runtime also serves its clients. A device that cannot execute it — every classic Comfort Panel, which runs a Windows PE-based system — hosts nothing, no matter what points at it.

The four host classes and two non-Unified alternatives #

Four device classes execute the Unified runtime. Two further architectures answer the same operator need without Unified, and they stay in the comparison because one of them is the only row that carries a safety function.

Architecture Runtime executes on Local operator screen Remote access Handheld safety function
PC with WinCC Unified The PC, the SCADA-class host engineered in TIA Portal PC monitor Built-in web server; browsers on the network None on any client
Panel IPC The panel PC; runtime and client on one device The IPC screen Web server on the IPC serves browsers None on any client
Unified Comfort Panel The panel itself The panel screen Built-in web server; browsers view the panel's runtime None on any client
MD-34 tablet with Unified RT The tablet The tablet The tablet operates its own runtime None; a display, not a safety device
Classic Comfort Panel with Sm@rtServer The panel, Comfort runtime The panel screen One VNC mirror through Sm@rtServer None on any client
Fail-safe mobile Comfort panel The panel The panel in the operator's hand Mirror where the device supports it Yes; stop and enabling circuits wired to the safety chain

The web client reaches the runtime of a Unified PC or a Unified Comfort Panel from any device on the network — that is what the built-in web server is for. The MD-34 is the only handheld among the four; it is also the newest and narrowest, so verify availability, licensing and the environmental rating in current Siemens ordering data before the design freezes. A Unified Comfort Panel is downloaded and commissioned from TIA Portal like any other Unified device, and you pick the display size and bezel rating the outdoor mounting calls for.

What the browser and the VNC client actually do #

On the Unified side, the web server belongs to the device that executes the runtime: type the host's IP address into a supported browser and the project runtime renders there. The runtime owns TCP/80 on the IPC, which matters when a PLC web server shares the address — the S7-1500 web pages then need a port-forward or NAT rule on the IPC to appear behind the same address. The web server runs in parallel with the VNC Sm@rtServer on the same device, so a fixed screen can work over VNC while tablets use the browser.

On the Comfort side, Sm@rtServer is a VNC server that runs on Comfort Panels. A VNC client — Sm@rtClient or a generic VNC app — mirrors the panel screen and sends touch back; the panel runs the project exactly as it does locally, and the remote device only receives the picture and returns input. When a Sm@rtClient session is refused, the password and the loopback settings are the usual suspects, covered in Why Sm@rtServer rejects Sm@rtClient on a WinCC runtime PC.

The safety function decides the platform #

One safety note, and it comes first in every selection: a browser, a VNC mirror and a tablet host all display and write tags, and none of them is a safety device. If the risk assessment requires an emergency stop or an enabling function that travels with the operator, the handheld must be a fail-safe mobile panel with its stop and enabling circuits wired into the machine safety chain — and because no mobile panel exists for Unified, that single requirement fixes the platform as Comfort.

Below that threshold, the field arrangement is proven: one shop replaced its fail-safe mobile panels with a fixed Comfort Panel in the cabinet plus an Android tablet running a VNC client. Forms, notes and camera photos happen on the tablet, and a damaged tablet is swapped like a consumable. The KTP700F mobile panel is the responsiveness benchmark if a mirror ever feels slow — it is reported to run without lag.

Comfort panels, licenses and versions #

Unified and the classic Comfort world are incompatible: the engineering backbone changed, and no conversion makes a classic Comfort Panel a Unified host, so the choice is made per project. In the other direction, a PC runtime for classic WinCC runs a slightly modified version of the Comfort panel project, and that PC needs a runtime license the mobile panel does not. The license always sits on whatever executes the runtime; confirm the count against current ordering data before quoting.

On versions: V17 field use reported bugs and features still missing relative to Comfort panels, and much of that was added or fixed in V18. Freeze the design only after the version you will install covers recipes, parameter entry and alarms.

Choosing the host for an outdoor machine with no PC in the cabinet #

Inputs #

  • One machine outdoors; the operators keep a safe distance while it runs and still need full HMI access (the design case behind this article).
  • Zero PCs in the control cabinet (the stated constraint).
  • Zero safety functions on the handheld: this case's risk assessment keeps the emergency stop on the machine's safety hardware.
  • Operator duties: parameter entry, recipes, process monitoring.
  • One Android tablet on WiFi as the remote client.
  • TIA Portal V18 or later, because the V17 feature gaps were largely closed in V18.

Rule #

Count the host classes that survive each constraint. The runtime must execute on exactly one surviving host; a client is never a substitute for a host.

Arithmetic #

  • Unified host classes: 4 (PC, Panel IPC, Unified Comfort Panel, MD-34 tablet).
  • Classes that need a boxed PC added to this cabinet: 1 (the PC). Surviving: 4 − 1 = 3.
  • Handheld safety functions required: 0, so no class drops out on safety. At 1, the survivors fall to zero and the design moves to the one fail-safe mobile Comfort panel — Comfort platform, not Unified.
  • Screens in simultaneous use: 2 (the panel on the machine plus the tablet). A Sm@rtServer mirror shares one session, so that route puts 2 operators on 1 session whenever both act; the web client reaches the runtime from any device, so 2 screens are 2 separate accesses.

Result and decision #

Host: 1 Unified Comfort Panel, which executes the runtime and serves the web client on TCP/80. Client: the tablet's browser pointed at the panel's address, project built in V18-or-later Unified. Zero PCs and zero handheld safety functions give exactly this branch, and the thresholds are binary: one boxed PC in the cabinet moves the host onto it, and one handheld safety function moves the whole project to a fail-safe mobile Comfort panel.

Commissioning the branch you chose #

  1. Fix the addresses. Give the runtime host and the PLC static IPs on one subnet, and put the WiFi access point on a path that reaches the host; the tablet bookmark depends on a stable address, so keep the host off DHCP leases.
  2. Match project and host. Unified project for the PC, the Panel IPC, the Unified Comfort Panel or the MD-34; classic Comfort project for Comfort hardware. Nothing transfers between the two worlds.
  3. On a Unified host, enable the web server in the device settings and set user accounts and rights before the first browser connects; any client that can write tags gets authentication, because the browser exposes the same actions as the local screen. Secure connections to a Unified PC runtime require certificates, and the host PC's operating system and software configuration must meet the documented installation requirements for the runtime.
  4. On a Comfort Panel, enable Sm@rtServer in the panel settings and set its password before the first VNC connection.
  5. Load the client: the browser at the host IP for Unified, a VNC or Sm@rtClient app for the Comfort mirror, saved where the operator can find it.

Questions asked

Do remote browsers need their own runtime license?

No. The runtime license belongs to the device that executes the runtime: the PC, the Panel IPC or the panel hosting the project. A browser viewing the built-in web server and a VNC app mirroring a Comfort Panel execute no runtime, so runtime licensing never reaches them. The trap runs the other way: a PC runtime executing a Comfort project needs the runtime license, while the mobile panel running that project class does not.

Which browsers can open the Unified web client?

On Microsoft Windows, the documented supported browsers are Google Chrome and Microsoft Edge. The client needs only the browser, network reachability to the host, and the certificates a secured connection to a Unified PC runtime requires. Before a shop-standard tablet becomes the operator device, confirm its browser and operating system are on the support list for the runtime version you install.

How should screens be laid out for a tablet that mirrors a panel?

Design at the panel's native resolution, because the mirror only scales or letterboxes what the panel renders: a project built small stays readable on the tablet, a project built large shrinks. Treat the mirror as one session, since the local panel and the tablet are the same operator and input from both lands on the same screen. Lag tracks the WiFi link and the VNC encoding, not the panel's runtime.

Can the MD-34 tablet replace a fail-safe mobile panel?

Not for the safety duty. The MD-34 hosts the Unified runtime and settles the host question, but a handheld that carries an emergency stop or enabling function is a safety device wired into the machine safety chain, and a tablet supplies nothing of that. Where the risk assessment demands a travelling stop, the design uses a fail-safe mobile Comfort panel on the Comfort platform and keeps Unified off the handheld.

Keep reading

  • Selection guide

    Planning an HMI Terminal Replacement From an Older Operator Panel

    Decide an operator-terminal replacement on installed cost — the terminal, cutout adaptation, application software, engineering, commissioning, downtime and a spare — never on terminal price alone. Measure the opening against the replacement's documented cutout range and count displays before ordering: a slightly smaller terminal needs a bezel adapter, and a large converted application can force the higher-performance model. Convert in the same brand when the source project opens cleanly; rebuild cross-brand when you accept the extra engineering hours for source control.

    HMI and touchscreens

  • How-to

    Connecting an HMI Panel to an S7-1500 PLC

    Confirm the HMI's documented driver covers the S7-1500 for your exact panel model and software revision, put the panel and CPU on the same subnet, permit the connection in the CPU protection settings, then validate one known PLC tag before building screens. A working Ethernet link alone proves nothing about tag access.

    HMI and touchscreens

  • How-to

    Testing HMI Simulation Against a Live PLC

    A standalone HMI simulator proves screens and navigation, not communications. Test against a live controller only through a documented online-simulation mode or a physical panel, and verify every read at two data states and every write at the controller before release.

    HMI and touchscreens