TIA Portal WinCC Runtime Advanced: HMI Tag Configuration, PLC Communication & Connection Setup: Complete Contents
- 1. Understand the Runtime Advanced Communication Model
- 2. Add the HMI Station and PLC to the Same TIA Project
- 3. Configure the PLC Connection
- 4. Design HMI Tags: Process Tags vs Internal Tags
- 5. Prefer Stable Symbolic Interfaces
- 6. Configure Acquisition and Update Behavior
- 7. Practical Tag Mapping Example
- 8. Commission the Connection Systematically
- 9. Common Communication Problems
- 10. Hands-On Communication Lab
Practical WinCC Runtime Advanced Engineering Guide
1. Understand the Runtime Advanced Communication Model
WinCC Runtime Advanced is a PC-based HMI runtime engineered inside TIA Portal. The cleanest architecture is to treat the HMI interface as an intentional contract between PLC and visualization. The PLC owns machine state, interlocks, permissives and process values; the HMI reads status and writes only operator commands or setpoints that the PLC is prepared to validate. This separation makes troubleshooting far easier than allowing graphics to write directly into scattered control logic.
2. Add the HMI Station and PLC to the Same TIA Project
Create or open the PLC project, add the Runtime Advanced device/station, and place both devices on the intended Industrial Ethernet/PROFINET network. Assign engineering IP addresses that match the plant addressing plan. The project view should make the controller, HMI runtime and network relationship obvious before tag creation begins. If the PLC and Runtime Advanced are engineered in separate projects, document the controller address and symbol strategy carefully.
3. Configure the PLC Connection
Open the HMI Connections editor and create the SIMATIC S7 connection to the intended CPU. Verify the controller selection, network interface and addressing. For commissioning, confirm that the PC network adapter used by Runtime is on the same reachable network and that Windows/network security settings do not block the intended communication. Do not diagnose tags until the basic device-to-device path is proven.
4. Design HMI Tags: Process Tags vs Internal Tags
Use process/external HMI tags when the value belongs to the PLC, such as Motor01_Running, Furnace_TempPV, LineSpeedSP or Alarm_HighTemp. Use internal HMI tags for visualization-only states such as popup selection, temporary navigation values or display filters. Keep tag ownership clear. A useful naming pattern is Area_Equipment_Signal, which scales much better than generic names such as Tag1 or MotorBit.
5. Prefer Stable Symbolic Interfaces
Where supported by the project architecture, use PLC symbols and structured DB interfaces instead of scattering absolute addresses throughout the HMI. A dedicated HMI interface DB can group command, status, setpoint and diagnostic structures. This improves readability and reduces rework during PLC program changes. If absolute addressing is required on a legacy project, maintain a controlled tag list and verify every address after PLC modifications.
6. Configure Acquisition and Update Behavior
Fast update cycles should be reserved for values that genuinely need fast visualization. Status lamps, temperatures, pressures and production counters often tolerate different acquisition rates. Excessively fast cyclic reads increase communication load without improving operator decisions. Group high-priority animation values separately from historical or slow-changing values.
7. Practical Tag Mapping Example
Use a small, deterministic HMI interface before scaling the project.
PLC Interface DB example
DB_HMI.Motor01.StartCmd : Bool
DB_HMI.Motor01.StopCmd : Bool
DB_HMI.Motor01.Running : Bool
DB_HMI.Motor01.Fault : Bool
DB_HMI.Process.TempPV : Real
DB_HMI.Process.TempSP : Real
DB_HMI.Diagnostics.CommAlive : Bool8. Commission the Connection Systematically
Start with ping/network reachability where appropriate, then verify controller online status, Runtime connection state, one known Boolean tag, one analog value and finally command/write paths. A good commissioning sequence is: network → controller → HMI connection → tag quality → read values → write test → graphic behavior. This prevents graphics troubleshooting from hiding a lower-level communication fault.
9. Common Communication Problems
| Symptom | Likely cause | Check |
|---|---|---|
| All HMI values invalid | Connection/network issue | IP, adapter, CPU reachability, connection target |
| Only one tag wrong | Tag mapping/type mismatch | PLC symbol, datatype, DB path |
| Writes do not act | PLC validation/interlock | Command bit, mode, permissives, write permission |
| Runtime works in engineering but not plant PC | PC network/runtime configuration | NIC, firewall, Runtime settings, project transfer |
10. Hands-On Communication Lab
Build a four-object HMI screen containing motor Start/Stop, Running/Fault indication, a temperature PV/SP pair and a communication heartbeat. Force or simulate PLC states, verify tag quality and test controlled writes. The exercise is complete only when the engineer can deliberately create a wrong tag/connection condition and identify the fault from the Runtime/PLC side.
WinCC Runtime Advanced Hands-On Lab
Use a non-production PLC/HMI project, document the test conditions, and verify every HMI behavior against the PLC watch table or diagnostics. The objective is not only to make the screen work, but to prove that the engineer can diagnose a deliberate fault and recover the system methodically.
Frequently Asked Questions
What is WinCC Runtime Advanced?
It is a PC-based SIMATIC HMI runtime engineered with WinCC in TIA Portal for machine-level visualization and operator control.
Should WinCC Runtime Advanced use PLC tags or internal HMI tags?
Use PLC/process tags for controller-owned data and internal HMI tags for visualization-only values such as navigation, temporary selections or display states.
Why does an HMI tag show invalid quality?
Typical causes include a broken PLC connection, wrong controller target, incorrect symbol/address, datatype mismatch or a Runtime PC network configuration issue.
Can the HMI write directly to motor outputs?
A safer design writes operator commands to an HMI interface in the PLC, where mode, interlock, permissive and safety logic validate the command before the final output is driven.
Related WinCC Runtime Advanced & Siemens HMI Resources
Need Practical WinCC Runtime Advanced Training?
Build the complete HMI workflow from PLC communication and tags through alarms, trends, recipes and user administration with a practical Siemens automation project.
Discuss Training or Project Support