IEC 62541-11-2015 pdf free download.OPC unified architecture – Part 11: Historical Access.
Service. Some Servers may not support historizing both Source Timestamp and
ServerTimestamp, but it is expected that all Servers will support historizing Source Timestamp
(see IEC 6254 1-7 for details on Server Profiles).
If a request s made requesting both ServerTimestamp and Source Timestamp and the Server is only collecting the Source Timestamp the Server shall return Bad TimestampsToReturnlnvalid.
For HistoricalEventNodes this parameter does not apply. This parameter is ignored since the entries returned are dictated by the Event Filter. See IEC 6254 1-4 for details,
4.4 Bounding Values and time domain
When accessing HistoricalDataNodes via the HistoryRead Service, requests can set a flag. returnBounds, indicating that BoundingValues are requested. For a complete description of the Extensible Parameter HistoryReadDetails that include Start Time, EndTime and NumValuesPerNode. see 6.4. The concept of Bounding Values and how they affect the time domain that is requested as part of the HistoryRead request is further explained in 4.4. 4.4 also provides examples of TimeDomains to further illustrate the expected behaviour.
When making a request for historical data using the HistoryRead Service, the required parameters include at least 2 of these three parameters: startTime, endTime and numValuesPerNode. What is returned when Bounding Values are requested varies according to which of these parameters are provided. For a historian that has values stored at 5:00, 5:02. 5:03. 5:05 and 5:06, the data returned when using the Read Raw functionality is given by Table 1. In the table, FIRST stands for a tuple with a value of null, a timestamp of the specified Start Time, and a StatusCode of Bad_BoundNotFound. LAST stands for a tuple with a value of null, a timestamp of the specified EndTime, and a StatusCode of Bad_ Bou,idNotFound
In some cases, attempting to locate bounds. particularly FIRST or LAST points, may be resource intensive for Servers. Therefore how far back or forward to look in history for Bounding Values is Server dependent, and the Server search limits may be reached be(ore a bounding value can be found. There are also cases, such as reading Annotations or Attribute data where Bounding Values may not be appropriate. For such use cases it is permissible for the Server to return a StatusCode of Bad_BoundNotSupported.IEC 62541-11 pdf download.