Search

200 result(s) for Attribute

• OPC-10000-1 – OPC Unified Architecture - Part 1: Overview and Concepts
  2.1.4 Attribute
  Attribute primitive characteristic of a Node Note 1 to entry: All Attributes are defined by OPC UA, and may not be defined by Clients or Servers . Attributes are the only
• OPC-10000-1 – OPC Unified Architecture - Part 1: Overview and Concepts
  2.1.16 EventNotifier
  EventNotifier special Attribute of a Node that signifies that a Client may subscribe to that particular Node to receive Notifications of Event occurrences
• OPC-10000-1 – OPC Unified Architecture - Part 1: Overview and Concepts
  6.7 Attribute Service Set
  Attribute 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 ... only elements in the AddressSpace permitted to have data values. A special Attribute , the Value Attribute is used to define the value of Variables
• OPC-10000-1 – OPC Unified Architecture - Part 1: Overview and Concepts
  6.9 MonitoredItem Service Set
  Notification is to be generated. Filter criteria for Attributes are specified by their Attribute definitions in OPC 10000-4 . The sample rate defined for a MonitoredItem may be faster than
• OPC-10000-3 – OPC Unified Architecture - Part 3: Address Space Model
  3.1.2 DataType
  DataType instance of a DataType Node that is used together with the ValueRank Attribute to define the data type of a Variable
• OPC-10000-3 – OPC Unified Architecture - Part 3: Address Space Model
  3.3.2 Conventions for defining NodeClasses
  define NodeClasses . Table 1 - NodeClass Table Conventions Name Use Data Type Description Attributes "Attribute name" "M" or "O" Data type of the Attribute Defines ... Attribute References "Reference name" "1", "0..1" or "0..*" Not used Describes the use of the Reference by the NodeClass Standard Properties
• 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 ... 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 consists
• OPC-10000-3 – OPC Unified Architecture - Part 3: Address Space Model
  4.5.2 Properties
  only defined by this specification whereas Properties can be Server -defined. For example, an Attribute defines the DataType of Variables whereas a Property can be used to specify the engineering
• OPC-10000-3 – OPC Unified Architecture - Part 3: Address Space Model
  4.9.3 Evaluating Permissions with Roles
  Nodes defined in Table 4 . The table specifies the value of the RolePermissions Attribute for each Node . Table 4 - Example Nodes Node Role Permissions Unit1.Measurement AuthenticatedUser = Browse Operator1 = Browse, Read
• OPC-10000-3 – OPC Unified Architecture - Part 3: Address Space Model
  5.2.2 NodeId
  Servers may accept alternative NodeIds in addition to the canonical NodeId represented in this Attribute . A Server shall persist the identifierType and identifier NodeId elements of a Node as well
• OPC-10000-3 – OPC Unified Architecture - Part 3: Address Space Model
  5.2.5 DisplayName
  DisplayName The DisplayName Attribute contains the localised name of the Node . Clients should use this Attribute if they want to display the name of the Node to the user. They
• 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 ... that is, although an Attribute is writeable this may be restricted to a certain user/user group. If the OPC UA Server does not have the ability to get the WriteMask
• 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 ... defined in 8.60 . The UserWriteMask Attribute can only further restrict the WriteMask Attribute, when it is set to not writeable in the general case that applies for every user. Clients
• OPC-10000-3 – OPC Unified Architecture - Part 3: Address Space Model
  5.2.9 RolePermissions
  RolePermissions The optional RolePermissions Attribute specifies the Permissions that apply to a Node for all Roles which have access to the Node . The value of the Attribute is an array ... Role . See 8.55 Servers may allow administrators to write to the RolePermissions Attribute . If not specified, the value of DefaultRolePermissions Property from the NamespaceMetadata Object associated with the Node shall
• OPC-10000-3 – OPC Unified Architecture - Part 3: Address Space Model
  5.2.10 UserRolePermissions
  UserRolePermissions The optional UserRolePermissions Attribute specifies the Permissions that apply to a Node for all Roles granted to current Session . The value of the Attribute is an array of RolePermissionType ... logical OR of Permissions for each Role in the array. The value of this Attribute is derived from the rules used by the Server to map Sessions to Roles . This
• OPC-10000-3 – OPC Unified Architecture - Part 3: Address Space Model
  5.2.11 AccessRestrictions
  AccessRestrictions The optional AccessRestrictions Attribute specifies the AccessRestrictions that apply to a Node. Its data type is defined in 8.56 . If a Server supports AccessRestrictions for a particular Namespace ... Namespace needs to override the default value the Server adds the AccessRestrictions Attribute to the Node. If a Server implements a vendor specific access restriction model for a Namespace
• OPC-10000-3 – OPC Unified Architecture - Part 3: Address Space Model
  5.3.1 General
  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 ReferenceType , i.e. no Reference of this ... abstract ReferenceType , i.e. References of this type can exist. Symmetric M Boolean A boolean Attribute with the following values: TRUE the meaning of the ReferenceType is the same as seen
• OPC-10000-3 – OPC Unified Architecture - Part 3: Address Space Model
  5.3.2 Attributes
  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 from the SourceNode ... used in References that specify that the SourceNode contains the TargetNode . The inherited DisplayName Attribute contains a translation of the BrowseName. The BrowseName of a ReferenceType shall be unique
• OPC-10000-3 – OPC Unified Architecture - Part 3: Address Space Model
  5.4 View NodeClass
  from the Base NodeClass . See 5.2 . ContainsNoLoops M Boolean If set to TRUE this Attribute indicates that by following the References in the context of the View there ... Node to reach a Node contained in the View . If set to FALSE this Attribute indicates that following References in the context of the View may lead to loops. EventNotifier
• OPC-10000-3 – OPC Unified Architecture - Part 3: Address Space Model
  5.5.1 Object NodeClass
  Attributes M -- Inherited from the Base NodeClass . See 5.2 . EventNotifier M EventNotifierType The EventNotifier Attribute is used to indicate if the Node can be used to subscribe to Events ... used for Objects having their "SubscribeToEvents" bit set in the EventNotifier Attribute . See 7.17 for details. HasNotifier 0..* The HasNotifier Reference points to notifiers of the Object . References
• OPC-10000-3 – OPC Unified Architecture - Part 3: Address Space Model
  5.5.2 ObjectType 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 ObjectType , i.e. no Objects of this ... time a Reference is added or deleted to the Node the Property belongs to. Attribute value changes do not cause the NodeVersion to change. Clients may read the NodeVersion Property
• OPC-10000-3 – OPC Unified Architecture - Part 3: Address Space Model
  5.6.2 Variable NodeClass
  Inherited from the Base NodeClass . See 5.2 . Value M Defined by the DataType Attribute The most recent value of the Variable that the Server has. Its data type is defined ... DataType Attribute . It is the only Attribute that does not have a data type associated with it. This allows all Variables to have a value defined by the same Value
• OPC-10000-3 – OPC Unified Architecture - Part 3: Address Space Model
  5.6.4 DataVariable
  obtained. The Property AllowNulls indicates if null values are allowed for the Value Attribute . The Property ValueAsText provides a localized text representation for enumeration values. The Property MaxStringLength indicates
• OPC-10000-3 – OPC Unified Architecture - Part 3: Address Space Model
  5.6.5 VariableType NodeClass
  Inherited from the Base NodeClass . See 5.2 Value O Defined by the DataType attribute The default Value for instances of this type. DataType M NodeId NodeId of the data type ... null. Standard DataTypes are defined in Clause 7.23 8 . ValueRank M Int32 This Attribute indicates whether the Value Attribute of the VariableType is an array and how many dimensions
• OPC-10000-3 – OPC Unified Architecture - Part 3: Address Space Model
  5.7.1 Method NodeClass
  Attributes M -- Inherited from the Base NodeClass . See 5.2 . Executable M Boolean The Executable Attribute indicates if the Method is currently executable (FALSE means not executable, TRUE means executable ... Executable Attribute does not take any user access rights into account, i.e. although the Method is executable this may be restricted to a certain user / user group. UserExecutable M Boolean
• OPC-10000-3 – OPC Unified Architecture - Part 3: Address Space Model
  5.8.1 DataType Model
  structured data types. Data types are used to describe the structure of the Value Attribute of Variables and their VariableTypes . Therefore each Variable and VariableType 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, the NodeId of the DataType Node
• OPC-10000-3 – OPC Unified Architecture - Part 3: Address Space Model
  5.8.2 Encoding Rules for different kinds of DataTypes
  encoding they cannot have encodings defined in the AddressSpace . Clients can read the DataType Attribute of a Variable or VariableType to identify the Simple DataType of the Value Attribute ... handled on the wire as a Double but the Client can read the DataType Attribute and thus interpret the value as defined by Duration (see 8.13 ). Structured DataTypes are DataTypes
• OPC-10000-3 – OPC Unified Architecture - Part 3: Address Space Model
  5.8.3 DataType 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 DataType . FALSE ... abstract DataType . DataTypeDefinition O DataTypeDefinition The DataTypeDefinition Attribute is used to provide the meta data and encoding information for DataTypes . The abstract DataTypeDefinition DataType is defined in 8.47 . Structure
• OPC-10000-3 – OPC Unified Architecture - Part 3: Address Space Model
  5.8.4 DataTypeEncoding and Encoding Information
  DataType Modelling The information on how to encode the DataType is provided in the Attribute DataTypeDefinition of the DataType Node . The content of this Attribute shall not be changed once
• OPC-10000-3 – OPC Unified Architecture - Part 3: Address Space Model
  5.8.5.2 DataTypeRefinement Objects
  Table 17 , the mapping of the fields in the StructureField of the DataTypeDefinition Attribute to concepts of a Variable is defined. Table 17 - Mapping of DataTypeDefinition StructureField Variable Concept Comment ... Name String part of BrowseName Attribute Must match Description Description Attribute No requirements DataType DataType Attribute Variable must have the same DataType or a subtype ValueRank ValueRank Attribute Must match
• OPC-10000-3 – OPC Unified Architecture - Part 3: Address Space Model
  5.8.6.1 Overview
  subtype of the DataType unless restricted in the NoSubDataTypes bit of the AccessLevelEx Attribute. In fields of a structure, using subtypes is allowed when IsOptional ... disallow subtypes. In order to use a SubtypeRestriction, the ValueRank and ArrayDimensions Attribute of the Variable using the SubtypeRestriction shall be compatible to all referenced Variables using AllowedSubtype
• 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 ... Value Attribute . When a Variable used as InstanceDeclaration or a VariableType is overridden or instantiated the following rules apply: The DataType Attribute can only be changed to a new DataType
• 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
• OPC-10000-3 – OPC Unified Architecture - Part 3: Address Space Model
  6.3.3.3 Overriding InstanceDeclarations
  NodeClass or BrowseName , however, the restrictions on Attributes specified in 6.2.7 apply. Any Attribute provided by the overridden InstanceDeclaration has to be provided by the overriding InstanceDeclaration , additional optional Attributes
• OPC-10000-3 – OPC Unified Architecture - Part 3: Address Space Model
  6.4.2 Creating an Instance
  that has the same TypeDefinitionNode and BrowseName . If new copies are created, then the Attribute values of the InstanceDeclarations are used as the initial values. An instance shall
• OPC-10000-3 – OPC Unified Architecture - Part 3: Address Space Model
  6.4.3 Constraints on an Instance
  Constraints on an Instance Objects and 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
• OPC-10000-3 – OPC Unified Architecture - Part 3: Address Space Model
  7.17 HasEventSource
  Object or View that has its "SubscribeToEvents" bit set within the EventNotifier Attribute . The SourceNode may also be an ObjectType when referencing an InstanceDeclaration where an instance
• OPC-10000-3 – OPC Unified Architecture - Part 3: Address Space Model
  8.55 PermissionType
  Client is able to Read to Attributes other than the Value or the RolePermissions Attribute . This Permission is valid for all NodeClasses . ReadRolePermissions 1 The Client is allowed to read ... RolePermissions Attribute . This Permission is 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
• OPC-10000-3 – OPC Unified Architecture - Part 3: Address Space Model
  8.60 AttributeWriteMask
  UInt32 DataType with the OptionSetValues Property defined. It is used to define the Attribute access restrictions of a Node . The AttributeWriteMask is formally defined in Table ... means the Attribute is not writeable. If a bit is set to 1, it means it is writeable. If a Node does not support a specific Attribute , the corresponding
• OPC-10000-3 – OPC Unified Architecture - Part 3: Address Space Model
  9.33.1 General
  change of the AddressSpace semantics. The change consists of a change to the Value Attribute of a Property . The SemanticChangeEvent contains information about the Node owning the Property that ... Variable or Object , the TypeDefinitionNode is also present. The SemanticChange bit of the AccessLevel Attribute of a Property indicates whether changes of the Property value are considered for SemanticChangeEvents
• OPC-10000-3 – OPC Unified Architecture - Part 3: Address Space Model
  B.2 Notation
  class diagram in Figure B.2 . OPC Attributes inherit from the abstract class Attribute and have a value identifying their data type. They are composed of a Node which is either ... represented as UML attributes without data types and marked with the stereotype <<Attribute>>, like InverseName in the UML object HasComponent . They have values, like InverseName =ComponentOf
• OPC-10000-3 – OPC Unified Architecture - Part 3: Address Space Model
  C.2.1 Overview
  like Attributes . The extended notation allows exposing all structure information of OPC UA, including Attribute values. The simple and the extended notation can be combined to expose OPC UA data
• OPC-10000-3 – OPC Unified Architecture - Part 3: Address Space Model
  C.2.3 Extended notation
  text describing the Attributes have to be separated using a horizontal line. Each Attribute has to be set into a new text line. Each text line shall contain the Attribute ... name followed by an "=" and the value of the Attribute . On top of the first text line containing an Attribute shall be a text line containing the underlined
• OPC-10000-4 – OPC Unified Architecture - Part 4: Services
  4.1 Service Set model
  data from the AddressSpace or the View . Figure 5 - View Service Set The Attribute Service Set is illustrated in Figure 6 . It defines Services that allow Clients to read ... including their historical values. Since the value of a Variable is modelled as an Attribute , these Services allow Clients to read and write the values of Variables . Figure 6 - Attribute
• OPC-10000-4 – OPC Unified Architecture - Part 4: Services
  5.8.2.2 Parameters
  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 ... Server shall choose a suitable default value. The Server may still add an optional Attribute to the Node with an appropriate default value even if the Client does not specify
• OPC-10000-4 – OPC Unified Architecture - Part 4: Services
  5.9.4.1 Description
  Boiler1" and the graphical element could subscribe to its Value Attribute . If a Node has multiple targets with the same BrowseName , the Server shall return a list of NodeIds
• OPC-10000-4 – OPC Unified Architecture - Part 4: Services
  5.9.5.1 Description
  vendor-specific. For Variable Nodes Servers shall concentrate their optimization efforts on the Value Attribute . Registered NodeIds are only guaranteed to be valid within the current Session . Clients shall unregister ... NodeIds but only the canonical NodeId s which is the value of the NodeId Attribute
• OPC-10000-4 – OPC Unified Architecture - Part 4: Services
  5.11.2.1 Description
  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 allows Clients to read
• OPC-10000-4 – OPC Unified Architecture - Part 4: Services
  5.11.2.2 Parameters
  time it was requested. If the Server has one or more values of an Attribute that are within the maximum age, it can return any one of the values ... read a new value from the data source. The number of values of an Attribute that a Server has depends on the number of MonitoredItems that are defined
• OPC-10000-4 – OPC Unified Architecture - Part 4: Services
  5.11.3.1 Description
  used to read historical values or Events of one or more Nodes . For constructed Attribute values whose elements are indexed, such as an array, this Service allows Clients to read ... Service , although the historical values themselves are not visible in the AddressSpace . The AccessLevel Attribute defined in OPC 10000-3 indicates a Node 's support for historical values. Several request
• OPC-10000-4 – OPC Unified Architecture - Part 4: Services
  5.11.3.2 Parameters
  enumeration that specifies the timestamps to be returned for each requested Variable Value Attribute . The TimestampsToReturn enumeration is defined in 7.39 . Specifying a TimestampsToReturn of NEITHER is not valid
• OPC-10000-4 – OPC Unified Architecture - Part 4: Services
  5.11.4.1 Description
  write values to one or more Attributes of one or more Nodes . For constructed Attribute values whose elements are indexed, such as an array, this Service allows Clients to write ... depends on the different data sources and the internal Server logic. If an Attribute and Node combination is contained in more than one operation, the order of the processing
• OPC-10000-4 – OPC Unified Architecture - Part 4: Services
  5.11.4.2 Parameters
  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 ... NumericRange type is defined in 7.27 . This parameter is not used if the specified Attribute is not an array. However, if the specified Attribute is an array and this parameter
• OPC-10000-4 – OPC Unified Architecture - Part 4: Services
  5.12.2.4 StatusCodes
  node that does not exist in the Server address space. Bad_NotExecutable The executable Attribute does not allow the execution of the Method . Bad_ArgumentsMissing The Client did not specify
• OPC-10000-4 – OPC Unified Architecture - Part 4: Services
  5.13.1.1 Overview
  send Notifications . The item to be monitored may be any Node Attribute . Notifications are data structures that describe the occurrence of data changes and Events . They are packaged into NotificationMessages ... 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 is not used for these
• OPC-10000-4 – OPC Unified Architecture - Part 4: Services
  5.13.1.2 Sampling interval
  identifies the minimum sampling interval supported by the Server . The optional MinimumSamplingInterval Attribute defined in OPC 10000-3 identifies the minimum sampling interval supported for a Variable . If a Server ... underlying system updates the item is known, it will be available via the MinimumSamplingInterval Attribute defined in OPC 10000-3 . If the Server specifies a value for the MinimumSamplingInterval Attribute
• OPC-10000-4 – OPC Unified Architecture - Part 4: Services
  5.13.1.6 Triggering model
  unaffected. Deletion of a MonitoredItem should not be confused with the removal of the Attribute that it monitors. If the Node that contains the Attribute being monitored is deleted
• OPC-10000-4 – OPC Unified Architecture - Part 4: Services
  5.13.2.2 Parameters
  Events , the attributeId element of the ReadValueId structure is the id of the EventNotifier Attribute . The ReadValueId type is defined in 7.28 . monitoringMode Enum MonitoringMode The monitoring mode
• OPC-10000-4 – OPC Unified Architecture - Part 4: Services
  5.14.2.2 Parameters
  value of this parameter does not affect the value of the monitoring mode Attribute of MonitoredItems . priority Byte Indicates the relative priority of the Subscription . When more than one Subscription
• OPC-10000-4 – OPC Unified Architecture - Part 4: Services
  5.14.4.2 Parameters
  value of this parameter does not affect the value of the monitoring mode Attribute of MonitoredItems . Setting this value to FALSE does not discontinue the sending of keep-alive Messages
• OPC-10000-4 – OPC Unified Architecture - Part 4: Services
  6.5.8 Auditing for Attribute Service Set
  Auditing for Attribute Service Set The Write or HistoryUpdate Services in this Service Set for Servers that support auditing may generate audit entries and shall generate audit Events for both ... failed. For Clients that support auditing, accessing the Write or HistoryUpdate services in the Attribute Service Set shall generate audit entries for both successful and failed invocations of the Service
• OPC-10000-4 – OPC Unified Architecture - Part 4: Services
  7.7.4.1 Overview
  operand of one element to a sub-element. Literal Specifies a literal value. Attribute Specifies any Attribute of an Object or Variable Node using a Node in the type system ... relative path constructed from ReferenceTypes and BrowseNames . SimpleAttribute Specifies any Attribute of an Object or Variable Node using a TypeDefinition and a relative path constructed from BrowseNames
• OPC-10000-4 – OPC Unified Architecture - Part 4: Services
  7.7.4.4 AttributeOperand
  Table 128 defines the AttributeOperand type. Table 128 - AttributeOperand Name Type Description AttributeOperand structure Attribute of a Node in the AddressSpace . nodeId NodeId NodeId of a Node from the type ... nodeId parameter. See 7.30 for the definition of RelativePath . attributeId IntegerId Id of the Attribute . This shall be a valid AttributeId . The IntegerId is defined in 7.19 . The IntegerIds
• OPC-10000-4 – OPC Unified Architecture - Part 4: Services
  7.7.4.5 SimpleAttributeOperand
  Table 129 defines the SimpleAttributeOperand type. Table 129 - SimpleAttributeOperand Name Type Description SimpleAttributeOperand structure Attribute of a Node in the AddressSpace . typeDefinitionId NodeId NodeId of a TypeDefinitionNode . This parameter restricts ... empty the Node is the instance of the TypeDefinition . attributeId IntegerId Id of the Attribute . The IntegerId is defined in 7.19 . The Value Attribute shall be supported by all Servers
• OPC-10000-4 – OPC Unified Architecture - Part 4: Services
  7.11.3 SourceTimestamp
  from the bad or 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
  Server's AddressSpace . The SimpleAttributeOperand structure allows the Client to specify any Attribute ; however, the Server is only required to support the Value Attribute for Variable Nodes and the NodeId ... Attribute for Object 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
• OPC-10000-4 – OPC Unified Architecture - Part 4: Services
  7.24.1 Overview
  NodeClass . GenericAttributes Defines an id and value list for passing in any number of Attribute values. It should be used instead of the NodeClass specific structures since it allows ... mask for specified Attributes Field Bit Description AccessLevel 0 Indicates if the AccessLevel Attribute is set. ArrayDimensions 1 Indicates if the ArrayDimensions Attribute is set. Reserved 2 Reserved
• OPC-10000-4 – OPC Unified Architecture - Part 4: Services
  7.24.2 ObjectAttributes parameter
  Table 150 . displayName LocalizedText See OPC 10000-3 for the description of this Attribute . description LocalizedText See OPC 10000-3 for the description of this Attribute . writeMask UInt32 ... description of this Attribute . userWriteMask UInt32 See OPC 10000-3 for the description of this Attribute . eventNotifier Byte See OPC 10000-3 for the description of this Attribute
• OPC-10000-4 – OPC Unified Architecture - Part 4: Services
  7.24.3 VariableAttributes parameter
  Table 150 . displayName LocalizedText See OPC 10000-3 for the description of this Attribute . description LocalizedText See OPC 10000-3 for the description of this Attribute . writeMask UInt32 ... description of this Attribute . userWriteMask UInt32 See OPC 10000-3 for the description of this Attribute . value BaseDataType See OPC 10000-3 for the description of this Attribute . dataType NodeId
• OPC-10000-4 – OPC Unified Architecture - Part 4: Services
  7.24.4 MethodAttributes parameter
  Table 150 . displayName LocalizedText See OPC 10000-3 for the description of this Attribute . description LocalizedText See OPC 10000-3 for the description of this Attribute . writeMask UInt32 ... description of this Attribute . userWriteMask UInt32 See OPC 10000-3 for the description of this Attribute . executable Boolean See OPC 10000-3 for the description of this Attribute . userExecutable Boolean
• OPC-10000-4 – OPC Unified Architecture - Part 4: Services
  7.24.5 ObjectTypeAttributes parameter
  Table 150 . displayName LocalizedText See OPC 10000-3 for the description of this Attribute . description LocalizedText See OPC 10000-3 for the description of this Attribute . writeMask UInt32 ... description of this Attribute . userWriteMask UInt32 See OPC 10000-3 for the description of this Attribute . isAbstract Boolean See OPC 10000-3 for the description of this Attribute
• OPC-10000-4 – OPC Unified Architecture - Part 4: Services
  7.24.6 VariableTypeAttributes parameter
  Table 150 . displayName LocalizedText See OPC 10000-3 for the description of this Attribute . description LocalizedText See OPC 10000-3 for the description of this Attribute . writeMask UInt32 ... description of this Attribute . userWriteMask UInt32 See OPC 10000-3 for the description of this Attribute . value BaseDataType See OPC 10000-3 for the description of this Attribute . dataType NodeId
• OPC-10000-4 – OPC Unified Architecture - Part 4: Services
  7.24.7 ReferenceTypeAttributes parameter
  Table 150 . displayName LocalizedText See OPC 10000-3 for the description of this Attribute . description LocalizedText See OPC 10000-3 for the description of this Attribute . writeMask UInt32 ... description of this Attribute . userWriteMask UInt32 See OPC 10000-3 for the description of this Attribute . isAbstract Boolean See OPC 10000-3 for the description of this Attribute . symmetric Boolean
• OPC-10000-4 – OPC Unified Architecture - Part 4: Services
  7.24.8 DataTypeAttributes parameter
  Table 150 . displayName LocalizedText See OPC 10000-3 for the description of this Attribute . description LocalizedText See OPC 10000-3 for the description of this Attribute . writeMask UInt32 ... description of this Attribute . userWriteMask UInt32 See OPC 10000-3 for the description of this Attribute . isAbstract Boolean See OPC 10000-3 for the description of this Attribute
• OPC-10000-4 – OPC Unified Architecture - Part 4: Services
  7.24.9 ViewAttributes parameter
  Table 150 . displayName LocalizedText See OPC 10000-3 for the description of this Attribute . description LocalizedText See OPC 10000-3 for the description of this Attribute . writeMask UInt32 ... description of this Attribute . userWriteMask UInt32 See OPC 10000-3 for the description of this Attribute . containsNoLoops Boolean See OPC 10000-3 for the description of this Attribute . eventNotifier Byte
• OPC-10000-4 – OPC Unified Architecture - Part 4: Services
  7.24.10 GenericAttributes parameter
  Table 150 . displayName LocalizedText See OPC 10000-3 for the description of this Attribute . description LocalizedText See OPC 10000-3 for the description of this Attribute . writeMask UInt32 ... description of this Attribute . userWriteMask UInt32 See OPC 10000-3 for the description of this Attribute . attributeValues GenericAttributeValue [] Defines one attributeId and value combination. attributeId IntegerId Id of the Attribute
• OPC-10000-4 – OPC Unified Architecture - Part 4: Services
  7.25.2 DataChangeNotification parameter
  Triggering model. After creating a MonitoredItem, the current value or status of the monitored Attribute shall be queued without applying the filter. If the current value is not available after ... defined in 7.19 Value DataValue The StatusCode , value and timestamp(s) of the monitored Attribute depending on the sampling and queuing configuration. If the StatusCode indicates an error then
• OPC-10000-4 – OPC Unified Architecture - Part 4: Services
  7.28 ReadValueId
  monitor. nodeId NodeId NodeId of a Node . attributeId IntegerId Id of the Attribute . This shall be a valid Attribute id. The IntegerId is defined in 7.19 . The IntegerIds ... type is defined in 7.27 . This parameter is null or empty if the specified Attribute is not an array. However, if the specified Attribute is an array, and this parameter
• OPC-10000-4 – OPC Unified Architecture - Part 4: Services
  B.1.1 Overview
  processing events. The following conventions apply to these examples with regard to how Attribute operands are used (for a definition of this operand see 7.7.4 ): AttributeOperand: Refers to a Node ... Attribute of a Node or the Value Attribute of a Property associated with a Node . In the examples, the character names of NodeIds are used instead of an actual nodeId
• OPC-10000-4 – OPC Unified Architecture - Part 4: Services
  B.2.1 Overview
  Server are in the form of an array of QueryDataSets . The selected Attribute values in each QueryDataSet come from the definition of the selected TypeDefinitionNodes or related TypeDefinitionNodes and appear ... were passed into the Query . Query also supports Node filtering on the basis of Attribute values, as well as relationships between TypeDefinitionNodes
• OPC-10000-4 – OPC Unified Architecture - Part 4: Services
  B.2.2 Querying Views
  Query can be used to retrieve a portion of a past AddressSpace so that Attribute value history may be accessed using Historical Access even if the Node is no longer
• OPC-10000-4 – OPC Unified Architecture - Part 4: Services
  B.2.3 QueryFirst
  Client can request the Server return instances of subtypes of TypeDefinitionNodes . If a selected Attribute does not exist in a TypeDefinitionNode but does exist in a subtype, it is assumed ... does not constitute an error condition and a null value is returned for the Attribute . The Client can use the filter parameter to limit the result set by restricting Attributes
• OPC-10000-4 – OPC Unified Architecture - Part 4: Services
  B.3.1 Overview
  examples illustrate complex filters . The following conventions apply to these examples with regard to Attribute operands (for a definition of these operands, see 7.7.4 ). AttributeOperand: Refers to a Node ... Attribute of a Node or the Value Attribute of a Property associated with a Node . In the examples character names of ExpandedNodeId are used instead of an actual ExpandedNodeId , this
• OPC-10000-4 – OPC Unified Architecture - Part 4: Services
  B.3.3 Example Notes
  actual call it would be the ExpandedNodeId assigned to the Node . The Attribute is the symbolic name of the Attribute , in the actual call they would be translated ... IntegerId of the Attribute . Also in all of the examples the BrowseName is included in the result table for clarity; normally this would not be returned. All of the examples
• OPC-10000-4 – OPC Unified Architecture - Part 4: Services
  B.3.4 Example 1
  B.10 . Table B.10 - Example 1 NodeTypeDescription Type Definition Node Include Subtypes QueryDataDescription Relative Path Attribute Index Range PersonType FALSE ".12:LastName" value N/A "<12:HasPet ... Operand[1] Operand[2] Operand[3] 1 RelatedTo AttributeOperand = NodeId: PersonType, BrowsePath ".", Attribute: NodeId ElementOperand = 2 AttributeOperand = NodeId: HasPet, BrowsePath ".", Attribute: NodeId LiteralOperand = '1' 2 RelatedTo
• OPC-10000-5 – OPC Unified Architecture - Part 5: Information Model
  3.3 Conventions for Node descriptions
  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 are defined by providing ... Category element of the UANodeSet file provides the precise information. Table 2 - TypeDefinition Table Attribute Value Attribute name Attribute value. If it is an optional Attribute that
• OPC-10000-5 – OPC Unified Architecture - Part 5: Information Model
  5.1 General
  shall be set as specified in Table 3 . Table 3 - Common Node Attributes Attribute Value DisplayName The DisplayName is a LocalizedText . Each server shall provide the DisplayName identical ... defined in 4.1 and defined in OPC 10000-6 . WriteMask Optionally the WriteMask Attribute can be provided. If the WriteMask Attribute is provided, it shall set all non-server-specific
• OPC-10000-5 – OPC Unified Architecture - Part 5: Information Model
  5.3 Variables
  shall be set as specified in Table 5 . Table 5 - Common Variable Attributes Attribute Value MinimumSamplingInterval Optionally, a server-specific minimum sampling interval is provided. AccessLevel The access level ... shall allow reading; other settings are server-specific. UserAccessLevel The value for the UserAccessLevel Attribute is server-specific. It is assumed that all Variables can be accessed by at least
• OPC-10000-5 – OPC Unified Architecture - Part 5: Information Model
  5.4 VariableTypes
  ValueRank <= 0) the ArrayDimensions can either be set to null or the Attribute is missing. This behaviour is server-specific. If the ValueRank specifies an array of a specific ... dimension (i.e. ValueRank > 0) then the ArrayDimensions Attribute shall be specified
• OPC-10000-5 – OPC Unified Architecture - Part 5: Information Model
  5.5 Methods
  Attributes Attributes Value Executable All Methods defined in this specification shall be executable ( Executable Attribute set to "True"), unless it is defined differently in the Method definition. UserExecutable ... value of the UserExecutable Attribute is server-specific. It is assumed that all Methods can be executed by at least one user
• OPC-10000-5 – OPC Unified Architecture - Part 5: Information Model
  6.3.13 NamespaceMetadataType
  Servers is provided by the StaticNodeIdTypes, StaticNumericNodeIdRange and StaticStringNodeIdPattern Properties . Table 22 - NamespaceMetadataType definition Attribute Value BrowseName NamespaceMetadataType IsAbstract False References NodeClass BrowseName DataType TypeDefinition Modelling Rule Subtype ... TRUE. Static Nodes are identical for all Attributes in all Servers , including the Value Attribute . For TypeDefinitionNodes , also the InstanceDeclarations shall be identical. That means that for static Nodes
• OPC-10000-5 – OPC Unified Architecture - Part 5: Information Model
  6.3.15 NonTransparentBackupRedundancyType
  Warm Failover mode defined in OPC 10000-4 . Table 24 - NonTransparentBackupRedundancyType definition Attribute Value BrowseName NonTransparentBackupRedundancyType IsAbstract False References NodeClass BrowseName DataType TypeDefinition Modelling Rule Subtype of the NonTransparentRedundancyType defined ... take over, it will become the primary. The Server should set the Executable Attribute of this method to indicate if the failover is currently possible. Signature Failover( ); Method Result Codes
• OPC-10000-5 – OPC Unified Architecture - Part 5: Information Model
  6.4.25 AuditWriteUpdateEventType
  representation in the AddressSpace is formally defined in Table 49 . Table 49 - AuditWriteUpdateEventType definition Attribute Value BrowseName AuditWriteUpdateEventType IsAbstract True References NodeClass BrowseName DataType TypeDefinition ModellingRule Subtype of the AuditUpdateEventType ... shall be "Attribute/Write". Their semantic is defined in 6.4.24 . AttributeId identifies the Attribute that was written. The SourceNode Property identifies the Node that was written. IndexRange identifies
• OPC-10000-5 – OPC Unified Architecture - Part 5: Information Model
  6.8 AggregateFunctionType
  Server . It is formally defined in Table 65 . Table 65 - AggregateFunctionType definition Attribute Value BrowseName AggregateFunctionType IsAbstract False References NodeClass BrowseName DataType TypeDefinition ModellingRule Subtype of the BaseObjectType defined ... Conformance Units Historical Access Aggregates For the AggregateFunctionType , the Description Attribute is mandatory. The Description Attribute provides a localized description of the AggregateFunction. Specific AggregateFunctions may be defined in further
• OPC-10000-5 – OPC Unified Architecture - Part 5: Information Model
  8.3.2 Server Object
  Table 111 . The Server Object serves as root notifier, that is, its EventNotifier Attribute shall be set providing Events . All Events of the Server shall be accessible subscribing ... Events of the Server Object . Table 111 - Server definition Attribute Value BrowseName Server References NodeClass BrowseName DataType TypeDefinition ModellingRule HasTypeDefinition ObjectType ServerType Defined in 6.3.1 Conformance Units Base Info Core
• OPC-10000-5 – OPC Unified Architecture - Part 5: Information Model
  12.16 ModelChangeStructureDataType
  only for affected Nodes that are Variables or VariableTypes . It indicates that the DataType Attribute has changed. Reserved 5:7 Reserved for future use. Shall always be zero. A verb
• OPC-10000-5 – OPC Unified Architecture - Part 5: Information Model
  A.7 Redundant information
  information, because the information is directly provided in the complex DataType of the Value Attribute of the complex Variable , and also exposed individually in the components of the complex Variable
• OPC-10000-5 – OPC Unified Architecture - Part 5: Information Model
  B.1 Overview
  document . In OPC 10000-3 a simplified approach is now defined having a DataTypeDefinition Attribute on the DataType Node . It is required to only use the DataTypeDefinition Attribute approach
• OPC-10000-6 – OPC Unified Architecture - Part 6: Mappings
  5.1.9 Variant
  applications shall not rely on this distinction. This requirement also means that if an Attribute supports the writing of a null value it shall also support writing of an empty ... Attributes are always returned in instances of DataValues . Therefore, the DataType of an Attribute cannot be a DataValue . Variants can contain DataValue when used in other contexts such as Method
• OPC-10000-6 – OPC Unified Architecture - Part 6: Mappings
  5.2.5 Arrays
  where they are used. When a multi-dimensional Array is the Value of an Attribute it uses the Variant encoding described in 5.2.2.16 . When a multi-dimensional Array
• OPC-10000-6 – OPC Unified Architecture - Part 6: Mappings
  5.2.6 Structures
  values in 'M' encoded sequentially as described in 5.2.2.16 . The Value of the DataTypeDefinition Attribute for a DataType Node describing Type1 is shown in Table 30 . Table 30 - DataTypeDefinition ... maxStringLength UInt32 0 isOptional Boolean false The Value of the DataTypeDefinition Attribute for a DataType Node describing Type2 is shown in Table 31 . Table 31 - DataTypeDefinition for "Type2
• OPC-10000-6 – OPC Unified Architecture - Part 6: Mappings
  5.2.7 Structures with optional fields
  subtypes extend the EncodingMask defined for the parent. The Value of the DataTypeDefinition Attribute for a DataType Node describing TypeA is: Name Type Description defaultEncodingId NodeId NodeId
• OPC-10000-6 – OPC Unified Architecture - Part 6: Mappings
  5.2.8 Unions
  Field1 Field1 4 The value of Field1 The Value of the DataTypeDefinition Attribute for a DataType Node describing Type1 is: Name Type Description defaultEncodingId NodeId NodeId of the "Type1 ... arrayDimensions UInt32[] null maxStringLength UInt32 0 isOptional Boolean true The Value of the DataTypeDefinition Attribute for a DataType Node describing Type2 is: Name Type Description defaultEncodingId NodeId NodeId
• OPC-10000-8 – OPC Unified Architecture - Part 8: Data Access
  5.3.3.4 MultiStateValueDiscreteType
  from the DiscreteItemType . It is formally defined in Table 11 . Table 11 - MultiStateValueDiscreteType definition Attribute Value BrowseName MultiStateValueDiscreteType IsAbstract False ValueRank -2 (-2 = 'Any') DataType Number References NodeClass BrowseName DataType ... definition of this type. MultiStateValueDiscrete Variables expose the current integer notation in their Value Attribute . Clients will often read the EnumValues Property in advance and cache it to lookup
• OPC-10000-8 – OPC Unified Architecture - Part 8: Data Access
  5.3.4.4 ImageItemType
  pixel intensity. ImageItemType is formally defined in Table 16 . Table 16 - ImageItemType definition Attribute Value BrowseName ImageItemType IsAbstract False ValueRank 2 (2 = two dimensional array) DataType BaseDataType References NodeClass BrowseName ... restricted to SByte, Int16, Int32, Int64, Float, Double, ComplexNumberType and DoubleComplexNumberType. The ArrayDimensions Attribute for Variables of this type or subtypes shall use the first entry in the array
• OPC-10000-8 – OPC Unified Architecture - Part 8: Data Access
  5.3.4.5 CubeItemType
  particle size. CubeItemType is formally defined in Table 17 . Table 17 - CubeItemType definition Attribute Value BrowseName CubeItemType IsAbstract False ValueRank 3 (3 = three dimensional array) DataType BaseDataType References NodeClass BrowseName ... restricted to SByte, Int16, Int32, Int64, Float, Double, ComplexNumberType and DoubleComplexNumberType . The ArrayDimensions Attribute for Variables of this type or subtypes should use the first entry in the array
• OPC-10000-8 – OPC Unified Architecture - Part 8: Data Access
  5.4 Address Space model
  AddressSpace Each DataItem is represented by a DataVariable with a specific set of Attribute s. The TypeDefinition reference indicates the type of the DataItem (in this case the AnalogItemType ). Additional ... than one that is vendor-specific. The above figure shows only a subset of Attribute s and Properties . Other Attributes that are defined for Variable
• OPC-10000-8 – OPC Unified Architecture - Part 8: Data Access
  5.5 Attributes of DataItems
  Attributes of DataItems The following Attribute s of Variable s (specified in detail in OPC 10000-3 ) are particularly important for DataItems : Value DataType AccessLevel MinimumSamplingInterval Value is the most ... Variable that the Server has. Its data type is defined by the DataType Attribute . The AccessLevel Attribute defines the Server's basic ability to access current data and MinimumSamplingInterval defines
• OPC-10000-8 – OPC Unified Architecture - Part 8: Data Access
  6.4.1 QuantityType ObjectType definition
  illustrated in Figure 9 and formally defined in Table 41 . Table 41 - QuantityType definition Attribute Value BrowseName QuantityType IsAbstract False References NodeClass BrowseName DataType TypeDefinition Other Subtype of the BaseObjectType ... HasComponent Object ServerUnits BaseObjectType M Conformance Units Data Access Quantities Base The DisplayName Attribute of each instance shall provide the name of the quantity, e.g. "acceleration", "battery
• OPC-10000-8 – OPC Unified Architecture - Part 8: Data Access
  6.4.2.2 UnitType ObjectType Definition
  UnitType ObjectType Definition It is formally defined in Table 43 . Table 43 - UnitType definition Attribute Value BrowseName UnitType IsAbstract True References NodeClass BrowseName DataType TypeDefinition Other Subtype of the BaseObjectType ... HasProperty Variable Discipline String PropertyType O Conformance Units Data Access Quantities Base The DisplayName Attribute of each instance shall provide the name of the unit, e.g. "second
• OPC-10000-8 – OPC Unified Architecture - Part 8: Data Access
  7.1 General
  View service set and Query service set to detect DataItems , and their Properties . The Attribute service set to read or write Attributes and in particular the value Attribute . The MonitoredItem
• OPC-10000-8 – OPC Unified Architecture - Part 8: Data Access
  A.3.1.3 Item
  Property. The Description property value in the DA server is assigned to the Description Attribute . The DataType property value in the DA server is assigned to the DataType Attribute ... item in the DA server is an array, the ValueRank Attribute is set as OneOrMoreDimensions. If not, it is set to Scalar. The AccessLevel Attribute is set with the AccessRights
• OPC-10000-8 – OPC Unified Architecture - Part 8: Data Access
  A.3.1.4 Property
  DataType value in the DA server is used as value for the DataType Attribute of the Property in the COM UA Wrapper. If the property value in the DA server ... array, the ValueRank Attribute of the Property is set to OneOrMoreDimensions. Otherwise, it is set to Scalar. If the property has an ItemID in the DA server , then the AccessLevel
• OPC-10000-9 – OPC Unified Architecture - Part 9: Alarms & Conditions
  4.10 Condition instances in the AddressSpace
  allows Data Access Clients to monitor the current Condition state by subscribing to the Attribute values of Variable Nodes . It is possible that the value of a node
• OPC-10000-9 – OPC Unified Architecture - Part 9: Alarms & Conditions
  5.2 Two-state state machines
  defined in 10000-16 . and formally defined in Table 1 . Table 1 - TwoStateVariableType definition Attribute Value BrowseName TwoStateVariableType DataType LocalizedText ValueRank -1 (-1 = Scalar) IsAbstract False References NodeClass BrowseName DataType ... Optional HasProperty Variable FalseState LocalizedText PropertyType Optional ConformanceUnits A & C Basic The Value Attribute of an instance of TwoStateVariableType contains the current state as a human readable name
• OPC-10000-9 – OPC Unified Architecture - Part 9: Alarms & Conditions
  5.3 ConditionVariable
  represented by a ConditionVariableType, formally defined in Table 2 . Table 2 - ConditionVariableType definition Attribute Value BrowseName ConditionVariableType DataType BaseDataType ValueRank -2 (-2 = Any) IsAbstract False References NodeClass BrowseName DataType TypeDefinition ... returned from the Read Service inside the DataValue structure for the ConditionVariable Value Attribute
• OPC-10000-9 – OPC Unified Architecture - Part 9: Alarms & Conditions
  D.2.1 Event areas
  Wrapper as Objects with a TypeDefinition of BaseObjectType . The EventNotifier Attribute for these Objects always has the SubscribeToEvents flag set to True. The root Area is represented by an Object ... shown in the UA Server address space. Some implementations could use the AREAS Attribute to provide filtering by Areas within the A&E COM UA Wrapper
• OPC-10000-9 – OPC Unified Architecture - Part 9: Alarms & Conditions
  D.2.4 Event attributes
  D.2.4 Event attributes Event Attribute s in the A&E COM Server are represented in the UA Server as Variables which are targets of HasProperty Reference s from ... represent the Event Categories. The BrowseName and DisplayName are the description for the Event Attribute . The data type of the Event Attribute is used to set DataType and ValueRank
• OPC-10000-9 – OPC Unified Architecture - Part 9: Alarms & Conditions
  D.2.5 Event subscriptions
  last Event is not available. Comment - The value of the ACK_COMMENT Attribute ClientUserId szActorID - AckedState wNewState Set to "Acknowledged" or "Unacknowledged" AckedState.Id wNewState
• OPC-10000-9 – OPC Unified Architecture - Part 9: Alarms & Conditions
  D.3.4 Event category mapping
  categories Category name is derived from the display name Attribute of the Node type as discovered in the type hierarchy of the UA A & C Server . Category description ... derived from the description Attribute of the Node type as discovered in the type hierarchy of the UA A & C Server . The A&E COM UA Proxy assigns
• OPC-10000-9 – OPC Unified Architecture - Part 9: Alarms & Conditions
  D.3.5 Event Category attribute mapping
  D.3.5 Event Category attribute mapping The collection of Attribute s associated with any given A&E Event is encapsulated within the ONEVENTSTRUCT. Therefore ... Proxy populates the Attribute fields within the ONEVENTSTRUCT using corresponding values from UA Event Notification s either directly (e.g., Source, Time, Severity) or indirectly (e.g., OPC COM Event category determined
• OPC-10000-9 – OPC Unified Architecture - Part 9: Alarms & Conditions
  D.3.6 Event Condition mapping
  Event processing proceeds as described in Table D.5 (see A&E ONEVENTSTRUCT " Attribute " rows: OPC_CONDITION_ACTIVE, OPC_CONDITION_ENABLED and OPC_CONDITION_ACKED
• OPC-10000-9 – OPC Unified Architecture - Part 9: Alarms & Conditions
  D.3.7 Browse mapping
  branches/areas such that each Object Node which contains a HasNotifier Reference and whose EventNotifier Attribute is set to SubscribeToEvents is considered an area. The root for the HasNotifier hierarchy ... Server Object , HasNotifier Reference s are followed and each HasNotifier target whose EventNotifier Attribute is set to SubscribeToEvents becomes a nested COM area within the hierarchy. Note that the HasNotifier
• OPC-10000-11 – OPC Unified Architecture - Part 11: Historical Access
  4.6 Bounding Values and time domain
  bounding value can be found. There are also cases, such as reading Annotations or Attribute data where Bounding Values may not be appropriate. For such use cases it is permissible
• OPC-10000-11 – OPC Unified Architecture - Part 11: Historical Access
  4.7 Changes in AddressSpace over time
  historized, then the Object should be maintained in the AddressSpace , with the appropriate AccessLevel Attribute and Historizing Attribute settings (see OPC 10000-3 for details on access levels ... audit Event of AuditHistoryConfigurationChangeEventType shall be generated. A Historian shall expose the Historizing attribute on any nodes that are currently collecting historical data. They shall also set the AccessLevel HistoryRead
• OPC-10000-11 – OPC Unified Architecture - Part 11: Historical Access
  5.6.2 HistoricalDataNodes Address Space Model
  with Historical Data Configuration and Annotations Each HistoricalDataNode with history shall have the Historizing Attribute (see OPC 10000-3 ) defined and can reference a HistoricalAccessConfiguration Object . In the case where ... data is available, a Client will look for the HistoryRead/Write states in the AccessLevel Attribute (see OPC 10000-3 for details on use of this Attribute ). Figure 3 only shows
• OPC-10000-11 – OPC Unified Architecture - Part 11: Historical Access
  5.8.2 AuditHistoryEventUpdateEventType
  representation in the AddressSpace is formally defined in Table 16 . Table 16 - AuditHistoryEventUpdateEventType definition Attribute Value BrowseName AuditHistoryEventUpdateEventType IsAbstract True References NodeClass BrowseName DataType TypeDefinition ModellingRule Subtype of the AuditHistoryUpdateEventType ... AuditHistoryUpdateEventType . Their semantic is defined in OPC 10000-3 . The UpdateNode identifies the Attribute that was written on the SourceNode . The PerformInsertReplace enumeration reflects the parameter on the Service call
• OPC-10000-11 – OPC Unified Architecture - Part 11: Historical Access
  5.8.3 AuditHistoryValueUpdateEventType
  representation in the AddressSpace is formally defined in Table 17 . Table 17 - AuditHistoryValueUpdateEventType definition Attribute Value BrowseName AuditHistoryValueUpdateEventType IsAbstract True References NodeClass BrowseName DataType TypeDefinition ModellingRule Subtype of the AuditHistoryUpdateEventType ... AuditHistoryUpdateEventType . Their semantic is defined in OPC 10000-3 . The UpdatedNode identifies the Attribute that was written on the SourceNode . The PerformInsertReplace enumeration reflects the parameter on the Service call
• OPC-10000-11 – OPC Unified Architecture - Part 11: Historical Access
  6.6.1 Overview
  returns different types of data depending on whether the request asked for the value Attribute of a Node or the history Events of a Node . The historyData is an Extensible
• OPC-10000-13 – OPC Unified Architecture - Part 13: Aggregates
  4.2.2.2 AggregateFunctionType
  Server . This Object is formally defined in Table 4 . Table 4 - AggregateFunctionType Definition Attribute Value BrowseName AggregateFunctionType IsAbstract False References Node Class BrowseName DataType Type Definition Mod. Rule Subtype ... Conformance Units Historical Access Aggregates For the AggregateFunctionType , the Description Attribute (inherited from the Base NodeClass ) , is mandatory. The Description Attribute provides a localized description of the Aggregate . Table
• OPC-10000-14 – OPC Unified Architecture - Part 14: PubSub
  6.2.3.7.1 PublishedData
  provided through the DataSetMetaData provided for the DataSet . AttributeId IntegerId Id of the Attribute to publish e.g. the Value Attribute . This shall be a valid Attribute id. The Attributes
• OPC-10000-14 – OPC Unified Architecture - Part 14: PubSub
  6.2.10.2.3 FieldTargetDataType
  type is defined in OPC 10000-4 . This parameter is null if the specified Attribute is not an array. However, if the specified Attribute is an array, and this parameter ... which the received DataSetMessage field value is written. AttributeId IntegerId Id of the Attribute to write e.g. the Value Attribute . This shall be a valid AttributeId . The Attributes are defined
• OPC-10000-14 – OPC Unified Architecture - Part 14: PubSub
  9.1.9.3 SubscribedDataSetMirrorType
  Subscriber AddressSpace . The SubscribedDataSetMirrorType is formally defined in Table 300 . Table 300 - SubscribedDataSetMirrorType definition Attribute Value BrowseName SubscribedDataSetMirrorType IsAbstract False References NodeClass BrowseName DataType TypeDefinition ModellingRule Subtype of SubscribedDataSetType defined ... Variables is CurrentRead . The RolePermissions is derived from the parent Node . The other Attribute values are taken from the FieldMetaData . The properties in the FieldMetaData are created as Properties
• OPC-10000-16 – OPC Unified Architecture - Part 16: State Machines
  4.4.2 StateMachineType
  StateMachine . Subtypes may add Methods which affect the state of the machine. The Executable Attribute is used to indicate whether the Method is valid given the current state ... StateMachineType is formally defined in Table 1 . Table 1 - StateMachineType definition Attribute Value BrowseName StateMachineType IsAbstract False References Node Class BrowseName DataType TypeDefinition Modelling Rule Subtype of the BaseObjectType defined
• OPC-10000-16 – OPC Unified Architecture - Part 16: State Machines
  4.4.6 FiniteStateMachineType
  each of the Transitions that may be triggered by the Method . The Executable Attribute for a Method is used to indicate whether the current State of the machine allows ... Table 19 ). The FiniteStateMachineType is formally defined in Table 6 . Table 6 - FiniteStateMachineType definition Attribute Value BrowseName FiniteStateMachineType IsAbstract True References Node Class BrowseName DataType TypeDefinition Modelling Rule Subtype
• OPC-10000-18 – OPC Unified Architecture - Part 18: Role-Based Security
  4.2.1 RoleSetType definition
  RoleSetType which is formally defined in Table 1 . Table 1 - RoleSetType definition Attribute Value BrowseName RoleSetType IsAbstract False References Node Class BrowseName DataType TypeDefinition Modelling Rule Subtype of BaseObjectType defined
• OPC-10000-18 – OPC Unified Architecture - Part 18: Role-Based Security
  4.3 RoleSet
  used to publish all Roles supported by the Server . Table 4 - RoleSet definition Attribute Value BrowseName RoleSet References Node Class BrowseName DataType TypeDefinition Modelling Rule ComponentOf the ServerCapabilities Object defined
• OPC-10000-18 – OPC Unified Architecture - Part 18: Role-Based Security
  4.4.1 RoleType definition
  RoleType which is formally defined in Table 6 . Table 6 - RoleType definition Attribute Value BrowseName RoleType IsAbstract False References Node Class BrowseName DataType TypeDefinition Modelling Rule Subtype of BaseObjectType HasProperty ... Properties are configured with the corresponding Method calls. The CurrentWrite bit of the AccessLevel Attribute for the Properties Identities , Applications and Endpoints shall be FALSE. If the configuration
• OPC-10000-18 – OPC Unified Architecture - Part 18: Role-Based Security
  5.2.1 UserManagementType definition
  UserManagementType which is formally defined in Table 21 . Table 21 - UserManagementType definition Attribute Value BrowseName UserManagementType IsAbstract False References Node Class BrowseName DataType TypeDefinition Modelling Rule Subtype of BaseObjectType defined
• OPC-10000-18 – OPC Unified Architecture - Part 18: Role-Based Security
  5.3 UserManagement
  used to manage users known to the Server . Table 32 - UserManagement definition Attribute Value BrowseName UserManagement References Node Class BrowseName DataType TypeDefinition Modelling Rule ComponentOf the ServerConfiguration Object defined
• OPC-10000-22 – OPC Unified Architecture - Part 22: Base Network Model
  5.2.1 IIetfBaseNetworkInterfaceType Interface
  network interface. The IIetfBaseNetworkInterfaceType is formally defined in Table 1 . Table 1 - IIetfBaseNetworkInterfaceType definition Attribute Value BrowseName IIetfBaseNetworkInterfaceType IsAbstract True References NodeClass BrowseName DataType TypeDefinition ModellingRule Subtype of the BaseInterfaceType ... defined in IETF RFC 2863 ). The component Variables of the IIetfBaseNetworkInterfaceType have the Attribute values defined in Table 2 . Table 2 - IIetfBaseNetworkInterfaceType Attribute values for child Nodes Source Path Value
• OPC-10000-22 – OPC Unified Architecture - Part 22: Base Network Model
  5.2.2 IIeeeBaseEthernetPortType Interface
  based port. The IIeeeBaseEthernetPortType is formally defined in Table 3 . Table 3 - IIeeeBaseEthernetPortType definition Attribute Value BrowseName IIeeeBaseEthernetPortType IsAbstract True References NodeClass BrowseName DataType TypeDefinition Modelling Rule Subtype ... IEEE 802.3-2022 , clause 30.3.1.1.37, aMaxFrameLength). The component Variables of the IIeeeBaseEthernetPortType have the Attribute values defined in Table 4 . Table 4 - IIeeeBaseEthernetPortType Attribute values for child Nodes Source Path
• OPC-10000-22 – OPC Unified Architecture - Part 22: Base Network Model
  5.5.1.2 IetfBaseNetworkInterfaceType definition
  IetfBaseNetworkInterfaceType definition The IetfBaseNetworkInterfaceType is formally defined in Table 58 . Table 58 - IetfBaseNetworkInterfaceType definition Attribute Value BrowseName IetfBaseNetworkInterfaceType IsAbstract False References Node Class BrowseName DataType TypeDefinition Other Subtype ... PubSub connection is shown in Annex A.2 . The components of the IetfBaseNetworkInterfaceType have the Attribute values defined in Table 59 . Table 59 - IetfBaseNetworkInterfaceType Attribute values for child Nodes Source Path
• OPC-10000-24 – OPC Unified Architecture - Part 24: Scheduler
  7.1.2 ObjectType definition
  ObjectType definition Table 4 - CalendarType Definition Attribute Value BrowseName CalendarType IsAbstract False Description Provides a list of calendar dates. Each entry in the list describes a specific date or date ... date pattern, or range of dates. The child Nodes of the CalendarType have additional Attribute values defined in Table 5 . Table 5 - CalendarType Attribute values for child Nodes BrowsePath Description
• OPC-10000-24 – OPC Unified Architecture - Part 24: Scheduler
  7.2.2 ObjectType definition
  ObjectType definition Table 10 - ScheduleType definition Attribute Value BrowseName ScheduleType IsAbstract False Description Defines a periodic schedule that can recur over a range of dates. The schedule may have optional ... schedule Object (see 6.3 for details). The child Nodes of the ScheduleType have additional Attribute values defined in Table 11 . Table 11 - ScheduleType Attribute values for child Nodes BrowsePath Description
• OPC-10000-25 – OPC Unified Architecture - Part 25: Object Serialization
  4.2 Read Access to the SerializationValue
  access creates the SerializationValue . The DataType of the SerializationValue is provided by the DataType Attribute . The Server may create the DataType information at the time when the SerializationValue DataType
• OPC-10000-25 – OPC Unified Architecture - Part 25: Object Serialization
  6.3.2 SerializedData Variable
  SerializationValue is the SerializationValue DataType and is a subtype of Structure where the DataTypeDefinition Attribute of this DataType provides the metadata and encoding information. The DataType Node including the DataTypeDefinition ... Attribute is dynamically created. It only has an inverse Reference to its supertype Structure . Clients must obtain the NodeId by reading the DataType Attribute of the SerializedData Variable . Then they
• OPC-10000-25 – OPC Unified Architecture - Part 25: Object Serialization
  6.3.3 ConfigureSerialization Method
  Server will create a new DataType for the SerializedData Variable with the DataTypeDefinition Attribute for the metadata and encoding information. The signature of this Method is specified below. Table ... hierarchical References are not allowed to be included Table 4 - ConfigureSerialization Method AddressSpace definition Attribute Value BrowseName ConfigureSerialization References NodeClass BrowseName DataType TypeDefinition Other HasProperty Variable InputArguments Argument[] PropertyType
• OPC-10000-81 – OPC Unified Architecture - Part 81: UAFX Connecting Devices and Information Model
  3.3.1 Usage of Other column in type definitions
  ModellingRule . OptionalPlaceholder OP The Node has the OptionalPlaceholder ModellingRule . ReadOnly RO The Node AccessLevel Attribute has the CurrentRead bit set but not the CurrentWrite bit. ReadWrite RW The Node AccessLevel ... Attribute has the CurrentRead and CurrentWrite bits set. WriteOnly WO The Node AccessLevel Attribute has the CurrentWrite bit set but not the CurrentRead bit. If multiple characteristics are defined, they
• OPC-10000-81 – OPC Unified Architecture - Part 81: UAFX Connecting Devices and Information Model
  13.1 Overview
  resolve Node information. Resolving Node information may require using View Services ( Browse , TranslateBrowsePathsToNodeIds ) and Attribute Services ( Read ). The details related to an application's configuration are provided in a Descriptor
• OPC-10000-100 – OPC Unified Architecture - Part 100: Devices
  3.3.1.1 Node definitions
  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 are defined by providing ... column is introduced to point to the Node definition. Table 2 - Type Definition table Attribute Value Attribute name Attribute value. If it is an optional Attribute that
• OPC-10000-100 – OPC Unified Architecture - Part 100: Devices
  3.3.1.4 Additional Attribute values
  Additional Attribute 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 ... Table 6 is used. Table 6 - <some>Type Attribute values for child Nodes BrowsePath <Attribute name> Attribute BrowsePath is always relative to the TypeDefinition. Multiple elements
• OPC-10000-100 – OPC Unified Architecture - Part 100: Devices
  3.3.3.1 General
  mandatory and shall be provided by a Server . The following tables define if the Attribute value is defined by this document or if it is server-specific. For all Nodes ... shall be set as specified in the table. Table 7 - Common Node Attributes Attribute Value DisplayName The DisplayName is a LocalizedText . Each Server shall provide the DisplayName identical
• OPC-10000-100 – OPC Unified Architecture - Part 100: Devices
  3.3.3.3 Variables
  Attributes can be found in OPC 10000-3 . Table 9 - Common Variable Attributes Attribute Value MinimumSamplingInterval Optionally, a server-specific minimum sampling interval is provided. AccessLevel The access level ... shall allow reading; other settings are server-specific. UserAccessLevel The value for the UserAccessLevel Attribute is server-specific. It is assumed that all Variables can be accessed by at least
• OPC-10000-100 – OPC Unified Architecture - Part 100: Devices
  3.3.3.4 VariableTypes
  ValueRank <= 0) the ArrayDimensions can either be set to null or the Attribute is missing. This behavior is server-specific. If the ValueRank specifies an array of a specific ... dimension (i.e. ValueRank > 0) then the ArrayDimensions Attribute shall be specified in the table defining the VariableType
• OPC-10000-100 – OPC Unified Architecture - Part 100: Devices
  3.3.3.5 Methods
  Attributes Attributes Value Executable All Methods defined in this document shall be executable ( Executable Attribute set to "True"), unless it is defined differently in the Method definition. UserExecutable ... value of the UserExecutable Attribute is server-specific. It is assumed that all Methods can be executed by at least one user
• OPC-10000-100 – OPC Unified Architecture - Part 100: Devices
  4.4.2 Well-Known FunctionalGroup BrowseNames
  configuration items of the TopologyElement . If the CurrentWrite bit is set in the AccessLevel Attribute they can be modified by Clients . Tuning Parameters and Methods to optimize the behavior
• OPC-10000-100 – OPC Unified Architecture - Part 100: Devices
  4.5.5 OperationCounter Interface
  duration of operation. It is formally defined in Table 24 . Table 24 - IOperationCounterType definition Attribute Value BrowseName 1:IOperationCounterType IsAbstract True Description Interface defining counters for the duration of operation ... reset when the Device is restarted. The child Nodes of the IOperationCounterType have additional Attribute values defined in Table 25 . Table 25 - IOperationCounterType Attribute values for child Nodes BrowsePath Description
• OPC-10000-100 – OPC Unified Architecture - Part 100: Devices
  10.2 LifetimeVariableType definition
  things like software. It is formally defined in Table 144 . Table 144 - LifetimeVariableType definition Attribute Value BrowseName 1:LifetimeVariableType IsAbstract False ValueRank -1 (-1 = Scalar) DataType Number Description Remaining lifetime ... remaining time is provided. The child Nodes of the LifetimeVariableType have additional Attribute values defined in Table 145 . Table 145 - LifetimeVariableType Attribute values for child Nodes BrowsePath Description Attribute
• OPC-10000-110 – OPC Unified Architecture - Part 110: Asset Management Basics
  3.3.1.1 Node definitions
  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 are defined by providing ... column is introduced to point to the Node definition. Table 2 - Type Definition Table Attribute Value Attribute name Attribute value. If it is an optional Attribute that
• OPC-10000-110 – OPC Unified Architecture - Part 110: Asset Management Basics
  3.3.1.4 Additional Attribute values
  Additional Attribute 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 ... Table 6 is used. Table 6 - <some>Type Attribute values for child Nodes BrowsePath <Attribute name> Attribute BrowsePath is always relative to the TypeDefinition . Multiple elements
• OPC-10000-110 – OPC Unified Architecture - Part 110: Asset Management Basics
  3.3.3.1 General
  mandatory and shall be provided by a Server . The following tables define if the Attribute value is defined by this document or if it is server-specific. For all Nodes ... shall be set as specified in the table. Table 7 - Common Node Attributes Attribute Value DisplayName The DisplayName is a LocalizedText . Each Server shall provide the DisplayName identical
• OPC-10000-110 – OPC Unified Architecture - Part 110: Asset Management Basics
  3.3.3.3 Variables
  Attributes can be found in OPC 10000-3 . Table 9 - Common Variable Attributes Attribute Value MinimumSamplingInterval Optionally, a server-specific minimum sampling interval is provided. AccessLevel The access level ... shall allow reading; other settings are server-specific. UserAccessLevel The value for the UserAccessLevel Attribute is server-specific. It is assumed that all Variables can be accessed by at least
• OPC-10000-110 – OPC Unified Architecture - Part 110: Asset Management Basics
  3.3.3.4 VariableTypes
  ValueRank <= 0) the ArrayDimensions can either be set to null or the Attribute is missing. This behaviour is server-specific. If the ValueRank specifies an array of a specific ... dimension (i.e. ValueRank > 0) then the ArrayDimensions Attribute shall be specified in the table defining the VariableType
• OPC-10000-110 – OPC Unified Architecture - Part 110: Asset Management Basics
  3.3.3.5 Methods
  Attributes Attributes Value Executable All Methods defined in this document shall be executable ( Executable Attribute set to "True"), unless it is defined differently in the Method definition. UserExecutable ... value of the UserExecutable Attribute is server-specific. It is assumed that all Methods can be executed by at least one user
• OPC-10000-110 – OPC Unified Architecture - Part 110: Asset Management Basics
  9.4.2 IRootCauseIndicationType
  AlarmTypes , but in general to subtypes of 0: ConditionType . Table 16 - IRootCauseIndicationType Definition Attribute Value BrowseName IRootCauseIndicationType IsAbstract True Description Information on the root cause of conditions, should be applied ... that the root cause is unknown. The child Nodes of the IRootCauseIndicationType have additional Attribute values defined in Table 17 . Table 17 - IRootCauseIndicationType Attribute values for child Nodes BrowsePath Value
• OPC-10000-110 – OPC Unified Architecture - Part 110: Asset Management Basics
  9.6 Tracking of health information
  used. For each 2: DeviceHealth Variable , where the history is currently tracked, the Historizing Attribute is set to True and the AccessLevel is set to HistoryRead . In order to provide
• OPC-10000-110 – OPC Unified Architecture - Part 110: Asset Management Basics
  10.5.3 AddLink Method
  after resetting or reconfiguring the Server or after calling the RemoveLink Method . The Value Attribute of the created Node should be writable, so the end-user can change ... general description. Table 32 - AddLink Method AddressSpace definition Attribute Value BrowseName AddLink References NodeClass BrowseName DataType TypeDefinition ModellingRule 0:HasProperty Variable 0:InputArguments 0:Argument[] 0:PropertyType 0:Mandatory
• OPC-10000-110 – OPC Unified Architecture - Part 110: Asset Management Basics
  12.2 IMaintenanceEventType
  ConditionTypes . It is formally defined in Table 35 . Table 35 - IMaintenanceEventType Definition Attribute Value BrowseName IMaintenanceEventType IsAbstract True Description Information on maintenance activities, should by applied to conditions (ConditionType ... notify Clients with an Event notification. The child Nodes of the IMaintenanceEventType have additional Attribute values defined in Table 36 . Table 36 - IMaintenanceEventType Attribute values for child Nodes BrowsePath Description
• OPC-10000-120 – OPC Unified Architecture - Part 120: OPC UA and XML Data Type Mapping
  3.3.1.1 Node definitions
  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 are defined by providing ... target of a HasSubtype Reference . For Variables and VariableTypes , the value of the DataType Attribute is a dependency. For DataType Nodes , any DataTypes referenced in the DataTypeDefinition Attribute are also
• OPC-10000-120 – OPC Unified Architecture - Part 120: OPC UA and XML Data Type Mapping
  3.3.1.4 Additional Attribute values
  Additional Attribute 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 ... Table 6 is used. Table 6 - <some>Type Attribute values for child Nodes BrowsePath <Attribute name> Attribute BrowsePath is always relative to the TypeDefinition . Multiple elements
• OPC-10000-120 – OPC Unified Architecture - Part 120: OPC UA and XML Data Type Mapping
  3.3.3.1 General
  mandatory and shall be provided by a Server . The following tables define if the Attribute value is defined by this document or if it is server-specific. For all Nodes ... shall be set as specified in the table. Table 7 - Common Node Attributes Attribute Value DisplayName The DisplayName is a LocalizedText . Each Server shall provide the DisplayName identical
• OPC-10000-120 – OPC Unified Architecture - Part 120: OPC UA and XML Data Type Mapping
  3.3.3.3 Variables
  Attributes can be found in OPC 10000-3 . Table 9 - Common Variable Attributes Attribute Value MinimumSamplingInterval Optionally, a server-specific minimum sampling interval is provided. AccessLevel The access level ... shall allow reading; other settings are server-specific. UserAccessLevel The value for the UserAccessLevel Attribute is server-specific. It is assumed that all Variables can be accessed by at least
• OPC-10000-120 – OPC Unified Architecture - Part 120: OPC UA and XML Data Type Mapping
  3.3.3.4 VariableTypes
  ValueRank <= 0) the ArrayDimensions can either be set to null or the Attribute is missing. This behaviour is server-specific. If the ValueRank specifies an array of a specific ... dimension (i.e. ValueRank > 0) then the ArrayDimensions Attribute shall be specified in the table defining the VariableType
• OPC-10000-120 – OPC Unified Architecture - Part 120: OPC UA and XML Data Type Mapping
  3.3.3.5 Methods
  Attributes Attributes Value Executable All Methods defined in this document shall be executable ( Executable Attribute set to "True"), unless it is defined differently in the Method definition. UserExecutable ... value of the UserExecutable Attribute is server-specific. It is assumed that all Methods can be executed by at least one user
• OPC-10000-200 – OPC Unified Architecture - Part 200: Industrial Automation
  3.3.1 Conventions for Node descriptions
  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 are defined by providing ... column is introduced to point to the Node definition. Table 2 - Type Definition Table Attribute Value Attribute name Attribute value. If it is an optional Attribute that
• OPC-10000-200 – OPC Unified Architecture - Part 200: Industrial Automation
  3.3.1.3 Additional Attribute values
  Additional Attribute 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 ... Table 6 is used. Table 6 - <some>Type Attribute values for child Nodes BrowsePath <Attribute name> Attribute BrowsePath is always relative to the TypeDefinition . Multiple elements
• OPC-10000-200 – OPC Unified Architecture - Part 200: Industrial Automation
  3.3.3.1 General
  mandatory and shall be provided by a Server . The following tables define if the Attribute value is defined by this document or if it is server-specific. For all Nodes ... shall be set as specified in the table. Table 7 - Common Node Attributes Attribute Value DisplayName The DisplayName is a LocalizedText . Each server shall provide the DisplayName identical
• OPC-10000-200 – OPC Unified Architecture - Part 200: Industrial Automation
  3.3.3.3 Variables
  Attributes can be found in OPC 10000-3 . Table 9 - Common Variable Attributes Attribute Value MinimumSamplingInterval Optionally, a server-specific minimum sampling interval is provided. AccessLevel The access level ... shall allow reading; other settings are server-specific. UserAccessLevel The value for the UserAccessLevel Attribute is server-specific. It is assumed that all Variables can be accessed by at least
• OPC-10000-200 – OPC Unified Architecture - Part 200: Industrial Automation
  3.3.3.4 VariableTypes
  ValueRank <= 0) the ArrayDimensions can either be set to null or the Attribute is missing. This behaviour is server-specific. If the ValueRank specifies an array of a specific ... dimension (i.e. ValueRank > 0) then the ArrayDimensions Attribute shall be specified in the table defining the VariableType
• OPC-10000-200 – OPC Unified Architecture - Part 200: Industrial Automation
  3.3.3.5 Methods
  Attributes Attributes Value Executable All Methods defined in this document shall be executable ( Executable Attribute set to "True"), unless it is defined differently in the Method definition. UserExecutable ... value of the UserExecutable Attribute is server-specific. It is assumed that all Methods can be executed by at least one user
• OPC-10000-200 – OPC Unified Architecture - Part 200: Industrial Automation
  5.2.1 BasicStacklightType
  overview is given. It is formally defined in Table 12 . Table 12 - BasicStacklightType Definition Attribute Value BrowseName BasicStacklightType IsAbstract False Description Entry point to a stacklight containing elements ... ordering from the base of the stacklight. The InstanceDeclarations of the BasicStacklightType have the Attribute values defined in Table 13 . Table 13 - BasicStacklightType Attribute values for child Nodes Source Path
• OPC-10000-200 – OPC Unified Architecture - Part 200: Industrial Automation
  5.2.2 StacklightType
  overview is given. It is formally defined in Table 14 . Table 14 - StacklightType Definition Attribute Value BrowseName StacklightType IsAbstract False Description Entry point to a stacklight with the possibility ... used as specified in OPC 10000-100 . The InstanceDeclarations of the StacklightType have the Attribute values defined in Table 15 . Table 15 - StacklightType Attribute values for child Nodes Source Path
• OPC-10000-200 – OPC Unified Architecture - Part 200: Industrial Automation
  5.2.3 StackLevelType
  overview is given. It is formally defined in Table 16 . Table 16 - StackLevelType Definition Attribute Value BrowseName StackLevelType IsAbstract False Description Contains information relevant to a stacklight operating ... percentual value is displayed with the stacklight. The InstanceDeclarations of the StackLevelType have the Attribute values defined in Table 17 . Table 17 - StackLevelType Attribute values for child Nodes Source Path
• OPC-10000-200 – OPC Unified Architecture - Part 200: Industrial Automation
  5.2.5 StackElementType
  overview is given. It is formally defined in Table 19 . Table 19 - StackElementType Definition Attribute Value BrowseName StackElementType IsAbstract True Description Base class for elements in a stacklight. References Node ... beginning from the base of the stacklight. The InstanceDeclarations of the StackElementType have the Attribute values defined in Table 20 . Table 20 - StackElementType Attribute values for child Nodes Source Path
• OPC-10000-200 – OPC Unified Architecture - Part 200: Industrial Automation
  5.2.6 StackElementLightType
  overview is given. It is formally defined in Table 21 . Table 21 - StackElementLightType Definition Attribute Value BrowseName StackElementLightType IsAbstract False Description Represents a lamp element in a stacklight. References Node ... independent colour channel of the stacked element. The InstanceDeclarations of the StackElementLightType have the Attribute values defined in Table 22 . Table 22 - StackElementLightType Attribute values for child Nodes Source Path
• OPC-10000-200 – OPC Unified Architecture - Part 200: Industrial Automation
  5.2.7 StackElementAcousticType
  overview is given. It is formally defined in Table 23 . Table 23 - StackElementAcousticType Definition Attribute Value BrowseName StackElementAcousticType IsAbstract False Description Represents an acoustic element in a stacklight. References Node ... Object 0:<OrderedObject> AcousticSignalType MP The InstanceDeclarations of the StackElementAcousticType have the Attribute values defined in Table 25 . Table 25 - StackElementAcousticType Attribute values for child Nodes Source Path
• OPC-10000-200 – OPC Unified Architecture - Part 200: Industrial Automation
  5.2.8 ControlChannelType
  overview is given. It is formally defined in Table 26 . Table 26 - ControlChannelType Definition Attribute Value BrowseName ControlChannelType IsAbstract False Description Used for control channels of single colour elements within ... highest is interpreted as 100 percent. The InstanceDeclarations of the ControlChannelType have the Attribute values defined in Table 27 . Table 27 - ControlChannelType Attribute values for child Nodes Source Path Value
• OPC-10000-200 – OPC Unified Architecture - Part 200: Industrial Automation
  5.2.9 AcousticSignalType
  overview is given. It is formally defined in Table 28 . Table 28 - AcousticSignalType Definition Attribute Value BrowseName AcousticSignalType IsAbstract False Description Represents an acoustic signal. References Node Class BrowseName DataType ... PropertyType M 0:HasComponent Variable AudioSample 0:AudioDataType 0:BaseDataVariableType O The Description Attribute of each Object of type AcousticSignalType should be used as textual description of the audio signal
• OPC-10000-200 – OPC Unified Architecture - Part 200: Industrial Automation
  6.2.1.1 Overview
  IStatisticsType Interface IStatisticsType is formally defined in Table 40 . Table 40 - IStatisticsType Definition Attribute Value BrowseName IStatisticsType IsAbstract True Description Base interface for managing statistical data. References Node Class BrowseName ... IStatisticsType directly, but only subtypes of it. The InstanceDeclarations of the IStatisticsType have the Attribute values defined in Table 41 . Table 41 - IStatisticsType Attribute values for child Nodes Source Path
• OPC-10000-200 – OPC Unified Architecture - Part 200: Industrial Automation
  6.2.2 IAggregateStatisticsType
  tracking gets reset. It is formally defined in Table 43 . Table 43 - IAggregateStatisticsType Definition Attribute Value BrowseName IAggregateStatisticsType IsAbstract True Description Base interface for managing statistical data that ... resets the statistics on a local HMI. The InstanceDeclarations of the IAggregateStatisticsType have the Attribute values defined in Table 44 . Table 44 - IAggregateStatisticsType Attribute values for child Nodes Source Path
• OPC-10000-200 – OPC Unified Architecture - Part 200: Industrial Automation
  6.2.3 IRollingStatisticsType
  statistical data. It is formally defined in Table 45 . Table 45 - IRollingStatisticsType Definition Attribute Value BrowseName IRollingStatisticsType IsAbstract True Description Base interface for managing statistical data that is rolled over ... maximum of one of those Properties . The InstanceDeclarations of the IRollingStatisticsType have the Attribute values defined in Table 46 . Table 46 - IRollingStatisticsType Attribute values for child Nodes Source Path Value
• OPC-10000-200 – OPC Unified Architecture - Part 200: Industrial Automation
  7.4.1 CalibrationTargetType ObjectType
  target, or subtyped to define specific types of calibration targets. Table 48 - CalibrationTargetType Definition Attribute Value BrowseName CalibrationTargetType IsAbstract False Description Provides information about a calibration target. References Node Class ... ComponentName 0:LocalizedText 0:PropertyType O The child Nodes of the CalibrationTargetType have additional Attribute values defined in Table 50 . Table 50 - CalibrationTargetType Attribute values for child Nodes BrowsePath Description
• OPC-10000-200 – OPC Unified Architecture - Part 200: Industrial Automation
  7.5.2 CapacityRangeType
  each step. The VariableType is formally defined in Table 57 . Table 58 - CapacityRangeType Definition Attribute Value BrowseName CapacityRangeType IsAbstract False ValueRank -1 (-1 = Scalar) DataType 0:Range Description Represent ... step size and is used in combination with the Range provided in the Value Attribute to determine, what individual calibration values can be used for calibration. Remark: The quantity
• OPC-10000-210 – OPC Unified Architecture - Part 210: Relative Spatial Location
  3.4.1.1 Node definitions
  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 are defined by providing ... column is introduced to point to the Node definition. Table 2 - Type Definition Table Attribute Value Attribute name Attribute value. If it is an optional Attribute that
• OPC-10000-210 – OPC Unified Architecture - Part 210: Relative Spatial Location
  3.4.1.4 Additional Attribute values
  Additional Attribute 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 ... Table 6 is used. Table 6 - <some>Type Attribute values for child Nodes BrowsePath <Attribute name> Attribute BrowsePath is always relative to the TypeDefinition . Multiple elements
• OPC-10000-210 – OPC Unified Architecture - Part 210: Relative Spatial Location
  3.4.3.1 General
  mandatory and shall be provided by a Server . The following tables define if the Attribute value is defined by this document or if it is server-specific. For all Nodes ... shall be set as specified in the table. Table 7 - Common Node Attributes Attribute Value DisplayName The DisplayName is a LocalizedText . Each Server shall provide the DisplayName identical
• OPC-10000-210 – OPC Unified Architecture - Part 210: Relative Spatial Location
  3.4.3.3 Variables
  Attributes can be found in OPC 10000-3 . Table 9 - Common Variable Attributes Attribute Value MinimumSamplingInterval Optionally, a server-specific minimum sampling interval is provided. AccessLevel The access level ... shall allow reading; other settings are server-specific. UserAccessLevel The value for the UserAccessLevel Attribute is server-specific. It is assumed that all Variables can be accessed by at least
• OPC-10000-210 – OPC Unified Architecture - Part 210: Relative Spatial Location
  3.4.3.4 VariableTypes
  ValueRank <= 0) the ArrayDimensions can either be set to null or the Attribute is missing. This behaviour is server-specific. If the ValueRank specifies an array of a specific ... dimension (i.e. ValueRank > 0) then the ArrayDimensions Attribute shall be specified in the table defining the VariableType
• OPC-10000-210 – OPC Unified Architecture - Part 210: Relative Spatial Location
  3.4.3.5 Methods
  Attributes Attributes Value Executable All Methods defined in this document shall be executable ( Executable Attribute set to "True"), unless it is defined differently in the Method definition. UserExecutable ... value of the UserExecutable Attribute is server-specific. It is assumed that all Methods can be executed by at least one user