Internal data points of the OPC UA client

Defines the mapping of OPC UA severities to WinCC OA alert classes.

A mapping has the following format:

<OPC UA startSeverity1> <WinCC OA alertClass1>
<OPC UA startSeverity2> <WinCC OA alertClass2>
                                ...

An example of such a mapping is:

0 OPCUA_info
250 OPCUA_warning
500 OPCUA_alarm
1000 OPCUA_danger

I.e.:

• If an alarm with a severity of 150 is received, this belongs to the WinCC OA alert class "OPCUA_info".
• If an alarm with a severity of 499 is received, this belongs to the WinCC OA alert class "OPCUA_warning".
• If an alarm with a severity of 500 is received, this belongs to the WinCC OA alert class "OPCUA_alarm".
• If an alarm with a severity of 1000 (highest OPC UA severity) is received, this belongs to the WinCC OA alert class "OPCUA_danger".

The return code for the triggered history read request. The following values are possible:

• 0 - The specified parameters for the history read request were valid and the service request was sent to the server.

• -1 - No RequestID or no connection to the server, no history read request was sent to the server

• -2 - Unknown Function, no history read request was sent to the server

• -3 - Unknown Method, no history read request was sent to the server

• -4 - No matching peripheral addresses found, no history read request was sent to the server

The result codes for the history read request. If a peripheral address wildcard was defined in the parameters then this DPE contains a list of result codes for the appropriate data point elements.

The following values are possible:

• 0 - The OPC UA server returned the status code “Good” for the history read request

• -1 - The OPC UA server returned the status code “Bad” or “Uncertain” for the history read request

• -2 - The parameters for the history read request are invalid and no request was sent to the OPC UA server

The data type of the variable for which a history read request was triggered.

This DPE is only set if either method NodeId or BrowsePath was defined in the parameters.

The historical values returned for the read request.

This DPE is only set if either method NodeId or BrowsePath was defined in the parameters.

The source timestamps in local time returned for the history read request.

This DPE is only set if either method NodeId or BrowsePath was defined in the parameters.

The server timestamps in local time returned for the history read request.

This DPE is only set if either method NodeId or BrowsePath was defined in the parameters.

The OPC UA value status codes returned for the history read request.

This DPE is only set if either method NodeId or BrowsePath was defined in the parameters.

Specifies the server URL. This defines how the server can be reached. An example for the format is:

opc.tcp://localhost:4841

Each bit (0-based counting) allows additional settings for the OPC UA Client.

bit 3

Setting the bit (=1) will delay the creation of subscriptions within the client until the server returns the state "Running".

Warning: Please make sure, that the server supports the state "Running", otherwise no subscriptions will be created.

bit 8

Setting the bit (=1) allows the client to communicate with OPC UA server that do not support secure communication.

CAUTION: The setting must only be used if your plant provides a secure environment as it will lead to unencrypted transmissions of passwords between client and server.

bit 9

Setting the bit (=1) allows the client to communicate with an OPC UA server that does not provide a valid certificate.

CAUTION: This setting must only be used if the server cannot be updated with a valid certificate!

Contains the password for the access to the server. The password is displayed encoded.

The following security policies are possible:

• None (0)

• Basic128Rsa15 (2)

• Basic256 (3)

• Basic256Sha256 (4)

• Aes128Sha256RsaOaep (5)

• Aes256Sha256RsaPss (6)

The following message concepts are possible:

• None (0)

• Sign (1)

• Sign&Encrypt (2)

Certificate which should be used by the client for connection establishment (example: myCertificate.der).

If this field is empty, the client uses "WinCC_OA_UA_Client.der".

Specifies the mapping of the OPC UA status codes to WinCC OA user bits.

The mapping is specified in a dyn_string. The dyn_string contains entries in the following form:

<UA status code><space><user bit number>

Whereas one user bit on the right side can be used multiple times:

For example:

0x00000000 1
0x80280000 2
0x80300000 2
2150891520 32

Allows defining OPC UA status filters for incoming data values. This means that values from the OPC UA server are filtered and discarded based on the UPC UA status.

It is possible to specify several status filters.

A subscription is always uniquely assigned to a server. A server can have multiple subscriptions. In this internal data point element the corresponding subscriptions are stored in the format:

<systemName>:_<subscriptionName>

Defines which timestamp is applied when using method 3 (writing historical data to _archive config of the appropriate data point element). The following values can be set:

• 0 (default) - Timestamp of the subscription of the appropriate data point element. If no subscription is defined the source timestamp is used.

• 1 - Timestamp of the subscription of the appropriate data point element. If no subscription is defined the server timestamp is used.

Indicates the connection status to the server:

• Not connected (0)

• Connected (1)

Format:

Contains information of timeout errors. Possible values:

• 0 - no error
• 1 - error during read (actually not used)
• 2 - error during write

Triggers a general query on the server. The specified value indicates whether values, alarms or both are queried:

• values and alarms (0)

• values only (1)

• alarms only (2)

Historical read requests are triggered via this element. The following parameters must be specified.

Specifies the server URL of the redundant server. This defines how to connect the OPC UA server. An example of the format is:

opc.tcp://localhost:4841

Defines the behavior for historical requests in case of redundant OPC UA servers. The following values are possible:

• 0 - The HistoryRead request is sent to the first accessible server. This is the default behavior if a connection to an OPC UA server is configured.

• 1 - The HistoryRead request is sent to both redundant servers. The result of these two service requests is merged. For merging the historical data values the source timestamps are used. If the server does not provide source timestamps, the server timestamps of the history read results will be used.

Defines the input data source within a redundant server pair.

The allowed values are:

• 0 - take input data from both server (as it is up to now)
• 1 - take input data only form server 1
• 2 - take input data only from server 2
• 3 - take the input data from the server with higher service level

If a server is explicitly selected than the client does not use values of the other server, even if the connection to the selected server fails. In that case the application has to switch manually to the other server.

The option only affects input data. In any case, output values ​​are written to both servers.

Indicates the connection status to the redundant server.

• not connected (0)

• connected (1)

Indicates the start time of the redundant server. Format:

JJJJ.MM.TT HH:MM:SS:MMM

Contains information of timeout errors. Possible values:

• 0 ... no error
• 1 ... error during read (actually not used)
• 2 ... error during write

• Id - Id of the requests (assigned by the UI, used to match a reply with the request.)
• ServerName | S1
• StartNode | ns=1;s=SYSTEM
• Level | 0 (recursive), >0 (number of levels downwards)

Alarm type browsing is triggered via this datapoint element. The dyn_string contains only the ID from the UI (see Browse.GetBranch).

The function corresponds to Browse.GetBranchbut . ConditionType is always used as the start node, any number of levels down are used, and only nodes representing alarm types are returned.

View of the names up from the start node. The levels are separated with a separator that was defined in the server data point.

For example:

Folder?stringArray

View of the whole browsing path in the defined notation beginning at the node /0:Objects:

/1:AGENT/1:Objects/1:pUInt32

View of each NodeId per browsed node in the defined notation:

ns=1;s=AGENT.Objects.pUInt32

View of each NodeClass per browsed node:

• OpcUa_NodeClass_Unspecified

• OpcUa_NodeClass_Object

• OpcUa_NodeClass_Variable

• OpcUa_NodeClass_Method

• OpcUa_NodeClass_ObjectType

• OpcUa_NodeClass_VariableType

• OpcUa_NodeClass_ReferenceType

• OpcUa_NodeClass_DataType

• OpcUa_NodeClass_View

A bit mask indicating whether the current value of the Value Attribute is readable and writeable as well as whether the history of the value is readable and writeable.

This DPE can be used to specify a limit for notifications the server shall send as response to a Publish request. It can be used to reduce peaks of communication load, when buffered data are transmitted.

The value 0 means that the client does not specify a limit and the server will use the maximum number of notifications per publish.

The maximum values are server dependent, e.g. the WinCC OA OPC UA server has a maximum value of 65535

This value indicates with which priority the notifications of this subscription are sent by the server.

Value range: 0 - 255;

whereby 0 means no special priority and 255 the highest priority.

Defines whether this is a subscription on :

• Data (1)

• Events (2)

• Alarms & Conditions (3)

• undefined (0) - not selectable in the panel

Indicates which timestamp of the node should be used.

In WinCC OA the corresponding availability is defined by:

• Source (0)

• Server (1)

• Reserved (2)

• None (3) - OPC UA client passes timestamp.

Defines the trigger to which the filter applies:

• Status (0)

• Status, Value (1)

• Status, Value, Timestamp (2)

Defines the deadband type for value calculation:

• none (0)

• absolute (1)

• percent (2)

Internal identification number for every subscription. This is unique for each server.

• 0 = invalid

Returned MaxKeepAliveCount.

• 0 = invalid

Returned publishing interval in milliseconds.

• 0 = invalid

Trigger for the general query per subscription. This is triggered independent of the value.

Since a subscription can be either for values ​​or alarms, the value passed is irrelevant.