Figure 11 – Overview of Result Information Model
The JoiningSystemResultManagementType is a subtype of ResultManagementType and provides mechanism to access results generated by the underlying joining system. It is formally defined in Table 56.
Table 56 – JoiningSystemResultManagementType Definition
Attribute |
Value |
||||
BrowseName |
JoiningSystemResultManagementType |
||||
IsAbstract |
False |
||||
References |
Node Class |
BrowseName |
DataType |
TypeDefinition |
Other |
Subtype of the 5:ResultManagementType defined in OPC 40001-101, which means it inherits the InstanceDeclarations of that Node. |
|||||
0:HasComponent |
Object |
5:Results |
|
0:FolderType |
O |
0:GeneratesEvent |
ObjectType |
JoiningSystemResultReadyEventType |
|
|
|
Conformance Units |
|||||
IJT Get Latest Result |
|||||
IJT Get Result by Id |
|||||
IJT Get Result with Filter Criteria |
|||||
IJT Result Variable Access |
|||||
IJT Result Event Access |
Note:
- The optional 5:ResultTransfer Object is not used in the Joining System.
- The definition of the methods is available in OPC 40001-101.
The components of the JoiningSystemResultManagementType have additional subcomponents which are defined in Table 57.
Table 57 – JoiningSystemResultManagementType Additional Subcomponents
Source Path |
Reference |
NodeClass |
BrowseName |
DataType |
TypeDefinition |
Others |
5:Results |
0:HasComponent |
Variable |
<ResultVariable> |
5:ResultDataType |
JoiningSystemResultType |
OP |
Each <ResultVariable> represents a result.
Note: It is recommended to use the BrowseName of the <ResultVariable> as “Result” if only one instance of the variable is exposed in the address space. The implementation of ResultVariable is application specific.