To start a Movicon operator interface when Windows starts, create a shortcut that launches the Movicon runtime with the project file as an argument, test the shortcut manually, and then place it in Windows Startup. The available evidence covers Movicon 11.5 on Windows 7; behavior on other releases is not established.
Build the Movicon 11.5 Runtime Command
The runtime executable was identified in the Movicon 11.5 installation folder. Use the complete executable path and pass the project filename after it. Keep both arguments in quotation marks because the executable path contains spaces.
"C:\Program Files (x86)\Progea\Movicon11.5\moviconRunTime.exe" "myproject.movprj"Replace myproject.movprj with the actual project name. If Windows cannot locate the project by filename alone, enter its complete path; the evidence does not establish the project directory.
Configure Automatic Startup
- Locate
moviconRunTime.exeinC:\Program Files (x86)\Progea\Movicon11.5and create a Windows shortcut. - Open the shortcut properties and append a space followed by the quoted project filename or complete project path to the target.
- Run the shortcut manually. Confirm that it opens the runtime and loads the intended project rather than only opening the development environment.
- After the manual test succeeds, copy the shortcut into Windows Startup and restart the computer to verify unattended launch.
Separate Shortcut and Active-Project Methods
| Method | Evidence-supported requirement | Verification |
|---|---|---|
| Explicit shortcut | Launch the runtime executable and supply the project as an argument. | Run the shortcut directly before placing it in Startup. |
| Active project | Open or associate the project as the active project in the development environment. | Launch the runtime from File Explorer and confirm that the associated project opens. |
| Windows service | The development software exposes an install-as-service command. | Check Windows administrative services for an automatic Movicon service. |
The service method was reported not to start the interface when Windows booted, so do not treat service installation as equivalent to a verified interactive HMI launch. Test the explicit shortcut first.
Diagnose a Touch-Screen Startup Failure
The reported system used Windows 7 on a CET S.N.C. PC 2015 1S 34 TS touch-screen computer. Reports were contradictory: startup was first said to work and later said not to work on the touch screen. No error message or confirmed root cause was supplied.
On the target panel, repeat the manual shortcut test under the same Windows account used at startup. Verify the runtime path, project argument, active-project association, and presence of the shortcut in Startup. If using the service method, inspect Windows Services and confirm whether the Movicon service exists and is configured for automatic startup; service presence alone does not prove that the graphical interface will appear.
FAQ
How do I start a Movicon 11.5 project automatically in Windows 7?
Create a shortcut to moviconRunTime.exe, append the quoted project filename or full path, test it manually, and then copy the working shortcut into Windows Startup.
What command launches a Movicon 11.5 project?
Use "C:\Program Files (x86)\Progea\Movicon11.5\moviconRunTime.exe" "myproject.movprj", replacing the project argument with the actual filename or complete path.
Why does the Movicon shortcut work on a PC but not on the touch screen?
The evidence does not identify a root cause. Test the shortcut directly on the touch-screen computer and verify its runtime path, project path, active-project association, Startup placement, and startup user account.