Search

180 result(s) for Attributes

• OPC-10000-1 – OPC Unified Architecture - Part 1: Overview and Concepts
  4.4.2 Integrated AddressSpace model
  Node s connected by References . Primitive characteristics of Node s are described by Attributes . Attributes are the only elements of a Server that have data values. Data types that define ... AddressSpace . 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-1 – OPC Unified Architecture - Part 1: Overview and Concepts
  6.7 Attribute Service Set
  Service Set The Attribute Service Set is used to read and write Attribute values. Attributes are primitive characteristics of Nodes that are defined by OPC UA. They ... defined by Clients or Servers . Attributes are the only elements in the AddressSpace permitted to have data values. A special Attribute , the Value Attribute is used to define the value
• OPC-10000-1 – OPC Unified Architecture - Part 1: Overview and Concepts
  6.9 MonitoredItem Service Set
  used by the Client to create and maintain MonitoredItems . MonitoredItems monitor Variables , Attributes and EventNotifiers . They generate Notifications when they detect certain conditions. They monitor Variables for a change ... value or status; Attributes for a change in value; and EventNotifiers for newly generated Alarm and Event reports. Each MonitoredItem identifies the item to monitor and the Subscription
• OPC-10000-1 – OPC Unified Architecture - Part 1: Overview and Concepts
  6.10 Subscription Service Set
  format of Notifications is specific to the type of item being monitored (i.e. Variables , Attributes , and EventNotifiers ). Once created, the existence of a Subscription is independent of the Client
• OPC-10000-3 – OPC Unified Architecture - Part 3: Address Space Model
  3.3.1 Conventions for AddressSpace figures
  used, it contains the BrowseName . Node rectangles may contain boxes used to define their Attributes and References . Specific names in these boxes identify specific Attributes and References . Shaded rectangles with
• OPC-10000-3 – OPC Unified Architecture - Part 3: Address Space Model
  3.3.2 Conventions for defining NodeClasses
  used to define NodeClasses . Table 1 - NodeClass Table Conventions Name Use Data Type Description Attributes "Attribute name" "M" or "O" Data type ... description of the Attribute , the Reference or the Property . Only this document may define Attributes . Thus, all Attributes of the NodeClass are specified in the table and may only
• OPC-10000-3 – OPC Unified Architecture - Part 3: Address Space Model
  4.4.1 General
  their components are represented in the AddressSpace as a set of Nodes described by Attributes and interconnected by References . Figure 3 illustrates the model of a Node and the remainder
• OPC-10000-3 – OPC Unified Architecture - Part 3: Address Space Model
  4.4.2 NodeClasses
  NodeClasses NodeClasses are defined in terms of the Attributes and References that shall be instantiated (given values) when a Node is defined in the AddressSpace . Attributes are discussed
• OPC-10000-3 – OPC Unified Architecture - Part 3: Address Space Model
  4.4.3 Attributes
  Attributes Attributes are data elements that describe Nodes . Clients can access Attribute values using Read, Write, Query, and Subscription/MonitoredItem Services . These Services are defined in OPC 10000-4 . Attributes ... AddressSpace . Each Attribute definition consists of an attribute id (for attribute ids of Attributes , see OPC 10000-6 ), a name, a description, a data type and a mandatory/optional indicator
• OPC-10000-3 – OPC Unified Architecture - Part 3: Address Space Model
  4.4.4 References
  accessed using the browsing and querying Services defined in OPC 10000-4 . Like Attributes , they are defined as fundamental components of Nodes . Unlike Attributes , References are defined as instances
• OPC-10000-3 – OPC Unified Architecture - Part 3: Address Space Model
  4.5.2 Properties
  Properties are Server -defined characteristics of Objects , DataVariables and other Nodes . Properties differ from Attributes in that they characterise what the Node represents, such as a device or a purchase ... 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 whereas
• OPC-10000-3 – OPC Unified Architecture - Part 3: Address Space Model
  4.6.1 General
  type if no more specialised type information is available. Objects and Variables inherit the Attributes specified by their TypeDefinitionNode (see 6.4 for details). In some cases, the NodeId used
• OPC-10000-3 – OPC Unified Architecture - Part 3: Address Space Model
  5.2.1 General
  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 ... Base NodeClass . Table 7 - Base NodeClass Name Use Data Type Description Attributes NodeId M NodeId See 5.2.2 NodeClass M NodeClass See 5.2.3 BrowseName M QualifiedName See 5.2.4 DisplayName M LocalizedText
• OPC-10000-3 – OPC Unified Architecture - Part 3: Address Space Model
  5.2.7 WriteMask
  WriteMask The optional WriteMask Attribute exposes the possibilities of a client to write the Attributes of the Node . The WriteMask Attribute does not take any user access rights into account
• OPC-10000-3 – OPC Unified Architecture - Part 3: Address Space Model
  5.2.8 UserWriteMask
  UserWriteMask The optional UserWriteMask Attribute exposes the possibilities of a client to write the Attributes of the Node taking user access rights into account. It uses the AttributeWriteMask DataType which
• OPC-10000-3 – OPC Unified Architecture - Part 3: Address Space Model
  5.3.2 Attributes
  Attributes 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 ... more complex semantics associated with a ReferenceType than can be expressed in those Attributes (e.g. the semantic of HasSubtype ). This standard does not specify how this semantic should be exposed
• OPC-10000-3 – OPC Unified Architecture - Part 3: Address Space Model
  5.4 View NodeClass
  type FolderType (see 5.5.3 ). Table 10 - View NodeClass Name Use Data Type Description Attributes Base NodeClass Attributes M -- Inherited from the Base NodeClass . See 5.2 . ContainsNoLoops M Boolean ... ViewVersion shall always be greater than 0. The View NodeClass inherits the base Attributes from the Base NodeClass defined in 5.2 . It also defines two additional Attributes . The mandatory ContainsNoLoops
• OPC-10000-3 – OPC Unified Architecture - Part 3: Address Space Model
  5.5.1 Object NodeClass
  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 ... Icon Property contains a relatively small image. The Object NodeClass inherits the base Attributes from the Base NodeClass defined in 5.2 . The mandatory EventNotifier Attribute identifies whether the Object
• OPC-10000-3 – OPC Unified Architecture - Part 3: Address Space Model
  5.5.2 ObjectType NodeClass
  specified in Table 12 . Table 12 - ObjectType NodeClass Name Use Data Type Description Attributes Base NodeClass Attributes M -- Inherited from the Base NodeClass . See 5.2 . IsAbstract M Boolean A boolean ... shall only be on the type Node . The ObjectType NodeClass inherits the base Attributes from the Base NodeClass defined in 5.2 . The additional IsAbstract Attribute indicates if the ObjectType
• OPC-10000-3 – OPC Unified Architecture - Part 3: Address Space Model
  5.6.2 Variable NodeClass
  NodeClass , specified in Table 13 . Table 13 - Variable NodeClass Name Use Data Type Description Attributes Base NodeClass Attributes M -- Inherited from the Base NodeClass . See 5.2 . Value M Defined ... Property belongs to. Attribute value changes except for the DataType , ValueRank and ArrayDimensions Attributes do not cause the NodeVersion to change. Clients may read the NodeVersion Property or subscribe
• OPC-10000-3 – OPC Unified Architecture - Part 3: Address Space Model
  5.6.5 VariableType NodeClass
  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 ... Property belongs to. Attribute value changes except for the DataType , ValueRank and ArrayDimensions Attributes do not cause the NodeVersion to change. Clients may read the NodeVersion Property or subscribe
• OPC-10000-3 – OPC Unified Architecture - Part 3: Address Space Model
  5.7.1 Method NodeClass
  NodeClass , specified in Table 15 . Table 15 - Method NodeClass Name Use Data Type Description Attributes Base NodeClass Attributes M -- Inherited from the Base NodeClass . See 5.2 . Executable M Boolean ... specifies the result returned from the Method call. The Method NodeClass inherits the base Attributes from the Base NodeClass defined in 5.2 . The Method NodeClass defines no additional Attributes
• OPC-10000-3 – OPC Unified Architecture - Part 3: Address Space Model
  5.8.3 DataType NodeClass
  specified in Table 16 . Table 16 - DataType NodeClass Name Use Data Type Description Attributes Base NodeClass Attributes M -- Inherited from the Base NodeClass . See 5.2 . IsAbstract M Boolean A boolean ... OptionSetLength shall be at least 3 bytes. The DataType NodeClass inherits the base Attributes from the Base NodeClass defined in 5.2 . The IsAbstract Attribute specifies if the DataType is abstract
• OPC-10000-3 – OPC Unified Architecture - Part 3: Address Space Model
  5.8.6.1 Overview
  defined, the DataType of the Value is defined by the DataType , ValueRank and ArrayDimensions Attributes . In general, it is always allowed for the Value to use a subtype
• OPC-10000-3 – OPC Unified Architecture - Part 3: Address Space Model
  5.9 Summary of Attributes of the NodeClasses
  Summary of Attributes of the NodeClasses Table 18 summarises all Attributes defined in this document and points out which NodeClasses use them either in an optional (O) or mandatory ... Table 18 - Overview of Attributes Attribute Variable Variable Type Object Object Type Reference Type DataType Method View AccessLevel M AccessLevelEx O AccessRestrictions
• OPC-10000-3 – OPC Unified Architecture - Part 3: Address Space Model
  6.2.7 Attribute Handling of InstanceDeclarations
  Attribute Handling of InstanceDeclarations Some restrictions exist regarding the Attributes of InstanceDeclarations when the InstanceDeclaration is overridden or instantiated. The BrowseName and the NodeClass shall never change and always
• OPC-10000-3 – OPC Unified Architecture - Part 3: Address Space Model
  6.2.8 Attribute Handling of Variable and VariableTypes
  Attribute Handling of Variable and VariableTypes Some restrictions exist regarding the Attributes of a VariableType or a Variable used as an InstanceDeclaration with regard to the data type
• OPC-10000-3 – OPC Unified Architecture - Part 3: Address Space Model
  6.3.2 Attributes
  Attributes Subtypes inherit the parent type's Attribute values, except for the NodeId . Inherited Attribute values may be overridden by the subtype, the BrowseName and DisplayName values should be overridden ... Special rules apply for some Attributes of VariableTypes as defined in 6.2.8 . Optional Attributes , not provided by the parent type, may be added to the subtype
• OPC-10000-3 – OPC Unified Architecture - Part 3: Address Space Model
  6.3.3.1 Overview
  Nodes , changing References to be subtypes of the original ReferenceType , changing values of the Attributes or adding optional Attributes . In order to get the full information about a subtype
• OPC-10000-3 – OPC Unified Architecture - Part 3: Address Space Model
  6.3.3.3 Overriding InstanceDeclarations
  specified in the parent. The overriding Node may specify new values for the Node Attributes other than the NodeClass or BrowseName , however, the restrictions on Attributes specified in 6.2.7 apply ... overridden InstanceDeclaration has to be provided by the overriding InstanceDeclaration , additional optional Attributes may be added. A subtype shall not override an argument of its supertype's Method InstanceDeclaration which
• OPC-10000-3 – OPC Unified Architecture - Part 3: Address Space Model
  6.4.2 Creating an Instance
  Creating an Instance Instances inherit the initial values for the Attributes that they have in common with the TypeDefinitionNode from which they are instantiated, with the exceptions of the NodeClass
• OPC-10000-3 – OPC Unified Architecture - Part 3: Address Space Model
  6.4.3 Constraints on an Instance
  Variables may change their Attribute values after being created. Special rules apply for some Attributes as defined in 6.2.7 . Additional References may be added to the Nodes , and References
• OPC-10000-3 – OPC Unified Architecture - Part 3: Address Space Model
  8.55 PermissionType
  from the Node . This implies that the Client is able to Read to Attributes other than the Value or the RolePermissions Attribute . This Permission is valid for all NodeClasses . ReadRolePermissions ... valid for all NodeClasses . WriteAttribute 2 The Client is allowed to write to Attributes other than the Value , Historizing or RolePermissions Attribute if the WriteMask indicates that the Attribute
• OPC-10000-3 – OPC Unified Architecture - Part 3: Address Space Model
  8.60 AttributeWriteMask
  does not apply for Variables since this is handled by the AccessLevel and UserAccessLevel Attributes for the Variable . For Variables this bit shall be set to 0. DataTypeDefinition 22 Indicates
• OPC-10000-3 – OPC Unified Architecture - Part 3: Address Space Model
  B.2 Notation
  concept Base is given in the UML class diagram in Figure B.2 . OPC Attributes inherit from the abstract class Attribute and have a value identifying their data type. They ... TypeExtension>> objects (e.g. HasComponent in Figure B.3 ). In object diagrams, OPC Attributes are represented as UML attributes without data types and marked with the stereotype <<Attribute
• OPC-10000-3 – OPC Unified Architecture - Part 3: Address Space Model
  B.3 Meta Model
  this series of standards can extend the OPC UA Meta Model by adding Attributes and defining new ReferenceTypes . The figures in the following clauses are not intended to be complete
• OPC-10000-3 – OPC Unified Architecture - Part 3: Address Space Model
  B.3.3 Attributes
  B.3.3 Attributes Attributes are shown in Figure B.7 . Figure B.7 - Attributes There may be more Attributes defined in other parts of this series of standards. Attributes used for references, which
• OPC-10000-3 – OPC Unified Architecture - Part 3: Address Space Model
  C.1 General
  graphical notation is able to expose all structural data of OPC UA. Nodes , their Attributes including their current value and References between the Nodes including the ReferenceType can be exposed
• OPC-10000-3 – OPC Unified Architecture - Part 3: Address Space Model
  C.2.1 Overview
  simple notation only provides a simplified view on the data hiding some details like Attributes . The extended notation allows exposing all structure information of OPC UA, including Attribute values
• OPC-10000-3 – OPC Unified Architecture - Part 3: Address Space Model
  C.2.3 Extended notation
  HasTypeDefinition . Figure C.2 - Example of using a TypeDefinition inside a Node To display Attributes of a Node additional text can be put inside the form representing the Node under ... text representing the DisplayName . The DisplayName and the text describing the Attributes have to be separated using a horizontal line. Each Attribute has to be set into a new text
• OPC-10000-4 – OPC Unified Architecture - Part 4: Services
  4.1 Service Set model
  illustrated in Figure 6 . It defines Services that allow Clients to read and write Attributes of Nodes , including their historical values. Since the value of a Variable is modelled
• OPC-10000-4 – OPC Unified Architecture - Part 4: Services
  5.8.2.2 Parameters
  nodeClass NodeClass NodeClass of the Node to add. nodeAttributes Extensible Parameter NodeAttributes The Attributes that are specific to the NodeClass . The NodeAttributes parameter type is an extensible parameter type specified ... Client is allowed to omit values for some or all Attributes . If an Attribute value is null, the Server shall use the default values from the TypeDefinitionNode . If a TypeDefinitionNode
• OPC-10000-4 – OPC Unified Architecture - Part 4: Services
  5.8.2.4 StatusCodes
  among nodes that share the same relationship with the parent. Bad_NodeAttributesInvalid The node Attributes are not valid for the node class. Bad_TypeDefinitionInvalid See Table 179 for the description
• OPC-10000-4 – OPC Unified Architecture - Part 4: Services
  5.11.1 Overview
  Overview This Service Set provides Services to access Attributes that are part of Nodes
• OPC-10000-4 – OPC Unified Architecture - Part 4: Services
  5.11.2.1 Description
  Description This Service is used to read one or more Attributes of one or more Nodes . For constructed Attribute values whose elements are indexed, such as an array, this Service
• OPC-10000-4 – OPC Unified Architecture - Part 4: Services
  5.11.2.2 Parameters
  TimestampsToReturn enumeration is defined in 7.39 . nodesToRead [] ReadValueId List of Nodes and their Attributes to read. For each entry in this list, a StatusCode is returned, and if it indicates
• OPC-10000-4 – OPC Unified Architecture - Part 4: Services
  5.11.4.1 Description
  Description This Service is used to write values to one or more Attributes of one or more Nodes . For constructed Attribute values whose elements are indexed, such as an array ... needs separate Service calls. It is possible that the Server may successfully write some Attributes , but not others. Rollback is the responsibility of the Client . If a Server allows writing
• OPC-10000-4 – OPC Unified Architecture - Part 4: Services
  5.11.4.2 Parameters
  request parameters (see 7.32 for RequestHeader definition). nodesToWrite [] WriteValue List of Nodes and their Attributes to write. This structure is defined in-line with the following indented items. nodeId NodeId ... NodeId of the Node that contains the Attributes . attributeId IntegerId Id of the Attribute . This shall be a valid Attribute id. The IntegerId is defined in 7.19 . The IntegerIds
• OPC-10000-4 – OPC Unified Architecture - Part 4: Services
  5.13.1.1 Overview
  filter and the queue parameter. Figure 15 illustrates these concepts. Figure 15 - MonitoredItem model Attributes , other than the Value Attribute , are only monitored for a change in value. The filter ... used for these Attributes . Any change in value for these Attributes causes a Notification to be generated. The Value Attribute is used when monitoring Variables . Variable values are monitored
• OPC-10000-4 – OPC Unified Architecture - Part 4: Services
  5.13.2.2 Parameters
  IntegerId definition). timestampsToReturn Enum Timestamps ToReturn An enumeration that specifies the timestamp Attributes to be transmitted for each MonitoredItem . The TimestampsToReturn enumeration is defined in 7.39 . When monitoring Events , this
• OPC-10000-4 – OPC Unified Architecture - Part 4: Services
  5.13.3.2 Parameters
  IntegerId definition). timestampsToReturn Enum Timestamps ToReturn An enumeration that specifies the timestamp Attributes to be transmitted for each MonitoredItem to be modified. The TimestampsToReturn enumeration is defined in 7.39 . When
• OPC-10000-4 – OPC Unified Architecture - Part 4: Services
  7.7.4.5 SimpleAttributeOperand
  Value Attribute shall be supported by all Servers . The support of other Attributes depends on requirements set in Profiles or other parts of this specification. indexRange NumericRange This parameter
• OPC-10000-4 – OPC Unified Architecture - Part 4: Services
  7.11.3 SourceTimestamp
  uncertain status. The sourceTimestamp is only returned with a Value Attribute . For all other Attributes the returned sourceTimestamp is set to null
• OPC-10000-4 – OPC Unified Architecture - Part 4: Services
  7.22.3 EventFilter
  Nodes . That said, profiles defined in OPC 10000-7 may make support for additional Attributes mandatory. The SimpleAttributeOperand structure is used in the selectClauses to select the value to return
• OPC-10000-4 – OPC Unified Architecture - Part 4: Services
  7.24.1 Overview
  Overview The AddNodes Service allows specifying the Attributes for the Nodes to add. The NodeAttributes is an extensible parameter whose structure depends on the type of the NodeClass being added ... identifies the NodeClass that defines the structure of the Attributes that follow. The parameterTypeIds are defined in Table 149 . The ExtensibleParameter type is defined in 7.17 . Table 149 - NodeAttributes parameterTypeIds
• OPC-10000-4 – OPC Unified Architecture - Part 4: Services
  7.24.2 ObjectAttributes parameter
  defines the ObjectAttributes parameter. Table 151 - ObjectAttributes Name Type Description ObjectAttributes structure Defines the Attributes for the Object NodeClass. specifiedAttributes UInt32 A bit mask that indicates which fields contain valid
• OPC-10000-4 – OPC Unified Architecture - Part 4: Services
  7.24.3 VariableAttributes parameter
  defines the VariableAttributes parameter. Table 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
• OPC-10000-4 – OPC Unified Architecture - Part 4: Services
  7.24.4 MethodAttributes parameter
  defines the MethodAttributes parameter. Table 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
• OPC-10000-4 – OPC Unified Architecture - Part 4: Services
  7.24.5 ObjectTypeAttributes parameter
  defines the ObjectTypeAttributes parameter. Table 154 - ObjectTypeAttributes Name Type Description ObjectTypeAttributes structure Defines the Attributes for the ObjectType NodeClass. specifiedAttributes UInt32 A bit mask that indicates which fields contain valid
• OPC-10000-4 – OPC Unified Architecture - Part 4: Services
  7.24.6 VariableTypeAttributes parameter
  defines the VariableTypeAttributes parameter. Table 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
• OPC-10000-4 – OPC Unified Architecture - Part 4: Services
  7.24.7 ReferenceTypeAttributes parameter
  defines the ReferenceTypeAttributes parameter. Table 156 - ReferenceTypeAttributes Name Type Description ReferenceTypeAttributes structure Defines the Attributes for the ReferenceType NodeClass. specifiedAttributes UInt32 A bit mask that indicates which fields contain valid
• OPC-10000-4 – OPC Unified Architecture - Part 4: Services
  7.24.8 DataTypeAttributes parameter
  defines the DataTypeAttributes parameter. Table 157 - DataTypeAttributes Name Type Description DataTypeAttributes structure Defines the Attributes for the DataType NodeClass. specifiedAttributes UInt32 A bit mask that indicates which fields contain valid
• OPC-10000-4 – OPC Unified Architecture - Part 4: Services
  7.24.9 ViewAttributes parameter
  defines the ViewAttributes parameter. Table 158 - ViewAttributes Name Type Description ViewAttributes structure Defines the Attributes for the View NodeClass. specifiedAttributes UInt32 A bit mask that indicates which fields contain valid
• OPC-10000-4 – OPC Unified Architecture - Part 4: Services
  7.24.10 GenericAttributes parameter
  other sub sections of 7.24 since it allows the handling of additional Attributes defined in future specification versions. Table 159 defines the GenericAttributes parameter. Table 159 - GenericAttributes Name Type Description ... GenericAttributes structure Defines a generic structure for passing in any number of Attributes. specifiedAttributes UInt32 A bit mask that indicates which fields contain valid values. A field shall be ignored
• OPC-10000-4 – OPC Unified Architecture - Part 4: Services
  7.39 TimestampsToReturn
  TimestampsToReturn The TimestampsToReturn is an enumeration that specifies the Timestamp Attributes to be transmitted for MonitoredItems or Nodes in Read and HistoryRead . The values of this parameter are defined
• OPC-10000-4 – OPC Unified Architecture - Part 4: Services
  B.2.1 Overview
  instances of one or more TypeDefinitionNodes in the AddressSpace should supply a set of Attributes . Results returned by a Server are in the form of an array of QueryDataSets ... TypeDefinitionNodes or related TypeDefinitionNodes and appear in results in the same order as the Attributes that were passed into the Query . Query also supports Node filtering on the basis
• OPC-10000-4 – OPC Unified Architecture - Part 4: Services
  B.2.2 Querying Views
  time and the latter is used to Query for the value of Attributes over time. In this way, a Query can be used to retrieve a portion of a past
• OPC-10000-4 – OPC Unified Architecture - Part 4: Services
  B.2.3 QueryFirst
  array of NodeTypeDescription which specify the NodeId of a TypeDefinitionNode and selects what Attributes are to be returned in the response. A Client can also provide a set of RelativePaths ... starting from an originating TypeDefinitionNode . Using these paths, the Client selects a set of Attributes from Nodes that are related to instances of the originating TypeDefinitionNode . Additionally, the Client
• OPC-10000-5 – OPC Unified Architecture - Part 5: Information Model
  3.3 Conventions for Node descriptions
  Conventions for Node descriptions Node definitions are specified using tables (see Table 2 ). Attributes are defined by providing the Attribute name and a value, or a description of the value ... TargetNode is a component of the Node being defined in the table, the Attributes of the composed Node are defined in the same row of the table. The DataType
• OPC-10000-5 – OPC Unified Architecture - Part 5: Information Model
  5.1 General
  General For all Nodes specified in NamespaceIndex 0, the Attributes named in Table 3 shall be set as specified in Table 3 . Table 3 - Common Node Attributes Attribute Value DisplayName ... provided. If the WriteMask Attribute is provided, it shall set all non-server-specific Attributes to not writable. For example, the Description Attribute may be set to writable since
• OPC-10000-5 – OPC Unified Architecture - Part 5: Information Model
  5.2 Objects
  Objects For all Objects specified in NamespaceIndex 0, the Attributes named in Table 4 shall be set as specified in Table 4 . Table 4 - Common Object Attributes Attribute Value EventNotifier
• OPC-10000-5 – OPC Unified Architecture - Part 5: Information Model
  5.3 Variables
  Variables For all Variables specified in NamespaceIndex 0, the Attributes named in Table 5 shall be set as specified in Table 5 . Table 5 - Common Variable Attributes Attribute Value MinimumSamplingInterval
• OPC-10000-5 – OPC Unified Architecture - Part 5: Information Model
  5.4 VariableTypes
  VariableTypes For all VariableTypes specified in NamespaceIndex 0, the Attributes named in Table 6 shall be set as specified in Table 6 . Table 6 - Common VariableType Attributes Attributes Value Value
• OPC-10000-5 – OPC Unified Architecture - Part 5: Information Model
  5.5 Methods
  Methods For all Methods specified in NamespaceIndex 0, the Attributes named in Table 7 shall be set as specified in Table 7 . Table 7 - Common Method Attributes Attributes Value Executable
• OPC-10000-5 – OPC Unified Architecture - Part 5: Information Model
  6.3.12 AddressSpaceFileType
  namespace from the Server AddressSpace to the XML file represented by the AddressSpaceFileType . Value Attributes are only exported if they represent static configuration information. The client is expected to call
• OPC-10000-5 – OPC Unified Architecture - Part 5: Information Model
  6.3.13 NamespaceMetadataType
  then this Property shall be set to TRUE. Static Nodes are identical for all Attributes in all Servers , including the Value Attribute . For TypeDefinitionNodes , also the InstanceDeclarations shall be identical
• OPC-10000-6 – OPC Unified Architecture - Part 6: Mappings
  5.1.9 Variant
  table of strings. As a result, Variants cannot contain instances of DiagnosticInfo. Values of Attributes are always returned in instances of DataValues . Therefore, the DataType of an Attribute cannot
• OPC-10000-6 – OPC Unified Architecture - Part 6: Mappings
  F.2 UANodeSet
  UANodeSet is the root of the document. It defines a set of Nodes , their Attributes and References . References to Nodes outside of the document are allowed. The structure
• OPC-10000-6 – OPC Unified Architecture - Part 6: Mappings
  F.3 UANode
  abstract base type for all Nodes . It defines 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 for the OPC UA Attributes specific to the NodeClass . The fields in the UANode type are defined in Table F.2 . Table F.2 - UANode Element
• OPC-10000-8 – OPC Unified Architecture - Part 8: Data Access
  1 Scope
  Access (DA). It particularly includes additional VariableTypes and complementary descriptions of the NodeClasses and Attributes needed for Data Access, additional Properties , and other information and behaviour. The complete address space ... model, including all NodeClasses and Attributes is specified in OPC 10000-3 . The services to detect and access data are specified in OPC 10000-4 . Annex A specifies
• OPC-10000-8 – OPC Unified Architecture - Part 8: Data Access
  5.3.4.2 YArrayItemType
  XAxisDefinition (see 5.2 for additional information). Figure 3 shows an example of how Attributes and Properties can be used in a graphical interface. Figure 3 - Graphical view of a YArrayItem
• OPC-10000-8 – OPC Unified Architecture - Part 8: Data Access
  5.4 Address Space model
  specific. The above figure shows only a subset of Attribute s and Properties . Other Attributes that are defined for Variable s in OPC 10000-3 (e.g., Description ) can also
• OPC-10000-8 – OPC Unified Architecture - Part 8: Data Access
  6.4.3 SyntaxReferenceEntryType ObjectType definition
  corresponding field in Table 38 . The namespace for the NodeId and the BrowseName Attributes of instances of the SyntaxReferenceEntryType shall be the URI of the Syntax Reference as defined
• OPC-10000-8 – OPC Unified Architecture - Part 8: Data Access
  7.1 General
  detect DataItems , and their Properties . The Attribute service set to read or write Attributes and in particular the value Attribute . The MonitoredItem and Subscription service set to set up monitoring
• OPC-10000-9 – OPC Unified Architecture - Part 9: Alarms & Conditions
  5.5.2 ConditionType
  Condition instance is disabled. For any Condition that exists in the AddressSpace the Attributes and the following Variables will continue to have valid values even in the Disable d state
• OPC-10000-9 – OPC Unified Architecture - Part 9: Alarms & Conditions
  5.8.17.1 Overview
  HasCause True TimedShelve HasCause True TimedShelve2 The component Variables of the ShelvedStateMachineType have additional Attributes defined in Table 75 . Table 75 - ShelvedStateMachineType Attribute values for child Nodes BrowsePath Value Attribute
• OPC-10000-9 – OPC Unified Architecture - Part 9: Alarms & Conditions
  5.8.19.2 ExclusiveLimitStateMachineType
  ToState True LowLow HasEffect True AlarmConditionType The component Variables of the ExclusiveLimitStateMachineType have additional Attributes defined in Table 95 . Table 95 - ExclusiveLimitStateMachineType Attribute values for child Nodes BrowsePath Value Attribute
• OPC-10000-9 – OPC Unified Architecture - Part 9: Alarms & Conditions
  D.2.5 Event subscriptions
  Server . A simple A&E COM UA Wrapper will always request all Attributes for all Event Categories when creating the Subscription . A more sophisticated wrapper may look ... EventFilter to determine which Attributes are actually used and only request those. Table D.2 lists how the fields in the ONEVENTSTRUCT that are used
• OPC-10000-9 – OPC Unified Architecture - Part 9: Alarms & Conditions
  D.3.5 Event Category attribute mapping
  condition-related events which are acknowledgement notifications szActorID Vendor specific Attributes - ALL ACK Comment AREAS All A&E Events are assumed to support the "Areas" Attribute. However ... Figure D.4 - Example mapping of UA Event Types to A&E categories with attributes
• OPC-10000-9 – OPC Unified Architecture - Part 9: Alarms & Conditions
  F.2 SystemStateStateMachineType
  ToState True Maintenance HasCause True Maintain The component Variables of the SystemStateStateMachineType have additional Attributes defined in Table F . 3 . Table F. 3 - SystemStateStateMachineType Attribute values for child Nodes BrowsePath
• OPC-10000-10 – OPC Unified Architecture - Part 10: Programs
  1 Scope
  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 to invoke
• OPC-10000-10 – OPC Unified Architecture - Part 10: Programs
  5.2.1 Overview
  ProgramStateMachineType specific semantics are assigned to the other base ObjectType or FiniteStateMachineType Attributes or Properties . Table 5 - ProgramStateMachineType Attribute Value Includes all attributes specified for the FiniteStateMachineType BrowseName ProgramStateMachineType IsAbstract ... BaseObjectType O Conformance Units Program Basic The component Variables of the ProgramStateMachineType have additional Attributes defined in Table 6 . Table 6 - ProgramStateMachineType Attribute values for child Nodes BrowsePath Value Attribute
• OPC-10000-10 – OPC Unified Architecture - Part 10: Programs
  A.2.6.2 DomainDownloadType
  which it does not support. Table A.2 - DomainDownloadType Attribute Value Includes all non-optional attributes specified for the ProgramStateMachineType BrowseName DomainDownloadType IsAbstract False References NodeClass BrowseName Data Type TypeDefinition Modelling ... substates for the Program's Running StateType . Table A.3 - TransferStateMachineType Attribute Value Includes all attributes specified for the FiniteStateMachineType BrowseName TransferStateMachineType IsAbstract False References NodeClass BrowseName Data Type TypeDefinition Modelling
• OPC-10000-11 – OPC Unified Architecture - Part 11: Historical Access
  1 Scope
  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. The 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 and access historical
• OPC-10000-11 – OPC Unified Architecture - Part 11: Historical Access
  5.2.3 Attributes
  Attributes Subclause 5.2.6 lists the Attributes of Variables that have particular importance for historical data. They are specified in detail in OPC 10000-3 . AccessLevel Historizing
• OPC-10000-11 – OPC Unified Architecture - Part 11: Historical Access
  5.4.4 HistoricalEventNode Attributes
  HistoricalEventNode Attributes The Attributes of Objects or Views that have importance for historical Events are specified in detail in OPC 10000-3 . The following Attributes are particularly important
• OPC-10000-11 – OPC Unified Architecture - Part 11: Historical Access
  5.5.2 External Historical Event Node
  ConformanceUnits Historical Access External Event Source All instances of HistoricalExternalEventSourceType shall set the Object Attributes bits as described in 5.4.4 . An instance of this ObjectType can also have a HasHistoricalConfiguration
• OPC-10000-11 – OPC Unified Architecture - Part 11: Historical Access
  5.6.2 HistoricalDataNodes Address Space Model
  details on use of this Attribute ). Figure 3 only shows a subset of Attributes and Properties . Other Attributes that are defined for Variables in OPC 10000-3 , can also
• OPC-10000-11 – OPC Unified Architecture - Part 11: Historical Access
  6.9.1 Overview
  support the capability to update entries. See OPC 10000-3 for a description of Attributes that expose the support of Historical Updates. If the HistoryUpdate Service is called with
• OPC-10000-12 – OPC Unified Architecture - Part 12: Discovery and Global Services
  10.1 Namespace Metadata
  namespace and an indication about static Nodes . Static Nodes are identical for all Attributes in all Servers , including the Value Attribute . See OPC 10000-5 for more details. The information
• OPC-10000-12 – OPC Unified Architecture - Part 12: Discovery and Global Services
  10.2 Handling of OPC UA Namespaces
  used by OPC UA to create unique identifiers across different naming authorities. The Attributes NodeId and BrowseName are identifiers. A Node in the UA AddressSpace is unambiguously identified using
• OPC-10000-12 – OPC Unified Architecture - Part 12: Discovery and Global Services
  E.3 LDAP
  objects organized into hierarchies. Each object has an objectClass which specifies a number of attributes . Attributes have values which describe an object . Figure E.3 illustrates a sample LDAP hierarchy which ... used with any LDAP implementation. Administrators may extend the LDAP schema by adding new attributes
• OPC-10000-13 – OPC Unified Architecture - Part 13: Aggregates
  4.2.2.2 AggregateFunctionType
  provides a localized description of the Aggregate . Table 5 specifies the BrowseName and Description Attributes for the standard Aggregate Objects . The description is the localized "en" text
• OPC-10000-14 – OPC Unified Architecture - Part 14: PubSub
  6.2.3.7.1 PublishedData
  publish e.g. the Value Attribute . This shall be a valid Attribute id. The Attributes are defined in OPC 10000-3 . The IntegerId DataType is defined ... IntegerIds for the Attributes are defined in OPC 10000-6 . SamplingIntervalHint Duration A recommended rate of acquiring new values for change or deadband evaluation. A Publisher should use this value
• OPC-10000-14 – OPC Unified Architecture - Part 14: PubSub
  6.2.10.2.3 FieldTargetDataType
  Attribute to write e.g. the Value Attribute . This shall be a valid AttributeId . The Attributes are defined in OPC 10000-3 . The IntegerId DataType is defined ... IntegerIds for the Attributes are defined in OPC 10000-6 . WriteIndexRange NumericRange The index range used for writing received data to the target node. It is used to identify
• OPC-10000-19 – OPC Unified Architecture - Part 19: Dictionary Reference
  5.3 IRDI ISO/IEC 11179-6 conformant DictionaryEntryType
  unique string. This identifier is used for the NodeId and the BrowseName Attributes of instances of the DictionaryEntryType . The IdentifierType of the NodeId shall be STRING_1 with the identifier
• OPC-10000-19 – OPC Unified Architecture - Part 19: Dictionary Reference
  5.4 URI based dictionary entry type
  unique URI string. This identifier is used for the NodeId and the BrowseName Attributes of instances of the DictionaryEntryType . The IdentifierType of the NodeId shall be STRING_1 with
• OPC-10000-20 – OPC Unified Architecture - Part 20: File Transfer
  4.4.6 FileTransferStateMachineType
  Conformance Units Base Info TemporaryFileTransferType Base The component Variables of the FileTransferStateMachineType have additional Attributes defined in Table 18 . Table 18 - FileTransferStateMachineType Attribute values for child Nodes Source Path Value
• OPC-10000-21 – OPC Unified Architecture - Part 21: Device Onboarding
  10.1 Namespace Metadata
  namespace and an indication about static Nodes . Static Nodes are identical for all Attributes in all Servers , including the Value Attribute . See OPC 10000-5 for more details. The information
• OPC-10000-21 – OPC Unified Architecture - Part 21: Device Onboarding
  10.2 Handling of OPC UA Namespaces
  used by OPC UA to create unique identifiers across different naming authorities. The Attributes NodeId and BrowseName are identifiers. A Node in the UA AddressSpace is unambiguously identified using
• OPC-10000-24 – OPC Unified Architecture - Part 24: Scheduler
  10.1 Namespace Metadata
  namespace and an indication about static Nodes . Static Nodes are identical for all Attributes in all Servers , including the Value Attribute . See OPC 10000-5 for more details. The information
• OPC-10000-24 – OPC Unified Architecture - Part 24: Scheduler
  10.2 Handling of OPC UA Namespaces
  used by OPC UA to create unique identifiers across different naming authorities. The Attributes NodeId and BrowseName are identifiers. A Node in the UA AddressSpace is unambiguously identified using
• OPC-10000-25 – OPC Unified Architecture - Part 25: Object Serialization
  4.5 General Features
  NonatomicRead and NonatomicWrite flags of the AccessLevelExType part of the SerializedData Variable's Attributes are set to 1 ( Server specific, see OPC 10000-3 ). When writing of the SerializationValue with
• OPC-10000-81 – OPC Unified Architecture - Part 81: UAFX Connecting Devices and Information Model
  6.8.1 Overview
  users or in general. This can be determined by examining the AccessLevel and UserAccessLevel Attributes of the data. With these mechanisms, the generator of the ConnectionConfigurationSet can specify and restrict
• OPC-10000-81 – OPC Unified Architecture - Part 81: UAFX Connecting Devices and Information Model
  6.9.2 ConnectionConfigurationSetStateMachineType definition
  ProcessConnectionConfigurationSets 0:HasEffect True 4:ConnectionConfigurationSetProcessingStartedEventType The component Variables of the ConnectionConfigurationSetStateMachineType have additional Attributes defined in Table 93 . Table 93 - ConnectionConfigurationSetStateMachineType attribute values for child Nodes BrowsePath Value Attribute
• OPC-10000-81 – OPC Unified Architecture - Part 81: UAFX Connecting Devices and Information Model
  14.1 Namespace metadata
  namespaces and an indication of static Nodes . Static Nodes are identical for all Attributes in all Servers , including the Value Attribute . See OPC 10000-5 for more details. The information
• OPC-10000-81 – OPC Unified Architecture - Part 81: UAFX Connecting Devices and Information Model
  14.2 Handling of OPC UA namespaces
  namespaces OPC UA uses namespaces to create unique identifiers across different naming authorities. The Attributes NodeId and BrowseName are identifiers. A Node in the UA AddressSpace is unambiguously identified using
• OPC-10000-100 – OPC Unified Architecture - Part 100: Devices
  3.3.1.1 Node definitions
  Node definitions Node definitions are specified using tables (see Table 2 ). Attributes are defined by providing the Attribute name and a value, or a description of the value. References ... TargetNode is a component of the Node being defined in the table the Attributes of the composed Node are defined in the same row of the table. The DataType
• OPC-10000-100 – OPC Unified Architecture - Part 100: Devices
  3.3.1.4 Additional Attribute values
  values The type definition table provides columns to specify the values for required Node Attributes for InstanceDeclarations . To provide information about additional Attributes , the format as shown in Table ... Multiple elements are defined as separate rows of a nested table The values of Attributes are converted to text by adapting the reversible JSON encoding rules defined
• OPC-10000-100 – OPC Unified Architecture - Part 100: Devices
  3.3.3.1 General
  General The Attributes of Nodes , their DataTypes and descriptions are defined in OPC 10000-3 . Attributes not marked as optional are mandatory and shall be provided by a Server ... server-specific. For all Nodes specified in this document, the Attributes named in Table 7 shall be set as specified in the table. Table 7 - Common Node Attributes Attribute Value
• OPC-10000-100 – OPC Unified Architecture - Part 100: Devices
  3.3.3.2 Objects
  Objects For all Objects specified in this document, the Attributes named in Table 8 shall be set as specified in the Table 8 . The definitions for the Attributes ... found in OPC 10000-3 . Table 8 - Common Object Attributes Attribute Value EventNotifier Whether the Node can be used to subscribe to Events or not is server-specific
• OPC-10000-100 – OPC Unified Architecture - Part 100: Devices
  3.3.3.3 Variables
  Variables For all Variables specified in this document, the Attributes named in Table 9 shall be set as specified in the table. The definitions for the Attributes can be found ... Table 9 - Common Variable Attributes Attribute Value MinimumSamplingInterval Optionally, a server-specific minimum sampling interval is provided. AccessLevel The access level for Variables used for type definitions is server-specific
• OPC-10000-100 – OPC Unified Architecture - Part 100: Devices
  3.3.3.4 VariableTypes
  VariableTypes For all VariableTypes specified in this document, the Attributes named in Table 10 shall be set as specified in the table. The definitions for the Attributes can be found ... Table 10 - Common VariableType Attributes Attributes Value Value Optionally a server-specific default value can be provided. ArrayDimensions If the ValueRank does not identify an array of a specific dimension
• OPC-10000-100 – OPC Unified Architecture - Part 100: Devices
  3.3.3.5 Methods
  Methods For all Methods specified in this document, the Attributes named in Table 11 shall be set as specified in the table. The definitions for the Attributes can be found ... Table 11 - Common Method Attributes Attributes Value Executable All Methods defined in this document shall be executable ( Executable Attribute set to "True"), unless it is defined differently
• OPC-10000-100 – OPC Unified Architecture - Part 100: Devices
  8.4.8.1 Overview
  TransitionType Conformance Units DI SU PrepareForUpdate The component Variables of the PrepareForUpdateStateMachineType have additional Attributes defined in Table 92 . Table 92 - 1:PrepareForUpdateStateMachineType Attribute values for child Nodes BrowsePath Value
• OPC-10000-100 – OPC Unified Architecture - Part 100: Devices
  8.4.9.1 Overview
  Conformance Units DI SU Software Update The component Variables of the InstallationStateMachineType have additional Attributes defined in Table 95 . Table 95 - 1:InstallationStateMachineType Attribute values for child Nodes BrowsePath Value
• OPC-10000-100 – OPC Unified Architecture - Part 100: Devices
  8.4.10 PowerCycleStateMachineType
  Units DI SU Manual Power Cycle The component Variables of the PowerCycleStateMachineType have additional Attributes defined in Table 102 . Table 102 - 1:PowerCycleStateMachineType Attribute values for child Nodes BrowsePath Value
• OPC-10000-100 – OPC Unified Architecture - Part 100: Devices
  8.4.11.1 Overview
  Conformance Units DI SU Update Confirmation The component Variables of the ConfirmationStateMachineType have additional Attributes defined in Table 105 . Table 105 - 1:ConfirmationStateMachineType Attribute values for child Nodes BrowsePath Value
• OPC-10000-100 – OPC Unified Architecture - Part 100: Devices
  12.1 Namespace Metadata
  namespace and an indication about static Nodes . Static Nodes are identical for all Attributes in all Servers , including the Value Attribute . See OPC 10000-5 for more details. The information
• OPC-10000-100 – OPC Unified Architecture - Part 100: Devices
  12.2 Handling of OPC UA namespaces
  used by OPC UA to create unique identifiers across different naming authorities. The Attributes NodeId and BrowseName are identifiers. A Node in the UA AddressSpace is unambiguously identified using
• OPC-10000-110 – OPC Unified Architecture - Part 110: Asset Management Basics
  3.3.1.1 Node definitions
  Node definitions Node definitions are specified using tables (see Table 2 ). Attributes are defined by providing the Attribute name and a value, or a description of the value. References ... TargetNode is a component of the Node being defined in the table the Attributes of the composed Node are defined in the same row of the table. The DataType
• OPC-10000-110 – OPC Unified Architecture - Part 110: Asset Management Basics
  3.3.1.4 Additional Attribute values
  values The type definition table provides columns to specify the values for required Node Attributes for InstanceDeclarations . To provide information about additional Attributes , the format as shown in Table ... Multiple elements are defined as separate rows of a nested table The values of attributes are converted to text by adapting the reversible JSON encoding rules defined
• OPC-10000-110 – OPC Unified Architecture - Part 110: Asset Management Basics
  3.3.3.1 General
  General The Attributes of Nodes , their DataTypes and descriptions are defined in OPC 10000-3 . Attributes not marked as optional are mandatory and shall be provided by a Server ... server-specific. For all Nodes specified in this document, the Attributes named in Table 7 shall be set as specified in the table. Table 7 - Common Node Attributes Attribute Value
• OPC-10000-110 – OPC Unified Architecture - Part 110: Asset Management Basics
  3.3.3.2 Objects
  Objects For all Objects specified in this document, the Attributes named in Table 8 shall be set as specified in the Table 8 . The definitions for the Attributes ... found in OPC 10000-3 . Table 8 - Common Object Attributes Attribute Value EventNotifier Whether the Node can be used to subscribe to Events or not is server-specific
• OPC-10000-110 – OPC Unified Architecture - Part 110: Asset Management Basics
  3.3.3.3 Variables
  Variables For all Variables specified in this document, the Attributes named in Table 9 shall be set as specified in the table. The definitions for the Attributes can be found ... Table 9 - Common Variable Attributes Attribute Value MinimumSamplingInterval Optionally, a server-specific minimum sampling interval is provided. AccessLevel The access level for Variables used for type definitions is server-specific
• OPC-10000-110 – OPC Unified Architecture - Part 110: Asset Management Basics
  3.3.3.4 VariableTypes
  VariableTypes For all VariableTypes specified in this document, the Attributes named in Table 10 shall be set as specified in the table. The definitions for the Attributes can be found ... Table 10 - Common VariableType Attributes Attributes Value Value Optionally a server-specific default value can be provided. ArrayDimensions If the ValueRank does not identify an array of a specific dimension
• OPC-10000-110 – OPC Unified Architecture - Part 110: Asset Management Basics
  3.3.3.5 Methods
  Methods For all Methods specified in this document, the Attributes named in Table 11 shall be set as specified in the table. The definitions for the Attributes can be found ... Table 11 - Common Method Attributes Attributes Value Executable All Methods defined in this document shall be executable ( Executable Attribute set to "True"), unless it is defined differently
• OPC-10000-110 – OPC Unified Architecture - Part 110: Asset Management Basics
  10.5.2 DocumentationLinksType
  links provided by instances of this type. The components of the DocumentationLinksType have additional Attributes defined in Table 30 . Table 30 - DocumentationLinksType Attribute values for child Nodes BrowsePath Value Attribute
• OPC-10000-110 – OPC Unified Architecture - Part 110: Asset Management Basics
  10.5.3 AddLink Method
  writable. Servers might restrict the execution of this Method as well as writing the Attributes to specific users / roles. The signature of this Method is specified below. Table
• OPC-10000-110 – OPC Unified Architecture - Part 110: Asset Management Basics
  12.3 MaintenanceEventStateMachineType
  FromState True Finished 0:ToState True Planned The components of the MaintenanceEventStateMachineType have additional Attributes defined in Table 39 . Table 39 - MaintenanceEventStateMachineType Attribute values for child Nodes BrowsePath Value Attribute
• OPC-10000-110 – OPC Unified Architecture - Part 110: Asset Management Basics
  16.1 Namespace Metadata
  namespace and an indication about static Nodes . Static Nodes are identical for all Attributes in all Servers , including the Value Attribute . See OPC 10000-5 for more details. The information
• OPC-10000-110 – OPC Unified Architecture - Part 110: Asset Management Basics
  16.2 Handling of OPC UA Namespaces
  used by OPC UA to create unique identifiers across different naming authorities. The Attributes NodeId and BrowseName are identifiers. A Node in the UA AddressSpace is unambiguously identified using
• OPC-10000-120 – OPC Unified Architecture - Part 120: OPC UA and XML Data Type Mapping
  3.3.1.1 Node definitions
  Node definitions Node definitions are specified using tables (see Table 2 ). Attributes are defined by providing the Attribute name and a value, or a description of the value. References ... TargetNode is a component of the Node being defined in the table the Attributes of the composed Node are defined in the same row of the table. The DataType
• OPC-10000-120 – OPC Unified Architecture - Part 120: OPC UA and XML Data Type Mapping
  3.3.1.4 Additional Attribute values
  values The type definition table provides columns to specify the values for required Node Attributes for InstanceDeclarations . To provide information about additional Attributes , the format as shown in Table ... Multiple elements are defined as separate rows of a nested table The values of attributes are converted to text by adapting the reversible JSON encoding rules defined
• OPC-10000-120 – OPC Unified Architecture - Part 120: OPC UA and XML Data Type Mapping
  3.3.3.1 General
  General The Attributes of Nodes , their DataTypes and descriptions are defined in OPC 10000-3 . Attributes not marked as optional are mandatory and shall be provided by a Server ... server-specific. For all Nodes specified in this document, the Attributes named in Table 7 shall be set as specified in the table. Table 7 - Common Node Attributes Attribute Value
• OPC-10000-120 – OPC Unified Architecture - Part 120: OPC UA and XML Data Type Mapping
  3.3.3.2 Objects
  Objects For all Objects specified in this document, the Attributes named in Table 8 shall be set as specified in the Table 8 . The definitions for the Attributes ... found in OPC 10000-3 . Table 8 - Common Object Attributes Attribute Value EventNotifier Whether the Node can be used to subscribe to Events or not is server-specific
• OPC-10000-120 – OPC Unified Architecture - Part 120: OPC UA and XML Data Type Mapping
  3.3.3.3 Variables
  Variables For all Variables specified in this document, the Attributes named in Table 9 shall be set as specified in the table. The definitions for the Attributes can be found ... Table 9 - Common Variable Attributes Attribute Value MinimumSamplingInterval Optionally, a server-specific minimum sampling interval is provided. AccessLevel The access level for Variables used for type definitions is server-specific
• OPC-10000-120 – OPC Unified Architecture - Part 120: OPC UA and XML Data Type Mapping
  3.3.3.4 VariableTypes
  VariableTypes For all VariableTypes specified in this document, the Attributes named in Table 10 shall be set as specified in the table. The definitions for the Attributes can be found ... Table 10 - Common VariableType Attributes Attributes Value Value Optionally a server-specific default value can be provided. ArrayDimensions If the ValueRank does not identify an array of a specific dimension
• OPC-10000-120 – OPC Unified Architecture - Part 120: OPC UA and XML Data Type Mapping
  3.3.3.5 Methods
  Methods For all Methods specified in this document, the Attributes named in Table 11 shall be set as specified in the table. The definitions for the Attributes can be found ... Table 11 - Common Method Attributes Attributes Value Executable All Methods defined in this document shall be executable ( Executable Attribute set to "True"), unless it is defined differently
• OPC-10000-120 – OPC Unified Architecture - Part 120: OPC UA and XML Data Type Mapping
  8.1 Namespace Metadata
  namespace and an indication about static Nodes . Static Nodes are identical for all Attributes in all Servers , including the Value Attribute . See OPC 10000-5 for more details. The information
• OPC-10000-120 – OPC Unified Architecture - Part 120: OPC UA and XML Data Type Mapping
  8.2 Handling of OPC UA Namespaces
  used by OPC UA to create unique identifiers across different naming authorities. The Attributes NodeId and BrowseName are identifiers. A Node in the UA AddressSpace is unambiguously identified using
• OPC-10000-200 – OPC Unified Architecture - Part 200: Industrial Automation
  3.3.1 Conventions for Node descriptions
  Conventions for Node descriptions Node definitions are specified using tables (see Table 2 ). Attributes are defined by providing the Attribute name and a value, or a description of the value ... TargetNode is a component of the Node being defined in the table the Attributes of the composed Node are defined in the same row of the table. The DataType
• OPC-10000-200 – OPC Unified Architecture - Part 200: Industrial Automation
  3.3.1.3 Additional Attribute values
  values The type definition table provides columns to specify the values for required Node Attributes for InstanceDeclarations . To provide information about additional Attributes , the format as shown in Table ... Multiple elements are defined as separate rows of a nested table The values of attributes are converted to text by adapting the reversible JSON encoding rules defined
• OPC-10000-200 – OPC Unified Architecture - Part 200: Industrial Automation
  3.3.3.1 General
  General The Attributes of Nodes , their DataTypes and descriptions are defined in OPC 10000-3 . Attributes not marked as optional are mandatory and shall be provided by a Server ... server-specific. For all Nodes specified in this document, the Attributes named in Table 7 shall be set as specified in the table. Table 7 - Common Node Attributes Attribute Value
• OPC-10000-200 – OPC Unified Architecture - Part 200: Industrial Automation
  3.3.3.2 Objects
  Objects For all Objects specified in this document, the Attributes named in Table 8 shall be set as specified in the Table 8 . The definitions for the Attributes ... found in OPC 10000-3 . Table 8 - Common Object Attributes Attribute Value EventNotifier Whether the Node can be used to subscribe to Events or not is server-specific
• OPC-10000-200 – OPC Unified Architecture - Part 200: Industrial Automation
  3.3.3.3 Variables
  Variables For all Variables specified in this document, the Attributes named in Table 9 shall be set as specified in the table. The definitions for the Attributes can be found ... Table 9 - Common Variable Attributes Attribute Value MinimumSamplingInterval Optionally, a server-specific minimum sampling interval is provided. AccessLevel The access level for Variables used for type definitions is server-specific
• OPC-10000-200 – OPC Unified Architecture - Part 200: Industrial Automation
  3.3.3.4 VariableTypes
  VariableTypes For all VariableTypes specified in this document, the Attributes named in Table 10 shall be set as specified in the table. The definitions for the Attributes can be found ... Table 10 - Common VariableType Attributes Attributes Value Value Optionally a server-specific default value can be provided. ArrayDimensions If the ValueRank does not identify an array of a specific dimension
• OPC-10000-200 – OPC Unified Architecture - Part 200: Industrial Automation
  3.3.3.5 Methods
  Methods For all Methods specified in this document, the Attributes named in Table 11 shall be set as specified in the table. The definitions for the Attributes can be found ... Table 11 - Common Method Attributes Attributes Value Executable All Methods defined in this document shall be executable ( Executable Attribute set to "True"), unless it is defined differently
• OPC-10000-200 – OPC Unified Architecture - Part 200: Industrial Automation
  9.1 Namespace Metadata
  namespace and an indication about static Nodes . Static Nodes are identical for all Attributes in all Servers , including the Value Attribute . See OPC 10000-5 for more details. The information
• OPC-10000-200 – OPC Unified Architecture - Part 200: Industrial Automation
  9.2 Handling of OPC UA Namespaces
  used by OPC UA to create unique identifiers across different naming authorities. The Attributes NodeId and BrowseName are identifiers. A Node in the UA AddressSpace is unambiguously identified using
• OPC-10000-210 – OPC Unified Architecture - Part 210: Relative Spatial Location
  3.4.1.1 Node definitions
  Node definitions Node definitions are specified using tables (see Table 2 ). Attributes are defined by providing the Attribute name and a value, or a description of the value. References ... TargetNode is a component of the Node being defined in the table the Attributes of the composed Node are defined in the same row of the table. The DataType
• OPC-10000-210 – OPC Unified Architecture - Part 210: Relative Spatial Location
  3.4.1.4 Additional Attribute values
  values The type definition table provides columns to specify the values for required Node Attributes for InstanceDeclarations . To provide information about additional Attributes , the format as shown in Table ... Multiple elements are defined as separate rows of a nested table The values of attributes are converted to text by adapting the reversible JSON encoding rules defined
• OPC-10000-210 – OPC Unified Architecture - Part 210: Relative Spatial Location
  3.4.3.1 General
  General The Attributes of Nodes , their DataTypes and descriptions are defined in OPC 10000-3 . Attributes not marked as optional are mandatory and shall be provided by a Server ... server-specific. For all Nodes specified in this document, the Attributes named in Table 7 shall be set as specified in the table. Table 7 - Common Node Attributes Attribute Value
• OPC-10000-210 – OPC Unified Architecture - Part 210: Relative Spatial Location
  3.4.3.2 Objects
  Objects For all Objects specified in this document, the Attributes named in Table 8 shall be set as specified in the Table 8 . The definitions for the Attributes ... found in OPC 10000-3 . Table 8 - Common Object Attributes Attribute Value EventNotifier Whether the Node can be used to subscribe to Events or not is server-specific
• OPC-10000-210 – OPC Unified Architecture - Part 210: Relative Spatial Location
  3.4.3.3 Variables
  Variables For all Variables specified in this document, the Attributes named in Table 9 shall be set as specified in the table. The definitions for the Attributes can be found ... Table 9 - Common Variable Attributes Attribute Value MinimumSamplingInterval Optionally, a server-specific minimum sampling interval is provided. AccessLevel The access level for Variables used for type definitions is server-specific
• OPC-10000-210 – OPC Unified Architecture - Part 210: Relative Spatial Location
  3.4.3.4 VariableTypes
  VariableTypes For all VariableTypes specified in this document, the Attributes named in Table 10 shall be set as specified in the table. The definitions for the Attributes can be found ... Table 10 - Common VariableType Attributes Attributes Value Value Optionally a server-specific default value can be provided. ArrayDimensions If the ValueRank does not identify an array of a specific dimension
• OPC-10000-210 – OPC Unified Architecture - Part 210: Relative Spatial Location
  3.4.3.5 Methods
  Methods For all Methods specified in this document, the Attributes named in Table 11 shall be set as specified in the table. The definitions for the Attributes can be found ... Table 11 - Common Method Attributes Attributes Value Executable All Methods defined in this document shall be executable ( Executable Attribute set to "True"), unless it is defined differently
• OPC-10000-210 – OPC Unified Architecture - Part 210: Relative Spatial Location
  6.1.1 Overview
  FrameIdentifier> BaseDataType SpatialLocationType MP The component 0:DefaultInstanceBrowseName of the SpatialObjectType have additional Attributes defined in Table 14 . Table 14 - SpatialObjectType Attribute values for child Nodes BrowsePath Value Attribute
• OPC-10000-210 – OPC Unified Architecture - Part 210: Relative Spatial Location
  6.2.1 Overview
  SpatialObject is contained in a SpatialObjectsList . The components of the SpatialObjectsListType have additional Attributes defined in Table 16 . Table 16 - SpatialObjectsListType Attribute values for child Nodes BrowsePath Value Attribute Description
• OPC-10000-210 – OPC Unified Architecture - Part 210: Relative Spatial Location
  10.1 Namespace Metadata
  namespace and an indication about static Nodes . Static Nodes are identical for all Attributes in all Servers , including the Value Attribute . See OPC 10000-5 for more details. The information
• OPC-10000-210 – OPC Unified Architecture - Part 210: Relative Spatial Location
  10.2 Handling of OPC UA Namespaces
  used by OPC UA to create unique identifiers across different naming authorities. The Attributes NodeId and BrowseName are identifiers. A Node in the UA AddressSpace is unambiguously identified using
• OPC-10000-211 – OPC Unified Architecture - Part 211: Global Positioning
  3.4.1.1 Node definitions
  Node definitions Node definitions are specified using tables (see Table 2 ). Attributes are defined by providing the Attribute name and a value, or a description of the value. References ... TargetNode is a component of the Node being defined in the table the Attributes of the composed Node are defined in the same row of the table. The DataType
• OPC-10000-211 – OPC Unified Architecture - Part 211: Global Positioning
  3.4.1.4 Additional Attribute values
  values The type definition table provides columns to specify the values for required Node Attributes for InstanceDeclarations . To provide information about additional Attributes , the format as shown in Table ... Multiple elements are defined as separate rows of a nested table The values of attributes are converted to text by adapting the reversible JSON encoding rules defined
• OPC-10000-211 – OPC Unified Architecture - Part 211: Global Positioning
  3.4.3.1 General
  General The Attributes of Nodes , their DataTypes and descriptions are defined in OPC 10000-3 . Attributes not marked as optional are mandatory and shall be provided by a Server ... server-specific. For all Nodes specified in this document, the Attributes named in Table 7 shall be set as specified in the table. Table 7 - Common Node Attributes Attribute Value
• OPC-10000-211 – OPC Unified Architecture - Part 211: Global Positioning
  3.4.3.2 Objects
  Objects For all Objects specified in this document, the Attributes named in Table 8 shall be set as specified in the Table 8 . The definitions for the Attributes ... found in OPC 10000-3 . Table 8 - Common Object Attributes Attribute Value EventNotifier Whether the Node can be used to subscribe to Events or not is server-specific
• OPC-10000-211 – OPC Unified Architecture - Part 211: Global Positioning
  3.4.3.3 Variables
  Variables For all Variables specified in this document, the Attributes named in Table 9 shall be set as specified in the table. The definitions for the Attributes can be found ... Table 9 - Common Variable Attributes Attribute Value MinimumSamplingInterval Optionally, a server-specific minimum sampling interval is provided. AccessLevel The access level for Variables used for type definitions is server-specific
• OPC-10000-211 – OPC Unified Architecture - Part 211: Global Positioning
  3.4.3.4 VariableTypes
  VariableTypes For all VariableTypes specified in this document, the Attributes named in Table 10 shall be set as specified in the table. The definitions for the Attributes can be found ... Table 10 - Common VariableType Attributes Attributes Value Value Optionally a server-specific default value can be provided. ArrayDimensions If the ValueRank does not identify an array of a specific dimension
• OPC-10000-211 – OPC Unified Architecture - Part 211: Global Positioning
  3.4.3.5 Methods
  Methods For all Methods specified in this document, the Attributes named in Table 11 shall be set as specified in the table. The definitions for the Attributes can be found ... Table 11 - Common Method Attributes Attributes Value Executable All Methods defined in this document shall be executable ( Executable Attribute set to "True"), unless it is defined differently
• OPC-10000-211 – OPC Unified Architecture - Part 211: Global Positioning
  12.1 Namespace Metadata
  namespace and an indication about static Nodes . Static Nodes are identical for all Attributes in all Servers , including the Value Attribute . See OPC 10000-5 for more details. The information
• OPC-10000-211 – OPC Unified Architecture - Part 211: Global Positioning
  12.2 Handling of OPC UA Namespaces
  used by OPC UA to create unique identifiers across different naming authorities. The Attributes NodeId and BrowseName are identifiers. A Node in the UA AddressSpace is unambiguously identified using