Search
92 result(s) for NodeClass
-
OPC-10000-1 – OPC Unified Architecture - Part 1: Overview and Concepts2.1.24 NodeClassNodeClass class of a Node in an AddressSpace Note 1 to entry: NodeClasses define the metadata for the components of the OPC UA object model. They also define constructs, such
-
OPC-10000-5 – OPC Unified Architecture - Part 5: Information Model12.2.5.2 NodeClassNodeClass The representation in the AddressSpace of the NodeClass DataType is defined in Table 167 . Table 167 - NodeClass definition Attributes Value BrowseName NodeClass IsAbstract FALSE References NodeClass BrowseName DataType TypeDefinition
-
OPC-10000-1 – OPC Unified Architecture - Part 1: Overview and ConceptsAddressSpace . OPC 10000-3 defines the OPC UA NodeClasses . The Base NodeClass defines Attributes common to all Node s, allowing identification, classification, and naming. Each NodeClass inherits these Attributes
-
OPC-10000-3 – OPC Unified Architecture - Part 3: Address Space ModelWhen two lines are used, the first text line in the rectangle identifies the NodeClass and the second line contains the BrowseName . When one line is used, it contains
-
OPC-10000-3 – OPC Unified Architecture - Part 3: Address Space ModelTable 1 describes the format of the tables used to define NodeClasses . Table 1 - NodeClass Table Conventions Name Use Data Type Description Attributes "Attribute name ... used Describes the use of the Reference by the NodeClass Standard Properties "Property name" "M" or "O" Data type of the Property Defines
-
OPC-10000-3 – OPC Unified Architecture - Part 3: Address Space Model4.3 Object Modelmodel are represented in the AddressSpace as Nodes . Each Node is assigned to a NodeClass and each NodeClass represents a different element of the Object Model. Clause 4.10 defines
-
OPC-10000-3 – OPC Unified Architecture - Part 3: Address Space Model4.4.3 AttributesAttributes are elementary components of NodeClasses . Attribute definitions are included as part of the NodeClass definitions in Clause 4.10 and, therefore, are not included in the AddressSpace . Each Attribute definition ... data type and a mandatory/optional indicator. The set of Attributes defined for each NodeClass shall not be extended by Clients or Servers . When a Node is instantiated in the AddressSpace
-
OPC-10000-3 – OPC Unified Architecture - Part 3: Address Space Model4.4.4 ReferencesNodes . ReferenceType Nodes are visible in the AddressSpace and are defined using the ReferenceType NodeClass (see 5.3 ). The Node that contains the Reference is referred to as the SourceNode
-
OPC-10000-3 – OPC Unified Architecture - Part 3: Address Space Model4.5.2 Propertiespurchase order. Attributes define additional metadata that is instantiated for all Nodes from a NodeClass . Attributes are common to all Nodes of a NodeClass and only defined by this specification
-
OPC-10000-3 – OPC Unified Architecture - Part 3: Address Space Model4.7.2 EventTypesEventTypes are represented as ObjectTypes in the AddressSpace and do not have a special NodeClass associated to them. OPC 10000-5 defines how a Server exposes the EventTypes in detail
-
OPC-10000-3 – OPC Unified Architecture - Part 3: Address Space Model4.10.2 Interface Modelshall not use the same BrowsePath for a different Node (e.g. with a different NodeClass ). If the rules cannot be fulfilled (e.g. name collisions) the ObjectType cannot apply the Interface
-
OPC-10000-3 – OPC Unified Architecture - Part 3: Address Space Model5.1 Overviewdefine Nodes in the OPC UA AddressSpace . NodeClasses are derived from a common Base NodeClass . This NodeClass is defined first, followed by those used to organise the AddressSpace and then
-
OPC-10000-3 – OPC Unified Architecture - Part 3: Address Space Model5.2.1 GeneralGeneral The OPC UA Address Space Model defines a Base NodeClass from which all other NodeClasses are derived. The derived NodeClasses represent the various components of the OPC UA Object ... Model (see 4.2 ). The Attributes of the Base NodeClass are specified in Table 7 . There are no References specified for the Base NodeClass . Table 7 - Base NodeClass Name Use Data
-
OPC-10000-3 – OPC Unified Architecture - Part 3: Address Space Model5.2.3 NodeClassNodeClass The NodeClass Attribute identifies the NodeClass of a Node . Its data type is defined
-
OPC-10000-3 – OPC Unified Architecture - Part 3: Address Space Model5.3.1 GeneralNodes . ReferenceType Nodes are visible in the AddressSpace and are defined using the ReferenceType NodeClass as specified in Table 9 . In contrast, a Reference is an inherent part ... Node and no NodeClass is used to represent References . This standard defines a set of ReferenceTypes provided as an inherent part of the OPC UA Address Space Model. These ReferenceTypes
-
OPC-10000-3 – OPC Unified Architecture - Part 3: Address Space Model5.3.2 AttributesAttributes The ReferenceType NodeClass inherits the base Attributes from the Base NodeClass defined in 5.2 . The inherited BrowseName Attribute is used to specify the meaning of the ReferenceType as seen
-
OPC-10000-3 – OPC Unified Architecture - Part 3: Address Space Model5.4 View NodeClassView NodeClass Underlying systems are often large and Clients often have an interest in only a specific subset of the data. They do not need, or want, to be burdened ... root for the Nodes in the View . Views are defined using the View NodeClass , which is specified in Table 10 . All Nodes contained in a View shall be accessible starting
-
OPC-10000-3 – OPC Unified Architecture - Part 3: Address Space Model5.5.1 Object NodeClassObject NodeClass Objects are used to represent systems, system components, real-world objects and software objects. Objects are defined using the Object NodeClass , specified in Table 11 . Table 11 - Object ... NodeClass Name Use Data Type Description Attributes Base NodeClass Attributes M -- Inherited from the Base NodeClass . See 5.2 . EventNotifier M EventNotifierType The EventNotifier Attribute is used to indicate
-
OPC-10000-3 – OPC Unified Architecture - Part 3: Address Space ModelView or an Object of the ObjectType FolderType ; the TargetNode can be of any NodeClass . Organizes References can be used in any combination with HasChild References ( HasComponent , HasProperty
-
OPC-10000-3 – OPC Unified Architecture - Part 3: Address Space Model5.6.1 Generalhave different constraints described in the remainder of 5.6 they use the same NodeClass described in 5.6.2 . The constraints of Properties based on this NodeClass are defined
-
OPC-10000-3 – OPC Unified Architecture - Part 3: Address Space Model5.6.2 Variable NodeClassVariable NodeClass Variables are used to represent values which may be simple or complex. Variables are defined by VariableTypes , as specified in 5.6.5 . Variables are always defined as Properties ... related to any number of other Nodes . Variables are defined using the Variable NodeClass , specified in Table 13 . Table 13 - Variable NodeClass Name Use Data Type Description Attributes Base NodeClass
-
OPC-10000-3 – OPC Unified Architecture - Part 3: Address Space Model5.6.5 VariableType NodeClassVariableType NodeClass VariableTypes are used to provide type definitions for Variables . VariableTypes are defined using the VariableType NodeClass , as specified in Table 14 . Table 14 - VariableType NodeClass Name Use Data ... Type Description Attributes Base NodeClass Attributes M -- Inherited from the Base NodeClass . See 5.2 Value O Defined by the DataType attribute The default Value for instances of this type. DataType
-
OPC-10000-3 – OPC Unified Architecture - Part 3: Address Space Model5.7.1 Method NodeClassMethod NodeClass Methods define callable functions. Methods are invoked using the Call Service defined in OPC 10000-4 . Method invocations are not represented in the AddressSpace . Method invocations always ... completion and always return responses when complete. Methods are defined using the Method NodeClass , specified in Table 15 . Table 15 - Method NodeClass Name Use Data Type Description Attributes Base NodeClass
-
OPC-10000-3 – OPC Unified Architecture - Part 3: Address Space Modelextends the semantic of the HasComponent ReferenceType to reference argument Metadata of a Method NodeClass . The SourceNode of this ReferenceType shall be a Method and the TargetNode of this ReferenceType
-
OPC-10000-3 – OPC Unified Architecture - Part 3: Address Space Model5.8.1 DataType ModelVariableType is pointing with its DataType Attribute to a Node of the DataType NodeClass as shown in Figure 17 . Figure 17 - Variables, VariableTypes and their DataTypes In many cases
-
OPC-10000-3 – OPC Unified Architecture - Part 3: Address Space Modelrepresentation. An example of an enumeration DataType containing a sparse list of Integers is NodeClass which is defined in 8.29 . An OptionSet can be defined in one of two ways
-
OPC-10000-3 – OPC Unified Architecture - Part 3: Address Space Model5.8.3 DataType NodeClassDataType NodeClass The DataType NodeClass describes the syntax of a Variable Value . DataTypes are defined using the DataType NodeClass , as specified in Table 16 . Table 16 - DataType NodeClass Name ... Data Type Description Attributes Base NodeClass Attributes M -- Inherited from the Base NodeClass . See 5.2 . IsAbstract M Boolean A boolean Attribute with the following values: TRUE it is an abstract
-
OPC-10000-3 – OPC Unified Architecture - Part 3: Address Space Modelsimilar Node of an InstanceDeclaration is a Node that has the same BrowseName and NodeClass as the InstanceDeclaration and in cases of Variables and Objects the same TypeDefinitionNode
-
OPC-10000-3 – OPC Unified Architecture - Part 3: Address Space ModelAttributes of InstanceDeclarations when the InstanceDeclaration is overridden or instantiated. The BrowseName and the NodeClass shall never change and always be the same as the original InstanceDeclaration . In addition ... rules defined in 6.2.8 apply for InstanceDeclarations of the NodeClass Variable
-
OPC-10000-3 – OPC Unified Architecture - Part 3: Address Space Model6.3.1 OverviewReferenceType defines subtypes of types. Subtyping can only occur between Nodes of the same NodeClass . Rules for subtyping ReferenceTypes are described in 5.3.3.3 . There is no common definition for subtyping
-
OPC-10000-3 – OPC Unified Architecture - Part 3: Address Space Model6.3.3.3 Overriding InstanceDeclarationsspecifying an InstanceDeclaration with the same BrowsePath . An overridden InstanceDeclaration shall have the same NodeClass and BrowseName . The TypeDefinitionNode of the overridden InstanceDeclaration shall be the same or a subtype ... change the target of the Reference but the new target shall have the same NodeClass and for Objects and Variables also the same type or a subtype of the type
-
OPC-10000-3 – OPC Unified Architecture - Part 3: Address Space Model6.4.1 OverviewNode has an InstanceDeclaration then it shall have the same BrowseName and NodeClass as the InstanceDeclaration and, in cases of Variables and Objects , the same TypeDefinitionNode or a subtype
-
OPC-10000-3 – OPC Unified Architecture - Part 3: Address Space Model6.4.2 Creating an Instancecommon with the TypeDefinitionNode from which they are instantiated, with the exceptions of the NodeClass and NodeId . When a Server creates an instance of a TypeDefinitionNode it shall create ... child Node s. If a child Node exists then the BrowseName and NodeClass shall match the InstanceDeclaration . In the case of Objects or Variables, also the TypeDefinitionNode shall either match
-
OPC-10000-3 – OPC Unified Architecture - Part 3: Address Space Model6.4.4.4.3 ExposesItsArrayVariable in the AddressSpace . The ExposesItsArray ModellingRule can only be applied on InstanceDeclarations of NodeClass Variable that are part of a VariableType having a single- or multidimensional array
-
OPC-10000-3 – OPC Unified Architecture - Part 3: Address Space ModelProperties are described in 4.5.2 . The SourceNode of this ReferenceType can be of any NodeClass . The TargetNode shall be a Variable . By using the HasProperty Reference , the Variable is defined
-
OPC-10000-3 – OPC Unified Architecture - Part 3: Address Space ModelVariableType , a DataType or a ReferenceType and the TargetNode shall be of the same NodeClass as the SourceNode . Each ReferenceType shall be the TargetNode of at most one Reference
-
OPC-10000-3 – OPC Unified Architecture - Part 3: Address Space Modelsubtypes (see 5.5.3 ). The TargetNode of this ReferenceType can be of any NodeClass
-
OPC-10000-3 – OPC Unified Architecture - Part 3: Address Space Model7.17 HasEventSourceEvent Subscriptions. The TargetNode of this ReferenceType can be a Node of any NodeClass that can generate event notifications via a subscription to the reference source. Starting from Node
-
OPC-10000-3 – OPC Unified Architecture - Part 3: Address Space Modelinformation model. The SourceNode of this ReferenceType shall be a Node of any NodeClass . The TargetNode shall be an Object which represents the information model version where the Node
-
OPC-10000-3 – OPC Unified Architecture - Part 3: Address Space Model8.14 EnumerationEnumeration This abstract DataType is the base DataType for all enumeration DataTypes like NodeClass defined in 8.29 . All DataTypes inheriting from this DataType have special handling for the encoding
-
OPC-10000-3 – OPC Unified Architecture - Part 3: Address Space Model8.29 NodeClassNodeClass This DataType is an enumeration that identifies a NodeClass . Its values are defined in Table 30 . Table 30 - NodeClass Values Name Value Description Unspecified 0 No value is specified
-
OPC-10000-3 – OPC Unified Architecture - Part 3: Address Space ModelC.2.2 Simple notationC.2.2 Simple notation Depending on their NodeClass Nodes are represented by different graphical forms as defined in Table C.1 . Table C.1 - Notation of Nodes depending on the NodeClass NodeClass Graphical ... solution can also be used. Table C.2 - Simple Notation of Nodes depending on the NodeClass ReferenceType Graphical Representation Comment Any symmetric ReferenceType Symmetric ReferenceTypes are represented as lines between Nodes
-
OPC-10000-4 – OPC Unified Architecture - Part 4: Services5.8.2.2 Parametersdescription of ReferenceType NodeIds . browseName QualifiedName The browse name of the Node to add. nodeClass NodeClass NodeClass of the Node to add. nodeAttributes Extensible Parameter NodeAttributes The Attributes that ... specific to the NodeClass . The NodeAttributes parameter type is an extensible parameter type specified in 7.24 . A Client is allowed to omit values for some or all Attributes
-
OPC-10000-4 – OPC Unified Architecture - Part 4: Services5.8.3.1 Descriptionused to add one or more References to one or more Nodes . The NodeClass is an input parameter that is used to validate that the Reference to be added matches ... NodeClass of the TargetNode . This parameter is not validated if the Reference refers to a TargetNode in a remote Server . In certain cases, adding new References to the AddressSpace shall
-
OPC-10000-4 – OPC Unified Architecture - Part 4: Services5.8.3.2 ParametersSourceNode . The targetNodeClass of each Reference in the list shall match the NodeClass of the TargetNode . This structure is defined in-line with the following indented items. sourceNodeId NodeId NodeId ... TargetNode is a local Node the nodeId shall contain the namespace index. targetNodeClass NodeClass NodeClass of the TargetNode . The Client shall specify this since the TargetNode might not be accessible
-
OPC-10000-4 – OPC Unified Architecture - Part 4: Services5.9.2.2 Parameterswith the selected NodeClasses are returned. The NodeClasses are assigned the following bits: Bit NodeClass 0 Object 1 Variable 2 Method 3 ObjectType 4 VariableType 5 ReferenceType 6 DataType ... View If set to zero, then all NodeClasses are returned. If the NodeClass is unknown for a remote Node , the nodeClassMask is ignored. resultMask UInt32 Specifies the fields
-
OPC-10000-4 – OPC Unified Architecture - Part 4: Services7.7.3 FilterOperatoroperand that resolves to a NodeId or ExpandedNodeId where the Node is of the NodeClass DataType . If there is any error in conversion or in any of the parameters then
-
OPC-10000-4 – OPC Unified Architecture - Part 4: Services7.7.4.5 SimpleAttributeOperandHierarchicalReferences ReferenceType . All Nodes followed by the browsePath shall be of the NodeClass Object or Variable . If this list is empty the Node is the instance of the TypeDefinition . attributeId
-
OPC-10000-4 – OPC Unified Architecture - Part 4: Services7.24.1 OverviewNodeAttributes is an extensible parameter whose structure depends on the type of the NodeClass being added. It identifies the NodeClass that defines the structure of the Attributes that follow ... Table 149 - NodeAttributes parameterTypeIds Symbolic Id Description ObjectAttributes Defines the Attributes for the Object NodeClass . VariableAttributes Defines the Attributes for the Variable NodeClass . MethodAttributes Defines the Attributes for the Method
-
OPC-10000-4 – OPC Unified Architecture - Part 4: Services7.24.3 VariableAttributes parameterTable 152 - VariableAttributes Name Type Description VariableAttributes structure Defines the Attributes for the Variable NodeClass specifiedAttributes UInt32 A bit mask that indicates which fields contain valid values. A field shall
-
OPC-10000-4 – OPC Unified Architecture - Part 4: Services7.24.4 MethodAttributes parameterTable 153 - MethodAttributes Name Type Description MethodAttributes structure Defines the Attributes for the Method NodeClass specifiedAttributes UInt32 A bit mask that indicates which fields contain valid values. A field shall
-
OPC-10000-4 – OPC Unified Architecture - Part 4: ServicesTable 155 - VariableTypeAttributes Name Type Description VariableTypeAttributes structure Defines the Attributes for the VariableType NodeClass specifiedAttributes UInt32 A bit mask that indicates which fields contain valid values. A field shall
-
OPC-10000-4 – OPC Unified Architecture - Part 4: Services7.24.10 GenericAttributes parameterGenericAttributes parameter This structure should be used instead of the NodeClass specific structures defined in the other sub sections of 7.24 since it allows the handling of additional Attributes defined
-
OPC-10000-4 – OPC Unified Architecture - Part 4: Services7.29 ReferenceDescriptionQualifiedName The BrowseName of the TargetNode . displayName LocalizedText The DisplayName of the TargetNode . nodeClass 1 NodeClass NodeClass of the TargetNode . typeDefinition 1 Expanded NodeId Type definition NodeId of the TargetNode ... ExpandedNodeId indicates that the TargetNode is a remote Node , then the browseName , nodeClass and typeDefinition may be null or empty. If they are not null or empty, they might
-
OPC-10000-5 – OPC Unified Architecture - Part 5: Information Modeldefined by providing the ReferenceType name, the BrowseName of the TargetNode and its NodeClass . If the TargetNode is a component of the Node being defined in the table, the Attributes ... NodeClasses cannot be defined in the same table; therefore only the used ReferenceType , their NodeClass and their BrowseName are specified. A reference to another part of this document points
-
OPC-10000-5 – OPC Unified Architecture - Part 5: Information Model5.1 Generalother LocaleIds is server-specific. Description Optionally a server-specific description is provided. NodeClass Shall reflect the NodeClass of the Node. NodeId The NodeId is described by BrowseNames as defined
-
OPC-10000-6 – OPC Unified Architecture - Part 6: Mappings5.3.3 Enumerationsnumeric value associated with enumerated value. For example, the XML schema for the NodeClass enumeration is: <xs:simpleType name="NodeClass"> <xs:restriction base ... Int32 value. For example, any Variable could have a value with a DataType of NodeClass . In this case, the corresponding numeric value is placed in the Variant (e.g. NodeClass Object
-
OPC-10000-6 – OPC Unified Architecture - Part 6: MappingsF.3 UANodedefines the base set of Attributes and the References . There are subtypes for each NodeClass defined in OPC 10000-4 . Each of these subtypes defines XML elements and attributes ... Attributes specific to the NodeClass . The fields in the UANode type are defined in Table F.2 . Table F.2 - UANode Element Type Description NodeId NodeId A NodeId serialized as a String
-
OPC-10000-9 – OPC Unified Architecture - Part 9: Alarms & Conditions7.3 HasEffectEnableObjectType TransitionType or one of its subtypes. The TargetNode can be of any NodeClass . The representation of the HasEffectEnable ReferenceType in the AddressSpace is specified in Table 139 Table ... HasEffectEnable ReferenceType Attributes Value BrowseName HasEffectEnable InverseName MayBeEnabledBy Symmetric False IsAbstract False References NodeClass BrowseName Comment ConformanceUnits A & C Statemachine Trigger
-
OPC-10000-9 – OPC Unified Architecture - Part 9: Alarms & ConditionsObjectType TransitionType or one of its subtypes. The TargetNode can be of any NodeClass . The representation of the HasEffectSuppressed ReferenceType in the AddressSpace is specified in Table 140 Table ... HasEffectSuppressed ReferenceType Attributes Value BrowseName HasEffectSuppressed InverseName MayBeSuppressedBy Symmetric False IsAbstract False References NodeClass BrowseName Comment ConformanceUnits A & C Statemachine Suppression Trigger
-
OPC-10000-9 – OPC Unified Architecture - Part 9: Alarms & ConditionsObjectType TransitionType or one of its subtypes. The TargetNode can be of any NodeClass . The representation of the HasEffectUnsuppressed ReferenceType in the AddressSpace is specified in Table 141 . Table ... HasEffectUnsuppressed ReferenceType Attributes Value BrowseName HasEffectUnsuppressed InverseName MayBeUnsuppressedBy Symmetric False IsAbstract False References NodeClass BrowseName Comment ConformanceUnits A & C Statemachine Suppression Trigger
-
OPC-10000-10 – OPC Unified Architecture - Part 10: Programs1 ScopeEvents and associated behaviour and information for Programs . The complete AddressSpace model including all NodeClass es and Attributes is specified in OPC 10000-3 . The Services such as those used
-
OPC-10000-11 – OPC Unified Architecture - Part 11: Historical Access1 Scopeassociated with Historical Access (HA). It particularly includes additional and complementary descriptions of the NodeClass es and Attributes needed for Historical Access, additional standard Properties , and other information and behaviour ... complete AddressSpace Model including all NodeClass es and Attributes is specified in OPC 10000-3 . The predefined Information Model is defined in OPC 10000-5 . The Services to detect
-
OPC-10000-16 – OPC Unified Architecture - Part 16: State Machines4.4.14 HasCauseObjectType TransitionType or one of its subtypes. The TargetNode can be of any NodeClass . The representation of the HasCause ReferenceType in the AddressSpace is specified in Table 14 . Table ... HasCause ReferenceType Attributes Value BrowseName HasCause InverseName MayBeCausedBy Symmetric False IsAbstract False References NodeClass BrowseName Comment Conformance Units Base Info Finite State Machine Instance
-
OPC-10000-16 – OPC Unified Architecture - Part 16: State Machines4.4.15 HasEffectObjectType TransitionType or one of its subtypes. The TargetNode can be of any NodeClass . If the TargetNode is an EventType , each time the Transition is triggered (either by a Client ... HasEffect ReferenceType Attributes Value BrowseName HasEffect InverseName MayBeEffectedBy Symmetric False IsAbstract False References NodeClass BrowseName Comment Conformance Units Base Info Finite State Machine Instance
-
OPC-10000-23 – OPC Unified Architecture - Part 23: Common ReferenceTypes4.8.2 Definitionreal world. The SourceNode of References of this ReferenceType can be of any NodeClass . The TargetNode of References of this ReferenceType can be of any NodeClass . Both, SourceNode and TargetNode ... Table 7 - RepresentsSameEntityAs Definition Attributes Value BrowseName RepresentsSameEntityAs InverseName - Symmetric TRUE IsAbstract FALSE References NodeClass BrowseName Comment Subtype of NonHierarchicalReferences defined in OPC 10000-5 Conformance Units Base Info RepresentsSameEntityAs
-
OPC-10000-23 – OPC Unified Architecture - Part 23: Common ReferenceTypes4.9.2 Definitionsame hardware. The SourceNode of References of this ReferenceType can be of any NodeClass . The TargetNode of References of this ReferenceType can be of any NodeClass . Both, SourceNode and TargetNode ... Table 8 - RepresentsSameHardwareAs Definition Attributes Value BrowseName RepresentsSameHardwareAs InverseName - Symmetric TRUE IsAbstract FALSE References NodeClass BrowseName Comment Subtype of RepresentsSameEntityAs defined in 4.8 Conformance Units Base Info RepresentsSameHardwareAs
-
OPC-10000-23 – OPC Unified Architecture - Part 23: Common ReferenceTypes4.10.2 Definitionsame functionality. The SourceNode of References of this ReferenceType can be of any NodeClass . The TargetNode of References of this ReferenceType can be of any NodeClass . Both, SourceNode and TargetNode ... Table 9 - RepresentsSameFunctionalityAs Definition Attributes Value BrowseName RepresentsSameFunctionalityAs InverseName - Symmetric TRUE IsAbstract FALSE References NodeClass BrowseName Comment Subtype of RepresentsSameEntityAs defined in 4.8 Conformance Units Base Info RepresentsSameFunctionalityAs
-
OPC-10000-23 – OPC Unified Architecture - Part 23: Common ReferenceTypes5.4.1 HasReferenceDescriptionrefinement path)). The SourceNode of References of this type can be of any NodeClass . The TargetNode of this ReferenceType shall be a Variable of VariableType ReferenceDescriptionVariableType ... HasReferenceDescription Definition Attributes Value BrowseName HasReferenceDescription InverseName ReferenceDescriptionOf Symmetric FALSE IsAbstract FALSE References NodeClass BrowseName Comment Subtype of HasChild defined in OPC 10000-5 Conformance Units Base Info ReferenceDescription
-
OPC-10000-81 – OPC Unified Architecture - Part 81: UAFX Connecting Devices and Information Model6.3.3 VerifyAsset methodnull, it shall be verified that NodeId exists. The Node may be of any NodeClass, but only the NodeClass of Variable or VariableType can have a non-null value. VerificationResult
-
OPC-10000-81 – OPC Unified Architecture - Part 81: UAFX Connecting Devices and Information Model6.4.3 Verify methodverify if the Node exists in the Server . The Node may be of any NodeClass, but only the NodeClass of Variable or VariableType can have a non-null value . VerificationResult
-
OPC-10000-83 – OPC Unified Architecture - Part 83: UAFX OfflineEngineeringbase class from which they all derive; they just all conform to the Method NodeClass . In AML, it is desirable to have a base SUC UaMethodNodeClass that represents ... Methods are instantiated. Since there is no Node that represents the Method NodeClass in a UA Namespace (because it is built-in to the UA meta-model), the SUC UaMethodNodeClass
-
OPC-10000-83 – OPC Unified Architecture - Part 83: UAFX OfflineEngineeringNodeClass mapping The OPC UA metamodel uses the concept of NodeClasses to define sets of primitive attributes that are present on different types of nodes in the UA address space ... This NodeClass concept is not mapped directly in AutomationML . Instead, the relevant attributes are first introduced in the SystemUnitClass, where they would appear on an ObjectType or VariableType
-
OPC-10000-83 – OPC Unified Architecture - Part 83: UAFX OfflineEngineeringvolatile memory Added AccessLevelEx to Table A.6. 9214 Clarification Table "Mapping UA Base NodeClass attributes to SUC UaMethodNodeClass, BaseObjectType ... attributes" is not updated Updated chapter A.4 with additions ... content of the OPC UA Base NodeClass and the NodeId attribute in Table A.4. 9231 Clarification Handling of nodeids for interfaceclasses of inverse referencetypes Added to the NodeId
-
OPC-10000-100 – OPC Unified Architecture - Part 100: Devices3.3.1.1 Node definitionsdefined by providing the ReferenceType name, the BrowseName of the TargetNode and its NodeClass . If the TargetNode is a component of the Node being defined in the table the Attributes ... NodeClasses cannot be defined in the same table; therefore, only the used ReferenceType , their NodeClass and their BrowseName are specified. A reference to another part of this document points
-
OPC-10000-100 – OPC Unified Architecture - Part 100: Devices3.3.2.2 BrowseNamesBrowseNames defined in this document is defined in Annex A . For InstanceDeclarations of NodeClass Object and Variable that are placeholders ( OptionalPlaceholder and MandatoryPlaceholder ModellingRule ), the BrowseName and the DisplayName
-
OPC-10000-100 – OPC Unified Architecture - Part 100: Devices3.3.3.1 Generalother LocaleIds are server-specific. Description Optionally a server-specific description is provided. NodeClass Shall reflect the NodeClass of the Node. NodeId The NodeId is described by BrowseNames as defined
-
OPC-10000-110 – OPC Unified Architecture - Part 110: Asset Management Basics3.3.1.1 Node definitionsdefined by providing the ReferenceType name, the BrowseName of the TargetNode and its NodeClass . If the TargetNode is a component of the Node being defined in the table the Attributes ... NodeClasses cannot be defined in the same table; therefore, only the used ReferenceType , their NodeClass and their BrowseName are specified. A reference to another part of this document points
-
OPC-10000-110 – OPC Unified Architecture - Part 110: Asset Management Basics3.3.2.2 BrowseNamesBrowseNames defined in this document is defined in 16.2 . For InstanceDeclarations of NodeClass Object and Variable that are placeholders ( OptionalPlaceholder and MandatoryPlaceholder ModellingRule ), the BrowseName and the DisplayName are enclosed
-
OPC-10000-110 – OPC Unified Architecture - Part 110: Asset Management Basics3.3.3.1 Generalother LocaleIds are server-specific. Description Optionally a server-specific description is provided. NodeClass Shall reflect the NodeClass of the Node. NodeId The NodeId is described by BrowseNames as defined
-
OPC-10000-120 – OPC Unified Architecture - Part 120: OPC UA and XML Data Type Mapping3.3.1.1 Node definitionsdefined by providing the ReferenceType name, the BrowseName of the TargetNode and its NodeClass . If the TargetNode is a component of the Node being defined in the table the Attributes ... NodeClasses cannot be defined in the same table; therefore, only the used ReferenceType , their NodeClass and their BrowseName are specified. A reference to another part of this document points
-
OPC-10000-120 – OPC Unified Architecture - Part 120: OPC UA and XML Data Type Mapping3.3.2.2 BrowseNamesBrowseNames defined in this document is defined in 8.2 . For InstanceDeclarations of NodeClass Object and Variable that are placeholders ( OptionalPlaceholder and MandatoryPlaceholder ModellingRule ), the BrowseName and the DisplayName are enclosed
-
OPC-10000-120 – OPC Unified Architecture - Part 120: OPC UA and XML Data Type Mapping3.3.3.1 Generalother LocaleIds is server-specific. Description Optionally a server-specific description is provided. NodeClass Shall reflect the NodeClass of the Node. NodeId The NodeId is described by BrowseNames as defined
-
OPC-10000-200 – OPC Unified Architecture - Part 200: Industrial Automationdefined by providing the ReferenceType name, the BrowseName of the TargetNode and its NodeClass . If the TargetNode is a component of the Node being defined in the table the Attributes ... NodeClasses cannot be defined in the same table; therefore, only the used ReferenceType , their NodeClass and their BrowseName are specified. A reference to another part of this document points
-
OPC-10000-200 – OPC Unified Architecture - Part 200: Industrial Automation3.3.2.2 BrowseNamesBrowseNames defined in this document is defined in Annex A. For InstanceDeclarations of NodeClass Object and Variable that are placeholders ( OptionalPlaceholder and MandatoryPlaceholder ModellingRule ), the BrowseName and the DisplayName
-
OPC-10000-200 – OPC Unified Architecture - Part 200: Industrial Automation3.3.3.1 Generalother LocaleIds are server-specific. Description Optionally a server-specific description is provided. NodeClass Shall reflect the NodeClass of the Node. NodeId The NodeId is described by BrowseNames as defined
-
OPC-10000-210 – OPC Unified Architecture - Part 210: Relative Spatial Location3.4.1.1 Node definitionsdefined by providing the ReferenceType name, the BrowseName of the TargetNode and its NodeClass . If the TargetNode is a component of the Node being defined in the table the Attributes ... NodeClasses cannot be defined in the same table; therefore, only the used ReferenceType , their NodeClass and their BrowseName are specified. A reference to another part of this document points
-
OPC-10000-210 – OPC Unified Architecture - Part 210: Relative Spatial Location3.4.2.2 BrowseNamesBrowseNames defined in this document is defined in 10.2 . For InstanceDeclarations of NodeClass Object and Variable that are placeholders ( OptionalPlaceholder and MandatoryPlaceholder ModellingRule ), the BrowseName and the DisplayName are enclosed
-
OPC-10000-210 – OPC Unified Architecture - Part 210: Relative Spatial Location3.4.3.1 Generalother LocaleIds are server-specific. Description Optionally a server-specific description is provided. NodeClass Shall reflect the NodeClass of the Node. NodeId The NodeId is described by BrowseNames as defined
-
OPC-10000-211 – OPC Unified Architecture - Part 211: Global Positioning3.4.1.1 Node definitionsdefined by providing the ReferenceType name, the BrowseName of the TargetNode and its NodeClass . If the TargetNode is a component of the Node being defined in the table the Attributes ... NodeClasses cannot be defined in the same table; therefore, only the used ReferenceType , their NodeClass and their BrowseName are specified. A reference to another part of this document points
-
OPC-10000-211 – OPC Unified Architecture - Part 211: Global Positioning3.4.2.2 BrowseNamesBrowseNames defined in this document is defined in 12.2 . For InstanceDeclarations of NodeClass Object and Variable that are placeholders ( OptionalPlaceholder and MandatoryPlaceholder ModellingRule ), the BrowseName and the DisplayName are enclosed
-
OPC-10000-211 – OPC Unified Architecture - Part 211: Global Positioning3.4.3.1 Generalother LocaleIds is server-specific. Description Optionally a server-specific description is provided. NodeClass Shall reflect the NodeClass of the Node. NodeId The NodeId is described by BrowseNames as defined