Search
8 result(s) for Bounding Values
-
OPC-10000-11 – OPC Unified Architecture - Part 11: Historical Access3.1.2 BoundingValuesBoundingValues values associated with the starting and ending time Note 1 to entry: BoundingValues are the values that are associated with the starting and ending time of a ProcessingInterval specified ... when reading from the historian. BoundingValues may be required by Clients to determine the starting and ending values when requesting RawData over a time range. If a RawData value exists
-
OPC-10000-13 – OPC Unified Architecture - Part 13: Aggregates3.1.7 bounding valuesbounding values values at the startTime and endTime needed for Aggregates to compute the result Note 1 to entry: If Raw data does not exist at the startTime and endTime ... value shall be estimated. There are two ways to determine Bounding Values for an interval. One way (called Interpolated Bounding Values ) uses the first non-Bad data points found before
-
OPC-10000-11 – OPC Unified Architecture - Part 11: Historical Access3.1.10 TimeDomainTimeDomain is not included in the TimeDomain . See the examples in 4.6 . BoundingValues effect the time domain as described in 4.6 . All timestamps which can legally be represented
-
OPC-10000-11 – OPC Unified Architecture - Part 11: Historical Accessaccessing 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 StartTime , EndTime ... least two of these three parameters: startTime, endTime and numValuesPerNode . What is returned when BoundingValues are requested varies according to which of these parameters are provided. For a Historian that
-
OPC-10000-13 – OPC Unified Architecture - Part 13: Aggregatesinterpolated bounding values bounding values determined by a calculation using the nearest Good value Note 1 to entry: Interpolated Bounding Values using SlopedInterpolation are calculated as follows ... search a time range which is at least the size of the ProcessingInterval. Interpolated Bounding Values using SlopedExtrapolation are calculated as follows: find the first non-Bad Raw value before
-
OPC-10000-13 – OPC Unified Architecture - Part 13: Aggregates3.1.9 simple bounding valuessimple bounding values bounding values determined by a calculation using the nearest value Note 1 to entry: Simple Bounding Values using SlopedInterpolation are calculated as follows: if any Raw value ... value after the timestamp is Bad or Uncertain the StatusCode is Uncertain_DataSubNormal . Simple Bounding Values using SteppedInterpolation are calculated as follows: if any Raw value exists at the timestamp
-
OPC-10000-13 – OPC Unified Architecture - Part 13: AggregatesMonitoredItem Aggregates and Bounding Values When calculating MonitoredItem Aggregates that require the use of Bounding Values , the bounds may not be known. The calculation is done in the same manner
-
OPC-10000-13 – OPC Unified Architecture - Part 13: Aggregates5.4.3.2.1 GeneralAggregate operates on raw values but can also return a Bounding Value then the Bounding Values are included in the count when computing the StatusCode . If an Aggregate does ... divided into regions of Good or Bad data. Creating these regions requires that the bounding values be calculated for each interval and the type of bounding value depends