Explainer
Start a published WebIQ HMI project without Runtime Manager
Short answer
No current WebIQ version starts a project automatically after publishing: start and stop live in Runtime Manager, and Designer only shows the running state. During development, point panel devices at the Designer preview server on port 10124 instead; publish and start only for tests that need the ctrlX reverse proxy.
On this page
- Can WebIQ start the project automatically after publishing?
- Where do I start the published project instead?
- Does starting the project need a Runtime license?
- How do I test on the panel without publishing every time?
- Does the Designer preview behave like the deployed runtime?
- Why does the HTTP preview fail inside an HTTPS page?
- When must the project run on ctrlX instead of in preview?
- Questions asked
No, and the missing button is deliberate: current WebIQ versions cannot start a project automatically after publishing, and Designer no longer starts or stops runtimes at all — Runtime Manager on the ctrlX Core web server is the only place that happens. The efficient workflow splits in two: point the machine's panel devices at the Designer preview server, http://{IP_OF_WEBIQ_DESIGNER_PC}:10124, while you iterate, and reserve publish-plus-Start for deployment tests, because the preview cannot reproduce the ctrlX reverse proxy that iframes and REST calls depend on.
Can WebIQ start the project automatically after publishing? #
No. Current WebIQ versions have no auto-start after publish and no start command in Designer; runtime start and stop live only in Runtime Manager, which on ctrlX Core means logging into the device's web server and starting the project by hand.
Earlier WebIQ versions had a one-click start inside Designer. That control was removed when the runtime side of the product was consolidated in Runtime Manager, on the reasoning that a project under development is verified in the preview — which behaves like the started runtime — so starting the server-side runtime from the engineering tool was an edge case. Designer kept the running-state display: you can still see whether a project runs there, but you can neither start it nor stop it from Designer.
Nothing in the publish path starts anything. Publishing and starting are separate operations, so a fresh publish sits in a published-but-not-running state until someone starts it. Decision: stop hunting for the setting; publish-then-Start is the designed sequence, not a fault.
Where do I start the published project instead? #
In WebIQ Runtime Manager: open the HMI Projects tab, tap the ... button next to the project, and select Start; a play icon appears next to the project once it runs.
On ctrlX Core, Runtime Manager is reached through the device's web server and that access needs a login — the exact friction behind the auto-start request. Keep the cost down by logging in once at the start of the working day and leaving the Runtime Manager page open in a browser tab, so Start stays one click away for every publish that day. Read state before acting, too: the play icon next to the project, not the fact that you published, is what says the HMI is being served.
Decision: one login per day, tab kept open, Start after each publish that must run on the target.
Does starting the project need a Runtime license? #
Yes — starting the published application requires a Runtime license on the target that runs it, and a setup without a direct connection to ctrlX usually has none, so publish-and-start belongs to deployment rather than to every design iteration.
A Designer session proves nothing about the deployment target's entitlement, because editing and previewing on the engineering PC is a different operating context from executing the published application on ctrlX. Before treating a Start that goes nowhere as a fault, open the Installed Licenses page in Runtime Manager and read the license list there. This is also why an automatic start after publish would not have solved the workflow on every site: on targets without a Runtime license it would simply fail. Licensing the Designer side of the work is its own subject — see activating a WebIQ Designer trial license for project conversion when that is the question.
Decision: treat Start as a deployment action gated by the target's license list; develop in the preview, which needs no Runtime license on ctrlX.
How do I test on the panel without publishing every time? #
Point the panel browser at the Designer preview server, http://{IP_OF_WEBIQ_DESIGNER_PC}:10124, instead of the deployed address http://{CTRLX_IP}:10123/{PROJECTNAME}, and the panel shows the current project without a publish-and-start cycle.
| Destination | Address pattern | What the panel gets |
|---|---|---|
| Designer preview | http://{IP_OF_WEBIQ_DESIGNER_PC}:10124 | The live project from the Designer PC; no publish, no Start, HTTP only |
| Published project | http://{CTRLX_IP}:10123/{PROJECTNAME} | The deployed runtime on ctrlX; needs publish plus Start in Runtime Manager |
Both entries are templates: substitute the Designer PC's address, the ctrlX device's address, and the project name. Verify reachability from the panel itself rather than only from the engineering PC, because the panel's subnet and firewall decide whether the address opens, and the preview additionally depends on the Designer PC staying on with its preview server available. For the round trip you are skipping, read why an HMI edit needs a new runtime download — the rebuild and transfer it describes is exactly what the preview avoids while the design is still moving.
Decision: leave the preview address on the panel throughout development and switch to the deployed address for integration and release checks.
Does the Designer preview behave like the deployed runtime? #
For screen layout, navigation and ordinary HMI interaction, yes — the running project behaves exactly the same in the Designer preview as on the started runtime, which is the stated reason the start command could be removed from Designer at all.
That parity makes the preview the efficient branch: layout, navigation and interaction faults reproduce there, so a question like why a WebIQ button stays highlighted after touch release is answerable without spending a publish cycle on it. The limit is equally plain. The preview is faithful to the project, not to the place the project is served from, so anything that depends on the serving context — embedded ctrlX content, REST through the reverse proxy, an HTTPS host page — does not test honestly there.
Decision: verify screens and interactions in preview; when something passes in preview and fails deployed, suspect the serving context before the screen.
Why does the HTTP preview fail inside an HTTPS page? #
Because browsers block HTTP content inside an HTTPS page, and the Designer preview server is HTTP-only, so an HTTPS parent page cannot embed the preview or fetch active content from it — a browser security boundary, not a WebIQ fault.
The rule is the W3C Mixed Content specification: framable and scriptable content counts as blockable, and a secure page is refused plain-HTTP loads of it. Keep a second check separate from that one: the same-origin policy compares origins, and an origin is the scheme, host and port taken together — change any one of the three and the origin differs, even when both addresses are reachable.
Worked example with illustrative addresses from the RFC 5737 documentation range. A ctrlX page at https://192.0.2.10 has scheme https, host 192.0.2.10, port 443. It embeds the preview at http://192.0.2.50:10124, which has scheme http, host 192.0.2.50, port 10124. Comparing the three parts: scheme https is not http, host 192.0.2.10 is not 192.0.2.50, port 443 is not 10124 — three mismatches out of three. The frame is mixed content, so the browser refuses it before cross-origin rules are even reached. Opened directly as a top-level page, the same http://192.0.2.50:10124 has no HTTPS parent and loads normally, which is why a preview that works alone in a tab proves nothing about embedding it.
Decision: never embed port 10124 inside an HTTPS host page; test embedded layouts against the deployed project.
When must the project run on ctrlX instead of in preview? #
Whenever the HMI shows content from another ctrlX application in an iframe or talks to a REST API through the ctrlX reverse proxy, it must run on ctrlX at http://{CTRLX_IP}:10123/{PROJECTNAME}, because the preview cannot reproduce that proxy path.
ctrlX combines content from several web servers into one page through its reverse proxy, and the HMI can use that proxy only when it is itself served from the ctrlX web server. The preview runs on the Designer PC — a different server and a different origin — so iframe content and REST destinations that resolve through the reverse proxy behave differently there or do not resolve at all. For those projects, publish-plus-Start is a legitimate repeated step rather than an inefficiency to engineer away: publish, start once from the Runtime Manager tab you keep open, and test the integration pages at the deployed address.
Decision: integration pages are tested only on the started runtime on ctrlX; everything else is faster in preview.
Questions asked
Does closing WebIQ Designer stop the running project?
No. A published project that has been started runs as the WebIQ runtime on ctrlX, not inside the Designer application on your PC, so closing Designer leaves it running. Stopping it is a Runtime Manager action; Designer's display only reports the state.
Can the panel reach the preview from any network?
Only if it can reach the Designer PC itself. The preview is served straight from that computer on port 10124, so a firewall on the Designer PC, a subnet the panel cannot route to, or a shut-down engineering PC breaks it. The deployed project on ctrlX is unaffected because it is served there.
Is a preview that opens on its own proof the deployed page will embed?
No. Opening the preview directly as a plain HTTP page tells you the project renders; it does not reproduce an HTTPS parent page embedding that preview or calling it by script. Transport and origin only match inside the real deployment context, so test embedding where the page will actually run.
Do I have to publish before the panel can use the preview?
No. The preview is served from the Designer PC, not from ctrlX, so the panel sees the project you have open without any publish. Publishing moves the application to the deployment target, which matters only when the test needs the runtime, the reverse proxy, or the Runtime license there.