Search

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

12 result(s) for Identifier

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

8.2.4 Identifier value

Identifier value The Identifier value element is used within the context of the first three elements to identify the Node . Its data type and format is defined by the IdType ... Identifier values of IdType String are restricted to 4096 characters and shall not contain Unicode control characters. Unicode control characters are defined by Unicode C0 and Unicode C1 . Identifier values
OPC-10000-6 – OPC Unified Architecture - Part 6: Mappings

5.2.2.9 NodeId

defined NodeIds. IdentifierType Enumeration The format and data type of the identifier. The value may be one of the following: NUMERIC - the value is an UInt32; STRING - the value ... value is a ByteString ; Value UInt32 or String or Guid or ByteString The identifier for a node in the address space of an OPC UA Server . The DataEncoding
OPC-10000-6 – OPC Unified Architecture - Part 6: Mappings

5.4.2.10 NodeId

string using the format defined in 5.1.12 . NodeIds in NamespaceIndex 0 use the <identifier> form. All other NodeIds use the <namespace-uri> form. The first abnormal ... decoder shall set the NamespaceIndex to 0, the IdType to String and the Identifier to the JSON string
OPC-10000-6 – OPC Unified Architecture - Part 6: Mappings

5.4.2.11 ExpandedNodeId

ServerIndex to 0, the NamespaceIndex to 0, the IdType to String and the Identifier to the JSON string. When the ServerIndex is 0, decoders shall replace a NamespaceUri with
OPC-10000-6 – OPC Unified Architecture - Part 6: Mappings

A.3 Numeric Node Ids

Each line in the CSV file has the following fields: <SymbolName>, <Identifier>, <NodeClass> Where the SymbolName is either the BrowseName of a Type Node ... BrowsePath for an Instance Node that appears in the specification and the Identifier is numeric value for the NodeId . Each SymbolName is unique within the CSV file. The BrowsePath
OPC-10000-6 – OPC Unified Architecture - Part 6: Mappings

H.3 ExpandedNodeId

Description IdType The IdentifierType encoded as a JSON number. Allowed values are: 0 - UInt32 Identifier encoded as a JSON number. 1 - A String Identifier encoded as a JSON string ... Guid Identifier encoded as described in 5.4.2.7 . 3 - A ByteString Identifier encoded as described in 5.4.2.8 . This field is omitted for UInt32 identifiers. Id The Identifier . The value
OPC-10000-14 – OPC Unified Architecture - Part 14: PubSub

9.1.3.7.4 PubSubConfigurationValueDataType

related PubSubConfiguration2DataType Structure. Name String The name of the referenced PubSub configuration element. Identifier BaseDataType The identifier value used for the referenced element in the PubSub NetworkMessages . The value ... PubSubConneciton , WriterGroup or DataSetWriter . The value is null otherwise. If ConfigurationElement references a PubSubConnection , Identifier will contain the value of the PublisherId . If ConfigurationElement references a WriterGroup , Identifier will contain
OPC-10000-24 – OPC Unified Architecture - Part 24: Scheduler

A.1 Namespace and Identifiers for the Scheduler Information Model

specified in a CSV file with the following syntax: <SymbolName>, <Identifier>, <NodeClass> Where the SymbolName is either the BrowseName of a Type Node ... BrowsePath for an Instance Node that appears in the specification and the Identifier is the numeric value for the NodeId . The BrowsePath for an Instance Node is constructed by appending
OPC-10000-210 – OPC Unified Architecture - Part 210: Relative Spatial Location

6.2.1 Overview

TypeDefinition Other Subtype of the BaseObjectType defined in OPC 10000-5. 0:HasProperty Variable Identifier 0:String 0:PropertyType M 0:HasComponent Variable WorldFrame 0:BaseDataType {Any} SpatialLocationType ... SpatialObjectsListType shall be used to add application specific identification. The mandatory Property Identifier shall be used to name the SpatialObjectsList . Annex C.3 describes different scenarios
OPC-10000-210 – OPC Unified Architecture - Part 210: Relative Spatial Location

9.1 Conformance Units

SpatialObjectType instance shall be of a discrete subtype of SpatialLocationType ( 7.2 ) Server RSL SpatialObject Identifier Supports the variable Identifier of SpatialObjectType ( 6.1 ). Server RSL SpatialObject AttachPoints Supports the folder AttachPoints
OPC-10000-210 – OPC Unified Architecture - Part 210: Relative Spatial Location

A.1 Namespace and identifiers for Relative Spatial Location Information Model

specified in a CSV file with the following syntax: <SymbolName>, <Identifier>, <NodeClass> Where the SymbolName is either the BrowseName of a Type Node ... BrowsePath for an Instance Node that appears in the specification and the Identifier is the numeric value for the NodeId . The BrowsePath for an Instance Node is constructed by appending
OPC-10000-210 – OPC Unified Architecture - Part 210: Relative Spatial Location

C.3 Example use of the Identifier Property in a multi-server scenario

Example use of the Identifier Property in a multi-server scenario For the use in multi-server scenarios with different servers it might be needed to identify all related SpatialObjectsLists ... bring them in relationship in a higher levelled SpatialObjectsList. For this the Property Identifier of a SpatialObjectsList can be instantiated as the Property Identifier of a SpatialObject contained