Search

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

28 result(s) for RawData

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

3.1.8 RawData

RawData data that is stored within the historian for a HistoricalDataNode Note 1 to entry: The data can be all data collected for the DataValue or it can be some
OPC-10000-1 – OPC Unified Architecture - Part 1: Overview and Concepts

2.1.2 Aggregate

Aggregate function that calculates derived values from Raw data Note 1 to entry: Raw data may be from a historian or buffered real time data. Common Aggregates include averages over
OPC-10000-11 – OPC Unified Architecture - Part 11: Historical Access

3.1.2 BoundingValues

required by Clients to determine the starting and ending values when requesting RawData over a time range. If a RawData value exists at the start or end point ... bounding value even though it is part of the data request. If no RawData value exists at the start or end point, then the Server will determine the boundary value
OPC-10000-11 – OPC Unified Architecture - Part 11: Historical Access

5.2.2 HistoricalDataConfigurationType

sloped line between points) or as SteppedInterpolation (vertically-connected horizontal lines between points) when RawData is examined. This Property also effects how some Aggregates are calculated. A value of True
OPC-10000-11 – OPC Unified Architecture - Part 11: Historical Access

5.7.2 HistoryServerCapabilitiesType

values capability. A value of True indicates the Server supports the capability to delete RawData values in history. The default value is False. The DeleteAtTimeCapability Variable indicates support
OPC-10000-11 – OPC Unified Architecture - Part 11: Historical Access

6.5.3.2 Read raw functionality

saved within the historian. The actual data can be compressed or can be all RawData collected for the item depending on the historian and the storage rules invoked when
OPC-10000-13 – OPC Unified Architecture - Part 13: Aggregates

3.1.7 bounding values

endTime needed for Aggregates to compute the result Note 1 to entry: If Raw data does not exist at the startTime and endTime a value shall be estimated. There ... Interpolated'. When calculating bounding values , the value portion of Raw data that has Bad status is set to null. This means the value portion is not used in any calculation
OPC-10000-13 – OPC Unified Architecture - Part 13: Aggregates

3.1.8 interpolated bounding values

values exist between the before value and the timestamp. If no non-Bad Raw data exists before the timestamp then the StatusCode is Bad_NoData. If the value before
OPC-10000-13 – OPC Unified Architecture - Part 13: Aggregates

5.3.3.1 General

aggregation). These bits are mutually exclusive. Table 47 - Data location StatusCode Description Raw A Raw data value. Calculated A data value which was calculated. Interpolated A data value which ... Extra Data If a Server chooses to set this bit, it indicates that a Raw data value supersedes other data at the same timestamp. Multiple Values Multiple values match
OPC-10000-13 – OPC Unified Architecture - Part 13: Aggregates

5.4.1 General

behaviour shall be similar to every other Aggregate's behaviour where input parameters, Raw data , and boundary conditions are similar. Where possible, the Aggregates should deal with input and preconditions
OPC-10000-13 – OPC Unified Architecture - Part 13: Aggregates

5.4.3.5 Average

Average Aggregate defined in Table 53 adds up the values of all Good Raw data for each interval, and divides the sum by the number of Good values ... Calculated Set Always Interpolated Not Set Raw Not Set Multi Value Not Set StatusCode Common Special Cases Before Start of Data Bad_NoData After End of Data Bad_NoData
OPC-10000-14 – OPC Unified Architecture - Part 14: PubSub

5.3.2 DataSetMessage field

DataSet field can be represented as a DataValue , as a Variant or as a RawData in the DataSetMessage field. The representation depends on the DataSetFieldContentMask defined ... value or bad status should be included in the DataSetMessage . The representation as RawData is the most efficient format and is used if a common status and timestamp per DataSet
OPC-10000-14 – OPC Unified Architecture - Part 14: PubSub

6.2.3.2.4 FieldMetaData

shall not be used in UADP message mapping if the field is represented as RawData set by the DataSetFieldContentMask defined in 6.2.4.2 . (2) Enumeration DataTypes are encoded as Int32 ... shall be used for UADP message mapping if the field is represented as RawData set by the DataSetFieldContentMask defined in 6.2.4.2 . ArrayDimensions UInt32[] This field specifies the maximum supported length
OPC-10000-14 – OPC Unified Architecture - Part 14: PubSub

6.2.4.2 DataSetFieldContentMask

Table 32 - DataSetFieldContentMask Values Value Bit No. Description DataSet fields can be represented as RawData, Variant or DataValue as described in 5.3.2 . If none of the bits ... fields are represented as Variant . If the RawData bit is set for UADP message mapping, the fields are represented as RawData and all other bits are ignored. For JSON message
OPC-10000-14 – OPC Unified Architecture - Part 14: PubSub

6.3.2.3.1 DataSetMessageContentMask

encoding. True True The JSON CompactEncoding is used for the DataSetMessage field encoding. The RawData bit of the DataSetFieldContentMask shall be ignored. False False The deprecated JSON NonReversibleEncoding is used ... DataSetMessage field encoding. The RawData bit of the DataSetFieldContentMask shall be ignored. True False The deprecated JSON ReversibleFieldEncoding is used for the DataSetMessage field encoding. The RawData
OPC-10000-14 – OPC Unified Architecture - Part 14: PubSub

7.2.4.5.5 Data Key Frame DataSetMessage

fields of the DataSet contained in the DataSetMessage . The FieldCount shall be omitted if RawData field encoding is set in the EncodingFlags defined in 7.2.4.5.4 . DataSetFields BaseDataType [FieldCount] The field
OPC-10000-14 – OPC Unified Architecture - Part 14: PubSub

7.2.4.5.11 RawData field encoding

RawData field encoding The encoding of the DataSetMessage fields is handled like a Structure DataType where the DataSet fields are handled like Structure fields and fields with Structure DataType ... maximum size indicated by ArrayDimensions or MaxStringLength . The padding only applies to RawData field encoding. All restrictions for the encoding of Structure DataTypes also apply to the RawData Field Encoding
OPC-10000-14 – OPC Unified Architecture - Part 14: PubSub

7.2.5.4.1 Message content

defined in Table 35 . For MessageType "ua-event", only Variant or RawData encoding shall be allowed. If bits for DataValue encoding are set, the Variant encoding shall ... omit the deprecated JSON encodings. If the DataSetFieldContentMask is 0x0 or 0x20 (only the RawData flag is set), the DataSetMessage fields are encoded as Variant . Otherwise the fields are encoded
OPC-10000-14 – OPC Unified Architecture - Part 14: PubSub

7.2.5.4.3 VerboseEncoding and abstract type handling

when a field of a nested Structure has DataType BaseDataType or AllowSubTypes =TRUE. If RawData =FALSE, then the Publisher always includes the full Variant with the UaType or ExtensionObject with ... when encoding these fields at the top level or within a nested Structure . If RawData =TRUE the Publisher will encode the Variant but not include the UaTypeId and UaType which
OPC-10000-14 – OPC Unified Architecture - Part 14: PubSub

7.2.5.6.2 ActionRequest

DataType of the field and the flags specified by the DataSetFieldContentMask. Only Variant or RawData encoding shall be allowed. If bits for DataValue encoding are set, the Variant encoding shall ... ActionRequest message. The DataValue encoding shall not be used in ActionRequest message. The RawData flag shall be FALSE for ActionRequest messages
OPC-10000-14 – OPC Unified Architecture - Part 14: PubSub

7.2.5.6.3 ActionResponse

DataType of the field and the flags specified by the DataSetFieldContentMask. Only Variant or RawData encoding shall be allowed. If bits for DataValue encoding are set, the Variant encoding shall ... ActionResponse message. The DataValue encoding shall not be used in ActionResponse message. The RawData flag shall be FALSE for ActionResponse messages
OPC-10000-14 – OPC Unified Architecture - Part 14: PubSub

A.2.1.7 Header layout for DataSetMessages

this header layout: DataSetFlags1 DataSetMessageSequenceNumber Status Additional restrictions: Fields within the payload use RawData Field Encoding Only data key frame DataSetMessages are supported The DataSetMessage header layout is shown ... Indicates whether this DataSetMessage is valid Bit range 1-2: Field Encoding 01 RawData Field Encoding Bit 3: DataSetMessageSequenceNumber enabled = 1 Bit 4: Status enabled Bit 5: ConfigurationVersionMajorVersion enabled
OPC-10000-14 – OPC Unified Architecture - Part 14: PubSub

A.2.1.8 Example fixed message layout without security

this example it is assumed that DataSetMessage[1] and DataSetMessage[W-1] are using RawData field encoding and all DataSet fields are from constant size, so the total length
OPC-10000-14 – OPC Unified Architecture - Part 14: PubSub

A.3.2.2 Overview

DataSetMessage header is not included The DataSet field encoding is set to VerboseEncoding with RawData
OPC-10000-25 – OPC Unified Architecture - Part 25: Object Serialization

A.2 RIO Channel Group Configuration

serialized fields as JSON literals when using VerboseEncoding (see OPC 10000-6 ) and RawData field encoding (see OPC 10000-14 ) in a PubSub scenario. The Enumeration Values are encoded
OPC-10000-25 – OPC Unified Architecture - Part 25: Object Serialization

A.3 RIO Channel Process Values

Values in the SerializationScope are serialized using VerboseEncoding (see OPC 10000-6 ) and RawData field encoding (see OPC 10000-14 ) in a PubSub scenario. In Figure A.3 the details
OPC-10000-25 – OPC Unified Architecture - Part 25: Object Serialization

A.4 Energy Measurement Values

energy data in the SerializationScope are serialized using VerboseEncoding (see OPC 10000-6 ) and RawData field encoding (see OPC 10000-14 ) in a PubSub scenario. Figure A.4 - PROFIenergy Energy Measurement
OPC-10000-25 – OPC Unified Architecture - Part 25: Object Serialization

A.7 Combining SerializationScopes

resulting SerializationValue structure DataType is serialized using VerboseEncoding (see OPC 10000-6 ) and RawData field encoding (see OPC 10000-14 ) in a PubSub scenario. If the StatusCode