Figure 1 – Pelletizer_InterfaceType Overview
Table 1 – Pelletizer_InterfaceType Definition
|
Attribute |
Value |
||||
|
BrowseName |
Pelletizer_InterfaceType |
||||
|
IsAbstract |
False |
||||
|
References |
Node Class |
BrowseName |
DataType |
TypeDefinition |
Other |
|
Subtype of 4:ExtrusionDeviceType (defined in OPC 40084-1) |
|||||
|
0:HasComponent |
Object |
Drive |
|
3:DriveType |
M |
|
0:HasProperty |
Variable |
PelletizerClosed |
0:Boolean |
0:PropertyType |
O, RO |
|
0:HasProperty |
Variable |
WaterFlowActive |
0:Boolean |
0:PropertyType |
O, RO |
|
0:HasComponent |
Variable |
CutGap |
0:Double |
0:AnalogUnitType |
O, RO |
|
0:HasComponent |
Object |
TemperatureZones |
|
4:ExtrusionTemperatureZonesType |
O |
|
0:HasComponent |
Object |
PressureZones |
|
3:MeasuringDevicesType |
O |
|
0:HasComponent |
Object |
KnifePackage_<Nr> |
|
KnifePackageType |
OP |
|
0:HasComponent |
Object |
DiePlate_<Nr> |
|
DiePlateType |
OP |
The BrowseName of the object instance shall be "Pelletizer_<Manufacturer>_<SerialNumber>"
Example: "Pelletizer_Erema_0123456".
The instance(s) of Pelletizer_InterfaceType shall be located under the DeviceSet Object of the Server (see OPC UA Part 100).
NOTE: If the OPC UA server is implemented in the control of the pelletizer so only one instance of Pelletizer_InterfaceType will be created. But it is also possible that one OPC UA server is connected to several machine controls as one interface to the MES. In this case several instances of Pelletizer_InterfaceType will be created.