How-to
Running a WinCC 7.0 project on another PC without a new build
Short answer
No. WinCC has no compile-to-EXE option: the destination PC needs WinCC Runtime of version 7.0 or higher, installed and licensed, and you transfer the project files to it. A newer WinCC opens and converts the project; an older release will not open it.
On this page
No, there is no compile step. WinCC does not turn a runtime project into a standalone EXE the way Visual Basic or C++ does, so the second PC needs its own WinCC installation and a runtime license, and it runs the transferred project files on top of them. The version rule is just as plain: a project built in WinCC 7.0 runs on 7.0 and every later release, and it will not open in an earlier one. Opening it in a newer version converts the project to that version, so convert a copy and keep the 7.0 archive untouched. And yes, a project that reads and writes PLC data on supervisory screens is doing SCADA work; the label changes nothing about what the destination PC needs.
Why there is no EXE and what the runtime supplies #
A WinCC project is configuration, not a program image. Screens, tag configurations, scripts, alarms and archive settings are stored as project data, and the runtime installation is the part that executes them. Communication with the PLC, screen rendering, the script engine and the alarm and archive services all live in the installed WinCC, not in the project folder. Copying the project therefore moves the data and none of the machinery, which is why there is nothing to link into an executable. Classic WinCC simply has no build target that produces one for a runtime project.
The destination runtime plays back exactly the files that were transferred to it, which is the same behavior behind why an HMI edit needs a new runtime download: change the project on the engineering side, transfer again. If the split between project, runtime and SCADA functions is still fuzzy, what WinCC does in an HMI and SCADA system walks through the pieces.
This is not a WinCC quirk. Engineering runtimes are deployed this way across vendors; VeriStand deployment requires its licensed system installed rather than a self-contained executable, for the same reason.
What the destination PC must have #
- Classic WinCC with runtime functionality, at version 7.0 or higher. WinCC Unified and the TIA Portal runtimes are different products; neither runs a classic 7.0 project.
- A runtime license sized for the project. The classic runtime license counts PowerTags, the process variables read from and written to the controller, so the license has to cover that count.
- An operating system the chosen release supports. Each WinCC release documents its own supported Windows list, and that list can decide the version you install as firmly as the project does.
- Engineering capability only on stations that will edit the project. A pure operator station needs none of it.
When the runtime station is a touchscreen computer at the machine instead of a desk PC, industrial panel PCs are the category to specify.
Which WinCC versions open the project #
The pattern is consistent across releases: a newer WinCC opens a project saved by an older one, and an older WinCC does not open a project saved by a newer one. The whole version question reduces to one comparison, the destination's version against the version the project was last saved with.
| Destination installation | What happens | What you do |
|---|---|---|
| WinCC 7.0, same or newer service pack | Project runs as built | Baseline move; match installed options and update level |
| WinCC newer than 7.0 | Project opens, then converts to that version | Convert a copy, retest everything, keep the 7.0 archive |
| WinCC older than 7.0 | Project does not open | Upgrade the destination, or leave the project on 7.0 |
The conversion is one-way. Once a newer version has opened and converted the project, it no longer opens in 7.0, which is why the untouched archive matters. Service packs follow the same logic: keep the destination at a service-pack level equal to or newer than the one the project was last saved under. The same match between built version and installed runtime governs the other product lines, and it is why you can run a TIA Portal V14 HMI on WinCC Runtime Advanced only with the corresponding runtime in place.
How to move the project #
- Record the source baseline first: WinCC version and service pack, installed options, license type, PLC connection settings, and any diagnostics the project currently shows.
- Close the runtime on the source PC, open WinCC Explorer, and run File → Archive Project to produce a complete archive of the project.
- Move the archive to the destination PC. USB, a network copy or FTP all work; the medium only has to hold the archive.
- On the destination, install classic WinCC at 7.0 or higher with runtime functionality, its options, and the runtime license, and confirm the operating system is on that release's supported list.
- Retrieve the project from the archive on the destination, using the retrieve side of the same archive function.
- Fix the machine-specific settings: the computer name the project expects, the network adapter selection, the PLC connection address, file paths and user accounts. A copied configuration still points at the old station until you change it.
- Start the runtime and clear format, component and licensing diagnostics before you touch communication.
- Test the read path, then the write path. Issue write-path commands only against a function approved for testing, or with the machine in a safe state.
Worked example: sizing and timing the transfer #
Illustrative numbers, not measurements from your project. Suppose the project folder on the source PC is 1.8 GB and the archive comes out at 0.7 GB. A 1 GB USB stick holds it: 1.0 GB − 0.7 GB = 0.3 GB to spare. Transfer time at an effective 25 MB/s over USB 2.0 is 700 MB ÷ 25 MB/s = 28 s; over a 100 Mbit/s office LAN delivering an effective 40 Mbit/s it is 0.7 GB × 8 = 5.6 Gbit = 5600 Mbit, then 5600 Mbit ÷ 40 Mbit/s = 140 s.
Decision: either medium works, so choose by convenience. What moves the numbers is archive size, and time scales linearly with it, so a 7 GB archive takes ten times the 140 s, about 1400 s or 23 min, over that same LAN. After retrieval, compare the restored project size against the source: 1.8 GB matching 1.8 GB passes, and any shortfall means the transfer is incomplete.
What to check at the destination #
- Startup diagnostics show nothing unresolved about missing components, project conversion or licensing.
- Read path: pick one tag, compare it with the online value in the controller, make a controlled change there, and watch the runtime value follow. Check tag quality, not just the number, because a stale or substituted value can still look alive on screen.
- Write path: an authorized test command arrives in the PLC and the program responds per its conditions.
- Configured functions behave as on the source: navigation, scripts, alarms, trends and archives.
Symptoms that point at the real fault #
| Symptom on the destination PC | Where to look | Healthy result |
|---|---|---|
| Project will not open | Installed product, version and product line; completeness of the transfer | The installation recognizes the project and its files |
| Opens, but reports missing functions or licensing | Runtime license and installed options | Required functions installed and licensed |
| Screens open, values do not update | Connection settings, network path, tag quality | Good quality; values track the PLC |
| Values update, commands fail | Operator permissions, writable tags, PLC-side conditions | An authorized command reaches the PLC |
Write down the exact diagnostic message before changing anything. A project-format error and an unreachable PLC take different fixes, and the message tells you which one you have.
Questions asked
Does the destination PC also need the engineering software?
No. A runtime installation with its license is enough to run the project. Install the engineering environment only on stations that will edit the project, and one engineering PC can serve several runtime stations, each with its own runtime license.
Can the source and destination PCs run the project at the same time?
Yes, when each station has its own runtime license and you set the second station's computer name, adapter selection and connection addresses so both reach the PLC independently. Coordinate any commands the two stations write to the same tags, or the last write wins.
After opening the project in a newer WinCC, can I move it back to 7.0?
No. The conversion that runs when a newer version opens the project is one-way. Keep the untouched 7.0 archive from the transfer and restore that copy if the project ever has to run on a 7.0 machine again.
Do internal tags count toward the runtime license?
No. The classic WinCC runtime license is sized by PowerTags, the process variables connected to the controller. Internal tags, screen objects and scripts do not add to that count, so count the PowerTags in the project and choose the license that covers them with room for growth.
Is my runtime project an HMI or a SCADA system?
The functions you describe, reading and writing controller data and displaying and logging it, are SCADA functions. One operator station serving one machine is what most sites simply call an HMI. Use whichever label your site prefers; the software and license the destination PC needs are the same.