How-to
Running a WinCC Flexible 2008 Project in PC Runtime
Short answer
Yes — WinCC flexible 2008 Advanced targets a PC station. Compile the project to a .fwx file and run it with the separately installed, tag-licensed WinCC flexible Runtime through its loader; the compile never produces an .exe.
On this page
Yes, and you do not need a different SCADA package to do it. A WinCC flexible 2008 SP3 project runs on the operator PC as a PC station: set the project's device to the PC runtime target in the engineering tool, compile it, and run the resulting .fwx file under the separately installed WinCC flexible Runtime, started through its loader. The compile never produces an .exe — the .fwx is a compiled runtime file, the installed Runtime is the program, and the license is sized on the tags the project uses.
What the compile actually produces #
The compile step writes a file with the .fwx extension into the project folder. It is a compiled binary holding the screens, tags, alarms, scripts and runtime configuration, and it executes in exactly two places: on a Siemens panel or under an installed WinCC flexible Runtime. It cannot be opened in the engineering tool for modification, so it is deployable output, not source.
The editable source is the project itself — the *.hmi file with its *.log in the project folder. Keep source and compiled output in separate, labeled archives: a .fwx handed over without its project is a runnable application whose screens you can no longer change. A .psb is a third thing entirely, a panel backup rather than a PC runtime project, which is why a PSB backup cannot run in WinCC flexible PC runtime.
Set the project to the PC runtime target #
The engineering installation must be the edition that can configure a PC station: WinCC flexible 2008 Advanced. Read the full product name and service pack in the installed software's product information before trusting what the station is called on the floor — the name shown there decides, and a wrong edition cannot be worked around later in the project.
- Confirm the edition and service pack — Advanced at SP3 in this case — in the product information of the installed engineering software.
- Set the project's device to the PC runtime target in the device selection, in place of the panel model.
- Open every screen after the retarget and check the functions the panel target allowed; panel-specific functions surface as compile errors at this point, which is when you want to find them.
- Point the PLC connection at the controller address and interface the operator PC will actually use.
- Save the project with the PC target in place.
Install the runtime and its license on the operator PC #
The runtime is a separate component, selected during the WinCC flexible setup; an engineering installation elsewhere on the network proves nothing about the operator PC. Install the runtime generation that matches the compiler: a .fwx compiled by 2008 does not run under the 2007 runtime, so the operator PC gets the WinCC flexible 2008 runtime, matching the service pack where you can.
The documented rule comes from the WinCC flexible 2008 Runtime manual: unrestricted use on a standard PC or a panel PC requires a license, and the license step is sized on the tags the project uses. Without one the software still starts and periodically raises a license notice — that is not a state to run production in, and the fix is the correctly sized license obtained through Siemens' official channels, not something to click through shift after shift.
If the station at the machine is new hardware rather than a reused office PC, industrial panel PCs are the touchscreen computers this runtime deploys onto.
Sizing the license for a 212-tag line HMI #
Inputs, illustrative but typical: the tag lists of a mixing-line project edited in WinCC flexible 2008 SP3 show 148 tags on the connection to the first PLC and 64 tags on the connection to the second PLC; the busiest single screen binds 24 of them. The connection counts come from the project's own tag overview, the screen count from that screen's objects.
Rule in words: the runtime license covers the tags the whole project uses, not the tags visible on one screen.
Arithmetic: 148 + 64 = 212 tags the runtime must be licensed for. Sizing on the busiest screen instead would under-license by 212 − 24 = 188 tags.
Decision: install the license step at or above 212 tags, with headroom for the tags your edits will add, because every added tag lands in the same count. Anything below 212 puts the license notice on a running production screen.
Compile, deploy and start the .fwx file #
- Compile the project and clear every reported error; the .fwx appears in the project folder on a successful compile.
- Check the .fwx modification time against this build before copying anything. A shortcut aimed at an old output folder is the classic way a corrected project appears unchanged on the floor.
- Copy the .fwx to the operator PC.
- Open the WinCC flexible Runtime loader, select that .fwx, and start it. The initial screen opening proves the file executes.
- Create a Windows shortcut to the .fwx on the desktop; double-clicking it starts the runtime with that application loaded.
The shortcut is a convenience, not a mechanism. If double-clicking does nothing, the .fwx file association is missing on that PC: start through the loader and repair the association instead of re-copying the file.
Every later change reaches the operator PC only as a newly compiled, newly copied .fwx — why an HMI edit needs a new runtime download.
Match the loader settings to the PLC connection #
The loader keeps its own PC connection settings, and they are not inherited from the engineering tool — a transfer that worked from the engineering seat proves nothing about the loader on the operator PC.
- On Ethernet, compare the controller address in the project connection with the interface selected in the loader and with the path the PC actually reaches the PLC through.
- On an adapter-based link, compare the configured interface with the installed adapter and its settings.
- Prove the path with one tag: read a known value on the HMI and against the controller itself, scaling accounted for, and watch it move.
A screen that opens proves file execution; a value that changes and matches proves data exchange. Diagnose them as two separate faults. On a PC cloned from another machine, check the interface selection first — runtime showing ### on a copied target PC is that fault, not a broken project.
Stay on 2008 or move #
With the Advanced edition compiling, the matching-generation runtime installed, and the license covering the tag count, the flexible project on a PC is a finished configuration — leave it in service and stop there. Move only when the toolchain starts costing you: when the Windows versions it installs on age out of your plant, or when a .fwx arrives with no source project behind it. That is the point to plan migrating the WinCC flexible project to TIA Portal rather than patching 2008 further. And if the scope grows from one operator PC toward a plant-wide PC SCADA, the split is its own comparison — see WinCC vs WinCC flexible for small PC SCADA applications.
Questions asked
Does compiling a WinCC flexible project produce an .exe file?
No. The compile writes a .fwx file into the project folder, and that file executes only under an installed WinCC flexible Runtime or on a Siemens panel. A desktop shortcut to the .fwx starts the runtime with your application loaded; it is not a standalone Windows program and runs nowhere without the runtime installed.
Can I edit screens inside the .fwx file?
No. The .fwx is compiled output and cannot be opened for modification in the engineering tool. Editing happens in the source project — the *.hmi file with its *.log — so archive the source next to every .fwx you deploy. If you were handed a .fwx with no project behind it, treat the screens as read-only until the source turns up.
Which WinCC flexible 2008 edition do I need for a PC runtime project?
Advanced is the edition that engineers a PC station target, and it is the installed edition on the engineering PC that limits the choice — not the panel model the project started on. If the project was created for a panel under a lesser edition, opening it under Advanced and switching the device with the retarget steps above adds the PC target; the wrong edition cannot be selected around later in the project.
Will the runtime keep running with no license?
It starts and runs, but periodically raises a license notice on screen. The runtime manual requires a license for unrestricted use on a standard PC or panel PC, and the license step is sized on the tags the project uses, so production operation means installing the license that covers your full tag count — 212 in the worked example above.