Before creating this topic, I was browsing the search results for CodesysControl.cfg - many results, and I remember very well, it's a problematic issue for a long time.
To summarize: there were many requests for documentation on this file - the most comprehensive reply is:
Hi,
not really, this is covered by the manual which you get if you use a runtime toolkit which is not free of charge.
Maybe we need to extract the config file part from that documentation if that is possible.
BR
Edwin
I am not sure how much is this relevant, since we buy SL License directly from CODESYS... I think it is a reasonable demand, to get documentation on the configuration entries affecting the documented behaviour of the runtime system and it's components
The actual reason I bring up this issue again can be read here:
but mostly my frustration about noticing some new, unknown and undocumented entries in my configuration file. Again. And this happens a lot recently.
Just some examples:
Changes with SysFile - and mandatory use of IEC path
Introduction of Mandatory user management
File transfer service now disabled by default
SysProcess - allowed commands
The above mentioned CmpApp parameters...
And finally (Regaridng windows install):
With the newer versions, the installation directory (together with the configuration file) tends to hide itself to some super silly location under the roaming profile data of local system account. I am not sure if this change was documented somewhere, but was a very unpleasant one. Someone could please explain the reason and the concept of the introduction of this release specific directories (I am sure, there is a good reason)
- how to use them properly?
- How to re-introduce user configuration (to preserve configuration data between versions)?
- How to do version - to version migrations properly?
- How to keep old version of runtime available and ready to start with it's original configuration and application?
- ...
Therefore, the lack a regularly updated description of CodesysControl .cfg , including all the configuration entries, together with their default values for different runtime versions is really a big deficiency.* This should be done for all components storing or just seeking data from this file...
(Maybe there is such thing but I failed to find???)
It is regularly causing trouble when introducing a new version (together with the long awaited bug fixes and enhancements), what has changed it's default behaviour for security or other practical reasons. I agree this is very important, and it is logical to change the default options: But it must be documented historically, and make it easily available, so we can prepare better for the upgrade of the runtime.
Forge talk is a great source, but not very practical for this kind of documentation purposes...
Thanks in advance for CODESYS staff 🙏🙏🙏
(Ps.: It would look rather silly, if some members of the user community prepares this documentation on a Forge Wiki page... Or??? Should we?)
👍
1
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Before creating this topic, I was browsing the search results for CodesysControl.cfg - many results, and I remember very well, it's a problematic issue for a long time.
To summarize: there were many requests for documentation on this file - the most comprehensive reply is:
https://forge.codesys.com/forge/talk/Runtime/thread/ebbf851a3d/#eb85
I am not sure how much is this relevant, since we buy SL License directly from CODESYS... I think it is a reasonable demand, to get documentation on the configuration entries affecting the documented behaviour of the runtime system and it's components
The actual reason I bring up this issue again can be read here:
https://forge.codesys.com/forge/talk/Runtime/thread/febad3cc40/#0e12
but mostly my frustration about noticing some new, unknown and undocumented entries in my configuration file. Again. And this happens a lot recently.
Just some examples:
And finally (Regaridng windows install):
With the newer versions, the installation directory (together with the configuration file) tends to hide itself to some super silly location under the roaming profile data of local system account. I am not sure if this change was documented somewhere, but was a very unpleasant one. Someone could please explain the reason and the concept of the introduction of this release specific directories (I am sure, there is a good reason)
- how to use them properly?
- How to re-introduce user configuration (to preserve configuration data between versions)?
- How to do version - to version migrations properly?
- How to keep old version of runtime available and ready to start with it's original configuration and application?
- ...
Therefore, the lack a regularly updated description of CodesysControl .cfg , including all the configuration entries, together with their default values for different runtime versions is really a big deficiency.* This should be done for all components storing or just seeking data from this file...
(Maybe there is such thing but I failed to find???)
It is regularly causing trouble when introducing a new version (together with the long awaited bug fixes and enhancements), what has changed it's default behaviour for security or other practical reasons. I agree this is very important, and it is logical to change the default options: But it must be documented historically, and make it easily available, so we can prepare better for the upgrade of the runtime.
Forge talk is a great source, but not very practical for this kind of documentation purposes...
Thanks in advance for CODESYS staff 🙏🙏🙏
(Ps.: It would look rather silly, if some members of the user community prepares this documentation on a Forge Wiki page... Or??? Should we?)