I have a Control Win V3.5 SP20 (64-bit) application, and until now, I open the program (with a password) and download it. However, I need to give the client the option to install the program on the Controller, without them having to open it and access the code. So, I followed these steps:
1 – In the Online => Create Boot Application menu, I saved the generated files in a directory:
Application.app
Application.crc
PlcLogic\visu\ directory with several files
2 – In the SysTray, I ran the PLC, and it created a directory. In the root of this directory (C:\ProgramData\CODESYS\CODESYSControlWinV3x64\E84889DB), I pasted Application.app and Application.crc.
Since it created a \visu directory, I pasted the PlcLogic\visu\ files generated in Create Boot Application into it.
3 - In the general Codesys directory (C:\ProgramData\CODESYS\CODESYSControlWinV3x64), I edited CodesysControl.cfg, adding: [CmpLog]
Application.1=Application
4 - When running the PLC, nothing happens and the TargetVisu screen does not open.
What I'm doing wrong?
From what you describe, the boot application files are in the right place, but the key step you’re missing is how the runtime knows which application to load. In most cases with CODESYS Control Win, you don’t need to edit CodesysControl.cfg manually. Instead, once you’ve created the boot application (Application.app and .crc), copy them into the runtime instance directory (for example …\E84889DB), then restart the service. The PLC should automatically detect Application.app and start it. If TargetVisu still doesn’t open, double-check that the visualization settings are enabled for TargetVisu (Project → Devices → Visualization), and that you built the project with visualization included before creating the boot application. Editing the config is rarely required unless you’re running multiple applications ball orbit
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I did these steps and it worked:
- Copied Application.app and Application.crc to the Folder C:\ProgramData\CODESYS\CODESYSControlWinV3x64\ID_of_CPU\PlcLogic\Application\
copied the visu folder content to the folder C:\ProgramData\CODESYS\CODESYSControlWinV3x64\ID_of_CPU\PlcLogic\Application\visu\
Changed by Notepad the CODESYSControl.cfg at the folder C:\ProgramData\CODESYS\CODESYSControlWinV3x64\ID_ of_CPU\
Where is [CmpApp], adding a line with: Application.1=Application
Last edit: leandroct 2025-09-04
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I have a Control Win V3.5 SP20 (64-bit) application, and until now, I open the program (with a password) and download it. However, I need to give the client the option to install the program on the Controller, without them having to open it and access the code. So, I followed these steps:
1 – In the Online => Create Boot Application menu, I saved the generated files in a directory:
Application.app
Application.crc
PlcLogic\visu\ directory with several files
2 – In the SysTray, I ran the PLC, and it created a directory. In the root of this directory (C:\ProgramData\CODESYS\CODESYSControlWinV3x64\E84889DB), I pasted Application.app and Application.crc.
Since it created a \visu directory, I pasted the PlcLogic\visu\ files generated in Create Boot Application into it.
3 - In the general Codesys directory (C:\ProgramData\CODESYS\CODESYSControlWinV3x64), I edited CodesysControl.cfg, adding:
[CmpLog]
Application.1=Application
4 - When running the PLC, nothing happens and the TargetVisu screen does not open.
What I'm doing wrong?
From what you describe, the boot application files are in the right place, but the key step you’re missing is how the runtime knows which application to load. In most cases with CODESYS Control Win, you don’t need to edit CodesysControl.cfg manually. Instead, once you’ve created the boot application (Application.app and .crc), copy them into the runtime instance directory (for example …\E84889DB), then restart the service. The PLC should automatically detect Application.app and start it. If TargetVisu still doesn’t open, double-check that the visualization settings are enabled for TargetVisu (Project → Devices → Visualization), and that you built the project with visualization included before creating the boot application. Editing the config is rarely required unless you’re running multiple applications ball orbit
Last edit: chloereed 2025-09-04
I did these steps and it worked:
- Copied Application.app and Application.crc to the Folder C:\ProgramData\CODESYS\CODESYSControlWinV3x64\ID_of_CPU\PlcLogic\Application\
copied the visu folder content to the folder C:\ProgramData\CODESYS\CODESYSControlWinV3x64\ID_of_CPU\PlcLogic\Application\visu\
Where is [CmpApp], adding a line with: Application.1=Application
Last edit: leandroct 2025-09-04