How-to
Launching Windows programs from a Vijeo Designer runtime
Short answer
No. A Vijeo Designer runtime screen cannot start a Windows program: the object action lists contain no run-program entry, and the only application-level control is the exit-runtime key. Configure third-party tools from the Windows desktop after exiting, or reach them through a remote session while the runtime keeps running.
On this page
- What the runtime controls and what Windows still gives you
- Confirm the limit in your own project
- Prove the tools coexist with the runtime
- Route 1: exit the runtime and work from the desktop
- Route 2: keep the runtime running and reach the tools remotely
- Worked example: budgeting HMI offline time for two tools on one iPC
- Boot behavior and window focus
- Verify the whole arrangement end to end
- Questions asked
No. A Vijeo Designer runtime screen cannot start a Windows program. The object action and function lists contain no run-program entry, and the only application-level control the runtime exposes is the key that quits it. The launch behavior you may have seen demonstrated on a Pro-face unit does not carry over: the panel hardware overlaps, but the HMI software layer is a different product. You work with the limit in one of two ways — exit the runtime and run the third-party tools from desktop shortcuts, or leave the runtime alone and reach the tools remotely while it keeps running. Both routes are below, with the checks that make each one dependable.
What the runtime controls and what Windows still gives you #
On an iPC the Vijeo runtime is an ordinary Windows application, and the iPC documentation for these targets keeps the Windows side reachable: key combinations such as Alt+Tab, which switches between open applications, and Alt+F4, which closes one, still work when a keyboard is attached. What the HMI project itself can do to Windows stops at the runtime-exit function. There is no shell call, no file-open action, no launcher object. That is why a Pro-face screen that starts external software proves nothing about a Vijeo Designer project: the metal is shared, the software is not.
Confirm the limit in your own project #
- Open the iPC's project in Vijeo Designer on the engineering PC.
- Open the screen that carries the button you intended to use as a launcher.
- Review the action, animation, and system-function lists offered on that object in your installed Designer version.
- Locate the runtime-exit function — it is the single application-control entry.
- Decide: no run-program entry exists, so use one of the two routes below. If your version does list a launch action, configure it there and skip the workarounds.
Prove the tools coexist with the runtime #
Coexistence is a resource question, not a licensing or launch question. Prove it once before you design access around it:
- Start the runtime with the production project and let it reach steady state.
- Start each third-party tool from the Windows desktop, with a keyboard attached if the touch-only flow blocks you.
- Open Task Manager and record CPU, memory, and disk load for the runtime process and for each tool's process.
- Cycle the heaviest trend and alarm screens while the tools stay open.
- Decide: if screen changes or tag updates slow noticeably, that tool does not belong on this iPC — run it from the engineering PC or a separate computer instead.
Route 1: exit the runtime and work from the desktop #
This route uses the one function the software gives you. It takes the HMI offline while you work, so it suits planned configuration windows.
| Piece | What to set | What it gives you |
|---|---|---|
| Exit key | The runtime-exit function on one screen, away from operating buttons, restricted by user level | A controlled return to the Windows desktop |
| Tool shortcuts | One Windows desktop shortcut per tool, each with its correct working directory | Every tool opens with its saved configuration |
| Runtime relaunch | A desktop shortcut that starts the runtime with the production project | The HMI returns to its first screen without a reboot |
- Place the exit key on a screen that operator-level users cannot reach.
- Create the tool shortcuts and the relaunch shortcut on the desktop.
- Download the updated project, and stop the runtime on the target first — the runtime must not be running during a download. If the iPC sits behind a router, the network path is covered in downloading a Vijeo Designer project to a remote HMI over VPN.
- Press the exit key and confirm in Task Manager that the runtime process is gone.
- Open each tool from its shortcut, make the configuration change, and close the tool.
- Start the runtime from its shortcut and confirm the first screen loads with live tag values.
Treat the exit as lost alarm visibility and lost operator input for the whole window: the controller keeps running the machine, so agree that window with operations before you use this route in production.
Route 2: keep the runtime running and reach the tools remotely #
When the HMI must stay up, configure the tools from outside the runtime session:
- Use the tool's own network interface — a web page or a remote configuration client — from the engineering PC, and confirm you can read and write its settings while the HMI screens keep updating.
- If the tool is desktop-only, use a remote-control product that attaches to the existing console session rather than creating a new one, and confirm the local HMI display does not change when you connect.
- Test plain Windows Remote Desktop separately before relying on it: a login for the same account can pull the interactive session off the local console and leave the panel on a lock screen, which disrupts a runtime that depends on that session. Remote sessions onto operator panels carry the same constraint, as making remote HMI access read-only over RDP covers.
- Verify with the remote session open, then closed: the local screen still shows the runtime and touch input still works.
Worked example: budgeting HMI offline time for two tools on one iPC #
The case is the one asked about: one iPC running the production Vijeo project, with two third-party configuration tools to maintain on the same panel. The timing inputs below are illustrative values of the kind you measure once on your own panel — replace them with your measurements and the arithmetic holds.
Inputs:
- Exit key pressed to Windows desktop: 5 s
- Configuration edits across both tools: 120 s
- Runtime relaunch to the first live screen: 20 s
Rule in words: the HMI blackout is everything between pressing the exit key and the runtime showing its first screen again — exit time plus edit time plus relaunch time.
Arithmetic: 5 s + 120 s + 20 s = 145 s.
Result: 145 s with no operator screen and no alarm visibility.
Decision: if the process rides through a blind window of about two and a half minutes — most manual and batch interventions do — schedule Route 1 and stop there. Any function the operator must watch closer than your measured blackout forces Route 2.
Boot behavior and window focus #
Adding tools changes what the panel does after a power cycle:
- Review the startup items and scheduled tasks; only the intended applications should start.
- Power-cycle the iPC and confirm the runtime reaches its first screen with no operator action.
- Any tool that starts at boot must not cover the runtime window or hold focus — a tool that opens a dialog at start blocks touch access to the HMI.
- If the panel ends up booting to the wrong application, the Runtime Installer included with Vijeo Designer reverts it to its initial start mode.
- Confirm the exit key still reaches the desktop and the relaunch shortcut still works after the reboot.
Verify the whole arrangement end to end #
- Cold-start the iPC and confirm the runtime loads the production project with no manual step.
- Confirm the exit key is reachable only at the access level you set.
- With the runtime up, reach each tool by its chosen path and make a test configuration change.
- Confirm the local screen, touch input, and tag updates stayed normal during and after that session.
- Exit the runtime, open each tool from its desktop shortcut, relaunch, and confirm the first screen and live values return.
- Record CPU and memory in Task Manager with everything open and confirm the values match the coexistence baseline.
Questions asked
Can a Vijeo Designer button launch an external Windows program?
No. The runtime exposes no run-program action on any object, and a review of the action lists in your own Designer version confirms it in minutes. The only application-level control is the exit-runtime function; after that, third-party tools open from Windows desktop shortcuts like on any PC.
How do I get back to the Windows desktop on a touch-only iPC?
Put the runtime-exit function on a screen that operator-level users cannot reach, download the project with the runtime stopped on the target, and press the key. Confirm the runtime process disappears from Task Manager, do the work, then start the runtime again from a desktop shortcut to return to the first screen.
Why did a Pro-face demonstration launch programs when my Vijeo iPC cannot?
The panels overlap in hardware, but the launch function belongs to the HMI software layer, which is a different product. Behavior seen on a Pro-face unit does not transfer to a Vijeo Designer project, so design your access around the exit key plus shortcuts, or around a remote session that leaves the runtime running.
Can I use Windows Remote Desktop to configure the tools while the runtime runs?
Only after a separate test. A Remote Desktop login for the same account can move the interactive session off the local console and leave the panel locked, which breaks a runtime tied to that session. Prefer a remote-control tool that shares the console session, then verify the local screen and touch input after connecting and disconnecting.