AlfredoQuintero
Lifetime Supporting Member
Hello. I have been trying to crack this one without success and could not find any hint after several search attempts. I wonder if any CODESYS guru could help.
I am finishing a CODESYS WIN 64 application for a customer.
This customer will then sell the application to their end-users, but the end-users are responsible for the Windows 10 system in which the program will run, and the customer needs to get the CODESYS license and so on.
When one wants to install the runtime application on the Windows "runtime-only" system (in which the CODESYS development environment is NOT to be installed), normally the computer with the CODESYS engineering tool is connected on the same network as the runtime system, one starts the PLC application in the runtime and from the engineering environment the runtime PC is scanned and detected, the program is successfully downloaded and then the program will work on the runtime system without needing to use the engineering tool if there is no change in the soft-PLC program.
But my customer does not want to give the sources of my program to the end-users, not only for intellectual property protection, but also because doing what I describe in above paragraph may be challenge for many customers and could be an after-sales support nightmare, which my customer is so eager to avoid.
I tried a number of hacks, like copying the full C:\ProgramData\CODESYS\CODESYSControlWinV3x64\7F8584BF\PlcLogic folder from one system in which the program works to another, but if I do this the program does not start on the system on which I copy the full contents of this folder. It seems this is not a very good hack.
I hope there is a way to do this, otherwise all I can tell my customer is that they provide the CODESYS project to the end-user password protected or some other inelegant solution. Thanks for reading down to this point.
I am finishing a CODESYS WIN 64 application for a customer.
This customer will then sell the application to their end-users, but the end-users are responsible for the Windows 10 system in which the program will run, and the customer needs to get the CODESYS license and so on.
When one wants to install the runtime application on the Windows "runtime-only" system (in which the CODESYS development environment is NOT to be installed), normally the computer with the CODESYS engineering tool is connected on the same network as the runtime system, one starts the PLC application in the runtime and from the engineering environment the runtime PC is scanned and detected, the program is successfully downloaded and then the program will work on the runtime system without needing to use the engineering tool if there is no change in the soft-PLC program.
But my customer does not want to give the sources of my program to the end-users, not only for intellectual property protection, but also because doing what I describe in above paragraph may be challenge for many customers and could be an after-sales support nightmare, which my customer is so eager to avoid.
I tried a number of hacks, like copying the full C:\ProgramData\CODESYS\CODESYSControlWinV3x64\7F8584BF\PlcLogic folder from one system in which the program works to another, but if I do this the program does not start on the system on which I copy the full contents of this folder. It seems this is not a very good hack.
I hope there is a way to do this, otherwise all I can tell my customer is that they provide the CODESYS project to the end-user password protected or some other inelegant solution. Thanks for reading down to this point.
