Search

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

33 result(s) for Structures

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

5.2.9 RolePermissions

access to the Node . The value of the Attribute is an array of RolePermissionType Structures (see Table 8 ). Table 8 - RolePermissionType Name Type Description RolePermissionType Structure Specifies the Permissions
OPC-10000-3 – OPC Unified Architecture - Part 3: Address Space Model

5.2.10 UserRolePermissions

granted to current Session . The value of the Attribute is an array of RolePermissionType Structures (see Table 8 ). Clients may determine their effective Permissions by performing a logical
OPC-10000-3 – OPC Unified Architecture - Part 3: Address Space Model

8.32 Structure

base DataType for all Structured DataTypes like Argument defined in 8.6 . While abstract Structures may be defined with no fields a non-abstract Structure shall have one or more fields
OPC-10000-3 – OPC Unified Architecture - Part 3: Address Space Model

8.48 StructureDefinition

default DataTypeEncoding for the DataType . If the DataType is only used inside nested Structures and is not directly contained in an ExtensionObject , the DefaultEncodingId is allowed to be null ... structure has a sequential layout. The StructureField DataType is defined in 8.51 . For Structures derived from another Structure DataType this list shall begin with the fields of the baseDataType followed
OPC-10000-4 – OPC Unified Architecture - Part 4: Services

7.1 AdditionalParametersType

name to be used in different contexts. The value is a Variant which allows Structures to be passed in addition to basic types such as Strings. Note that the calls
OPC-10000-5 – OPC Unified Architecture - Part 5: Information Model

12.31 DataTypeSchemaHeader

Union DataTypes used in the data that follows the DataTypeSchemaHeader . This includes nested Structures . DataType NodeIds for Structure DataTypes used in the data refer to entries in this array
OPC-10000-6 – OPC Unified Architecture - Part 6: Mappings

5.1.7 Structures and Unions

Structures and Unions Structures are sequences of name value pairs defined by the DataTypeDefinition Attribute in OPC 10000-3 . Each DataEncoding describes how to use the DataTypeDefinition to serialize Structures
OPC-10000-6 – OPC Unified Architecture - Part 6: Mappings

5.1.15 Messages

Messages Messages are the top-level Structures exchanged between a Client and Server . A Message sent from a Client to a Server is a Request . A Message sent back
OPC-10000-6 – OPC Unified Architecture - Part 6: Mappings

5.2.6 Structures

Structures Structures are encoded as a sequence of fields in the order that they appear in the definition. The encoding for each field is determined by the built-in type ... structure shall be encoded. If optional fields exist in the Structure , then see 5.2.7 . Structures do not have a null value. If an encoder is written in a programming language
OPC-10000-6 – OPC Unified Architecture - Part 6: Mappings

5.2.7 Structures with optional fields

Structures with optional fields Structures with optional fields are encoded with an encoding mask preceding a sequence of fields in the order that they appear in the definition. The encoding
OPC-10000-6 – OPC Unified Architecture - Part 6: Mappings

5.2.9 Messages

Messages Messages are Structures encoded as sequence of bytes prefixed by the NodeId of for the OPC UA Binary DataTypeEncoding defined for the Message . Each OPC UA Service described
OPC-10000-6 – OPC Unified Architecture - Part 6: Mappings

5.3.6 Structures with optional fields

Structures with optional fields Structures with optional fields are encoded as a xs:complexType with all of the fields appearing as a sequence of xs:elements . The first element
OPC-10000-6 – OPC Unified Architecture - Part 6: Mappings

5.4.2.16 ExtensionObject

UaEncoding and UaBody fields are only used when UA Binary or UA XML encoded Structures are serialized. Only the fields in Table 40 are present if these fields are used ... data is encoded in the UaBody field. This field is omitted for JSON encoded Structures . UaBody A ByteString containing an UA Binary or UA XML encoded Structure. This field
OPC-10000-6 – OPC Unified Architecture - Part 6: Mappings

5.4.6 Structures

Structures Structures shall be encoded as JSON objects. Note that JSON objects are unordered sets of name-value pairs. The order specified by the DataTypeDefinition is not preserved when ... encoded using the rules shown in Table 45 . Table 45 - JSON Encoding Rules for Structures Field Value Compact Verbose NULL Omitted JSON null Default Value Omitted Default Value For example
OPC-10000-6 – OPC Unified Architecture - Part 6: Mappings

5.4.7 Structures with optional fields

Structures with optional fields Structures with optional fields shall be encoded as JSON objects as shown in Table 46 . Note that JSON objects are unordered sets of name-value pairs ... omitted because they have a default value. Table 46 - JSON Object Definition for a Structures with Optional Fields Name Description EncodingMask A bit mask indicating what fields are encoded
OPC-10000-6 – OPC Unified Architecture - Part 6: Mappings

F.10 TranslationType

translations. It only appears if the Value is a Structure or an array of Structures . Name String The name of the field. This uniquely identifies the field within the structure
OPC-10000-12 – OPC Unified Architecture - Part 12: Discovery and Global Services

6.5.10 QueryApplications

Servers that meet the specified filters. QueryApplications returns ApplicationDescriptions instead of the ServerOnNetwork Structures returned by QueryServers . This is more useful to some Clients because it matches the return type
OPC-10000-14 – OPC Unified Architecture - Part 14: PubSub

5.4.4 Configuration Tool

configure the Subscriber functionality in the device. The PubSubConfigurationDataType and the other configuration Structures defined in Clause 6 can be used to prepare an offline PubSub configuration that
OPC-10000-14 – OPC Unified Architecture - Part 14: PubSub

6.1 Overview

specific mechanisms. The parameter groupings in this clause define the parameters and also define Structures used to represent the parameters of the groupings. These Structures are used in the PubSub
OPC-10000-14 – OPC Unified Architecture - Part 14: PubSub

6.4.1.1.2 QosDataType structure

QosDataType structure This Structure DataType is an abstract base type for Structures with QoS related parameters. The QosDataType is formally defined in Table 119 . Table 119 - QosDataType structure Name Type
OPC-10000-14 – OPC Unified Architecture - Part 14: PubSub

6.4.1.1.3 TransmitQosDataType

TransmitQosDataType This Structure DataType is an abstract base type for Structures with transmit QoS related parameters. The TransmitQosDataType is formally defined in Table 121 . Table 121 - TransmitQosDataType structure Name Type
OPC-10000-14 – OPC Unified Architecture - Part 14: PubSub

6.4.1.1.5 ReceiveQosDataType

ReceiveQosDataType This Structure DataType is an abstract base type for Structures with receive QoS related parameters. The ReceiveQosDataType is formally defined in Table 125 . Table 125 - ReceiveQosDataType structure Name Type
OPC-10000-14 – OPC Unified Architecture - Part 14: PubSub

6.4.1.2.6 DatagramQos

DatagramQos parameter contains QoS related parameters for the PubSubConnection as array of QosDataType Structures . The abstract DataType is defined in 6.4.1.1.2 . The concrete subtypes are used to represent different
OPC-10000-14 – OPC Unified Architecture - Part 14: PubSub

6.4.1.3.6 DatagramQos

DatagramQos parameter contains QoS related parameters for the WriterGroup as array of TransmitQosDataType Structures . The abstract TransmitQosDataType is defined in 6.4.1.1.3 . The concrete subtypes are used to represent different
OPC-10000-14 – OPC Unified Architecture - Part 14: PubSub

6.4.1.6.3 DatagramQos

DatagramQos parameter contains the QoS related parameters for the DataSetReader as array of ReceiveQosDataType Structures . The abstract ReceiveQosDataType is defined in 6.4.1.1.5 . The concrete subtypes are used to represent different
OPC-10000-15 – OPC Unified Architecture - Part 15: Safety

6.2.3.4 ResponseSPDUDataType

placeholder DataType , see requirement RQ6.8). [RQ6.8] To avoid possible problems with empty Structures , the dummy Structure NonSafetyDataPlaceholder shall be used as DataType for OutNonSafetyData when no NonSafetyData is used
OPC-10000-25 – OPC Unified Architecture - Part 25: Object Serialization

3.1.6 SerializationFieldDataType

Node may be nested (this means it can contain fields which are Structures ) and contain the SerializationFieldDataType s of child Nodes . The SerializationFieldDataType s are Structure DataTypes created
OPC-10000-25 – OPC Unified Architecture - Part 25: Object Serialization

6.3.3 ConfigureSerialization Method

Int32[] Results ); Table 3 - ConfigureSerialization Method arguments Argument Description SerializationFilterProperties Array of KeyValuePair Structures containing the desired settings. The key field of each Structure contains the BrowseName of a serialization
OPC-10000-81 – OPC Unified Architecture - Part 81: UAFX Connecting Devices and Information Model

F.1.2.4 Extensibility

Extensibility Structured DataTypes can only be extended by subtyping. This is a problem if Structures are embedded into other Structures , e.g., the ConnectionConfigurationSet -related Structure has an array of AutomationComponent ... related Structures . Therefore, each Structure has an additional field with an array of KeyValuePairs that can be used for potential future standardised or vendor-specific extensions
OPC-10000-81 – OPC Unified Architecture - Part 81: UAFX Connecting Devices and Information Model

F.1.2.5 Optional fields

F.1.2.5 Optional fields Connection configuration and communication flow-related configuration Structures use Structures with optional fields to handle the optional Variables . In other configuration Structures , AllowSubtypes is needed. Since AllowSubtypes
OPC-10000-83 – OPC Unified Architecture - Part 83: UAFX OfflineEngineering

A.3.3 Structures

A.3.3 Structures OPC UA Structures are defined as AML AttributeTypes. Structures in OPC UA can be derived from other Structures and composed of any other OPC UA DataTypes . Similarly ... AttributeTypes and composed of any other AttributeTypes. This allows all OPC UA DataTypes (including Structures ) to appear as AML AttributeTypes with the same derivation and composition structure as seen
OPC-10000-100 – OPC Unified Architecture - Part 100: Devices

3.3.1.4 Additional Attribute values

fields in the DataTypeDefinition . If the value is an array of non- Structures then a sequence of values is entered where each value is followed by a newline ... value is an array of Structures or a Structure with fields that are arrays or with nested Structures then the complete JSON array or JSON object is entered. There
OPC-10000-211 – OPC Unified Architecture - Part 211: Global Positioning

3.4.4 Structures

Structures OPC 10000-3 differentiates between different kinds of Structures . The following conventions explain, how these Structures shall be defined. The first kind are Structures without optional fields where none ... subtype (except fields with abstract DataTypes ). Its definition is in Table 12 . Table 12 - Structures without optional fields where none of the fields allow subtypes Name Type Description <someStructure