How-to
Run a TIA Portal V14 HMI on WinCC Runtime Advanced
Short answer
Compile the HMI for its configured WinCC RT Advanced target, transfer the compiled application, and select it in RT Loader. Match the configured device version to the runtime installed on the workstation. Verify Windows support and use a valid runtime license sized for the application.
On this page
Compile the HMI application configured in the TIA Portal V14 PC station, transfer it to the operator workstation, and start the compiled file in RT Loader. Before loading, check that the WinCC RT Advanced device version configured in the station matches the WinCC RT Advanced version installed on the workstation. Confirm that Siemens supports the workstation's Windows version for that release and that the runtime license covers the application.
What RT Loader opens #
Edit the engineering project and compile it in TIA Portal. On the workstation, open RT Loader, choose Settings, and select the compiled application.
The PLC program has its own download. If the HMI opens and its values stay blank or stale, verify that the CPU is running the expected PLC program and that the HMI can communicate with it.
Saving the project updates the engineering data only. The station keeps running the last build until you compile and load again, which is the rule behind why an HMI edit needs a new runtime download. Note where each build lands, so an earlier successful build is not mistaken for the current one.
Match the runtime edition, version, OS and license first #
A workstation inventory line that says WinCC Runtime is not a compatibility statement. WinCC RT Advanced is the PC runtime that TIA Portal targets here; classic WinCC and WinCC Unified are different products with different project types, and none of their runtimes starts an RT Advanced build.
Use the Runtime version selected in the PC station's hardware catalog and properties as the comparison point. Siemens' SINUMERIK Integrate Create MyHMI /WinCC V14 SP1 Configuration Manual, section 4.3, shows where to select it and says it must match the Runtime installed on the PC. Check the released Windows edition and build for the exact Runtime release in Siemens' compatibility documentation.
Check the license separately. Siemens' TIA Portal V21 documentation, Licensing STEP 7 and WinCC, lists WinCC RT Advanced V17.x license keys as valid for RT Advanced V14.x. Use a valid key of sufficient capacity for the application and check any separately licensed options. Resolve licensing messages before investigating transfer or communications.
If the workstation itself is being chosen rather than reused, industrial panel PCs and touchscreen computers are the class of machine that hosts this runtime at the machine.
Compile in TIA Portal, then load #
The PC station in the project holds the two objects that matter here: the WinCC RT Advanced application and the network interface it communicates through. The HMI connection under the station points at the PLC. Compile the HMI station and clear every error — copying files cannot repair a build that never succeeded. Loading then transfers the compiled application to the workstation, and on completion of the download you start the project in runtime. Run the application in simulation first; the method is in testing HMI simulation against a live PLC.
Deployment step by step #
- Record the installed WinCC RT Advanced version on the workstation. Confirm Windows support for that release and verify the runtime key and capacity in Automation License Manager.
- In TIA Portal, confirm that the HMI application in the PC station is WinCC RT Advanced and that its configured device version matches the installed runtime.
- Check the configured HMI connection partner and the workstation network settings. For a direct local subnet, put the adapter on the same subnet as the CPU.
- Compile the HMI station and resolve all errors.
- Load the station to the workstation over the network and confirm the transfer completes.
- On the workstation, start WinCC Runtime Loader, click Settings, and select the compiled application.
- Start runtime and confirm the first screen opens.
- Verify one live tag end to end, then check the archive and trend configuration.
Worked deployment example #
Use these illustrative addresses for a direct connection. The TIA Portal PC station is configured for WinCC RT Advanced V14. The workstation has that runtime version, a Windows release supported for it, and a runtime license of sufficient capacity. The CPU uses 192.168.0.1/24 and the workstation adapter uses 192.168.0.10/24. Both addresses are on 192.168.0.0/24. A successful ping, where ICMP is permitted, checks IP reachability.
Set the HMI connection partner to 192.168.0.1. Compile and transfer the application, then select the resulting build in RT Loader. Confirm that the expected screen opens. Compare the screen value of one known read-only PLC tag with the value in the engineering tool, then check trend logging separately.
Perform commissioning on a test bench or with the machine in its approved safe state. Use the agreed machine procedure for any test that changes a PLC value.
When runtime starts but something is missing #
| What you see | What it tells you | What to do next |
|---|---|---|
| The loader cannot find or select the application | Wrong path or an incomplete transfer | Recheck the load result and the folder the loader points at |
| Runtime reports a device-version mismatch | The configured target and installed runtime may differ | Compare both versions, select a supported target or install the corresponding runtime, then compile again |
| Screens open but show an older layout | The loader points at a previous build | Recompile, reload, and reselect the new build |
| Screens open, PLC values invalid or stale | Startup succeeded; communication failed | Check the connection partner, adapter address and route |
| Values live, trend history empty | The live tag path works | Check logged tags, archive path and write access |
The archive behind the trends #
The item the workstation shows as Logging is the runtime archiving function: it records tag histories that trends read back. After startup, check the logged tags and their acquisition cycles, the archive destination, and write access to that destination under the account running the runtime. Then confirm each historical trend data source points at that archive — an archive that never receives data and a trend pointed at the wrong source both give an empty line.
The decision for each case #
- The installed runtime, configured target, Windows release and license are compatible. Compile, transfer and start the build in RT Loader.
- The installed runtime differs from the configured target. Install the corresponding Runtime or change the configured device version where Siemens supports it, then recompile and load. Migrate the engineering project through Siemens' documented path when needed.
- The workstation has classic WinCC or Unified. Use a workstation with RT Advanced or follow the engineering procedure for the other target.
- Screens open, no live values: leave the loader alone and fix the connection — partner address, adapter, route.
- Values live, history empty: fix the archive — logged tags, destination, permissions.
Questions asked
The workstation already runs classic WinCC V7 with an Activate command in the File menu. Will the V14 build run there?
Classic WinCC V7 runs its own project type. Use a workstation with WinCC RT Advanced installed at the version configured for your PC station and a license that covers that runtime and the application.
How do I make the HMI application start automatically when the workstation boots?
Follow the WinCC RT Advanced autostart instructions for your installed release. Test a planned restart under the intended Windows account and verify that the loader starts the current compiled application.
Live values work, so why are the historical trends empty?
Because they read different data. A live trend shows samples collected while the screen is running; a historical trend reads the archive the logging function writes. With good live data and blank history, either the logged tags, the acquisition cycle or the archive destination is misconfigured, or the trend data source points somewhere else.
Runtime refuses the build and reports a version problem. What is the fix?
Compare the WinCC RT Advanced device version configured in the PC station with the runtime installed on the workstation. Install the corresponding runtime or select a device version the engineering system supports, then compile and load again. Check Siemens' documented migration path if the project needs an upgrade.
Corrections
- : Clarified the configured WinCC RT Advanced version, supported Windows release and runtime license checks.