The VariableSetType is used for storing additional sample data that was created during a run. It is formally defined in Table 76.
Table 76 – VariableSetType Definition
Attribute |
Value |
||||
BrowseName |
VariableSetType |
||||
IsAbstract |
False |
||||
References |
Node Class |
BrowseName |
DataType |
TypeDefinition |
Other |
Subtype of the SetType defined in 7.2.5 |
|||||
0:HasComponent |
Variable |
<VariableSetElement > |
BaseDataType |
BaseVariableType |
OP |
0:HasComponent |
Object |
<SetElement> |
|
BaseObjectType |
OP |
Conformance Units |
|||||
LADS VariableSetType |
|||||
|
VariableSetElement: Placeholder for vendor-specific properties.
SetElement: Placeholder for one or more objects that hold vendor-specific data that was created during a run. Objects follow these rules:
- The type of each object shall be BaseObjectType. Each object may have arbitrary child nodes.
- The structure and data contained in each object are vendor specific.
- It is up to the vendor whether the list contains objects with the same kind of data or objects of different kinds of data.
- The structure may be nested.
For objects and properties added to the VariableSet, vendors shall use only types from the OPC UA base specification, specifically:
- Vendors shall use only the built-in data types defined in OPC UA Part 10000-6 (https://reference.opcfoundation.org/Core/Part6/v104/5.1.2)
- Vendors shall use only simple variable types and simple object types (i.e., types that do not define child nodes beneath them).
Vendors should annotate each node with a reference to a dictionary entry.
Vendors should specify the structure in their documentation. See Annex D for a typical example.