C++ Based OPC UA Client/Server/PubSub SDK  1.7.6.537
OpcUa_ReadEventDetails Struct Reference

Selects a set of events from the history database by specifying a filter and a time domain for one or more objects or views. More...

#include <opcua_types.h>

Public Attributes

OpcUa_UInt32 NumValuesPerNode
 The maximum number of values returned for any node over the time range. More...
 
OpcUa_DateTime StartTime
 The beginning of the period to read. More...
 
OpcUa_DateTime EndTime
 The end of the period to read. More...
 
OpcUa_EventFilter Filter
 A filter used by the Server to determine which HistoricalEventNode should be included. More...
 

Detailed Description

Selects a set of events from the history database by specifying a filter and a time domain for one or more objects or views.

The ReadEventDetails structure is used to read the events from the history database for the specified time domain for one or more HistoricalEventNodes. The events are filtered based on the filter structure provided. This filter includes the event fields that are to be returned.

The startTime and endTime are used to filter on the Time field for events.

The time domain of the request is defined by startTime, endTime, and numValuesPerNode; at least two of these must be specified. If endTime is less than startTime, or endTime and numValuesPerNode alone are specified, the data will be returned in reverse order with later/newer data provided first, as if time was flowing backward. If all three are specified, the call shall return up to numValuesPerNode results, going from startTime to endTime, in either ascending or descending order, depending on the relative values of startTime and endTime. If numValuesPerNode is 0, all of the values in the range are returned. The default value is used to indicate that startTime, endTime, or numValuesPerNode is not specified.

It is specifically allowed for the startTime and the endTime to be identical. This allows the Client to request the event at a single instance in time. If startTime and endTime are identical, time is presumed to be flowing forward. If no data exists at the time specified, the server must return the Good_NoData StatusCode.

If a startTime, endTime, and numValuesPerNode are all provided, and if more than numValuesPerNode events exist within that time range for a given node, then only numValuesPerNode events per node are returned along with a continuationPoint. When a continuationPoint is returned, a Client wanting the next numValuesPerNode values should call HistoryRead again with the continuationPoint.

For an interval in which no data exists, the corresponding StatusCode shall be Good_NoData.

The filter parameter is used to determine which historical events and their corresponding fields are returned. It is possible that the fields of an EventType are available for real time updating, but not available from the historian. In this case, a StatusCode value will be returned for any event field that cannot be returned. The value of the StatusCode must be Bad_NoData.

If the requested timestamp format is not supported for a node, the operation shall return the Bad_TimestampNotSupported StatusCode. When reading events, this only applies to Event fields that are of type DataValue.


The documentation for this struct was generated from the following file: