Search

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

106 result(s) for NodeIds

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

4.6.1 General

Servers . Organizations may define TypeDefinitionNodes that are well-known in the industry. Well-known NodeIds of TypeDefinitionNodes provide for commonality across OPC UA Servers and allow Clients to interpret ... without having to read it from the Server . Therefore, Servers may use well-known NodeIds without representing the corresponding TypeDefinitionNodes in their AddressSpace . However, the TypeDefinitionNodes shall be provided
OPC-10000-3 – OPC Unified Architecture - Part 3: Address Space Model

4.9.2 Well Known Roles

Well Known Roles The NodeIds for the well-known Roles are defined in OPC 10000-6 . All Servers should support the well-known Roles which are defined in Table
OPC-10000-3 – OPC Unified Architecture - Part 3: Address Space Model

5.2.2 NodeId

unambiguously identified using a constructed identifier called the NodeId . Some Servers may accept alternative NodeIds in addition to the canonical NodeId represented in this Attribute . A Server shall persist
OPC-10000-3 – OPC Unified Architecture - Part 3: Address Space Model

5.2.4 BrowseName

name of a Node . The DisplayName should be used instead for this purpose. Unlike NodeIds , the BrowseName cannot be used to unambiguously identify a Node . Different Nodes may have
OPC-10000-3 – OPC Unified Architecture - Part 3: Address Space Model

5.8.1 DataType Model

identify the DataType and it's encoding as defined in OPC 10000-6 , those NodeIds may also be well-known for well-known DataTypeIds
OPC-10000-3 – OPC Unified Architecture - Part 3: Address Space Model

5.8.4 DataTypeEncoding and Encoding Information

used for the DataType . Since Clients identify the DataType via the DataTypeEncodings , also the NodeIds for the DataTypeEncodings of the DataType shall be changed, when the encoding changes
OPC-10000-3 – OPC Unified Architecture - Part 3: Address Space Model

6.2.9 NodeIds of InstanceDeclarations

NodeIds of InstanceDeclarations InstanceDeclarations are identified by their BrowsePath . Different Servers might use different NodeIds for the InstanceDeclarations of common TypeDefinitionNodes , unless the definition of the TypeDefinitionNode already defines ... NodeId for the InstanceDeclaration . All TypeDefinitionNodes defined in OPC 10000-5 already define the NodeIds for their InstanceDeclarations and therefore shall be used in all Servers
OPC-10000-3 – OPC Unified Architecture - Part 3: Address Space Model

8.2.3 IdType

Guid 2 Globally Unique Identifier Opaque 3 Namespace specific format Normally the scope of NodeIds is the Server in which they are defined. For certain types of NodeIds , NodeIds ... That is, Clients shall consider them case sensitive. Servers are allowed to provide alternative NodeIds (see 5.2.2 ) and using this mechanism Servers can handle NodeIds as case insensitive
OPC-10000-3 – OPC Unified Architecture - Part 3: Address Space Model

8.18 IdType

Table 23 . See 8.2.3 for a description of the use of this DataType in NodeIds
OPC-10000-4 – OPC Unified Architecture - Part 4: Services

5.8.2.2 Parameters

should be a numeric id. See OPC 10000-3 for a description of ReferenceType NodeIds . browseName QualifiedName The browse name of the Node to add. nodeClass NodeClass NodeClass
OPC-10000-4 – OPC Unified Architecture - Part 4: Services

5.9.4.1 Description

used to request that the Server translates one or more browse paths to NodeIds . Each browse path is constructed of a starting Node and a RelativePath . The specified starting Node ... multiple targets with the same BrowseName , the Server shall return a list of NodeIds . However, since one of the main purposes of this Service is to support programming against type
OPC-10000-4 – OPC Unified Architecture - Part 4: Services

5.9.4.2 Parameters

parameters (see 7.32 for RequestHeader definition). browsePaths [] BrowsePath List of browse paths for which NodeIds are being requested. This structure is defined in-line with the following indented items. startingNode
OPC-10000-4 – OPC Unified Architecture - Part 4: Services

5.9.5.1 Description

access operations will be more efficient. Clients can expect performance improvements when using registered NodeIds , but the optimization measures are vendor-specific. For Variable Nodes Servers shall concentrate their optimization ... efforts on the Value Attribute . Registered NodeIds are only guaranteed to be valid within the current Session . Clients shall unregister unneeded Ids immediately to free up resources. RegisterNodes does
OPC-10000-4 – OPC Unified Architecture - Part 4: Services

5.9.5.2 Parameters

Request Header Common request parameters (see 7.32 for RequestHeader definition). nodesToRegister [] NodeId List of NodeIds to register that the Client has retrieved through browsing, querying or in some other manner ... Header Common response parameters (see 7.33 for ResponseHeader definition). registeredNodeIds [] NodeId A list of NodeIds which the Client shall use for subsequent access operations. The size and order of this
OPC-10000-4 – OPC Unified Architecture - Part 4: Services

5.9.5.3 Service results

this result code. Servers shall completely reject the RegisterNodes request if any of the NodeIds in the nodesToRegister parameter are structurally invalid
OPC-10000-4 – OPC Unified Architecture - Part 4: Services

5.9.6.1 Description

Description This Service is used to unregister NodeIds that have been obtained via the RegisterNodes service. UnregisterNodes does not validate the NodeIds from the request. Servers shall simply unregister NodeIds ... that are known as registered NodeIds . Any NodeIds that are in the list, but are not registered NodeIds are simply ignored
OPC-10000-4 – OPC Unified Architecture - Part 4: Services

5.9.6.2 Parameters

Header Common request parameters (see 7.32 for RequestHeader definition). nodesToUnregister [] NodeId A list of NodeIds that have been obtained via the RegisterNodes service. Response responseHeader Response Header Common response parameters
OPC-10000-4 – OPC Unified Architecture - Part 4: Services

6.3.2 Parameters

empty arrays in the response. namespaceUris [] String A list of URIs referenced by NodeIds or QualifiedNames in the request. NamespaceIndex 0 shall not be in this list. The first entry ... Service request for the serviceId . Response namespaceUris [] String A list of URIs referenced by NodeIds or QualifiedNames in the response. NamespaceIndex 0 shall not be in this list. The first
OPC-10000-4 – OPC Unified Architecture - Part 4: Services

6.6.2.2 RedundantServerSet Requirements

RedundantServerSet . Servers in the RedundantServerSet shall have an identical AddressSpace including: identical NodeIds identical browse paths and structure of the AddressSpace identical logic for setting the ServiceLevel The only Nodes ... that fails over shall not be required to translate browse paths or otherwise resolve NodeIds . Servers are allowed to add and delete Nodes as long as all Servers
OPC-10000-4 – OPC Unified Architecture - Part 4: Services

7.7.3 FilterOperator

operand[2]. In this case, the referred to element returns a list of NodeIds instead of TRUE or FALSE. In this case if any errors occur
OPC-10000-5 – OPC Unified Architecture - Part 5: Information Model

4.1 NodeIds

NodeIds The NodeIds of all Nodes described in this standard are only symbolic names. OPC 10000-6 defines the actual NodeIds . The symbolic name of each Node defined in this ... InstanceDeclaration described above has the symbolic name "Server.ServerCapabilities.MinSupportedSampleRate". The NamespaceIndex for all NodeIds defined in this standard is 0. The namespace for this NamespaceIndex is specified
OPC-10000-5 – OPC Unified Architecture - Part 5: Information Model

6.3.1 ServerType

indexes into the namespace table are referred to as NamespaceIndexes . NamespaceIndexes are used in NodeIds in OPC UA Services , rather than the longer namespace URI. Index 0 is reserved ... indexes of the namespace table but only add entries, because the client may cache NodeIds using the indexes. Nevertheless, it might not always be possible for Servers to avoid changing
OPC-10000-5 – OPC Unified Architecture - Part 5: Information Model

6.3.13 NamespaceMetadataType

static Nodes . The StaticNumericNodeIdRange Property provides a list of NumericRanges used for numeric NodeIds of static Nodes . If the StaticNodeIdTypes Property contains an entry for numeric NodeIds then this Property ... defined for the Like Operator defined in OPC 10000-4 to filter for string NodeIds of static Nodes . If the StaticNodeIdTypes Property contains an entry for string NodeIds then this
OPC-10000-5 – OPC Unified Architecture - Part 5: Information Model

6.4.2 BaseEventType

using this Property for filtering, Clients have to specify all individual subtypes of BaseConditionClassType NodeIds . The OfType operator cannot be applied. BaseConditionClassType is used as class whenever an Event cannot ... this Property for filtering, Clients have to specify all individual sub types of BaseConditionClassType NodeIds . The OfType operator cannot be applied. The Client specifies a NULL in the filter
OPC-10000-5 – OPC Unified Architecture - Part 5: Information Model

12.31 DataTypeSchemaHeader

index into the array is referred to as NamespaceIndex . The NamespaceIndex is used in NodeIds and QualifiedNames , rather than the longer namespace URI. NamespaceIndex 0 is reserved ... 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. The StructureDescription
OPC-10000-5 – OPC Unified Architecture - Part 5: Information Model

A.2 ServerType and Server Object

Typically, each Server will provide one Server Object with a well-known NodeId . The NodeIds of the containing Nodes are also well-known because their symbolic name is specified
OPC-10000-6 – OPC Unified Architecture - Part 6: Mappings

5.1.8 ExtensionObject

Nodes of the AddressSpace . Elements of an array of ExtensionObjects can have different DataTypeEncoding NodeIds specified. In some cases, this will be invalid, however, it is the responsibility ... valid ExtensionObject as an array element. Server implementers should use namespace qualified numeric NodeIds for any DataTypeEncoding Objects they define. This will minimize the overhead introduced by packing Structured DataType
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 ... 4HEXDIG) "-" 12HEXDIG <opaqueid> = "b=" BASE64 NodeIds with a NamespaceIndex of 0 or a NamespaceUri of http://opcfoundation.org/UA/ shall only use the <identifier
OPC-10000-6 – OPC Unified Architecture - Part 6: Mappings

5.4.2.10 NodeId

values shall be encoded as a JSON string using the format defined in 5.1.12 . NodeIds in NamespaceIndex 0 use the <identifier> form. All other NodeIds
OPC-10000-6 – OPC Unified Architecture - Part 6: Mappings

A.3 Numeric Node Ids

Numeric Node Ids Clause A.3 defines the numeric identifiers for all of the numeric NodeIds defined by the OPC UA Specification. The identifiers are specified in a UTF8 encoded ... have the form: <DataTypeName>_Encoding_<BrowseName> The NamespaceUri for all NodeIds defined is http://opcfoundation.org/UA/ The CSV released with this version of the standards
OPC-10000-6 – OPC Unified Architecture - Part 6: Mappings

F.2 UANodeSet

BrowseName , DataType and ValueRank . The UANodeSet aliases are a list of string substitutions for NodeIds . UANodeSet aliases can be used to make the file more readable by allowing a string
OPC-10000-6 – OPC Unified Architecture - Part 6: Mappings

F.14 Variant

calls can be used to serialize Variant in this file syntax. Variants can contain NodeIds , ExpandedNodeIds and QualifiedNames which must be modified so the NamespaceIndexes and ServerIndexes reference the NamespaceUri ... which contain an EncodingId and a Structure with fields which with any DataType including NodeIds , ExpandedNodeIds or QualifiedNames . The NamespaceIndexes and ServerIndexes in these fields shall also reference the tables
OPC-10000-6 – OPC Unified Architecture - Part 6: Mappings

F.15 Example

Alias may be used for any NodeId value in the document except for NodeIds that appear in Values of Variables or VariableTypes . <Aliases> <Alias Alias="HasComponent ... references onto another OPC UA Server by adding a ServerIndex to TargetNode NodeIds . The structure of the DataType is defined by the Definition element. This information can be used
OPC-10000-9 – OPC Unified Architecture - Part 9: Alarms & Conditions

5.5.3 Condition and branch instances

representative ConditionId) follows the same rules associated with Nodes (and their representative NodeIds ) in the AddressSpace (see 10000-3 ). Therefore, once a Condition is created in a system that does
OPC-10000-11 – OPC Unified Architecture - Part 11: Historical Access

4.7 Changes in AddressSpace over time

that the AddressSpace of a Server will change over time (i.e. TypeDefinitions can change; NodeIds can be modified, added or deleted). Server developers and administrators need to be aware that
OPC-10000-12 – OPC Unified Architecture - Part 12: Discovery and Global Services

7.6 Pull Management Workflow

PullManagement workflow ApplicationId NodeId of the OPC UA Application in the CertificateManager . CertificateGroupIds NodeIds for each CertificateGroup in the CertificateManager that are relevant to the OPC UA Application . This includes
OPC-10000-12 – OPC Unified Architecture - Part 12: Discovery and Global Services

7.8.3.1 CertificateGroupType

TrustList Object is the TrustList associated with the CertificateGroup . The CertificateTypes Property specifies the NodeIds of the CertificateTypes which may be assigned to applications which belong to the CertificateGroup
OPC-10000-12 – OPC Unified Architecture - Part 12: Discovery and Global Services

7.9.2 CertificateDirectoryType

CertificateManager to specific applications are persisted by PullManagement Clients . These Clients use the NodeIds to relate their local configuration to the CertificateGroup in the CertificateManager . The StartSigningRequest Method is used ... Private Key (if requested) are returned . The GetCertificateGroups Method returns a list of NodeIds for CertificateGroupType Objects that can be used to request Certificates or TrustLists for an application
OPC-10000-12 – OPC Unified Architecture - Part 12: Discovery and Global Services

7.10.17 TransactionDiagnosticsType

CancelChanges Method was called the value is Bad_RequestCancelledByClient. The AffectedTrustLists Property specifies the NodeIds of the TrustLists that are included in the transaction. It is updated each time ... soon as a TrustList is added to the transaction. The AffectedCertificateGroups Property specifies the NodeIds of the CertificateGroups are included in the transaction. It is updated each time as soon
OPC-10000-12 – OPC Unified Architecture - Part 12: Discovery and Global Services

10.2 Handling of OPC UA Namespaces

identifiers. A Node in the UA AddressSpace is unambiguously identified using a NodeId . Unlike NodeIds , the BrowseName cannot be used to unambiguously identify a Node . Different Nodes may have ... namespace of the NodeId reflects something else, for example the EngineeringUnits Property . All NodeIds of Nodes not defined in this document shall not use the standard namespaces. Table 162 provides
OPC-10000-12 – OPC Unified Architecture - Part 12: Discovery and Global Services

B.2 Numeric Node Ids

defines Nodes which are only used by GlobalDiscoveryServers . The NamespaceUri for any GDS specific NodeIds is http://opcfoundation.org/UA/GDS / The CSV released with this version of the standards
OPC-10000-13 – OPC Unified Architecture - Part 13: Aggregates

5.2.2 ReadProcessedDetails structure overview

endTime End of period to read. processingInterval Interval between returned Aggregate values. aggregateType[] The NodeIds of the AggregateFunction Objects . AggregateFunction Objects indicate the list of Aggregates to be used when
OPC-10000-13 – OPC Unified Architecture - Part 13: Aggregates

5.2.3 AggregateFilter structure overview

AggregateFilter startTime Beginning of period to calculate the Aggregate the first time. aggregateType The NodeIds of the AggregateFunction Objects that indicates the list of Aggregates to be used when retrieving
OPC-10000-13 – OPC Unified Architecture - Part 13: Aggregates

5.3.2 Operation level result codes

AggregateListMismatch The requested number of Aggregates does not match the requested number of NodeIds . When multiple Aggregates are requested, a corresponding NodeId is required for each AggregateFunction . Bad_AggregateNotSupported
OPC-10000-14 – OPC Unified Architecture - Part 14: PubSub

5.4.5.1 General

Publisher or by a central SKS. In both cases, the well-known NodeIds for the PublishSubscribe Object and the related GetSecurityKeys Method are used to call the GetSecurityKeys Method
OPC-10000-14 – OPC Unified Architecture - Part 14: PubSub

6.2.3.2.2 DataTypeSchemaHeader

information model e.g. if the values are written to target Variables . This affects encoding NodeIds in ExtensionObjects but also all other namespace indices in NodeIds and BrowseNames contained ... Structure DataTypes where the target Variables DataTypes have the same structure but different DataType NodeIds , the Subscriber must verify the consistency of the layout at start-up and must
OPC-10000-14 – OPC Unified Architecture - Part 14: PubSub

6.2.9.4 DataSetMetaData

information model e.g. if the values are written to target Variables . This affects encoding NodeIds in ExtensionObjects but also all other namespace indices in NodeIds and BrowseNames contained ... Structure DataTypes where the target Variables DataTypes have the same structure but different DataType NodeIds , the Subscriber must verify the consistency of the layout at start-up and must
OPC-10000-14 – OPC Unified Architecture - Part 14: PubSub

6.2.12.1 PubSubConfigurationDataType

Values Namespaces String[] Namespace URIs for namespace indices used in the body. Examples are NodeIds contained in PublishedDataSets . The OPC UA namespace is skipped. The DataTypes used for configuration
OPC-10000-14 – OPC Unified Architecture - Part 14: PubSub

7.2.4.6.11 ActionMetaData announcement message

size and order of the ActionTargets. The namespace URIs for the NamespaceIdex in the NodeIds shall be contained in the Request DataSetMetaData
OPC-10000-14 – OPC Unified Architecture - Part 14: PubSub

8.3.2 GetSecurityKeys Method

Publisher or by a central SKS. In both cases, the well-known NodeIds for the PublishSubscribe Object and the related GetSecurityKeys Method are used to call the GetSecurityKeys Method
OPC-10000-14 – OPC Unified Architecture - Part 14: PubSub

8.6.3 ConnectSecurityGroups

Server . Signature ConnectSecurityGroups ( [in] NodeId[] SecurityGroupIds, [out] StatusCode[] ConnectResults ); Argument Description SecurityGroupIds The NodeIds of the SecurityGroups to connect to the PushTarget . ConnectResults The result codes for the SecurityGroups
OPC-10000-14 – OPC Unified Architecture - Part 14: PubSub

8.6.4 DisconnectSecurityGroups Method

Server . Signature DisconnectSecurityGroups ( [in] NodeId[] SecurityGroupIds, [out] StatusCode[] DisconnectResults ); Argument Description SecurityGroupIds The NodeIds of the SecurityGroups to disconnect. DisconnectResults The result codes for the SecurityGroups to disconnect. Method Result
OPC-10000-14 – OPC Unified Architecture - Part 14: PubSub

8.8 Security Key Service Roles

support the well-known Roles for SKS which are defined in Table 231 . The NodeIds for the well-known Roles are defined in OPC 10000-6 . Table 231 - Well-Known
OPC-10000-17 – OPC Unified Architecture - Part 17: Alias Names

1 Scope

from multiple Servers and provide a lookup Method to allow Client applications to discover NodeIds on a system wide basis. An aggregating Server could also define AliasNames for Nodes
OPC-10000-17 – OPC Unified Architecture - Part 17: Alias Names

6.3.4 AddAliasesToCategory Method

specific as to what namespace the AliasName is added to. TargetNodes An array of NodeIds that represents the target Nodes of the AliasNames to be added. Each element in this
OPC-10000-17 – OPC Unified Architecture - Part 17: Alias Names

B.1 Aggregating Server with a collection of Aggregates

also shall be merged. An aggregating Server could expose the same AliasName referencing multiple NodeIds . For example as shown in Figure B.1 , if a temperature sensor were to be connected
OPC-10000-17 – OPC Unified Architecture - Part 17: Alias Names

C.1 Overview

BrowseNames . The GDS will provide the ExpandedNodeId of all of the referenced NodeIds and the ServerUri of the Server containing the NodeId . The details of the expected behaviour
OPC-10000-17 – OPC Unified Architecture - Part 17: Alias Names

C.4 Disconnect between a Client and an AliasName Server

important to remember that the FindAlias Method will return a list of NodeIds (and Servers ) that meet the requested AliasName search string. It is up to the Client to determine
OPC-10000-17 – OPC Unified Architecture - Part 17: Alias Names

D.1.2 PubSub multicast messages

NodeId(s) in the list: The Subscriber would issue a Browse for the provided NodeIds of the AliasNameCategories . Note: The Browse could contain all NodeIds in the list. The Subscriber
OPC-10000-18 – OPC Unified Architecture - Part 18: Role-Based Security

4.2.2 AddRole Method

used together with the OPC UA namespace URI. The Server shall use the NodeIds for the well-known Roles in this case. The NodeIds for the well-known Roles
OPC-10000-18 – OPC Unified Architecture - Part 18: Role-Based Security

5.2.8 ChangePassword Method

shall be accessible and callable by the Session user with the well defined NodeIds for the UserManagement Object and the ChangePassword Method . This Method affects security and shall only
OPC-10000-19 – OPC Unified Architecture - Part 19: Dictionary Reference

7.1 MultiStateDictionaryEntryDiscreteBaseType VariableType

Properties and TargetNode being the DictionaryEntry Nodes. EnumDictionaryEntries is a two-dimensional array of NodeIds . The first dimension is used to list all possible dictionary entry values for the related ... well. Clients writing to the ValueAsDictionaryEntries Property shall use one of the DictionaryEntryType NodeIds defined by the Enum DictionaryEntries Property . This will have the same result as writing the value
OPC-10000-21 – OPC Unified Architecture - Part 21: Device Onboarding

10.2 Handling of OPC UA Namespaces

identifiers. A Node in the UA AddressSpace is unambiguously identified using a NodeId . Unlike NodeIds , the BrowseName cannot be used to unambiguously identify a Node . Different Nodes may have ... namespace of the NodeId reflects something else, for example the EngineeringUnits Property . All NodeIds of Nodes not defined in this document shall not use the standard namespaces. Table 37 provides
OPC-10000-21 – OPC Unified Architecture - Part 21: Device Onboarding

A.1 Namespace and Identifiers for the Onboarding Information Model

Nodes which are only used by Registrars . The NamespaceUri for any Device Onboarding specific NodeIds is: http://opcfoundation.org/UA/Onboarding/ The CSV released with this version of the standards
OPC-10000-24 – OPC Unified Architecture - Part 24: Scheduler

10.2 Handling of OPC UA Namespaces

identifiers. A Node in the UA AddressSpace is unambiguously identified using a NodeId . Unlike NodeIds , the BrowseName cannot be used to unambiguously identify a Node . Different Nodes may have ... namespace of the NodeId reflects something else, for example the EngineeringUnits Property . All NodeIds of Nodes not defined in this document shall not use the standard namespaces. Table 50 provides
OPC-10000-24 – OPC Unified Architecture - Part 24: Scheduler

A.1 Namespace and Identifiers for the Scheduler Information Model

Scheduler Information Model This appendix defines the numeric identifiers for all of the numeric NodeIds defined in this document. The identifiers are specified in a CSV file with the following ... ExceptionSchedule InstanceDeclaration within the ScheduleType declaration is: ScheduleType_ExceptionSchedule. The NamespaceUri for all NodeIds defined here is http://opcfoundation.org/UA/Scheduler/ The CSV released with this version of the specification
OPC-10000-25 – OPC Unified Architecture - Part 25: Object Serialization

6.3.2 SerializedData Variable

with the StatusCode Bad_NoValue. Note 1: It may be useful to use GUID NodeIds due to the dynamic of the process. Note 2: It is recommended, that Servers persist ... DataType NodeIds so that these NodeIds remain in place after restart, if the SerializationScope has not changed
OPC-10000-25 – OPC Unified Architecture - Part 25: Object Serialization

6.3.4 Include- and ExcludeReferenceTypes Properties

followed to create the SerializationScope : The IncludeReferenceTypes Property contains an array of ReferenceType NodeIds . Any Reference of each ReferenceType NodeId of the array including their subtypes is considered. The ExcludeReferenceTypes ... Property contains an array of ReferenceType NodeIds . Any Reference of each ReferenceType NodeId of the array including their subtypes is removed from the results out of the IncludeReferenceType Property
OPC-10000-81 – OPC Unified Architecture - Part 81: UAFX Connecting Devices and Information Model

6.4.6.3 SetStoredVariables method

StatusCode[] Results ); Table 50 - SetStoredVariables Method arguments Argument Description VariablesToStore An array of NodeIds containing configuration data variables. NodeId shall be the NodeId of a configuration data variable belonging
OPC-10000-81 – OPC Unified Architecture - Part 81: UAFX Connecting Devices and Information Model

6.7.4 EditConnectionConfigurationSets method

commit the updates to the ConnectionConfigurationSets or discard the updates. ConnectionConfigurationSets A list of NodeIds of ConnectionConfigurationSets to be edited. Results A list of StatusCode corresponding to the ConnectionConfigurationSets input
OPC-10000-81 – OPC Unified Architecture - Part 81: UAFX Connecting Devices and Information Model

6.7.5.2 ProcessConnectionConfigurationSets signature

operation to be performed on the ConnectionConfigurationSets (see 10.25 ). ConnectionConfigurationSets A list of NodeIds of ConnectionConfigurationSets to be processed. Results The array of StatusCode corresponding to the ConnectionConfigurationSets input argument
OPC-10000-81 – OPC Unified Architecture - Part 81: UAFX Connecting Devices and Information Model

6.16.3.2 PubSubCommunicationModelConfigurationType definition

Namespaces contains namespace URIs for NamespaceIndex used in the PubSubConfiguration . Examples are NodeIds contained in PublishedDataSets . The NamespaceIndex in the PubSubConfiguration will need to be updated to reflect the NamespaceIndexes ... addressed Server . NodeIds contained in the PubSubConfiguration , which use the special namespace " http://opcfoundation.org/UA/FX/CM/Translation/ ", are not valid NodeIds but placeholders which shall be resolved before the ConnectionManager
OPC-10000-81 – OPC Unified Architecture - Part 81: UAFX Connecting Devices and Information Model

8.9 EstablishConnectionErrorEventType

shall include a description of the action that was being taken, e.g. resolving NodeIds , configuring an SKS, verifying Nodes, or establishing a Connection . It shall include the FxErrorEnum value reported
OPC-10000-81 – OPC Unified Architecture - Part 81: UAFX Connecting Devices and Information Model

10.18.2 ConnectionEndpointParameterDataType definition

subtypes of the ConnectionEndpointType (for example, PubSubConnectionEndpointType ) InputVariableIds 0:NodeId[] Specifies a list of NodeIds that are inputs. If InputVariables are not provided, it shall be null or empty. OutputVariableIds ... NodeId[] Specifies a list of NodeIds that are outputs. If OutputVariables are not provided , it shall be null or empty. IsPersistent 0:Boolean If TRUE, specifies that the ConnectionEndpoint shall
OPC-10000-81 – OPC Unified Architecture - Part 81: UAFX Connecting Devices and Information Model

13.3.1 General

represented as PortableNodeId , PortableRelativePath or AliasName . These all need to be resolved to NodeIds (illustrated in Figure 67 and described in Clause 13.3.2 , 13.3.3 , and 13.3.4 ). This clause contains figures ... explain these concepts. Figure 67 - Configuration resolution A ConnectionManager shall be able to resolve NodeIds using PortableNodeIds , PortableRelativePaths and AliasNames . The following provides an illustration of what needs
OPC-10000-81 – OPC Unified Architecture - Part 81: UAFX Connecting Devices and Information Model

13.3.2 PortableNodeId provided

options and is described in its own clause (see 13.2 ). Convert the PortableNodeIds into NodeIds . This is accomplished by connecting to the Server , reading the NamespaceArray from the Server
OPC-10000-81 – OPC Unified Architecture - Part 81: UAFX Connecting Devices and Information Model

13.3.3 PortableRelativePath provided

TranslateBrowsePathsToNodeIds Service with all of the BrowsePaths that are to be converted to NodeIds . Cache the resulting list of NodeIds . The cache shall also include the NamespaceArray of the target ... illustrated in the sequence diagram shown in Figure 71 . The resolution of BrowsePaths to NodeIds can result in multiple NodesIds for a single BrowsePath . Configurations should try to produce unique
OPC-10000-81 – OPC Unified Architecture - Part 81: UAFX Connecting Devices and Information Model

13.3.4 AliasName provided

records in the ConnectionConfigurationSet . The returned list of Servers ( Connection information) and NodeIds should be cached. Figure 72 - AliasName Resolution If an AliasName was used to obtain the Server information
OPC-10000-81 – OPC Unified Architecture - Part 81: UAFX Connecting Devices and Information Model

14.2 Handling of OPC UA namespaces

identifiers. A Node in the UA AddressSpace is unambiguously identified using a NodeId . Unlike NodeIds , the BrowseName cannot be used to unambiguously identify a Node . Different Nodes may have ... namespace of the NodeId reflects something else, for example, the EngineeringUnits Property . All NodeIds of Nodes defined outside of this document shall not use the standard namespaces defined in this
OPC-10000-81 – OPC Unified Architecture - Part 81: UAFX Connecting Devices and Information Model

E.2.1 Overview

generated by the engineering tool generating the ConnectionConfigurationSet , the ConnectionManager must resolve the NodeIds contained in it (see 6.16.3.2 ). The ConnectionManager must ensure that the PubSubCommunicationFlowConfigurations and SubscriberConfigurations are reflected ... could be used. A ConnectionManager typically stores (in a vendor-specific manner) all resolved NodeIds
OPC-10000-81 – OPC Unified Architecture - Part 81: UAFX Connecting Devices and Information Model

E.3 Enable, disable, or remove Connections

remove are described in normative text (see 6.2.4 and 6.2.5 ), and since caching of NodeIds is vendor-specific, no example is provided
OPC-10000-81 – OPC Unified Architecture - Part 81: UAFX Connecting Devices and Information Model

E.6.6 Loading / Saving ConnectionConfigurationSets

include DataSets (published or subscribed) that would include fields that are of NodeId DataType . NodeIds contain a NamespaceIndex . The NamespaceIndex is an index into a NamespaceArray that contains ... Namespaces could not exist on the ConnectionManager Server . This document describes how these NodeIds are to be resolved to the correct NamespaceIndex on the target Server before the structure
OPC-10000-81 – OPC Unified Architecture - Part 81: UAFX Connecting Devices and Information Model

F.1.5 ConnectionEndpointConfigurationConfDataType

used for connecting the InputVariables . If the OutputVariableIds are not configured with NodeIds, the source variable NodeIds shall be null. They must be filled in by the ConnectionManager after getting ... NodeIds from the AutomationComponent during connection establishment. True SubscribedDataSetData 0:StandaloneSubscribedDataSetDataType If not null, it specifies a SubscribedDataSet to be used for connecting the InputVariables. If the InputVariableIds
OPC-10000-81 – OPC Unified Architecture - Part 81: UAFX Connecting Devices and Information Model

F.1.11 ServerAddressConfDataType

configuration properties for the Server. True Namespaces 0:String[] Namespace table for translation of NodeIds and RelativePaths related to this Server. For further details, see F.1.2.2 . False The ServerAddressConfDataType representation
OPC-10000-81 – OPC Unified Architecture - Part 81: UAFX Connecting Devices and Information Model

F.1.14 PubSubCommunicationModelConfigurationDataType

PubSubConfiguration2DataType PubSub configuration for the addressed Server when establishing Connections. TranslationTable 4:NodeIdTranslationDataType[] NodeIds contained in the PubSubConfiguration , which use the special namespace " http://opcfoundation.org/UA/FX/CM/Translation/ ... valid NodeIds but placeholders which shall be resolved before the ConnectionManager can use the PubSubConfiguration for connection establishment. ConfigurationReferences 0:PubSubConfigurationRefDataType[] ConfigurationReferences points to elements within the PubSubConfiguration and indicates
OPC-10000-81 – OPC Unified Architecture - Part 81: UAFX Connecting Devices and Information Model

F.3.3.1 CloseAndUpdate signature

elements shall match the length and order of the Operations array. ConfigurationObjects NodeIds of the related Objects If NodeIds are returned, the length of the array and the order ... contained in the written file. If the Server does not support the creation of NodeIds , the array is null or empty. The possible Method result codes are formally defined
OPC-10000-83 – OPC Unified Architecture - Part 83: UAFX OfflineEngineering

A.3.7.3 NodeId DataType

A.3.7.3 NodeId DataType NodeId - NodeIds in running OPC UA Servers are represented as an ID and a NamespaceIndex . In order to make reference to Nodes in the offline AutomationML file
OPC-10000-100 – OPC Unified Architecture - Part 100: Devices

3.3.1.4 Additional Attribute values

value field. Double quotes are not included. If the DataType includes a NamespaceIndex ( QualifiedNames , NodeIds or ExpandedNodeIds ) then the notation used for BrowseNames is used. If the value
OPC-10000-100 – OPC Unified Architecture - Part 100: Devices

3.3.2.1 NodeIds

NodeIds The NodeIds of all Nodes described in this standard are only symbolic names. Annex A defines the actual NodeIds . The symbolic name of each Node defined in this document ... unique name in this document, the symbolic name is unique. The NamespaceUri for all NodeIds defined in this document is defined in Annex A. The NamespaceIndex for this NamespaceUri
OPC-10000-100 – OPC Unified Architecture - Part 100: Devices

6.3.1 General

corresponding counterpart in the online ParameterSet shall have the same BrowseName . Their NodeIds shall be different, though, since this is the identifier passed by the Client in read/write requests
OPC-10000-100 – OPC Unified Architecture - Part 100: Devices

8.4.6.3 GetUpdateBehavior Method

NodeId of their FileType instance in the FileSystem . Signature GetUpdateBehavior( [in] 0:NodeId[] NodeIds, [out] UpdateBehavior UpdateBehavior); Table 86 - GetUpdateBehavior Method Arguments Argument Description NodeIds NodeIds of the files ... Codes (defined in Call Service) Result Code Description Bad_NotFound If one or more NodeIds are not found. Table 87 - GetUpdateBehavior Method AddressSpace definition Attribute Value BrowseName 1:GetUpdateBehavior References
OPC-10000-100 – OPC Unified Architecture - Part 100: Devices

8.4.6.4 ValidateFiles Method

part of the file transfer (e.g., in CloseAndCommit ). Signature ValidateFiles( [in] 0:NodeId[] NodeIds, [out] 0:Int32 ErrorCode, [out] 0:LocalizedText ErrorMessage); Table 88 - ValidateFiles Method Arguments Argument Description NodeIds ... NodeIds of the files to validate. ErrorCode 0 for success or device specific number for validation issues. ErrorMessage Message for the user that describes how to resolve the issue. Method
OPC-10000-100 – OPC Unified Architecture - Part 100: Devices

12.2 Handling of OPC UA namespaces

identifiers. A Node in the UA AddressSpace is unambiguously identified using a NodeId . Unlike NodeIds , the BrowseName cannot be used to unambiguously identify a Node . Different Nodes can have ... namespace of the NodeId reflects something else, for example the EngineeringUnits Property . All NodeIds of Nodes not defined in this specification shall not use the standard namespaces. Table 154 provides
OPC-10000-110 – OPC Unified Architecture - Part 110: Asset Management Basics

3.3.2.1 NodeIds

NodeIds The NodeIds of all Nodes described in this standard are only symbolic names. Annex A defines the actual NodeIds . The symbolic name of each Node defined in this document ... unique name in this document, the symbolic name is unique. The NamespaceUri for all NodeIds defined in this document is defined in Annex A. The NamespaceIndex for this NamespaceUri
OPC-10000-110 – OPC Unified Architecture - Part 110: Asset Management Basics

16.2 Handling of OPC UA Namespaces

identifiers. A Node in the UA AddressSpace is unambiguously identified using a NodeId . Unlike NodeIds , the BrowseName cannot be used to unambiguously identify a Node . Different Nodes may have ... namespace of the NodeId reflects something else, for example the EngineeringUnits Property . All NodeIds of Nodes not defined in this document shall not use the standard namespaces. Table 59 provides
OPC-10000-120 – OPC Unified Architecture - Part 120: OPC UA and XML Data Type Mapping

3.3.2.1 NodeIds

NodeIds The NodeIds of all Nodes described in this standard are only symbolic names. Annex A defines the actual NodeIds . The symbolic name of each Node defined in this document ... unique name in this document, the symbolic name is unique. The NamespaceUri for all NodeIds defined in this document is defined in Annex A. The NamespaceIndex for this NamespaceUri
OPC-10000-120 – OPC Unified Architecture - Part 120: OPC UA and XML Data Type Mapping

8.2 Handling of OPC UA Namespaces

identifiers. A Node in the UA AddressSpace is unambiguously identified using a NodeId . Unlike NodeIds , the BrowseName cannot be used to unambiguously identify a Node . Different Nodes may have ... namespace of the NodeId reflects something else, for example the EngineeringUnits Property . All NodeIds of Nodes not defined in this document shall not use the standard namespaces. Table 42 provides
OPC-10000-200 – OPC Unified Architecture - Part 200: Industrial Automation

3.3.2.1 NodeIds

NodeIds The NodeIds of all Nodes described in this standard are only symbolic names. Annex A defines the actual NodeIds . The symbolic name of each Node defined in this document ... unique name in this document, the symbolic name is unique. The NamespaceUri for all NodeIds defined in this document is defined in Annex A. The NamespaceIndex for this NamespaceUri
OPC-10000-200 – OPC Unified Architecture - Part 200: Industrial Automation

9.2 Handling of OPC UA Namespaces

identifiers. A Node in the UA AddressSpace is unambiguously identified using a NodeId . Unlike NodeIds , the BrowseName cannot be used to unambiguously identify a Node . Different Nodes may have ... namespace of the NodeId reflects something else, for example the EngineeringUnits Property . All NodeIds of Nodes not defined in this document shall not use the standard namespaces. Table 72 provides
OPC-10000-210 – OPC Unified Architecture - Part 210: Relative Spatial Location

3.4.2.1 NodeIds

NodeIds The NodeIds of all Nodes described in this standard are only symbolic names. Annex A defines the actual NodeIds . The symbolic name of each Node defined in this document ... unique name in this document, the symbolic name is unique. The NamespaceUri for all NodeIds defined in this document is defined in Annex A. The NamespaceIndex for this NamespaceUri
OPC-10000-210 – OPC Unified Architecture - Part 210: Relative Spatial Location

10.2 Handling of OPC UA Namespaces

identifiers. A Node in the UA AddressSpace is unambiguously identified using a NodeId . Unlike NodeIds , the BrowseName cannot be used to unambiguously identify a Node . Different Nodes may have ... namespace of the NodeId reflects something else, for example the EngineeringUnits Property . All NodeIds of Nodes not defined in this document shall not use the standard namespaces. Table 29 provides
OPC-10000-210 – OPC Unified Architecture - Part 210: Relative Spatial Location

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

Location Information Model This appendix defines the numeric identifiers for all of the numeric NodeIds defined in this document. The identifiers are specified in a CSV file with the following ... Identifier InstanceDeclaration within the SpatialObjectType declaration is: SpatialObjectType_Identifier . The NamespaceUri for all NodeIds defined here is http://opcfoundation.org/UA/RSL/ The CSV released with this version of the specification
OPC-10000-211 – OPC Unified Architecture - Part 211: Global Positioning

3.4.2.1 NodeIds

NodeIds The NodeIds of all Nodes described in this standard are only symbolic names. Annex A defines the actual NodeIds . The symbolic name of each Node defined in this document ... unique name in this document, the symbolic name is unique. The NamespaceUri for all NodeIds defined in this document is defined in Annex A. The NamespaceIndex for this NamespaceUri
OPC-10000-211 – OPC Unified Architecture - Part 211: Global Positioning

4.2.3.1 Concepts

designed to search for children based on the BrowseNames from the type instead of NodeIds . This eliminates the need for manual reconfiguration of systems if a Client uses types that
OPC-10000-211 – OPC Unified Architecture - Part 211: Global Positioning

4.2.3.2 Namespaces

types of structured values in OPC UA that are qualified with NamespaceIndexes : NodeIds and QualifiedNames . NodeIds are locally unique (and sometimes globally unique) identifiers for Nodes . The same globally unique ... data means in these Nodes . OPC UA Information Models generally define globally unique NodeIds for the TypeDefinitions defined by the Information Model . QualifiedNames are non-localized names qualified with
OPC-10000-211 – OPC Unified Architecture - Part 211: Global Positioning

12.2 Handling of OPC UA Namespaces

identifiers. A Node in the UA AddressSpace is unambiguously identified using a NodeId . Unlike NodeIds , the BrowseName cannot be used to unambiguously identify a Node . Different Nodes may have ... namespace of the NodeId reflects something else, for example the EngineeringUnits Property . All NodeIds of Nodes not defined in this document shall not use the standard namespaces. Table 31 provides