Search

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

61 result(s) for BrowseNames

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

4.10.2 Interface Model

Node's base type. Clients can also use the TranslateBrowsePathsToNodeId Service with BrowseNames of Interface members to get the NodeId of these members directly. In the example in Figure
OPC-10000-3 – OPC Unified Architecture - Part 3: Address Space Model

5.2.4 BrowseName

localised human-readable name when browsing the AddressSpace to create paths out of BrowseNames . The TranslateBrowsePathsToNodeIds Service defined in OPC 10000-4 can be used to follow a path constructed ... BrowseNames . A BrowseName should never be used to display the name of a Node . The DisplayName should be used instead for this purpose. Unlike NodeIds , the BrowseName cannot be used
OPC-10000-3 – OPC Unified Architecture - Part 3: Address Space Model

5.5.1 Object NodeClass

then all Nodes referenced with forward hierarchical References direction shall have unique BrowseNames in the context of this Object . If the Object is created based on an InstanceDeclaration then
OPC-10000-3 – OPC Unified Architecture - Part 3: Address Space Model

5.5.2 ObjectType NodeClass

described in Clause 7 . All Nodes referenced with forward hierarchical References shall have unique BrowseNames in the context of an ObjectType
OPC-10000-3 – OPC Unified Architecture - Part 3: Address Space Model

5.6.4 DataVariable

InstanceDeclaration (see 4.6 ) all Nodes referenced with forward hierarchical References shall have unique BrowseNames in the context of this DataVariable
OPC-10000-3 – OPC Unified Architecture - Part 3: Address Space Model

5.6.5 VariableType NodeClass

described in Clause 7 . All Nodes referenced with forward hierarchical References shall have unique BrowseNames in the context of the VariableType
OPC-10000-3 – OPC Unified Architecture - Part 3: Address Space Model

5.7.1 Method NodeClass

InstanceDeclaration (see 4.6 ) all Nodes referenced with forward hierarchical References shall have unique BrowseNames in the context of this Method . The Variable referenced by a HasArgumentDescription ReferenceType shall
OPC-10000-3 – OPC Unified Architecture - Part 3: Address Space Model

6.2.5 BrowsePath

BrowsePath A BrowsePath is a sequence of BrowseNames used to describe a path between Nodes related w ith a Reference
OPC-10000-3 – OPC Unified Architecture - Part 3: Address Space Model

6.4.4.4.3 ExposesItsArray

Therefore it references two instances of the same type as the InstanceDeclaration ArrayExpose. The BrowseNames of those instances are not defined by the ModellingRule . In general, it is not possible
OPC-10000-3 – OPC Unified Architecture - Part 3: Address Space Model

6.4.4.4.4 OptionalPlaceholder

expects from instances of the TypeDefinition to add instances with specific References without defining BrowseNames for the instances. For example, a Device might have a Folder for DeviceParameters
OPC-10000-4 – OPC Unified Architecture - Part 4: Services

5.9.4.1 Description

from which the RelativePath is based. The RelativePath contains a sequence of ReferenceTypes and BrowseNames . One purpose of this Service is to allow programming against type definitions. Since BrowseNames shall
OPC-10000-4 – OPC Unified Architecture - Part 4: Services

7.7.4.1 Overview

using a Node in the type system and relative path constructed from ReferenceTypes and BrowseNames . SimpleAttribute Specifies any Attribute of an Object or Variable Node using a TypeDefinition ... relative path constructed from BrowseNames
OPC-10000-4 – OPC Unified Architecture - Part 4: Services

7.7.4.5 SimpleAttributeOperand

path to a Node . This parameter specifies a relative path using a list of BrowseNames instead of the RelativePath structure used in the AttributeOperand . The list of BrowseNames is equivalent
OPC-10000-4 – OPC Unified Architecture - Part 4: Services

7.30 RelativePath

Table 169 - RelativePath Name Type Description RelativePath structure Defines a sequence of References and BrowseNames to follow. elements [] RelativePath Element A sequence of References and BrowseNames to follow. This structure
OPC-10000-4 – OPC Unified Architecture - Part 4: Services

A.2 BNF of RelativePath

reserved character is escaped by inserting the '&' in front of it. Examples of BrowseNames with escaped characters are: Received browse path name Resolves to "&/Name_1
OPC-10000-5 – OPC Unified Architecture - Part 5: Information Model

4.2 BrowseNames

BrowseNames The text part of the BrowseNames for all Nodes defined in this standard is specified in the tables defining the Nodes . The NamespaceIndex for all BrowseNames defined in this
OPC-10000-5 – OPC Unified Architecture - Part 5: Information Model

5.1 General

NodeClass Shall reflect the NodeClass of the Node. NodeId The NodeId is described by BrowseNames as defined in 4.1 and defined in OPC 10000-6 . WriteMask Optionally the WriteMask Attribute
OPC-10000-11 – OPC Unified Architecture - Part 11: Historical Access

5.2.4 Historical Data Configuration Object

shall have a BrowseName of 'HA Configuration'. Additional configurations can be defined with different BrowseNames . It is highly recommended that display names for historical configuration historical configuration are chosen that
OPC-10000-12 – OPC Unified Architecture - Part 12: Discovery and Global Services

10.2 Handling of OPC UA Namespaces

standard namespaces. Table 162 provides a list of namespaces and their index used for BrowseNames in this document. The default namespace of this document is not listed since all BrowseNames
OPC-10000-14 – OPC Unified Architecture - Part 14: PubSub

6.2.3.2.2 DataTypeSchemaHeader

affects encoding NodeIds in ExtensionObjects but also all other namespace indices in NodeIds and BrowseNames contained in the messages. If the Subscriber receives Structure DataTypes where the target Variables DataTypes
OPC-10000-14 – OPC Unified Architecture - Part 14: PubSub

6.2.9.4 DataSetMetaData

affects encoding NodeIds in ExtensionObjects but also all other namespace indices in NodeIds and BrowseNames contained in the messages. If the Subscriber receives Structure DataTypes where the target Variables DataTypes
OPC-10000-15 – OPC Unified Architecture - Part 15: Safety

6.2.2.2 Safety ObjectType definitions

ReferenceType HasProperty (and shall not be derived from ReferenceType HasProperty ) for Property References . As BrowseNames (i.e. name and Namespace ) are used to find Methods , the names of Objects and Properties
OPC-10000-17 – OPC Unified Architecture - Part 17: Alias Names

C.1 Overview

Pull all AliasNameCategory instances, merge any that have identical Name part of the BrowseNames . The GDS will provide the ExpandedNodeId of all of the referenced NodeIds and the ServerUri
OPC-10000-21 – OPC Unified Architecture - Part 21: Device Onboarding

10.2 Handling of OPC UA Namespaces

standard namespaces. Table 37 provides a list of namespaces and their index used for BrowseNames in this document. The default namespace of this document is not listed since all BrowseNames
OPC-10000-22 – OPC Unified Architecture - Part 22: Base Network Model

4.1 Type and Naming Conventions

types used by the related managed objects of IEEE and IETF. BrowseNames of Variables and parameter sets (UA interface) are preferably derived from standardized IETF / IEEE YANG models
OPC-10000-24 – OPC Unified Architecture - Part 24: Scheduler

10.2 Handling of OPC UA Namespaces

used in a Scheduler Server NamespaceURI Description http://opcfoundation.org/UA/ Namespace for NodeIds and BrowseNames defined in the OPC UA specification. This namespace shall have namespace index 0. Local Server ... This namespace shall have namespace index 1. http://opcfoundation.org/UA/Scheduler/ Namespace for NodeIds and BrowseNames defined in this document. The namespace index is Server specific. Vendor specific types A Server
OPC-10000-25 – OPC Unified Architecture - Part 25: Object Serialization

6.2 Limitations

Limitations Since the BrowseNames of the Variables in the SerializationScope are used as field names for the SerializationFieldDataType fields in the SerializationValue DataType , limitations for BrowseNames arise: The characters used ... BrowseNames must be permissible in field names of Structure DataTypes . To achieve this, it is recommended to limit the characters used in BrowseNames to letters (lower- and uppercase), digits
OPC-10000-25 – OPC Unified Architecture - Part 25: Object Serialization

6.3.7 CustomMetaDataProperties Property

Variable . Sub- Variables are represented with elements containing KeyValuePairs with keys equal to the BrowseNames of the Variables (see "Variable1", "Variable2" and "Variable3" elements
OPC-10000-25 – OPC Unified Architecture - Part 25: Object Serialization

6.4.3 SerializationFieldDataType of Variables with Children

mapped child. Servers shall make sure that field names are unique (e.g., two BrowseNames can have the same text field but different namespaces). The SerializationFieldDataType of each of those fields
OPC-10000-81 – OPC Unified Architecture - Part 81: UAFX Connecting Devices and Information Model

6.2.2 AutomationComponentType definition

contains Variables that report diagnostic statistics and counters (see OPC 10000-100 Recommended FunctionalGroup BrowseNames ). EstablishCallCount diagnostics counter Variable provides a count of the number of EstablishConnections calls received. EstablishCallFailedCount
OPC-10000-81 – OPC Unified Architecture - Part 81: UAFX Connecting Devices and Information Model

6.4.2 FunctionalEntityType definition

Variables representing the configuration items of the FunctionalEntity (see OPC 10000-100 Recommended FunctionalGroup BrowseNames ). The optional Tuning FunctionalGroup contains Variables that can be used to optimise the behaviour ... FunctionalEntity (see OPC 10000-100 Recommended FunctionalGroup BrowseNames ). The optional Capabilities is a FunctionalEntityCapabilitiesType Folder that describes the functionality provided by a FunctionalEntity (see 6.4.7 ). The optional PublisherCapabilities provide
OPC-10000-81 – OPC Unified Architecture - Part 81: UAFX Connecting Devices and Information Model

6.4.4 InputsFolderType

Variable via subtypes of the HasChild Reference (HasProperty, HasComponent or other subtypes ). The BrowseNames of Variables in this Folder shall be unique within this Folder ; the use of nested
OPC-10000-81 – OPC Unified Architecture - Part 81: UAFX Connecting Devices and Information Model

6.4.5 OutputsFolderType

Variable via subtypes of the HasChild Reference (HasProperty, HasComponent or other subtypes ). The BrowseNames of Variables in this Folder shall be unique within this Folder ; the use of nested
OPC-10000-81 – OPC Unified Architecture - Part 81: UAFX Connecting Devices and Information Model

6.4.6.2 ConfigurationDataFolderType definition

Variables via subtypes of the HasChild Reference (HasProperty, HasComponent or other subtypes ). The BrowseNames of Variables in this Folder shall be unique within this Folder . All Variables in this folder ... into a tree of FunctionalGroups . This will also assist with the uniqueness requirement for BrowseNames . The optional Methods SetStoredVariables , ClearStoredVariables , and ListStoredVariables allow for the maintenance of storage for configuration
OPC-10000-81 – OPC Unified Architecture - Part 81: UAFX Connecting Devices and Information Model

6.7.2 ConnectionManagerType definition

Diagnostics FunctionalGroup contains Variables and Methods for diagnostics (see OPC 10000-100 Recommended FunctionalGroup BrowseNames ). For UAFX, this includes the defined diagnostic Variable in Table 78 - ConnectionManagerType additional subcomponents Table
OPC-10000-81 – OPC Unified Architecture - Part 81: UAFX Connecting Devices and Information Model

6.15.2 AssetVerificationType definition

expected that this list contains IdentifierBrowsePath with a PortableRelativePath as Keys using BrowseNames as defined in Table 31 . ExpectedAdditionalVerificationVariables hold the variables to be verified for compatibility and/or identity
OPC-10000-81 – OPC Unified Architecture - Part 81: UAFX Connecting Devices and Information Model

10.39 PortableRelativePath

PortableRelativePath This structure contains a PortableRelativePath , which defines a sequence of References and BrowseNames to follow for storing a relative path outside the context of where the target ... Structure defined in OPC 10000-5 Elements 4:PortableRelativePathElement[] A sequence of References and BrowseNames to follow. This array defines a sequence of elements. Each element in the sequence
OPC-10000-81 – OPC Unified Architecture - Part 81: UAFX Connecting Devices and Information Model

14.2 Handling of OPC UA namespaces

UAFX Server NamespaceURI Description Use http://opcfoundation .org/UA/ Namespace for NodeIds and BrowseNames defined in the OPC UA specification. This namespace shall have the namespace index 0. Mandatory Local Server ... between a ConnectionManager and an AutomationComponent . Mandatory http://opcfoundation.org/UA/FX/AC / Namespace for NodeIds and BrowseNames defined in the AutomationComponent -related part of this document. The namespace index is Server -specific
OPC-10000-100 – OPC Unified Architecture - Part 100: Devices

3.3.1.4 Additional Attribute values

DataType includes a NamespaceIndex ( QualifiedNames , NodeIds or ExpandedNodeIds ) then the notation used for BrowseNames is used. If the value is an Enumeration the name of the enumeration value is entered
OPC-10000-100 – OPC Unified Architecture - Part 100: Devices

3.3.2.2 BrowseNames

BrowseNames The text part of the BrowseNames for all Nodes defined in this document is specified in the tables defining the Nodes . The NamespaceUri for all BrowseNames defined in this
OPC-10000-100 – OPC Unified Architecture - Part 100: Devices

3.3.3.1 General

NodeClass Shall reflect the NodeClass of the Node. NodeId The NodeId is described by BrowseNames as defined in 3.3.2.1 . WriteMask Optionally the WriteMask Attribute can be provided. If the WriteMask
OPC-10000-100 – OPC Unified Architecture - Part 100: Devices

4.4.1 Model

BrowseName of a FunctionalGroup should indicate its purpose. A list of well-known BrowseNames is in 4.4.2 . Figure 3 shows the FunctionalGroupType components. It is formally defined in Table ... Variable 1:UIElement 0:BaseDataType 1:UIElementType O Conformance Units DI Information Model All BrowseNames for Nodes referenced by a FunctionalGroup with an Organizes Reference shall be unique. The Organizes
OPC-10000-100 – OPC Unified Architecture - Part 100: Devices

4.10 DeviceFeatures entry point

Devices referenced by the DeviceSet . Companion specifications can standardize such instances and their BrowseNames . Figure 13 shows the AddressSpace organisation with this standard entry point. Figure 13 - Standard entry point
OPC-10000-100 – OPC Unified Architecture - Part 100: Devices

12.2 Handling of OPC UA namespaces

Devices Server NamespaceURI Description Use http://opcfoundation.org/UA/ Namespace for NodeIds and BrowseNames defined in the OPC UA specification. This namespace shall have namespace index 0. Mandatory Local Server ... namespace shall have namespace index 1. Mandatory http://opcfoundation.org/UA/DI/ Namespace for NodeIds and BrowseNames defined in this specification. The namespace index is Server specific. Mandatory Vendor specific types
OPC-10000-110 – OPC Unified Architecture - Part 110: Asset Management Basics

3.3.2.2 BrowseNames

BrowseNames The text part of the BrowseNames for all Nodes defined in this document is specified in the tables defining the Nodes . The NamespaceUri for all BrowseNames defined in this
OPC-10000-110 – OPC Unified Architecture - Part 110: Asset Management Basics

3.3.3.1 General

NodeClass Shall reflect the NodeClass of the Node. NodeId The NodeId is described by BrowseNames as defined in 3.3.2.1 . WriteMask Optionally the WriteMask Attribute can be provided. If the WriteMask
OPC-10000-110 – OPC Unified Architecture - Part 110: Asset Management Basics

16.2 Handling of OPC UA Namespaces

Asset Management Basics Server NamespaceURI Description Use http://opcfoundation.org/UA/ Namespace for NodeIds and BrowseNames defined in the OPC UA specification. This namespace shall have namespace index 0. Mandatory Local ... namespace shall have namespace index 1. Mandatory http://opcfoundation.org/UA/DI/ Namespace for NodeIds and BrowseNames defined in OPC 10000-100 . The namespace index is Server specific. Mandatory http://opcfoundation.org/UA/AMB/
OPC-10000-120 – OPC Unified Architecture - Part 120: OPC UA and XML Data Type Mapping

3.3.2.2 BrowseNames

BrowseNames The text part of the BrowseNames for all Nodes defined in this document is specified in the tables defining the Nodes . The NamespaceUri for all BrowseNames defined in this
OPC-10000-120 – OPC Unified Architecture - Part 120: OPC UA and XML Data Type Mapping

3.3.3.1 General

NodeClass Shall reflect the NodeClass of the Node. NodeId The NodeId is described by BrowseNames as defined in 3.3.2.1 . WriteMask Optionally the WriteMask Attribute can be provided. If the WriteMask
OPC-10000-120 – OPC Unified Architecture - Part 120: OPC UA and XML Data Type Mapping

8.2 Handling of OPC UA Namespaces

Data Types Server NamespaceURI Description Use http://opcfoundation.org/UA/ Namespace for NodeIds and BrowseNames defined in the OPC UA specification. This namespace shall have namespace index 0. Mandatory Local Server ... namespace shall have namespace index 1. Mandatory http://opcfoundation.org/UA/XML/ Namespace for NodeIds and BrowseNames defined in this document. The namespace index is Server specific. Mandatory Vendor specific types
OPC-10000-200 – OPC Unified Architecture - Part 200: Industrial Automation

3.3.2.2 BrowseNames

BrowseNames The text part of the BrowseNames for all Nodes defined in this document is specified in the tables defining the Nodes . The NamespaceUri for all BrowseNames defined in this
OPC-10000-200 – OPC Unified Architecture - Part 200: Industrial Automation

3.3.3.1 General

NodeClass Shall reflect the NodeClass of the Node. NodeId The NodeId is described by BrowseNames as defined in 3.3.2.1 . WriteMask Optionally the WriteMask Attribute can be provided. If the WriteMask
OPC-10000-200 – OPC Unified Architecture - Part 200: Industrial Automation

9.2 Handling of OPC UA Namespaces

Industrial Automation Server NamespaceURI Description Use http://opcfoundation.org/UA/ Namespace for NodeIds and BrowseNames defined in the OPC UA specification. This namespace shall have namespace index 0. Mandatory Local Server ... namespace shall have namespace index 1. Mandatory http://opcfoundation.org/UA/DI/ Namespace for NodeIds and BrowseNames defined in OPC 10000-100 . The namespace index is Server specific. Mandatory http://opcfoundation.org/UA/IA/
OPC-10000-210 – OPC Unified Architecture - Part 210: Relative Spatial Location

3.4.2.2 BrowseNames

BrowseNames The text part of the BrowseNames for all Nodes defined in this document is specified in the tables defining the Nodes . The NamespaceUri for all BrowseNames defined in this
OPC-10000-210 – OPC Unified Architecture - Part 210: Relative Spatial Location

3.4.3.1 General

NodeClass Shall reflect the NodeClass of the Node. NodeId The NodeId is described by BrowseNames as defined in 3.4.2.1 . WriteMask Optionally the WriteMask Attribute can be provided. If the WriteMask
OPC-10000-210 – OPC Unified Architecture - Part 210: Relative Spatial Location

10.2 Handling of OPC UA Namespaces

Relative Spatial Location Server NamespaceURI Description Use http://opcfoundation.org/UA/ Namespace for NodeIds and BrowseNames defined in the OPC UA specification. This namespace shall have namespace index 0. Mandatory Local ... namespace shall have namespace index 1. Mandatory http://opcfoundation.org/UA/DI/ Namespace for NodeIds and BrowseNames defined in OPC 10000-100 . The namespace index is Server specific. Optional http://opcfoundation.org/UA/RSL/
OPC-10000-211 – OPC Unified Architecture - Part 211: Global Positioning

3.4.2.2 BrowseNames

BrowseNames The text part of the BrowseNames for all Nodes defined in this document is specified in the tables defining the Nodes . The NamespaceUri for all BrowseNames defined in this
OPC-10000-211 – OPC Unified Architecture - Part 211: Global Positioning

3.4.3.1 General

NodeClass Shall reflect the NodeClass of the Node. NodeId The NodeId is described by BrowseNames as defined in 3.4.2.1 . WriteMask Optionally the WriteMask Attribute can be provided. If the WriteMask
OPC-10000-211 – OPC Unified Architecture - Part 211: Global Positioning

4.2.3.1 Concepts

instances of PersonType are expected to have the same children with the same BrowseNames . Within a type the BrowseNames uniquely identify the children. This means Client applications can be designed ... 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 multiple Servers
OPC-10000-211 – OPC Unified Architecture - Part 211: Global Positioning

4.2.3.2 Namespaces

QualifiedNames are non-localized names qualified with a Namespace. They are used for the BrowseNames of Nodes and allow the same names to be used by different information models without ... conflict. TypeDefinitions are not allowed to have children with duplicate BrowseNames ; however, instances do not have that restriction
OPC-10000-211 – OPC Unified Architecture - Part 211: Global Positioning

12.2 Handling of OPC UA Namespaces

Global Positioning Server NamespaceURI Description http://opcfoundation.org/UA/ Namespace for NodeIds and BrowseNames defined in the OPC UA specification. This namespace shall have namespace index 0. Local Server URI Namespace ... This namespace shall have namespace index 1. http://opcfoundation.org/UA/RSL/ Namespace for NodeIds and BrowseNames defined in OPC 10000-210 . The namespace index is Server specific. http://opcfoundation.org/UA/GPOS/ Namespace