Search

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

22 result(s) for HistoryRead

OPC-10000-3 – OPC Unified Architecture - Part 3: Address Space Model

8.55 PermissionType

read the history associated with a Node . For Variables , this bit affects the HistoryRead bit of the UserAccessLevel Attribute . This Permission is only valid for Variables (for reading historical values
OPC-10000-4 – OPC Unified Architecture - Part 4: Services

5.11.3.1 Description

indicates a Node 's support for historical Events . The continuationPoint parameter in the HistoryRead is used to mark a point from which to continue the read if not all values
OPC-10000-4 – OPC Unified Architecture - Part 4: Services

5.11.3.2 Parameters

Parameters Table 50 defines the parameters for the Service . Table 50 - HistoryRead Service Parameters Name Type Description Request requestHeader RequestHeader Common request parameters (see 7.32 for RequestHeader definition). historyReadDetails Extensible ... historical information. A Client shall always use the continuation point returned by a HistoryRead response to free the resources for the continuation point in the Server . If the Client does
OPC-10000-4 – OPC Unified Architecture - Part 4: Services

6.5.8 Auditing for Attribute Service Set

failed. The additional parameters should include the details of the request. The Read and HistoryRead Services may generate audit entries and audit Events for failed Service invocations. These Services should
OPC-10000-4 – OPC Unified Architecture - Part 4: Services

7.9 ContinuationPoint

ContinuationPoint A ContinuationPoint is used to pause a Browse, QueryFirst or HistoryRead operation and allow it to be restarted later by calling BrowseNext, QueryNext or HistoryRead. Operations are paused when
OPC-10000-4 – OPC Unified Architecture - Part 4: Services

7.38.1 General

meaning only for StatusCodes returned as part of a data change Notification or the HistoryRead . StatusCodes used in other contexts shall always set this bit to zero ... meaning only for StatusCodes returned as part of a data change Notification or the HistoryRead . StatusCodes used in other contexts shall always set this bit to zero
OPC-10000-4 – OPC Unified Architecture - Part 4: Services

7.39 TimestampsToReturn

specifies the Timestamp Attributes to be transmitted for MonitoredItems or Nodes in Read and HistoryRead . The values of this parameter are defined in Table 180 . Table 180 - TimestampsToReturn values Name ... default value for MonitoredItems if a Variable value is not being accessed. For HistoryRead this is not a valid setting. INVALID 4 No value specified
OPC-10000-11 – OPC Unified Architecture - Part 11: Historical Access

4.6 Bounding Values and time domain

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 ... they affect the time domain that is requested as part of the HistoryRead request is further explained in 4.4. Subclause 4.4 also provides examples of TimeDomains to further illustrate
OPC-10000-11 – OPC Unified Architecture - Part 11: Historical Access

4.7 Changes in AddressSpace over time

nodes that are currently collecting historical data. They shall also set the AccessLevel HistoryRead and optionally the HistoryWrite bits for HistoricalNodes (those with Historical data). If a HistoricalConfiguration Object
OPC-10000-11 – OPC Unified Architecture - Part 11: Historical Access

5.1.2 Annotations Property

Annotations whether or not Annotations currently exist. Annotation data is accessed using the standard HistoryRead functions. Annotations are modified, inserted or deleted using the standard HistoryUpdate functions and the UpdateStructuredDataDetails ... manners. It can be accessed via ReadAnnotationDataDetails or ReadRawModifiedDetails structure in the HistoryRead service. The ReadAnnotationDataDetails is described in 6.5.6 . The ReadAnnotationDataDetails contains an element reqTimes that is a list
OPC-10000-11 – OPC Unified Architecture - Part 11: Historical Access

5.4.4 HistoricalEventNode Attributes

following Attributes are particularly important for a HistoricalEventNode: EventNotifier OptionSet bits: HistoryRead 2 Indicates if the history of the Events is readable. (0 means not readable, 1 means readable). HistoryWrite
OPC-10000-11 – OPC Unified Architecture - Part 11: Historical Access

6.1 General

Browse Service Set or Query Service Set to detect HistoricalNodes and their configuration. The HistoryRead and HistoryUpdate Services of the Attribute Service Set to read and update history of HistoricalDataNodes ... HistoryRead service has the following parameters (see OPC 10000-4 for details): historyReadDetails timestampsToReturn releaseContinuationPoints nodesToRead [] nodeId indexRange dataEncoding continuationPoint The HistoryReadDetails is an extensible parameter that
OPC-10000-11 – OPC Unified Architecture - Part 11: Historical Access

6.3 Continuation Points

Continuation Points The continuationPoint parameter in the HistoryRead Service is used to mark a point from which to continue the history read if not all values could be returned ... other internal constraints. It can also be required to return a ContinuationPoint due to HistoryRead parameter constraints. If a request is taking a long time to calculate and is approaching
OPC-10000-11 – OPC Unified Architecture - Part 11: Historical Access

6.5.1 Overview

Overview The HistoryRead Service defined in OPC 10000-4 can perform several different functions. The HistoryReadDetails parameter is an Extensible Parameter that specifies which function to perform and the details ... example, text such as 'using the Read modified functionality' refers to the function the HistoryRead Service performs using the Extensible Parameter structure ReadRawModifiedDetails with the isReadModified Boolean parameter
OPC-10000-11 – OPC Unified Architecture - Part 11: Historical Access

6.6.1 Overview

Overview The HistoryRead Service returns different types of data depending on whether the request asked for the value Attribute of a Node or the history Events of a Node
OPC-10000-11 – OPC Unified Architecture - Part 11: Historical Access

6.6.2 HistoryData type

defines the structure of the HistoryData used for the data to return in a HistoryRead . Table 47 - HistoryData structure Name Type Description HistoryData Structure This structured datatype is a subtype
OPC-10000-11 – OPC Unified Architecture - Part 11: Historical Access

6.6.3 HistoryModifiedData type

defines the structure of the HistoryModifiedData used for the data to return in a HistoryRead when IsReadModified = True. This DataType is a subtype of HistoryData. Table 49 - HistoryModifiedData structure Name
OPC-10000-11 – OPC Unified Architecture - Part 11: Historical Access

6.6.6 Annotation DataType

defines the structure of the Annotation used for the data to return in a HistoryRead . This DataType describes Annotation structure information for the history data items. Its elements are defined
OPC-10000-13 – OPC Unified Architecture - Part 13: Aggregates

5.2.1 Overview

Overview The HistoryRead service defined in OPC 10000-4 can perform several different functions. The historyReadDetails parameter is an Extensible Parameter that specifies which function to perform. The ReadProcessedDetails structure
OPC-10000-13 – OPC Unified Architecture - Part 13: Aggregates

5.4.3.1 General

General When accessing aggregated data using the HistoryRead or the CreateMonitoredItems Service , the following rules are used to handle specific Aggregate use cases. If ProcessingInterva l is 0, the Server
OPC-10000-110 – OPC Unified Architecture - Part 110: Asset Management Basics

9.6 Tracking of health information

tracked, the Historizing Attribute is set to True and the AccessLevel is set to HistoryRead . In order to provide the information, when history tracking started, a HistoryDataConfiguration is referenced with
OPC-40083 – OPC UA for Plastics and Rubber Machinery - General Type Definitions

6.3 EventNotifier

specific interface (e.g. IMM_MES_Interface for OPC 40077) shall set the HistoryRead flag in the EventNotifier attribute