Settings for the Control Manager
[ctrl] ctrlDLL
- Type
- string
This config entry loads a CtrlExtension DLL. First, the DLL is searched in
<proj_path>/bin. If it does not exist there, it will be searched in the
<wincc_oa_path>/bin. This entry can only be set in the [ui] or the [ctrl] section. If a
DLL should be used by the UI and CTRL, this must be loaded in both sections. The number of
DLLs to be load is not limited.
Note: It is recommended to load a CtrlExtention DLL directly from the Ctrl script using the
#uses statement.
[ctrl] minWorkInterval
- Type
- int
- Default
- 1
- Range
- >= 0
Minimal time in seconds the CTRL Manger waits between two work() calls.
[ctrl] queryRDBdirect
- Type
- bool
- Default
- 0
- Range
- 0|1
Indicates the mode of database read queries:
- 0 = Standard CTRL read functions (dpGet...()) via the WinCC OA Event Manager and the
WinCC OA Data Manager.
- 1 = The standard CTRL read functions (dpGet...()) are redirected to directly contact the
database server.
Note that the two required CTRL extensions must also be loaded in order to be able to use
the RDB read functions.
Can be used in [ui] and [ctrl] sections.
CtrlDLL = "CtrlRDBArchive"
CtrlDLL = "CtrlRDBCompr"
CAUTION: If you use queryRDBdirect = 1 and query DPEs using the event screen, enter the
DPEs or *.* for the query. Otherwise the event screen does not show the DPEs.
[ctrl] useNGADirectRead
- Type
- bool
- Default
- 0
- Range
- 0|1
By using the config entry "useNGADirectRead" (can be used in [general], [ui] or [ctrl]
sections) the behavior of the standard WinCC OA historical read functions can be changed to
always use their "NGA" counterpart, i.e. use direct read. This means, e.g., that when a client
calls dpGetPeriod(), the direct read counterpart dpGetPeriod-NGA() is called instead.
