Search

Scope: Core (OPC-10000-*) All specs

24 result(s) for HistoricalDataNodes

OPC-10000-11 – OPC Unified Architecture - Part 11: Historical Access

3.1.4 HistoricalNode

series data or Events stored for this HistoricalNode . The term HistoricalNode refers to both HistoricalDataNodes and HistoricalEventNodes
OPC-10000-11 – OPC Unified Architecture - Part 11: Historical Access

3.1.5 HistoricalDataNode

information (open/closed, moving) dynamically changing system data (like stock quotes) diagnostic data The term HistoricalDataNodes is used when referencing aspects of the standard that apply to accessing historical data only
OPC-10000-11 – OPC Unified Architecture - Part 11: Historical Access

4.5 Timestamps

with invalid settings will be rejected with Bad_TimestampsToReturnInvalid (see OPC 10000-4 ). For HistoricalDataNodes , the SourceTimestamp is used to determine which historical data values are to be returned ... SourceTimestamp and ServerTimestamp . NEITHER This is not a valid setting for any HistoryRead accessing HistoricalDataNodes. Any reference to timestamps in this context throughout this document will represent either ServerTimestamp
OPC-10000-11 – OPC Unified Architecture - Part 11: Historical Access

4.7 Changes in AddressSpace over time

impact a Client's ability to access historical information. If the history for a HistoricalDataNodes is still required, but the HistoricalDataNodes is no longer historized, then the Object should
OPC-10000-11 – OPC Unified Architecture - Part 11: Historical Access

5.1.1 General

General The Historical Access model defines additional Properties that are applicable for both HistoricalDataNodes and HistoricalEventNodes
OPC-10000-11 – OPC Unified Architecture - Part 11: Historical Access

5.2.2 HistoricalDataConfigurationType

defined interval. The ExceptionDeviation Variable specifies the minimum amount that the data for the HistoricalDataNodes shall change in order for the change to be reported to the history database
OPC-10000-11 – OPC Unified Architecture - Part 11: Historical Access

5.6.2 HistoricalDataNodes Address Space Model

HistoricalDataNodes Address Space Model HistoricalDataNodes are always a part of other Nodes in the AddressSpace. They are never defined by themselves. A simple example of a container for HistoricalDataNodes would
OPC-10000-11 – OPC Unified Architecture - Part 11: Historical Access

5.7.2 HistoryServerCapabilitiesType

values. A value of True indicates the Server supports access to the history for HistoricalDataNodes , a value of False indicates the Server does not support access to the history ... HistoricalDataNodes . The default value is False. At least one of AccessHistoryDataCapability or AccessHistoryEventsCapability shall have a value of True for the Server to be a valid OPC UA Server supporting
OPC-10000-11 – OPC Unified Architecture - Part 11: Historical Access

5.7.3 Default configuration

nodes, the Historian shall expose a default instance under the Server Object. If HistoricalDataNodes exist without a referenced configuration, an Object with a BrowseName of " DefaultHAConfiguration " shall
OPC-10000-11 – OPC Unified Architecture - Part 11: Historical Access

6.2.1 Overview

defines additional codes and rules that apply to the StatusCode when used for HistoricalDataNodes . The general structure of the StatusCode is specified in OPC 10000-4 . It includes
OPC-10000-11 – OPC Unified Architecture - Part 11: Historical Access

6.5.2.4 Read modified functionality

modification from the history database for the specified time domain for one or more HistoricalDataNodes . If there are multiple replaced Events the Server shall return all of them. The updateType
OPC-10000-11 – OPC Unified Architecture - Part 11: Historical Access

6.5.3.2 Read raw functionality

timestamps from the history database for the specified time domain for one or more HistoricalDataNodes . This parameter is intended for use by a Client that wants the actual data saved
OPC-10000-11 – OPC Unified Architecture - Part 11: Historical Access

6.5.3.3 Read modified functionality

modification from the history database for the specified time domain for one or more HistoricalDataNodes . If there are multiple replaced values the Server shall return all of them. The updateType
OPC-10000-11 – OPC Unified Architecture - Part 11: Historical Access

6.5.4.2 Read processed functionality

data in the history database for the specified time domain for one or more HistoricalDataNodes . The time domain is divided into intervals of duration ProcessingInterval . The specified Aggregate Type
OPC-10000-11 – OPC Unified Architecture - Part 11: Historical Access

6.5.5.2 Read at time functionality

qualities from the history database for the specified timestamps for one or more HistoricalDataNodes . This function is intended to provide values to correlate with other values with a known timestamp
OPC-10000-11 – OPC Unified Architecture - Part 11: Historical Access

6.5.6.2 Read Annotation Data functionality

Annotation Data from the history database for the specified timestamps for one or more HistoricalDataNodes . It will return any annotation that is associated with the given HistoricalDataNodes . The ExtraData ... timestamps supplied in the request. If Annotation Data is not supported for a HistoricalDataNodes then the StatusCode shall be Bad_HistoryOperationUnsupported. The standard ContinuationPoint rules (see 6.3 ) apply
OPC-10000-11 – OPC Unified Architecture - Part 11: Historical Access

6.9.1 Overview

values into the history database at the specified timestamps for one or more HistoricalDataNodes The Variable 's value is represented by a composite value defined by the DataValue data type ... existing values into the history database at the specified timestamps for one or more HistoricalDataNodes . The Variable 's value is represented by a composite value defined by the DataValue data
OPC-10000-11 – OPC Unified Architecture - Part 11: Historical Access

6.9.2.2 Insert data functionality

inserts entries into the history database at the specified timestamps for one or more HistoricalDataNodes . If an entry exists at the specified timestamp, then the new entry shall
OPC-10000-11 – OPC Unified Architecture - Part 11: Historical Access

6.9.2.3 Replace data functionality

replaces entries in the history database at the specified timestamps for one or more HistoricalDataNodes . If no entry exists at the specified timestamp, then the new entry shall
OPC-10000-11 – OPC Unified Architecture - Part 11: Historical Access

6.9.2.4 Update data functionality

replaces entries in the history database for the specified timestamps for one or more HistoricalDataNodes . If the item has an entry at the specified timestamp, then the new entry will
OPC-10000-11 – OPC Unified Architecture - Part 11: Historical Access

6.9.5.2 Delete raw functionality

entries from the history database for the specified time domain for one or more HistoricalDataNodes . If no data is found in the time range for a particular HistoricalDataNode , then
OPC-10000-11 – OPC Unified Architecture - Part 11: Historical Access

6.9.5.3 Delete modified functionality

entries from the history database for the specified time domain for one or more HistoricalDataNodes . If no data is found in the time range for a particular HistoricalDataNode , then
OPC-10000-11 – OPC Unified Architecture - Part 11: Historical Access

6.9.6.2 Delete at time functionality

Annotations in the history database for the specified timestamps for one or more HistoricalDataNodes . This parameter is intended to be used to delete specific data from the history database
OPC-10000-13 – OPC Unified Architecture - Part 13: Aggregates

5.2.1 Overview

which function to perform. The ReadProcessedDetails structure is used to read aggregated data for HistoricalDataNodes . The CreateMonitoredItems Service allows specifying a filter for each MonitoredItem . The MonitoringFilter is an extensible