Search

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

26 result(s) for ExpandedNodeId

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

7.16 ExpandedNodeId

ExpandedNodeId The components of this parameter are defined in Table 137 . ExpandedNodeId allows the namespace to be specified explicitly as a string or with an index in the Server ... namespace table. Table 137 - ExpandedNodeId Name Type Description ExpandedNodeId structure The NodeId with the namespace expanded to its string representation. serverIndex Index Index that identifies the Server that contains
OPC-10000-5 – OPC Unified Architecture - Part 5: Information Model

12.3.9 ExpandedNodeId

ExpandedNodeId The representation in the AddressSpace of the ExpandedNodeId DataType is defined in Table 218 . Table 218 - ExpandedNodeId definition Attributes Value BrowseName ExpandedNodeId IsAbstract FALSE References NodeClass BrowseName DataType TypeDefinition
OPC-10000-4 – OPC Unified Architecture - Part 4: Services

5.8.2.2 Parameters

This structure is defined in-line with the following indented items. parentNodeId Expanded NodeId ExpandedNodeId of the parent Node for the Reference . The ExpandedNodeId type is defined
OPC-10000-4 – OPC Unified Architecture - Part 4: Services

5.8.3.2 Parameters

serverIndex in the targetNodeId . targetNodeId Expanded NodeId Expanded NodeId of the TargetNode . The ExpandedNodeId type is defined in 7.16 . If the server Index indicates that the TargetNode is a remote
OPC-10000-4 – OPC Unified Architecture - Part 4: Services

7.7.3 FilterOperator

operands: [0]: Any operand. [1]: Any operand that resolves to a NodeId or ExpandedNodeId where the Node is of the NodeClass DataType . If there is any error in conversion ... restrictions apply to the operands: [0]: Any operand that resolves to a NodeId or ExpandedNodeId that identifies an ObjectType or VariableType Node or a reference to another element which
OPC-10000-4 – OPC Unified Architecture - Part 4: Services

7.29 ReferenceDescription

TargetNode as assigned by the Server identified by the Server index. The ExpandedNodeId type is defined in 7.16 . If the server Index indicates that the TargetNode is a remote Node ... nodeId shall contain the namespace index. 1) If the Server index in the ExpandedNodeId indicates that the TargetNode is a remote Node , then the browseName , nodeClass and typeDefinition
OPC-10000-4 – OPC Unified Architecture - Part 4: Services

B.3.1 Overview

Attribute of a Property associated with a Node . In the examples character names of ExpandedNodeId are used instead of an actual ExpandedNodeId , this also applies to Attribute Ids. The string
OPC-10000-4 – OPC Unified Architecture - Part 4: Services

B.3.3 Example Notes

listed in its symbolic form, in the actual call it would be the ExpandedNodeId assigned to the Node . The Attribute is the symbolic name of the Attribute , in the actual
OPC-10000-4 – OPC Unified Architecture - Part 4: Services

B.3.9 Example 6

PigType, HasPet, HasFarmAnimal identifiers used in the above table would be translated to actual ExpandedNodeId
OPC-10000-5 – OPC Unified Architecture - Part 5: Information Model

6.4.37 AuditClientUpdateMethodResultEventType

which means it inherits the InstanceDeclarations of that Node. HasProperty Variable ObjectId ExpandedNodeId PropertyType Mandatory HasProperty Variable MethodId ExpandedNodeId PropertyType Mandatory HasProperty Variable StatusCodeId StatusCode PropertyType Mandatory HasProperty Variable InputArguments ... Method called. ObjectId identifies the Object on which the Method was called. The ExpandedNodeId shall use a namespaceUri , the serverIndex shall be set to 0 and the serverIndex shall
OPC-10000-6 – OPC Unified Architecture - Part 6: Mappings

5.1.12 QualifiedName, NodeId and ExpandedNodeId String Encoding

QualifiedName, NodeId and ExpandedNodeId String Encoding QualifiedNames , NodeIds and ExpandedNodeIds optimize representation of NamespaceUris by using a NamespaceIndex to reference the location of the URI in a NamespaceTable . The NamespaceTable ... acme.com,2023:schemas:data#off%3B;b=M/RbKBsRVkePCePcx24oRA== The description for a ExpandedNodeId is found in Table 6 . Table 6 - Description for a ExpandedNodeId <expanded-node
OPC-10000-6 – OPC Unified Architecture - Part 6: Mappings

5.2.2.9 NodeId

Guid value. ByteString 0x05 An opaque (ByteString) value. NamespaceUri Flag 0x80 See discussion of ExpandedNodeId in 5.2.2.10 . ServerIndex Flag 0x40 See discussion of ExpandedNodeId in 5.2.2.10 . The standard NodeId DataEncoding
OPC-10000-6 – OPC Unified Architecture - Part 6: Mappings

5.2.2.10 ExpandedNodeId

ExpandedNodeId An ExpandedNodeId extends the NodeId structure by allowing the NamespaceUri to be explicitly specified instead of using the NamespaceIndex . The NamespaceUri is optional. If it is specified, then ... NamespaceIndex inside the NodeId shall be ignored. The ExpandedNodeId is encoded by first encoding a NodeId as described in 5.2.2.9 and then encoding NamespaceUri as a String . An instance
OPC-10000-6 – OPC Unified Architecture - Part 6: Mappings

5.3.1.11 ExpandedNodeId

ExpandedNodeId An ExpandedNodeId value is encoded as an xs:string with the syntax defined in 5.1.12 . The XML schema for an ExpandedNodeId is: <xs:complexType name="ExpandedNodeId
OPC-10000-6 – OPC Unified Architecture - Part 6: Mappings

5.4.2.11 ExpandedNodeId

ExpandedNodeId ExpandedNodeId values shall be encoded as a JSON string using the format defined in 5.1.12 . The NodeId portion of the ExpandedNodeId uses the rules from 5.4.2.10 . ExpandedNodeIds with ... cannot be created the NamespaceUri is stored in the NamespaceUri field of the ExpandedNodeId
OPC-10000-6 – OPC Unified Architecture - Part 6: Mappings

F.4 Reference

serialized as a String . The syntax of the serialized String is defined in 5.3.1.11 ( ExpandedNodeId ). This value can be replaced by an Alias . ReferenceType NodeId The NodeId of the ReferenceType
OPC-10000-6 – OPC Unified Architecture - Part 6: Mappings

H.3 ExpandedNodeId

ExpandedNodeId ExpandedNodeId values shall be encoded as a JSON object with the fields defined in Table H.2 . Decoders that support the deprecated encodings use the JSON datatype to detect which ... object means it is the deprecated encoding. Table H.2 - JSON Object Definition for an ExpandedNodeId Name Description IdType The IdentifierType encoded as a JSON number. Allowed values are: 0 - UInt32
OPC-10000-12 – OPC Unified Architecture - Part 12: Discovery and Global Services

A.2 Resolving References to Remote Servers

Nodes that exist in different Server AddressSpace spaces. These references are specified with a ExpandedNodeId that includes the URI of the Server which owns the Node . A Client that wishes
OPC-10000-14 – OPC Unified Architecture - Part 14: PubSub

7.2.4.5.11 RawData field encoding

DataSet fields and Structure fields shall not have the builtInType NodeId , ExpandedNodeId , QualifiedName , LocalizedText , XmlElement, DiagnosticInfo or DataValue . RawField encoding shall only be applied to Data Key Frame DataSetMessages . Structure
OPC-10000-17 – OPC Unified Architecture - Part 17: Alias Names

6.3.4 AddAliasesToCategory Method

below, the arguments are defined in Table 9 . Signature AddAliasesToCategory( [in] String[] AliasNames, [in] ExpandedNodeId[] TargetNodes, [in] String[] TargetServers, [in] NodeId TargetReferenceType, [out] StatusCode[] ErrorCodes ); Table 9 - AddAliasesToCategory Method Arguments ... exist on the Server that contains the AliasName node). The ServerIndex in the ExpandedNodeId shall be ignored and the TargetServers Uri shall be used. TargetServers An array of the ServerUri
OPC-10000-17 – OPC Unified Architecture - Part 17: Alias Names

7.2 AliasNameDataType

AliasNameDataType This DataType defines a structure that can contain an array of ExpandedNodeId for a single AliasName . Its elements are defined in Table 17 . It will always have at least ... Name Type Description AliasNameDataType Structure AliasName QualifiedName The AliasName ( BrowseName of the Node ). ReferencedNodes ExpandedNodeId[] The Nodes referenced by the AliasName . Its representation in the AddressSpace is defined in Table
OPC-10000-17 – OPC Unified Architecture - Part 17: Alias Names

7.3 AliasNameVerboseDataType

AliasNameVerboseDataType This DataType defines a structure that can contain an array of ExpandedNodeId for a single AliasName . Its elements are defined in Table 19 . It will always have at least ... Name Type Description AliasNameVerboseDataType Structure AliasName QualifiedName The AliasName ( BrowseName of the Node ). ReferencedNodes ExpandedNodeId[] The Nodes referenced by the AliasName . ServerUris String[] The ServerUri associated with each
OPC-10000-17 – OPC Unified Architecture - Part 17: Alias Names

A.5 Client use of an AliasName Server

aggregating Server , the Client reads the ServerArray to resolve which Server the ExpandedNodeId was referencing. This is the last piece of information that a Client requires to be able
OPC-10000-17 – OPC Unified Architecture - Part 17: Alias Names

C.1 Overview

that have identical Name part of the BrowseNames . The GDS will provide the ExpandedNodeId of all of the referenced NodeIds and the ServerUri of the Server containing the NodeId
OPC-10000-81 – OPC Unified Architecture - Part 81: UAFX Connecting Devices and Information Model

5.7 AliasNames and OPC UA FX

Figure 15 ). These names can be grouped into categories. The FindAlias method returns the ExpandedNodeId for the actual Object / Variable / Method . AliasNames are most commonly used for configuration management
OPC-10000-83 – OPC Unified Architecture - Part 83: UAFX OfflineEngineering

A.3.7.4 ExpandedNodeId data type

A.3.7.4 ExpandedNodeId data type ExpandedNodeId - ExpandedNodeId has the same definition as NodeId since NodeId can already express an ExpandedNodeId as well