Welcome to our new forum
All users of the legacy CODESYS Forums, please create a new account at account.codesys.com. But make sure to use the same E-Mail address as in the old Forum. Then your posts will be matched.
Close
Reason: I have a script which restarts the service ...\GatewayPLC\CodesysControlService.exe in (though rare) system crash events, but at this time 1 ) Add the following folders to Windows Environment Variables:
Reason: I need to make a script that will upgrade many Controlleres at the same time, so with an environment variable, I could do the job with no need to create any additional step to seek the name of the above folder.
Last edit: alrcastro 2020-04-07
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
hm... but this is a typcial task for the CODESYS Automation server... this would be done in seconds on x controller
Just want to motivate to try out this option.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
this is a typcial task for the CODESYS Automation server
Ok, it could solve the issue for while, but it will not remain free. Since is is expected a big amount of deploys during the end 2020 and start of 2021, I just wanted to deal with the affordable solution.
I'm sure it is quite easy to implement on the development team side.
Please consider forwarding this request.
Last edit: alrcastro 2020-04-07
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
@alrcastro
If that would be a product feature, someone would have to solve the problem of multiple runtimes being installed.
And what should happen if the runtime is running with different configuration files resulting in different ProgramData paths.
Currently the feature request sounds really specific for your use case.
👍
1
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Regarding the PATH request in the environment variable for each installed runtime, I absolutely cannot understand the issue of implementing this, since the installation is made by a standard installer application, which when generating the directory could create an entry for each one.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Adding the runtime installation folder to the PATH would not help you with multiple installations.
Then always the first installed runtime would win and for everyone it would not be clear which runtime is currently used.
👍
1
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Forget about creating a PATH enviroment variable, something that is available in many other programs, not Codesys. To be honest, I give up on this request.
👍
1
Last edit: alrcastro 2020-04-09
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
That´s my 2 cents, I guess not too complicated:
1 ) Add the following folders to Windows Environment Variables:
Reason: I have a script which restarts the service ...\GatewayPLC\CodesysControlService.exe in (though rare) system crash events, but at this time 1 ) Add the following folders to Windows Environment Variables:
Reason: I need to make a script that will upgrade many Controlleres at the same time, so with an environment variable, I could do the job with no need to create any additional step to seek the name of the above folder.
Last edit: alrcastro 2020-04-07
more posts ...
hm... but this is a typcial task for the CODESYS Automation server... this would be done in seconds on x controller
Just want to motivate to try out this option.
Ok, it could solve the issue for while, but it will not remain free. Since is is expected a big amount of deploys during the end 2020 and start of 2021, I just wanted to deal with the affordable solution.
I'm sure it is quite easy to implement on the development team side.
Please consider forwarding this request.
Last edit: alrcastro 2020-04-07
@alrcastro
If that would be a product feature, someone would have to solve the problem of multiple runtimes being installed.
And what should happen if the runtime is running with different configuration files resulting in different ProgramData paths.
Currently the feature request sounds really specific for your use case.
Regarding the PATH request in the environment variable for each installed runtime, I absolutely cannot understand the issue of implementing this, since the installation is made by a standard installer application, which when generating the directory could create an entry for each one.
Adding the runtime installation folder to the PATH would not help you with multiple installations.
Then always the first installed runtime would win and for everyone it would not be clear which runtime is currently used.
Anyway you might use this to get the information where the plc has his working directory:
The section [Sysfile] in CODESYSControl.cfg
C:\Program Files (x86)\CODESYS 3.5.15.40\GatewayPLC\CODESYSControl.cfg
[SysFile]
Windows.WorkingDirectory=C:\ProgramData\CODESYS\CODESYSControl\175939B4\
Forget about creating a PATH enviroment variable, something that is available in many other programs, not Codesys. To be honest, I give up on this request.
Last edit: alrcastro 2020-04-09