Registry Entries of the RTE
The behavior of CODESYS Control RTE can be configured partially in the Windows Registry Editor (Windows registry). The following table provides information about the values and respective default values that are used if the value is missing. Only part of these values can be modified in the PLC Configuration dialog of CODESYS Control RTE.
All values are located in the registry at the path HKEY_LOCAL_MACHINE\SOFTWARE\3S-Smart Software Solutions GmbH\CODESYS SP\3SRTE3
, or relative when a key is specified before the name in the table.
Name | Type | Meaning | Default Value |
---|---|---|---|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
DWORD |
|
|
|
|
|
|
|
| Size of the buffer for asynchronous function calls (all function calls that are executed from Windows (for example, file services or socket functions). The more simultaneous calls an application requires, the larger this buffer should be for reasons of performance. |
|
|
| This value points directly to the configuration file of CODESYS Control RTE. | <installation path of CODESYS Control RTE> |
|
| This value is used internally by the PLC Configuration dialog. This variable can be changed manually for example only if the configuration dialog would crash and the variable would no longer write to |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| This value points to the directory that is the root path of the file system of CODESYS Control RTE. | <installation path of CODESYS Control RTE> |
|
| TCP/IP port where the communication takes place locally between "SysTray" and the system service of CODESYS Control RTE. |
|
|
DWORD | IP address of the remote system that should be managed with the "SysTray" of CODESYS Control RTE. |
|
|
| Same as |
|
|
|
|
|
|
| Version of CODESYS Control RTE that was started last time on this PC. Written each time the CODESYS Control RTE starts. | <version ID> |
|
| Version of the system service of CODESYS Control RTE. Should always be the same version as for the kernel, except for manual patches for which the kernel or the system service was replaced manually by another version for testing purposes. | <version ID> |
|
| All subkeys in this key are displayed in the list box of the available components in the PLC Configuration dialog. | |
|
| Size of the stack for each task when needed (unexplainable crashes for complex function calls). |
|
|
| The first exception that occurs should generate a blue screen of death (and therefore a core dump used for diagnostic purposes. Kernel memory should be selected in the Windows system settings for Start and Restore. |
|
For more information, see: Configuring Real-Time Behavior on Special Platforms