Search

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

17 result(s) for ContinuationPoint

OPC-10000-4 – OPC Unified Architecture - Part 4: Services

5.9.3.2 Parameters

continue. Clients may mix continuation points from different Browse or BrowseNext responses. The ContinuationPoint type is described in 7.9 . Response responseHeader Response Header Common response parameters (see 7.33 for ResponseHeader
OPC-10000-4 – OPC Unified Architecture - Part 4: Services

5.11.3.1 Description

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

7.6 BrowseResult

Good if there are still references to return for the BrowseDescription . continuationPoint ContinuationPoint A Server defined opaque value that identifies the continuation point. The ContinuationPoint type is defined
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 ... this number of results but it may return fewer results. The Server allocates a ContinuationPoint if there are more results to return. Servers shall support at least one ContinuationPoint
OPC-10000-4 – OPC Unified Architecture - Part 4: Services

B.2.3 QueryFirst

empty if no Nodes or References met the nodeTypes criteria. In this case the continuationPoint parameter should be empty. The QueryDataSet type is defined in B.2.5 . continuationPoint ContinuationPoint Server -defined ... maximum continuation points have been reached the oldest continuation point should be reset. The ContinuationPoint type is described in 7.9 . parsingResults[] ParsingResult List of parsing results for QueryFirst . The size
OPC-10000-4 – OPC Unified Architecture - Part 4: Services

B.2.4 QueryNext

RequestHeader definition). releaseContinuationPoint Boolean A Boolean parameter with the following values: TRUE passed continuationPoint should be reset to free resources for the continuation point in the Server . FALSE passed continuationPoint ... TRUE all array parameters in the response should contain empty arrays. continuationPoint ContinuationPoint Server defined opaque value that represents the continuation point. The value of the continuation point was returned
OPC-10000-11 – OPC Unified Architecture - Part 11: Historical Access

6.1 General

parameters (see OPC 10000-4 for details): historyReadDetails timestampsToReturn releaseContinuationPoints nodesToRead [] nodeId indexRange dataEncoding continuationPoint The HistoryReadDetails is an extensible parameter that can be any of the parameters defined ... return parameter for the HistoryRead service has the following parameter: results [] statusCode continuationPoint historyData The historyData parameter is an extensible parameter that is defined in 6.6 . The other return parameters
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 ... This can reduce the need in the Server to store state information for the ContinuationPoint . The Client specifies the maximum number of results per operation in the request Message
OPC-10000-11 – OPC Unified Architecture - Part 11: Historical Access

6.5.2.2 Read Event functionality

time specified then the Server shall return the Good_NoData StatusCode . The standard ContinuationPoint rules (see 6.3 ) apply. In addition, the following ContinuationPoint rule applies to ReadEventDetails. If a startTime ... given Node , then only numValuesPerNode Events per Node are returned along with a ContinuationPoint . For an interval in which no data exists, the corresponding StatusCode shall be Good_NoData
OPC-10000-11 – OPC Unified Architecture - Part 11: Historical Access

6.5.2.4 Read modified functionality

time specified then the Server shall return the Good_NoData StatusCode . The standard ContinuationPoint rules (see 6.3 ) apply. In addition, the following ContinuationPoint rule applies to ReadEventDetails. If a startTime ... given Node , then only numValuesPerNode Events per Node are returned along with a ContinuationPoint . For an interval in which no Events exists, the corresponding StatusCode shall be Good_NoData
OPC-10000-11 – OPC Unified Architecture - Part 11: Historical Access

6.5.3.2 Read raw functionality

starting point and the requested number of values is returned. The standard ContinuationPoint rules (see 6.3 ) apply. In addition, the following ContinuationPoint rule applies to ReadRawModifiedDetails If a startTime , endTime ... given Node then only numValuesPerNode values per Node shall be returned along with a ContinuationPoint . It is specifically allowed for the startTime and the endTime to be identical. This allows
OPC-10000-11 – OPC Unified Architecture - Part 11: Historical Access

6.5.3.3 Read modified functionality

then it shall return ModifiedValues with the same timestamp in subsequent calls. The standard ContinuationPoint rules (see 6.3 ) apply. In addition, the following ContinuationPoint rule applies to ReadRawModifiedDetails . If more ... given Node then only numValuesPerNode values per Node are returned along with a ContinuationPoint . If a value has been modified multiple times then all values for the time are returned
OPC-10000-11 – OPC Unified Architecture - Part 11: Historical Access

6.5.4.2 Read processed functionality

intervals being requested in the two cases are not the same. The standard ContinuationPoint rules (see 6.3 ) apply. Refer to OPC 10000-13 for handling of Aggregate specific cases
OPC-10000-11 – OPC Unified Architecture - Part 11: Historical Access

6.5.5.2 Read at time functionality

values, then the Server will set the StatusCode InfoBits to be Interpolated. The standard ContinuationPoint rules (see 6.3 ) apply. If the requested TimestampsToReturn is not supported for a Node , then
OPC-10000-11 – OPC Unified Architecture - Part 11: Historical Access

6.5.6.2 Read Annotation Data functionality

supported for a HistoricalDataNodes then the StatusCode shall be Bad_HistoryOperationUnsupported. The standard ContinuationPoint rules (see 6.3 ) apply
OPC-10000-26 – Part 26: LogObject - Part 26: LogObject Model

5.3 GetRecords Method

request as if it was a new request. If the Client specifies a ContinuationPoint In that is no longer valid, then the Server shall return a Bad _ ContinuationPointInvalid error. Results
OPC-10000-26 – Part 26: LogObject - Part 26: LogObject Model

5.4 ReleaseContinuationPoint Method

ReleaseContinuationPoint Method This Method allows a Client to release a LogObject ContinuationPoint that was returned to it. The signature of the Method is described below, and the arguments are described