[opcae_servername]

[opcae_servername] conditionEventDp

Type: string

Defines a datapoint of type string to which all conditional events are mapped. If the entry is empty (default) no mapping is done. If the entry is defined to a valid string DPE all conditional events of this server are mapped to the DPE in JSON format.

[opcae_servername] prefix

Type: string
Default: AE_

Defines the prefix which is used in all automatically generated datapoint elements. If the same items exist in two or more servers, the prefix has to be different for each of the servers.

[opcae_servername] simpleEventDp

Type: string
Default: DP prefix+SimpleEventNotifications

Defines a datapoint of type string to which all simple events are mapped on the client. If this entry is not specified, the simple events are mapped to the datapoint prefix+SimpleEventNotifications.


Example:
[opcae_ABB1]
simpleEventDp = "GU_SimpleEvents."

The string that is written by the AE client, is composed as follows:


EventSource + "|" + EventMessage + " (severity " + EventSeverity + ")"

Thereby the italic written values are the values sent by the OPC server in it's message and put together to the string (shown below) by the client.


Example:
"123.124.23.17_ConERR | No Alive Signal (severity 250)"

[opcae_servername] twoStateConditionsOnly

Type: bool
Default: 0
Range: 0|1

Use this config entry to inform the client that the server only provides boolean alarms. If the server only provides boolean alarms, you cannot create master datapoints using the panels or assign server items to client items. You have to create the configuration manually in the PARA or import it by using the ASCII manager. The OPC A&E client automatically creates a master datapoint with two alert ranges (0=inactive, 1=active) at run time.

[opcae_servername] watchdog

Type: string string int
Range: <wdMsg> <wdTargetDp> <wsTimeout>

The monitoring of the OPC AE connection works in the following way:

The OPC AE server sends a SimpleEvent of a special format (watchdog event) to the client periodically.
The arrival of a watchdog event at the client resets a timer.
If the timer expires before a new watchdog event is risen by the server a binary DPE is set (1). This signal can then be used for further processing (redundancy switch, raising an alarm, archiving).

Only changes in the state of the watchdog will be sent to the system to minimize traffic Note: As many watchdogs as desired can be introduced for one server by just adding the appropriate number of config entries (see example). The config entry must be specified like this: watchdog = <wdMsg> <wdTargetDp> <wsTimeout> wdMsg = string that identifies the watchdog message within the SimpleEvent. It can either be the entire message or part thereof; no wildcards are allowed. wdTargetDp = DP name of the binary DPE that is set to TRUE in case of absence of the watchdog signal. wdTimeOut = timeout in ms Example watchdog = "WATCHDOG_PLC1" "wdDpPlc1" 10000 watchdog = "WATCHDOG_PLC2" "wdDpPlc2" 20000 watchdog = "WATCHDOG_PLC3" "wdDpPlc3" 30000 Redundancy In order for this mechanism to work in a redundant system, the following steps must be taken:

The target DP must exist twice (for "targetDP" there must be "targetDP_2"). The AE client will automatically set the correct DP.
To set the data points also on the passive system, there is an entry necessary in the config.redu file. The watchdog DPs must be declared as "forward DPs" (see fwdDp and fwdDpType).