Search

200 result(s) for Variables

• OPC-10000-1 – OPC Unified Architecture - Part 1: Overview and Concepts
  6.7 Attribute Service Set
  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
  Service Set is 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 ... specifies the rate at which the item is to be monitored (sampled) and, for Variables and EventNotifiers , the filter criteria used to determine when a Notification is to be generated
• 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.1.7 DataVariable
  DataVariable Variables that represent values of Objects , either directly or indirectly for complex Variables , where the Variables are always the TargetNode of a HasComponent Reference
• OPC-10000-3 – OPC Unified Architecture - Part 3: Address Space Model
  3.1.13 Property
  Property Variables that are the TargetNode for a HasProperty Reference Note 1 to entry: Properties describe the characteristics of a Node
• OPC-10000-3 – OPC Unified Architecture - Part 3: Address Space Model
  4.3 Object Model
  Model has been designed to meet this objective. It defines Objects in terms of Variables and Methods . It also allows relationships to other Objects to be expressed. Figure 2 illustrates
• OPC-10000-3 – OPC Unified Architecture - Part 3: Address Space Model
  4.5.1 General
  General Variables are used to represent values . Two types of Variables are defined, Properties and DataVariables . They differ in the kind of data that they represent and whether they ... contain other Variables
• OPC-10000-3 – OPC Unified Architecture - Part 3: Address Space Model
  4.5.2 Properties
  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 unit of some Variables
• OPC-10000-3 – OPC Unified Architecture - Part 3: Address Space Model
  4.6.1 General
  General OPC UA Servers shall provide type definitions for Objects and Variables . The HasTypeDefinition Reference shall be used to link an instance with its type definition represented by a TypeDefinitionNode ... such a base 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
• OPC-10000-3 – OPC Unified Architecture - Part 3: Address Space Model
  5.6.1 General
  General Two types of Variables are defined, Properties and DataVariables . Although they differ in the way they are used as described in 4.5 and have different constraints described
• OPC-10000-3 – OPC Unified Architecture - Part 3: Address Space Model
  5.6.2 Variable NodeClass
  Variable NodeClass Variables are used to represent values which may be simple or complex. Variables are defined by VariableTypes , as specified in 5.6.5 . Variables are always defined as Properties ... least one other Node , but may be related to any number of other Nodes . Variables are defined using the Variable NodeClass , specified in Table 13 . Table 13 - Variable NodeClass Name
• OPC-10000-3 – OPC Unified Architecture - Part 3: Address Space Model
  5.6.3 Properties
  Node . It is not permitted for a Node to refer to two Variables using HasProperty References having the same BrowseName
• OPC-10000-3 – OPC Unified Architecture - Part 3: Address Space Model
  5.6.5 VariableType NodeClass
  VariableType NodeClass VariableTypes are used to provide type definitions for Variables . VariableTypes are defined using the VariableType NodeClass , as specified in Table 14 . Table 14 - VariableType NodeClass Name Use Data ... shall exist, only of its subtypes. FALSE it is not an abstract VariableType , i.e. Variables of this type can exist. References HasProperty 0..* HasProperty References are used to identify
• OPC-10000-3 – OPC Unified Architecture - Part 3: Address Space Model
  5.6.6 Client-side creation of Variables of an VariableType
  Client-side creation of Variables of an VariableType Variables are always based on a VariableType , i.e. they have a HasTypeDefinition Reference pointing to its VariableType . Clients can create Variables using
• OPC-10000-3 – OPC Unified Architecture - Part 3: Address Space Model
  5.8.1 DataType Model
  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 ... 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 - the DataTypeId - will
• OPC-10000-3 – OPC Unified Architecture - Part 3: Address Space Model
  5.8.2 Encoding Rules for different kinds of DataTypes
  supported, which do not have any encodings and cannot be exchanged on the wire. Variables and VariableTypes use abstract DataTypes to indicate that their Value
• OPC-10000-3 – OPC Unified Architecture - Part 3: Address Space Model
  5.8.3 DataType NodeClass
  DataType is abstract or not. Abstract DataTypes can be used in the AddressSpace , i.e. Variables and VariableTypes can point with their DataType Attribute to an abstract DataType . However, concrete values
• OPC-10000-3 – OPC Unified Architecture - Part 3: Address Space Model
  5.8.5.3 Usage of DataTypeRefinements
  used from any DataType Node , from any VariableType , or any InstanceDeclaration , only from concrete Variables . This does include Variables describing a DataTypeRefinement , as shown in Figure 21 . Note, that Method ... Arguments can be further described using Variables referenced with a HasArgumentDescription . If the Method Argument is a Structured DataType , this Variable can be used as SourceNode for the UsesDataTypeRefinement
• OPC-10000-3 – OPC Unified Architecture - Part 3: Address Space Model
  5.8.5.4 Example of usage of DataTypeRefinements
  Var1 and Z:Var2, as defined on the X:SuperObjectType. Although all three Variables use the same DataType , the Z:Prop1 is refined by Y:Refinement_4 and Z:Var2
• OPC-10000-3 – OPC Unified Architecture - Part 3: Address Space Model
  5.8.6.1 Overview
  from exactly one DataType Node using a HasDataTypeRefinement Reference . A SubtypeRestriction Object is referencing Variables with an AllowedSubtype Reference (see 7.29 ), and thereby restricting that the DataType including ValueRank ... subtyping rules, etc. A SubtypeRestriction Object should have at least two AllowedSubtype References to Variables defining different variations of subtypes. Otherwise, a Variable using the SubtypeRestriction should just
• OPC-10000-3 – OPC Unified Architecture - Part 3: Address Space Model
  6.2.4 Similar Node of InstanceDeclaration
  that has the same BrowseName and NodeClass as the InstanceDeclaration and in cases of Variables and Objects the same TypeDefinitionNode or a subtype of it. In the case
• OPC-10000-3 – OPC Unified Architecture - Part 3: Address Space Model
  6.3.3.3 Overriding InstanceDeclarations
  Reference but the new target shall have the same NodeClass and for Objects and Variables also the same type or a subtype of the type specified in the parent
• OPC-10000-3 – OPC Unified Architecture - Part 3: Address Space Model
  6.4.1 Overview
  shall have the same BrowseName and NodeClass as the InstanceDeclaration and, in cases of Variables and Objects , the same TypeDefinitionNode or a subtype of it. Instances may reference several Nodes
• 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 ... ModellingRules defined on the InstanceDeclarations of the TypeDefinitionNode are still fulfilled. For Variables and Objects the HasTypeDefinition Reference shall always point to the same TypeDefinitionNode as the InstanceDeclaration
• OPC-10000-3 – OPC Unified Architecture - Part 3: Address Space Model
  6.4.4.4.3 ExposesItsArray
  array (e.g. the second). Clients will typically either get the array or access the Variables directly, so there is no need to provide that information. It is allowed to reference
• OPC-10000-3 – OPC Unified Architecture - Part 3: Address Space Model
  7.22.1 Overview
  that a VariableType or Variable also exposes its Structure fields or Array elements as Variables in the information model. The SourceNode of this ReferenceType shall be a VariableType
• OPC-10000-3 – OPC Unified Architecture - Part 3: Address Space Model
  7.22.2 Differences between HasStructuredComponent and ExposesItsArray
  HasStructuredComponent . When the first entry in the array is deleted, the Values of the Variables representing the first and second entry are changed accordingly, and the third Variable is deleted ... ExposesItsArray . When the first entry in the array is deleted, the values of the Variables originally representing the second and third entry of the array do not change
• OPC-10000-3 – OPC Unified Architecture - Part 3: Address Space Model
  7.24 UsesDataTypeRefinement
  used as InstanceDeclaration . Note that Method Arguments can be further described using Variables referenced with a HasArgumentDescription . If the Method Argument is a Structured DataType , this Variable can be used
• OPC-10000-3 – OPC Unified Architecture - Part 3: Address Space Model
  7.25 HasFieldDescription
  only be further restricted. It is not allowed to reference two Variables with the same BrowseName using the HasFieldDescription ReferenceType or a subtype from the same SourceNode
• OPC-10000-3 – OPC Unified Architecture - Part 3: Address Space Model
  7.28 UsesSubtypeRestriction
  used as InstanceDeclaration . Note, that Method Arguments can be further described using Variables referenced with a HasArgumentDescription . This Variable can be used as SourceNode for the UsesSubtypeRestriction to further restrict
• OPC-10000-3 – OPC Unified Architecture - Part 3: Address Space Model
  7.29 AllowedSubtype
  defined in the same Namespace . It is not allowed to reference two Variables with the same BrowseName using the AllowedSubtype ReferenceType or a subtype from the same SourceNode
• OPC-10000-3 – OPC Unified Architecture - Part 3: Address Space Model
  8.38 XmlElement
  Schema to define a DataTypeEncoding ). For this reason a Server should never define Variables that use the XmlElement DataType unless the Server has no information about the XML elements that
• OPC-10000-3 – OPC Unified Architecture - Part 3: Address Space Model
  8.55 PermissionType
  affects the value of the UserWriteMask Attribute . This Permission is only valid for Variables . Read 5 The Client is allowed to read the Value Attribute . This bit affects the CurrentRead ... UserAccessLevel Attribute . This Permission is only valid for Variables . Write 6 The Client is allowed to write the Value Attribute . This bit affects the CurrentWrite bit of the UserAccessLevel Attribute
• OPC-10000-3 – OPC Unified Architecture - Part 3: Address Space Model
  8.58 AccessLevelExType
  NoSubDataTypes Field represents the ability of a Variable to accept derived DataTypes . In general Variables are expected to allow the defined DataType or any subtype of that DataType . This Field
• OPC-10000-3 – OPC Unified Architecture - Part 3: Address Space Model
  8.60 AttributeWriteMask
  Value Attribute is writeable for a VariableType . It does not apply for Variables since this is handled by the AccessLevel and UserAccessLevel Attributes for the Variable . For Variables this
• OPC-10000-3 – OPC Unified Architecture - Part 3: Address Space Model
  A.3 ObjectTypes
  From a more abstract point of view Objects are used to group Variables and other Objects in the AddressSpace . Therefore ObjectTypes should be used when some common structures/groups of Objects ... and/or Variables should be described. Clients can use this knowledge to program against the ObjectType structure and use the TranslateBrowsePathsToNodeIds Service defined in OPC 10000-4 on the instances. Simple
• OPC-10000-3 – OPC Unified Architecture - Part 3: Address Space Model
  A.4.1 General
  VariableTypes are only used for DataVariables and should be used when there are several Variables having the same semantic (e.g. set point). It is not necessary to define a VariableType
• OPC-10000-3 – OPC Unified Architecture - Part 3: Address Space Model
  A.4.3 Many Variables and / or Structured DataTypes
  A.4.3 Many Variables and / or Structured DataTypes When structured data structures should be made available to the Client there are basically three different approaches: Create several simple Variables using simple ... DataTypes always reflecting parts of the simple structure. Objects are used to group the Variables according to the structure of the data. Create a Structured DataType and a simple Variable
• OPC-10000-3 – OPC Unified Architecture - Part 3: Address Space Model
  A.6 Methods
  some input is expected and the Server delivers a result. One should avoid using Variables to write the input values and other Variables to get the output results
• OPC-10000-3 – OPC Unified Architecture - Part 3: Address Space Model
  B.3.6 Variable and VariableType
  shall not be the SourceNode of a HasProperty or any other HierarchicalReferences Reference. All Variables having "A" as the SourceNode of a HasProperty Reference shall have a unique
• OPC-10000-4 – OPC Unified Architecture - Part 4: Services
  3.1.2 Deadband
  Note 1 to entry:  Deadband can be applied as a filter when subscribing to Variables and is used to keep noisy signals from updating the Client unnecessarily. This document defines
• OPC-10000-4 – OPC Unified Architecture - Part 4: Services
  4.1 Service Set model
  Attribute , these Services allow Clients to read and write the values of Variables . Figure 6 - Attribute Service Set The Method Service Set is illustrated in Figure 7 . It defines Services
• OPC-10000-4 – OPC Unified Architecture - Part 4: Services
  5.13.1.1 Overview
  Attributes causes a Notification to be generated. The Value Attribute is used when monitoring Variables . Variable values are monitored for a change in value or a change in their status
• OPC-10000-4 – OPC Unified Architecture - Part 4: Services
  5.14.1.2 State table
  letter. Internal Events may be accompanied by conditions that test state Variable values. State Variables are defined in 5.14.1.3 . They begin with an upper case letter. Service request and internal
• OPC-10000-4 – OPC Unified Architecture - Part 4: Services
  B.3.2 Used type model
  this Figure, the OPC UA notation is used for all References to ObjectTypes , Variables , Properties and subtypes. Additionally, supported References are contained in an inner box. The actual references only
• OPC-10000-5 – OPC Unified Architecture - Part 5: Information Model
  3.3 Conventions for Node descriptions
  defined in the same row of the table. The DataType is only specified for Variables ; "[<number>]" indicates a single-dimensional array, for multi-dimensional arrays ... single-dimensional array or a scalar. The TypeDefinition is specified for Objects and Variables . The TypeDefinition column specifies a symbolic name for a NodeId , i.e., the specified Node points with
• 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 ... Optionally, a server-specific minimum sampling interval is provided. AccessLevel The access level for Variables used for type definitions is server-specific, for all other Variables defined in this standard
• OPC-10000-5 – OPC Unified Architecture - Part 5: Information Model
  6.3.3 ServerDiagnosticsType
  sampling intervals. In these cases, length of the array and the set of contained Variables will be determined by the Server configuration and the NodeId assigned to a given sampling ... providing a Variable for each entry in the array as defined in 7.11 . Those Variables are also used as Variables referenced by other Variables . SessionsDiagnosticsSummary contains diagnostic information per session
• OPC-10000-5 – OPC Unified Architecture - Part 5: Information Model
  6.3.13 NamespaceMetadataType
  AccessLevelEx Attribute, defined in OPC 10000-3 , to optimize the use of Variables which have a constant value. The optional ModelVersion Property indicates the InformationModel version expressed as a SemanticVersionString
• OPC-10000-5 – OPC Unified Architecture - Part 5: Information Model
  7.6 ServerStatusType
  SecondsTillShutdown UInt32 BaseDataVariableType Mandatory HasComponent Variable ShutdownReason LocalizedText BaseDataVariableType Mandatory NOTE Containing Objects and Variables of these Objects and Variables are defined by their BrowseName defined in the corresponding TypeDefinitionNode
• OPC-10000-5 – OPC Unified Architecture - Part 5: Information Model
  7.13 SessionDiagnosticsArrayType
  will provide a Variable of the SessionDiagnosticsVariableType VariableType , having the SessionDiagnostics as BrowseName . Those Variables will also be referenced by the SessionDiagnostics Objects defined by their type
• OPC-10000-5 – OPC Unified Architecture - Part 5: Information Model
  7.15 SessionSecurityDiagnosticsArrayType
  will provide a Variable of the SessionSecurityDiagnosticsType VariableType , having the SessionSecurityDiagnostics as BrowseName . Those Variables will also be referenced by the SessionDiagnostics Objects defined by their type
• OPC-10000-5 – OPC Unified Architecture - Part 5: Information Model
  7.21 VectorType
  DataType , defined in 12.23 . Subtypes shall expose the structure of their structured DataTypes as Variables . Additionally, it can define a unit for each dimension of the vector ( Property VectorUnit
• OPC-10000-5 – OPC Unified Architecture - Part 5: Information Model
  7.23 CartesianCoordinatesType
  DataType , defined in 12.25 . Subtypes shall expose the structure of their structured DataTypes as Variables . Additionally, it can define a unit for the coordinates ( Property LengthUnit ). The VariableType is formally
• OPC-10000-5 – OPC Unified Architecture - Part 5: Information Model
  7.25 OrientationType
  DataType , defined in 12.27 . Subtypes shall expose the structure of their structured DataTypes as Variables . Additionally, it can define a unit for the orientation angles ( Property AngleUnit ). The VariableType
• OPC-10000-5 – OPC Unified Architecture - Part 5: Information Model
  8.1 General
  General Objects and Variables described in the following subclauses can be extended by additional Properties or References to other Nodes , except where it is stated in the text that
• OPC-10000-5 – OPC Unified Architecture - Part 5: Information Model
  8.2.4 Objects
  used as entry point into a subset of the AddressSpace containing Objects and Variables and thus the " Objects " Object can also reference View Nodes using Organizes References ... intent of the " Objects " Object is that all Objects and Variables that are not used for type definitions or other organizational purposes (e.g. organizing the Views ) are accessible
• OPC-10000-5 – OPC Unified Architecture - Part 5: Information Model
  8.3.1 General
  General The Server Object and its containing Objects and Variables are built in a way that the information can be gained in several ways, suitable for different kinds of clients ... different approaches. Figure 10 gives an overview of the containing Objects and Variables of the diagnostic information of the Server Object and where the information can be found. The SessionsDiagnosticsSummary
• OPC-10000-5 – OPC Unified Architecture - Part 5: Information Model
  12.16 ModelChangeStructureDataType
  TargetNode . DataTypeChanged 4 This verb may be used only for affected Nodes that are Variables or VariableTypes . It indicates that the DataType Attribute has changed. Reserved 5:7 Reserved
• OPC-10000-5 – OPC Unified Architecture - Part 5: Information Model
  A.2 ServerType and Server Object
  Server Object . The Server Object is an Object , because it groups a set of Variables and Objects containing information about the Server . The ServerType is a complex ObjectType , because ... Object should be well-defined. However, the Server Object can be extended by adding Variables and Objects in an appropriate structure of the Server Object or its containing Objects
• OPC-10000-5 – OPC Unified Architecture - Part 5: Information Model
  A.7 Redundant information
  information of the individual entries. Thus, the information provided is redundant, but the Variables containing the arrays do not expose their individual entries
• OPC-10000-5 – OPC Unified Architecture - Part 5: Information Model
  A.10 Extensibility mechanism
  other scenarios this may be a useful way to add information. Add Objects containing Variables or add Variables to the Objects defined in this part. If, for example, additional diagnostic
• OPC-10000-6 – OPC Unified Architecture - Part 6: Mappings
  F.15 Example
  NodeId value in the document except for NodeIds that appear in Values of Variables or VariableTypes . <Aliases> <Alias Alias="HasComponent">i=47</Alias
• OPC-10000-8 – OPC Unified Architecture - Part 8: Data Access
  5.3.3.4 MultiStateValueDiscreteType
  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 ... numeric representation. Only DataTypes that can be represented with EnumValues are allowed for Variables of MultiStateValueDiscreteType . These are Integers up to 64 Bits (signed and unsigned). Clients should be prepared
• OPC-10000-8 – OPC Unified Architecture - Part 8: Data Access
  5.3.4.4 ImageItemType
  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 ([0]) to define
• OPC-10000-8 – OPC Unified Architecture - Part 8: Data Access
  5.3.4.5 CubeItemType
  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 ([0]) to define
• OPC-10000-8 – OPC Unified Architecture - Part 8: Data Access
  5.6.7 AxisInformation
  AxisInformation This structure defines the information for auxiliary axis for ArrayItemType Variables . There are three typical uses of this structure: The step between points is constant and can be predicted
• OPC-10000-8 – OPC Unified Architecture - Part 8: Data Access
  A.3.1.3 Item
  A.3.1.3 Item DA items (leafs) are represented in the COM UA Wrapper as Variables . The VariableType depends on the existance of special DA properties as follows: AnalogItemType : An item
• OPC-10000-9 – OPC Unified Architecture - Part 9: Alarms & Conditions
  4.6 Severity, quality, and comment
  this Condition is based. Since a Condition is usually based on one or more Variables , the Condition inherits the quality of these Variables . E.g., if the process value
• OPC-10000-9 – OPC Unified Architecture - Part 9: Alarms & Conditions
  5.4.6 AlarmSuppressionGroupMember ReferenceType
  AlarmGroupMember ReferenceType . This ReferenceType is used to indicate the Alarm instances or Boolean Variables that are part of an Alarm Group . The representation in the AddressSpace is specified in Table
• OPC-10000-9 – OPC Unified Architecture - Part 9: Alarms & Conditions
  5.5.2 ConditionType
  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; EventId , Event Type ... SourceName , Time, and EnabledState . Other Properties may no longer provide current valid values. All Variables that are no longer provided shall return a status of Bad _ ConditionDisabled . The Event that
• OPC-10000-9 – OPC Unified Architecture - Part 9: Alarms & Conditions
  5.5.7 ConditionRefresh Method
  Server specific, in that some Servers could replay the exact Events with all Properties / Variables maintaining the same values as originally sent, but other Servers would only regenerate the Event
• OPC-10000-9 – OPC Unified Architecture - Part 9: Alarms & Conditions
  5.5.8 ConditionRefresh2 Method
  Server specific, in that some Servers could replay the exact Events with all Properties / Variables maintaining the same values as originally sent, but other Servers would only regenerate the Event
• OPC-10000-9 – OPC Unified Architecture - Part 9: Alarms & Conditions
  5.8.2 AlarmConditionType
  shall be provided. In some systems, an Alarm may be calculated based on multiple Variables Values ; it is up to the system to determine which Variable's NodeId is used
• OPC-10000-9 – OPC Unified Architecture - Part 9: Alarms & Conditions
  5.8.4 AlarmSuppressionGroupType
  other alarms. This subtype of AlarmGroup extends the AlarmGroupType to allow the addition of Variables that have a Boolean DataType . The Variable can be thought of as representing ... ActiveState of an Alarm , i.e. when any of the included Variables have a value of true the AlarmSuppressionGroup is active. Table 43 - AlarmSuppressionGroupType definition Attribute Value BrowseName AlarmSuppressionGroupType IsAbstract False
• OPC-10000-9 – OPC Unified Architecture - Part 9: Alarms & Conditions
  5.8.17.1 Overview
  ToState True TimedShelved HasEffect True AlarmConditionType HasCause True TimedShelve HasCause True TimedShelve2 The component Variables of the ShelvedStateMachineType have additional Attributes defined in Table 75 . Table 75 - ShelvedStateMachineType Attribute values
• OPC-10000-9 – OPC Unified Architecture - Part 9: Alarms & Conditions
  5.8.19.2 ExclusiveLimitStateMachineType
  True AlarmConditionType LowToLowLow FromState True Low ToState True LowLow HasEffect True AlarmConditionType The component Variables of the ExclusiveLimitStateMachineType have additional Attributes defined in Table 95 . Table 95 - ExclusiveLimitStateMachineType Attribute values
• OPC-10000-9 – OPC Unified Architecture - Part 9: Alarms & Conditions
  6.5 Conditions in a VariableType
  VariableType Use of HasCondition in a VariableType is a special use case since Variables (and VariableTypes ) are not allowed to be the source of a HasComponent Reference to an Object
• OPC-10000-9 – OPC Unified Architecture - Part 9: Alarms & Conditions
  B.1.1 Overview
  Event flow for typical Alarm situations. The tables list the value of state Variables for each Event Notification
• OPC-10000-9 – OPC Unified Architecture - Part 9: Alarms & Conditions
  B.1.2 Server maintains current state only
  also the acknowledgement and confirmation cycles. Table B.1 lists the values of the state Variables . All Events are coming from the same Condition instance and therefore have the same ConditionId
• OPC-10000-9 – OPC Unified Architecture - Part 9: Alarms & Conditions
  B.1.3 Server maintains previous states
  transition into an inactive state. Table B.2 lists the values of the state Variables . All Events are coming from the same Condition instance and have therefore the same ConditionId . Figure
• OPC-10000-9 – OPC Unified Architecture - Part 9: Alarms & Conditions
  B.1.4 Server current-State Model with Suppression
  service and then inactive. Table B.3 lists the values of the state Variables . All Events are coming from the same Condition instance and therefore have the same ConditionId . The Client
• OPC-10000-9 – OPC Unified Architecture - Part 9: Alarms & Conditions
  D.2.4 Event attributes
  Server are represented in the UA Server as Variables which are targets of HasProperty Reference s from the ObjectTypes which represent the Event Categories. The BrowseName and DisplayName
• OPC-10000-9 – OPC Unified Architecture - Part 9: Alarms & Conditions
  F.2 SystemStateStateMachineType
  True Maintain OutOfServiceToMaintenance FromState True OutOfService ToState True Maintenance HasCause True Maintain The component Variables of the SystemStateStateMachineType have additional Attributes defined in Table F . 3 . Table F. 3 - SystemStateStateMachineType
• OPC-10000-10 – OPC Unified Architecture - Part 10: Programs
  5.2.1 Overview
  Method Resume OP HasComponent Object FinalResultData BaseObjectType O Conformance Units Program Basic The component Variables of the ProgramStateMachineType have additional Attributes defined in Table 6 . Table 6 - ProgramStateMachineType Attribute values
• OPC-10000-10 – OPC Unified Architecture - Part 10: Programs
  5.2.5.2 ProgramTransitionEventType
  after the Program transition. The IntermediateResult is an Object that aggregates a set of Variables whose values are relevant for the Program at the instant of the associated transition ... ObjectType for the IntermediateResult specifies the collection of Variables using a set of HasComponent References
• OPC-10000-10 – OPC Unified Architecture - Part 10: Programs
  5.2.9 ProgramDiagnostic2Type VariableType
  ProgramDiagnostic2Type VariableType This VariableType aggregates simple Variables using simple DataTypes that reflect the elements of the ProgramDiagnosticDataType structure. Its DataVariables have the same semantic as defined in in 5.2.8 . Note
• OPC-10000-10 – OPC Unified Architecture - Part 10: Programs
  A.2.6.2 DomainDownloadType
  destination. The Closing state is the cleanup phase of the download. The component Variables of the TransferStateMachineType have additional Attributes defined in Table A.4. Table A.4 - TransferStateMachineType Attribute values ... Completed state is the terminal state that indicates a successful domain download. The component Variables of the FinishStateMachineType have additional Attributes defined in Table A.6. Table A.6 - FinishStateMachineType Attribute values
• OPC-10000-11 – OPC Unified Architecture - Part 11: Historical Access
  4.2 Data architecture
  will provide historical data and Events for all or a subset of the available Variables , Objects, Properties or Views within the Server AddressSpace . Figure 1 illustrates how the AddressSpace
• 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.5.1 General
  HasCurrentEvent Reference to indicate the source node for the data or Event . Mirroring Variables is typically simple. Variables usually do not have complex structure or nested Variables under them
• OPC-10000-11 – OPC Unified Architecture - Part 11: Historical Access
  5.6.2 HistoricalDataNodes Address Space Model
  only shows a subset of Attributes and Properties . Other Attributes that are defined for Variables in OPC 10000-3 , can also be available
• OPC-10000-11 – OPC Unified Architecture - Part 11: Historical Access
  6.5.1 Overview
  values from the history database by specifying a time domain for one or more Variables . See 6.5.3.1 . When this parameter is specified, the Server returns a HistoryData structure for each ... ModifiedValues from the history database by specifying a time domain for one or more Variables. See 6.5.3.1 . When this parameter is specified, the Server returns a HistoryModifiedData structure for each
• OPC-10000-12 – OPC Unified Architecture - Part 12: Discovery and Global Services
  7.10.17 TransactionDiagnosticsType
  last transaction (see 7.10.1 . If no transaction has started the values of all Variables have a status of Bad_OutOfService. All existing results are discarded when a new transaction starts
• OPC-10000-13 – OPC Unified Architecture - Part 13: Aggregates
  4.2.1.2 AggregateConfigurationType
  calculate the value of the aggregate. Refer to 5.4.3 for details on using these Variables when assigning StatusCodes . The PercentDataGood and PercentDataBad shall follow the following relationship PercentDataGood ≥ (100 - PercentDataBad
• OPC-10000-14 – OPC Unified Architecture - Part 14: PubSub
  3.1.8 PublishedDataSet
  Action completes. Note 1 to entry: A PublishedDataSet can be a list of monitored Variables or an Event selection
• OPC-10000-14 – OPC Unified Architecture - Part 14: PubSub
  3.1.10 SubscribedDataSet
  Note 1 to entry: A SubscribedDataSet can be a mapping of DataSet fields to Variables in the Subscriber AddressSpace
• OPC-10000-14 – OPC Unified Architecture - Part 14: PubSub
  5.2.1 General
  fields can be defined to represent any information, for example, they could be internal Variables in the Publisher , Events from the Publisher or collected by the Publisher , network data ... Event fields. Similar to data MonitoredItems , the PublishedDataSet can contain a list of Variables . A DataSet does not define the mechanism to encode, secure and transport it. A DataSetWriter handles
• OPC-10000-14 – OPC Unified Architecture - Part 14: PubSub
  5.4.1.2 Message sending
  DataSetMetaData . Collection is a generic expression for various different options, like monitoring of Variables in an OPC UA Server AddressSpace , processing OPC UA Events , or for example reading data from
• OPC-10000-14 – OPC Unified Architecture - Part 14: PubSub
  5.4.2.2 Message reception
  SubscribedDataSetMirror . The configuration of TargetVariables allows the dispatching of DataSetMessage fields to existing Variables in the Subscribers OPC UA AddressSpace . The configuration of SubscribedDataSetMirror is used if the received DataSet ... fields should be represented as Variables in the Subscribers OPC UA AddressSpace but the Variables do not exist and must be created as part of the Subscriber configuration
• OPC-10000-14 – OPC Unified Architecture - Part 14: PubSub
  5.4.4 Configuration Tool
  where both communication partners have a pre-configured list of input and output data Variables and a generic configuration tool establishes the communication by selecting the Variables to be published ... Subscriber to receive the messages from the Publisher and to select the target Variables in the Subscriber
• OPC-10000-14 – OPC Unified Architecture - Part 14: PubSub
  5.4.6.2.2 Broker-less model with OPC UA UDP
  Application that maps data fields from UADP DataSetMessages to internal Variables can be configured through the DataSetReader Object and dispatcher in the Subscriber . The configuration of a DataSetReader defines
• OPC-10000-14 – OPC Unified Architecture - Part 14: PubSub
  5.4.6.3.2 Broker-based model
  protocol. A DataSet can be collected from a list of Event fields and/or selected Variables . Such a configuration is called PublishedDataSet . Each DataSet is sent as a separate DataSetMessage serialized
• OPC-10000-14 – OPC Unified Architecture - Part 14: PubSub
  6.2.3.2.2 DataTypeSchemaHeader
  Server information model e.g. if the values are written to target Variables . This affects encoding NodeIds in ExtensionObjects but also all other namespace indices in NodeIds and BrowseNames contained ... messages. If the Subscriber receives Structure DataTypes where the target Variables DataTypes have the same structure but different DataType NodeIds , the Subscriber must verify the consistency of the layout
• OPC-10000-14 – OPC Unified Architecture - Part 14: PubSub
  6.2.4.3 KeyFrameCount
  times the PublishingInterval expires before a key frame message with values for all published Variables is sent. The delta frame DataSetMessages contains just the changed values. If no changes exist
• OPC-10000-14 – OPC Unified Architecture - Part 14: PubSub
  6.2.9.4 DataSetMetaData
  Server information model e.g. if the values are written to target Variables . This affects encoding NodeIds in ExtensionObjects but also all other namespace indices in NodeIds and BrowseNames contained ... messages. If the Subscriber receives Structure DataTypes where the target Variables DataTypes have the same structure but different DataType NodeIds , the Subscriber must verify the consistency of the layout
• OPC-10000-14 – OPC Unified Architecture - Part 14: PubSub
  6.2.10.2.1 General
  option TargetVariables defines a list of Variable mappings between received DataSet fields and target Variables in the Subscriber AddressSpace . The FieldTargetDataType is defined in 6.2.10.2.3 . Target Variables shall only
• OPC-10000-14 – OPC Unified Architecture - Part 14: PubSub
  6.2.10.3.2 ParentNodeName
  with DataType String defines the BrowseName and DisplayName of the parent Node for the Variables representing the fields of the subscribed DataSet
• OPC-10000-14 – OPC Unified Architecture - Part 14: PubSub
  6.2.10.3.3 RolePermissions
  parent Node. This value is also used as RolePermissions for all Variables of the DataSet mirror
• OPC-10000-14 – OPC Unified Architecture - Part 14: PubSub
  6.2.11.1 Published data items
  type if there was never a value received before. If one of the target Variables in the SubscribedDataSet does not allow writing of the StatusCode and the OverrideValueHandling
• OPC-10000-14 – OPC Unified Architecture - Part 14: PubSub
  7.3.4.7.2 MessageType mapping
  Table 205 - MQTT Topic level access permissions MqttMessageType Publisher Subscriber Description data Write Read Variables and Events from an OPC UA applications acting as Publisher have RolePermissions . Such RolePermissions have
• OPC-10000-14 – OPC Unified Architecture - Part 14: PubSub
  9.1.1 General
  Publisher . Figure 44 - PubSub information flow The PublishedDataSetType represents the selection and configuration of Variables or Events . An Event notification or a snapshot of the Variables comprises a DataSet
• OPC-10000-14 – OPC Unified Architecture - Part 14: PubSub
  9.1.3.2 PublishSubscribeType
  include standardized DataSetClasses into their namespace. The DataSetClasses Folder references a list of Variables where the Value of a Variable represents a DataSetClass . For each Variable , the Name field
• OPC-10000-14 – OPC Unified Architecture - Part 14: PubSub
  9.1.4.1 Overview
  source of information for a DataSet in the OPC UA Server AddressSpace like Variables or Events
• OPC-10000-14 – OPC Unified Architecture - Part 14: PubSub
  9.1.4.2.1 PublishedDataSetType
  collect the DataSet to be published. For PublishedDataItemsType this is a list of monitored Variables used to create cyclic DataSets . For PublishedEventsType this is an Event selection used to create ... acyclic DataSets . The list of monitored Variables or the list of selected EventFields defines the content and metadata of the PublishedDataSetType Object . If the content of the DataSet is defined
• OPC-10000-14 – OPC Unified Architecture - Part 14: PubSub
  9.1.4.3.1 PublishedDataItemsType
  PublishedDataItemsType The PublishedDataItemsType is used to select a list of OPC UA Variables as the source for the creation of DataSets sent through one or more DataSetWriters . The PublishedDataItemsType
• OPC-10000-14 – OPC Unified Architecture - Part 14: PubSub
  9.1.4.3.2 AddVariables Method
  AddVariables Method This Method is used to add Variables to the PublishedData Property . The PublishedData contains a list of published Variables of a PublishedDataItemsType Object . The information provided ... input Arguments and information available for the added Variables is also used to create the content of the DataSetMetaData Property . The mapping to the DataSetMetaData is described for the input
• OPC-10000-14 – OPC Unified Architecture - Part 14: PubSub
  9.1.4.3.3 RemoveVariables Method
  RemoveVariables Method This Method is used to remove Variables from the PublishedData list. It contains the list of published Variables of a PublishedDataItemsType Object . A caller shall read the current ... calling this Method , to ensure the use of the correct index of the Variables that are being removed. If at least one Variable was successfully removed from the PublishedData
• OPC-10000-14 – OPC Unified Architecture - Part 14: PubSub
  9.1.4.5.2 AddPublishedDataItems Method
  PublishedDataItemsType . The DataSetMetaData of the PublishedDataSetType is created from meta-data of the Variables referenced in VariablesToAdd and the settings in FieldNameAliases and FieldFlags . The Client shall be authorized ... Name Name of the Object to create. FieldNameAliases The names assigned to the selected Variables for the fields in the DataSetMetaData and in the DataSetMessages for tagged message encoding
• OPC-10000-14 – OPC Unified Architecture - Part 14: PubSub
  9.1.8.5 CreateTargetVariables Method
  initially set the SubscribedDataSet to TargetVariablesType and to create the list of target Variables of a SubscribedDataSetType . The Client shall be authorized to modify the configuration for the PubSub functionality ... shall be returned. The ConfigurationVersionDataType is defined in 6.2.3.2.6 . TargetVariablesToAdd The list of target Variables to write received DataSet fields to. The FieldTargetDataType is defined in 6.2.10.2.3 . The succeeded targets
• OPC-10000-14 – OPC Unified Architecture - Part 14: PubSub
  9.1.8.6 CreateDataSetMirror Method
  SubscribedDataSet to SubscribedDataSetMirrorType used to represents the fields of the DataSet as Variables in the Subscriber Address Space . This Method creates an Object below the SubscribedDataSet and below this Object ... ParentNodeName This parameter defines the BrowseName and DisplayName of the parent Node for the Variables representing the fields of the subscribed DataSet . RolePermissions Value of the RolePermissions Attribute
• OPC-10000-14 – OPC Unified Architecture - Part 14: PubSub
  9.1.9.2.2 AddTargetVariables Method
  AddTargetVariables Method This Method is used to add target Variables to an existing list of target Variables of a TargetVariablesType Object . The Client shall be authorized to modify the configuration ... shall be returned. The ConfigurationVersionDataType is defined in 6.2.3.2.6 . TargetVariablesToAdd The list of target Variables to write received DataSet fields to. The FieldTargetDataType is defined in 6.2.10.2.3 . The succeeded connections
• OPC-10000-14 – OPC Unified Architecture - Part 14: PubSub
  9.1.9.2.3 RemoveTargetVariables Method
  RemoveTargetVariables Method This Method is used to remove entries from the list of target Variables of a TargetVariablesType Object . The Client shall be authorized to modify the configuration ... TargetsToRemove Array of indices of connections to remove from the list of target Variables. RemoveResults The result codes for the connections to remove. Method Result Codes ResultCode Description Bad_NothingToDo
• OPC-10000-14 – OPC Unified Architecture - Part 14: PubSub
  9.1.9.3 SubscribedDataSetMirrorType
  SubscribedDataSetMirrorType This ObjectType defines the information for the processing of DataSetMessages as mirror Variables. For each field of the DataSet a mirror Variable is created in the Subscriber AddressSpace ... used to set the SubscribedDataSet into the mirror mode. The mirror Object shall reference Variables for each DataSet field in the DataSetMetaData with HasComponent . The name, DataType , ValueRank and ArrayDimensions
• OPC-10000-14 – OPC Unified Architecture - Part 14: PubSub
  9.1.11.2 PubSubDiagnosticsType
  diagnostics Object . The counters use the VariableType PubSubDiagnosticsCounterType defined in 9.1.11.5 . The counter Variables of the PubSubDiagnosticsType are defined in Table 311 . Table 311 - Counters for PubSubDiagnosticsType BrowseName Modelling Rule ... live values of the diagnostics Object . If not further specified, the live values Variables use the VariableType BaseDataVariableType . The nodes in the Objects Counters and LiveValues may be activated/deactivated
• OPC-10000-14 – OPC Unified Architecture - Part 14: PubSub
  9.1.11.7 PubSubDiagnosticsRootType
  live values of the diagnostics Object . If not further specified, the live values Variables use the VariableType BaseDataVariableType . The live values Variables of the PubSubDiagnosticsRootType are defined in Table
• OPC-10000-14 – OPC Unified Architecture - Part 14: PubSub
  9.1.11.8 PubSubDiagnosticsConnectionType
  live values of the diagnostics Object . If not further specified, the live values Variables use the VariableType BaseDataVariableType . The live values Variables of the PubSubDiagnosticsConnectionType are defined in Table
• OPC-10000-14 – OPC Unified Architecture - Part 14: PubSub
  9.1.11.9 PubSubDiagnosticsWriterGroupType
  diagnostics Object . The counters use the VariableType PubSubDiagnosticsCounterType defined in 9.1.11.5 . The counter Variables of the PubSubDiagnosticsWriterGroupType are defined in Table 321 . Table 321 - Counters for PubSubDiagnosticsWriterGroupType BrowseName Modelling Rule ... live values of the diagnostics Object . If not further specified, the live values Variables use the VariableType BaseDataVariableType . The live values Variables of the PubSubDiagnosticsWriterGroupType are defined in Table
• OPC-10000-14 – OPC Unified Architecture - Part 14: PubSub
  9.1.11.10 PubSubDiagnosticsReaderGroupType
  diagnostics Object . The counters use the VariableType PubSubDiagnosticsCounterType defined in 9.1.11.5 . The counter Variables of the PubSubDiagnosticsReaderGroupType are defined in Table 324 . Table 324 - Counters for PubSubDiagnosticsReaderGroupType BrowseName Modelling Rule ... live values of the diagnostics Object . If not further specified, the live values Variables use the VariableType BaseDataVariableType . The live values Variables of the PubSubDiagnosticsReaderGroupType are defined in Table
• OPC-10000-14 – OPC Unified Architecture - Part 14: PubSub
  9.1.11.11 PubSubDiagnosticsDataSetWriterType
  diagnostics Object . The counters use the VariableType PubSubDiagnosticsCounterType defined in 9.1.11.5 . The counter Variables of the PubSubDiagnosticsDataSetWriterType are defined in Table 327 . Table 327 - Counters for PubSubDiagnosticsDataSetWriterType BrowseName Modelling Rule ... live values of the diagnostics Object . If not further specified, the live values Variables use the VariableType BaseDataVariableType . The live values Variables of the PubSubDiagnosticsDataSetWriterType are defined in Table
• OPC-10000-14 – OPC Unified Architecture - Part 14: PubSub
  9.1.11.12 PubSubDiagnosticsDataSetReaderType
  diagnostics Object . The counters use the VariableType PubSubDiagnosticsCounterType defined in 9.1.11.5 . The counter Variables of the PubSubDiagnosticsDataSetReaderType are defined in Table 330 . Table 330 - Counters for PubSubDiagnosticsDataSetReaderType BrowseName Modelling Rule ... live values of the diagnostics Object . If not further specified, the live values Variables use the VariableType BaseDataVariableType . The live values Variables of the PubSubDiagnosticsDataSetReaderType are defined in Table
• OPC-10000-14 – OPC Unified Architecture - Part 14: PubSub
  9.1.12.2 Supported configuration properties
  configuration parameters defined for the different PubSub components. A configuration property is described by Variables with the following information: BrowseName of the Variable is used as Key for the property
• OPC-10000-15 – OPC Unified Architecture - Part 15: Safety
  6.3.2 OPC UA Platform interface (OPC UA PI)
  Client/Server and remote Method invocation or the publishing of and subscribing to remote Variables as defined in OPC 10000-14. The requirements on the implementation of the mapper are implicitly
• OPC-10000-15 – OPC Unified Architecture - Part 15: Safety
  7.2.1.5 ResponseSPDU: SafetyData
  SafetyConsumer . It is comprised of a single or multiple basic OPC UA Variables (see 6.2.5 ). For the sake of reducing distinctions of cases, SafetyData shall always be a Structure , even
• OPC-10000-16 – OPC Unified Architecture - Part 16: State Machines
  4.4.3 StateVariableType
  StateVariableType The StateVariableType is the base VariableType for Variables that store the current state of a StateMachine as a human readable name. The StateVariableType is formally defined in Table
• OPC-10000-16 – OPC Unified Architecture - Part 16: State Machines
  4.4.5 TransitionVariableType
  TransitionVariableType The TransitionVariableType is the base VariableType for Variables that store a Transition that occurred within a StateMachine as a human readable name. The SourceTimestamp for the value specifies when
• OPC-10000-16 – OPC Unified Architecture - Part 16: State Machines
  4.5.2 StateMachineType with a SubStateMachine using inheritance
  this Variable . An Object of "MyStateMachineType", called "MyStateMachine" has Variables for the current State , but also has an Object "MySubMachine" and a Variable representing
• OPC-10000-16 – OPC Unified Architecture - Part 16: State Machines
  4.6.5 ExpressionGuardVariableType
  basic operators (see OPC 10000-4 for details). The ContentFilter can reference any Variables defined on the StateMachineType and are validated on the instance of the StateMachine . If the definition
• OPC-10000-17 – OPC Unified Architecture - Part 17: Alias Names
  6.2 AliasNameType ObjectType Definition
  defined in OPC 10000-5 ConformanceUnits AliasName Base This ObjectType has no Properties or Variables . The BrowseName of the Object is used as the alias name. The string part
• OPC-10000-17 – OPC Unified Architecture - Part 17: Alias Names
  A.2 AliasNames used within a single Server
  model for a well. This model contains a number of other Objects , which have Variables that are to be available via a standardized naming scheme. The model also includes ... configuration for a PubSub DataSet (see OPC 10000-14 ) that provides the Variables defined in the well. The AliasName model includes the standard organization items that are required in this
• OPC-10000-20 – OPC Unified Architecture - Part 20: File Transfer
  4.4.6 FileTransferStateMachineType
  Method Reset Defined in 4.4.7 Mandatory Conformance Units Base Info TemporaryFileTransferType Base The component Variables of the FileTransferStateMachineType have additional Attributes defined in Table 18 . Table 18 - FileTransferStateMachineType Attribute values
• OPC-10000-22 – OPC Unified Architecture - Part 22: Base Network Model
  4.1 Type and Naming Conventions
  types used by the related managed objects of IEEE and IETF. BrowseNames of Variables and parameter sets (UA interface) are preferably derived from standardized IETF / IEEE YANG models
• OPC-10000-22 – OPC Unified Architecture - Part 22: Base Network Model
  5.2.1 IIetfBaseNetworkInterfaceType Interface
  nominal bandwidth (ifSpeed and ifHighSpeed are defined in IETF RFC 2863 ). The component Variables of the IIetfBaseNetworkInterfaceType have the Attribute values defined in Table 2 . Table 2 - IIetfBaseNetworkInterfaceType Attribute values
• OPC-10000-22 – OPC Unified Architecture - Part 22: Base Network Model
  5.2.2 IIeeeBaseEthernetPortType Interface
  long (aMaxFrameLength is defined in 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
• OPC-10000-22 – OPC Unified Architecture - Part 22: Base Network Model
  5.2.7 IIeeeBaseTsnStreamType Interface
  IIeeeBaseTsnStreamType Interface The IIeeeBaseTsnStreamType contains Variables which are common for both TSN talkers and TSN listeners. They represent the configuration properties and diagnostic values like reservation status and failure codes
• OPC-10000-23 – OPC Unified Architecture - Part 23: Common ReferenceTypes
  5.1 Overview
  using the ReferenceType SomeReferenceType. Both References are described by a ReferenceDescription , that is, the Variables SomeReferenceType1 and SomeReferenceType2. The Values of those Variables uniquely identify the References by providing SourceNode ... BrowseName and therefore should use for the ReferenceType and/or VariableType to receive ReferenceDescription Variables , not the BrowseName . For each unique Reference ( SourceNode , ReferenceType , IsForward , TargetNode ) there shall be at most
• OPC-10000-23 – OPC Unified Architecture - Part 23: Common ReferenceTypes
  5.2 Reference Refinement
  first level, via the Switch. The "ConnectedTo1" and "ConnectedTo2" Variables further refine the References used in the first refinement level. Both contain multiple hops
• OPC-10000-24 – OPC Unified Architecture - Part 24: Scheduler
  1 Scope
  times and actions that should be executed at that time. The model defines writing Variables and calling Methods , but can be extended to other actions as well
• OPC-10000-24 – OPC Unified Architecture - Part 24: Scheduler
  4 General information to Scheduler
  parameterization is defined, when the action is executed. Actions can be the writing of Variables or calling Methods , but can also be extended to other actions
• OPC-10000-25 – OPC Unified Architecture - Part 25: Object Serialization
  4.1 Object Serialization Basic Concept
  Serialization is understood in this specification as the aggregation of the Values of different Variables belonging to a subset of the Information Model ( SerializationScope ) into the Value (SerializationValue
• OPC-10000-25 – OPC Unified Architecture - Part 25: Object Serialization
  4.4 SerializationScope and SerializationEntity
  SerializationScope is the SerializationEntity. It allows settings regarding the content of the DataType representing Variables ( SerializationFieldDataType ) inside the SerializationValue also and is the parent Object of the SerializedData Variable ... SerializedData Variable. The DataType of the SerializationValue maps all Values of the Variables in the SerializationScope (see Figure 3 ). The SerializationProperties are provided by the SerializationEntity (see Figure
• OPC-10000-25 – OPC Unified Architecture - Part 25: Object Serialization
  4.5 General Features
  SerializationScope is preserved. This means that the relationship of the Objects and Variables contributing to the SerializationValue is preserved. Servers can provide different serializations by providing different SerializationEntities
• OPC-10000-25 – OPC Unified Architecture - Part 25: Object Serialization
  5.1 Example Serialize RIO Channel Groups
  SerializationEntity 1" Object configures the "SerializationScope 1" by limiting the Variables belonging to the SerializationScope to those connected with HasRioProcessVariable References to the SerializationStartNode. A Client only ... shown in Figure 4 . Since the "ProcessValue" and "QualifierValue" Variables are part of this compact representation, reading the IO Data of all channels aggregated
• OPC-10000-25 – OPC Unified Architecture - Part 25: Object Serialization
  5.2 Example Serialization of PROFIenergy Data
  shown in Figure 5 . The SerializationScope shown in Figure 5 comprises all MeasurementValueType Variables which are components of the EnergyMeasurementType Objects organized in the "EnergyManagement" Folder Object
• OPC-10000-25 – OPC Unified Architecture - Part 25: Object Serialization
  6.1 Overview
  provides a consistent, compact representation of the Variable Values in the SerializationScope . Objects or Variables that are the root of such a serialization are called SerializationStartNodes and have HasSerializationEntity References ... their own SerializationFieldDataType . In the example shown in Figure 6 , the SerializationFieldDataTypes of the Variables in the SerializationScope equal the DataTypes of the original Values . Figure 6 - Example: Instance-specific
• OPC-10000-25 – OPC Unified Architecture - Part 25: Object Serialization
  6.2 Limitations
  Limitations Since the BrowseNames of the Variables in the SerializationScope are used as field names for the SerializationFieldDataType fields in the SerializationValue DataType , limitations for BrowseNames arise: The characters used
• OPC-10000-25 – OPC Unified Architecture - Part 25: Object Serialization
  6.3.2 SerializedData Variable
  write access, the Client's Session shall be able to successfully write all original Variables in the SerializationScope . If the write for any Variable fails, the write call shall fail
• OPC-10000-25 – OPC Unified Architecture - Part 25: Object Serialization
  6.3.7 CustomMetaDataProperties Property
  excluding the metadata comprising the EUInformation and EngineeringUnits Properties of the AnalogUnitType and AnalogUnitRangeType Variables in the SerializationScope . Figure 10 - CustomMetaDataProperties example The content of the CustomMetaDataProperties Property ... EngineeringUnits", value=EUInformation) for the Value of the represented Variable . Sub- Variables are represented with elements containing KeyValuePairs with keys equal to the BrowseNames of the Variables
• OPC-10000-25 – OPC Unified Architecture - Part 25: Object Serialization
  6.3.9 IncludeStatus, IncludeSourceTimestamp, and IncludeDictionaryReference Properties
  Properties The IncludeStatus Property is a Boolean indicating how the StatusCodes of the serialized Variables are serialized themselves. If True, the SerializationFieldDataType of the Variable shall always be a Structure ... field. The IncludeSourceTimestamp Property is a Boolean indicating how the sourceTimestamps of the serialized Variables are serialized themselves. If True, the SerializationFieldDataType of the Variable shall always be a Structure
• OPC-10000-25 – OPC Unified Architecture - Part 25: Object Serialization
  6.4.1 SerializationFieldDataType of Variables
  SerializationFieldDataType of Variables If Variables are serialized, the Value of the Variable is mapped also into the SerializationValue DataType of the SerializedData Variable . The Value is inserted as field into
• OPC-10000-25 – OPC Unified Architecture - Part 25: Object Serialization
  6.4.3 SerializationFieldDataType of Variables with Children
  SerializationFieldDataType of Variables with Children If the Variable has child nodes, the fields of the SerializationFieldDataType representing the Variable are generated as shown in Figure 12 for the V1 Variable ... Object tree. This is the case for Properties and "childless" Variables (see Figure 12 , left column, V1Type and V1ChildrenType with " Include-Properties " set to False
• OPC-10000-25 – OPC Unified Architecture - Part 25: Object Serialization
  6.4.4 SerializationFieldDataType of Objects with children
  Object , without an intermediate "Children" structure used in case of Variables with children. The SerializationFieldDataType for Variables with children are created according to chapter 6.4.3 Figure 14 - Serialization
• OPC-10000-25 – OPC Unified Architecture - Part 25: Object Serialization
  A.1 Model Instance: Variable with Components
  DataType structure generated by the Server for a SerializationScope with a Variable having other Variables as components, and one of these Variables also has Variables as components. The illustration shows
• OPC-10000-25 – OPC Unified Architecture - Part 25: Object Serialization
  A.4 Energy Measurement Values
  shows a SerializationScope configured to exclude the metadata Properties of the Objects and Variables reachable from the SerializationStartNode . The EnergyMeasurementType Object has a mandatory PeObjectNumber Property which is not part ... same applies to the PeMeasurementID , AccuracyDomain , AccuracyClass and EngineeringUnits Properties of the MeasurementValueType Variables (see OPC PE ) The SerializationValue DataType structure contains only fields for the Values of the MeasurementValueType
• OPC-10000-25 – OPC Unified Architecture - Part 25: Object Serialization
  A.5 Semantic Property Metadata in PubSub Scenarios
  metadata Properties attached to the EnergyMeasurementType Objects as well as to the MeasurementValueType Variables . The metadata can be conveyed to a PubSub Subscriber by coding this information into the Properties
• OPC-10000-25 – OPC Unified Architecture - Part 25: Object Serialization
  A.6 JSON encoding of FieldMetaData Properties
  values it describes by far (the JSON snippet only shows the metadata for 2 Variables ), demonstrating the usefulness of excluding the metadata from the SerializationScope especially for low-bandwidth requirements
• OPC-10000-81 – OPC Unified Architecture - Part 81: UAFX Connecting Devices and Information Model
  5.2.3 FunctionalEntity verification
  version (issued by the author of a FunctionalEntity ). It also supports checking any Variables defined by the application. It can include checking, for instance, specific additional properties (e.g., the existence
• OPC-10000-81 – OPC Unified Architecture - Part 81: UAFX Connecting Devices and Information Model
  5.3 ControlGroups
  occur if the given ControlGroup were selected for control. Locking can restrict access to Variables or Methods to a specific application/user. It can also just block all access to Variables
• OPC-10000-81 – OPC Unified Architecture - Part 81: UAFX Connecting Devices and Information Model
  5.4 ConfigurationData
  ConfigurationData ConfigurationData describes a collection of Variables within a FunctionalEntity that are used to set up and configure its functionality. As part of establishing a Connection between FunctionalEntities , some configuration ... Method allows any of the FunctionalEntity's ConfigurationData to be set. ConfigurationData can contain Variables that have the AccessLevelEx Attribute NonVolatile bit set to TRUE (see OPC 10000-3 ). After
• OPC-10000-81 – OPC Unified Architecture - Part 81: UAFX Connecting Devices and Information Model
  5.5.1 Overview
  data (for source of data, see OPC 10000-4 ). Changes in the values of Variables from a data source do not generate AuditEvents
• OPC-10000-81 – OPC Unified Architecture - Part 81: UAFX Connecting Devices and Information Model
  5.7 AliasNames and OPC UA FX
  defined in OPC 10000-17 ) that allows defining alternate names for Objects , Variables or Methods in an AddressSpace (see Figure 15 ). These names can be grouped into categories. The FindAlias ... used by the ConnectionManager . AliasNames allow offline engineering tools to assign alternate names to Variables or Objects that are used in the configuration (see Figure 16 ). These alternate names could
• OPC-10000-81 – OPC Unified Architecture - Part 81: UAFX Connecting Devices and Information Model
  6.2.2 AutomationComponentType definition
  Event EventType clause. Diagnostics is a FunctionalGroup ( Folder ) that contains Variables that report diagnostic statistics and counters (see OPC 10000-100 Recommended FunctionalGroup BrowseNames ). EstablishCallCount diagnostics counter Variable provides
• OPC-10000-81 – OPC Unified Architecture - Part 81: UAFX Connecting Devices and Information Model
  6.2.4.2 EstablishConnections signature
  requested ConnectionEndpoint was invalid. Bad_RequestNotAllowed The ConnectionEndpoint to be enabled references input Variables , which are referenced by another enabled ConnectionEndpoint . Bad_InvalidState A preconfigured ConnectionEndpoint exists
• OPC-10000-81 – OPC Unified Architecture - Part 81: UAFX Connecting Devices and Information Model
  6.2.4.3.2 Command VerifyAssetCmd
  command VerifyAssetCmd are formally defined in Table 10 . The StatusCodes related to individual verification Variables are formally defined in Table 33 and Table
• OPC-10000-81 – OPC Unified Architecture - Part 81: UAFX Connecting Devices and Information Model
  6.2.4.3.5 Command CreateConnectionEndpointCmd
  subtype specified in ConnectionEndpointTypeId. The BrowseName shall be set to Name, and all Variables shall be set according to Parameter . The appropriate entries in InputVariables and OutputVariables shall be populated
• OPC-10000-81 – OPC Unified Architecture - Part 81: UAFX Connecting Devices and Information Model
  6.2.4.3.7 Command SetConfigurationDataCmd
  related to ConfigurationData has IsPersistent set, SetStoredVariables (see 6.4.6.3 ) shall be called for all Variables indicated by Key having the NonVolatile bit in the AccessLevelEx Attribute not set. If ConfigurationData
• OPC-10000-81 – OPC Unified Architecture - Part 81: UAFX Connecting Devices and Information Model
  6.2.6 AutomationComponentCapabilitiesType
  FolderType defined in OPC 10000-5 . It shall be restricted to holding only Variables that reflect the capabilities of the AutomationComponentType . The AutomationComponentCapabilitiesType is formally defined in Table 26 . Table
• OPC-10000-81 – OPC Unified Architecture - Part 81: UAFX Connecting Devices and Information Model
  6.3.2 FxAssetType definition
  formal definition of the AssetConnectorType, see 6.3.4 . Diagnostics is a FunctionalGroup ( Folder ) that contains Variables that report diagnostic statistics and counters (see OPC 10000-100 Recommended FunctionalGroup BrowseNames). The UpTime
• OPC-10000-81 – OPC Unified Architecture - Part 81: UAFX Connecting Devices and Information Model
  6.3.3 VerifyAsset method
  Asset verification (see VerificationMode ). Each mode depends on a set of mandatory and optional Variables (see definition of AssetVerificationModeEnum in 10.4 ) to be present for verification. The VerifyAsset Method also ... accepts additional Variables for verification. An Asset implementing the VerifyAsset Method shall at least support the VerificationMode AssetCompatibility and expose the corresponding mandatory and implemented optional Variables in its Information
• OPC-10000-81 – OPC Unified Architecture - Part 81: UAFX Connecting Devices and Information Model
  6.4.2 FunctionalEntityType definition
  that companion specifications or vendors will define subtypes of FunctionalEntityType . Subtypes will define additional Variables that would exist in InputData , OutputData and ConfigurationData . The subtypes might also add Objects ... FunctionalGroups ( Configuration or Tuning ) to further organise configuration information. The optional Configuration FunctionalGroup contains Variables representing the configuration items of the FunctionalEntity (see OPC 10000-100 Recommended FunctionalGroup BrowseNames
• OPC-10000-81 – OPC Unified Architecture - Part 81: UAFX Connecting Devices and Information Model
  6.4.3 Verify method
  whether it is of the expected author, but also if it implements any optional Variables required by a Client application). It also supports verifying any Variables defined by the application ... Table 43 - Verify Method arguments Argument Description ExpectedVerificationVariables An array of NodeIdValuePair containing verification variables. NodeId shall be the NodeId of the node to verify, and for variables, the Value
• OPC-10000-81 – OPC Unified Architecture - Part 81: UAFX Connecting Devices and Information Model
  6.4.4 InputsFolderType
  BaseDataVariableType OP ConformanceUnits UAFX FunctionalEntity Base The InputsFolderType provides for the grouping of input variables. It shall be restricted to hold only Variables, SubscriberCapabilities or nested <InputGroup ... AutomationComponent . The restrictions for InputData only apply if the Connection is established with Variables referenced in InputData or any subfolders. If an entry is an empty array, then it shall
• OPC-10000-81 – OPC Unified Architecture - Part 81: UAFX Connecting Devices and Information Model
  6.4.5 OutputsFolderType
  BaseDataVariableType OP ConformanceUnits UAFX FunctionalEntity Base The OutputsFolderType provides for the grouping of output variables. It shall be restricted to hold only Variables, PublisherCapabilities or nested < OutputGroup ... AutomationComponent . The restrictions for OutputData only apply if the Connection is established with Variables referenced in OutputData or any subfolders. If an entry is an empty array, then it shall
• OPC-10000-81 – OPC Unified Architecture - Part 81: UAFX Connecting Devices and Information Model
  6.4.6.1 Overview
  Overview The ConfigurationDataFolderType is used to organise ConfigurationData Variables and provides the Methods for supporting the storage of Variables (see 5.4 ). A ConfigurationDataFolder may contain sub- Folders derived from FunctionalGroupType
• OPC-10000-81 – OPC Unified Architecture - Part 81: UAFX Connecting Devices and Information Model
  6.4.6.2 ConfigurationDataFolderType definition
  ConformanceUnits UAFX FunctionalEntity Base < ConfigurationVariable > represents the optional configuration data. The Variables in this Folder shall be Organized in this Folder, or the Folder shall reference the Variables ... subtypes of the HasChild Reference (HasProperty, HasComponent or other subtypes ). The BrowseNames of Variables in this Folder shall be unique within this Folder . All Variables in this folder shall
• OPC-10000-81 – OPC Unified Architecture - Part 81: UAFX Connecting Devices and Information Model
  6.4.6.3 SetStoredVariables method
  method The optional SetStoredVariables Method allows a Client to store current values of configuration Variables for the FunctionalEntity and its SubFunctionalEntities . The FunctionalEntity shall apply the stored values ... configuration variables after a power cycle. The signature of this Method is specified below; the arguments are defined in Table 50 . Signature SetStoredVariables ( [in] 0:NodeId[] VariablesToStore, [out] 0:StatusCode
• OPC-10000-81 – OPC Unified Architecture - Part 81: UAFX Connecting Devices and Information Model
  6.4.6.4 ClearStoredVariables Method
  optional ClearStoredVariables Method allows a Client to clear the Variable from the list of Variables that are to be restored. The signature of this Method is specified below; the arguments ... ClearStoredVariables Method arguments Argument Description VariablesToClear An array of NodeId containing configuration data variables . Results An array of StatusCode corresponding to the VariablesToClear input argument that indicates any errors that
• OPC-10000-81 – OPC Unified Architecture - Part 81: UAFX Connecting Devices and Information Model
  6.4.6.5 ListStoredVariables
  ListStoredVariables The optional ListStoredVariables Method allows a Client to list the Variables that are currently in storage. The signature of this Method is specified below; the arguments are defined
• OPC-10000-81 – OPC Unified Architecture - Part 81: UAFX Connecting Devices and Information Model
  6.4.7 FunctionalEntityCapabilitiesType
  FolderType defined in OPC 10000-5 . It shall be restricted to holding only Variables that reflect the capabilities of the FunctionalEntity . The FunctionalEntityCapabilitiesType is formally defined in Table 60 . Table
• OPC-10000-81 – OPC Unified Architecture - Part 81: UAFX Connecting Devices and Information Model
  6.5.1 Overview
  application. ControlGroups can be used by an application to help understand how the Variables (inputs, outputs, configuration) and Methods are logically related to each other in the application. ControlGroups utilise
• OPC-10000-81 – OPC Unified Architecture - Part 81: UAFX Connecting Devices and Information Model
  6.5.2 ControlGroupType definition
  restriction on the grouped items. The restriction can include Objects (input and configuration Variables ) and Method invocations. The restriction can block all changes to Variables or restrict changes to only ... instances of LockingServices . When a ControlGroup is assigned to a user or application, the Variables or Methods in ListToBlock or ListToRestrict are associated with that user or application (that user
• OPC-10000-81 – OPC Unified Architecture - Part 81: UAFX Connecting Devices and Information Model
  6.6.1 Overview
  Figure 27 . Figure 27 - ConnectionEndpointType illustration A ConnectionEndpoint further describes the link between Variables in the FunctionalEntityType and the communication model used for exchange. Communication models can be Client Server ... PubSub . This type specifies the exchanged Variables and contains the status of the Connection . Subtypes of ConnectionEndpointType provide details specific to the utilised communication model and specify how the Connection
• OPC-10000-81 – OPC Unified Architecture - Part 81: UAFX Connecting Devices and Information Model
  6.6.2 ConnectionEndpointType definition
  specific communication model is specified in the subtypes of ConnectionEndpointType . The optional InputVariables indicate Variables that are to have their values updated by the communication model connected to the ConnectionEndpoint ... referenced Variables shall be in the InputData of the FunctionalEntity related to the ConnectionEndpoint or a SubFunctionalEntity of the FunctionalEntity. The referenced Variables may be a subset of the Variables
• OPC-10000-81 – OPC Unified Architecture - Part 81: UAFX Connecting Devices and Information Model
  6.7.2 ConnectionManagerType definition
  ConnectionManage that failed. This applies to local and remote calls. The Diagnostics FunctionalGroup contains Variables and Methods for diagnostics (see OPC 10000-100 Recommended FunctionalGroup BrowseNames ). For UAFX, this includes
• OPC-10000-81 – OPC Unified Architecture - Part 81: UAFX Connecting Devices and Information Model
  6.7.6 ConnectionManagerCapabilitiesType
  FolderType defined in OPC 10000-5 . It shall be restricted to holding only Variables that reflect the capabilities of the ConnectionManager . The ConnectionManagerCapabilitiesType is formally defined in Table 88 . Table
• OPC-10000-81 – OPC Unified Architecture - Part 81: UAFX Connecting Devices and Information Model
  6.9.2 ConnectionConfigurationSetStateMachineType definition
  HasCause True 4:ConnectionManager 4:ProcessConnectionConfigurationSets 0:HasEffect True 4:ConnectionConfigurationSetProcessingStartedEventType The component Variables of the ConnectionConfigurationSetStateMachineType have additional Attributes defined in Table 93 . Table 93 - ConnectionConfigurationSetStateMachineType attribute values
• OPC-10000-81 – OPC Unified Architecture - Part 81: UAFX Connecting Devices and Information Model
  7.2 IFunctionalEntityType Interface definition
  HasComponent Variable 3:FailedVerificationCount 0:UInt32 0:BaseDataVariableType O The definitions of all Properties , Variables and Objects that are used in this Interface are provided in 6.4.2 . Examples
• OPC-10000-81 – OPC Unified Architecture - Part 81: UAFX Connecting Devices and Information Model
  B.3.2.1 Extending an existing type
  provided by the Interface were updated to include references to the already defined (existing) Variables in the MyCompanionSpec model. The OPC UA FX specification provides a required instance model. This
• OPC-10000-81 – OPC Unified Architecture - Part 81: UAFX Connecting Devices and Information Model
  B.3.2.2 Extending an instance of an existing type
  Interfaces . Furthermore, the references are added to provide the mapping to the existing Variables . When to use: Extending instances with Interfaces is used when an Information Model is already instantiated
• OPC-10000-81 – OPC Unified Architecture - Part 81: UAFX Connecting Devices and Information Model
  B.3.4 Parallel use of OPC UA FX and existing UA models
  instance of FxAssetType . The FunctionalEntity organizes in its InputData , OutputData , and ConfigurationData Variables, which are components of the MyModelInstance (derived from the MyCompanionSpecType). Figure B.7 - Parallel ... existing UA models Another variance would be defining separate Variables in the FunctionalEntity , where the underlying device just references the same memory location for its value, as a Variable being