This HMI example displays PLC values and sends operator commands through tags. Each lamp, gauge and button shown on the WinCC screen is bound to a controller tag. A PLC value updates the display; tapping a control writes a tag back. Change the tags on the right and follow each update on the panel at the left to see how those bindings work.
The left is a WinCC faceplate for one motor. The PLC's tag table is on the right. Each display element in this example watches a tag. Toggle "Motor".running, change the speed, raise the temperature past 80°C and trip the fault. These actions let you follow the displayed status, gauge values and alarm response for the same motor.
Tap START on the panel. It writes "Motor".running := TRUE back to the PLC, and the toggle on the right flips. Binding runs both ways: the screen reads tags to display, and writes tags when you touch a control.
The motor display is a faceplate: a reusable screen object with its own interface, like an FB for graphics. Build it once, then drop it on 30 motors and just point each copy at a different "Motor" instance. The UDTs from the previous track give those instances the same data structure.
🖥️ WinCC Unified is the modern, web-based runtime for Unified Comfort Panels & PC. Its HTML5 screens can scale across those targets, and it is the current direction for WinCC.
🖲️ WinCC Comfort/Advanced covers the long-established Comfort Panels and RT Advanced. These are widely deployed on existing production lines.
An operator says "when temp exceeds 80 °C the motor must stop." Where should that process interlock be programmed? If the stop is a safety function, a safety relay or safety PLC must handle it; an HMI or ordinary PLC interlock is not a substitute.