STSysType is an abstract object that represents the basic framework for every system in the area of Surface Technology. All other systems are created below as SubType of this ObjectType. The STSysType is formally defined in Table 15.
Table 15 – STSysType Definition
|
Attribute |
Value |
||||
|
BrowseName |
STSysType |
||||
|
IsAbstract |
True |
||||
|
References |
Node Class |
BrowseName |
DataType |
TypeDefinition |
Other |
|
Subtype of the BaseObjectType defined in OPC 10000-5 |
|||||
|
0:HasAddIn |
Object |
2:Identification |
|
4:MachineIdentificationType |
O |
|
0:HasAddIn |
Object |
4:Components |
|
4:MachineComponentsType |
O |
|
0:HasComponent |
Object |
4:Monitoring |
|
4:MonitoringType |
O |
|
0:HasComponent |
Object |
4:MachineryBuildingBlocks |
|
0:FolderType |
M |
|
0:HasComponent |
Object |
Description |
|
0:FolderType |
O |
Identification is used as defined in OPC 40001-1. It represents numerous identification features of the system.
Components is representing a collection of all physical components of the Surface Technology System.
Monitoring is representing a collection of ObjectTypes and VariableTypes, representing the current state of the process, that are not assigned to a component but to the overall system. The Monitoring of the overall system may contain specific process values of its components.
MachineryBuildingBlocks is representing a folder that directly references all those building blocks of the OPC UA for Machinery (OPC 40001-1, OPC 40001-3) which are implemented as an add-in.
Description is representing a collection of ObjectTypes and VariableTypes that describe the overall system. This may be information that is not an identifier for the system or that is static in character but must be stored on the server for some use cases. One example is the mesh size of a sieve, which does not vary but can be queried by cooperating systems.
The components of the STSysType have additional references which are defined in Table 16.
Table 16 – STSysType Additional References
|
SourceBrowsePath |
Reference Type |
Is Forward |
TargetBrowsePath |
|||
|
4:MachineryBuildingBlocks |
0:HasAddIn |
True |
2:Identification |
|||
|
4:MachineryBuildingBlocks |
0:HasAddIn |
True |
4:Components |
|||
|
4:MachineryBuildingBlocks |
0:HasAddIn |
True |
4:Monitoring |
|||
|
4:MachineryBuildingBlocks |
0:HasAddIn |
True |
|
|||
|
4:MachineryBuildingBlocks |
0:HasAddIn |
True |
|
The components of the STSysType have additional subcomponents which are defined in Table 17.
Table 17 – STSysType Additional Subcomponents
|
Source Path |
Reference |
NodeClass |
BrowseName |
DataType |
TypeDefinition |
Others |
||
|
4:Monitoring |
0:HasComponent |
Object |
4:Status |
|
0:FolderType |
O |
||
|
0:HasComponent |
Object |
4:MachineryItemState |
|
4:MachineryItemState_StateMachineType |
O |
||
|
0:HasComponent |
Object |
4:MachineryOperationMode |
|
4:MachineryOperationModeStateMachineType |
O |
||
|
4:MachineryBuildingBlocks |
0:HasAddIn |
Object |
2:OperationCounters |
|
4:MachineryOperationCounterType |
O |
Status is used as defined in OPC 40001-1.
MachineryItemState is used as defined in OPC 40001-1. It represents a StateMachine that shows the current machine state.
MachineryOperationMode is used as defined in OPC 40001-1. It represents a StateMachine that shows the current operational state of the overall system.
OperationCounters is used as defined in OPC 40001-1. All counters that are implemented according to the MachineryOperationCounterType of the OPC 40001-1 shall be integrated with the HasComponent reference under this Object.
STCompType is an abstract object that represents the basic framework for every component in the area of Surface Technology. All other components are created below as Subtype of this ObjectType. The STCompType is formally defined in Table 18.
Table 18 – STCompType Definition
|
Attribute |
Value |
||||
|
BrowseName |
STCompType |
||||
|
IsAbstract |
True |
||||
|
References |
Node Class |
BrowseName |
DataType |
TypeDefinition |
Other |
|
Subtype of the BaseObjectType defined in OPC 10000-5 |
|||||
|
0:HasAddIn |
Object |
2:Identification |
|
4:MachineryComponentIdentificationType |
O |
|
0:HasComponent |
Object |
4:Monitoring |
|
4:MonitoringType |
O |
|
0:HasComponent |
Object |
4:MachineryBuildingBlocks |
|
0:FolderType |
M |
|
0:HasComponent |
Object |
Description |
|
0:FolderType |
O |
Identification is used as defined in OPC 40001-1. It represents numerous identification features of the component.
Monitoring is representing a collection of ObjectTypes and VariableTypes, representing the current state of the process that are assigned to the component.
MachineryBuildingBlocks is representing a folder that directly references all those building blocks of the OPC UA for Machinery (OPC 40001-1, OPC 40001-3) which are implemented as an add-in.
Description is representing a collection of ObjectTypes and VariableTypes that describe the component. This may be information that is not an identifier for the component or that is static in character but must be stored on the server for some use cases. One example is the mesh size of a sieve, which does not vary but can be queried by cooperating systems.
The components of the STCompType have additional references which are defined in Table 19.
Table 19 – STCompType Additional References
|
SourceBrowsePath |
Reference Type |
Is Forward |
TargetBrowsePath |
|||
|
4:MachineryBuildingBlocks |
0:HasAddIn |
True |
4:Monitoring |
|||
|
4:MachineryBuildingBlocks |
0:HasAddIn |
True |
2:Identification |
|||
|
4:MachineryBuildingBlocks |
0:HasAddIn |
True |
|
|||
|
4:MachineryBuildingBlocks |
0:HasAddIn |
True |
|
The components of the STCompType have additional subcomponents which are defined in Table 20.
Table 20 – STCompType Additional Subcomponents
|
Source Path |
Reference |
NodeClass |
BrowseName |
DataType |
TypeDefinition |
Others |
||
|
4:Monitoring |
0:HasComponent |
Object |
4:Status |
|
0:FolderType |
O |
||
|
0:HasComponent |
Object |
4:MachineryItemState |
|
4:MachineryItemState_StateMachineType |
O |
||
|
0:HasComponent |
Object |
4:MachineryOperationMode |
|
4:MachineryOperationModeStateMachineType |
O |
||
|
4:MachineryBuildingBlocks |
0:HasAddIn |
Object |
2:OperationCounters |
|
4:MachineryOperationCounterType |
O |
Status is used as defined in OPC 40001-1.
MachineryItemState is used as defined in OPC 40001-1. It represents a StateMachine that shows the current machine state.
MachineryOperationMode is used as defined in OPC 40001-1. It represents a StateMachine that shows the current operational state of the overall system.
OperationCounters is used as defined in OPC 40001-1. All counters that are implemented according to the MachineryOperationCounterType of the OPC 40001-1 shall be integrated with the HasComponent reference under this Object.
The STSystemControllerType provides the possibility to control and influence different systems with the help of a controller and is formally defined in Table 21.
Table 21 – STSystemControllerType Definition
|
Attribute |
Value |
||||
|
BrowseName |
STSystemControllerType |
||||
|
IsAbstract |
True |
||||
|
References |
Node Class |
BrowseName |
DataType |
TypeDefinition |
Other |
|
Subtype of the BaseObjectType defined in OPC 10000-5 |
|||||
|
0:HasComponent |
Object |
State |
|
0:FolderType |
M |
|
0:HasComponent |
Object |
4:MachineryBuildingBlocks |
|
0:FolderType |
M |
State represents a collection of state machines and status information about the controller.
MachineryBuildingBlocks is representing a folder that directly references all those building blocks of the OPC UA for Machinery (OPC 40001-1, OPC 40001-3) which are implemented as an add-in.
The components of the STSystemControllerType have additional references which are defined in Table 22.
Table 22 – STSystemControllerType Additional References
|
SourceBrowsePath |
Reference Type |
Is Forward |
TargetBrowsePath |
||
|
4:MachineryBuildingBlocks |
0:HasAddIn |
True |
|
||
|
4:MachineryBuildingBlocks |
0:HasAddIn |
True |
|
The components of the STSystemControllerType have additional subcomponents which are defined in Table 23.
Table 23 – STSystemControllerType Additional Subcomponents
|
Source Path |
Reference |
NodeClass |
BrowseName |
DataType |
TypeDefinition |
Others |
|
State |
0:HasComponent |
Object |
4:MachineryItemState |
|
4:MachineryItemState_StateMachineType |
O |
|
State |
0:HasComponent |
Object |
4:MachineryOperationMode |
|
4:MachineryOperationModeStateMachineType |
O |
MachineryItemState is used as defined in OPC 40001-1. It represents a StateMachine that shows the consolidated state of the systems the controller manages.
MachineryOperationMode is used as defined in OPC 40001-1. It represents a StateMachine that shows the consolidated state of the systems the controller manages.
The STBaseControllerType provides basic functionalities for a simple controller. It is formally defined in Table 24.
Table 24 – STBaseControllerType Definition
|
Attribute |
Value |
||||
|
BrowseName |
STBaseControllerType |
||||
|
IsAbstract |
False |
||||
|
References |
Node Class |
BrowseName |
DataType |
TypeDefinition |
Other |
|
Subtype of the STSystemControllerType |
|||||
|
0:HasComponent |
Object |
StartUp |
|
0:ProgramStateMachineType |
O |
|
0:HasComponent |
Object |
ShutDown |
|
0:ProgramStateMachineType |
O |
|
Conformance Units |
|||||
|
STBaseController Basic |
|||||
|
STBaseController MachineryItemState |
|||||
|
STBaseController MachineryOperationMode |
|||||
StartUp is used as defined in OPC 10000-10. It allows to establish the operational status of a system.
ShutDown is used as defined in OPC 10000-10. It allows to shut down a system.
The STJobManagementType has the ability to orchestrate the manufacturing process by enabling job management and assignment to the respective equipment.
It includes alias handling functionality as defined in OPC 10000-17.
The STJobManagementType is formally defined in Table 25.
Table 25 – STJobManagementType Definition
|
Attribute |
Value |
||||
|
BrowseName |
STJobManagementType |
||||
|
IsAbstract |
False |
||||
|
References |
Node Class |
BrowseName |
DataType |
TypeDefinition |
Other |
|
Subtype of the 6:JobManagementType defined in OPC 40001-3. |
|||||
|
0:HasComponent |
Object |
STJobManagementAliases |
|
0:AliasNameCategoryType |
O |
|
0:HasComponent |
Method |
AddAlias |
|
|
O |
|
0:HasComponent |
Method |
RemoveAlias |
|
|
O |
|
Conformance Units |
|||||
|
STJobManagement Alias |
|||||
The Method AddAlias enables a new alias entry to be assigned. The signature of this Method is specified below.
Signature
AddAlias (
[in]0:StringAliasName,
[in]0:NodeIdReferenceID,
[in]0:ExpandedNodeIdTarget,
[out]0:NodeIdAliasNode
);
Table 26 – AddAlias Method Arguments
|
Argument |
Description |
|
AliasName |
The alias to be assigned to a particular node |
|
ReferenceID |
The ID of the reference that should apply to the new alias |
|
Target |
The exact node to which the alias should be assigned to |
|
AliasNode |
The ID of the node that has now been assigned the alias |
Table 27 – AddAlias Method AddressSpace Definition
|
Attribute |
Value |
||||
|
BrowseName |
AddAlias |
||||
|
References |
Node Class |
BrowseName |
DataType |
TypeDefinition |
Other |
|
0:HasProperty |
Variable |
InputArguments |
Argument[] |
0:PropertyType |
M |
|
0:HasProperty |
Variable |
OutputArguments |
Argument[] |
0:PropertyType |
M |
The Method RemoveAlias enables to delete already existing alias entries. The signature of this Method is specified below.
Signature
RemoveAlias (
[in]0:StringAliasName,
[in]0:NodeIdReferenceID
);
Table 28 – RemoveAlias Method Arguments
|
Argument |
Description |
|
AliasName |
The alias that has to be removed |
|
ReferenceID |
The ID of the reference that has to be removed |
Table 29 – RemoveAlias Method AddressSpace Definition
|
Attribute |
Value |
||||
|
BrowseName |
RemoveAlias |
||||
|
References |
Node Class |
BrowseName |
DataType |
TypeDefinition |
Other |
|
0:HasProperty |
Variable |
InputArguments |
Argument[] |
0:PropertyType |
M |