Search

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

23 result(s) for Values

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

3.1.7 DataVariable

DataVariable Variables that represent values of Objects , either directly or indirectly for complex Variables , where the Variables are always the TargetNode of a HasComponent Reference
OPC-10000-3 – OPC Unified Architecture - Part 3: Address Space Model

4.5.1 General

General Variables are used to represent values . Two types of Variables are defined, Properties and DataVariables . They differ in the kind of data that they represent and whether they
OPC-10000-4 – OPC Unified Architecture - Part 4: Services

B.2.5 QueryDataSet

Node description. typeDefinitionNode ExpandedNodeId The NodeId for the type definition for this Node description. values [] BaseDataType Values for the selected Attributes. The order of returned items matches the order ... were specified using a relative path from the selected instance's TypeDefinitionNode . If no values where found for a given requested item a null value is returned for that item
OPC-10000-6 – OPC Unified Architecture - Part 6: Mappings

5.1.9 Variant

StatusCode and table of strings. As a result, Variants cannot contain instances of DiagnosticInfo. Values of Attributes are always returned in instances of DataValues . Therefore, the DataType of an Attribute
OPC-10000-6 – OPC Unified Architecture - Part 6: Mappings

F.15 Example

used for any NodeId value in the document except for NodeIds that appear in Values of Variables or VariableTypes . <Aliases> <Alias Alias="HasComponent
OPC-10000-9 – OPC Unified Architecture - Part 9: Alarms & Conditions

5.8.2 AlarmConditionType

provided. In some systems, an Alarm may be calculated based on multiple Variables Values ; it is up to the system to determine which Variable's NodeId is used. SuppressedState , OutOfServiceState
OPC-10000-23 – OPC Unified Architecture - Part 23: Common ReferenceTypes

5.1 Overview

References are described by a ReferenceDescription , that is, the Variables SomeReferenceType1 and SomeReferenceType2. The Values of those Variables uniquely identify the References by providing SourceNode , TargetNode , ReferenceType and direction
OPC-10000-25 – OPC Unified Architecture - Part 25: Object Serialization

3.1.5 SerializationValue

SerializationValue the merged compact aggregation of the Values of all serialized Nodes belonging to the SerializationScope and is the Value of the SerializedData Variable
OPC-10000-25 – OPC Unified Architecture - Part 25: Object Serialization

3.1.8 SerializationProcess

SerializationProcess the mapping of the SerializationValue from and to the Values in the SerializationScope . Note 1 to entry: This can imply the creation or re-creation of the SerializationFieldDataType used
OPC-10000-25 – OPC Unified Architecture - Part 25: Object Serialization

4.1 Object Serialization Basic Concept

Basic Concept Object Serialization is understood in this specification as the aggregation of the Values of different Variables belonging to a subset of the Information Model ( SerializationScope ) into the Value ... SerializationValue) of a single Variable ( SerializedData ) . Clients gain access to all Values in the SerializationScope at once by accessing the SerializationValue
OPC-10000-25 – OPC Unified Architecture - Part 25: Object Serialization

4.4 SerializationScope and SerializationEntity

Value of the SerializedData Variable. The DataType of the SerializationValue maps all Values of the Variables in the SerializationScope (see Figure 3 ). The SerializationProperties are provided by the SerializationEntity ... referenced using certain ReferenceTypes , limiting the depth of the SerializationScope and settings which companion values like statusCodes shall be part of the SerializationFieldDataType of Variables is also possible
OPC-10000-25 – OPC Unified Architecture - Part 25: Object Serialization

4.5 General Features

preserved. Servers can provide different serializations by providing different SerializationEntities , e.g. for process values or for configuration data as shown in Figure 4 . Different SerializationScopes defined on the same data ... SerializationValue with NonatomicWrite flag set to 0, the update of the original Values in the SerializationScope is like a transaction. This means if update of one original Values fails
OPC-10000-25 – OPC Unified Architecture - Part 25: Object Serialization

5.1 Example Serialize RIO Channel Groups

shows a Channel Group containing two output channel Objects , a configuration Object and Process Values . Figure 4 - RIO Channel Group From the Clients' perspective, certain use cases when accessing ... subtrees are supported by the Server . A Client might be interested in the Process Values provided in the "Values" array and the associated Process Value Qualifiers
OPC-10000-25 – OPC Unified Architecture - Part 25: Object Serialization

6.1 Overview

Overview Object Serialization provides a consistent, compact representation of the Variable Values in the SerializationScope . Objects or Variables that are the root of such a serialization are called SerializationStartNodes ... this ObjectType. The DataType of the SerializedData Variable is the SerializationValue DataType mapping all Values in the SerializationScope . It is the serialization DataType of the SerializationStartNode . The Values themselves each
OPC-10000-25 – OPC Unified Architecture - Part 25: Object Serialization

6.3.7 CustomMetaDataProperties Property

DataSetMetaData (see OPC 10000-14 ). The field names from the structures containing the Values the semantic Properties belong to are qualified with the OPC UA Namespace . This allows the encoder ... CustomMetaDataProperties Property of the SerializedData Variable describes the semantic Properties for all Values mapped into the SerializationValue DataType of the SerializedData . It is used as Properties field of the FieldMetaData
OPC-10000-25 – OPC Unified Architecture - Part 25: Object Serialization

A.2 RIO Channel Group Configuration

this DataType is serialized by the JSON encoder. If the SerializationProperties have default values, the Properties of the ChannelGroupConfig Object (see OPC RIO) are mapped into fields of the SerializationValue ... JSON encoding of this structure only contains the field names as keys and the Values of the serialized fields as JSON literals when using VerboseEncoding
OPC-10000-25 – OPC Unified Architecture - Part 25: Object Serialization

A.3 RIO Channel Process Values

Channel Process Values Figure A.3 shows how Process Values (see OPC RIO) belonging to RioChannelType Objects are mapped into the SerializationValue DataType . The "SerializationEntity" referenced by the SerializationStartNode ... subtrees originating from the Channel Objects . The JSON snipped shows how the Values in the SerializationScope are serialized using VerboseEncoding (see OPC 10000-6 ) and RawData field encoding
OPC-10000-25 – OPC Unified Architecture - Part 25: Object Serialization

A.4 Energy Measurement Values

Energy Measurement Values Figure A.4 shows a SerializationScope configured to exclude the metadata Properties of the Objects and Variables reachable from the SerializationStartNode . The EnergyMeasurementType Object has a mandatory PeObjectNumber ... MeasurementValueType Variables (see OPC PE ) The SerializationValue DataType structure contains only fields for the Values of the MeasurementValueType Variables . The JSON snipped shows how the energy data in the SerializationScope
OPC-10000-25 – OPC Unified Architecture - Part 25: Object Serialization

A.7 Combining SerializationScopes

StatusCode of the "MeasurementX1", "MeasurementX2" and "MeasurementXn" Variable Values is never encoded into JSON. Figure A.7 - Combining Serialization Scopes
OPC-10000-81 – OPC Unified Architecture - Part 81: UAFX Connecting Devices and Information Model

E.4.7 PubSub DataSets

have a value that is returned in every message. The message only contains the values, so the Subscriber has to be aware of the order/mapping of Variables in the DataSet ... delta frame, which is very similar to Client Server communication, and only changed values are sent. In this type of DataSetMessage , an index and the value are packaged into
OPC-10000-100 – OPC Unified Architecture - Part 100: Devices

4.5.2 VendorNameplate Interface

manufacturer point of view. They can be used as part of the identification. The Values of these Properties are typically provided by the component vendor. The VendorNameplate Interface is illustrated
OPC-10000-100 – OPC Unified Architecture - Part 100: Devices

8.7.3 Package metadata

software package False PackageType 2:PackageType Type of the Software Package . Other values are reserved for future use. False SoftwareSubClass 0:String Name of the application (in case of SoftwareClass ... Identification functional group or its parent device or an application on that device… False Values[] 0:BaseDataType Comparison values (zero, one or more values depending on the comparison operator
OPC-10000-110 – OPC Unified Architecture - Part 110: Asset Management Basics

13.3.1 Overview

both information sources in sync, especially when the Property is writable. Servers may reject Values not represented by Objects or may extend the Locations hierarchy