[event]

[event] activeRecoveryTimeout

Type: unsigned int (seconds)
Default: 1800
Range: >= 0

Maximum time period in seconds the active Event may need for initialization of the passive Event. If after this period the initialization is still not completed, the Event cancels the initialization. This avoids that the initialization process takes too long in case of problems on the passive host.


Caution: The time must be sufficient so that both Event managers are able to connect to each other. This means
that in this time Redu managers and CTRL managers are started and both Redu managers od the redundant systems
are connected to each other.

[event] alertConditionBit

Type: string
Default: no check of a status bit
Range: identifier of a status bit

The alert handling of original values will be executed only if the here defined status bit (of the same DP element) has been set or not. This depends on the alertConditionLogic entry (see the entry below). This means that if you want to execute an alert handling of a particular datapoint element, the status bit of exactly this datapoint has to be set. All other values will be ignored by the alert handling. If the status bit has been set to the value of alertConditionLogic, an alert handling of the current value will follow immediately. The alertConditionBit = "_invalid" and alertConditionLogic = 0 for example, prevent the alert handling of invalid values. The value of the alertConditionBit can be any of the status attributes: _userbit1, _userbit2 (up to _userbit32), invalid or bad bit.

[event] alertConditionLogic

Type: bool
Default: 1
Range: 0|1

Defines to what value the status bit specified by the alertConditionBit has to be set to execute an alert handling of the corresponding original or online value. If the value of alertConditionLogic has been set to 1, an alert handling will be executed. If the value of alertConditionLogic has been set to 0, no alert handling will be executed. These two entries are dependent on each other. Thus, alertConditionBit = "_invalid" and alertConditionLogic = 0 for example, prevent an alert handling of invalid values.

[event] alertSignOrder

Type: string
Default: vVwWaA

For sum alerts, the Event must be able to sort alerts by the abbreviation. This string is used for the sorting. The first character has the lowest priority. Characters that are not contained in the string are all of the same priority and are placed before the first character of the string.

[event] attributesFromAddValues

Type: int
Default: 1
Range: 0-3

Defines whether additional values are written to alarm attributes and are shown in the specific columns of the AEScreen.

0 -> no transfer of additional values (_alert_hdl_add_values) to alarm attributes.
1 -> additional value with the index 2 (_alert_hdl.._add_value_2) is written to the alarm text (_alert_hdl.._text) if defined and shown in the alert screen. The attribute _alert_hdl.._mapped_text can be used additionally to query the additional value.
Note: Applies only to multiinstance alarms. If _alert_hdl.._add_value_2 is mapped to the _alert_hdl.._text attribute it may only be set in the same command (dpSet() or Message) when the alarm comes or goes (_event : DPATTR_ALERTEVENT_CAME/WENT) and is locked for later changes. If _alert_hdl.._add_value_2 should be freely available, attributesFromAddValues must be set to 0.
2 -> additional value with the index 1 (_alert_hdl.._add_value_1) is written to the alarm value (_alert_hdl.._value) if defined.
3 -> additional values are written to alarm text an alarm value (combination of 1+2).

Note: The use of this entry only makes sense when the alarm value and text are written to the first both additional values by the driver/manager.

If 'attributesFromAddValue' is set, it's considered as definitely mapping to text and value. After an alarm occured, the alarm value and text mustn't be changed (reason: alarm value and text describe the value and associated text which has triggered the alarm. Therefore, the mapped add_values mustn't be changed). The mapped values are only allowed to be passed at the coming (ALERTEVENT_CAME, ALERTEVENT_CAME_IMPULSE) or going (ALERTEVENT_GONE, ALERTEVENT_GONE_IMPULSE) of an alarm in the same message after an event. During the event ALERTEVENT_GONE_INACTIVE, value and text can't be set, because normally it modifies multiple alarm instances. In this case, as well as if there are no associated values, the value and text are provided by the parameterization or the current value. The config entry only applies to multi instance alerts and is ignored in case of normal alarms.

[event] copyDp

Type: string string
Range: <Name of source DP element> <Name of target DP element>


config.redu

Changes of the original attributes of the specified source DP element are also made on the same element of the specified target datapoint by the Event manager.The target datapoint has to be of the same type as the source datapoint. If the element is a node this applies for all leaves under the node. In order to duplicate different elements the entry can also be specified several times. Some specific datapoint elements (alerts from WinCC OA, e.g. HD is full) can have in redundant systems different values. Therefore for such elements system-specific datapoints are created. Unfortunately, these datapoints also contain elements (commands to WinCC OA, e.g. file switch) which actually should not be copied. As this would be only possible via a change of the datapoint type, the here described possibility is available. This config entry is for the redundancy, but can also be used in non-redundant systems.

[event] copyDpType

Type: string
Range: name of the source DP element


config.redu

With the entry copyDpTypes all changes of the original attributes in the specified source datapoint element are also made to the elements of all datapoints of the specified target datapoint type, analogous to copyDp. Syntax:


[event]
copyDpTypes = "<datapoint type>.<datapoint element>"

If two datapoints of this type have the names <DPname> and <DPname>_2, <DPname>.<element> will be copied to <DPname>_2.<element>.

Restriction: <DPname> must not end with _2.

For example: The datapoints Iec_2 and Iec_2_2 will never match for a copyDpType configuration.

[event] createUsersAllowed

Type: bool
Default: 1
Range: 0|1

Config entry for the Kerberos authentication. Specifies whether the Event manager may add new users to the _Users DP. The new user obtains a user ID, which is the highest user ID + 1. The system also sets the group membership and user rights etc.

[event] discardOldValues

Type: bool
Default: 0
Range: 0|1

discardOldValues = 1 discards old values which were received by the driver and, normally, would be set to invalid using negativeSourceTimeDiff. This entry should only be used in combination with negativeSourceTimeDiff and if it is guaranteed that there is always only one WinCC OA system connected to the periphery.

[event] dpFctActivate

Type: bool
Default: 1
Range: 0|1

This entry deactivates the execution of datapoint functions in the Event Manager, when indicated.

If this entry is set to 0, a dp_fct or stat_func config cannot be activated via a script.

[event] dpFuncOldNewCompare

Type: bool
Default: 0
Range: 0|1

Value 0 = unchanged Event manager functionality. Value 1 = For all datapoint functions a new/old comparision is enabled, regardless of the value of _dp_fct.._old_new_compare. This means the result of the calculation is only written if it differs from the current value in the process image.

[event] driverNegativeSourceTimeDiff

Type: double
Default: actual value of negativeSourceTimeDiff
Range: >= 0

Normally the active event manager discards the values from the driver within an old time stamp in a redundant operation, in case that it has already received a more recent value from the other event manager. The entry driverNegativeSourceTimeDiff causes that the event manager processes the values, which are younger then the values of negativeSourceTimeDiff. That applies only to value changes from the driver, which do not have a peripheral time stamp. This entry has no effect on values with a peripheral time stamp. Default: The default value is the current value of the negativeSourceTimeDiff config entry. That means that if driverNegativeSourceTimeDiff is not entered, the set value will be taken from negativeSourceTimeDiff (not the default value, but the current value).

[event] eventsFileStateBit

Type: unsigned integer
Default: 1
Range: 0..32

Defines the user bit for switching the debug of the event file (-dbg 19 in the command line). Only datapoints with this user bit will be displayed. The output file is in the log directory of <wincc_oa_proj>/events.YYMMDD. The outputs contains a bit pattern according to the status bit of the original value. The last 32 bits define the user bits, the others define the status bits and the first bit defines the data type of the original value. Note: The value 0 sets all user bits. The value 1 sets the user bit 1, etc

[event] evStatusDP

Type: string
Range: a bool element of an arbitrary datapoint

Using this datapoint the Event manager reports its active / passive state to the redundancy.

[event] forceActiveDP

Type: string
Default: _ReduManager[_2].ForceActive
Range: -

Using this data point element the event manager can be forced to close the connection to the active event manager and become active, even if the active event manager does not work properly. Must not be set using the PARA!

[event] fwdDp

Type: string
Range: name of the datapoint element


config.redu

Changes of the original attributes of the specified datapoint element are forwarded by the Event manager to the redundant Event manager (relates to redundancy). If the element is a node this applies for all leaves under the node. In order to forward different elements the entry can also be specified several times. Forwarding is used to report changes that can occur in only one of two systems (e.g. DM HD full) also to the other redundant system.

[event] fwdDpType

Type: string
Range: name of the datapoint element


config.redu

Analog to fwdDp, all changes at this datapoint element are forwarded by the Event manager to the redundant Event manager. In contrast to fwdDp not the name of a datapoint element of an existing datapoint is specified, but the element of a datapoint type in the format 'Type.Element' (e.g. 'ExampleDP_Bit.' for the root element of the datapoint type ExampleDP_Bit). Thus, the corresponding elements of all datapoints of this type are forwarded, independing of whether they already exist at start of the Event manager or they not. If the element is a node this applies for all leaves under the node. In order to forward different elements the entry can also be specified several times.

[event] heartbeatTime

Type: uint
Default: 1

Defines the interval in which the datapoint element _Event[_2].Heartbeat is incremented.

[event] licBACnetObjectsBlocksize

Type: unsigned integer
Default: 200
Range: 10-200

Defines the license block size for the "BACnet Objects" option.

If

licBACnetObjectsBlocksize = 100

is set, the size of the licenses requested in blocks is 100.

This setting applies exclusively to licenses with the license type "countable" and the product name "BACnet Objects".

[event] link0DP

Type: string

The Event manager tries to establish the connection to the peer only if the Redu manager verifies that the primary network connection is alive. If the alive check sets this datapoint to FALSE, the connection is shutdown and buffering is started. Note: normally _ReduManager*.PeerAlive.Link0 element of the own Redu manager.

[event] maxAlertConnectCount

Type: uint
Default: 1000000

Defines the number of elements (= the number of rows x the number of columns) that will be queried in a query with alarms. If the set number has been exceeded, the query will be canceled as soon as possible and an error will be returned. This config entry is valid for dpQueryConnect(). If the entry is set to 0 there is no limitation.

[event] maxAlertRequestCount

Type: uint
Default: 1000000

Defines the number of elements (= the number of rows x the number of columns) that will be queried in a query with alarms. If the set number has been exceeded, the query will be canceled as soon as possible and an error will be returned. This config entry is valid for dpQuery(). If the entry is set to 0 there is no limitation.

NOTE: If you set higher values than the default values for this config entry, this can lead to a significant increase in memory consumption (RAM) by the WinCC OA runtime.

[event] maxInputMsgCount

Type: unsigned
Default: 100000
Range: >= 1000

Upper limit of messages (amount of messages) in the message queue container of the Event Manager (receiving direction). If the limit of 'msgQueueLimitTimeout' seconds has been exceeded, the connection to the concerned manager is closed.

[event] maxParseTime

Type: unsigned integer
Default: 20
Range: >= 0

Defines the time (in seconds) that a query to the event manager can take at parse time. This entry can be used to analyze what queries block the system.

[event] maxValueConnectCount

Type: uint
Default: 1000000

Defines the number of elements (=number of rows x the number of columns) that are queried. If the set number has been exceeded, the query will be canceled as soon as possible and an error will be returned. This config entry is valid for dpQueryConnect(). If the entry is set to 0 there is no limitation.

[event] maxValueRequestCount

Type: uint
Default: 1000000

Defines the number of elements (=number of rows x number of columns) that are queried in a query. If the set number is exceeded the query is canceled as soon as possible and an error is returned. This config entry is valid for dpQuery() and dpGetPeriod(). Queries for the history DB are also limited with this config entry. If the entry is set to 0 there is no limitation.

[event] msgQueueHoldTime

Type: int
Default: 60

During the time (in seconds) between the failure of driver communication and the switch to the passive system, the passive system will buffer the values from the driver until it receives a current value from the active driver. The buffering time is specified in the config file with the config entry msgQueueHoldTime.

[event] msgQueueLimitTimeout

Type: unsigned
Default: 60
Range: >= 20

Time period in seconds within the limit of the message queue container in the Event manager (in receiving direction) may be exceeded. For the reset of the timeout the fall of 10% below the limit is necessary. If the double value of the limit is reached, after only one tenth of the time an emergency treatment occurs. Handling when the timeout expires: The Data manager issues only one error message. For all other managers the connection is closed. For managers in other systems the queue of the Event manager is cleared.

[event] negativeSourceTimeDiff

Type: unsigned integer
Default: 0
Range: >= 0

Time in seconds between one source time and the last source time without that the bit is set to "invalid source time". The source time will be corrected to "last source time + 1 millisecond".

[event] passiveRecoveryTimeout

Type: unsigned integer
Default: 300
Range: >= 0

The maximum time period in seconds which the passive Event waits for the end of its initialization by the active Event. If after this period the initialization is still not completed, it becames active by itself and does not buffer any messages anymore. This prevents that the passice Event waits too long when the connection fails during the initialization of the connection.


Caution: The time must be sufficient so that both Event managers are able to connect to each other. This means
that in this time Redu managers and CTRL managers are started and both Redu managers od the redundant systems
are connected to each other.

[event] redConnTryInterval

Type: unsigned integer
Default: 60
Range: >= 0

Defines in which intervals (in seconds) the connection between the redundant Event managers (redundancy) is tried to be established when the connection is not established.

[event] redOldNewComp

Type: bool
Default: 1
Range: 0|1

This setting is relevant in redundant systems only. After a redundancy switch drivers will do a GQ which will forward all values from the PLC to the event manager without any smoothing. That way it is ensured that the values the driver uses for smoothing are the same as the values in the process image. Instead the event manager can compare the values from a GQ with the process image and discard identitical values. That way the load of the Event manager during a redundancy switch is reduced. Value 0 = the Event manager will not do an old/new comparision Value 1 = the Event manager will do an old/new comparision

[event] refuseCNS

Type: bool
Default: 1
Range: 0|1

Specifies if a manager shall hold CNS data of the identification in memory. CNS data is still tranferred with the identification but the manager discards this data.

[event] updateUsersAllowed

Type: bool
Default: 1
Range: 0|1

Specifies whether the WinCC OA Event may update the _Users DP when a user contained in the _Users DP, logs on. Under Windows, the system runs a search for the OSID, under Linux for the name. The WinCC OA Event manager updates the name (only under Windows), description, group membership, authorization bits and primary group. If the config entry createUsersAllowed is set to 1 (Default value), the Event manager ignores the updateUsersAllowed entry, and updates of the _User-DP are basically allowed.

[event] useALMTrialLicenseDialog

Type: bool
Default: 1
Range: 0|1

useALMTrialLicenseDialog = 0 prevents the opening of a pop-up dialog in which the user is asked whether the found ALM trial license should be used. This entry should be set to 0 if WinCC OA is started as service. Otherwise in case of non-confirmation of the pop-up dialog WinCC OA is started in demo mode.

[event] useCRC

Type: bool
Default: 0
Range: 0|1

useCRC is a safety feature of the WinCC OA messaging system. It offers extended failure detection capabilities compared to the Standard messaging system. To ensure data integrity in WinCC OA Messages, these messages are divided into CRC telegrams of appropriate length each containing a 32 bit CRC. On reception of the messages the values are checked and if the values do not match, an error is detected. The error is shown in the log viewer and the connection between the WinCC OA managers is closed.

The entry "useCRC" can be used in the [event] or in a driver specific section of the config file. It can be used in one of these sections or in both sections.
The entry is always manager specific. The "stronger" manager wins and decides the type of connection:
EXAMPLE The connection between the driver and the event will use the extended data integrity check. As will all other managers that connect to the event manager.
```
[event]
        useCRC  = 1
        [mod]
        useCRC = 0
```
EXAMPLE The connection between the driver and the event will use the extended data integrity check. All other managers that connect to the event manager will not use it (unless specified in their section).
```
[event]
        useCRC  = 0
        [mod]
        useCRC = 1
```
The information whether a specific connection uses extended data integrity check or not is written to the connection data point of the manager. In addition a log entry will be written upon startup of the manager reporting its way of communication.
In a redundant system the entry can be used in one or both system(s) of the redundant system.
In a DRS system the entry can be used in one or both of the DRS system(s).
If distributed systems are used and one of the systems is a safety system and the other system is not, use the entry only for the safety system. The distributed partner of the safety system will use CRC checks when communicating with the safety system's event. CRC checks will not be used when communicating with the non-safety system's event manager.
NOTE Default behavior is communication without extended CRC checks.
In case an invalid value is entered to the config file for the keyword "useCRC", a warning will be output in the log file and the manager will use default behaviour in its communication.
Log messages are output when CRC is used or when CRC was configured but is not used due to a localhost connection.
A message is also output when CRC is configured and should be used but is not being used (WARNING).

For a safety project see also the "Basic and operating Conditions" document in the ETM portal.

[event] useSourceTime

Type: bool
Default: 0
Range: 0|1

If attributes of other configs than _default, _corr and _original are changed, the time of the Message is ignored and the current time is used. This ensures, that the parameterization is always timed ascending. If useSourceTime = 1 is set, the Message's time is taken for all configs.

[event] validTimeDiff

Type: unsigned int (minutes)
Default: 10
Range: >= 0

Maximum time in minutes, the source time of a value change may lie in the future. If the time lies further in the future, the corresponding ValueChangeMsg will be discarded and an error message is issued.